- Tei-council - lists.tei-c.org

Re: [Tei-council] Draft Roma beta announcement
by James Cummings 17 Sep '19

17 Sep '19

Do we have plans for it to support RelaxNG? Or are we using it as a way to help people decide to move to Pure ODD. The latter seems a defensible reason to me and means Raff doesn't need to write ability to cope with Relax NG. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Elisa Beshero-Bondar <ebb8(a)pitt.edu> Sent: 16 September 2019 13:02 To: Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Cc: TEI Council <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] Draft Roma beta announcement Hi Raff, My suggestion is just to reverse the order of the 2nd and 3rd sentences like this: The TEI Council has released a new version of Roma, the web interface for creating TEI customizations. Find it at https://romabeta.tei-c.org/ Council member Raff Viglianti is the lead developer. Cheers, Elisa On Mon, Sep 16, 2019 at 12:28 PM Raffaele Viglianti <raffaeleviglianti(a)gmail.com<mailto:raffaeleviglianti@gmail.com>> wrote: Wordsmithing much appreciated! I figure Martina would send this. Dear TEI-L The TEI Council has released a new version of Roma, the web interface for creating TEI customizations. Council member Raff Viglianti is the lead developer. Find it at https://romabeta.tei-c.org/ The software is currently in beta and we invite the TEI community to try it out and report issues on the GitHub repository https://github.com/teic/romajs Please note that Roma beta currently only supports pure ODD and uploading customizations with RelaxNG content models will fail. There is also no support yet for @source attributes so all customizations will start from the latest stable version of the TEI. This will be addressed in the future. Roma "classic" will remain available at https://roma.tei-c.org/ until the new version reaches a more stable and complete status, at which point it will be replaced. After that, we plan to keep it available at a different address but it will not get further updated. If you are at the TEI Conference and Members Meeting in Graz, please come visit Raff's poster about Roma this Thursday Sept 19 to learn more and leave suggestions! _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu<mailto:ebb8@pitt.edu> Development site: http://newtfire.org<http://newtfire.org/>

2 1

attending SIGs
by Mylonas, Elli 17 Sep '19

17 Sep '19

Hi all, I asked our fearless leader last night what she would like us to do about SIGs and she suggested that i ask the rest of council. I was wondering who is thinking of going to which SIG if any? Shouldn't we have some Council presence in order to know what is they are thinking about generally? I am thinking about periodicals and if necessary, but could just as well use the time otherwise. many thanks, --elli

6 5

Draft Roma beta announcement
by Raffaele Viglianti 16 Sep '19

16 Sep '19

Wordsmithing much appreciated! I figure Martina would send this. Dear TEI-L The TEI Council has released a new version of Roma, the web interface for creating TEI customizations. Council member Raff Viglianti is the lead developer. Find it at https://romabeta.tei-c.org/ The software is currently in beta and we invite the TEI community to try it out and report issues on the GitHub repository https://github.com/teic/romajs Please note that Roma beta currently only supports pure ODD and uploading customizations with RelaxNG content models will fail. There is also no support yet for @source attributes so all customizations will start from the latest stable version of the TEI. This will be addressed in the future. Roma "classic" will remain available at https://roma.tei-c.org/ until the new version reaches a more stable and complete status, at which point it will be replaced. After that, we plan to keep it available at a different address but it will not get further updated. If you are at the TEI Conference and Members Meeting in Graz, please come visit Raff's poster about Roma this Thursday Sept 19 to learn more and leave suggestions!

3 2

Broken links on the TEI site
by Martin Holmes 16 Sep '19

16 Sep '19

Hi Luis, At the TEI Council meeting, we noticed that if you go here: <https://tei-c.org/tools/stylesheets/> there are two broken links. The first goes to the XSLT documentation, which is missing from the server for some reason. The second is a link into the wiki, which goes to http rather than https. If you click on that link with Chrome, it'll work because Chrome pre-emptively tries https, but other browsers try plain http and get a 404. So: how do we get the Stylesheets and their documentation onto the server; and can you set up the explicit redirects for all http URLs to https? Also, can we have directory browsing turned on for the whole server? We want people to be able to browse around through various versions of the Guidelines etc. Thanks, Martin

