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

Next Stylesheets meeting: September 24th
by Helena Bermúdez Sabel 22 Sep '24

22 Sep '24

Dear all, According to the results of the poll, there aren’t any slots in which we are all available for 1h30, so let’s have 1h-long meetings on the last Tuesday of every month at 9am PDT / 12pm EDT / 4pm UTC / 6pm CEST. Thus, the next Stylesheets meeting will take place on September 24th. Please add any topics and/or issues you want to tackle to the agenda (I will be completing it soon): https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp… Best, Helena

1 0

Stylesheets meeting today
by Helena Bermúdez Sabel 26 Aug '24

26 Aug '24

Dear all, The next Stylesheets meeting will take place today (August 26) at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. Please add any topics and/or issues you want to tackle to the agenda: https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp… Best, Helena

1 0

Reminder: TEI Council Monthly Call on Tuesday, August 13
by Elisa Beshero-Bondar 12 Aug '24

12 Aug '24

Dear Council, A reminder that we plan for our monthly Council call this August on Tuesday, August 13 at 10:00–11:30 PDT 13:00–14:30 EDT 17:00–18:30 UTC 19:00–20:30 CEST Zoom: https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1 This is an unusual date that we agreed on because so many of us were unavailable last week for the big DH 2024 conference in Washington, DC, and I’m going to be traveling to another conference later this week.) I’ll send our Google Doc soon with an agenda, but just wanted to remind you all of the weird date/time. Hope you can make it! Among other things we need to sort out is dates for our September, November, and December council meetings just before and after the Buenos Aires F2F! Cheers, Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

2 1

Reminder: Council Meeting Wed. July 10!
by Elisa Beshero-Bondar 09 Jul '24

09 Jul '24

Hi Council! Just a quick reminder that we scheduled a meeting tomorrow to follow up on our happily successful release of the Guidelines/Stylesheets. We've invited Hugh to join us (thanks, Hugh!) so we can talk about changes to processing the Guidelines and perhaps an incremental release to correspond with the new website launch. Meeting time: 10:00am PDT / 1:00pm EDT / 5:00pm UTC / 7:00pm CEST Agenda + Zoom link <https://docs.google.com/document/d/1lgrFBqvw-n9j7XDGE0hzvhTVU41XzT9UNjU2dVf…> Please update the agenda with anything we need to discuss! I've added several tickets that we nearly closed but didn't in time for the release that I think we can probably dispatch quickly... Thanks, everyone! See you soon! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

Freeze is lifted
by Helena Bermúdez Sabel 08 Jul '24

08 Jul '24

Dear all, We have successfully finished the release (thanks to Hugh Cayless and his assistance with some permission issues). This means that you can no push to dev. Best, The Release Technicians

1 0

Freeze on release branch
by Helena Bermúdez Sabel 08 Jul '24

08 Jul '24

Dear all, The release branches are now frozen: please do not push any changes. Best, The release technicians

1 0

Freeze announcement
by Helena Bermúdez Sabel 06 Jul '24

06 Jul '24

Dear all, We are officially in freeze: Please do not commit any changes to the dev branches until the release is finished. Best, H.

1 0

victims of version vagueness
by Bauman, Syd 25 Jun '24

25 Jun '24

I started working on the teidata.version = teidata.version.unicode | teidata.version.semver | teidata.version.calver | teidata.whatever system today. (In a branch I have not committed, let alone pushed.) Less than halfway through the process I ran into a (moderately embarrassing) problem. It turns out calVer<https://calver.org/> is not a calendar-based version numbering system as we had assumed during our recent discussions. It is rather a cheerleading document in favor of calendar-based versioning in general, with both a breakdown of the potential components such a version number might use, and a list of specific projects that use a calendar-based version numbering system (along with the pattern of aforementioned components that project uses). My first reaction is I have no idea what we should do about this. My second reaction is I can easily scope out a range of options, as follows. 1. Do nothing with calVer — drop it from the list of TEI datatypes-to-be. 2. Go whole-hog: For every system described by calVer, create a TEI datatype that validates it. E.g., the datatype for the Ubuntu system would be defined with something like <dataRef name="token" restriction="([4-9]|[1-9][0-9]|[1-9][0-9][0-9])\.(0[[0-9]|1[0-2])(\.[0-9]+)?"/> Datatypes could be named flatly, e.g. teidata.version.ubuntu, or could be named hierarchicly, e.g. teidata.version.calendar.ubuntu. 3. Something in between. (E.g., calVer divides systems into case studies, notables, and others; maybe do #2 but only for the case study ones.) I really don’t like #1, because, in general, this is a great way to do version numbering. I encourage everyone to scan the major portions of the calVer document, if not read the whole thing.

