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

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

04 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] Issue 1908
by James Cummings 20 Aug '19

20 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 20 Aug '19

20 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 17 Aug '19

17 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 16 Aug '19

16 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) 14 Aug '19

14 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) 07 Aug '19

07 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