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

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

Next Stylesheets meeting: September 28
by Helena Bermúdez Sabel 22 Sep '23

22 Sep '23

Dear all, The next Stylesheets meeting is scheduled for September 28 at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). Here you have the suggested agenda <https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, and as always, do not hesitate to add other topics/tickets to discuss. Best, H.

1 0

A little update
by Elli Bleeker 07 Sep '23

07 Sep '23

Dear council members, First of all, I hope you're thoroughly enjoying the conference in Paderborn! I wanted to write to you with a quick update on my situation (as far as Elisa hasn't already filled you in). The past months have been, well, hard work, but I'm happy to report all is well with our new little family. The twins were born on March 17, two months too soon, and we had to stay in the hospital for three weeks, but since taking them home they've been doing great. Enclosed a picture for those interested. Still, it's been quite demanding to take care of newborn twins (who would've thought?) and so far I haven't had a chance to recover from the burn-out symptoms I experienced right before (and during) my pregnancy. So when Elisa wrote to me proposing I extend my leave from Council, thus not only giving me some more time to recover but also giving someone else the chance to experience Council for a year, I considered it a good solution. I was indeed very happy to hear that Joey has been a wonderful addition to Council and I'm glad this solution worked out so well. This is not to say I miss you very much and I wish I could be there in Paderborn with you. Starting this week, the twins are going to daycare, giving me some much needed time to rest and get better. For now, I wish you an interesting, productive and overall great conference and members meeting. All best, Elli [image: image.png]

4 3

Fwd: Mailing List Change of Address
by Elisa Beshero-Bondar 04 Sep '23

04 Sep '23

