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

Fwd: please drop simplePrint or correct its embarrassing description.
by Elisa Beshero-Bondar 15 May '25

15 May '25

Dear Council, Martin Mueller sends this request about simplePrint. I wonder which of these options is more sensible. I think I’m persuaded that we should drop it now and replace it with the TEI Publisher ODD, but perhaps we can discuss at the VF2F. Elisa Elisa Beshero-Bondar, PhD (she/they) Chair, TEI Technical Council 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 Typeset by hand on my iPhone Begin forwarded message: > From: Martin Mueller <martinmueller(a)northwestern.edu> > Date: May 15, 2025 at 2:27:11 PM EDT > To: Elisa Beshero-Bondar <ebbondar(a)gmail.com> > Subject: please drop simplePrint or correct its embarrassing description. > > > Dear Elisa, > > I have on several occasions complained (without success) about the embarrassing description of TEI simplePrint. My name appears at the top of the current introduction. > > The description is oddly condescending and in some instances plain wrong. In retrospect, I think it was a mistake to associate the Processing Model with a particular schema. Since the Processing Model is alive and well in EI Publisher, the best thing would be to drop this particular customization and replace it with TEI Publisher Base > > If that can’t be done—and I don’t see any reason why it couldn’t be done—it should at least be possible to correct gross inaccuracies. > > In the first of the four summary points, the distinction between print and manuscript is misleading. There are manuscript pages that could be easily encoded with simplePrint, and there are aspects of typography or layout on a printed page that you could not do with this tag set. The relevant criteria are the complexity of the page design and the degree to which you would want to capture its “materiality”. > > In the second point, “Early Modern” is defined as “up to the end of the nineteenth century”. The conventional limits of the term are roughly from the 1400’s to 1800. I am not aware of any features that can be encoded in simplePrint but are rarely found in modern materials. > > In the third point the reference to “Western European” is plain wrong. As long as the text can be represented in combinations of Unicode, you could use simplePrint as long as the document structure is supported. Homer, the Hebrew Bible, and Anna Karenina are not exactly “Western European” texts. > > The condescending tone of the document is most pronounced in the final point, which seems to assume that “specialist research” is measured by the degree of attention to the way in which the text was printed. There are highly specialized forms of inquiry that do not give a hoot about the ways in which pages are laid out and pages are printed as long as the words appear in the right order and in a spelling that makes their meaning apparent. > > To conclude with my initial point, the best solution would be to quietly drop simplePrint and replace it with TEI Publisher’s Base ODD. For its first couple of years TEI Publisher followed simplePrint and added its own Base version, which was marginally different. I suggested to Magdalena that TEI Publisher should should drop simplePrint and start with Base. What ever was useful about simplePrint survives in TEI Publisher Base without any of the very dubious rhetoric of simplePrint. > > Best > > MM > > Martin Mueller > Professor emeritus of English and Classics > Northwestern University >

1 0

Next Stylesheets meeing: April 22
by Helena Bermúdez Sabel 20 Apr '25

20 Apr '25

Dear all, The next Stylesheets meeting will take place on Tuesday April 22nd at 4 pm UTC, 9 am PDT, 12 pm EDT, and 6 pm CET. Please find the agenda here: https://docs.google.com/document/d/1NNfj0b7utonqFU7BeiE_KuhowGthH_C6wnQE1fk… Best, Helena

1 0

Great thing forgot
by Lou Burnard 17 Apr '25

17 Apr '25

Surely the "in memoriam" page at the front of the guidelines ought to include Michael's name? . Apologies for not having thought to mention this before current release.

2 1

DHSI Courses in Montreal
by Elisa Beshero-Bondar 25 Mar '25

25 Mar '25

Dear TEI list, Those interested in courses related to digital humanities as well as XML and TEI will find some good anticipated options on the slate at the Digital Humanities Summer Institute (DHSI), which has moved to Montreal, Quebec this year! Please take a look at this year's courses <https://dhsi.org/course-offerings/>(all of which we hope will be approved with sufficient enrollment), and consider whether a DHSI course might be helpful to you or those you work with. I'll note some very good options for our community in Week 1, May 26-30 (be sure to look from the start to the end of the list)! I hope to see you in Montreal in May! If you're curious about my course (that I co-teach with David Birnbaum), please peruse our course materials <https://ebeshero.github.io/UpTransformation/> and be in touch with questions about your project--we very much enjoy assisting with your projects in real time! 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: March 25th
by Helena Bermúdez Sabel 22 Mar '25

22 Mar '25

Dear all, The next Stylesheets meeting will take place on Tuesday March 25th at 7 pm UTC, 12pm PDT, 3 pm EDT, and 8 pm CET. As discussed, the meeting will be focused on testing and building the Guidelines. Best, Helena

1 0

Reminder: Council teleconference later today (Tues. March 18)
by Elisa Beshero-Bondar 18 Mar '25

18 Mar '25

