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

Next meeting: July 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Jul '22

06 Jul '22

Dear all, This is the agenda (tbc) for our next meeting on Friday, July 8 at 7am PDT / 10am EDT / 4pm CEST: https://docs.google.com/document/d/1-c5WIAlm8mzTpbiophrgqdzK8SCkWj6JaSJJvl4… I'm on the train at the time of our meeting and cannot guarantee that I will have a stable internet connection. Besides, I have to change trains after an hour. Could someone please take over as moderator if I get cut off? Best, Martina Dr. Martina Scholger Centre for Information Modeling Austrian Centre for Digital Humanities University of Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

1 0

Next Stylesheets meeting: July 1st
by BERMUDEZ SABEL Helena 01 Jul '22

01 Jul '22

Dear all, The next Stylesheets meeting will take place on July 1st at 16.00Z (8.00 PDT, 11.00 EDT, 17.00 CEST). I would like to focus again on cleaning the PRs. I still need to select which ones can be tackled during the meeting (but I will do so before Friday). Nevertheless, if you have tickets that you would like us to discuss, do not hesitate to add them to the agenda<https://docs.google.com/document/d/1LHIhvuNTISCrlMZDZx7jkVbDt8teivQTbJrF0EV…>! Best, Helena [Université de Neuchâtel]<https://www.unine.ch/> Helena Bermúdez Sabel Post-doctorante FNS Institute des sciences du langage Université de Neuchâtel Rue Pierre-à-Mazel 7 CH-2000 Neuchâtel Tél. +41 32 718 16 21 www.unine.ch/isla<http://www.unine.ch/isla>

6 7

Current P5 build break
by Martin Holmes 19 Jun '22

19 Jun '22

HI all, I think the current P5 build break is caused by a Stylesheets bug, and I've raised a ticket here: <https://github.com/TEIC/Stylesheets/issues/556> Might be a good issue for the Stylesheets group to tackle. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

Council call started
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Jun '22

10 Jun '22

This is the agenda https://docs.google.com/document/d/1cwoNEraVDt2SyQ3-k2JngPKh8m3zIOccQuQD_-X…<https://docs.google.com/document/d/1cwoNEraVDt2SyQ3-k2JngPKh8m3zIOccQuQD_-X…> Mag. Dr.phil. Martina Scholger Zentrum für Informationsmodellierung - Austrian Centre for Digital Humanities Elisabethstraße 59/III 8010 Graz Austria martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at> https://informationsmodellierung.uni-graz.at<https://informationsmodellierung.uni-graz.at/> | https://gams.uni.graz.at<https://gams.uni.graz.at/> Institut für Dokumentologie und Editorik e.V. | https://i-d-e.de<https://i-d-e.de/> Chair of the TEI Technical Council | http://tei-c.org

1 0

Next meeting: Fri, June 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '22

08 Jun '22

Dear all, This is the agenda for our next Council meeting on Friday, June 10 https://docs.google.com/document/d/1cwoNEraVDt2SyQ3-k2JngPKh8m3zIOccQuQD_-X… at 7am PDT / 10am EDT / 4pm CEST Please add more topics that you would like to discuss. Best, Martina

1 0

change date next Stylesheets meeting?
by BERMUDEZ SABEL Helena 08 Jun '22

08 Jun '22

Dear all, The next Stylesheets meeting is scheduled for June 24th at 16:00Z (17:00 CEST, 8:00 PDT, 11:00 EDT). However, I will be traveling, so I was wondering if it would be possible to move the meeting one week and meet on July 1st instead (same time). If the change is inconvenient, I will send a doodle with more possibilities. All the best, H. [Université de Neuchâtel]<https://www.unine.ch/> Helena Bermúdez Sabel Post-doctorante FNS Institute des sciences du langage Université de Neuchâtel Rue Pierre-à-Mazel 7 CH-2000 Neuchâtel Tél. +41 32 718 16 21 www.unine.ch/isla<https://www.unine.ch/>