1 0

Trial builds to address the circularity issue
by Martin Holmes 15 Sep '19

15 Sep '19

Hi all, Ahead of our discussion of the build circularity today, I've set up a couple of extra builds on my Jenkins server to try out one of the ideas we've been kicking around. I now have these build jobs: Stylesheets-dev-with-P5-release: this builds the dev branch of the Stylesheets, but using the p5subset.xml from the current P5 release. Stylesheets-dev-with-P5-release: this does a comprehensive build of the P5-dev branch (tests followed by a full build of the output), but using the latest release version of the TEI stylesheets. The stylesheets used to be available on the TEI website, but that's no longer the case, so I've ended up installing the deb packages on my Jenkins instead. They're still building, so I don't know whether they'll be successful or not, but if either or both of them fail, at least we'll have some idea of the kind of issues we might face if we do take this approach to avoiding the circularity problem. Cheers, Martin

1 0

Agenda F2F
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 Sep '19

14 Sep '19

https://docs.google.com/document/d/1d3OpQ8N-r1nJq0T0kUreUReCCG5FJ6P3HfHIEQ-…

1 0

Re: [Tei-council] F2F meeting in Graz
by James Cummings 11 Sep '19

11 Sep '19

Martina, Sounds great! And yes, quite a coincidence. Where I grew up weirdos would wear dirndl and lederhosen but only at Octoberfest. Looking forward to some good Styrian cooking and replenishing my supply of kürbiskernöl. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University From: Scholger, Martina (martina.scholger(a)uni-graz.at) Sent: Tuesday, 10 September, 22:32 Subject: [Tei-council] F2F meeting in Graz To: TEI Council Dear all, Here is some final information for the F2F meeting in Graz before you start your trip. The draft agenda can be found here, I will prepare the agenda in time. https://docs.google.com/document/d/1d3OpQ8N-r1nJq0T0kUreUReCCG5FJ6P3HfHIEQ-… Please add your travel information if you haven’t so far: https://docs.google.com/document/d/1Igi0Op1XVBNhv91tkcTpd_i6-fFIj1h1JPw5L8N… Our meeting starts on Saturday at Elisabethstraße 59 at 9 am – on the weekend there is swipe access only, so I will wait for you at the front door. See map: https://www.google.com/maps/d/edit?mid=1krAUIXid_1xRPu_yh-ESCDB2-S77ficR We have a room with a projector and also additional rooms for breakout sessions. There is also coffee 😊 Don’t forget your power plugs and adaptors. Evening plans: Friday: As you might know, we are currently running a pre-conference summer school. On Friday evening the workshop instructors will have dinner together at Herzl Weinstube at 6:30 pm. You are welcome to join us. Please let me know if you plan to come, so that we can make reservations accordingly (Syd, Anne, Raff, and James are already accounted for). Herzl Weinstube: https://www.dieherzl.at/speisen/ Prokopigasse 12 / Mehlplatz Saturday: The weekend is very busy in Graz, since there is a local festival going on where people are running around in Dirndl and Lederhosen. @James: it is really a coincidence that this festival always takes place when you are in Graz. And no, I don't have a Dirndl. I reserved a table at the "Kunsthaus" (artmuseum) to make sure that we will get some food, but we can decide on Saturday if we really want to go there or prefer something else: Kunsthauscafe: http://kunsthauscafe.co.at/download/KHC-Karte-19.pdf?cache=no Südtirolerplatz 2 Sunday: Dinner at my place, of course spouses and partners are welcome too. Monday: The joint Board/Council-dinner will be at Landhauskeller, which is in the city center. Landhauskeller: http://www.landhaus-keller.at/ Schmiedgasse 9 For lunch we can decide individually. We can either order from different restaurants and have it delivered by a bycicle service or we can have lunch somewhere close to the university. Have a save trip and see you soon in Graz! Best, Martina

7 6

F2F meeting in Graz
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Sep '19

10 Sep '19