Council: I'm forwarding this e-mail exchange recently with Martin Mueller who has some ideas for us to get more involved with university libraries. Elisa ---------- Forwarded message --------- From: Elisa Beshero-Bondar <ebbondar(a)gmail.com> Date: Sun, Sep 3, 2023 at 11:28 PM Subject: Re: Mailing List Change of Address To: Martin Mueller <martinmueller(a)northwestern.edu> Hi Martin, Thanks for your thoughtful messages, including the one about what we're currently calling "New Light" or "Lite 2" in Council. (You'll have more to read as we get our minutes posted--it's turning into a fascinating conceptual project.) Some of our discussion has been about studying how librarians understand metadata (including those who don't use the TEI very much) in order to put forward a streamlined version of the teiHeader, I will say that Penn State's IT are good generous people, and Listserv a remarkably robust and well-maintained software used by many universities in the US--and the transfer work was entirely pleasant and remarkably easy as a result. Libraries had little to do with that development in particular. Curriculum is another matter--I agree that it would be lovely to connect the Big Ten with TEI, but I suspect the real bottleneck is faculty teaching undergraduates. Some of us do, but we're a patchy network I think. Markup theory and practice needs to be taught to more grad students for this to catch on as canonical in curricula, but I think it certainly does teach remarkably well and appeals to students for what you can make and build of it--as you say, a sort of "maker space." TCP is certainly an important project to celebrate for bringing institutions together with a common goal, and it certainly does make for a good starting point for discussions about TEI in academe. Cheers from Paderborn, Elisa On Sat, Sep 2, 2023 at 9:36 PM Martin Mueller < martinmueller(a)northwestern.edu> wrote: > Dear Elisa, > > > > This is promising news. I take it somewhere at Penn State there is an > institutional interest in the TEI and that you had something to do with it. > Penn State is part of the Big Ten. In the old days, when there were just > ten, the Big Ten Libraries formed a very productive alliance (called the > CIC), which among other things was responsible for the Text Creation > Partnership. Technically that was a collaboration between Michigan and > Oxford, but Michigan did the heavy lifting, and good deal of the money came > from CIC subscribing libraries. Mark Sandler, a Michigan librarian who > became the directory of the CIC Libraries initiative, negotiated the key > provision of the deal between Proquest and the TCP: that the text would > move into the public domain within five years of the completion of the > project. > > > > The TCP texts are arguably the most important and almost certainly the > largest collection of TEI-encoded texts. At one time the CIC libraries > provided significant financial support for the TEI. I haven’t seen a > budget report from the TEI, but to gather from the dwindling number of > institutional members and their average contributions, the budget must be > pretty shaky. I think there is a strong case to be made for the successor > of the CIC—the Big Ten Academic Alliance Library Initiatives—to take an > active cross-institutional interest in the TEI. What would be chump change > to them would be significant support for the TEI. > > > > I enclose with this email two longish documents. One is a talk that I > gave as the keynote address at the 2012 Chicago Colloquium on Digital > Humanities and Computer Science, where I sketched a model of distributed > editorial work that would actively engage undergraduates in the > collaborative curation of our cultural heritage. The other is a report to > the Mellon Foundation about a number of steps towards building such a model. > > > > I have sometimes toyed with the acronym CHOCK for Cultural Heritage Object > Construction Kit. The TEI provides a key tool—perhaps the key tool for > such a kit. “Maker spaces” across many campuses, helped by network > technologies, can be the sites for working gradually and in quite loosely > coordinated ways towards a common goal. > > > > You are an editor and should find this model attractive. If you can get > enough librarians and faculty in the Big Ten Alliance to see how and why > the TEI matters for undergraduate education, the long-term support for the > TEI would be on pretty sound footing. > > > > Best wishes > > > > MM > > > > > > > > > > > > *From: *TEI (Text Encoding Initiative) public discussion list < > TEI-L(a)LISTSERV.BROWN.EDU> on behalf of Elisa Beshero-Bondar < > ebbondar(a)GMAIL.COM> > *Date: *Saturday, September 2, 2023 at 4:24 AM > *To: *TEI-L(a)LISTSERV.BROWN.EDU <TEI-L(a)LISTSERV.BROWN.EDU> > *Subject: *Mailing List Change of Address > > Greetings, esteemed list members! > > This TEI community listserv, like several others hosted at Brown > University, is about to change its address to Penn State University. We > hope you don't notice any significant difference when that happens! You > will automatically remain subscribed to the same lists. Mail from the list > will be sent to you from a lists.psu.edu > <https://urldefense.com/v3/__http:/lists.psu.edu__;!!Dq0X2DkFhyF93HkjWTBQKhk…> > address instead of a listserv.brown.edu > <https://urldefense.com/v3/__http:/listserv.brown.edu__;!!Dq0X2DkFhyF93HkjWT…> > address. You will, for the foreseeable future, be able to send mail to the > list using either the old listserv.brown.edu > <https://urldefense.com/v3/__http:/listserv.brown.edu__;!!Dq0X2DkFhyF93HkjWT…> > or the new lists.psu.edu > <https://urldefense.com/v3/__http:/lists.psu.edu__;!!Dq0X2DkFhyF93HkjWTBQKhk…> > address. However, you will want to update your bookmarks to the listserv > archives to the new address as soon as the change has occurred, which will > be announced here. > > > > The big day for listserv transfer is scheduled on October 19, 2023, and it > will be a team operation between Brown and Penn State IT. > > Elli Mylonas will continue the day-to-day management of the listserv, with > assistance from myself and Syd Bauman. > > > > Please let us know if you have questions or concerns about the transfer > operations. We'll be discussing this at the Annual General Meeting in > Paderborn soon, so we can talk about it in person if you're there for the > TEI-MEC conference. > > > > Cheers, > > Elisa, with Elli and Syd > > -- > > Elisa Beshero-Bondar, PhD > > TEI Technical Council Chair and member of the TEI Infrastructure Group > > 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 > <https://urldefense.com/v3/__https:/newtfire.org/__;!!Dq0X2DkFhyF93HkjWTBQKh…> > > -- 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 -- 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

Fwd: More about TEI Lite
by Elisa Beshero-Bondar 04 Sep '23

04 Sep '23

Message from Martin Mueller to the TEI-L list, pertinent to our discussion of Lite 2. ---------- Forwarded message --------- From: Martin Mueller <martinmueller(a)northwestern.edu> Date: Mon, Aug 21, 2023 at 6:44 PM Subject: More about TEI Lite To: <TEI-L(a)listserv.brown.edu> I read through the minutes of the Technical Council that discussed my proposal to phase out simplePrint and merge it into a new version of TEI Lite that includes the Processing Model. I was pleased by the thoughtfulness of the discussion. Much of it was given over to naming the child, and I have a half-serious suggestion about that. Why not rechristen Lite and All TEI200 and TEI600? TEI-All has not quite 600 elements, and a revised TEI Lite falls short of 200. But the names give you a good sense of scale. TEI600 has a lot of elements, and TEI 200 has quite a few. The names get you out of implicit and confusing value judgements about what is ‘lite’ or ‘simple’. It may sound too much like F150 or C300, but that’s another matter, and some might like it for that reason. I disagree a little with the comment that “the phrasing of 90% of the needs of 90% of the community” is “outdated”. Pareto distributions and other power laws are pretty universal in their application. “90 % of the needs of 90% of the users” is an excellent version of the 80/20 rule. If anything, progress over the past quarter century may mean that the rule applies even more now than it did when it was used in the preface to the first version of TEI Lite. I remember working on a moderately complex project some twenty years ago. It was SGML rather than XML, and validation told you that things didn’t work without telling you much about the where or what of the errors. It’s a mystery to me now how I got it to work, though I did. Since then, the access costs to working with any kind of XML have dropped sharply, and folks with very little previous experience can “ramp up” quickly to doing useful work. If you belong to that category of users, it’s probably a good idea to ask yourself whether you can solve your encoding problem within a space of 200 elements rather than 600, not to speak of adding your own customization. That takes us back to the Nobel Prize behavioural economist Richard Thayer, who argued that in most walks of life people make better decisions if given a limited number of standard choices, as long as they can opt out. We all like to think that our projects are special, but typically they are not that special. A friend of mine told me that in Medical School he learned that “when you hear hooves behind you think horses not zebras”. Physicians like “interesting cases”. Patients not so much. This is good advice much of the time, and especially for groups like the Technical Council. Any such group is likely to have a preponderance of geeks, and geeks are more interested in exciting, new, and technically challenging things. Steven Pinker in his recent book on writing has a whole chapter on the problem that the hardest thing for a writer is to imagine what the reader does not know. Geeks share this problem, and groups like the Technical Council need to remind themselves constantly about the need to countersteer and focus on what most users do or need most of the time. Ben Shneiderman observed that good software should have “low thresholds and high ceilings”. From the bread-and-butter perspective of a thriving TEI enterprise, lowering the threshold should remain a key goal. I’m not much of a TEI expert, but I am an expert on the attitudes and anxieties of the key user community of people in English departments and their neighbours. Quite a few years Jerry McGann equipped about TEI as an acronym for *terra incognita. *Alas, the quip may still apply. The TEI has man virtues, but preaching beyond the choir is not one of them. It would be a good idea for the Technical Council to apply the 80/20 rule in such a way that 80% of the work is done on lowering the thresholds. TEI-Publisher, the happy child of the TEI Simple project, has done a lot of good work on that front. But even there much of the documentation is not as successful as it might be in keeping mind what the reader does not know. I have on occasions argued for the need of a “Small Catechism” to accompany the “Grand Catechism” of the TEI Guidelines—a magnificent document in some ways but not reader-friendly in others. The most useful part of the Guidelines is Appendix C1—the easiest and quickest way to figure out where an element may or may not occur. Since Appendix must be based on a program, it should be possible and not very expensive to create a version that Is populated only by the most frequently used elements (TEI 200 or whatever you call it. >From one perspective you don’t this: it doesn’t tell you what you can’t get from the full version. On the other hand, a TEI200 catalogue of elements and their behaviours would give novice users a much better sense of the TEI architecture. -- 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

Fwd: Ihre Reservierungsbestätigung / Im: Pader Café
by Peter Stadler 30 Aug '23

30 Aug '23

3 2

Meeting at Paderborn
by Peter Stadler 29 Aug '23

29 Aug '23

Dear all, it’s only a few days until your/our meeting at Paderborn and I thought it high time to send you some Information! Your meeting room for Sun–Tue will be F0.550 (the nicest room in the building!) which is located directly on the ground floor next to the entrance of the Heinz-Nixdorf-Insitute (HNI) [1]. Since room numbers are boring I labelled it <hni:egXML> – watch out for other tag names as room labels! The room is equipped with two large screens and a projector and allows connecting via HDMI or Airplay or some other Android thing I’m not familiar with. More rooms are available for break out sessions. All the pre-conference workshops (Mon-Tue) will be held at the HNI, too, so you will have to have regular breaks since the coffee break catering is located directly next to your room. For Sunday, I will bring some coffee, tea, and biscuits directly to your room. The lunch breaks on Mon/Tue will be at the cafeteria free of charge for all conference participants (I hope you are all registered for the conference?) On Sunday, I recommend to order some food because there’s not much around the HNI. A nice place might be the Pader Café, though, wich is a 10min walk away and should serve some food on Sundays according to [2]. Sunday evening you’re invited to my place (6:30pm, is that ok?) – I hope the weather will be fine and we can have a barbecue, so please let me know about your dietary restrictions and/or preferences! Please let me know if you need anything else! Looking forward to hosting you at Paderborn Peter [1] https://www.hni.uni-paderborn.de/service/raeume-im-gebaeude-f/besprechungsr… <https://www.hni.uni-paderborn.de/service/raeume-im-gebaeude-f/besprechungsr…> [2] https://www.pader.cafe <https://www.pader.cafe/>

6 10

Next Stylesheets meeting: August 24
by Helena Bermúdez Sabel 22 Aug '23

22 Aug '23

Dear all, The next Stylesheets meeting is scheduled for August 24 at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). Here you have the suggested agenda <https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, but please do not hesitate to add other things to discuss. During the last meeting, we ended up touching topics that were beyond the Stylesheets Group’s “jurisdiction.” I added these topics to the “Paderborn collection of topics”: I hope I wasn’t too late doing this @Elisa <ebbondar(a)gmail.com> Best, H.

1 0

Next Stylesheets meeting: July 27
by Helena Bermúdez Sabel 23 Jul '23

23 Jul '23

Dear all, The next Stylesheets meeting is scheduled for July at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). Here you have the suggested agenda <https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, but as always, do not hesitate to add other things to discuss. Best, H.