8 8

Stylesheets meeting in two hours
by BERMUDEZ SABEL Helena 27 May '22

27 May '22

Dear all, Reminder of the meeting will have today at 16.00Z (8.00 PDT, 11.00 EDT, 17.00 CEST). https://docs.google.com/document/d/1LHIhvuNTISCrlMZDZx7jkVbDt8teivQTbJrF0EV… See you in a bit! H. [Université de Neuchâtel]<https://www.unine.ch/> Helena Bermúdez Sabel Post-doctorante FNS Institute des sciences du langage Université de Neuchâtel Rue Pierre-à-Mazel 7 CH-2000 Neuchâtel Tél. +41 32 718 16 21 www.unine.ch/isla<https://www.unine.ch/>

1 0

Next Stylesheets meeting: May 27
by BERMUDEZ SABEL Helena 25 May '22

25 May '22

Dear all, The next Stylesheets meeting will take place on May 27th at 16.00Z (8.00 PDT, 11.00 EDT, 17.00 CEST). The proposed agenda<https://docs.google.com/document/d/1LHIhvuNTISCrlMZDZx7jkVbDt8teivQTbJrF0EV…> is focused on cleaning up the PRs currently open, but if you have tickets that you would like us to discuss, do not hesitate to add them to the agenda! Best, Helena [Université de Neuchâtel]<https://www.unine.ch/> Helena Bermúdez Sabel Post-doctorante FNS Institute des sciences du langage Université de Neuchâtel Rue Pierre-à-Mazel 7 CH-2000 Neuchâtel Tél. +41 32 718 16 21 www.unine.ch/isla<https://www.unine.ch/>

3 2

gitHelp, again
by Bauman, Syd 14 May '22

14 May '22

I checked out dev branch of the TEI repo, then created a new branch: | $ git status -uno | On branch dev | Your branch is up to date with 'origin/dev'. | | nothing to commit (use -u to show untracked files) | $ git checkout -b sydb_2279 | Switched to a new branch 'sydb_2279' Then I made a bunch of changes, making a few commits. Then I went to push my new branch up so y'all could play with it: | $ git status -uno | On branch sydb_2279 | nothing to commit (use -u to show untracked files) | $ git push -u | Branch 'dev' set up to track remote branch 'dev' from 'origin'. | Branch 'gender' set up to track remote branch 'gender' from 'origin'. | Everything up-to-date Huh? And the sydb_2279 branch is *not* pushed up to gitHub. What gives?

2 2

Next Council meeting: May 13
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 May '22

11 May '22

Dear all, This is the agenda for the next Council meeting on Fri May 13 at 7am PDT / 10am EDT / 4pm CEST https://docs.google.com/document/d/1oKYxbGKVXE8u8mRQ5CvSmBA_-gDhBNnkM8XEBAw… Best, Martina

1 0

xenoData users?
by Lou Burnard 11 May '22

11 May '22

a few weeks ago i posted a query about usage of xenoData on tei-l and followed it up with a repeat on twitter. i was a bit surprised to receive absolutely zero response (full disclosure : i did get a reply from m.mueller but not to the question i asked) . so either no one is using this lovely tag or no one wants to admit to it. either of which seems somewhat of a problem. maybe, i thought, maybe the mandarins of the tei council know better? are any of you using it for real in a project?do you know any project which is?

5 5

Next stylesheets meeting: April 22
by BERMUDEZ SABEL Helena 22 Apr '22

22 Apr '22

Dear all, The next Stylesheets meeting will take place on April 22th at 16.00Z (8.00 PDT, 11.00 EDT, 17.00 CEST). As discussed in the VF2F meeting, we will dedicate a Stylesheets meeting to address the oXygen plugin and its maintenance, and Martin Holmes kindly accepted to walk us though the basics. This introduction will be the main point of the agenda<https://docs.google.com/document/d/1LHIhvuNTISCrlMZDZx7jkVbDt8teivQTbJrF0EV…>. See you all on Friday and good luck to the release techs today! Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel

