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

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

Next Stylesheets Meeting (about testing infrastucture)
by Helena Bermúdez Sabel 24 May '24

24 May '24

Dear all, The next Stylesheets meeting will take place on May 27th at 10am PDT / 1pm EDT / 5pm UTC / 7pm CEST. Peter Stadler has kindly accepted to take the lead in this meeting, and do an overview of our testing infrastructure. Best, Helena

1 0

May Council Meeting changed to May 15, Buenos Aires travel doc
by Elisa Beshero-Bondar 09 May '24

09 May '24

Dear Council members, The Council meeting we’d planned for this Friday May 10 is now postponed to Wednesday May 15 at a new time: - 10:30am - noon Pacific time (Joey) - 1:30 - 3pm Eastern Time (Syd, Raff, Elisa) - 7:30 - 9pm CET (Sabine, Martina, Torsten, et al) It will be the usual Zoom link: https://psu.zoom.us/j/98850059066?pwd=UzhBL2NFc1lweWYzS2xZd2dqYVZpdz09 (Password: tei) I've also started a very rough Google Doc <https://docs.google.com/document/d/1EVwA5vbreWLUeyWJU286g43t4XKkIm2otkjjrtK…> to assist our travel planning to Buenos Aires. We're awaiting details on the locations of Council's meetings, but I think we'll have that very soon. Traditionally, Council members share arrival times / flight numbers (etc) here so we can look out for each other and try to meet at airports / stations as we arrive and depart. Please feel free to begin sharing your information here. We also have started using two new channels in Slack: * #f2f-planning * #tei-conference (where Torsten has begun discussing travel plans) One more thing! We need to determine dates for summer monthly meetings ahead of our trip to Buenos Aires, so please be thinking of good times of day and dates for our one 90-minute meeting per month. See you soon, and many thanks for all you do for the TEI! 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