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

VF2F this weekend
by Scholger, Martina (martina.scholger＠uni-graz.at) 27 Sep '21

27 Sep '21

Dear Council, This is the agenda for our virtual F2F meeting on Friday and Saturday (October 1 and 2): https://docs.google.com/document/d/18RIt71cxW8ywCI-Km5cDr7gOR3pIwupHxa7VWhd… Please feel free to add more topics to the agenda. Meeting times: Friday, Oct 1: North American break-outs 13:00-16:00 PST 16:00-19:00 EST Saturday, Oct 2: European break-outs 09:00-12:00 BST 10:00-13:00 CET Full Council 06:00-10:00 PST 09:00-13:00 EST 14:00-18:00 BST 15:00-19:00 CET I'll add the table with links to the Guidelines/Stylesheets issues in the next couple of days. Best, Martina

1 0

Stylesheets meeting this Thu 23 Sep
by Bauman, Syd 23 Sep '21

23 Sep '21

We are scheduled to hold a Stylesheets meeting on Thu 26 Aug 21 at 17:30Z for 1.5 hours. That is * 10:30–12:00 PDT (JJ, MH) * 13:30–15:00 EDT (SB, EBB, MB, HC, JL, RV) * 18:30–20:00 BST (HSB?, NC, MT?) * 19:30–21:00 CEST (MS, PS) Martina — let me know if you want me to send out a Zoom link, or, if you would prefer just to send it out yourself. Also, I presume we will be taking notes on our scratchpad<https://docs.google.com/document/d/1lbdA_oikjNJvNuMKVdgn41JHL-NpdrtLhh2qK6_…> but let us know if you have other plans. Proposed agenda: 1. Admonish everyone (except MH) for not testing the examples in TCW32 and putting your results in the GoogleDoc<https://docs.google.com/document/d/1nAi_6pB1ayTV3SYAsrf8InKL1T5n8DAdgdhf-o5…>. 2. Housekeeping (location of notes, certification of quorum, birthday announcements, etc. :-) 3. Remind everyone to test the examples in TCW32, using the GoogleDoc<https://docs.google.com/document/d/1nAi_6pB1ayTV3SYAsrf8InKL1T5n8DAdgdhf-o5…> as a guide. 4. Tickets. Possibilities include * <empty/> element not processed #263<https://github.com/TEIC/Stylesheets/issues/263>: LB→HC. Next step, I think, is to create a test suite. * .docx to TEI P5 XML Document conversion fails #405<https://github.com/TEIC/Stylesheets/issues/405>: fricke-steyer→PS. Do we bother? What about Tomaz’s extra problem posted 2020-10-13? * tei-to-markdown.xsl needs a template to handle images #511<https://github.com/TEIC/Stylesheets/issues/511>: MH→EBB. MH says it is simple. Seems it would be, but we have all heard that before. 😀 * <ptr> in <desc> gets dropped in rng #513<https://github.com/TEIC/Stylesheets/issues/513>: NC→NC. Probably one of those cases for which it is very hard to figure out what is going on, but easy to fix once you figure it out. Maybe. 5. Implore everyone to test the examples in TCW32, using MS’s GoogleDoc<https://docs.google.com/document/d/1nAi_6pB1ayTV3SYAsrf8InKL1T5n8DAdgdhf-o5…> as a guide.

8 8

Stylesheets meeting link
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Sep '21

23 Sep '21

Hi all, This is the link for the Stylesheet meeting: https://us02web.zoom.us/j/82509109944?pwd=aS9Va2ZVbUNEOTQ2ZXFXMXNkV3k2Zz09 Best, Martina

1 0

two sizable editing tasks
by Bauman, Syd 14 Sep '21

14 Sep '21

We (well, y’all) now have two sizable editing & testing tasks in the hopper that I would like to see handled as soon as reasonable. 1. TCW32<https://github.com/TEIC/Documentation/blob/master/TCW/tcw32.xml>, which I would like to see published (as TCUxx, I think) in October, if possible. Reviewers of this document (which should include you, James, as you are assigned to this ticket<https://github.com/TEIC/TEI/issues/1675>) should: * Read the prose, make any obvious changes necessary, check right back into master branch. * Read the prose, inform me or post any controversial suggested changes. Use a new branch and PR if you make extensive changes. * Try out the examples, make sure they do what they say they will do. Since there are 17 of them, and some are quite complex, and in most cases you will have to make a test file, it might be nicer to divvy them up among several people. See below. 2. Furthermore, there are (at least) 2 significant problems in the HTML output using teitohtml<https://github.com/TEIC/Stylesheets/blob/dev/bin/teitohtml> which we should probably fix before publishing: * The little anchor symbols are not floating over to the R side of the examples. (Only the first 2 little examples in the running prose have anchor symbols.) * Every <ref> to a figure in the back matter is being rendered with an extraneous preceding “, ” (i.e., COMMA SPACE) that has to go. 3. Issue 2173. Comment on the ticket<https://github.com/TEIC/TEI/issues/2173#issuecomment-917810897> discusses minimum that needs to be done. (I have not actually created a PR for two reasons: * need real messages, first * I had started by creating the ODD-with-tests, so went ahead with that route.) below Here is a list of the 17 snippets of ODD in TCW32 that need to be tested (as of the 1st checked-in version; I may have corrected some typos since then). If folks reading this could each grab one or two at random and test, that would be lovely. Or if y’all prefer we can ask Martina to just assign them to people. * #eg01: PureODD to limit attribute to one URI * #eg02: Ensure ref of g is a shorthand pointer * #eg03: Ensure ref of g is a shorthand pointer, PureODD * #eg04: Check that ref of g points to something * #eg05: Check that ref of g points to a char or a glyph * #eg06: Require the url of moduleRef to refer to a particular file * #eg07: Check that url of moduleRef refers to an RNG file in the same directory * #eg08: Ensure file is readable XML * #eg09: Ensure file is readable RELAX NG grammar * #eg10: Require persName to refer to a person in the local personography * #eg11: Ensure uri of equiv is present and refers to an item on a particular page * #eg12: Require a filter on equiv that points to an XSLT program * #eg13: rendtion points to 1 or 2 renditions * #eg14: Check that each pointer in wit points to witness * #eg15: Required ref of persName eventually refers to person * #eg16: Required ref of persName eventually refers to person using abstract patterns * #eg17: Resolve prefixDef for references to people

2 1

Stylesheets Test2 job on Jenkins
by Peter Stadler 13 Sep '21

13 Sep '21

Hi Martin and Council, at yesterday's Council meeting we decided to push your Test2 forward and run both test suites in parallel for some time to see whether they fail/succeed for the same issues. If this runs smooth, we might remove the original tests completely at some point. Syd was so kind to add a new „Test2“ target to the Makefile [1] and I set up a new job at the Paderborn Jenkins [2]. It simply runs `make clean test2` (so no artifacts are built). I had to update the `tei-log-parse-rules` and now everything seems to work nicely. Cheers Peter [1] https://github.com/TEIC/Stylesheets/commit/c8a8f6fbc0ff98c47041fc365a98f6d5… [2] https://jenkins.tei-c.org/job/Stylesheets-dev-Test2/

2 2

Call in 45 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Sep '21

09 Sep '21

Dear all, This is the agenda for our call, starting in 45 minutes https://docs.google.com/document/d/1fQ1MheXD-9lcUM5W1gjUdJxkZ5ghvJoJqDFAq-2… Best, Martina Holen Sie sich Outlook für Android<https://aka.ms/ghei36>

1 0

Next Council call, Sept 9
by Scholger, Martina (martina.scholger＠uni-graz.at) 07 Sep '21

07 Sep '21

Dear all, This is the agenda for our next Council call on Thursday, Sept 9 at 10:30am PDT / 1:30pm EDT / 6:30pm BST / 7:30pm CEST https://docs.google.com/document/d/1fQ1MheXD-9lcUM5W1gjUdJxkZ5ghvJoJqDFAq-2… Please add topics that you would like to discuss. Best, Martina

1 0

Release finished
by Scholger, Martina (martina.scholger＠uni-graz.at) 31 Aug '21

31 Aug '21

Dear Council, The release techs are very happy to report that the Guidelines 4.3.0 and Stylesheets 7.52.0 are released. Special thanks to Helena and Peter for doing a great job! You can now push to dev again. Best wishes, Helena, Peter, and Martina

1 0

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

31 Aug '21

Dear all, we are in the middle of the release. Please do not push changes to the release branch. Best, Martina

1 0

dot-dot-dot release
by Scholger, Martina (martina.scholger＠uni-graz.at) 30 Aug '21

30 Aug '21

Dear Council, We will start with the release process tomorrow morning (~9am CEST). Here are the release notes, I hope I didn't miss anything. The codename is "dot-dot-dot", but we are open for other suggestions. If you find a typo in the in the release notes, please push changes to the release branch. See https://jenkins.tei-c.org/job/TEIP5-release-4.3.0/lastSuccessfulBuild/artif… Best, Martina

1 0

Build of release branch
by Scholger, Martina (martina.scholger＠uni-graz.at) 30 Aug '21

30 Aug '21

Dear Jenkins Maintainers, The release branches (release-4.3.0 and release-7.52.0) have been created. May I ask you to add a Jenkins job? Thanks! Best, Martina

3 8

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

29 Aug '21

Dear Council, This is a reminder that the Freeze starts at the end of today. The release technicians will create the release branch tomorrow morning (~10am CEST). Best, Martina