Dear all, Here is some final information for the F2F meeting in Graz before you start your trip. The draft agenda can be found here, I will prepare the agenda in time. https://docs.google.com/document/d/1d3OpQ8N-r1nJq0T0kUreUReCCG5FJ6P3HfHIEQ-… Please add your travel information if you haven’t so far: https://docs.google.com/document/d/1Igi0Op1XVBNhv91tkcTpd_i6-fFIj1h1JPw5L8N… Our meeting starts on Saturday at Elisabethstraße 59 at 9 am – on the weekend there is swipe access only, so I will wait for you at the front door. See map: https://www.google.com/maps/d/edit?mid=1krAUIXid_1xRPu_yh-ESCDB2-S77ficR We have a room with a projector and also additional rooms for breakout sessions. There is also coffee 😊 Don’t forget your power plugs and adaptors. Evening plans: Friday: As you might know, we are currently running a pre-conference summer school. On Friday evening the workshop instructors will have dinner together at Herzl Weinstube at 6:30 pm. You are welcome to join us. Please let me know if you plan to come, so that we can make reservations accordingly (Syd, Anne, Raff, and James are already accounted for). Herzl Weinstube: https://www.dieherzl.at/speisen/ Prokopigasse 12 / Mehlplatz Saturday: The weekend is very busy in Graz, since there is a local festival going on where people are running around in Dirndl and Lederhosen. @James: it is really a coincidence that this festival always takes place when you are in Graz. And no, I don't have a Dirndl. I reserved a table at the "Kunsthaus" (artmuseum) to make sure that we will get some food, but we can decide on Saturday if we really want to go there or prefer something else: Kunsthauscafe: http://kunsthauscafe.co.at/download/KHC-Karte-19.pdf?cache=no Südtirolerplatz 2 Sunday: Dinner at my place, of course spouses and partners are welcome too. Monday: The joint Board/Council-dinner will be at Landhauskeller, which is in the city center. Landhauskeller: http://www.landhaus-keller.at/ Schmiedgasse 9 For lunch we can decide individually. We can either order from different restaurants and have it delivered by a bycicle service or we can have lunch somewhere close to the university. Have a save trip and see you soon in Graz! Best, Martina

1 0

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Sep '19

03 Sep '19

Dear all, Thanks for filling in the doodle! Our next meeting will take place on September 3rd, 11:00-12:00 PST, 14:00-15:00 EST, 20:00-21:00 CEST. I will send a hangouts link half an hour before we start. Best wishes, Martina

2 3

Re: [Tei-council] let's talk about food
by James Cummings 03 Sep '19

03 Sep '19

I believe invited experts are invited and thus earn any meals through their participation. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Martin Holmes <mholmes(a)uvic.ca> Sent: Monday, September 2, 2019 10:28:08 PM To: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] let's talk about food I eat everything (although I'm not sure whether I'm entitled to any food since I'm not elected :-)). Cheers, Martin On 2019-09-02 2:24 p.m., James Cummings wrote: > Hi Martina, > > No pertinent allergies. And I eat most things, those which I don't like > rarely seem to come up in Styrian cuisine. > > Many thanks, > James > > -- > Dr James Cummings, James.Cummings(a)newcastle.ac.uk > School of English Literature, Language, and Linguistics, Newcastle > University > > ------------------------------------------------------------------------ > *From:* Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of > Scholger, Martina (martina.scholger(a)uni-graz.at) > <martina.scholger(a)uni-graz.at> > *Sent:* Monday, September 2, 2019 9:34:06 PM > *To:* TEI Council <tei-council(a)lists.tei-c.org> > *Subject:* [Tei-council] let's talk about food > > Dear all, > > Planning ahead for our F2F meeting, I wanted to ask about your dietary > requirements. Please let me know if you have any restrictions or allergies. > > Best, > > Martina > > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council > _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Re: [Tei-council] let's talk about food
by James Cummings 02 Sep '19

02 Sep '19

Hi Martina, No pertinent allergies. And I eat most things, those which I don't like rarely seem to come up in Styrian cuisine. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Monday, September 2, 2019 9:34:06 PM To: TEI Council <tei-council(a)lists.tei-c.org> Subject: [Tei-council] let's talk about food Dear all, Planning ahead for our F2F meeting, I wanted to ask about your dietary requirements. Please let me know if you have any restrictions or allergies. Best, Martina