1 0

Rahtz Prize Committee interest?
by Elisa Beshero-Bondar 21 Jul '23

21 Jul '23

Greetings, Council! We need one representative from Council to serve on a little three-person committee to award the Rahtz Prize for TEI Ingenuity <https://tei-c.org/activities/rahtz-prize-for-tei-ingenuity/> for 2023: one from Council, one from Board, and one who won the award in a previous cycle. Apparently we have a proud tradition of always running late in the posted cycle--but we do need to get started quickly! I understand that the little committee needs to form and issue a call for applications, likely by early August and then start reviewing them to make a decision by the time of the TEI / MEC conference. This involves looking for applications, reviewing submissions and that we'll typically announce the winner at the TEI Conference in the Annual General Meeting. So long as you have not served on the committee 4 times already, you're eligible to represent Council. Are you interested in serving on the Rahtz committee to represent the Council? If so reply to this and let me know--probably in course of the next week--say before July 27, okay? I am willing to serve in this capacity but I wanted to ask the group first--I am also going to be crazy busy in August getting ready for my university classes (which start 21 August) and the Council F2F. I'd be super grateful for anyone with a more peaceful August schedule who is willing to serve on this committee! Thanks, 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 3

namespace declaration in examples
by Bauman, Syd 20 Jul '23