1 0

Stylesheets meeting tomorrow, 2021-08-26
by Bauman, Syd 26 Aug '21

26 Aug '21

We are scheduled to hold a Stylesheets meeting tomorrow, Thu 26 Aug 21 at 17:30Z for 1.5 hours. That is * 10:30–12:00 PDT (JJ, MH) * 13:30–15:00 EDT (SB, EBB, MB, HC, JL, RV) * 18:30–20:00 BST (HSB?, NC, MT?) * 19:30–21:00 CEST (MS, PS) Martina — let me know if you want me to send out a Zoom link, or, if you would prefer just send it out yourself. Agenda: 1. Housekeeping (location of notes, certification of quorum, birthday announcements, etc. :-) 2. New p5subset → Stylesheets repo: I would like someone who has not done so before to share screen and be talked through the process 3. Tickets. Possibilities include * <empty/> element not processed #263<https://github.com/TEIC/Stylesheets/issues/263>: LB→HC. Next step, I think, is to create a test suite. * .docx to TEI P5 XML Document conversion fails #405<https://github.com/TEIC/Stylesheets/issues/405>: fricke-steyer→PS. Do we bother? What about Tomaz’s extra problem posted 2020-10-13? * tei-to-markdown.xsl needs a template to handle images #511<https://github.com/TEIC/Stylesheets/issues/511>: MH→EBB. MH says it is simple. Seems it would be, but we have all heard that before. 😀 * <ptr> in <desc> gets dropped in rng #513<https://github.com/TEIC/Stylesheets/issues/513>: NC→NC. Probably one of those cases for which it is very hard to figure out what is going on, but easy to fix once you figure it out. Maybe. 4. <https://github.com/TEIC/Stylesheets/issues/263>

4 4

TEI conference 2021: reviewer for submissions
by Scholger, Martina (martina.scholger＠uni-graz.at) 26 Aug '21

26 Aug '21

Dear Council, In the Board meeting on Thursday, the conference organizing committee asked whether some TEI Council members would be willing to review conference submissions for the TEI 2021 conference. The time frame for that is the first three weeks of September. Please let me know if you want to support the review process by volunteering for this. Best, Martina

3 3

release notes
by Scholger, Martina (martina.scholger＠uni-graz.at) 24 Aug '21

24 Aug '21

Dear all, Here is a draft of release notes: https://github.com/TEIC/TEI/commit/e4619ad3a6cae2b839c320cce017713a43867c65 Please have a look at them and feel free to modify. Best, Martina Holen Sie sich Outlook für Android<https://aka.ms/ghei36>

1 0

release blocking PR
by Bauman, Syd 22 Aug '21

22 Aug '21

Attn: Martina & Peter You are reviewers for a release blocking PR<https://github.com/TEIC/Stylesheets/pull/521>. In truth, anyone could review it, but I picked you two because it has to be merged (or some other fix has to be found) before release, and you are release techs. 🙂

2 2

Action failure notices
by Hugh Cayless 18 Aug '21

18 Aug '21

Hi all, You may get notifications about a failed action if you push to dev. Just ignore them. I’m trying to set up a mirroring operation to another repo as part of the work on translations, but it’s not working yet. Hugh

1 0

TEI repo labels
by Bauman, Syd 16 Aug '21

16 Aug '21

We need (at least) 2 more labels for the TEI repo: * a label for discussing labels or other github topics (maybe “meta” or “label”) * a label for queries like the newest issue<https://github.com/TEIC/TEI/issues/2170>. Yes, queries are (in some sense) supposed to be on TEI-L or in the GitHub discussion group thingies<https://github.com/TEIC/TEI/discussions>, but if users put them in as an issue, we should be able to tag it as such. (Or perhaps we should move it to a discussion place and close it?)

4 7

Meeting today
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Aug '21

12 Aug '21

Dear all, our meeting starts in 1 hour. https://docs.google.com/document/d/1MjfZaYPjtykz8sP8eMBu9dMAoSsSETSABmmNexG…<https://docs.google.com/document/d/1MjfZaYPjtykz8sP8eMBu9dMAoSsSETSABmmNexG…> Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Dienstag, 10. August 2021 23:24 An: tei-council(a)lists.tei-c.org Betreff: Next meeting: Thu, Aug 12 Dear all, This is the agenda for our next Council meeting on Thursday, August 12 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST: https://docs.google.com/document/d/1MjfZaYPjtykz8sP8eMBu9dMAoSsSETSABmmNexG…<https://docs.google.com/document/d/1MjfZaYPjtykz8sP8eMBu9dMAoSsSETSABmmNexG…> In this meeting we will focus on the upcoming release (next week). Please add issues and open pull requests that need to be discussed and/or approved. According to our schedule, the refrigeration period starts tomorrow. This means that we should not commit major changes to the schema (except work that has been done in a branch, tested and approved); minor changes (wording, typos, examples) are ok. However, as we have a meeting on Thursday where we will certainly discuss some of the open issues, I suggest that we start the refrigeration period after the meeting. Best, Martina

1 0

Next meeting: Thu, Aug 12
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Aug '21

10 Aug '21

Dear all, This is the agenda for our next Council meeting on Thursday, August 12 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST: https://docs.google.com/document/d/1MjfZaYPjtykz8sP8eMBu9dMAoSsSETSABmmNexG… In this meeting we will focus on the upcoming release (next week). Please add issues and open pull requests that need to be discussed and/or approved. According to our schedule, the refrigeration period starts tomorrow. This means that we should not commit major changes to the schema (except work that has been done in a branch, tested and approved); minor changes (wording, typos, examples) are ok. However, as we have a meeting on Thursday where we will certainly discuss some of the open issues, I suggest that we start the refrigeration period after the meeting. Best, Martina

1 0

Work on OxGarage
by Peter Stadler 26 Jul '21

26 Jul '21

