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

Travel Form
by Hugh Cayless 22 May '19

22 May '19

Hi All, I noticed this morning that the link to the travel form on the TEI website is broken, so until that can be fixed, I'll just circulate the form here. Great to see you all last week! Hugh

3 2

Stylesheets in 40 mins
by Syd Bauman 20 May '19

20 May '19

So the (sparesly attended) Stylesheets meeting starts in ~0.7 hours. I do not know what technology we should use to meet, but I think the plan is for Peter to review the recent build breakage that was caused by, what, #375 or #239? If I haven't heard otherwise from folks I will look on Google Hangouts for y'all in a bit over half an hour. (We could just use Skype, BTW, as there will be very few of us -- SB, MS, PS, MH? are the only confirmations I've had.)

2 1

upcoming meetings
by Syd Bauman 16 May '19

16 May '19

Are we having a Council conference call this coming Fri 05-17 20:00Z? Are we having a Stylesheets meeting a week from tomorrow, 05-20 15:00Z?

8 10

mysterious new validation error in ODD-generated Relax NG XML schema
by Elisa Beshero-Bondar 16 May '19

16 May '19

Dear Council, Are any of you seeing mysterious problems with ODD-generated schemas since we returned from DC? I'm not sure what's going on here, but a schema that was functioning on my project files in the first week of May--a schema that I have in no way altered--is suddenly today refusing to validate, with a bizarre ISO-Schematron error pointed at a line that makes no sense at all. When I try to generate a new version of the schema, the error appears again pointing at a completely different line. I've written up the problem to the oXygen-user mailing list to see what they advise. My message with more details on the errors, with links to my files is below. Baffled, Elisa ---------- Forwarded message --------- From: Elisa Beshero-Bondar <ebbondar(a)gmail.com> Date: Thu, May 16, 2019 at 2:38 AM Subject: mysterious new validation error in ODD-generated Relax NG XML schema To: <oxygen-user(a)oxygenxml.com> Dear oXygen list, I generated a schema in Relax NG XML syntax from a TEI ODD file some weeks ago, on May 6, and the schema behaved as I expected it to. It is posted on my GitHub repo and shared with my project team, and other members of my team worked with it in the past few weeks. I have not edited the schema that my team using since that date. Today one of my team members alerted me that she was seeing a strange error, and I confirmed locally that this is on the Relax NG schema. The error reads: Description Effective boolean value is not defined for a sequence of two or more items starting with a boolean Severity Fatal System ID https://digitalmitford.github.io/DM_documentation/MitfordODD/out/mitfordODD… Main validation file /Users/elisa/Downloads/OVWalksInTheCountryTHECOWSLIPBALL.xml <http://users/elisa/Downloads/OVWalksInTheCountryTHECOWSLIPBALL.xml> Engine name ISO Schematron Start location line: 4996, column: 0 Here is another wrinkle to the problem. In attempting to debug, I generated a new RNG schema from the source ODD to see if that would make a difference. Interestingly, it did, with this effect: On attempting to validate a project XML file, I saw the same message about the effective boolean value, only this time it pointed to a different line in the RNG (not 4996, but 5151). In neither of these cases was the code on these lines at all meaningful or related to the reported ISO Schematron error. Line 4996 is the blank line below after defining the element binaryObject. <define name="teibinaryObject"> <element name="binaryObject"> <text/> <ref name="teiatt.global.attributes"/> <ref name="teiatt.media.attributes"/> <ref name="teiatt.timed.attributes"/> <ref name="teiatt.typed.attributes"/> ... </define> The other line was similarly not about making a boolean test of any kind. I do not understand what could be causing these problems, particularly since the schema was behaving normally two weeks ago. I cannot seem to generate a working schema now due to this strange ISO-Schematron error that keeps flagging different lines of my Relax NG document. Here is a copy of my schema, which I link here from my GitHub repo: https://raw.githubusercontent.com/DigitalMitford/DM_documentation/master/Mi… And here is a project XML file associated with that schema: https://raw.githubusercontent.com/DigitalMitford/DM_documentation/master/mr… I hope someone on this list can help! I don't think this is a problem with my ODD or with ODD processing, but with something that is firing ISO-Schematron over my RNG schema, which is expressed in XML syntax. The strangeness of this prompted me to write to this list instead of to the TEI. Thanks, Elisa -- Elisa Beshero-Bondar, PhD Associate Professor of English University of Pittsburgh at Greensburg Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu

