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

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

09 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 26 Jan '24

26 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

Next Stylesheets meeting: October 26
by Helena Bermúdez Sabel 22 Oct '23

22 Oct '23

Dear all, The next Stylesheets meeting is scheduled for October 26 at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). I think we should dedicate some minutes to discuss the future of Test, and then focus on the priorities before the next release: if there is a ticket that you want to see discussed in time before the release, please add it to the agenda! H.

1 0