2 1

Next Stylesheets Meeting: June 24
by Helena Bermúdez Sabel 21 Jun '24

21 Jun '24

Dear all, The next Stylesheets meeting will take place on June 24th at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. We will focus on the upcoming release, so if there is anything that you think needs to be tackled/discussed, please add it to the agenda: https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp… Best, Helena

1 0

Next Stylesheets Meeting (about testing infrastucture)
by Helena Bermúdez Sabel 24 May '24

24 May '24

Dear all, The next Stylesheets meeting will take place on May 27th at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. Peter Stadler has kindly accepted to take the lead in this meeting, and do an overview of our testing infrastructure. Best, Helena

1 0

May Council Meeting changed to May 15, Buenos Aires travel doc
by Elisa Beshero-Bondar 08 May '24

08 May '24

Dear Council members, The Council meeting we’d planned for this Friday May 10 is now postponed to Wednesday May 15 at a new time: - 10:30am - noon Pacific time (Joey) - 1:30 - 3pm Eastern Time (Syd, Raff, Elisa) - 7:30 - 9pm CET (Sabine, Martina, Torsten, et al) It will be the usual Zoom link: https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1lweWYzS2xZd2dqYVZpdz09 (Password: tei) I've also started a very rough Google Doc <https://docs.google.com/document/d/1EVwA5vbreWLUeyWJU286g43t4XKkIm2otkjjrtK…> to assist our travel planning to Buenos Aires. We're awaiting details on the locations of Council's meetings, but I think we'll have that very soon. Traditionally, Council members share arrival times / flight numbers (etc) here so we can look out for each other and try to meet at airports / stations as we arrive and depart. Please feel free to begin sharing your information here. We also have started using two new channels in Slack: * #f2f-planning * #tei-conference (where Torsten has begun discussing travel plans) One more thing! We need to determine dates for summer monthly meetings ahead of our trip to Buenos Aires, so please be thinking of good times of day and dates for our one 90-minute meeting per month. See you soon, and many thanks for all you do for the TEI! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

CMC-SIG repo now a TEIC branch
by Bauman, Syd 15 Mar '24

15 Mar '24

I have created a new branch in the TEIC/TEI repo called “cmc”. It is a squashed fork of the TEI-CMC-SIG/TEI branch “cmc-features”. What this means (presuming I have done this right) is that most, if not all, further work on the new CMC chapter should be performed in the new branch. Harald and Michael do not have write access to that branch (I don’t think), so if they wish to commit a change they may have to either make a requests of someone who does, or commit to their TEI-CMC-SIG/TEI, in which case we would need to merge. Because there have been some updates to other parts of P5 (although none to CMC itself) in the past few weeks, I have generated new outputs (see below). In addition, Jenkins maintainers may want to make jobs for building the TEI cmc branch against the Stylesheets dev branch. * Guidelines: https://bauman.zapto.org/~syd/temp/CMC/Guidelines-web/en/html/index.html * Exemplars: https://bauman.zapto.org/~syd/temp/CMC/Exemplars/

1 0

Agenda for VF2F Fri 3/15 - Sat 3/16
by Elisa Beshero-Bondar 13 Mar '24

13 Mar '24

Dear Council, Here is a draft agenda for our VF2F this weekend <https://docs.google.com/document/d/1DeLuEw8p_ZVD9AM8HXX1-a3G9ycQXFsD-u6JD9t…>! Timing and Zoom link to access the VF2F are in the Google Doc. I've also posted the agenda in our Slack (to circulate at 8am EDT today!) Please feel free to add tickets or discussion items for the full Council session, or to prioritize particular tickets and issues that you want to make sure we address sooner rather than later! Also, please make sure I haven’t made timing mistakes for the meeting. Thanks, each of you, for making time for this important work session for Council! For those of you who can't join us, you'll still see lots of activity on the GitHub repos and in Slack, and I hope this VF2F gets us all moving productively on tickets and big issues, rolling toward our next release! Cheers, Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