2 3

stickers
by Syd Bauman 15 May '19

15 May '19

Elisa (and anyone else who needs some TEI stickers before we see each other again) -- Send me your postal address.

1 0

Re: [Tei-council] upcoming meetings
by James Cummings 14 May '19

14 May '19

Hi, Just to send my apologies for the Stylesheets meetings. I'll be in London at the Wellcome Institute interviewing people for a post as a TEI manuscript cataloguer. (At least it is TEI related!) There is a chance I might miss or be late to a meeting this Friday, I have something after work that day and I'm not sure how long it will go on for. (I'll try to find out. But if the meeting does run I'll make every effort to get there on time.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 14 May 2019 10:40 To: Peter Stadler; Syd Bauman Cc: TEI Council Subject: Re: [Tei-council] upcoming meetings Dear all, Our next Council call is scheduled for Friday. I think what Syd meant is that we usually don’t have meetings in the same month as our F2F meeting. What do you think, should we have a meeting on Friday or skip it? If we do the meeting, I would suggest to continue with open tickets that we didn’t discuss during the F2F and I would add a table with tickets to the agenda. @Stylesheets meeting: Monday is fine for me too. Best wishes, Martina -----Ursprüngliche Nachricht----- Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Peter Stadler Gesendet: Dienstag, 14. Mai 2019 08:05 An: Syd Bauman <s.bauman(a)northeastern.edu> Cc: TEI Council <tei-council(a)lists.tei-c.org> Betreff: Re: [Tei-council] upcoming meetings Syd, I assume those dates are correct and listed on the TEI calendar (which makes them tautologically correct for me … ) Yet, my apologies because I can’t make it this Friday. Monday is ok with me. Best Peter > Am 12.05.2019 um 20:33 schrieb Syd Bauman <s.bauman(a)northeastern.edu>: > > Are we having a Council conference call this coming Fri 05-17 20:00Z? > > Are we having a Stylesheets meeting a week from tomorrow, 05-20 > 15:00Z? > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1

F2F Washington
by Scholger, Martina (martina.scholger＠uni-graz.at) 14 May '19

14 May '19

Dear all, It was great to see you last week - thanks for the productive meeting! I hope you all made it back home without too much troubles. Thanks Meaghan for hosting us at the Folger Library and Raff for showing us your Washington! Best wishes, Martina

1 0

Re: [Tei-council] Jenkins build failure
by James Cummings 11 May '19

11 May '19

Ah. That would make sense! Change in the stylesheets ... bitten by that circularity again. The ref/@target of that change to the stylesheets at the pull request we accepted at https://github.com/TEIC/Stylesheets/commit/5e6c445b1dbe92c2d3d30ef0bfa95127… just uses the @target in xhtml:a/@xhtml:href when we might need to sanitise it for things EPUB can't handle? Sounds like the @target is used in an xpath somewhere in the conversion to EPUB where it being a fragmentary identifier causes a problem. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Peter Stadler <stadler(a)edirom.de> Sent: Sunday, May 12, 2019 12:04:53 AM To: Syd Bauman Cc: tei-council(a)lists.tei-c.org Subject: Re: [Tei-council] Jenkins build failure Hi Syd, thanks for the response :) But it might be I actually used the wrong address? (Although I got auto response from James …) Anyway, regarding the more important issue with the broken build. I think I nailed it down to a Stylesheets not a Guidelines issue. First, I checked locally the current Guidelines master branch with the dev version of the Stylesheets and the same pub error surfaced. So I started looking at the Stylesheets and going back to ed6ac7263bb0d9cbaf448783aceb58fe97824f95 ‚fixed‘ the Guidelines build. More testing, the following https://github.com/TEIC/Stylesheets/commit/5e6c445b1dbe92c2d3d30ef0bfa95127… then introduced the bug. It’s too late for me today but maybe someone else wants to investigate further? Best Peter > Am 12.05.2019 um 00:54 schrieb Syd Bauman <s.bauman(a)northeastern.edu>: > > Fingers crossed ... > > And I'm mostly sending this, Peter, to test whether or not I get a > "moderator approval needed" message. > >> Elisa, you’re right, there were some issues due to the DNS change >> but not the ones James mentioned. Nevertheless I kicked off new >> Travis and Jenkins builds to fix the DNS issues and hope the pub >> issues will magically disappear as well ;) > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Re: [Tei-council] Your message to Tei-council awaits moderator approval
by Peter Stadler 11 May '19

11 May '19

Is it just me getting those replies? Peter > Am 12.05.2019 um 00:35 schrieb tei-council-owner(a)lists.tei-c.org: > > Your mail to 'Tei-council' with the subject > > Re: [Tei-council] Jenkins build failure > > Is being held until the list moderator can review it for approval. > > The reason it is being held: > > Post by non-member to a members-only list > > Either the message will get posted to the list, or you will receive > notification of the moderator's decision. If you would like to cancel > this posting, please visit the following URL: > > http://lists.lists.tei-c.org/mailman/confirm/tei-council/d41b40affc3a586249… >

1 0

Jenkins build failure
by James Cummings 11 May '19

11 May '19

Does anyone have any suggestions why commit: https://github.com/TEIC/TEI/commit/672a64aa68080154242a8c27e19644a88afb9e8a and/or https://github.com/TEIC/TEI/commit/a5892a7bbbf8212eb3f66137790c5708bb64dd7b which are changes to the <desc> of <msFrag> seem to have broken Jenkins? https://jenkins.tei-c.org/job/TEIP5-dev/changes The errors from that build https://jenkins.tei-c.org/job/TEIP5-dev/242/parsed_console/ all seem to relate to the creation of EPUB and seem to cover every chapter of the Guidelines complaining about fragment identifiers. I've spent a bit of time investigating it but haven't figured out why EPUB should be affected by this change (or what randomly changed in between this and the last successful build.) :-( Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University

5 5

Re: [Tei-council] Jenkins build failure
by James Cummings 11 May '19

11 May '19

Possible ... but the commit that broke it was during the afternoon of Wednesday during the meeting. The DNS change wasn't until Friday wasn't it? Was there something that changed with the website on Weds? Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Elisa Beshero-Bondar <ebbondar(a)gmail.com> Sent: Saturday, May 11, 2019 11:28:45 PM To: James Cummings Cc: tei-council(a)lists.tei-c.org Subject: Re: [Tei-council] Jenkins build failure Just a guess— could it be related to the DNS change? Do we need to change a line in the stylesheet that generates ePub? Elisa Sent from my iPhone On May 11, 2019, at 3:00 PM, James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: Does anyone have any suggestions why commit: https://github.com/TEIC/TEI/commit/672a64aa68080154242a8c27e19644a88afb9e8a and/or https://github.com/TEIC/TEI/commit/a5892a7bbbf8212eb3f66137790c5708bb64dd7b which are changes to the <desc> of <msFrag> seem to have broken Jenkins? https://jenkins.tei-c.org/job/TEIP5-dev/changes The errors from that build https://jenkins.tei-c.org/job/TEIP5-dev/242/parsed_console/ all seem to relate to the creation of EPUB and seem to cover every chapter of the Guidelines complaining about fragment identifiers. I've spent a bit of time investigating it but haven't figured out why EPUB should be affected by this change (or what randomly changed in between this and the last successful build.) :-( Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Re: [Tei-council] Testing
by James Cummings 10 May '19

10 May '19

Got it but for some reason marked as spam. :-( Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: Friday, May 10, 2019 6:57:18 PM To: Hugh Cayless; TEI Council Subject: Re: [Tei-council] Testing Hip - Hip - Hurra Von meinem Huawei-Mobiltelefon gesendet -------- Originalnachricht -------- Betreff: Re: [Tei-council] Testing Von: Hugh Cayless An: TEI Council Cc: Here's to unexpected success! On Fri, May 10, 2019 at 1:28 PM Raffaele Viglianti <raffaeleviglianti(a)gmail.com<mailto:raffaeleviglianti@gmail.com>> wrote: Got it! On Fri, May 10, 2019 at 1:26 PM Hugh Cayless <philomousos(a)gmail.com<mailto:philomousos@gmail.com>> wrote: Let me know if you get this _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1

Testing
by Hugh Cayless 10 May '19

10 May '19

Let me know if you get this

4 4

test
by Hugh Cayless 10 May '19

10 May '19

1 0

Re: [Tei-council] Roma for class
by Syd Bauman 06 Mar '19

06 Mar '19

Thank you, Peter. So sweet. (And I'm not going to *try* to take it down. Just worried.) Peter Stadler writes: > Re question 1) > There’s also https://roma.tei-c.de/ but that’s pointing at the same > instance as https://roma2.tei-c.org/. But I think the bottleneck is > OxGarage which might choke on multiple concurrent requests. So, I > updated my OxGarage stack (which roma2 uses) to run three instances > (behind a load balancer) — just for you, Syd :) I’d be happy to get > some feedback about whether and how you were still(?) able to bring > it down.

1 0

test
by Scholger, Martina (martina.scholger＠uni-graz.at) 06 Mar '19

06 Mar '19

Just a test

2 1

Roma for class
by Syd Bauman 05 Mar '19

05 Mar '19

I am teaching a class on TEI schemas Fri 03-08 10:00/12:00-05:00. At the moment * https://tei-c.org/tools/roma/ does NOT work * https://roma.tei-c.org/ does NOT work -- bad certificate * https://roma2.tei-c.org/ does work Question 1: Are there other instances of Roma runinng that I might use? Does anyone happen to have one up? (I used to have one at Brown, but never set it up at Northeastern.) Question 2 (mostly for Raff): Bad or good idea to show them RomaJS?

1 0

RomaJS - update and meeting
by Raffaele Viglianti 05 Feb '19

05 Feb '19

Hello Council, Now that the new release is (mostly) behind us (thanks Elli, Hugh, at al!), I wanted to give you a quick update about RomaJS and attempt to schedule a call for the second week of February to discuss development and get started on planning user testing. DOODLE for meeting: https://doodle.com/poll/8p7exq3vptpb8g9t I've just updated the demo at http://mith.us/romajs. Feel free to try it out and let me know what's broken. I've been using waffle.io to keep track of GitHub issues and I found it very helpful to make sure what I do is reflected as much as possible into GitHub. The board is public and accessible here: https://waffle.io/TEIC/romajs If you have permissions on Github for TEIC, you will also be able to do stuff here if you log in. All of this is also available on GitHub issues, I just like the kanban style of waffle. To get a summary of what I've been working on since mid-December have a look at the "Done" column on the right. Here's a couple of highlights: - Create new classes and new elements in custom namespace - Implement revert to source button - Update material components web (you'll notice that the UI is pretty much the same but a little slicker) - Split updateOdd reducers (huge task with little practical effects, but that has greatly affected code readability) Please fill in the doodle and don't hesitate to ask questions here or on slack (there's a romajs channel). Thank you! Raff

1 1

additions/improvements to tcw22
by Mylonas, Elli 04 Feb '19

04 Feb '19

Hi all - I have notes that include improvements to tcw22 from the latest release experience. (The Raven...) Should I go ahead and edit? what is the protocol? --elli

2 3

Re: [Tei-council] dataSpec content
by James Cummings 03 Feb '19

03 Feb '19

If I understand Raff's suggestion correctly, then I would support the restrictive approach to only allow users possibilities of making dataTypes that 'Make Sense'. If they want to do something so weird as put an elementRef into the content of a dataSpec then they clearly should understand it well enough to be hand-editing their ODD, and then explain to us why it should be allowed in RomaJS. (But generally, RomaJS doesn't have to do everything that is possible, but only what we recommend people do.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 02 February 2019 12:04 To: lou.burnard(a)retired.ox.ac.uk; TEI Council Subject: Re: [Tei-council] dataSpec content [Trying to channel Raff, who is probably still asleep.] 1. Actual content model (that Raff was discussing -- i.e., a model against which all of our current dataSpec/content elements are valid): ( dataRef* | valList | textNode | aDr | avL | atN ) aDr = element alternate { dataRef* } avL = element alternate { valList } atN = element alternate { textNode } 2. No, Raff was not suggesting any change to content models, only to his user interface in RomaJS. But now that you point it out, it would probably make sense to disallow at least <empty>, <anyElement>, <elementRef>, & <classRef>, and probably even <macroRef> from the <content> of a <dataSpec>. > Firstly, I dont understand your pseudocode content model. Does it > mean the same as the following: > > <alternate minOccurs="1" maxOccurs="undefined"> > <elementRef key="dataRef"/> > <elementRef key="valList"/> > <elementRef key="textNode"/> > </alternate> > > > Are you proposing to change the current content model of <content> > or of <dataSpec> ? > > In either case, I suggest defining a class model.dataSpecPart might > help. > > Or is it just about how selective your interface should be in what > it permits, perhaps as a not-so-subtle way of avoiding the > question? > > Current practice in defining dataSpecs is constrained by what was > done in P4: I re-used the <content> element here because we also > used it to define the expansion of macroSpecs (i.e parameter > entities) back in the day, but that's a historical explanation. > This over-generates, as you rightly say: it's not at all clear what > it might mean to put e.g. an elementRef into the content of a > dataSpec! _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

3 2

Re: [Tei-council] Stylesheets: rub out tei: prefix?
by James Cummings 02 Feb '19

02 Feb '19

Syd: To clarify, yes #2, get rid of them, but I'm not going to worry about it too much if you don't. ;-) Apologies for my confusion. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Syd Bauman <s.bauman(a)northeastern.edu> Sent: 02 February 2019 12:21 To: Lou Burnard; TEI Council; Martin Holmes Subject: Re: [Tei-council] Stylesheets: rub out tei: prefix? Four of you have still not voted. summary so far ------- -- --- 1) I very much want to get rid of the "tei:" prefix in XPaths 2) I prefer to get rid of them, but don't care much 3) It makes no difference to me, mate 4) I prefer to keep them, but don't care much 5) I very much want to keep the "tei:" prefix in XPaths SB: 0 (My vote is weighted :-) EB: 1 LB: 4 ? HC: JC: 2 (Said "4", but seems to have meant "2") MH: 1 VJ: EM: 4 MS: 5 PS: 5 SS: MT: RV: 5 That's a total of 27 in 9 votes, for an average of exactly 3! Thus the remaining 4 votes will likely be the deciding ones ... what a nail-biter! _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Re: [Tei-council] Stylesheets: rub out tei: prefix?
by James Cummings 02 Feb '19

02 Feb '19

Just to point out an option that Syd didn't suggest: - Use both prefix and xpath-default-namespace. This gives you the tei: prefix when you want to use it, but if you forget, defaults to the TEI namespace anyway. This is, of course, a _horrible_ idea for which I hope there is no support. Except if we were adopting a process of gradual conversion from prefixed to not. However, I would point out that xpath-default-namespace is used throughout the Stylesheets repository so that we are *already* inconsistent in our practice. So really we're already doing my horrible idea, though not commonly in a single stylesheet but more metaphorically throughout the repository as a whole. c.f. https://github.com/TEIC/Stylesheets/search?q=xpath-default-namespace&unscop… Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 04 January 2019 19:14:00 To: Elisa Beshero-Bondar; Lou Burnard Cc: TEI Council; Martin Holmes Subject: Re: [Tei-council] Stylesheets: rub out tei: prefix? Hi all, I usually use prefixes. So I would prefer option 5. Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von Elisa Beshero-Bondar Gesendet: Freitag, 4. Januar 2019 19:48 An: Lou Burnard <lou.burnard(a)retired.ox.ac.uk> Cc: TEI Council <tei-council(a)lists.tei-c.org>; Martin Holmes <mholmes(a)uvic.ca> Betreff: Re: [Tei-council] Stylesheets: rub out tei: prefix? And it's one more thing to forget! Life's challenging enough. When you have an opportunity to use a default namespace, why not use it? E :) On Fri, Jan 4, 2019 at 1:47 PM Lou Burnard <lou(a)ox.ac.uk<mailto:lou@ox.ac.uk>> wrote: (which is what I do, btw) they're only pesky if you forget them! On 04/01/2019 18:45, Mylonas, Elli wrote: you can always abbreviate to a single letter... On Fri, Jan 4, 2019 at 1:43 PM Elisa Beshero-Bondar <ebb8(a)pitt.edu<mailto:ebb8@pitt.edu>> wrote: I will take this opportunity to express surprise that so many of you like those pesky prefixes! Forgetting to use them drives me mad--think of occasions in writing XSLT where it's just so many extra keystrokes and one thing more to debug. Anyway, happy new year, you namespace-prefix-lovers! Elisa On Fri, Jan 4, 2019 at 1:41 PM Mylonas, Elli <elli_mylonas(a)brown.edu<mailto:elli_mylonas@brown.edu>> wrote: Hi all - I tend to prefer tp see namespaces expressed explicitly. But agree with James that Syd is the one groping around in the code. So 4 or 5 for me. --elli On Fri, Jan 4, 2019 at 11:44 AM James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>> wrote: Hi all, I simultaneously agree that explicitness is good and tend to use xpath-default-namespace all the time myself. I also remember learning from Sebastian that you *always* check namespaces first when something goes wrong. ;-) But since ODDs are always written in TEI (even non-TEI ODDs), it makes sense to me to use default namespace for TEI. I'd vote 4. Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Lou Burnard <lou(a)OX.AC.UK<mailto:lou@OX.AC.UK>> Sent: 04 January 2019 15:07:27 To: Raffaele Viglianti; Elisa Beshero-Bondar Cc: Peter Stadler; Lou Burnard; TEI Council; Martin Holmes Subject: Re: [Tei-council] Stylesheets: rub out tei: prefix? FWIW, I agree with Raffaele and Peter in preferring the explicitness and clarity of a prefix. Sebastian always used to say that whenever a stylesheet didn't behave as expected, it was a namespace problem. But if Syd is producing a new version, clearly he has the right to make whatever cosmetic changes he is more comfortable with. Might be a good idea to keep the old version around for a while though, just to check nothing has been broken by such changes, if I may state the obvious. On 04/01/2019 11:44, Raffaele Viglianti wrote: I always use prefixes. I think it helps with clarity and feels more rigorous/consistent. So my preference would be 5. Raff On Fri, Jan 4, 2019, 5:09 AM Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com> wrote: By the way, I think there’s a way to do it in pure Schematron, but I am not sure (have to check) if it can be done in the ODD context. If I remember right for pure Schematron at least, the question is whether you have to set the prefix on the Schematron elements or the TEI ones. Elisa Sent from my iPhone > On Jan 4, 2019, at 5:05 AM, Elisa Beshero-Bondar <ebbondar(a)gmail.com<mailto:ebbondar@gmail.com>> wrote: > > Having worked with setting default namespaces rather a lot in various contexts (XSLT, XQuery, Schematron, I vote enthusiastically for 1). This really just amounts to a change that reduces verbosity, as Syd indicates, but also reflects the default centrality of the TEI in the Stylesheets anyway. And it is a pain to have to remember the default prefix all the time when we gave to edit. > > Elisa > > Sent from my iPhone > >> On Jan 4, 2019, at 3:54 AM, Peter Stadler <pstadler(a)mail.uni-paderborn.de<mailto:pstadler@mail.uni-paderborn.de>> wrote: >> >> I honestly prefer the verbosity of 5) — and I don’t think these XPath expressions can be significantly simplified nor compressed by removing those namespace prefixes. >> But just to make double sure: This is just a (proposed) cosmetic change due to your personal preference, right? This wouldn’t be bad thing, though, and I think you deserve to do it your way since you are the ODD one :) >> >> Cheers >> Peter >> >>> Am 04.01.2019 um 02:18 schrieb Syd Bauman <s.bauman(a)northeastern.edu<mailto:s.bauman@northeastern.edu>>: >>> >>> The current odd2odd.xsl (like most of the stylesheets) uses the >>> explicitly bound namespace prefix "tei:" in XPaths. I am inclined to >>> use @xpath-default-namespace and get rid of them. I think our XPaths >>> are often already long enough to wrap around even a wide screen >>> twice, and things like "ancestor::tei:teiHeader" are just harder to >>> read. >>> >>> Please vote (fast): >>> 1) I very much want to get rid of the "tei:" prefix in XPaths >>> 2) I prefer to get rid of them, but don't care much >>> 3) Makes no difference to me, mate >>> 4) I prefer to keep them, but don't care much >>> 5) I very much want to keep the "tei: prefix in XPaths >>> >>> In case you're curious, there are approximately >>> 517 tei: >>> 38 rng: >>> 15 xs: >>> 5 a: >>> 4 xml: >>> 2 sch: >>> prefixes in odd2odd.xsl. (Looking only in attr values.) >>> _______________________________________________ >>> Tei-council mailing list >>> Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> >>> http://lists.lists.tei-c.org/mailman/listinfo/tei-council >> >> _______________________________________________ >> Tei-council mailing list >> Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> >> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu<mailto:ebb8@pitt.edu> Development site: http://newtfire.org<http://newtfire.org/> _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council -- Elisa Beshero-Bondar, PhD Director, Center for the Digital Text | Associate Professor of English University of Pittsburgh at Greensburg | Humanities Division 150 Finoli Drive Greensburg, PA 15601 USA E-mail: ebb8(a)pitt.edu<mailto:ebb8@pitt.edu> Development site: http://newtfire.org<http://newtfire.org/>

3 2

dataSpec content
by Raffaele Viglianti 02 Feb '19

02 Feb '19

Hello Council and Lou, As I'm working on supporting dataSpec in RomaJS, I've been thinking about what an interface for defining a datatype's content would look like. I did a quick survey of teidata.* source files and it looks like <content> is limited to this pseudocode content model (I hope it makes sense): (dataRef* | valList | textNode) | alternate { (dataRef* | valList | textNode) } I don't see any use of <sequence>, <empty>, <anyElement>, other *Ref elements besides dataRef, or multiple <valList>s and <textNode>s. This makes perfect sense to me. The question is: should I limit the interface to allow users to build only datatypes that "make sense", or allow more flexibility? The advantage of a more restrictive approach, which I support, is that the interface can be more to the point. If we wanted more flexibility, I'd implement the Blockly interface that is currently in use for <elementSpec>s. But I think it might discourage people from defining good datatypes as it's not immediately obvious how to use it. I wanted to run this by the group to make sure I analyzed this correctly. Does this make sense? Also a quick reminder to fill the Doodle for a call in the second week of February if you're interested in participating https://doodle.com/poll/8p7exq3vptpb8g9t Thank you! Raff

3 3

Re: [Tei-council] OxGarage and Roma updated
by James Cummings 01 Feb '19

01 Feb '19

That sounds reasonable (though the argument that John Unsworth originally made for paying our way by using commercially purchased systems, and not relying on handouts dependent on particular projects, institutions, and individuals, also sounds reasonable). I'd humbly suggest, if they are willing, that the maintainers of parts of our infrastructure like those hosting Jenkins, OxGarage, and developer of new bit of infrastructure RomaJS should all be part of that larger group. (But understand that they're busy.) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Scholger, Martina (martina.scholger(a)uni-graz.at) <martina.scholger(a)uni-graz.at> Sent: 01 February 2019 06:39 To: James Cummings; TEI Council Cc: Martin Holmes Subject: AW: [Tei-council] OxGarage and Roma updated Hi, The reasoning behind moving the servers to HumaNum is that the current ADHO servers are rented from a commercial supplier whereas the HumaNum servers are actually maintained by a university based DH institution … I think. I would suggest that we decide on who of us should get involved with this process on behalf of the Council (checking requirements, etc.). Then I would write to the Board-Council list to suggest a dedicated call with Laurent, Luis and whoever will represent the Council and the Board. Meanwhile, I will ask Luis how far the process already is. Mahna Mahna, Martina Von: Tei-council <tei-council-bounces(a)lists.tei-c.org> Im Auftrag von James Cummings Gesendet: Donnerstag, 31. Januar 2019 16:15 An: TEI Council <tei-council(a)lists.tei-c.org> Cc: Martin Holmes <mholmes(a)uvic.ca> Betreff: Re: [Tei-council] OxGarage and Roma updated Out of curiosity, what is the benefit of having the hosting with HumaNum[1] as opposed to ADHO? Doesn't this shift our eggs out of one basket and into another? Or is it cloud-based hosting with redundancy or something? Not arguing against it, just curious as to what it gets us. (It might be better, for example, to have a mirrored site or geographically dispersed copies for redundancy and load-balancing, but still seems like overkill to me.) Many thanks, James [1] Whenever I say this in my head I hear the muppets version of Mahna Mahna. https://en.wikipedia.org/wiki/Mah_N%C3%A0_Mah_N%C3%A0 -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Hugh Cayless <philomousos(a)gmail.com<mailto:philomousos@gmail.com>> Sent: 31 January 2019 12:21:26 To: Peter Stadler Cc: TEI Council; Martin Holmes Subject: Re: [Tei-council] OxGarage and Roma updated There’s an (exploratory I think at this stage) effort underway to move the website hosting to HumaNum. I’m not sure what the implications are for our other services. Probably we should schedule a meeting with the interested parties before things progress much further. That message should come from Martina as Chair I think. > On Jan 31, 2019, at 06:28, Peter Stadler <stadler(a)edirom.de<mailto:stadler@edirom.de>> wrote: > > My ultimate goal would be for the tei user to be member of the Unix group ‚docker‘ — that would allow us to restart those containers. We’ll have to sort that out with the new ADHO sysadmin who will hopefully be installed in the near future. > > Another option would be to move these services into some AWS or Azure (or whatheveyou) cloud. Kathryn was suggesting (in her recent mail to TEI-L) that "we have already begun to make significant changes to the TEI-C infrastructure in response to last summer’s server fail. Thanks to outgoing Board member Laurent Romary, our webmaster Luis Meneses is working with HumaNum to establish a more reliable foundation for our data.“ — I don’t know what that means?!? Has anyone some insights? > > Best > Peter > >> Am 31.01.2019 um 12:22 schrieb James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>>: >> >> >> That is good! Is there a way to have it so that the tei user on tei-c.org has the ability to restart these services? >> >> Many thanks, >> James >> >> -- >> Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> >> Senior Lecturer in Late-Medieval Literature and Digital Humanities >> School of English, Newcastle University >> From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Peter Stadler <stadler(a)edirom.de<mailto:stadler@edirom.de>> >> Sent: 31 January 2019 09:28:56 >> To: TEI Council >> Cc: Martin Holmes >> Subject: [Tei-council] OxGarage and Roma updated >> >> Dear all, >> >> I just had an excellent admin session with Christof Schöch (many thanks!) and we managed to restart the Roma and OxGarage services. Both should now run with the current Stylesheets and TEI sources. >> >> So, OxGarage, Roma, and the Debian packages should be updated to the current release (please test!), let alone the Oxygen plugin still needs some attention. >> >> Best >> Peter > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> > http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org<mailto:Tei-council@lists.tei-c.org> http://lists.lists.tei-c.org/mailman/listinfo/tei-council

4 3

Re: [Tei-council] OxGarage and Roma updated
by James Cummings 31 Jan '19

31 Jan '19

Out of curiosity, what is the benefit of having the hosting with HumaNum[1] as opposed to ADHO? Doesn't this shift our eggs out of one basket and into another? Or is it cloud-based hosting with redundancy or something? Not arguing against it, just curious as to what it gets us. (It might be better, for example, to have a mirrored site or geographically dispersed copies for redundancy and load-balancing, but still seems like overkill to me.) Many thanks, James [1] Whenever I say this in my head I hear the muppets version of Mahna Mahna. https://en.wikipedia.org/wiki/Mah_N%C3%A0_Mah_N%C3%A0 -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk Senior Lecturer in Late-Medieval Literature and Digital Humanities School of English, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Hugh Cayless <philomousos(a)gmail.com> Sent: 31 January 2019 12:21:26 To: Peter Stadler Cc: TEI Council; Martin Holmes Subject: Re: [Tei-council] OxGarage and Roma updated There’s an (exploratory I think at this stage) effort underway to move the website hosting to HumaNum. I’m not sure what the implications are for our other services. Probably we should schedule a meeting with the interested parties before things progress much further. That message should come from Martina as Chair I think. > On Jan 31, 2019, at 06:28, Peter Stadler <stadler(a)edirom.de> wrote: > > My ultimate goal would be for the tei user to be member of the Unix group ‚docker‘ — that would allow us to restart those containers. We’ll have to sort that out with the new ADHO sysadmin who will hopefully be installed in the near future. > > Another option would be to move these services into some AWS or Azure (or whatheveyou) cloud. Kathryn was suggesting (in her recent mail to TEI-L) that "we have already begun to make significant changes to the TEI-C infrastructure in response to last summer’s server fail. Thanks to outgoing Board member Laurent Romary, our webmaster Luis Meneses is working with HumaNum to establish a more reliable foundation for our data.“ — I don’t know what that means?!? Has anyone some insights? > > Best > Peter > >> Am 31.01.2019 um 12:22 schrieb James Cummings <James.Cummings(a)newcastle.ac.uk>: >> >> >> That is good! Is there a way to have it so that the tei user on tei-c.org has the ability to restart these services? >> >> Many thanks, >> James >> >> -- >> Dr James Cummings, James.Cummings(a)newcastle.ac.uk >> Senior Lecturer in Late-Medieval Literature and Digital Humanities >> School of English, Newcastle University >> From: Tei-council <tei-council-bounces(a)lists.tei-c.org> on behalf of Peter Stadler <stadler(a)edirom.de> >> Sent: 31 January 2019 09:28:56 >> To: TEI Council >> Cc: Martin Holmes >> Subject: [Tei-council] OxGarage and Roma updated >> >> Dear all, >> >> I just had an excellent admin session with Christof Schöch (many thanks!) and we managed to restart the Roma and OxGarage services. Both should now run with the current Stylesheets and TEI sources. >> >> So, OxGarage, Roma, and the Debian packages should be updated to the current release (please test!), let alone the Oxygen plugin still needs some attention. >> >> Best >> Peter > > _______________________________________________ > Tei-council mailing list > Tei-council(a)lists.tei-c.org > http://lists.lists.tei-c.org/mailman/listinfo/tei-council _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1