2 1

let's talk about food
by Scholger, Martina (martina.scholger＠uni-graz.at) 02 Sep '19

02 Sep '19

Dear all, Planning ahead for our F2F meeting, I wanted to ask about your dietary requirements. Please let me know if you have any restrictions or allergies. Best, Martina

1 0

Re: [Tei-council] Issue 1908
by James Cummings 19 Aug '19

19 Aug '19

Yes, the real difference is that for teidata.enumerated then you should have a valList in your ODD enumerating the specific values for your project. Indeed... if we wanted to add checks into an ODD editor like Roma, one could have it check through all classes and elements included in the ODD and find any attributes with teidata.enumerated and check that they have a valList, and if not prompt a user to enter one. That would, however, be quite strict, so maybe only in a future checker 'strict' mode (otherwise just a warning). ;-) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: 19 August 2019 19:38 To: James Cummings <James.Cummings(a)newcastle.ac.uk> Cc: tei-council(a)lists.tei-c.org <tei-council(a)lists.tei-c.org> Subject: Re: [Tei-council] Issue 1908 Sounds fine to me. It looks like teidata.enumerated is just a wrapper for teidata.word anyway...? Raff On Mon, Aug 19, 2019 at 2:20 PM James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: https://github.com/TEIC/TEI/issues/1908 https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Although I fixed the corrigible error for this ticket 25 days ago (within minutes of it being submitted ;-)) I noticed that the datatype for the @role attribute on <org> is teidata.word. For another issue I was looking at the @role attribute usage in other places and it is usually teidata.enumerated and that would make sense with this attribute as well. Any objections if I modified tei:org/@role to be teidata.enumerated instead of teidata.word? (This has no backwards compatibility issues as far as I'm aware, but means that a project _should_ document this list of possible values... which is a good thing.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Issue 1908
by James Cummings 19 Aug '19

19 Aug '19

https://github.com/TEIC/TEI/issues/1908 https://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rel… Although I fixed the corrigible error for this ticket 25 days ago (within minutes of it being submitted ;-)) I noticed that the datatype for the @role attribute on <org> is teidata.word. For another issue I was looking at the @role attribute usage in other places and it is usually teidata.enumerated and that would make sense with this attribute as well. Any objections if I modified tei:org/@role to be teidata.enumerated instead of teidata.word? (This has no backwards compatibility issues as far as I'm aware, but means that a project _should_ document this list of possible values... which is a good thing.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University

3 2

Call in 20 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Aug '19

19 Aug '19

Dear all, our call starts in 20 minutes: https://docs.google.com/document/d/1SwwoO1XHVGIvRsSOKov3fzz9qkhFnUg80BWrU_k… Best, Martina

2 1

Stylesheets meeting in just over 4 hours
by Syd Bauman 16 Aug '19

16 Aug '19

We're planning to meet at 20:00Z (13:00 PDT, 16:00 EDT, 21:00 BST, 22:00 CEST). Main topic of discussion will be ticket 370. Google Hangouts, I presume, but feel free to tell me to use Skype or Google Whatever instead.

3 4

Build failed in Jenkins: Stylesheets-dev #1
by mholmes＠uvic.ca 15 Aug '19

15 Aug '19