TEI Council Upcoming VF2Fs, Modified Meeting schedule
by Elisa Beshero-Bondar 01 Mar '24

01 Mar '24

Greetings, TEI Council! We have a short virtual face-to-face (VF2F) meeting coming up on March 15/16. I'm traveling next week and won't be in a reliable place for internet the day of our scheduled Council call of March 8. I also think we don't really need this meeting with the VF2F. We need to work on our VF2F agenda, so I'll try to get a start on that and share it with the group for modification over the next couple of weeks. So let's cancel the meeting of March 8. If you'd like to use that 90 minutes this Friday to get together and work on a dedicated task or ticket, feel free to use my Council meeting Zoom at https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1lweWYzS2xZd2dqYVZpdz09 I shall simply remove that March 8 meeting from our calendar. Cheers and see you in the middle of March! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

Stylesheets meeting: change of date
by Helena Bermúdez Sabel 01 Mar '24

01 Mar '24

Dear all, We were meant to meet next Friday (March 23rd). However, I won't be able to chair the meeting this coming week, so I propose meeting on March 1st instead. If there is a preference for keeping the original date, maybe someone else can volunteer to chair the meeting? Apologies for this change. I will send the agenda in the following days. Best, Helena

5 6

monthly ticket triage
by Bauman, Syd 01 Mar '24

01 Mar '24