4 4

Deprecation for ident changes?
by Martin Holmes 21 Apr '22

21 Apr '22

Hi all, OUr LEMDO project got bitten by an unexpected change in the latest TEI release: we have a customization which deletes the Schematron rule which disallows nested ab elements, because we believe they should be nestable. However, the @ident of that rule was changed in the release, so suddenly our customization failed and a pile of files were suddenly invalid. No problem to figure out and fix, but it does show that changing an @ident should be subject to deprecation warnings if we aim not to catch people out with a release. I don't know how that could be done, though. We noticed a bunch of other unexpected changes too, and I was a bit surprised because I subscribe to the bleeding-edge Oxygen plugin so that I get plenty of warning of changes landing in the dev branches. However, I think what has been happening is that a lot of changes have been taking place in feature branches, and then languishing there until the last-minute mad scramble to land them in dev and release branches before the release date. That means that the value of the bleeding-edge plugin as an advance testing mechanism is diminished. Again, not sure what could be done about that. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day.

3 4

altIdent screw up
by Bauman, Syd 21 Apr '22

21 Apr '22

Oh BLEEP! I failed to change the manual deprecation date from "2022-07-14" to "2022-10-21" on the "deprecate_altIdent_in_non-ODD_places" constraint specification (in file P5/Source/Specs/altIdent.xml). Now that we have published 4.4.0 with the “wrong” date I see 3 possible courses of action: 1. Leave things as is, and just act on the deprecation on 2022-07-14. Yes, that makes the deprecation period pretty short, but who uses `<altIdent>` anyway? 2. Do nothing in July. For the _next_ release (call it 4.5.0, as that is likely what it will be) reset the valid until date from 2022-07-14 to a date a few months after the 4.5.0 release. 3. Issue a point release (4.4.1) now that corrects the date to the desired 2022-10-21.

3 3

Freeze lifted
by Raffaele Viglianti 20 Apr '22

20 Apr '22

Dear Council, The release process is completed, feel free to start pushing to dev again! Raff

2 1

Entering Freeze period for v 4.4.0
by Raffaele Viglianti 17 Apr '22

17 Apr '22