See <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/1/display/redirect> Changes: ------------------------------------------ Started by an SCM change Running as SYSTEM Building in workspace <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/> No credentials specified Cloning the remote Git repository Cloning repository https://github.com/TEIC/Stylesheets.git > git init <https://teijenkins.hcmc.uvic.ca/job/Stylesheets-dev/ws/> # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git --version # timeout=10 > git fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/TEIC/Stylesheets.git # timeout=10 > git config --add remote.origin.fetch +refs/heads/*:refs/remotes/origin/* # timeout=10 > git config remote.origin.url https://github.com/TEIC/Stylesheets.git # timeout=10 Fetching upstream changes from https://github.com/TEIC/Stylesheets.git > git fetch --tags --progress https://github.com/TEIC/Stylesheets.git +refs/heads/*:refs/remotes/origin/* # timeout=10 > git rev-parse refs/remotes/origin/dev^{commit} # timeout=10 > git rev-parse refs/remotes/origin/origin/dev^{commit} # timeout=10 Checking out Revision e2d67981faa8d51f3c6a4c529d73783d9c01fd1c (refs/remotes/origin/dev) > git config core.sparsecheckout # timeout=10 > git checkout -f e2d67981faa8d51f3c6a4c529d73783d9c01fd1c # timeout=10 Commit message: "incrementing post-release version 7.48.0a" First time build. Skipping changelog. > git tag -a -f -m Jenkins Build #1 jenkins-Stylesheets-dev-1 # timeout=10 FATAL: Could not apply tag jenkins-Stylesheets-dev-1 hudson.plugins.git.GitException: Command "git tag -a -f -m Jenkins Build #1 jenkins-Stylesheets-dev-1" returned status code 128: stdout: stderr: *** Please tell me who you are. Run git config --global user.email "you(a)example.com" git config --global user.name "Your Name" to set your account's default identity. Omit --global to set the identity only in this repository. fatal: unable to auto-detect email address (got 'jenkins(a)teijenkins.(none)') at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2318) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2248) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommandIn(CliGitAPIImpl.java:2244) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1777) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.launchCommand(CliGitAPIImpl.java:1789) at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1658) Caused: hudson.plugins.git.GitException: Could not apply tag jenkins-Stylesheets-dev-1 at org.jenkinsci.plugins.gitclient.CliGitAPIImpl.tag(CliGitAPIImpl.java:1660) at hudson.plugins.git.GitAPI.tag(GitAPI.java:274) at hudson.plugins.git.extensions.impl.PerBuildTag.onCheckoutCompleted(PerBuildTag.java:30) at hudson.plugins.git.GitSCM.checkout(GitSCM.java:1256) at hudson.scm.SCM.checkout(SCM.java:504) at hudson.model.AbstractProject.checkout(AbstractProject.java:1208) at hudson.model.AbstractBuild$AbstractBuildExecution.defaultCheckout(AbstractBuild.java:574) at jenkins.scm.SCMCheckoutStrategy.checkout(SCMCheckoutStrategy.java:86) at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:499) at hudson.model.Run.execute(Run.java:1815) at hudson.model.FreeStyleBuild.run(FreeStyleBuild.java:43) at hudson.model.ResourceController.execute(ResourceController.java:97) at hudson.model.Executor.run(Executor.java:429) Archiving artifacts

1 1

Next call: Monday, August 19
by Scholger, Martina (martina.scholger＠uni-graz.at) 13 Aug '19

13 Aug '19

Dear all, Our next meeting is on Monday, August 19 (EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30). This is the agenda - please add topics: https://docs.google.com/document/d/1SwwoO1XHVGIvRsSOKov3fzz9qkhFnUg80BWrU_k… Hugh, could you please start the call? If you have time, please have a look at the open tickets from the Washington meeting (see table in the agenda). Best, Martina

1 0

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Aug '19

06 Aug '19

Dear all, Here is a reminder for the Doodle for our next Infrastructure Group meeting: https://doodle.com/poll/rxxdrnkkmd9ywdbg. I added the first week of September to increase our chance to meet. Best, Martina

1 0

Re: [Tei-council] Enable CORS on the TEI Vault
by Raffaele Viglianti 28 Jul '19

28 Jul '19