I performed ticket triage this morning. All issues and pull requests in the TEI and Stylesheets repos that are < 2 years old now have assignees except the Stylesheets issue I opened yesterday (Documentation file teixsl.xml needs updating #665<https://github.com/TEIC/Stylesheets/issues/665>). This issue could be a pretty sizeable task, since that document has not had any significant updates since 2015. That said, it is not huge: the document is only a bit over 2,500 words long. It has 6 or 7 major divisions and some 45 paragraphs. In principle I do not mind doing this myself. But my plate is already pretty full. Maybe we could divide and conquer, or maybe someone who wants to review how the Stylesheets work (for users) just wants to take it on?

2 1

ATOP TF down one
by Bauman, Syd 08 Feb '24

08 Feb '24

Dear Council — I write to you with the concerning news that David Maus has decided to resign from the ATOP task force. I call this “concerning” rather than “sad” news because although it is sad for us (the remaining members) to lose David whom we both like and like working with, and sad for us (the TEI) to lose such an incredible talent, it is not really sad in the sense that David is not leaving for some horrible reason like he has decided that the digital humanities is a waste of time. Rather, David has decided to stop working on ATOP for reasons that I think we should be concerned about. The main reason for David’s departure is that he no longer believes that the task of writing an ODD processor is a feasible one. He spent some significant time and effort working on ATOP over the holiday break. While he made some progress, the chief result of his labors was frustration with the poor quality of the specification of ODD, namely the TEI Guidelines, specifically chapter 22, Documentation Elements<https://tei-c.org/Vault/P5/4.7.0/doc/tei-p5-doc/en/html/TD.html>. He believes that the poor quality of the specification makes a proper implementation impossible.[1] David also has a sense of frustration with TEI as an organization. The TEI Board has not gotten back to him on a potential collaboration, and it is taking us (the TEI Council) months and months to address some of the issues he has raised. While I share David’s frustration with the sluggishness of progress in the TEI-C, I also recognize that the work is being done by volunteers with real jobs. So I see both sides of this coin. Lastly, and in some sense most importantly, David just is not having fun doing ATOP work anymore. The good news is that David is still willing to help as an occasional as-needed consultant, and to pitch in with the jTEI publications we have already committed to. Furthermore, I am confident David will still be available as a resource to TEI when thorny Schematron issues come up. (He is one of the leading experts on Schematron, having written what many consider the premier Schematron processor in the world: SchXslt<https://schxslt.github.io/schxslt/>, which I call mausatron.) I do not intend to try to replace David immediately. The ATOP task force will work with just the three of us for a few months first, and then we will discuss as a group whether we want to expand or not. Note [1] He may well be right. While the remaining members of the task force do not currently share this belief, we do all believe we might very well agree with him after diving further into the nitty-gritty details of the ODD specification. We are actually somewhat worried that after a few more meetings we may also be throwing our arms up in despair.

2 1

CMC time!
by Bauman, Syd 02 Feb '24

02 Feb '24

[Note to Jessica, Harald, and Michael — If you try replying to this message it may be rejected by the list. If that happens (and I get a copy) I can post it for you.] I think it is time to move work on CMC from the small subgroup (me, Peter Stadler, Harald Lüngen, and Michael Beißwenger) to Council as a whole (still with input from Peter, Harald, and Michael, and hopefully from Jessica Lu as well). I hope that we can discuss the new chapter at our meeting 1 week from today. The goal, of course, is to incorporate the new CMC chapter and module into the Guidelines with due haste.[1] With that in mind, I am hoping everyone will at least read the chapter (it is not particularly long — less than 6,800 words), if not also try to encode some CMC with it, before we meet. Resources: * The ticket<https://github.com/TEIC/TEI/issues/1955> * The fork of P5<https://github.com/TEI-CMC-SIG/TEI> that we have been working in * The cmc-features branch of that fork<https://github.com/TEI-CMC-SIG/TEI/tree/cmc-features> is the one we have been using * The Jenkins job<https://jenkins.tei-c.org/job/TEIP5-CMC-features/> Peter set up for that branch * The last HTML Guidelines<https://jenkins.tei-c.org/job/TEIP5-CMC-features/lastSuccessfulBuild/artifa…> that job successfully built (chapter 9<https://jenkins.tei-c.org/job/TEIP5-CMC-features/lastSuccessfulBuild/artifa…> is the new chapter) * The last PDF Guidelines<https://jenkins.tei-c.org/job/TEIP5-CMC-features/lastSuccessfulBuild/artifa…> that job successfully built * The last tei_all closed (.rnc) schema<https://jenkins.tei-c.org/job/TEIP5-CMC-features/> that job successfully built * The last tei_all open (.isosch) schema<https://jenkins.tei-c.org/job/TEIP5-CMC-features/lastSuccessfulBuild/artifa…> that job successfully built * The last HTML Guidelines<https://bauman.zapto.org/~syd/temp/CMC/Guidelines-web/en/html/index.html> I built locally (chapter 9<https://bauman.zapto.org/~syd/temp/CMC/Guidelines-web/en/html/CMC.html> is the new chapter) * The last set of Exemplars<https://bauman.zapto.org/~syd/temp/CMC/Exemplars/> I built locally (includes RELAX NG and Schematron) There are several known problems: * Internal references: TEI issue #2332<https://github.com/TEIC/TEI/issues/2332> * The first figure needs to be scaled (it looks bad in HTML, awful in PDF) * PDF output: * Headings are in an ugly monospaced typeface (this is not unique to CMC) * Inline monospaced bits are way too big (this is not unique to CMC) * Stylesheets issue #661<https://github.com/TEIC/Stylesheets/issues/661>. * The ultimate section should list classes defined, in addition to elements and macros. Also my somewhat out-of-date spell checker flags lots of problems, many of which I think are OK. The majority are compound words that it claims should be separate words or hyphenated. I think all of the following are correct as is, except where noted. * “multimodal” * “audiovideo” — I think these should be “audiovisual” * “coworking” — I am not sure the word is used correctly, but I think it is spelled correctly * “kinesic” * “macrostructure” and “microstructure” * “logfile” * “webpage” — I think this would be better as “web page” * “interactants” * “anonymize” and “anonymisation” — I think these are correct as is, but we should be consistent * “reconstructible” — I am not confident about this one * “tokenisation” * “substring” * “pseudonymised” and “pseudonymisation” Note [1] I am not exactly sure how we go about merging the forked branch into our repo, but figure that detail is not particularly important right now, and we can discuss that at this or a later meeting. I have merged the TEIC/TEI dev branch into the TEI-CMC-SIG/TEI cmc-features branch recently (yesterday, I think).

1 0

Next Stylesheets meeting: Friday January 26
by Helena Bermúdez Sabel 25 Jan '24

25 Jan '24

Dear all, The next Stylesheets meeting will take place on January 26th at 6:30am PST / 9:30am EST / 2:30pm UTC / 3:30pm CET. Here you have the suggested agenda <https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp…>, but please don’t hesitate to add other tickets or discussion topics. Best, Helena

2 1

GitHub Sponsors
by Hugh Cayless 02 Jan '24

02 Jan '24

Hi All, I’ve no idea of anything will come of it, but I’m signing the TEIC up for GitHub Sponsors. You may see emails related to it because the Council email is the default organizational email on GitHub. All the best, Hugh

1 0

Next Stylesheets meeting: Friday January 5th
by Helena Bermúdez Sabel 02 Jan '24

02 Jan '24

Dear all, The Stylesheets meeting of December 2023 will take place on January 5th in the same time slot for Council meetings: 6:30am PST / 9:30am EST / 2:30pm UTC / 3:30pm CET. Here you have the suggested agenda <https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, but please don’t hesitate to add other tickets or discussion topics. Best, Helena

1 0

Happy New Year! 2024 Council Monthly Meetings
by Elisa Beshero-Bondar 02 Jan '24

02 Jan '24

Happy New Year, Council! Thanks, each of you, for responding to the calendar poll to help us arrange our meetings these next several months. We have a very clear moment of collective alignment. Council will be meeting on the same schedule as last year, that is on *Fridays at 6:30am PST / 9:30am EST / 2:30pm UTC / 3:30pm CET* . We'll stick with this schedule for Council meetings until any of us needs to make a change. Meetings are 90 minutes long. Holding our pattern of regularly meeting in the 2nd full week of the month, that means our first meeting of 2024 will be on *Friday January 12 over Zoom*. I've updated our schedule on the TEI Google Calendar, and will send out a draft agenda with the Zoom link via Slack as usual. Cheers, Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

1 0

Next Stylesheets meeting: November 30
by Helena Bermúdez Sabel 28 Nov '23

28 Nov '23

Dear all, The next Stylesheets meeting is scheduled for November 30 at at 19:00Z (11:00 PST, 14:00 EST, 20:00 CET). My proposal <https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…> for the next meeting is to start the work on our test suite (unless the general opinion is that a specific group should take care of this task and thus we should do something else during the Stylesheets Group meeting). Best, H.

1 0

Last Council Meeting of 2023: Moved to Friday December 15
by Elisa Beshero-Bondar 28 Nov '23

28 Nov '23

Dear TEI Council, As discussed on Slack, I've had to reschedule our last Council meeting of the year 2023 to one week later: *Friday December 15*. From our Slack discussion that should work for most of us, at the same times as usual (at 6:30am PST / 9:30am EST / 2:30pm UTC / 3:30pm CET), same Zoom link we've circulated in past minutes. We have some new topics "brewing" for the Council call connected to the November release. We'll also try to do some "calendaring" with some new polls to watch for on Slack and here to 1. Make sure we have a good meeting time for everyone in 2024, and 2. Sort out when to hold our virtual F2F sessions this spring. Cheers and more soon! Elisa -- Elisa Beshero-Bondar, PhD TEI Technical Council Chair Program Chair of Digital Media, Arts, and Technology | Professor of Digital Humanities | Director of the Digital Humanities Lab at Penn State Erie, The Behrend College Development site: https://newtfire.org

2 1

time to fix, retire, or kill Test/
by Bauman, Syd 26 Oct '23

26 Oct '23

Trish & I are doing the p5subset → Stylesheets process. Most of our time has been spent handling Test/. I think it is just too cumbersome — the amount of time we (Council, collectively) spend wrangling with Test/ is likely by now much greater than the amount of time it saves by catching bugs early. I think we need to do one of three things, toot sweet: 1. Re-work the Test/Makefile so that the process is much easier: e.g., when comparisons are deferred, a shell script to perform them needs to be generated; this might be hard to impossible. 2. Stop using Test/, it is just not helpful enough to be worth it. Leave the directory in the repo so that we can use it when there is a particularly gnarly case, or when a human is not waiting for it, but remove it from the general test procedure we use, e.g. when generating p5subset for the Stylesheets repo. 3. Remove Test/ from the repo (and various instructions) entirely (and rename Test2/ to Test/ :-) My vote is for (2). I could be perhaps be talked into (3) reasonably easily; it would take some serious convincing to get me to vote for (1). P.S. BTW, Martin & I intended that we would do (3) when we developed Test2/. (I wanted to hang onto Test/, i.e. do (2), for awhile to ensure that everything tested by Test/ was also tested by Test2/.)

7 11