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

Release branches
by Hugh Cayless 17 Aug '20

17 Aug '20

Dear All, I've created release branches "release-4.1.0" for the Guidelines, and "release-7.50.0" for the Stylesheets. All the best, Hugh

3 3

Annotations and impasses
by Hugh Cayless 17 Aug '20

17 Aug '20

Hi All, Since we essentially have today to make the go/no-go decision for getting Annotations into this release. We seem to be deadlocked in a couple of ways, and I would like to see if we can un-jam things. Syd and I are arguing over whether annotations should look like: <annotation xml:id="anno9" target="http://example.org/image1 http://example.org/image2"> <respStmt xml:id="HAC"> <resp>creator</resp> <persName>Hugh Cayless</persName> </respStmt> <ptr target="http://example.org/description1"/> <note>tag1</note> </annotation> or <annotation xml:id="anno9" target="http://example.org/image1 http://example.org/image2"> <annMeta> <respStmt xml:id="SB"> <resp>creator</resp> <persName>Syd Bauman</persName> </respStmt> </annMeta> <annBody> <ptr target="http://example.org/description1"/> <note>tag1</note> </annBody> </annotation> Syd's argument (and you should correct me if I'm misrepresenting your opinion, Syd) is that it's cleaner to partition things this way and we might want in the future to say virtually any TEI element could be an annotation body. My counter to this is that we set out here to implement the Web Annotation Data Model (or parts of it at least) in TEI, and that WADM doesn't have extra containers for annotation metadata or bodies. Further, WADM doesn't do specialized body types. They have text and they have URIs. I'm certainly in favor of adding useful features to TEI annotations, but if we want to do that in the next round of work on annotations, we'll have to do it by adding new TEI functionality (probably via new elements), and I don't think partitioning the content of annotation will buy us anything. It might make it worse, because the extra-sparkly new TEI functionality won't be compatible with WADM:body and therefore probably shouldn't go in an <annBody> element. To compound this, Laurent seems to say that WADM was only ever meant to be an inspiration and actual interoperability with Web Annotation wasn't a goal they had in mind in requesting this feature. I'm just going to go cry for a bit...excuse me. Ok. I will sum up: I would really like to have WADM compatibility this year because I have things I want to do with it. My proposal is that we proceed with WADM-compatible annotations and then begin work on more powerful TEI annotations. I would like to keep the content model of <annotation> as simple and as close to WADM as possible, but I won't pout if I'm voted down on that. What do you all think? Hugh

7 12

Freeze
by Scholger, Martina (martina.scholger＠uni-graz.at) 16 Aug '20

16 Aug '20

Dear all, I would like to remind you that we had agreed to freeze starting tonight. Please keep that in mind and check with the release technicians in case of late changes. Best, Martina Von meinem Huawei-Mobiltelefon gesendet

2 1

Stylesheets 454 and thus TEI 1848
by Syd Bauman 16 Aug '20

16 Aug '20

I have put multiple days of debugging work into Stylesheets 454, the release-blocking error that means a <classRef>, or at least a <classRef> with an @except, is ignored when processing an ODD. While I have made serious progress (some of which is in the sydb-454 branch), it is looking like I will not have a viable solution by the end of the day. Thus I think we need an alternate solution, which would be to back out [1] and either leave title page stuff out of <lem> and <rdg> for this release, or use some other ODD mechanism to put them in there. Possibilities (listed in my order of preference) include: 1. Use a bunch of <elementRef>s 2. Use <classRef> w/o @except, and add a <constraint> to flag <binaryObject>, <graphic>, and <castList> as invalid 3. Make a new class "model.frontPart.apparatusable" and put the needed elements in it. 4. Use <classRef> w/ @include (but I am highly suspicious that this will fail in exactly the same way). We can change any of the above back to <classRef> w/ @except after 454 is fixed. The other possibility, of course, is that someone else will take a look at this and fix the bug in the next few hours. If anyone wants to join my for a screen-sharing debugging session, speak up. That said, I really have other things I need to do today, too. :-| Notes ----- [1] TEI repo commit 193e6283321aeeb68b9a93b0d95b10a82148ef74

1 0

OxGarage release
by Peter Stadler 13 Aug '20

13 Aug '20

