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

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

Re: [Tei-council] Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph
by James Cummings 18 Apr '23

18 Apr '23

Hi all, In order to keep kicking this TEI Panel at the Making Links conference into shape I've opened up a google doc at https://docs.google.com/document/d/1zJlc98LSaK5T_8WgHvMxR0g3HiSz-XhRjB0oAEe… Diane: You weren't listed in the initial list of people on the panel, do you want to be? (I added you in, but feel free to remove yourself if you don't!) Susan: Do you need an abstract or individual contribution titles from us? Or is no abstract and just general session title okay? I've added a place for people to suggest other overall titles. Many Thanks, James -- Dr James Cummings, Senior Lecturer in Late-Medieval Literature and Digital Humanities, School of English, Newcastle University In-Person Office Hours: https://jamescummings.youcanbook.me/ Zoom Office Hours: https://jamescummings-zoom.youcanbook.me/ ________________________________ From: Elisa Beshero-Bondar <ebbondar(a)gmail.com> Sent: 14 April 2023 16:28 To: Susan Brown <sbrown(a)uoguelph.ca> Cc: diane.jakacki(a)bucknell.edu <dkj004(a)bucknell.edu>; Constance Crompton <constance.crompton(a)uottawa.ca>; Hugh Cayless <philomousos(a)gmail.com>; James Cummings <James.Cummings(a)newcastle.ac.uk>; Janelle Jenstad <jenstad(a)uvic.ca>; rviglian(a)umd.edu <rviglian(a)umd.edu> Subject: Re: Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph Hi Susan and all, TEI Council met today, and I discussed the TEI Panel at LINCS with them, to get some more information on when people are arriving and who is interested. If it is possible for us to do this on Sunday morning at 9am, that will make it possible for some of our Council members to join--some who were involved in recent Guidelines developments on standoff annotation. So, if the panel is on Sunday morning at 9am, you could add Magdalena Turska. Hugh Cayless can also be listed, though he (still) might be delayed in his arrival. Magdalena would not be able to come on either of the Saturday afternoon slots due to her arrival time, but Sunday AM is fine! At any rate, more Council members can simply even be present at the panel if we do this on Sunday morning. I hope this is still timely and workable! It's okay if not--but let us know. If you need to keep the Saturday afternoon timing for the panel, we'll start the Council workday a little earlier on Sunday. On a related note, here's a pretty important question for us! What will Council need to know about working at the THINC Lab? * When is it okay for Council to be there--how early can we be there? * Do we need to leave by a certain time? (Is it okay if we work late on Sunday, like until 6pm or so--if we're getting a later start?) * Can we leave our computers safely in the room while going out for lunch? (Do we lock the door, do I get a key, etc etc? Cheers and thanks, on behalf of Council, for arranging a way for us to participate in the LINCS conference! Elisa On Sat, Apr 8, 2023 at 5:18 PM Susan Brown <sbrown(a)uoguelph.ca<mailto:sbrown@uoguelph.ca>> wrote: Hi Elisa, We’ve scheduled the session for Saturday afternoon at. 1:15 in the first session after lunch, and have been able to free up a bit more time for it so it will now be 75 minutes. We could, however, swap it to 9-10:15 on Sunday morning if that was better. The conference is being held less than a 5-minute walk from the THINC Lab, where you’ll have your meetings. Cheers, Susan From: Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>> Date: Friday, April 7, 2023 at 8:40 PM To: Diane Jakacki <dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu>> Cc: Constance Crompton <constance.crompton(a)uottawa.ca<mailto:constance.crompton@uottawa.ca>>, Hugh Cayless <philomousos(a)gmail.com<mailto:philomousos@gmail.com>>, James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>>, Janelle Jenstad <jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>>, Susan Brown <sbrown(a)uoguelph.ca<mailto:sbrown@uoguelph.ca>>, rviglian(a)umd.edu<mailto:rviglian@umd.edu> <rviglian(a)umd.edu<mailto:rviglian@umd.edu>> Subject: Re: Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph CAUTION: This email originated from outside of the University of Guelph. Do not click links or open attachments unless you recognize the sender and know the content is safe. If in doubt, forward suspicious emails to IThelp(a)uoguelph.ca<mailto:IThelp@uoguelph.ca> Hi all, Sorry for my late response to the panel arrangements! I've been in the teaching zone the past two days and needed a moment to catch up on this long thread. Susan, yes, Council does plan to meet all day on Sunday, but the hour we begin is flexible at the moment, and we can work around a Sunday morning LINCS panel slot, I'm sure. If the LINCS panel were at 9 or 9:30 am on Sunday morning, would that work for Council to begin around 10:30 or 11am on Sunday? That said,I think holding the panel on Saturday afternoon may be better if there are one or two people from Council already on site and willing to be part of it. Elisa On Fri, Apr 7, 2023 at 3:00 PM Diane Jakacki <dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu>> wrote: All props for LEAF-Writer should go to the CWRC team - I just talk about and use it a lot! On Fri, Apr 7, 2023 at 11:15 AM Constance Crompton <constance.crompton(a)uottawa.ca<mailto:constance.crompton@uottawa.ca>> wrote: Hi, I would be happy to participate – I can certainly speak about the way embedded TEI uris are being used in the LINCS TEI that I am working with and (if in a slightly handwavy way) my admiration for the standoff rdf json that you produce through LEAFWriter Diane and James. What a delight to all be together in person! Best, Connie From: Hugh Cayless <philomousos(a)gmail.com<mailto:philomousos@gmail.com>> Date: Thursday, April 6, 2023 at 12:44 PM To: James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> Cc: Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>>, Janelle Jenstad <jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>>, Susan Brown <sbrown(a)uoguelph.ca<mailto:sbrown@uoguelph.ca>>, Constance Crompton <constance.crompton(a)uottawa.ca<mailto:constance.crompton@uottawa.ca>>, dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu> <dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu>>, rviglian(a)umd.edu<mailto:rviglian@umd.edu> <rviglian(a)umd.edu<mailto:rviglian@umd.edu>> Subject: Re: Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph Attention : courriel externe | external email Sunday morning would be my only option (and that only if the travel gods smile upon me) but it’s a topic dear to my heart. It would certainly be a good thing to talk about the affordances TEI provides for linked data. Some of them are quite new, and people might not know about them. Hugh On Apr 6, 2023, at 09:34, James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: Hi all, Yes, if in addition to Connie and Diane, we get up to 2 people from TEI Council who happen to be there early enough (say before Saturday Afternoon or Sunday first thing?) then we could do a roundtable-like panel that I'm happy to chair and act as a respondent to it in some way. I'll send an email to the tei-council list. Susan: When do you need What from us by? Many Thanks, James -- Dr James Cummings, Senior Lecturer in Late-Medieval Literature and Digital Humanities, School of English, Newcastle University In-Person Office Hours: https://jamescummings.youcanbook.me/ Zoom Office Hours: https://jamescummings-zoom.youcanbook.me/ ________________________________ From: Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>> Sent: 06 April 2023 12:28 To: Janelle Jenstad <jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>> Cc: James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>>; Susan Brown <sbrown(a)uoguelph.ca<mailto:sbrown@uoguelph.ca>>; Constance Crompton <constance.crompton(a)uottawa.ca<mailto:constance.crompton@uottawa.ca>>; diane.jakacki(a)bucknell.edu<mailto:diane.jakacki@bucknell.edu> <dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu>>; rviglian(a)umd.edu<mailto:rviglian@umd.edu> <rviglian(a)umd.edu<mailto:rviglian@umd.edu>> Subject: Re: Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph ⚠ External sender. Take care when opening links or attachments. Do not provide your login details. Also, if you do want to organize a panel as James proposes, I can bring it up at the Council meeting next week to see who among the developers of the stand-off annotation encoding is arriving early enough to feasibly participate. Shall I do that? Elisa Typeset by hand on my iPhone On Apr 6, 2023, at 7:21 AM, Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>> wrote: I think James was referring more to the structures the TEI has recently introduced to handle stand-off annotation of various kinds—that facilitate or perhaps even represent in themselves a representation of linked data. These are set up with things like triple-stores in mind…and some of us on Council now were involved in drafting those new structures. It’s important material—and James, I think you should reach out to a wider pool of Council members about it—including Hugh, Magdalena, Martina, as well as us of course. Elisa Typeset by hand on my iPhone On Apr 6, 2023, at 2:01 AM, Janelle Jenstad <jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>> wrote: Hi All, I’ll be at the Making LINCS conference from Friday on. Connie and Diane are the real experts. I usually feel that I’m just along for the ride and occasionally create some linked data that you all think is useful! What are you thinking of, Susan? It’s easy enough to create xml:ids for entities in TEI and then tag those things using <placeName>, <persName>, <orgName>, etc. Is that too obvious or do you think it’s worth explaining how TEI has elements for the sort of entities that we like to link up? J. Janelle Jenstad (she/her) Professor, Department of English, University of Victoria<https://journals.uvic.ca/index.php/scene/> Traditional territory of the lək̓ʷəŋən peoples – the Songhees, Esquimalt and W̱SÁNEĆ Co-Coordinating Editor, Digital Renaissance Editions<https://digitalrenaissance.uvic.ca/>, the New Internet Shakespeare Editions, and the MoEML Mayoral Shows Anthology<https://lemdo.uvic.ca/moms/> Director, Map of Early Modern London<https://mapoflondon.uvic.ca/>; Director, Linked Early Modern Drama Online<https://lemdo.uvic.ca/> Co-Applicant, The Endings Project Email: jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>, lemdo(a)uvic.ca<mailto:lemdo@uvic.ca>, or london(a)uvic.ca<mailto:london@uvic.ca> From: Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>> Sent: April 4, 2023 7:41 PM To: James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> Cc: Susan Brown <sbrown(a)uoguelph.ca<mailto:sbrown@uoguelph.ca>>; Janelle Jenstad <jenstad(a)uvic.ca<mailto:jenstad@uvic.ca>>; Constance Crompton <constance.crompton(a)uottawa.ca<mailto:constance.crompton@uottawa.ca>>; diane.jakacki(a)bucknell.edu<mailto:diane.jakacki@bucknell.edu> <dkj004(a)bucknell.edu<mailto:dkj004@bucknell.edu>>; rviglian(a)umd.edu<mailto:rviglian@umd.edu> Subject: Re: Possible Linked Open Data In TEI Panel for the Making LINCS conference in Guelph Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information. Hi all, I think James's idea is a good one to update our communities about standoff developments in TEI, so I hope this comes together. I don't arrive in Guelph until Saturday evening May 6, and we start the TEI Council session on Sunday morning--so I'm guessing the timing is too tight for me to be involved--but I hope others can connect. Cheers, Elisa On Thu, Mar 30, 2023 at 4:08 PM James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: Hi potentially interested people, Susan had asked whether we would be willing to have a panel/roundtable type session in the Making LINCS conference talking about how Linked Open Data now works in the TEI. There have been a lot of developments (e.g. with <standOff>, <annotation> <annotationBlock> etc.) in the TEI. I think some of the people doing LOD but who have passing familiarity with TEI might still think of it as TEI P4 or earlier, so it might be good to bring them up to date. Would you be interested in being part of such a panel/roundtable type thing? I didn't know when Elisa, Janelle, and Raff were arriving in Guelph (so if you would be there in time), or if you think there would be better people on the TEI Technical Council who would be there to speak to this? Or if there are other obvious people who are going to be there that I don't know about? Many Thanks, James -- Dr James Cummings, Senior Lecturer in Late-Medieval Literature and Digital Humanities, School of English, Newcastle University In-Person Office Hours: https://jamescummings.youcanbook.me/ Zoom Office Hours: https://jamescummings-zoom.youcanbook.me/ -- Elisa Beshero-Bondar, PhD 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://newtfire.org/> -- Diane Jakacki, Ph.D. Digital Scholarship Coordinator Affiliate Faculty in Comparative & Digital Humanities Bucknell University diane.jakacki(a)bucknell.edu<mailto:diane.jakacki@bucknell.edu> (she/her) https://orcid.org/0000-0002-7836-1223 Fulbright Canada Research Chair in Digital Humanities, 2022-3 Principal Investigator, LAB Cooperative and REED London Online Executive Board Chair-Elect, ADHO Chair, TEI-C Executive Board -- Elisa Beshero-Bondar, PhD 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://newtfire.org/> -- Elisa Beshero-Bondar, PhD 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://newtfire.org/>

3 2

TC Minutes
by Lou Burnard 17 Apr '23

17 Apr '23

I understand that there is some interest amongst some council members in defining a more appropriate format for the TC's minutes than the WordPress files currently used. Readers of my personal blog at https://foxglove.hypotheses.org (if there are any) will know that I have been banging on about this very topic for the last few weeks; others are cordially invited to give said blog a quick glance, just in case it's of interest to you too. And if anyone cares to put their head above the parapet and confess to sharing my concerns, or has already thought through and solved the whole problem, then I would like to meet you!

3 3

tc mins in xml
by Lou Burnard 17 Apr '23

17 Apr '23

I understand that there is some interest amongst some council members in defining a more appropriate format for the TC's minutes than the WordPress files currently used. Readers of my personal blog at https://foxglove.hypotheses.org (if there are any) will know that I have been banging on about this very topic for the last few weeks; others are cordially invited to give said blog a quick glance, just in case it's of interest to you too. And if anyone cares to put their head above the parapet and confess to sharing my concerns, or has already thought through and solved the whole problem, then I would like to meet you!

1 0

Possible roundtable on TEI+LOD for Making LINCS conference in Guelph
by James Cummings 06 Apr '23

06 Apr '23

Hi TEI Council, As some of you are going to be appearing in Guelph for the TEI Council meeting which follows on from the Making LINCS conference (and then after the DH at Guelph Summer Workshops), and then for some of us having a LEAF-VRE project meeting! (I'm going to be around in Guelph from 4-17, then visiting my parents who live in Waterloo before flying home.) As such Susan Brown asked if we might have a roundtable or similar in the Making LINCS conference talking about how Linked Open Data now works so much better in the TEI. There have been a lot of developments (e.g. with <standOff>, <annotation> <annotationBlock> etc.) in the TEI. I think some of the people doing LOD but who have passing familiarity with TEI might still think of it as TEI P4 or earlier, so it might be good to bring them up to date. Say a roundtable session with a bit of show-and-tell point to all the neat new things TEI can do to record LOD. I'd happily chair and be a bit of a respondent, write up an overall abstract, etc. I'm hoping that Diane and Connie will volunteer (Diane indeed already has!), but it would be good to get a couple of current Council members depending on when people are arriving. (e.g. we could ask to be scheduled late Saturday or early Sunday and it wouldn't take too much time out of the Council meeting. I know Janelle indicated she might be available, but I didn't know when others were arriving and wanted to make sure to give everyone the opportunity. (There may be some for whom it would be useful but low-stakes CV entries?) Many Thanks, James -- Dr James Cummings, Senior Lecturer in Late-Medieval Literature and Digital Humanities, School of English, Newcastle University In-Person Office Hours: https://jamescummings.youcanbook.me/ Zoom Office Hours: https://jamescummings-zoom.youcanbook.me/

2 2

Brrr…
by Bauman, Syd 31 Mar '23

31 Mar '23

We are frozen. New branches (TEI/release-4.6.0 and Stylesheets/release-7.55.0) have been created. (Each was created from a dev branch for which I had just issues git pull.) Pushes and merges to these two branches should only be made by the release techs. (SB, HC, JT.)

1 0

roma + i18n: why are we waiting?
by Lou Burnard 26 Mar '23

26 Mar '23

The latest release of roma (Mar 13, 0.3.1) is what you get if you try romabeta.tei-c.org<http://romabeta.tei-c.org> today. This still doesn't have any i18n features and is thus useless to the non-anglophone. The prototype at https://romajsdev.netlify.app/ claims to be using roma 1.0.0 but that hasn't been released yet. When may we expect a change? It's doing my head in to have two beta versions to choose from...

1 0