Thanks Luis, I'm glad you were able to figure something out! I just tested and it all seems to be working. All the best, Raff On Fri, Jul 26, 2019 at 4:05 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > Hi Raff, > > I found a way to enable it without impacting security. > You should be good to go. > > Cheers, > ----- > -Luis > > On Jul 26, 2019, at 11:54 AM, Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > > Hi Luis, > > Any more thoughts on this? (Or from other council members?) For the time > being I'm switching to https://vault.tei-c.de which enables CORS for all > domains. > > Raff > > On Wed, Jul 24, 2019 at 1:28 PM Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > >> Hi Luis, >> >> Looping in the council list again. >> >> Why does it sound like a bad idea? What are your concerns and how could >> we address them while allowing full access to static data? >> >> One way could be making sure the header is only added to the /Vault >> location in Apache or Nginx. >> >> Raff >> >> >> On Wed, Jul 24, 2019, 1:06 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >> >>> Hi Raff, >>> >>> Enabling CORS for all sites does sound like a bad idea. >>> I can set a rule to allow it for some sites, but now all of them. >>> >>> Is this something that we can try to do? >>> >>> Best, >>> ----- >>> -Luis >>> >>> On Jul 24, 2019, at 7:10 AM, Raffaele Viglianti < >>> raffaeleviglianti(a)gmail.com> wrote: >>> >>> Hi Luis, >>> >>> We had CORS allowed from all domains before and the Council saw that as >>> a good idea. We should make it as simple as possible to obtain static files >>> from the Vault. I don't believe this will expose the server to any new >>> forms of attacks because this would simply allow GET requests of static >>> files from a browser JavaScript source. Since any other system can already >>> send unlimited requests of this type, limiting JavaScript does not make the >>> server more secure. In other words, the JavaScript won't be interacting >>> with an API, but simply GETting static files, so there shouldn't be any >>> risk involved in turning CORS on. >>> >>> Thanks, >>> Raff >>> >>> On Tue, Jul 23, 2019 at 6:45 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >>> >>>> Hi Raff, >>>> >>>> Would it be sufficient to allow requests from a smaller set of domains? >>>> >>>> For example: roma2.tei-c.org where the Roma tool lives? >>>> >>>> Making the other change can introduce some new attack vectors for the >>>> site. >>>> >>>> Best, >>>> ----- >>>> -Luis >>>> >>>> On Jul 22, 2019, at 6:28 AM, Raffaele Viglianti < >>>> raffaeleviglianti(a)gmail.com> wrote: >>>> >>>> Hi Luis, >>>> >>>> Thanks for the quick reply! The idea is that the server that serves the >>>> data from tei-c.org/Vault needs to add the Access-Control-Allow-Origin >>>> to the response so that browsers know they're allowed to grab data from >>>> different domains. If the server is Apache, it should enough to add the >>>> line below to <VirtualHost> or <Location> (depending on the set up) >>>> >>>> Header set Access-Control-Allow-Origin "*" >>>> >>>> If the server is nginx, you should add this under the right location >>>> stanza; >>>> >>>> add_header 'Access-Control-Allow-Origin' '*'; >>>> >>>> Let me know if I can help further, and thanks! >>>> Raff >>>> >>>> >>>> On Sun, Jul 21, 2019 at 10:12 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >>>> >>>>> Hi Raff, >>>>> >>>>> Sorry to hear about that you have an issue. >>>>> Can you give me more details on it? >>>>> >>>>> I am just not too sure about what I need to do to fix it. >>>>> >>>>> Best, >>>>> -Luis >>>>> >>>>> >>>>> On Jul 21, 2019, at 1:02 PM, Raffaele Viglianti < >>>>> raffaeleviglianti(a)gmail.com> wrote: >>>>> >>>>> Dear Luis, >>>>> >>>>> Sorry to add even more to your plate, but could you enable CORS on the >>>>> TEI Vault? The new version of Roma written in JavaScript needs it to access >>>>> ODD customizations and p5subet. Example: fetch >>>>> https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json >>>>> The response needs to contain the header >>>>> Access-Control-Allow-Origin: * >>>>> >>>>> Thanks! >>>>> Raff >>>>> >>>>> >>>>> >>>> >>> >

1 0

Re: [Tei-council] Enable CORS on the TEI Vault
by Raffaele Viglianti 27 Jul '19

27 Jul '19