Hi all, the last release of OxGarage was done in June 2019 and since then not much development has happened, yet there are some minor changes that IMHO qualify for a new release. Most of all, the current master branch won’t build anymore on Travis nor on DockerHub – which is already fixed in dev. While at it, I already created a new main branch to eventually replace master starting with this release. (As a side note, Hugh was right about GitHub providing tools for doing this change later this year, see https://github.com/github/renaming#later-this-year. So I won’t touch other repos …) So, my proposal is to release OxGarage v3.1.0 next week and take care of the branch name switch with this release. If I hear no objections, I will take this as silent consent and do so :) Best Peter

1 1

REGENERATING, NOT!
by Syd Bauman 11 Aug '20

11 Aug '20

Re: Stylesheets meeting further info BTW, passing REGENERATING=1 to the Stylesheets/Test/Makefile tells the Makefile to not bother doing all those `diff` commands, but it does NOT actually regenerate the expected_results/. I.e., it just generates the output files (like test15.odd.rnc), but does not move them into expected_results/. One would have to do that by hand. (I think this was a purposeful change by Martin or someone just to avoid clobbering all the expected_results/.) Moreover, back on 2020-03-18 Martin commented out the diffs of test21.rnc, test30.rnc, and test30.dtd. I think we should probably put those back, yes, Martin?

3 2

Slightly Updated: Steps for updating p5subset.xml in Stylesheets repo
by Martin Holmes 11 Aug '20

11 Aug '20

This is an outline of the process we designed for updating the local copy of p5subset.xml in the Stylesheets. The rationale for this process is that changes to P5 inevitably require changes to the Stylesheets, but it makes more sense to deal with those required changes in batches, periodically, rather than making every change to P5 trigger frantic work on the Stylesheets (which the P5 ticket implementer may not be able to undertake at the time). The Stylesheets Group should probably undertake this work, and it must happen in a timely manner before any release. This is how it goes: 1. Retrieve a fresh copy of p5subset.xml, built using the current dev branch of P5. 2. In the Stylesheets, switch to the dev branch and git pull. Switch to the subsetSetup branch, which is intended for this work, and git pull. 3. Merge any changes from the Stylesheets dev branch into the subsetSetup branch. 4. Replace the source/p5subset.xml in the subsetSetup branch with the fresh one. 5. Run the Stylesheets tests (Test and Test2) in the subsetSetup branch. 6. Fix any problems. At this point, if there are problems too difficult to fix in the time you have available, abandon the process and put in a ticket for the Stylesheets repo. If the error is serious, make it a release-blocking bug. 7. Commit changes to subsetSetup branch. git push. 8. Switch back to the dev branch, git pull, and merge changes from the subsetSetup branch. git push. 9. Watch Mr Jenkins to make sure all is well. -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

2 2

Fwd: Steps for updating p5subset.xml in Stylesheets repo
by Martin Holmes 11 Aug '20

11 Aug '20

-------- Forwarded Message -------- Subject: Steps for updating p5subset.xml in Stylesheets repo Date: Fri, 7 Aug 2020 08:41:32 -0700 From: Martin Holmes <mholmes(a)uvic.ca> To: Syd Bauman <s.bauman(a)neu.edu> CC: Martin Holmes <mholmes(a)uvic.ca> This is an outline of the process we designed for updating the local copy of p5subset.xml in the Stylesheets. The rationale for this process is that changes to P5 inevitably require changes to the Stylesheets, but it makes more sense to deal with those required changes in batches, periodically, rather than making every change to P5 trigger frantic work on the Stylesheets (which the P5 ticket implementer may not be able to undertake at the time). The Stylesheets Group should probably undertake this work, and it must happen in a timely manner before any release. This is how it goes: 1. Retrieve a fresh copy of p5subset.xml, built using the current dev branch of P5. 2. In the Stylesheets, switch to the dev branch and git pull. Switch to the subsetSetup branch, which is intended for this work, and git pull. 3. Merge any changes from the Stylesheets dev branch into the subsetSetup branch. 4. Replace the p5subset.xml in the subsetSetup branch with the fresh one. 5. Run the Stylesheets tests (Test and Test2) in the subsetSetup branch. 6. Fix any problems. 7. Commit changes to subsetSetup branch. git push. 8. Switch back to the dev branch, git pull, and merge changes. git push. 9. Watch Mr Jenkins to make sure all is well. -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

Stylesheets meeting Tue 11 Aug
by Syd Bauman 11 Aug '20

11 Aug '20

Time to get our heads spinning 'round circularity! We are planning a Stylesheets group meeting for this Tue 11 Aug at 13:00Z.[1] This is an important meeting, because we are going to step through the process of updating the p5subset.xml that the various build processes are using; i.e., we are implementing (for the first time) our planned "fix" for the circularity problem. (Not really so much a fix as a work-around, IMHO.) I expect we will be using Google Hangouts unless someone says otherwise. Notes ----- [1] 13:00 UTC is: 06:00 PDT 09:00 EDT 14:00 BST 15:00 CEST

3 2

Guidelines JQuery
by Hugh Cayless 06 Aug '20

06 Aug '20

Hi All, I've upgraded the Guidelines' copy of JQuery to 3.5.1 (the latest) and fixed a bug that followed on from that. Does anyone remember why we haven't nuked P5/Utilities-1 (which I believe was where old XSLT 1.0 Guidelines generation code got put, like over a decade ago). Can I get rid of it? Please? This is the sort of thing I was calling "cruft" in the meeting this morning :-). Hugh

4 5