20 Jul '23

Magic removal time! OMG, I am so excited. But I have to prep slides for tomorrow, no time to do this now. Thus I am writing some notes here. See https://tei-c.org/Vault/P5/4.6.0/doc/tei-p5-doc/en/html/ref-TEI.html. Note that there is a proper namespace declaration in both examples. How the BLEEP did it get there? We cannot put a namespace declaration for the empty namespace on an element in an <eg:egXML> (unless it is on an element that has an explicit prefix), because its contents need to be in the eg: namespace. The answer is that there is magic in the Stylesheets.[1] Now take a look at https://www.wwp.neu.edu/outreach/seminars/miami_2023-07/presentations/manus…. The source for that slide uses <egMarkup>, an element that has the same kind of namespace specification restriction. So how did the namespace declaration get there? Simple. So simple I am annoyed at myself for not thinking of this long ago. In the source it is not a namespace declaration, it is an xmlns attribute in a namespace. Thus it makes it to the Stylesheet as an attribute node and can be processed like any other attribute. The special case in the stylesheet that processes that slide is simple, straightforward, and easy to document: “An attribute in the duck: namespace has its prefix stripped off before it is rendered in the output”. Note [1] Particularly in Stylesheets/common/verbatim.xsl, starting at roughly line 463.

2 1