Hi Council! Just a reminder and also an alert about our March Council call for today, Tuesday March 18. I needed to move this to today because I was in Japan last week. But also, our time zones are a bit out of alignment, with those in continental Europe holding to the same time as usual, but the rest of us being pitched one hour later due to the strangeness of daylight saving time. Meeting times: *11:30–13:00 PDT | 14:30–16:00 EDT | 18:30–20:00 UTC* | 19:30–21:00 CET Here’s our Google Docs agenda with the Zoom link <https://docs.google.com/document/d/1SJyerfT5RbJ28zLkyZSllvz5doAsGUkfUfrUmNj…> (same Zoom as usual). Please add your topics and move things around as needed! Thanks everyone! Looking forward to seeing 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

Council Meeting Postponed to Tuesday March 18
by Elisa Beshero-Bondar 09 Mar '25

09 Mar '25

Dear Council, Greetings from Japan! I'm in Kyushu today (Monday March 10), on invitation of Kiyonori Nagasaki, to speak about the TEI at Fukuoka University, and I won't be back home until the end of this week. We spoke about this on Slack, but I just wanted to make sure we formalized the arrangement. We will plan to hold the monthly Council call next week on Tuesday March 18. It will be at the same time as usual for the Europeans, but for the Americans, we're starting "Daylight Savings Time" and the meeting time for us will be one hour later: 11:30–12:30 PST | 14:30–16:00 EST | 17:30–19:00 UTC | 19:30–21:00 CEST (*Please triple-check me on this*, but I believe Daylight Savings Time just began in Canada and the US. The meeting time is set for UTC and CEST to remain the same!) We're about to have the ISO on our agenda, by the way, and I'll send a longer message soon about that. Thanks, everyone! 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: February 26
by Helena Bermúdez Sabel 23 Feb '25

23 Feb '25

Dear all, Seeing the results of the poll, I think that the best time to meet is on February 26, at 10:15 am PST, 1:15 pm EST, 6:15 pm GMT, 7:15 pm CET. The meeting will only take place for one hour (but whoever is still available is invited to stay in the Zoom chanel and continue). I am still working on the agenda, but here you have the link: https://docs.google.com/document/d/1NNfj0b7utonqFU7BeiE_KuhowGthH_C6wnQE1fk… Best, Helena

1 0

What is a base ODD?
by Martin Holmes 13 Feb '25

13 Feb '25

Hi all, The ATOP group has been grappling with the issue of ODD chaining, and in particular, how to determine, starting from a customization ODD to process and following its chain of precursors, how to know when you reach a base ODD and don't have to go any further. This is easy if the ultimate base ODD is p5subset, and that is indeed the default. However, it's perfectly possible that you don't want anything at all from P5, you just want to customize a base ODD that you've already created. One obvious sign of a base ODD is that there is no <schemaSpec> element -- which is the case for p5subset -- but we know that many base ODDs in the wild DO have a `<schemaSpec>` element, and it also seems intuitive that if you're creating a schema specification, you should use a `<schemaSpec>` element. So we've arrived at a definition of a base ODD, which we believe is testable; it goes like this (adapted from our meeting notes): EITHER the ODD has no `<schemaSpec>` element, OR it has a <schemaSpec> with no `@source` (meaning that the source would default to p5subset), BUT there are no `<*Ref>` children of that `<schemaSpec>` invoking content from p5subset so there is no need to retrieve it. This is based on the assumption that if you use any `<*Ref>` element at the base level (i.e. as a direct child of `<schemaSpec>`), that constitutes a call to retrieve something from p5subset; but any such `<*Ref>` at a lower level must be referring to what is already in the schema (either because it's locally defined, or because it was brought in by a top-level `<moduleRef>`, `<elementRef>`, etc.). So my question is: does all this make sense to you all? If so, and we proceed on this basis, then P5 could probably use some more explanation of what a base ODD is, and how it fits into the chaining process. I should also say that current approaches to ODD chaining with the current Stylesheets involve pre-compiling any ODD which is earlier in the chain, so that it constitutes a .processedodd file (see <https://teic.github.io/PDF/howtoChain.pdf> section 4), but we would like ATOP to be able to do all that automatically, so that all you do is specify the source for your customization, and the processor can construct the entire chain and compile everything in sequence. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre I acknowledge and respect the lək̓ʷəŋən peoples on whose traditional territory the university stands and the Songhees, Esquimalt and WSÁNEĆ peoples whose historical relationships with the land continue to this day.

4 6

Reminder: TEI Council Meeting Tomorrow (Tues. Feb 11)
by Elisa Beshero-Bondar 10 Feb '25

10 Feb '25

TEI Councillors, Just a reminder that we meet tomorrow, Tuesday 2/11 (10:30–12:00 PST | 13:30–15:00 EST | 17:30–19:00 UTC | 19:30–21:00 CEST) for our monthly teleconference. Here’s the agenda Google Doc <https://docs.google.com/document/d/1XNBdtao_8p3G_AKSY1kUPIVCxRi6lT-3tvpE9jG…> with the Zoom link inside. Please add tickets / issues that you’d like us to discuss together at this meeting! 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