Hi Luis, Looping in the council list again. Why does it sound like a bad idea? What are your concerns and how could we address them while allowing full access to static data? One way could be making sure the header is only added to the /Vault location in Apache or Nginx. Raff On Wed, Jul 24, 2019, 1:06 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > Hi Raff, > > Enabling CORS for all sites does sound like a bad idea. > I can set a rule to allow it for some sites, but now all of them. > > Is this something that we can try to do? > > Best, > ----- > -Luis > > On Jul 24, 2019, at 7:10 AM, Raffaele Viglianti < > raffaeleviglianti(a)gmail.com> wrote: > > Hi Luis, > > We had CORS allowed from all domains before and the Council saw that as a > good idea. We should make it as simple as possible to obtain static files > from the Vault. I don't believe this will expose the server to any new > forms of attacks because this would simply allow GET requests of static > files from a browser JavaScript source. Since any other system can already > send unlimited requests of this type, limiting JavaScript does not make the > server more secure. In other words, the JavaScript won't be interacting > with an API, but simply GETting static files, so there shouldn't be any > risk involved in turning CORS on. > > Thanks, > Raff > > On Tue, Jul 23, 2019 at 6:45 PM Luis Meneses <ldmm(a)uvic.ca> wrote: > >> Hi Raff, >> >> Would it be sufficient to allow requests from a smaller set of domains? >> For example: roma2.tei-c.org where the Roma tool lives? >> >> Making the other change can introduce some new attack vectors for the >> site. >> >> Best, >> ----- >> -Luis >> >> On Jul 22, 2019, at 6:28 AM, Raffaele Viglianti < >> raffaeleviglianti(a)gmail.com> wrote: >> >> Hi Luis, >> >> Thanks for the quick reply! The idea is that the server that serves the >> data from tei-c.org/Vault needs to add the Access-Control-Allow-Origin >> to the response so that browsers know they're allowed to grab data from >> different domains. If the server is Apache, it should enough to add the >> line below to <VirtualHost> or <Location> (depending on the set up) >> >> Header set Access-Control-Allow-Origin "*" >> >> If the server is nginx, you should add this under the right location >> stanza; >> >> add_header 'Access-Control-Allow-Origin' '*'; >> >> Let me know if I can help further, and thanks! >> Raff >> >> >> On Sun, Jul 21, 2019 at 10:12 PM Luis Meneses <ldmm(a)uvic.ca> wrote: >> >>> Hi Raff, >>> >>> Sorry to hear about that you have an issue. >>> Can you give me more details on it? >>> >>> I am just not too sure about what I need to do to fix it. >>> >>> Best, >>> -Luis >>> >>> >>> On Jul 21, 2019, at 1:02 PM, Raffaele Viglianti < >>> raffaeleviglianti(a)gmail.com> wrote: >>> >>> Dear Luis, >>> >>> Sorry to add even more to your plate, but could you enable CORS on the >>> TEI Vault? The new version of Roma written in JavaScript needs it to access >>> ODD customizations and p5subet. Example: fetch >>> https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json >>> The response needs to contain the header >>> Access-Control-Allow-Origin: * >>> >>> Thanks! >>> Raff >>> >>> >>> >> >

2 2

Next IG meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Jul '19

25 Jul '19

Dear all, I think it's time to plan the next Infrastructure Group meeting. I am aware that this will not be easy during the summer, but I'll give it a try. In this meeting we should focus on the move to HumaNum - which Luis is planning for the summer - and the requirements of the Technical Council for the new environment to facilitate future release processes. I send this to the Council list as well, in case Council members want to add to the discussion. Please fill in the doodle: https://doodle.com/poll/rxxdrnkkmd9ywdbg Best, Martina

1 0

July ticket triage
by Elisa Beshero-Bondar 23 Jul '19

23 Jul '19

Dear Council, I've just done the July ticket triage round and some of you will have a new ticket in your pile. Feel free to reassign, but we've now at least given all the tickets a home. Cheers, Elisa -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu <ebb8(a)pitt.edu> Development site: http://newtfire.org

1 0

Next Stylesheets meeting
by Peter Stadler 22 Jul '19

22 Jul '19

Hi all, my apologies, but I’m on vacation next week thus unavailable for the Stylesheets meeting on Monday. Best Peter

7 8

Enable CORS on the TEI Vault
by Raffaele Viglianti 21 Jul '19

21 Jul '19

Dear Luis, Sorry to add even more to your plate, but could you enable CORS on the TEI Vault? The new version of Roma written in JavaScript needs it to access ODD customizations and p5subet. Example: fetch https://tei-c.org/Vault/P5/current/xml/tei/odd/p5subset.json The response needs to contain the header Access-Control-Allow-Origin: * Thanks! Raff

1 0