TEI Technical Council Teleconference, 2022-04-08

Meeting Times:

Present:

Apologies/Not Present:

Meeting minutes from virtual F2F (April) F2F meeting in Newcastle

Issues to discuss for the release

New section on TEI website for “How Tos”

Issues from previous SVF2F meeting

Lengthy test of adding namespaced attributes in response to #2069 and #237 comment. Action on SB by 2022-04-07: attach test ODD to ticket. We need to look at this with the full group. Guidelines Pull requests:

No. Group Title Comment
#1996 A align teidata.version with Semantic Versioning Specification, closes #1993 NA subgroup: we (Council) need to poke PS. For the 2nd bullet point we think this should be a “soft” requirement: Just recommend that @version matches; don’t actually validate it. 2022-04-08: Add language to indicate that for the TEI Guidelines we’re inspired by the semantic versioning conventions but we’re applying our own TEI conventions to it (not following the custom for identifying “major” / “minor”.)
#2069 A Warn if an attDef with a non-colonized @ident has a @ns attribute NA subgroup suggests a solution involving @ident and @altIdent when we specify the @ns, that solves the problem (we think) without changes required to TEI/Stylesheets. SB uploaded a sample ODD file. 2022-04-08: Council decided to reject PR.
#2143 A new langKnown example + bib ref NA subgroup: Connected to ticket #2139 which needs discussion. Check on #2143 is running; it will take 6 hours. We should ask Stuart Yeates to update his branch with changes from our dev, and make the small change requested. If he doesn’t respond we should recheck this in from a new branch we make. 2022-04-08: HBS will implement it as soon as she finished work on the bibliography.
#2156 A improve prose, constrain value of global source= attr NA subgroup discovers that sch:let is not permitted as a child of <constraint>, and that is the reason tests are failing. We think this is very strange, especially because our schema says it’s allowed. 2022-04-08: Council realized the build error problem is due to the positioning of the sch:let in the <constraintSpec>. SB will fix this.
#2188 B Fix #2187, I hope E subgroup: Left message in the PR regarding the failing of the test. 2022-04-08: Council decides for <contraintSpec schema=”schematron” ident=”blort” mode=”delete” />
#2185 B Address #2185 by restricting anyURI to not have spaces E subgroup: address in the afternoon session 2022-04-08: Action on HC to merge PR