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

TEI Lite 2.0 Task force
by Magdalena Turska 07 Nov '24

07 Nov '24

Dear Elisa and Council, Following up on our discussions in the F2F meeting in Buenos Aires I would like to request establishing a task force to create a new, substantially changed revision of the TEI Lite. As agreed in BA, task force members will be as follows: Helena Bermúdez-Sabel Gustavo Fernandez Riva Martina Scholger Magdalena Turska As for the organization of work, we are planning to meet in person in January 2025, in my house in Poland. Best regards, Magdalena Scope of the work and planned deliverables TEI Lite 2.0 task force is dedicated to the creation of the new TEI Lite schema and corresponding Guidelines with extended examples section. These will be accompanied by implementations for the new functionalities required for the schema processing and Guidelines publication. Rationale Motivations for the new version of the TEI Lite are several. First, its original dates back to 1996, later followed by a series of updates varying in scope. The last substantial revision was made in 2006, at a time when both the technologies supporting XML processing were not as developed, and, more importantly, consensus regarding publication and interoperability of TEI-encoded texts was completely lacking and implementation praxis varied hugely. Therefore TEI Lite (and TEI) Guidelines for the most part pay no heed to processing and publishing concerns, in particular rarely addressing encoding strategies for composite, heterogeneous collections, focusing rather on the "archive" function of the format, where effectively all information is injected into a single TEI resource. The task force's intention is to expand the horizon of the TEI Lite Guidelines, to discuss recommended data modeling, organization and processing practices for a broad range of real life uses. Especially the processing part will make use of the TEI Processing Model, non-existent yet when TEI Lite was last updated. Second, despite decades of efforts from the TEI community, the standard is still too often perceived as prohibitively complex, and even the presence of TEI Lite with its reduced set of elements did not amend the situation. One reason may be the fragmentary character of existing resources to learn TEI from, both in terms of structure and examples provided. Particularly the latter in the Guidelines are usually missing the broader context, from the facsimile of the original source to the complete TEI document to which they might belong, therefore making it impossible for the users to analyze the complete picture the Guidelines try to portray. Therefore, TEI Lite aims to extend the base of full encoding examples as well as illustrate remaining fragmentary ones with a broader context, from facsimile images, through the editorial process, to a proposed final presentation. This will be achieved through extensive use of graphic and other media (e.g. screencasts or animations), not relying solely on textual descriptions of phenomena discussed. Finally, one of the common concerns with the TEI standard is its increasing idiosyncrasy, for the most part a consequence of the inability to express contextually diverse content models for the same element. TEI Lite 2.0 task force intends to propose a syntax and implementation for that problem, together with the reorganization of a number of elements. We hope that the results of this effort will pave the way for the new, P6, version of the TEI.

1 0

Next Stylesheets meeting: October 29th
by Helena Bermúdez Sabel 22 Oct '24

22 Oct '24

Dear all, Tthe next Stylesheets meeting will take place on October 29th. There is a small poll in Slack to decide on the time since it will be in one of those weeks in the year in which our calendars are out of sync. The main point on the agenda is the discussed <valList> issue ( https://github.com/TEIC/TEI/issues/2597) (unless this is fixed before the meeting). Please, feel free to add any other topics to the agenda: https://docs.google.com/document/d/1K2raVt7dB9ti_O7JMoRRnu0KJk1JZbblB2tPDfp… Best, Helena

1 1

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 07 Jul '24

07 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