Next Stylesheets meeting: June 22
by BERMUDEZ SABEL Helena 18 Jun '23

18 Jun '23

Dear all, The next Stylesheets meeting is scheduled for June 22 at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). Here you have the agenda<https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, which proposes continuing with the work on the presentation of attribute lists, since we are very close to closing that ticket. However, I am also happy to organise a different meeting just to tackle that ticket (because I recognise that having dedicated two different meetings to it is frustrating), and that way we can do something different in the next Stylesheets meeting. Best, H. <http://www.unine.ch/isla>

1 0

June 9 TEI Council Meeting and discussion of #2173
by Elisa Beshero-Bondar 07 Jun '23

07 Jun '23

Dear Council, Reminder: we are meeting this Friday June 6 at 6:30 - 8am PT | 9:30 - 11am ET | 2:30 - 4pm UTC | 3:30 - 5PM CET. Syd has asked that we take some time to review atop ticket #2173 <https://github.com/TEIC/TEI/issues/2173>, and it will definitely help if we can try to do that before the meeting starts. Would you please take a moment this week to review the ticket, and especially the ODD + Schematron files attached to it ahead of the meeting? Here is our agenda with the Zoom link <https://docs.google.com/document/d/1mmIrn5BX3VVmsKpQ-H8GG2UZ2-3JYZKSVhtd4q-…> (also posted on Slack). Please feel free to add to the agenda! Thanks, 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

Next Stylesheets meeting: May 25
by BERMUDEZ SABEL Helena 21 May '23

21 May '23

Dear all, The next Stylesheets meeting is scheduled for May 25 at at 18:00Z (11:00 PDT, 14:00 EDT, 20:00 CEST). Here you have the agenda<https://docs.google.com/document/d/11_l_MZ6M2lxhE2qtH6QUkZVxo0-OQrNgRhOnpaU…>, which proposes continuing with the work on attribute lists presentation. Best, H. [Université de Neuchâtel]<https://www.unine.ch/> Helena Bermúdez Sabel Post-doctorante FNS Institute des sciences du langage Université de Neuchâtel Rue Pierre-à-Mazel 7 CH-2000 Neuchâtel Tél. +41 32 718 16 21 www.unine.ch/isla<http://www.unine.ch/isla>

1 0

Re: [Tei-council] on the Takeda strategy and macro.msDescPart
by Elisa Beshero-Bondar 14 May '23

14 May '23

2 1

on the Takeda strategy and macro.msDescPart
by Bauman, Syd 14 May '23

14 May '23