Dear all, during some of our last meetings I mentioned that we (at Paderborn University) are in the lucky position to have a skilled developer to work on the OxGarage. Our main focus is to add music (notation) specific conversion capabilities (for a „MEIGarage") but to keep a common code base with the TEI version and to update and enhance it in passing. Last week we had a first meeting between Paderborn and the TEI, namely Hugh Cayless and James Cummings, to discuss our plans. These are still quite technical (i.e. refactoring and restructuring the code base) but do need some organisational backing. In particular, we plan to split the OxGarage repo [1] into separate repos for every module (by keeping the appropriate Git version history for every module). For this, I want to add Anne as a collaborator to our TEIC GitHub organisation and she will add a few repos to our GitHub space. NB: At present, this will not affect our current OxGarage repo, nor the Docker images, nor the OxGarage deployments. You won’t notice anything but an increase of git repos at our TEIC Github :) We are still at a very early stage but will strive to engage with the (developers) community to share the plans and spread the knowledge more widely. This might involve a report to TEI Council during our next virtual f2f?! Hope this report was not too lengthy nor too short? If you have any questions, please do not hesitate to approach Anne (or me) directly. If I do not hear a loud „nay“ until next week, I will take this as approval and will perform the mentioned actions in our GitHub space :) Cheers Peter [1] https://github.com/TEIC/oxgarage

3 3

upcoming Stylesheets meeting
by Bauman, Syd 26 Jul '21

26 Jul '21

Four of us have explicitly expressed preference (on Slack) to move the Stylesheets meeting of Thu 22 Jul (which is in the middle of ACH) to Thu 29 Jul rather than this coming Thu 15 Jul (or leaving it 22 Jul, which is somewhat of a non-starter). Unless 3 or more object quickly and loudly I am going to make it so.

3 3

Next SVF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jul '21

08 Jul '21

Dear all, The next SVF2F meeting will take place on October 1 and 2. These are the meeting times (please verify in the google calendar): Friday, Oct 1 13:00-16:00 PST 16:00-19:00 EST North American break-outs Saturday, Oct 2 09:00-12:00 BST 10:00-13:00 CET European break-outs 06:00-10:00 PST 09:00-13:00 EST 14:00-18:00 BST 15:00-19:00 CET Full Council meeting There is already an agenda in case you come across topics that you want to discuss (and add): https://docs.google.com/document/d/18RIt71cxW8ywCI-Km5cDr7gOR3pIwupHxa7VWhd… Best, Martina

1 0

Next release + working groups
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jul '21

08 Jul '21

Dear all, The next release will take place in about one month+ (refridge 11 Aug; freeze 15 Aug; release 18 Aug). There are a lot of issues labeled with milestone 4.3.0 (https://github.com/TEIC/TEI/issues?q=is%3Aopen+is%3Aissue+milestone%3A%22Gu…) I want to ask you to focus on those issues and tackle as many as we can before refrigeration. If you think you cannot tackle the issue before the next release, please remove the milestone 4.3.0 or change the milestone label to 4.4.0. In our meeting today we discussed to organize small working groups in July/begin of August. This is how it works: if you want to work on an issue (ticket or otherwise) in pairs or a small group, please ask for a potential "buddy" on the mailing list or on Slack to join you. Best, Martina

1 0

Call starts in 1 hour
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jul '21

08 Jul '21

Dear all, our call starts in one hour. This is the agenda: https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…<https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…> Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Montag, 5. Juli 2021 09:43 An: tei-council(a)lists.tei-c.org Betreff: Call on Thursday, July 8 Dear all, This is the agenda for our next regular Council call on Thursday, July 8 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…<https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31…> Please add issues you would like to discuss. Best, Martina

1 0

Call on Thursday, July 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 05 Jul '21

05 Jul '21

Dear all, This is the agenda for our next regular Council call on Thursday, July 8 at 10:30am-12:00pm PDT, 1:30pm-3:00pm EDT, 6:30pm-8:00pm BST, 7:30pm-9:00pm CEST https://docs.google.com/document/d/1_G_4OYWSlU10_LjZCMtrAwSFvyQORwQM7uXik31… Please add issues you would like to discuss. Best, Martina

1 0

Organisation of SVF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Jul '21

01 Jul '21

Dear all, Since we could not find a suitable date for the SVF2F meeting in July or August, I've set up a new Doodle for September/first half of October. Please fill in your possible dates. https://doodle.com/poll/ptp7wp5w8hes5tpm?utm_source=poll&utm_medium=link As always, the North American Group will start Friday evening, the European group will continue on Saturday morning, and we meet all together on Saturday afternoon (for the Europeans) / Saturday morning (for the North Americans). Best, Martina

1 0

Menus. Point release?
by Hugh Cayless 22 Jun '21

22 Jun '21

Hi All, You may or may not have noticed that the menus on the Guidelines pages no longer 100% match the menus on the rest of the website. That's because we've sorted out how to edit the website menus, but the Guidelines menus are static, generated from the website at build time. I've just committed a new version that grabs the menu structure live from the website API and incidentally also dispenses with the old UDM Javascript menu code—in our brave new world, you can do these things exclusively in CSS, so why not? My question is whether this warrants a patch release to get things lined up again. Or really whether this even rises to the level of a patch. Maybe it should stay 4.2.2, just with a different build tag. Or we could just wait until the next release :-). Hugh

2 1

upcoming Stylesheets meeting
by Bauman, Syd 21 Jun '21

21 Jun '21

We are scheduled to hold a Stylesheets meeting this coming Thu 24 Jun at 17:30Z for 1½ hours. That is * 10:30–12:00 PDT * 13:30–15:00 EDT * 18:30–20:00 BST * 19:30–21:00 CEST Martina — will you be sending out a Zoom (or whatever) link or shall I? Proposed agenda: 1. Ticket 444<https://github.com/TEIC/Stylesheets/issues/444>, which we have tried before, but for which Martin & I have a new proposed solution. 2. Ticket 399<https://github.com/TEIC/Stylesheets/issues/399>, which we have tackled in the past only to find there were sequalae to the obvious solution. One possible approach: if we have 6 or more people, we could split into 2 groups and tackle them simultaneously. I like that idea for reasons of efficiency; I don’t like it in that I would feel left out of ½ of the fun.

3 2

Meeting times: Council and Stylesheets call
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Jun '21

19 Jun '21

Dear all, at our last Council meeting we agreed that we want to start with our monthly Council and Stylesheet call 30 minutes earlier. I hope this is also fine for the Council members who were not present at this meeting, and for Martin and Nicholas who regularly attend the Stylesheets meeting. This means that we start at: 10:30am PDT, 1:30pm EDT, 6:30 BST, 7:30pm CEST. Our next Stylesheets call is on Thursday, June 24. Best, Martina

2 1

renamed Jenkins repo branch to main
by Peter Stadler 15 Jun '21

15 Jun '21

Dear all, just a quick note that I changed the branch name from master to main in the Jenkins repo [1]. Additionally, I merged the current dev branch into the (new) main branch since this branch was not building anymore due to an outdated Debian package. housekeeperly greetings Peter [1] https://github.com/TEIC/Jenkins

1 0

handling multiple slots of different durations of service
by Bauman, Syd 14 Jun '21

14 Jun '21

[For Janelle our Nominations Committee representative] Problem: There are 6 positions open on Council, 4 of which are for 3-year terms (the usual), and 2 of which are for 1-year terms (due to recent by-law change). Possible solutions, from the idiotic to the clever (but not necessarily in that order here) include: 1. Elect 6 people, randomly assign who gets 1- and who gets 3-year terms. 2. Hold separate elections in OpaVote (or whatever) as if they were entirely different positions. 3. Just elect 6 people, let Council decide which ones serve for how long. 4. Just elect 6 people, let them fight it out among themselves. 5. Elect 6 people, let them each blindly choose 1- or 3-year term based on ranking 6. Elect 6 people, let them each choose 1- or 3- year term based on ranking in discussion with each other. Since #5 and #6 are my suggestions, I will detail them a bit, below. Worth noting, though, that although #2 has the huge advantage that a nominee could decide in advance that she wants to stand for only 1 year, it simultaneously has the disadvantage that each nominee has to decide in advance how many years he wants to run for, and he might win or lose depending on who else decides to go for that number of years. More importantly, perhaps, running a separate election would likely be a big pain for those running the elections. Because we are using an instant run-off election or ranked-choice voting system, whoever is running the election knows who among the 6 people elected got the most votes, the 2nd most votes, etc. (Even if that information is not shared with the electorate.) Thus for suggestions #5 the highest ranked Councilor-elect gets to choose whether she wants one of the two 1-year or one of the four 3-year terms. Then the 2nd highest is asked if he wants the one remaining 1-year or one of the four remaining 3-year terms OR if he wants one of the two remaining 1-year or four remaining 3-year terms. If any 1-year terms remain, the third ranking is asked to choose. And so on, until there is no longer any choice (because only one term length remains available). In suggestion #5, each Councilor-elect is queried in private (probably via e-mail or phone call) in rank order. Suggestion #6 is the same, but to ask the question of each in order with all 6 of them in the same (virtual) room, so haggling can take place. (So someone who really only wants to commit to 1 year can maybe convince someone higher in the rankings who doesn’t care …)

3 2

Reminder: meeting start in 90 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Jun '21

10 Jun '21

Dear all, please have a look at the agenda for our meeting at 10am-11:30pm PDT/1pm-2:30pm EDT/6pm-7:30pm BST/7pm-8:30pm CEST - which is one hour earlier than usual: https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Best, Martina

1 0

Tomorrow's meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Jun '21

09 Jun '21

Dear all, For those who didn't see the poll on slack about the meeting times tomorrow: Would it be possible for you to start the meeting an hour earlier (at 10am PDT / 1pm EDT / 6pm BST / 7pm CEST) so that Elisa and Janelle can join the whole meeting? Best, Martina

1 0

Next Council call: June 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Jun '21

08 Jun '21

Dear all, This is the agenda for our next Council call on Thursday, June 10 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1THZdj_acrUBpBejrs7MJA7eTtDtHGTZqAEa-T8i… Since we could not agree on a new date that suits everyone, we will stick with Thursday for the time being. Best, Martina

2 2

Stylesheets meeting?
by Bauman, Syd 27 May '21

27 May '21

Martina — I forgot ask in last e-mail that you let us know where the Stylesheets meeting will take place. If I don't hear from you in ~2 mins (here or Slack), I will post a personal Zoom meeting invitation here.

4 4

Meeting in ~46.3 hours
by Bauman, Syd 27 May '21

27 May '21

We are scheduled for a Stylesheets meeting this coming Thu 27 May, 18:00/19:30Z. That means starting at * 11:00 PDT, * 14:00 EDT, * 19:00 BST, & * 20:00 CEST, and scheduled to run for 1½ hours. Agenda items I would like to cover, other suggestions welcome: * (~4 min) Quick review of P5subset updating plans * (~4 min) report on progress on automation thereof (PS) * (~4 min) Quick report on #496<https://github.com/TEIC/Stylesheets/pull/496> progress (either MH or NC) * (~1 hour) Ticket #327 <https://github.com/TEIC/Stylesheets/pull/327>

2 1

Stylesheets meeting: May 27
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 May '21

25 May '21

Dear all, This is the zoom link for our meeting on Thursday, May 27 at 11 am PDT / 2 pm EDT / 7 pm BST / 8 pm CEST: https://zoom.us/j/94174447570?pwd=eGJmNXdkYlZsVWhSMHdNVmdONjZyQT09 And here is a blank google doc to which Syd will hopefully add some exciting issues. https://docs.google.com/document/d/1wbrqKTXN3_8cw4VCmn3rEJicu6SnwiDBcKWpwS9… Best, Martina

1 0

xmllint issues
by BERMUDEZ SABEL Helena 23 May '21

23 May '21

Hi all, At the last Stylesheets meeting, we checked how the command "xmllint --format -" that is run when testing the HTML transformations adds the XML declaration to the output file (which was a bit counterproductive because the XSLT code was explicitly demanding the omission of the declaration). Now I’ve run into another problem that is also generated due to the xmllint command: it outputs XML entities when a literal string is expected. I run the script without xmllint and the output is the expected one so it seems that it is another of the modifications done by this program. This issue primarily affects the quotation marks that are added in the HTML output using CSS. See diff: 17c16 < content:"‘"; --- > content:"‘"; 20c19 < content:"’"; --- > content:"’"; 23c22 < content:"“"; --- > content:"“"; 26c25 < content:"“"; My guess is that this wasn’t an issue before because xmllint had as an input a file with the XML declaration. Now it finds a file whose first line is the HTML doctype declaration and thus adds these modifications. Considering that in the HTML transformation Saxon already has the command to indent the results, my proposal is to modify Test/Makefile and delete the "xmllint" command ONLY for the transformations to HTML. Would this be a viable solution? Best, H. Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel

3 4

Doodle for regular Council call
by Scholger, Martina (martina.scholger＠uni-graz.at) 13 May '21

13 May '21

Dear all, As discussed during the VF2F meeting, I've set up a doodle to coordinate the meeting times for the monthly Council call for the next couple of month. I'll try again with the second week of each month (2nd Mon/2nd Tue etc.). As soon as we figured out the dates for the Council call, I'll set up a doodle to coordinate the Stylesheets meeting. Please fill in the doodle by 2021-05-17. https://doodle.com/poll/h3v3kwctxztauz9r?utm_source=poll&utm_medium=link Best, Martina

2 1

This is a test
by Peter Stadler 12 May '21

12 May '21

… as requested by Martina Best Peter

1 0

Next call: Thu May 13
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 May '21

11 May '21

Dear all, This is the agenda for our next regular Council call on Thursday (May 13) at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1pxhmicmZMLMaOfNfDb0BCCLO9jvn0cKRpma91xt… Best, Martina

1 0

VF2F meeting, May 7 and 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 May '21

01 May '21

Dear Council, This is the agenda for our virtual F2F meeting on Friday and Saturday (May 7 and 8): https://docs.google.com/document/d/18ZqzRQVAEA6yShflaahqs092xegVDrZosbIIVyK… Please feel free to add more topics to the agenda. Best, Martina

1 0

Issue 178 branch built successfully
by Martin Holmes 22 Apr '21

22 Apr '21

For everyone who was at the Stylesheets group meeting today: It looks like our ticket #178 work was successful, so I believe it's OK for someone to merge that branch. The temporary Jenkins job succeeded, and I just ran Test2 locally without problems. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

reminder: upcoming Stylesheets meeting Thu 22 Apr 18:00Z
by Bauman, Syd 22 Apr '21

22 Apr '21

We have a Stylesheets meeting scheduled for this coming Thursday 22 April 21 at 18:00Z for 1½ hours. That is * 11:00 PDT * 14:00 EDT * 19:00 BST * 20:00 CEST I hope to post a list of topics 48 hours before the meeting starts. (I expect to post a list of topics 24 hours before the meeting starts. :-) I hope Martina will post the Zoom details and perhaps a Google Doc for us to use 24 hours before the meeting starts. (I expect Martina to post the Zoom details and perhaps a Google Doc for us to use 24 minutes before the meeting starts. :-)

3 2

Fwd: Travis CI: [27421] - OSS credits for Text Encoding Initiative (@TEIC)
by Peter Stadler 20 Apr '21

20 Apr '21

Hi all, fowarding this fyi. That means, Travis checks are currently working again for the TEI repos (you may have noticed the reappearance of the green check marks at the GitHub commits?) Yet we were only provided a total of 25k credits which will not last long. So I think we should move on to GitHub actions (next to our self hosted Jenkins servers). I’m volunteering to do so but will not get to it in the near future. So, if anyone else steps forward please go ahead! Best Peter > Anfang der weitergeleiteten Nachricht: > > Von: "Qasim Abdullah (Support)" <support(a)travis-ci.com> > Betreff: Travis CI: [27421] - OSS credits for Text Encoding Initiative (@TEIC) > Datum: 14. April 2021 um 22:23:18 MESZ > An: Peter Stadler <pstadler(a)mail.uni-paderborn.de> > Antwort an: Support <support(a)travis-ci.com> > > ##- Please type your reply above this line -## > from Travis CI has an update for your ticket, #27421 <https://support.travis-ci.com/hc/requests/27421>. If you'd like to add additional comments, please reply to this email: > > > > Qasim Abdullah (Travis CI) > Apr 14, 2021, 16:23 EDT > > Hello Peter, > > Please accept our sincere apologies for any inconvenience caused due to delays in processing your open-source credit request while we made improvements to the platform. > > Open source has always been and always will be at the core of what Travis CI stands for. After reviewing your open source qualifications, I am pleased to notify you that 25k credits were added to your Github Organisation "TEIC" allowing you to resume running OSS builds. When your credits begin running low again, please reach back out to the Support team. > > Credits Consumption Metric > OS. # CREDITS PER STARTED BUILD MINUTE > Linux. 10 > Experimental FreeBSD. 10 > Windows. 20 > MacOS. 50 > > > Please let us know if you have any questions! > > Thanks and happy building!, > > -- > Qasim > > Your Friends @Travis CI > > Test and Deploy with Confidence. > www.travis-ci.com <http://www.travis-ci.com/> > — > Travis CI GmbH, Rigaer Str.8, 10247 Berlin, Germany | GF/CEO: Randy Jacops | Contact: contact(a)travis-ci.org <mailto:contact@travis-ci.org> | Amtsgericht Charlottenburg, Berlin, HRB 140133 B | Umsatzsteuer-ID gemäß §27 a Umsatzsteuergesetz: DE282002648 > > > > > Peter Stadler > Mar 16, 2021, 11:17 EDT > > Hi Travis support, > > the Text Encoding Initiative was happily using Travis CI for automated testing of our Open Source software hosted on GitHub and we really enjoyed the seamless support – many thanks for that! Recently we were hit by the new(?) constraint on credits so I wanted to ask whether (and how) it’d be possible for us to obtain ~10,000 monthly credits? > > My account name is @peterstadler on GitHub and I’m asking for the @TEIC organisation. > > Many thanks in advance > and best regards > Peter > signature.asc > > Attachment(s) > signature.asc <https://support.travis-ci.com/attachments/token/w2bwTYU0a9oSxX3D9GV6anmkE/?…> > This email is a service from Travis CI. Delivered by Zendesk <https://www.zendesk.com/support/?utm_campaign=text&utm_content=Travis+CI&ut…>[5LKOVG-94G7]

1 0

oXygen plug-in 14.0.0 releaesd
by Bauman, Syd 20 Apr '21

20 Apr '21

Martina — Martin, Hugh, and I have just released the new oXygen plug-in 14.0.0 for 4.2.2 and 7.51.2 (both bleeding edge, which is automatic, and real one via GitHub). This can be announced. In the process Martin updated the ant build script to work with the new Humana server. Martin is planning to update TCW22 within the next few hours.

4 4

GPG Key Expiration
by Nicholas Cole 19 Apr '21

19 Apr '21

Dear Council, Just to let you know — as part of creating the P5 4.2.2 release, I needed to update the expiration date for the gpg key, in order to build the Debian Package. I’ve set it for 3 months hence, but obviously it can be changed to whatever the Council thinks is appropriate! Best wishes, Nicholas

2 1

New release: Guidelines 4.2.2 / (unchanged) Stylesheets 7.51.2
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Apr '21

19 Apr '21

Dear TEI Community, After release 4.2.1, an issue was noticed concerning the controlled value lists of certain type attributes. The list was not appearing in either the documentation output or schemas. Thus a followup version 4.2.2 of the Guidelines and a corresponding (but unchanged) version 7.51.2 of the Stylesheets has been released to fix the issue. The following change was made to the Guidelines: * Add a mode attribute with value add (#2128<https://github.com/TEIC/Stylesheets/issues/2128>) to each type attribute that overrides the att.typed class. Thanks to Syd Bauman, Helena Bermúdez Sabel, Hugh Cayless, Nicholas Cole, Martin Holmes, Janelle Jenstad, and Peter Stadler for discovering and fixing this issue and accompanying the release process. Please find the full release notes including the notes of the Guidelines versions 4.2.1 and 4.2.0 and the Stylesheets versions 7.51.1 and 7.51.0 here: https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-4.2.2.html All of the TEI Consortium's software projects are hosted at https://github.com/TEIC and issues or feature requests should be reported at the various project repositories there. The Guidelines are available from all the usual places (such as the TEI website http://www.tei-c.org/release/doc/tei-p5-doc/en/html/index.html and the GitHub site https://github.com/TEIC/TEI/releases/tag/P5_Release_4.2.2) A new release of the TEI Stylesheets has been made in conjunction with the 4.2.2 release at https://github.com/TEIC/Stylesheets/releases/tag/v7.51.2. Furthermore, the Debian package has been updated at http://packages.tei-c.org/deb/. The TEI Guidelines and the Stylesheets are also available for download at https://sourceforge.net/projects/tei/files/. A documentation on how to update your oxygen is available at https://github.com/TEIC/oxygen-tei/blob/master/oxygen-tei-plugin.md. As always, we encourage you all to report bugs and make feature requests via the GitHub site at https://github.com/TEIC/TEI/issues. Best, Martina 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 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> 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

time to announce new release
by Bauman, Syd 12 Apr '21

12 Apr '21

Martina — Nick and I have finished the GitHub and SourceForge releases of 4.2.2 and 7.51.2. (Nick is still working on the Debian packages; Martin & Peter will do oXygen next week.) So it is time for step 22, which I think is up to you or Hugh, right? Update the list of previous releases of P5, which is found at https://tei-c.org/guidelines/p5/#section-2.If you have editing privileges on the TEI WordPress on tei-c.org, add the new release to the top of the release table. If not, ask one of the other Council members who does (currently Martina Scholger and Hugh Cayless) to make the change.

4 6

on ticket 2049 step 2
by Bauman, Syd 12 Apr '21

12 Apr '21

With 8 people (7 from Council) voting, there are only 2 places left that need discussion on the question of whether <altIdent> should be an allowable child. 1. <language>, which is not in the tagdocs module and does not currently have an <altIdent> child. It does have its own @ident. 2. <paramSpec>, which is in the tagsdocs module and does currently have an <altIdent> child. It gets @ident via the att.identifiable class. Please let’s discuss these two on the ticket<https://github.com/TEIC/TEI/issues/2049>, where I have posted a summary<https://github.com/TEIC/TEI/issues/2049#issuecomment-817394059> of step (2) decisions so far. I hope to post my own opinions later tonight, but need a break first, so I may not get to it.

1 0

The Never-ending 4.2 release!
by Nicholas Cole 11 Apr '21

11 Apr '21

Dear Council, Still with my release-manager hat on (!), Syd and Helena have noticed that a folder has been missing from recent releases of TEI. This is going to need another point release to fix. Fortunately, term doesn’t start again here for another two weeks, so I’ve actually got plenty of time to work on this in the coming days. Would some time on Monday or Wednesday suit people, for example? Syd, if you have time, perhaps we could hack away at a fix on Monday and then do the .3 release on Wednesday? We should probably also write a test to catch this kind of thing... Best wishes, Nicholas

7 13

Fwd: AW: link rot
by Lou Burnard 11 Apr '21

11 Apr '21

Actually, on further investigation, it seems that all I need to change is the explicit reference to "index.xml" http://www.tei-c.org/Guidelines/P5/#previous works just as it used to. -------- Forwarded Message -------- Subject: Re: AW: [Tei-council] link rot Date: Sun, 11 Apr 2021 12:28:42 +0100 From: Lou Burnard <lou.burnard(a)retired.ox.ac.uk> To: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Dear Martina Thanks for the quick response. I will tweak my tuto accordingly. It seems a shame that the ability to link to a specific part of this (rather long) page has been removed, but I guess thems the breaks. best Lou On 11/04/2021 12:21, Scholger, Martina (martina.scholger(a)uni-graz.at) wrote: > Dear Lou, > > this is the link to the table: https://tei-c.org/guidelines/p5/ > > Best, > Martina > > -----Ursprüngliche Nachricht----- > Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von > Lou Burnard > Gesendet: Sonntag, 11. April 2021 13:19 > An: tei-council(a)lists.tei-c.org > Betreff: [Tei-council] link rot > > There used to be a useful table listing the dates and version numbers > of all TEI P5 releases at > http://www.tei-c.org/Guidelines/P5/index.xml#previous > <http://www.tei-c.org/Guidelines/P5/index.xml#previous> > > But now it seems to have disappeared. Could you either put it back or > tell me where it's gone?My ODD chaining tutorial is broken without it. > > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

link rot
by Lou Burnard 11 Apr '21

11 Apr '21

There used to be a useful table listing the dates and version numbers of all TEI P5 releases at http://www.tei-c.org/Guidelines/P5/index.xml#previous <http://www.tei-c.org/Guidelines/P5/index.xml#previous> But now it seems to have disappeared. Could you either put it back or tell me where it's gone?My ODD chaining tutorial is broken without it.

2 1

Today's release preparations
by Martin Holmes 09 Apr '21

09 Apr '21

Hi all, Today Janelle, Martina, Nick, Syd and I in various combinations got this far with the new release: - Created new point-release branches for the TEI and Stylesheets repos. - Cherry-picked the fix commit into the P5 branch. - Added new release notes for this P5 release, and updated the two VERSION files. - Built the P5 branch in various places and confirmed it was good. - Took the p5subset from that branch and put it into the Stylesheets point-release branch. - Built the stylesheets and fixed all the many issues in tests resulting from the new p5subset. - Merged both these branches into the respective -released branches. Those branches are now building on the Jenkinses, eg: <https://jenkins.tei-c.org/view/TEI%20stable/> and when all those builds are complete, we'll have products we can use to create the release itself. The plan is for some of us to reconvene tomorrow if possible (Nick, Syd says he's available to help if you can arrange times). Anyone is of course welcome to ride along with the rest of the release process to learn how it works. I believe we will be starting from point 13, "Log into TEI server and run the tei-install.sh script", on TCW22: <https://teic.github.io/TCW/tcw22.html> Some time next week, once the release is done, Hugh and I should get together with anyone else who wants to learn the process and do the Oxygen plugin release, updating point 23 in TCW22 as we go. Anything I've missed? Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

Call today
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Apr '21

08 Apr '21

Dear all, This is the agenda for our meeting today (11am PDT / 2pm EDT / 7pm BST/ 8pm CEST) https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… and the zoom link https://us02web.zoom.us/j/82014974946?pwd=OVZXbTNkU1kyWGhEOUR3VWh0WUF3dz09 Best, Martina Von: Scholger, Martina (martina.scholger(a)uni-graz.at) Gesendet: Dienstag, 6. April 2021 16:25 An: tei-council(a)lists.tei-c.org Betreff: Next meeting: April 8 Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Fairly urgent bug in recent releases
by Martin Holmes 06 Apr '21

06 Apr '21

Hi all, Janelle and I came across a bad problem with releases starting at 4.0.0, which means that valLists for the @type attribute in 21 elements are missing from both the Guidelines pages and the schemas. There's a bug here: https://github.com/TEIC/TEI/issues/2128 and a PR with a full fix here: https://github.com/TEIC/TEI/pull/2129 Both Syd and I think this is bad enough to warrant an interim release. Could anyone with a free moment take a look at the bug and the PR, and review or comment? Also, could you weigh in on whether you agree that it deserves a quick release? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

6 8

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

06 Apr '21

Dear all, This is the agenda for our next Council meeting on Thursday, April 8 at 11am-12:30pm PDT/2pm-3:30pm EDT/7pm-8:30pm BST/8pm-9:30pm CEST. https://docs.google.com/document/d/1zCtgIH0YdAxviSGm8p72rZ6xmouStm8F8PoU9VA… Please add discussion topics to the agenda. I think we should discuss the point release issue at this meeting. Best, Martina

1 0

Council meetings missing from google calendar
by Scholger, Martina (martina.scholger＠uni-graz.at) 01 Apr '21

01 Apr '21

Dear all, Jessica brought to my attention that the dates for the regular Council meetings are missing in our shared google calendar (even the past meetings). I don't know how this could have happened. I have added the dates again, our next meeting will be on Thursday next week, April 8. Best, Martina

1 0

Stylesheets meeting today, Thu 25 Mar
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Mar '21

25 Mar '21

Dear all, please find the google doc for our Stylesheets meeting here: https://docs.google.com/document/d/1Qolxk9yzIAtqofcu7szuPArOuv1koy6g-bjhM1r… Meeting times: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) Zoom link: https://zoom.us/j/95354913465?pwd=ODZpVUxFVmJjWnlIZnBnaCtIVnFadz09 Best, Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Bauman, Syd Gesendet: Mittwoch, 24. März 2021 04:09 An: tei-council(a)lists.tei-c.org Betreff: Re: [Tei-council] upcoming Stylesheets meeting, Thu 25 Mar Topics for discussion, in no particular order: * 2-minute update on Saxon 9 -> Saxon 10 (MH) * Did we have more to discuss or work on for PR #327<https://github.com/TEIC/Stylesheets/pull/327>? (I forget) * Close issue #272<https://github.com/TEIC/Stylesheets/issues/272> and create new ticket for @mode? * Didn't we fix #482<https://github.com/TEIC/Stylesheets/issues/482>? * Issues we have started delving into, but have not solved: * Issue #327<https://github.com/TEIC/Stylesheets/issues/237>, generating an element or attr that has the same local-name as a TEI element or attr * Issue #402<http://We%20need%20a%20volunteer%20to%20write%20a%20test%20ODD>, on @mode: we need a volunteer to write a test ODD * Issue #399<https://github.com/TEIC/Stylesheets/issues/399>, <code> being dropped from <desc> * Issues that have had a lot of work done, but still are not fixed: * Issue #444<https://github.com/TEIC/Stylesheets/issues/444>, <desc> getting dropped * Issue #102<https://github.com/TEIC/Stylesheets/issues/102>, for which we now have test output, and I finally sort of understand the problem * Issue #424<https://github.com/TEIC/Stylesheets/issues/424>,@ns causing pain ________________________________ We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 1

upcoming Stylesheets meeting, Thu 25 Mar
by Bauman, Syd 24 Mar '21

24 Mar '21

We are scheduled to meet (on Zoom, right Martina?) this coming Thu 25 Mar 21 at 19:00Z for 1½ hours. Due to daylight saving time mis-match, this meeting time will be different for some people, most likely for this meeting only. Times are: * 12:00 PDT (Victoria, BC) * 15:00 EDT (New York) * 19:00 GMT (London) * 20:00 CET (Vienna) I plan to post a suggested agenda 24+ hours before the meeting starts. (So if you want something on the agenda, let me know now.)

2 2

git me this
by Bauman, Syd 23 Mar '21

23 Mar '21

I have on my local HD a copy of a fork one of our repos.[1] The interesting bit of this repo is in its dev branch. But sadly, its dev branch is somewhat behind our dev branch. So I would like to merge our dev branch in. How do I do that? I.e., how do I specify that I want the git merge command to use our repo’s dev branch (not the current repo’s dev branch, which would be silly, as I am on the current repo’s dev branch) as the upstream? Note [1] https://github.com/sanskrit-coders/Stylesheets.git to be precise, but that detail does not matter.

2 4

p5subset.xml and TCW22
by Martin Holmes 12 Mar '21

12 Mar '21

Hi all, Syd, Nick and I were looking at the Stylesheets repo this morning and we realized that the version of p5subset.xml in its source subfolder had not been updated for quite a long time. That means the Stylesheets tests were running against an old version of the Guidelines. When we decided to put p5subset.xml into the Stylesheets repo, the purpose was to avoid the circularity problem that causes an inability to build each repo against the other. That's been successful, but the corollary was that we should regularly update the p5subset.xml in the Stylesheets repo so that we caught new issues resulting from changes to the Guidelines in good time. That hasn't happened. We added an updated p5subset.xml this morning, and there were a LOT of test issues to fix, although none of them were significant. We've added two new steps to TCW22 so that at the beginning of the freeze or refrigeration period[1], an up-to-date p5subset.xml is added, meaning that almost everything will get fixed at that point; and then later, once the release-X.X.X branch of P5 is building, the p5subset.xml from that gets added into the release-X.X.X branch of the Stylesheets, so that our release is actually coordinated (the states of the two repos match), prior to the release. In the process, we also noticed that lots of the instructions about creating the release-X.X.X branch were written to apply ONLY to the TEI repo, but the same steps also have to happen for the Stylesheets repo, so we've made that more explicit. In our regular Friday meetings, the three of us are going to make a point of updating p5subset.xml so we don't get so far out of sync again. Anyone else is also free to update it any time of course. Cheers, Martin [1] TCW22 doesn't adequately distinguish these two phases; we should fix that. -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

minute assist
by Bauman, Syd 11 Mar '21

11 Mar '21

Janelle — The “minute assist” task is not about taking minutes during the meeting (in theory we all chip in on that), but rather is about helping the Chair whip the notes taken during the meeting into publishable minutes. Martina typically does this by transferring them to another GoogleDoc, making “suggestion” changes there, and then asking the minute assist person to review those changes and make any of her or his own. (Other Chairs have done it differently in the past, but that’s not important right now. :-) If that means you do not have time to do minute assist for this month, just say so. I spent much less time than expected last week on the minute assisting of the SVF2F, so would not mind doing this one.

1 0

call in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Mar '21

11 Mar '21

Dear all, Our call starts in 30 minutes: https://docs.google.com/document/d/1qcs0bVOjgm0ae7x7ZRMEMvlsipZ4FXzBNJXe5Oj… Best, Martina 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 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> 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 2

Next call: Thursday, March 11
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Mar '21

09 Mar '21

Dear all, Our next TEI Council meeting is scheduled for Thursday, March 11 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET. Please add discussion topics to the agenda: https://docs.google.com/document/d/1qcs0bVOjgm0ae7x7ZRMEMvlsipZ4FXzBNJXe5Oj… The zoom link is in the google doc. Best, Martina

1 0

Deb packages key signing broken?
by Martin Holmes 07 Mar '21

07 Mar '21

Hi all, My Jenkins server says: Err:9 https://packages.tei-c.org/deb/binary ./ Release.gpg The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> [...] W: An error occurred during the signature verification. The repository is not updated and the previous index files will be used. GPG error: https://packages.tei-c.org/deb/binary ./ Release: The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> W: Failed to fetch https://packages.tei-c.org/deb/binary/./Release.gpg The following signatures were invalid: EXPKEYSIG 19CF3E497B9824DC TEI Council (GPG key for signing Debian packages) <council(a)tei-c.org> Did the packages get signed correctly, or has the key expired? Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

3 3

what we’re up to
by Bauman, Syd 05 Mar '21

05 Mar '21

Martin, Nick, and I are halfway through updating the repos to use Saxon 10. We have finished the Stylesheets repo, which was probably the easier one. It has been checked in as the “saxon10” branch. We expect to do the TEI repo soon (unless someone else jumps on this interminable task). We expect to issue a PR for each repo, assigned to the same person (any volunteers?), at roughly the same time. Probably a good idea that each of the repos be merged at roughly the same time, too. (I think there shouldn’t be any circularity problem from this change, but just in case, having them both get to Mr. Jenkins in the same cycle sounds like a good defense.) I just realized there are no tickets for this, so I plan to create issues now.

1 0

Stylesheets meeting Thu 04 Mar
by Bauman, Syd 04 Mar '21

04 Mar '21

We have a Stylesheets meeting scheduled for tomorrow (likely today by the time you read this), Thu 04 Mar, 19:00Z to 20:30Z. That is * 11:00 PST * 14:00 EST * 19:00 GMT * 20:00 CET for 1½ hours. Agenda: 1. Update to 7.51.1, i.e. issue #488, PR #489 (Syd & Martin) 2. Issues surrounding yesterday’s release of TEI framework for oXygen (Hugh & Martin) 3. Detailed review of PR #327 (Peter) 4. Review of PR #462 (Syd)

3 2

TEI release directory structure
by Peter Stadler 01 Mar '21

01 Mar '21

Hi all, apologies for sending to both groups, but this issue is kind of between Council and infrastructure group, so I thought I’d be better to include both. The issue I see is about the „release“ directory structure, i.e. the stuff at https://tei-c.org/release/ Currently, on the Huma-Num server, „release“ is just a symlink pointing at "Vault/P5/current“ – this caused frequent errors with the Stylesheets release missing due to missing CSS files for building ePubs. It was hacked around by copying Stylesheets to P5 or symlinking Stylesheets into P5. Since the structure under „release“ seems to mimic the "/usr/share/doc“ and „/usr/share/xml“ structure known from Debian systems – and this is the place where the TEI Debian packages are installed by default – I think the *original* setup might have looked like an apache Webserver simply serving its local „/usr/share“ directory under „release“ to the outside. At the latest with the ADHO server crash, this setup got lost and we have a semi-functioning release directory now. IMHO, with our current infrastructure, the proper setup would be to (hard) create the directory „release/doc“ and „release/xml/tei“ and create symlinks within these directories to the respective directories in the Vault: release/doc * tei-p5-doc —> ../../Vault/P5/current/doc/tei-p5-doc * tei-p5-exemplars —> ../../Vault/P5/current/doc/tei-p5-exemplars * tei-xsl —> ../../Vault/Stylesheets/current/doc/tei-xsl release/xml/tei: * Exemplars —> ../../../Vault/P5/current/xml/tei/Exemplars * Test —> ../../../Vault/P5/current/xml/tei/Test * custom —> ../../../Vault/P5/current/xml/tei/custom * odd —> ../../../Vault/P5/current/xml/tei/odd * schema —> ../../../Vault/P5/current/xml/tei/schema * stylesheet —> ../../../Vault/Stylesheets/current/xml/tei/stylesheet * xquery —> ../../../Vault/P5/current/xml/tei/xquery release/oxygen —> Vault/P5/current/oxygen Does that make sense? Anything I’m missing? And of course, I’m curious about some more history that Lou(?) or James(?) might be able to share? Best Peter

3 2

Stylesheets meeting is scheduled for this Thu 04 Mar 19:00Z
by Bauman, Syd 01 Mar '21

01 Mar '21

If I understand correctly, we are scheduled to hold a Stylesheets meeting this coming Thursday, 04 March at 19:00Z to 20:30Z. That is * 11:00 PST * 14:00 EST * 19:00 GMT * 20:00 CET for 1½ hours. I am expecting we will spend a little time reviewing the fix for the 4.2.1 release, and intend to post here an actual agenda with a ticket or two to work on by at least 24 hours before the meeting. I am hoping Martina will also post the details of how to get to the meeting here at least a few hours before the meeting. Looking forward!

1 0

Slight borkitude in moduleRef content model display
by Martin Holmes 25 Feb '21

25 Feb '21

Hi all, Just clicking around in the various types of Guidelines outputs, and I noticed this: <https://www.tei-c.org/release/doc/tei-p5-doc/en/html/ref-moduleRef.html> Take a look at the content model. It's the same in the ebook; it's slightly different but I think also borked in the PDF (p. 1402). I don't think it's urgent, because it was the same in 4.1.0. I'll raise a ticket and start investigating. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 3

Version 4.2.0 released
by Nicholas Cole 25 Feb '21

25 Feb '21

Dear Council, The Release team is happy to report that with the exception of the Oxygen Plugin, the build and release of P5 4.2.0 and Stylesheets 7.51.0 has been done. The release notes need some moderately extensive updating, and I will be making some suggested changes and a pull request later today / tomorrow. Very best wishes, Nicholas, Meaghan, and Peter.

3 3

GPG Key
by Nicholas Cole 23 Feb '21

23 Feb '21

Dear Council, Just to note that the current expiration date for the TEI GPG key is the second of next month. This can be extended, of course, without problem, but I’m not sure whose task that is. Best wishes, Nicholas

2 3

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

22 Feb '21

Dear all, I've added a first draft of the release notes to the release branch (release-4.2.0): https://github.com/TEIC/TEI/commit/06af7ce77dae7d133c39da68cf0a179a579bca0a Please feel free to modify and please correct my spelling errors. Best, Martina

5 8

Release Number?
by Nicholas Cole 20 Feb '21

20 Feb '21

Dear Council, There is a lot in this release. Have we all agreed what the version number is? ;-) If there are any last pleas not to ‘freeze’ yet, make them now. As far as I can see, the Jenkins servers are reporting builds correctly. I’m going to ‘freeze’ at 15:00pm UK time, for Release 4.2.0, unless we think this is a ‘major’ version. (I actually think there’s quite a lot in this release, actually). Best wishes, N.

6 6

Freeze?
by Nicholas Cole 20 Feb '21

20 Feb '21

Dear Council, I suppose the Freeze starts at the end of today. Is that right? N

3 6

broken persPronouns
by Bauman, Syd 18 Feb '21

18 Feb '21

~10 hours ago PR 2014 was merged into dev. This broke the build because we (Meaghan and I) had examples that used <persPronouns> in running-prose-like places (inside <closer> and <docAuthor>, to be precise); but, because <persPronouns> was (as per the original FR) only a member of model.personPart, it was only allowed inside <person>, <personGrp>, and <persona>. We put our heads together on a brief telephone consultation, and concluded that we believe that the new <persPronouns> element is going to be desired for the encoding of signature blocks in email or blog posts as much or more than in personographies. Therefore we think the solution is to permit <persPronouns> in those sorts of places, not to remove the examples. Thus I have made <persPronouns> a member of model.persNamePart (in addition to model.personPart). This allows <persPronouns> in <closer> and <docAuthor>, and thus should fix the build. It also allows <persPronouns> in quite a few desirable places like inside an <s>, a <p>, or an <item>. It also allows it inside lots of somewhat screwy places like <tagUsage> and <unti>. However, <roleName> (for example) is allowed in precisely the same set of places, so even if screwy, at least it is consistently screwy. If anyone wants to object, please do so quickly (by Fri latest, preferably earlier). The commit that would need to be reverted is 1f874af07. Sorry everyone. The reason this got past me, BTW, is because oNVDL does not run on my system. (Martin is saying “I told you so” right now. :-)

4 3

semantic version conversation
by Bauman, Syd 15 Feb '21

15 Feb '21

At the VF2F we apparently discussed PR 1996 (which implements one point of the discussion on issue 1993). Does anyone remember what, if anything, I said about it? My suspicion is I was making tweaks for 2032 at the time, and did not realize y’all were accepting the idea that TEI/@version (et al.) is a “version number following the Semantic Versioning Specification”. Because it is not. This would have serious (albeit extremely rare) side-effects in processing, because it means we would be obligated to drop anything from a ‘+’ on (i.e., the build metadata) when ascertaining order of precedence. Much more importantly, it means that we would be obligated to change our system of changing the MAJOR and MINOR portions of the version number. (The PATCH bit would still be updated only for backwards-compatible bug fixes.) We currently update MINOR every new release (roughly every 6 months), and only update MAJOR if and when there is a significant change in functionality (e.g., switching to PureODD). If we adopt SemVer, we would be obligated to change MAJOR whenever any backwards-incompatible change occurred, no matter how small. Furthermore, we would have to define backwards-incompatible. Obviously a change (even a bug fix) that changes the schema such that a document that was valid before the change is invalid after it is a change that requires a bump in the MAJOR portion in the SemVer system. But what about the reverse, a change that allows a document that had been invalid to be considered valid? (E.g., adding "PostScript" to the value list of @scheme in att.styleDef.) Seems to me that is backwards-incompatible too, just in a different way. (The schema no longer catches the same “error” it used to.) Conversely, of course, we could use the idea that SemVer refers to the incompatibility of the API, not of the schema, to decide not to bump MAJOR for incompatible schema changes. But if the version number is about the API, what API is it about, and what does it have to do with our release system and schemas? I think all of this can be avoided by just saying “based on” rather than “following” the Semantic Versioning specification. (Note that in either case it should be capitalized and have a reference in the bibliography to the spec<https://semver.org/> that we don’t follow but maybe will say that we do.) If y’all really think we really should say we are following it, I will accept the majority opinion. That said, you should not vote in favor of “following” until you have actually read the SemVer<https://semver.org/> spec.

5 9

keep Subversion version # capability? On stupidity
by Bauman, Syd 13 Feb '21

13 Feb '21

Hey all. Two things. First just wanted to clarify that when I said “because it’s stupid” in reference to <text> as a direct child of <teiCorpus>, I was trying to express that it was inappropriate and careless of us to ever let <text> slip into the content model of <teiCorpus> in that position (which happened in 2016-02). I am (as y’all can probably tell) somewhat annoyed with myself for not noticing this as a problem when it came up then. I was not calling users (like Martin and Janelle, among others) who make use of this perfectly valid facility stupid. My current annoyance, though, is some horrible code. Thus I want input on what to do with P5/repodate.xml. This is an untracked file generated by the Makefile during the P5 build process and read by the P5/Utilities/expand.xsl program. That program changes the <?insert date?> PI found in P5/Source/guidelines-en.xml (and in P5/Source/guidelines-fr.xml) and thus in p5.xml into the date the GLs were built, and changes the <?insert revision?> PIs into the git commit number, etc. This whole system is made quite a bit more complicated by the fact that the code is designed to work whether the version control system we use is Subversion or git. My instinct is that it is no longer useful to maintain the code that worries we might be using Subversion rather than git. We have not been using Subversion for roughly 5 years,[1] and I do not see us ever going back to it. Sure, GitHub the service is a company and may fold, but git the command is not going away. Something better may come along, and we may switch in the future, but that means re-working all this code, anyway. The only reasonable concern that floats through my tiny brain is that maybe we need this code in case someone uses the current build system to try to generate a very old copy of the Guidelines that dates back to the pre-git days. But I do not have any reason to believe that either anyone would use the modern Makefile to build an ancient copy of the Guidelines (you would use the build system that came with that revision), or that there would be any hope of success even if this code for handling Subversion revision numbers was left in place. So does anyone think we should leave the Subversion code in there? Going once … P.S. Given that we are in the refrigeration period, I will be doing this in a separate branch and leave it to others whether to merge it before or after release. It should have absolutely no effect on the output at all. (And if anything goes wrong, would be very easy to spot by just checking the output of PIs.) Notes [1] My vague recollection is that the changeover from Subversion in Sourceforge to git in GitHub was masterfully handled by Peter Stadler in 2015 or 2016.

3 4

Next VF2F: May 7 and 8
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Feb '21

12 Feb '21

Dear all, Our next virtual F2F meeting is on May 7 and 8. As last time, the North American Group starts on Friday at 12am PST / 3pm EST (3 hours); the Europeans continue on Saturday morning at 9am BST/10am CET (3 hours); the full Council meets on Saturday 6am PST / 9am EST / 2pm BST / 3pm CET (4 hours). Please have a look at the google calendar to check the meeting times. Best, Martina

1 0

Council call in 40 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 11 Feb '21

11 Feb '21

Dear all, Our call starts in 40 minutes. Agenda: https://docs.google.com/document/d/1mnUQtzMFTpPfUwoBQX2yo4g_sWeBrHBG4Z2myRK… The zoom link is in the google doc. Best, Martina

1 0

Re: [Tei-council] Mr. Jenkins is ignoring me
by Bauman, Syd 10 Feb '21

10 Feb '21

Thank you, Peter! (Why did I not see it in the dashboard? Why did I miss the build failure locally? Hmmm...) ________________________________ seems it’s there at https://jenkins.tei-c.org/job/TEIP5-Test-dev/680/ The build has been kicked off due to your commit but failed, hence the subsequent jobs have not been started at all.

1 0

Mr. Jenkins is ignoring me
by Bauman, Syd 10 Feb '21

10 Feb '21

Attn: Peter & Martin I committed to dev branch at 20:50:00 localtime (± 6 sec), commit #9d8122417ee2ec8d05f979bf920f98069586817a. That was over 2 hours ago, and yet neither Jenkins[1] seems to have noticed. Worse, one of them seems to have kicked off a build at roughly halfway between then and now, but it does not list my commit as its reason for existing. Snif! What is going on? — Syd “I’ve been ghosted by a CI server!” Bauman [1] https://jenkins.tei-c.org/view/TEI%20dev/ https://jenkins2.tei-c.org/view/Dev%20branch%20jobs/

2 1

Re: [Tei-council] Next Stylesheets meeting
by BERMUDEZ SABEL Helena 09 Feb '21

09 Feb '21

Hello! No issues with the proposed date. Best, H. Helena Bermúdez Sabel Chercheuse FNS senior Institut des sciences du langage Université de Neuchâtel ________________________________ 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: 08 February 2021 18:08:07 To: tei-council(a)lists.tei-c.org; Martin Holmes; Nicholas Cole Subject: [Tei-council] Next Stylesheets meeting Dear all, The next Stylesheets meeting is scheduled for February 25, the day of our release. I propose to postpone the meeting to March 4. Please let me know if this works for you. Best, Martina

6 5

PDF build with Japanese
by Martin Holmes 08 Feb '21

08 Feb '21

Hi all, The ruby stuff is now merged into the repo, and I've spent a good few hours now trying to get the PDF to build properly. It dies with this error: ! LaTeX3 Error: The key 'fontspec-opentype/...' is unknown and is being (LaTeX3) ignored. which is something to do with xml:lang='ja' appearing in the source. At one point I got it to build, but without the Japanese language attributes, the characters just come out as square boxes. Can anyone who knows more about LaTeX than me suggest anything? I don't really want to go round removing xml:lang attributes just to get past the PDF problem, but I don't know what else to do at this point. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

4 8

Next Council call: Feb 11
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '21

08 Feb '21

Dear all, This is the preliminary agenda for our next Council call on February 11 at 11am-12:30pm PST/2pm-3:30pm EST/7pm-8:30pm GMT/8pm-9:30pm CET: https://docs.google.com/document/d/1mnUQtzMFTpPfUwoBQX2yo4g_sWeBrHBG4Z2myRK… The zoom link is in the google doc. Best, Martina

2 1

Next Stylesheets meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '21

08 Feb '21

Dear all, The next Stylesheets meeting is scheduled for February 25, the day of our release. I propose to postpone the meeting to March 4. Please let me know if this works for you. Best, Martina

1 0

Refrigeration
by Scholger, Martina (martina.scholger＠uni-graz.at) 08 Feb '21

08 Feb '21

Dear all, We are close to refrigeration, starting on Friday, February 12. After this date we should not commit major changes to the schema. Minor changes like improvements in wording, correction of typos etc. are fine. Please have a look at the open milestone 4.2.0 Guidelines issues (https://github.com/TEIC/TEI/issues?q=is%3Aissue+milestone%3A%22Guidelines+4…) and 7.51.0 Stylesheets issues https://github.com/TEIC/Stylesheets/issues?q=is%3Aopen+is%3Aissue+milestone…. Please remove issues that you will not tackle before the next release. Best, Martina

1 0

positioning of examples vis-a-vis prose
by Bauman, Syd 08 Feb '21

08 Feb '21

Working on ruby glosses, I think it is quite useful to say in the prose of CO things like “the following example” or “the example above”. I note that the “Examples” subsection of the “Style Notes” section of TCW 20<https://teic.github.io/TCW/tcw20.html> (why don’t these <div>s have IDs?) says in the very first paragraph not to do that. However, it is clear to me that the rest of that paragraph is about examples in tagdocs, not examples in the prose of the Guidelines. Furthermore, I think the logic (someone might come along later and add an example) at best does not really apply here in the prose (where being able to differentiate examples is useful), and at worst is basically silly. (I very vaguely remember the argument in favor of this restriction, and begrudgingly agreeing to it; but I cannot find the reasoning that led me to that agreement now, nor can I recall if it was intended for only tagdocs or for examples in the prose, too :-) That said, why don’t we have a mechanism for referring to specific examples?

4 3

Re: [Tei-council] More NVDL issues: Spec files not validating
by Bauman, Syd 05 Feb '21

05 Feb '21

Trying to validate which schema file against which schema? ________________________________ Just trying to validate the schema itself in oXygen.

3 10

Thanks for Ruby feedback
by Martin Holmes 04 Feb '21

04 Feb '21

Hi all, Thanks for the feedback on the location for the Ruby prose. The consensus is clear -- it should be in core -- and the comments suggest that the most appropriate approach will be to integrated it with the content relating to glosses, which is currently in 3.3.4, "Terms, Glosses, Equivalents, and Descriptions". That sub-subsection is already quite long, so what I propose to attempt is this: Take 3.3.4 "Terms, Glosses, Equivalents, and Descriptions" and 3.3.5 "Some Further Examples" and make them into a new subsection (i.e. one level higher), which will become 3.4. Title the new section "Terms, Glosses, Equivalents, Descriptions, and Ruby". (JJ suggests that terms belongs elsewhere, but that would be a major reorg, and I don't think we have time for that right now.) Create subsections: 3.4.1 "Terms and Glosses" covering the first part of what is now 3.3.4. This would also include the "Further Examples" bit, which is really an extension of this. 3.4.2 "Ruby Annotations" containing the new prose already proposed. 3.4.3 "Equivalents and Descriptions" containing the part of what is now 3.3.4 which discusses altIdent, desc, and equiv; I think this is a different topic, really, from glossing terms. I'm doing this work in a separate branch: <https://github.com/TEIC/TEI/tree/issue-2054-ruby> which I'll merge dev into steadily as I go, to minimize later merge conflicts. I'll also set up a build job for this branch on my Jenkins when the initial work is done. The time is relatively short, but I think we can get there before the freeze. I'll post the meat of this on the ticket too, for the record. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

3 10

More NVDL issues: Spec files not validating
by Martin Holmes 03 Feb '21

03 Feb '21

Hi all, Our Spec files (P5/Source/Specs/*.xml) all link to the NVDL schema here: <http://jenkins.tei-c.org/job/TEIP5-dev/lastSuccessfulBuild/artifact/P5/rele…> That generates an error in itself, because the Jenkins server gives a 308 Permanent Redirect to https. But if you do retrieve the schema and try to validate with it in Oxygen, you get (or at least, I get) the error: IllegalStateException - getSchemaProperties requires a schema I'm not sure why that is -- anybody know? It makes it a bit difficult to work on Spec files. What are people doing to validate their Spec files at the moment? Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

4 3

Next short VF2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Feb '21

03 Feb '21

Dear all, During the VF2F meeting this weekend, we agreed to do more short virtual F2F meetings as long as we can't do in-person meetings. Please fill in the doodle for our next short VF2F meeting (end of March / April): https://doodle.com/poll/dc68qph9py96w39f?utm_source=poll&utm_medium=link. The procedure is the same as last time: the North American Group starts on Friday, the European Group continues on Saturday morning and the full Council meets in the "afternoon" (morning for PST and EST). Best, Martina

1 0

issue 2010: <persPronoun>
by Bauman, Syd 02 Feb '21

02 Feb '21

Meg and I plan to finish up work on ticket #2010 on Mon evening 08 Feb (ET), and create a PR at that time. We are hoping it can be reviewed before the Council meeting on Thu 11 Feb. (If you don’t want to wait, see branch megjbrownIssue2010.)

1 0

Jenkins builds failing and not failing
by Martin Holmes 01 Feb '21

01 Feb '21

Hi all, If you look at Peter's Jenkins, you'll see that the TEI-P5-Test-dev job appears to succeed (it's green). However, the console log for the latest build (653) shows 14 errors: <https://jenkins.tei-c.org/job/TEIP5-Test-dev/653/parsed_console/> On my Jenkins, the latest build (547) also fails, but differently: <https://jenkins2.tei-c.org/job/TEIP5-Test-dev/547/parsed_console/> I'm going to try to figure out why my build is failing, but I'm even more puzzled by the main Jenkins, which seems to be giving the impression that all is well. Peter, do you know what's happening here? NVDL errors seem to be ignored. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

4 12

Council votes on Ruby in the Guidelines
by Martin Holmes 01 Feb '21

01 Feb '21

HI all, As Elisa points out, Council can't vote on the original ticket because it's not on the main TEI repo, so I've reposted it here: <https://github.com/TEIC/TEI/issues/2054#issuecomment-770934282> Please record your preferences for the location of the Ruby introductory prose and other mentions/pointers to it. I'll also check Slack where there's another poll under way. Doesn't matter which one you use. Cheers, Martin -- ------------------------------------- Humanities Computing and Media Centre University of Victoria mholmes(a)uvic.ca

1 0

Will miss the afternoon meeting
by Peter Stadler 30 Jan '21

30 Jan '21

Friends, I’m sorry but I have to apologise for the afternoon meeting. My wife got an appointment she can’t miss and I have to look after the kids. Just wanted to let you know that I’ll miss your (virtual) company and to wish you a productive discussion! Best Peter

1 0

TEI Council VF2F North America
by Hugh Cayless 29 Jan '21

29 Jan '21

Hugh Cayless, Ph.D. is inviting you to a scheduled Zoom meeting. Topic: TEI Council VF2F North America Time: Jan 29, 2021 03:00 PM Eastern Time (US and Canada) Join Zoom Meeting https://duke.zoom.us/j/8407352885 Meeting ID: 840 735 2885 One tap mobile +13126266799,,8407352885# US (Chicago) +16468769923,,8407352885# US (New York) Dial by your location +1 312 626 6799 US (Chicago) +1 646 876 9923 US (New York) +1 301 715 8592 US (Washington DC) +1 669 900 6833 US (San Jose) +1 253 215 8782 US (Tacoma) +1 346 248 7799 US (Houston) +1 408 638 0968 US (San Jose) Meeting ID: 840 735 2885 Find your local number: https://duke.zoom.us/u/abQMVai96I Join by SIP 8407352885(a)zoomcrc.com Join by H.323 162.255.37.11 (US West) 162.255.36.11 (US East) 115.114.131.7 (India Mumbai) 115.114.115.7 (India Hyderabad) 213.19.144.110 (Amsterdam Netherlands) 213.244.140.110 (Germany) 103.122.166.55 (Australia) 149.137.40.110 (Singapore) 64.211.144.160 (Brazil) 69.174.57.160 (Canada) 207.226.132.110 (Japan) Meeting ID: 840 735 2885

1 0

VF2F meeting: Jan 29 and 30
by Scholger, Martina (martina.scholger＠uni-graz.at) 28 Jan '21

28 Jan '21

Dear all, This is the agenda for our VF2F meeting: https://docs.google.com/document/d/1ditQHz4VXEitKZ7IeWO41tgzKZq_LwF0zclXHJF… I think that we first should work on pull requests (with milestone 4.2.0) and Guidelines issues with the milestone "Guidelines 4.2.0" which are still labeled with "Needs Discussion+Go" or do not have a status yet. For the North American Group - please start with whatever you like and fix issues from either or both of the tables. On Saturday the European group will continue. In the full Council session on Saturday we start with the discussion on ruby glosses. Please have a look at the issue and Martin's proposal on prose. Please feel free to add topics that you would like to discuss. Hugh will send a zoom link for tomorrow's meeting. Best, Martina

1 0