Dear, All, I have now created the release branch for version 4.4.0 of the Guidelines (https://github.com/TEIC/TEI/tree/release-4.4.0) and for version 7.53.0 of the Stylesheets ( https://github.com/TEIC/Stylesheets/tree/release-7.53.0) Please refrain from committing anything to dev until the release is completed. If you wish to make changes to the release branches, please notify the release technicians before pushing any change. The technicians are: Janelle Jenstad, Hugh Cayless, Raff Viglianti. Could the Jenkins maintainers add these branches to be built? Thanks everyone! Raff

1 0

release notes
by Scholger, Martina (martina.scholger＠uni-graz.at) 15 Apr '22

15 Apr '22

Dear all, I made a first draft of the release notes: https://github.com/TEIC/TEI/commit/6f9fd2aef3a1c6403843d1293499960e5d3e8be7 To be continued tomorrow. Best, Martina

1 0

how many namespaces?
by Bauman, Syd 12 Apr '22

12 Apr '22

I added a new routine to TEI/P5/Utilities/ called namespaces.xslt that generates a table that gives you counts of namespace nodes. See https://bauman.zapto.org/~syd/temp/4TEICouncil/namespaces_in_P5.xhtml.

1 2

Call in 25 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Apr '22

08 Apr '22

Here is the agenda: https://docs.google.com/document/d/1raASYeayA9dzeEWcvi1Zk17UGQAoqgnc-W8nbw4… Best, Martina

1 0

Next meeting: April 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Apr '22

06 Apr '22

Dear all, Our next meeting is on Friday, April 8 at 7am PDT / 10am EDT / 4pm CEST. Please add open issue/PR's to the agenda that we need to discuss for the release: https://docs.google.com/document/d/1raASYeayA9dzeEWcvi1Zk17UGQAoqgnc-W8nbw4… I'll add to the agenda tomorrow. Best, Martina

1 0

faster testing
by Bauman, Syd 06 Apr '22

06 Apr '22

One of the reasons the test procedure in Stylesheets/Test2/ is dramatically faster than the one in Stylesheets/Test/ is that it is, by default, run in parallel.[1,2] You can also ask the make command to run multiple jobs at once. The switches that control this are --jobs= and --output-sync=. I just tried an experiment, comparing how long it took to run make vs make --jobs=7 --output-sync=lines. (I chose 7 because my system has 8 threads, and I wanted to have some CPU available. What little I have found on the web seems to suggest I may as well go ahead and use 8.) The result was faster, although not even close to 7 times faster: down to 03:32 from 04:36. I compared the output of the 2 commands, and they were identical. On GNU/Linux, at least, the nproc command will tell you how many threads are available. Thus using the command $ make --jobs=`nproc 2>/dev/null || echo 1` -Oline seems to make sense to me. (-O is shorthand for --output-sync=.) It is also possible to get the Makefile to do that on its own. My first thought is that might not be such a good idea, because you may want to run with --jobs=1 in order to force error messages into the right order. (I.e., in case -Oline wasn’t good enough.) I ran the experiment again, this time using --jobs=8 and getting screen captures of the process monitor roughly 40 s after the make command started.[3] The timing results were very similar (down to 03:36 from 04:36), but the order of output lines was different. (Same output; i.e., they were identical after sorting and removing timestamps.) So I think anyone running the Stylesheets test process would do well to use the --jobs switch. You could use any of * -j 8 # if you know you have 8 threads, e.g. * --jobs=`nproc` # if you know the nproc command works on your system * -j `nproc 2> /dev/null || echo 1` # if there is a chance nproc fails, so it defaults to '1' Martina — could you either update the notes we have about updating P5 subset, or remind me where they are and I will? Thanks. Notes [1] ant test runs them in parallel; if you want them in series (likely because the order of messages was confusing when run in parallel) use ant testSeries. [2] There are other reasons, like it is written to be less redundant, and the JVM is only spun up once, rather than once for every test. [3] For evidence as to why --jobs makes make faster, see https://bauman.zapto.org/~syd/temp/4TEICouncil/Screenshot_of_make_process_m… and https://bauman.zapto.org/~syd/temp/4TEICouncil/Screenshot_of_make_-j_proces…

2 1

TEI PR #2204
by Bauman, Syd 03 Apr '22

03 Apr '22

Re: “Confirm with SB that https://github.com/TEIC/TEI/pull/2204 is ready to merge.” — agenda from yesterday’s meeting I think I have addressed Magdalena’s (reasonable) question on the PR<https://github.com/TEIC/TEI/pull/2204#pullrequestreview-929550387>. Thus, unless she or someone else disagrees, yes, PR #2204 is, IMHO, ready to merge. And I have just merged dev branch into the issue branch (sydb_issue-2185_URI_spaces).

1 0

Oxygen plugin
by Martin Holmes 01 Apr '22

01 Apr '22

Hi all, I'd like to draw Council's attention to these two tickets: <https://github.com/TEIC/oxygen-tei/issues/54> <https://github.com/TEIC/TEI/issues/2251> where two things have happened: 1. As usual, we were caught unawares when Oxygen released an update which broke functionality in the TEI Oxygen plugin version that we maintain. Oxygen maintain their own fork of the plugin repo and up to now, they've been making any necessary changes silently before an Oxygen release; then we realize that something is broken and struggle to catch up. I now have a pull request that I've asked Radu Coravu from Oxygen to review before I merge it, updating the included libs for transformations to take account of log4j changes. For those new to the situation, it's a bit complicated: the Oxygen folks only care about ensuring that the version of the plugin that ships with Oxygen works with the Oxygen version it ships with. However, we have different requirements, because we attempt to maintain support for older versions of Oxygen, so that those who cannot upgrade for some reason are still able to get up-to-date versions of P5, the Stylesheets, and the transformations in their older Oxygen. This means that we can't simply adopt any of the changes that the Oxygen folks make directly into our own branch; that would remove functionality for earlier Oxygen versions. So we have to try to merge the changes carefully. When the pull request is checked and merged, then our bleeding-edge version of the plugin will build, and those of us using it (which I hope is a reasonable subset of the Council) are able to test and make sure nothing is badly broken. We don't have a formal testing procedure, though, especially for older versions of Oxygen, because few of us run older versions. If the bleeding edge version is deemed OK, then Council will need to release the corresponding stable version using the procedure that's normally followed when we do a P5/Stylesheets release. There is a degree of urgency here because currently, anyone who is subscribed to our plugin and has upgraded their Oxygen to the current version will not be able to use any of the transformations, as Laurent discovered. 2. Radu has kindly agreed to raise issues on our plugin repo when they make changes in future, so we can try to avoid this happening again. I think I'm the only one who watches this repo at the moment, which is not really ideal. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day.

1 0

VF2F meeting this weekend
by Scholger, Martina (martina.scholger＠uni-graz.at) 31 Mar '22

31 Mar '22

Dear Council, This is the agenda for our virtual F2F meeting on Friday and Saturday (April 1 and 2): https://docs.google.com/document/d/1WhGAcLK0H_xNNPoEECBk9f0eEn-qhSiWfqnhaik… Please feel free to add more topics to the agenda. Meeting times: Friday, Apr 1: North American break-outs The North American group needs to decide whether to start at 12 PDT / 15 EDT or at 13 PDT / 16 EDT (see poll on slack). Saturday, Apr 2: European break-outs 10:00-13:00 CEST Full Council 06:00-10:00 PDT 09:00-13:00 EDT 15:00-19:00 CEST I'll add the table with links to the Guidelines/Stylesheets issues tomorrow. Best, Martina Dr. Martina Scholger Centre for Information Modeling Austrian Centre for Digital Humanities University of Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

3 3

@docLang chaining issues
by Lou Burnard 31 Mar '22

31 Mar '22

And here are my opinions on these questions: >p5subset.xml has all the languages (as it does); customization1.odd specifies >@docLang="en" customization2.odd, which points to customization1.odd, specifies >@docLang="it" What language should the output schema use? Schemas compiled against customization1 will see help popups in English, and those compiled against customization2 will see them in Italian. That is, assuming neither ODD has done anything to remove the relevant components. The languages available from a compiled ODD should presumably be managed in the same way as anything else. So if I delete an English <gloss> in my customization, and then compile that to use as a basis for a further customization, the compiled version will no longer have an English gloss to use, so specifying @docLang='en' won't produce anything. In general specifying @docLang only expresses an output preference; it has nothing to do with determining what components are available from a compiled version of the ODD. 2. Imagine: >customization1.odd modifies an element, replacing the English gloss with >something different. customization2.off specifies @docLang="es" Where should the >gloss be taken from in the output of the chain? I think I already answered that. If "customisation2.off" is using a compiled version of customization1.odd then the spanish gloss will be taken from that, if it's there. >3. Should it be part of the system that you can specify a series of languages in >order of preference, from which text will be taken if something is not available >in the main docLang? Seems like an over-complication. There is a canonical language in which ODD glosses are written, which is currently labelled "en" (unless and until the TEI becomes a purely Chinese -- say -- project). So it is not unreasonable to say if @docLang requests a language that's not available (for whatever reason), a version using the canonical language is the fallback. If you really want to I suppose you could supply multiple values for @docLang to indicate acceptable languages, and then choose whichever comes first on the list, but this seems like over-egging the pudding to me.

1 0