We have not heard from Torsten Schaßan or anyone else from the MS-SIG on 2214<https://github.com/TEIC/TEI/issues/2214>. I am going to suggest that we take the following actions. * Politely decline his PR<https://github.com/TEIC/TEI/pull/2423> — that content model will not do what anyone wants. * Merge sydb_2214 in. Even if it is not exactly what the MS-SIG wants, it is a step in the right direction. * IF the MS-SIG wants <msPart> and <msFrag> to intermingle with the other four elements (<msContents>, <physDesc>, <history>, and <additional>) we should push back against the idea. I am not saying we should not do it under any circumstances, but I honestly believe we (the MS description workgroup back in 2005) designed that part of the content model because, as JC affirmed in Guelph, it makes sense that way; whereas I think we designed the part of the content model for those other four elements that way because it was easy on us. * Develop a written policy for application of the Takeda Strategy that says, essentially, at 2–4 particles we simply expand the desired structure in PureODD [see below for what that looks like but in RNC, not PureODD], but at 5+ particles we loosen the grammar-based content model (RELAX NG) and add further constraints with the rule-based schema (ISO Schematron). * Note: The above policy need not be applied to an <interleave> with only 1 particle, as that is exactly the same as that 1 particle without an <interleave>. 🙂 * This, of course, is applicable during the time period before we get <tei:interleave> working. (I think, BTW, that if we want to do this right the Stylesheets should generate proper DTD code, if possible, no matter how many particles there are. But that can be discussed later on the ticket(s) for <tei:interleave>.) Seems to me writing the PureODD for 1–3 is pretty easy, and we already have an example of doing so for 4, so copying & modifying it should not be hard. But 5 is essentially unmanageable, and I don’t even want to consider 6+. (Note, BTW, that speed is not a concern — jing validates against the 5-element version in < 0.1 s. I compared running 100 iterations of jing using the 4-element version and the 5-element version. The change in real time was 5.2 s to 6.5 s; the change in user time was 7.8 s to 8.8 s. That was using RNC, so each iteration had to convert the compact syntax to XML syntax first.) Here is what an interleaves of 2–5 elements looks like expanded to be usable by XML DTD language. (To see what 4 look like in PureODD see macro.msDescpart<https://github.com/TEIC/TEI/blob/sydb_2214/P5/Source/Specs/macro.msDescPart…> or the file I attached to a comment<https://github.com/TEIC/TEI/issues/2214#issuecomment-1268958396> on the ticket.) Note that when just a list of references to elements with parens, commas, and or bars like these, DTD syntax and RELAX NG Compact Syntax are the same. one As mentioned above, an interleave of one item is just that item: <rng:interleave> <rng:ref name="one"/> </rng:interleave> is the same as just ( one ) two <rng:interleave> <rng:ref name="one"/> <rng:ref name="two"/> </rng:interleave> is the same as ( one & two ) is the same as ( ( one, two ) | ( two, one ) ) Four particles, 3 pair parens, and three connectors instead of two particles, 1 pair parens, and a connector three ( one & two & three ) is the same as ( ( one, ( ( two, three ) | ( three, two ) ) ) | ( two, ( ( one, three ) | ( three, one ) ) ) | ( three, ( ( one, two ) | ( two, one ) ) ) ) 15 particles, 13 pair parens, and 14 connectors instead of three particles, 1 pair parens, and 2 connectors four ( one & two & three & four ) is the same as ( ( one, ( ( two, ( ( three, four ) | ( four, three ) ) ) | ( three, ( ( two, four ) | ( four, two ) ) ) | ( four, ( ( two, three ) | ( three, two ) ) ) ) ) | ( two, ( ( one, ( ( three, four ) | ( four, three ) ) ) | ( three, ( ( one, four ) | ( four, one ) ) ) | ( four, ( ( one, three ) | ( three, one ) ) ) ) ) | ( three, ( ( one, ( ( two, four ) | ( four, two ) ) ) | ( two, ( ( one, four ) | ( four, one ) ) ) | ( four, ( ( one, two ) | ( two, one ) ) ) ) ) | ( four, ( ( one, ( ( two, three ) | ( three, two ) ) ) | ( two, ( ( one, three ) | ( three, one ) ) ) | ( three, ( ( one, two ) | ( two, one ) ) ) ) ) ) 64 particles, 57 pair parens, and 63 connectors instead of 4 particles, 1 pair parens, and 3 connectors five ( one & two & three & four & five ) is the same as ( ( one, ( ( two, ( ( three, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, four ) | ( four, three ) ) ) ) ) | ( three, ( ( two, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( two, five ) | ( five, two ) ) ) | ( five, ( ( two, four ) | ( four, two ) ) ) ) ) | ( four, ( ( three, ( ( two, five ) | ( five, two ) ) ) | ( two, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, two ) | ( two, three ) ) ) ) ) | ( five, ( ( three, ( ( four, two ) | ( two, four ) ) ) | ( four, ( ( three, two ) | ( two, three ) ) ) | ( two, ( ( three, four ) | ( four, three ) ) ) ) ) ) ) | ( two, ( ( one, ( ( three, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, four ) | ( four, three ) ) ) ) ) | ( three, ( ( one, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( one, five ) | ( five, one ) ) ) | ( five, ( ( one, four ) | ( four, one ) ) ) ) ) | ( four, ( ( three, ( ( one, five ) | ( five, one ) ) ) | ( one, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, one ) | ( one, three ) ) ) ) ) | ( five, ( ( three, ( ( four, one ) | ( one, four ) ) ) | ( four, ( ( three, one ) | ( one, three ) ) ) | ( one, ( ( three, four ) | ( four, three ) ) ) ) ) ) ) | ( three, ( ( one, ( ( two, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( two, five ) | ( five, two ) ) ) | ( five, ( ( two, four ) | ( four, two ) ) ) ) ) | ( two, ( ( one, ( ( four, five ) | ( five, four ) ) ) | ( four, ( ( one, five ) | ( five, one ) ) ) | ( five, ( ( one, four ) | ( four, one ) ) ) ) ) | ( four, ( ( one, ( ( two, five ) | ( five, two ) ) ) | ( two, ( ( one, five ) | ( five, one ) ) ) | ( five, ( ( one, two ) | ( two, one ) ) ) ) ) | ( five, ( ( one, ( ( four, two ) | ( two, four ) ) ) | ( four, ( ( one, two ) | ( two, one ) ) ) | ( two, ( ( one, four ) | ( four, one ) ) ) ) ) ) ) | ( four, ( ( one, ( ( three, ( ( two, five ) | ( five, two ) ) ) | ( two, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, two ) | ( two, three ) ) ) ) ) | ( two, ( ( three, ( ( one, five ) | ( five, one ) ) ) | ( one, ( ( three, five ) | ( five, three ) ) ) | ( five, ( ( three, one ) | ( one, three ) ) ) ) ) | ( three, ( ( two, ( ( one, five ) | ( five, one ) ) ) | ( one, ( ( two, five ) | ( five, two ) ) ) | ( five, ( ( two, one ) | ( one, two ) ) ) ) ) | ( five, ( ( three, ( ( one, two ) | ( two, one ) ) ) | ( one, ( ( three, two ) | ( two, three ) ) ) | ( two, ( ( three, one ) | ( one, three ) ) ) ) ) ) ) | ( five, ( ( one, ( ( three, ( ( four, two ) | ( two, four ) ) ) | ( four, ( ( three, two ) | ( two, three ) ) ) | ( two, ( ( three, four ) | ( four, three ) ) ) ) ) | ( two, ( ( three, ( ( four, one ) | ( one, four ) ) ) | ( four, ( ( three, one ) | ( one, three ) ) ) | ( one, ( ( three, four ) | ( four, three ) ) ) ) ) | ( three, ( ( two, ( ( four, one ) | ( one, four ) ) ) | ( four, ( ( two, one ) | ( one, two ) ) ) | ( one, ( ( two, four ) | ( four, two ) ) ) ) ) | ( four, ( ( three, ( ( two, one ) | ( one, two ) ) ) | ( two, ( ( three, one ) | ( one, three ) ) ) | ( one, ( ( three, two ) | ( two, three ) ) ) ) ) ) ) ) 325 particles, 291 pair parens, and 324 connectors instead of 5 particles, 1 pair parens, and 4 connectors.

2 1

pics from Guelph
by Bauman, Syd 12 May '23

12 May '23

See https://bauman.zapto.org/~syd/temp/4TEICouncil/TEI_in_Guelph_2023/index.html.

2 1