February 2024 - Tei-council

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 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