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

objectName/listObject/object/idGrp and other changes
by James Cummings 26 Oct '18

26 Oct '18

Hi all, I've put a summary of the locations for testing of the various elements related to adding the object element (to provide descriptions of real or fictional objects) on the github issue at: https://github.com/TEIC/TEI/issues/327#issuecomment-433548949 with links to the reference pages, first draft of Guidelines prose (needs more work), etc. I made minor changes to some descriptions other elements (like physDesc or msContents) to include 'or other object' to make them usable for <object>. I wasn't doing a full build locally (just generating Relax NG schema to test) and so when checking into Jenkins I had a variety of errors pop up that I mention now just for shared experience. All fairly trivial: - ambiguous content models. I'd accidentally included listObject and model.objectLike (object, listObject) in the content model of listObject and sensibly it pointed out that would be ambiguous. - duplicate xml:id's -- I have (for now) used the same example in the object/listObject and Guidelines prose, and of course the xml:id's were duplicated so I had to go and change them -The most fun error was when I put in a commit message that it was correcting an error. Jenkins sees the word 'error' in its output and assumes this must mean there is an error and so fails the job overall! ;-) Needed: - Suggestions of some other named objects for examples - More and better examples, especially less anglo/western - More prose for the Guidelines - Proofreading corrections - Any problems... Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University

1 0

Re: [Tei-council] Council and Stylesheets Teleconferences
by James Cummings 26 Oct '18

26 Oct '18

Hi all, Between filling out the doodle poll and us deciding the date I've had a commitment that I can't move come up on the evening of 16 November, so will have to miss that meeting. My apologies. 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: 25 October 2018 15:21:51 To: tei-council(a)lists.tei-c.org Subject: [Tei-council] Council and Stylesheets Teleconferences Dear all, I added the dates for the Council and Stylesheets meetings to our shared google calendar. I hope I did not mix anything up. Council meetings (alternating 3rd Monday 13Z and 3rd Friday 20Z a month) Fri, 16 November 2018, 20Z Mon, 17 December 2018, 13Z Fri, 18 January 2019, 20Z Mon, 18 February 2019, 13Z Fri, 15 March 2019, 20Z Mon, 15 April 2019, 13Z Fri, 17 May 2019, 20Z Mon, 17 June 2019, 13Z Stylesheets meetings (alternating 3rd Monday 13Z and 3rd Friday 20Z a month, opposite of Council meeting) Mon, 19 November 2018, 13Z Fri, 21 Dezember 2018, 20Z Mon, 21 January 2019, 13Z Fri, 15 February 2019, 20Z Mon, 18 March 2019, 13Z Fri, 19 April 2019, 20Z Mon, 20 May 2019, 13Z Fri, 21 June 2019, 20Z Best wishes, Martina

1 0

Re: [Tei-council] Tokyo Per Diem
by James Cummings 26 Oct '18

26 Oct '18

Hi Syd, My recollection was that we used the 70% of the USA rate when in the USA and not externally because the rate often was misjudged outside... but it may be that I was entirely reversed on that recollection. Maybe it was the reverse. I honestly am not sure and haven't found any documentation on it. I've submitted mine already but happy to use whatever Hugh says is right. ;-) 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 Syd Bauman <s.bauman(a)northeastern.edu> Sent: 25 October 2018 18:27:29 To: TEI Council Subject: Re: [Tei-council] Tokyo Per Diem I came at it from a different direction, but get the same result as RV: The US Department of State Meals & Incidentals per diem rate for Tokyo is $227. (RV went to gsa.gov; I went to state.gov.) But I have a recollection that we are supposed to use 70% of that rate,[1] but cannot find documentation which says that, or which gives the division into breakfast, lunch, and dinner. RV, where did you find it? Anyone else know where it is? The documentation at https://wiki.tei-c.org/index.php/Travel_Reimbursement_Procedures_for_Counci… does not include this information. Notes ----- [1] Which would be $158.90, which is still an awful lot of money for one day of eating in Tokyo, at least where we were. Unless I hear otherwise, that's what I'm planning to use. _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

1 0

Council and Stylesheets Teleconferences
by Scholger, Martina (martina.scholger＠uni-graz.at) 26 Oct '18

26 Oct '18

Dear all, I added the dates for the Council and Stylesheets meetings to our shared google calendar. I hope I did not mix anything up. Council meetings (alternating 3rd Monday 13Z and 3rd Friday 20Z a month) Fri, 16 November 2018, 20Z Mon, 17 December 2018, 13Z Fri, 18 January 2019, 20Z Mon, 18 February 2019, 13Z Fri, 15 March 2019, 20Z Mon, 15 April 2019, 13Z Fri, 17 May 2019, 20Z Mon, 17 June 2019, 13Z Stylesheets meetings (alternating 3rd Monday 13Z and 3rd Friday 20Z a month, opposite of Council meeting) Mon, 19 November 2018, 13Z Fri, 21 Dezember 2018, 20Z Mon, 21 January 2019, 13Z Fri, 15 February 2019, 20Z Mon, 18 March 2019, 13Z Fri, 19 April 2019, 20Z Mon, 20 May 2019, 13Z Fri, 21 June 2019, 20Z Best wishes, Martina

2 1

Tokyo Per Diem
by Raffaele Viglianti 25 Oct '18

25 Oct '18

Hi folks, PSA about the per diem in Tokyo: US Dept. of State rate for Meal and Incidental Expense rate in Tokyo is $227 The breakdown (source: https://www.gsa.gov/travel/plan-book/per-diem-rates/fy2018-mie-breakdown#1h ): Breakfast: 34 Lunch: 57 Dinner: 91 Incidentals: 45 (but remember we're supposed to keep this under 20 or submit receipts) Syd (and others), which meals did you pay for the group? We had fewer lunches / dinners together this year IIRC. I covered the okonomiyaki dinner on 2018/09/07 with council members: RV (+1), SS, JC, EBB. Hope everyone had smooth travel back home! Raff

4 6

Reminder: Scheduling Spring F2F
by Scholger, Martina (martina.scholger＠uni-graz.at) 25 Oct '18

25 Oct '18

Dear Council, please fill out the doodle for the Spring F2F meeting in case you haven't done yet: https://doodle.com/poll/yp3uucnqmmiqyc9v Thanks! Best wishes, Martina

1 0

Rep: TEI workshop at Assyriologists conference
by Vanessa Bigot-Juloux 23 Oct '18

23 Oct '18

Dear Martina, Dear colleagues, I had a look at the minutes and saw that Vanessa added an item to the agenda that I missed during the meeting, sorry for that! No worries--I have added it belatedly. Regarding TEI workshop proposal: We haven’t received a call of session yet, so it is just something I would like to suggest to the organizers of this International conference. I think it can be a good opportunity to introduce TEI to neophytes. A suggestion of TEI workshop for Assyriologists which needs to be improved of course: - Morning session, TEI intensive overview based from Assyriological data: * What is TEI? * How TEI can help Assyriologists to improve their research wether it’s for philology, paleography, anthropology or other archaeological purposes (including a practical example with a list of goals for a specific project in order to be used (later during the morning session) to look for the good <elements> and @attributes). * What must a TEI practitioner need to know (TEI, ODD, XPath, XSLT, CSS) and why? * Short pratical examples: TEI (teiCorpus), XPath, XSLT (via Oxygen + preview in a browser). * How to read/use the guidelines (1) (used simultaneously with the practical examples). - Afternoon session: * How to read/use the guidelines (2). * What software to use and where to find assistance regarding this software? * Overview of TEI community and how to use Github in order to ask assistance to TEI community. * First step (suggestion to TEI tech council) to neophyte: TEI online mentoring, who, why and how? As for the morning session, I suggest working on a few practical examples (very short) that participants will send prior to the workshop in order to allow them to have a better idea of how TEI can help them. In addition, on a handout: a list of univ. who propose TEI/Xpath/XSLT training and online course (i.e.: Marjorie and Elena online training). After the sessions, I suggest giving a short questionnaire in order to list the needs of Assyriologists and how we can improve our guidelines/assistance to them. What do you think? Of course it means I’ll need support for this intensive day—from my university (i.e. Peter Stokes if he’s available during summer time) or a TEI tech council colleague (in Europe?). In advance, thanks for your kind advices. Best, Vanessa Le 23 oct. 2018 à 00:07, Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> a écrit : Dear Vanessa and all, I had a look at the minutes and saw that Vanessa added an item to the agenda that I missed during the meeting, sorry for that! It is about the TEI workshop for ancient Near Eastern (ANE) scholars during the international conference of Assyriologists in July (Paris) https://iaassyriology.com/past-rencontres/ Vanessa, is it something that we can discuss via email? Best wishes, Martina _______________________________________________ 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 2

TEI workshop at Assyriologists conference
by Scholger, Martina (martina.scholger＠uni-graz.at) 23 Oct '18

23 Oct '18

Dear Vanessa and all, I had a look at the minutes and saw that Vanessa added an item to the agenda that I missed during the meeting, sorry for that! It is about the TEI workshop for ancient Near Eastern (ANE) scholars during the international conference of Assyriologists in July (Paris) https://iaassyriology.com/past-rencontres/ Vanessa, is it something that we can discuss via email? Best wishes, Martina

1 0

Scheduling Spring F2F
by Scholger, Martina (martina.scholger＠uni-graz.at) 22 Oct '18

22 Oct '18

Dear all, here is our doodle poll for scheduling the Spring F2F meeting: https://doodle.com/poll/yp3uucnqmmiqyc9v Our meeting is supposed to be three days. I hope we will find three days in a row, where everyone has time. Please vote! Best wishes, Martina

1 0

call in 30 minutes
by Scholger, Martina (martina.scholger＠uni-graz.at) 22 Oct '18

22 Oct '18

Hi all, we start our call in 30 minutes. See the agenda: https://docs.google.com/document/d/1n_Zo-s-PQeMCKwJPmGYbs0F9CMD0VcQe4Vie_Yo… Hangouts: https://hangouts.google.com/hangouts/_/brown.edu/teicouncil Best, Martina

2 1

open issues
by Scholger, Martina (martina.scholger＠uni-graz.at) 19 Oct '18

19 Oct '18

Dear all, I've put the issues that we skipped last time into the agenda for Monday. Maybe you'll have time to look at one or the other: * https://github.com/TEIC/TEI/issues/1795 - Language of Schematron messages where @role="nonfatal" and @role="warning" * Related: Issue with merging https://github.com/TEIC/TEI/issues/1621 into dev branch--apparently something breaks the Jenkins build--investigating. * https://github.com/TEIC/TEI/issues/1707 : EB: quick update on measurement: Naoki's new sample code based on Tokyo decisions. * https://github.com/TEIC/TEI/issues/1805 - Suggestion for new uniHan element * https://github.com/TEIC/TEI/issues/1756 - event should have ptr and idno in its content model Best wishes, Martina

1 0

Next call: October 22
by Scholger, Martina (martina.scholger＠uni-graz.at) 18 Oct '18

18 Oct '18

Dear all, our next call is on Monday, October 22 from 09:00-10:30 EDT / 14-15:30 BST / 15-16:30 CEST. Please add your topics to the agenda: https://docs.google.com/document/d/1n_Zo-s-PQeMCKwJPmGYbs0F9CMD0VcQe4Vie_Yo… This is the hangouts link: https://hangouts.google.com/hangouts/_/brown.edu/teicouncil Best wishes, Martina Martina Scholger Zentrum für Informationsmodellierung Austrian Centre for Digital Humanities Universität Graz A-8010 Graz | Elisabethstraße 59/III +43 316 380 2291 martina.scholger(a)uni-graz.at<mailto:martina.semlak@uni-graz.at> http://informationsmodellierung.uni-graz.at<http://informationsmodellierung.uni-graz.at/> | http://gams.uni-graz.at<http://gams.uni-graz.at/> Chair of the TEI Technical Council | http://www.tei-c.org/ Institut für Dokumentologie und Editorik e.V. | https://www.i-d-e.de/

1 0

Re: [Tei-council] thinking about oXygen
by James Cummings 15 Oct '18

15 Oct '18

Hi Peter, I guess that is a more reasoned approach. I'm not against it as a way forward, but if the money isn't too much (we don't know yet and how do we define 'much') and it helps a lot of people (again we don't really know, but certainly suspect it will), then it does seem reasonable. I'd be more concerned if it was taking a lot of time of council members. ;-) Many thanks, James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Peter Stadler <pstadler(a)mail.uni-paderborn.de> Sent: 12 October 2018 17:09:45 To: James Cummings Cc: Martin Holmes; Syd Bauman; TEI Council Subject: Re: [Tei-council] thinking about oXygen I’d like to see Alex’ response on how much it would cost and some estimation on how easy it would then be to maintain. I completely agree with Martin that the main motivation is to support older oXygen versions (which is common with our users, AFAIK). Finally, I think that money would be wisely spent, i.e. it shouldn’t be much but plenty of people will benefit (saying this without knowing any statistics …). Best Peter Am 12.10.2018 um 18:02 schrieb James Cummings <James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk>>: I'm increasingly of the opinion that our provision of the oxygen-tei framework is an optional extra and that it should just keep pace with the current version of the TEI and the current release of oXygen. If changes in oXygen mean that older version of it are no longer supported, so be it. I say that as someone who now doesn't have an institutional subscription to oXygen. I'm not saying that is the fairest or best decision for overall impact and outreach, but it might be the easiest in terms of managing our meagre time resources. Willing to be convinced to change my mind though. ;-) James -- Dr James Cummings, James.Cummings(a)newcastle.ac.uk<mailto:James.Cummings@newcastle.ac.uk> School of English Literature, Language, and Linguistics, Newcastle University ________________________________ From: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> on behalf of Martin Holmes <mholmes(a)uvic.ca<mailto:mholmes@uvic.ca>> Sent: 12 October 2018 16:20:34 To: s.bauman(a)northeastern.edu<mailto:s.bauman@northeastern.edu>; TEI Council Subject: Re: [Tei-council] thinking about oXygen The ticket Alex raised has all the details: <https://github.com/TEIC/oxygen-tei/issues/27> I don't think I can explain it any better than that. My sense is that we're basically faced with: 1. Abandoning support for older versions of Oxygen in order to provide a fully-working interface with support for all the new features in the Oxygen interface in current versions. 2. Creating special tags for every version of Oxygen in which new features are introduced, and building a separate version of the plugin for each of those tags every time we build, with every build requiring the use of its own version of the oxygen.jar file. I don't like either of these options, frankly. #1 is bad because the only reason for maintaining the plugin at all is that people with older versions of Oxygen can keep their TEI and Stylesheets code up to date. #2 is a potential nightmare from the maintenance and bugfixing point of view. What happens if one particular version fails to build? Do we release all the other versions and not that one, or do we hold them all back till the bug is fixed? But the main problem is that we no longer have anyone with any expertise regarding the Oxygen plugin. A few years ago I taught myself enough about it to write a build file to create the various versions we currently maintain (the stable one, the bleeding-edge one, and the release one). I don't remember enough to feel confident about doing any of this work right now, and I don't have time to re-learn what I used to know (which probably wasn't enough anyway). Really, we need two or three people to take a deep dive into this and take responsibility for it. At the Council meeting, though, I think Magda was tasked with asking Alex if he would do the initial setup for us as a paid job. Cheers, Martin On 2018-10-11 09:29 AM, Syd Bauman wrote: > First, hope Michael didn't beat you up too badly, Sarah. > > Back in late Sep when we did a Stylesheets release we agreed to defer > a release of the oXygen plug-in for a bit. So we probably need to > have a discussion about what we are going to do. > > As a reminder, the results of this summer's survey on oXygen usage > is: > > | count majorVersion > | ----- ------------ > | 12 17 > | 6 18 > | 2 16 > | 2 14 > | 1 20 > | 1 15 > | 1 19 > > And of the 5 people using versions 16 or older, 2 or 3 of 'em hope we > continue to support the older version. > > Could Martin or James or someone else who understands this better > than I do kick off the discussion with a summary of the problem(s)? > _______________________________________________ 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

1 0

Re: [Tei-council] thinking about oXygen
by James Cummings 12 Oct '18

12 Oct '18

I'm increasingly of the opinion that our provision of the oxygen-tei framework is an optional extra and that it should just keep pace with the current version of the TEI and the current release of oXygen. If changes in oXygen mean that older version of it are no longer supported, so be it. I say that as someone who now doesn't have an institutional subscription to oXygen. I'm not saying that is the fairest or best decision for overall impact and outreach, but it might be the easiest in terms of managing our meagre time resources. Willing to be convinced to change my mind though. ;-) 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 Martin Holmes <mholmes(a)uvic.ca> Sent: 12 October 2018 16:20:34 To: s.bauman(a)northeastern.edu; TEI Council Subject: Re: [Tei-council] thinking about oXygen The ticket Alex raised has all the details: <https://github.com/TEIC/oxygen-tei/issues/27> I don't think I can explain it any better than that. My sense is that we're basically faced with: 1. Abandoning support for older versions of Oxygen in order to provide a fully-working interface with support for all the new features in the Oxygen interface in current versions. 2. Creating special tags for every version of Oxygen in which new features are introduced, and building a separate version of the plugin for each of those tags every time we build, with every build requiring the use of its own version of the oxygen.jar file. I don't like either of these options, frankly. #1 is bad because the only reason for maintaining the plugin at all is that people with older versions of Oxygen can keep their TEI and Stylesheets code up to date. #2 is a potential nightmare from the maintenance and bugfixing point of view. What happens if one particular version fails to build? Do we release all the other versions and not that one, or do we hold them all back till the bug is fixed? But the main problem is that we no longer have anyone with any expertise regarding the Oxygen plugin. A few years ago I taught myself enough about it to write a build file to create the various versions we currently maintain (the stable one, the bleeding-edge one, and the release one). I don't remember enough to feel confident about doing any of this work right now, and I don't have time to re-learn what I used to know (which probably wasn't enough anyway). Really, we need two or three people to take a deep dive into this and take responsibility for it. At the Council meeting, though, I think Magda was tasked with asking Alex if he would do the initial setup for us as a paid job. Cheers, Martin On 2018-10-11 09:29 AM, Syd Bauman wrote: > First, hope Michael didn't beat you up too badly, Sarah. > > Back in late Sep when we did a Stylesheets release we agreed to defer > a release of the oXygen plug-in for a bit. So we probably need to > have a discussion about what we are going to do. > > As a reminder, the results of this summer's survey on oXygen usage > is: > > | count majorVersion > | ----- ------------ > | 12 17 > | 6 18 > | 2 16 > | 2 14 > | 1 20 > | 1 15 > | 1 19 > > And of the 5 people using versions 16 or older, 2 or 3 of 'em hope we > continue to support the older version. > > Could Martin or James or someone else who understands this better > than I do kick off the discussion with a summary of the problem(s)? > _______________________________________________ Tei-council mailing list Tei-council(a)lists.tei-c.org http://lists.lists.tei-c.org/mailman/listinfo/tei-council

2 1

thinking about oXygen
by Syd Bauman 12 Oct '18

12 Oct '18

First, hope Michael didn't beat you up too badly, Sarah. Back in late Sep when we did a Stylesheets release we agreed to defer a release of the oXygen plug-in for a bit. So we probably need to have a discussion about what we are going to do. As a reminder, the results of this summer's survey on oXygen usage is: | count majorVersion | ----- ------------ | 12 17 | 6 18 | 2 16 | 2 14 | 1 20 | 1 15 | 1 19 And of the 5 people using versions 16 or older, 2 or 3 of 'em hope we continue to support the older version. Could Martin or James or someone else who understands this better than I do kick off the discussion with a summary of the problem(s)?

2 1

Next call: October 22
by Scholger, Martina (martina.scholger＠uni-graz.at) 12 Oct '18

12 Oct '18

Dear all, the best option for our next call is Monday, October 22 from 9:00-10:30 EDT, 14-15:30 BST, 15-16:30 CEST. This is the link to the agenda, please add your topics: https://docs.google.com/document/d/1n_Zo-s-PQeMCKwJPmGYbs0F9CMD0VcQe4Vie_Yo… Elli, please let me know if you can start the call. Best wishes, Martina

2 2

Re: [Tei-council] Spring F2F meeting
by James Cummings 12 Oct '18

12 Oct '18

Apologies for the delay in responding. To confirm, I'd be willing to host a council meeting here in Newcastle. I could also do so in future years if that was preferable. Venues: There are two possible venues: A) One is the city centre campus, for which I could find one or more meeting rooms, downtown has plenty of hotels, airbnb, restaurants and that sort of thing. B) The other possible venue would be about 9 miles out of the city centre (direct metro line) in either a hotel conference room (at charge) or the Dove Marine Laboratory. This is a research institution in a victorian building right on the beach in Cullercoats bay https://goo.gl/maps/cJLSCEX8jHS2, a short walk south is Tynemouth (lots of trendy restaurants, cafes, lovely ruined medieval priory). I've been to university workshops at the Dove and will investigate the rules for booking it. No idea if it is free then. There is also a 'Premier Inn' hotel with conference rooms in Whitley Bay right next to the iconic recently refurbished Spanish City building (mentioned in a Dire Straits song if you are into such trivia). Travel: Newcastle Airport is connected to the city by a quick, fairly inexpensive and frequent metro system (that goes out to the coast and covers the whole metropolis area between Newcastle, the coast, and Sunderland.) Newcastle Airport is usually 1 hop to most major interchanges (via Heathrow, Schiphol, etc.) Dates: As we're really far North (literally, Hadrian's wall used to run through Newcastle), then later is better in terms of weather. In terms of the university calendar the Easter Break is from Friday 29 March to Monday 29 April. Good Friday is 19 April, Easter Monday: 22 April. I only mention it because these are probably not good days to travel or find open restaurants for large groups. I'm busy in the week 1-5 April doing a TEI workshop. This actually presents an opportunity where we might have budget to help with the travel for 1 (or 2 max) council members if they were also teaching on that workshop. This would mean maybe having it sometime in 6 - 12 April. According to weather.com historically that is like 9-10C/48-50F around that time of year (and windy on the coast). Some random videos: University promotional ones https://www.youtube.com/watch?v=E3jR3NvU-TY https://www.youtube.com/watch?v=htlYW8RppWA https://www.youtube.com/watch?v=Okf1pmDkem8 Cullercoats bay with Dove Marine Laboratory in the middle, boring drone footage https://www.youtube.com/watch?v=9BKf4hZNWRM Whitley Bay and Tynemouth, better drone footage https://www.youtube.com/watch?v=Hn5nx6VIAhw Spanish City (during refurb) boring drone footage: <https://www.youtube.com/watch?v=K4dHu_t9ETM>https://www.youtube.com/watch?v=CxHW3j83IDY 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 Mylonas, Elli <elli_mylonas(a)brown.edu> Sent: 03 October 2018 23:23:52 To: TEI Council Subject: Re: [Tei-council] Spring F2F meeting I can host at Brown most of the spring term. Some better and some blackout dates: When students aren't here: Long weekend Feb 16-19 Spring break Mar 23-31 NOT POSSIBLE - April 4-5 best, --elli On Wed, Oct 3, 2018 at 4:05 PM Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> wrote: Dear all, picking up on the minutes from our last call I would ask everyone who offered to host the next Spring F2F meeting to confirm their willingness to do so and to set out the possibilities in terms of place and date before our next call. We should figure out what is feasible as soon as possible. We have offers from: Elli at Brown University in Providence James at Newcastle University Magdalena in Warsaw Raff at Folger Library in Washington D.C. Best wishes, Martina _______________________________________________ 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

6 6

Re: [Tei-council] oxgarage missing
by Peter Stadler 09 Oct '18

09 Oct '18

Hi Ian thanks for your immediate reaction! If I recall correctly, we regularly had some memory issues with OxGarage, thus restarting it every(?) night via a cron job. I don’t think that’s necessary, but we could improve it in a more docker-like way by adding a health check to the Dockerfile. Do you have some monitoring software which could read that information and restart the container if necessary? Best Peter > Am 04.10.2018 um 00:51 schrieb Ian Rifkin <irifkin(a)brandeis.edu>: > > Hi, > > Java heap memory issues in the log file. I restart the oxgarage docker and it seems to be back up and running. Peter, let me know if you think it was a fluke or if something needs to be adjusted. > > Thanks, > Ian > > On Wed, Oct 3, 2018 at 6:21 PM Peter Stadler <stadler(a)edirom.de> wrote: > Hi Nick, > > I can confirm that I’m unable to connect to oxgarage.tei-c.org, as well. > Seems to be a server issue and probably needs a restart of the service (which I can’t do, sadly) … > In the meantime, please use oxgarage2.tei-c.org. > > Thanks for reporting! > Peter > > >> Am 03.10.2018 um 21:42 schrieb Nick Thieberger <thien(a)UNIMELB.EDU.AU>: >> >> I'm getting '504 Gateway Time-out' on ox-garage, is there any update on its availability please? >> >> Thanks, >> Nick >> >> On Tue, 26 Jun 2018 at 01:43, Hugh Cayless <philomousos(a)gmail.com> wrote: >> I haven't heard anything about it yet, but it looks like OxGarage and Roma are back. >> >> Hugh >> >> On Mon, Jun 25, 2018 at 7:28 AM Hugh Cayless <philomousos(a)gmail.com> wrote: >> It looks to me like the site has been switched over to the new version that's been waiting in the wings for a while, but that none of the configuration for handling the Tools section has been set up. The good news is that OxGarage is still running, it's just temporarily inaccessible. I've emailed our sysadmin. I'm afraid I don't have the necessary permissions to actually fix (or even see) the web server configuration. >> >> Hugh >> >> On Mon, Jun 25, 2018 at 6:22 AM Toma Tasovac <ttasovac(a)humanistika.org> wrote: >> Hi, >> >> what happened to OxGarage? >> >> http://www.tei-c.org/oxgarage/ (which is the link given in the Tools dropdown menu) gives oops that page can't be found >> >> All best, >> Toma >> -- >> Belgrade Center for Digital Humanities >> http://humanistika.org >> > > > > -- > Ian Rifkin '04, MS '09 > Director of Data and Systems Integration > Brandeis University, Information Technology Services (ITS) > Email: irifkin(a)brandeis.edu | Phone: (781) 736-4216 | Fax: (781) 736-4577 > Learn more about our campus move to Workday

2 2

Monthly call
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Oct '18

09 Oct '18

Dear all, we still need to find a solution for our monthly call. Unfortunately there is no slot that suits all of us. I had again a closer look at our "best" options with 9 or 10 "yes/if need be" answers. This is it (initials in brackets indicate those members who voted "no, I can't make it"): Mon 13Z (VB, EB) Tue 19Z (MT, EB); 20Z (MT, HC); 21Z (MT, HC) Fri 19Z (MT, EB); 20Z (MT); 21Z (MT, HC) Narrowing this down to the smallest overlap of people who can't make it, Mon 13Z and Fri 20Z are remaining. Therefore, I suggest to alternate every month between Monday and Friday in order to enable everyone to at least attend once every second month. I created another doodle poll with dates in the 3rd and 4th week of October to set a starting date. Please vote! https://doodle.com/poll/vwdvmm67xztq4csk (I hope you can see it in your time zone) I am aware that this is hardly an ideal solution, but I don't see another option yet. Best wishes, Martina

2 1

Monthly call
by Scholger, Martina (martina.scholger＠uni-graz.at) 09 Oct '18

09 Oct '18

Dear all, looking at the doodle I am somewhat at a loss. There is no single date and time where everyone on the Council is available. The "best" we could do is Friday at 20:00Z, but Magdalena would not be able to join and three people would rather not. The next best would be Friday at 19:00Z, but with two people missing. I don't think that we should schedule a regular date where we already know that at least one person will not be able to make it. I would ask everyone to have one more look at the doodle and consider if you can possibly make more choices. Keep in mind that we are meeting just once a month. https://doodle.com/poll/kk9hsr6z9csxhkub If we can't find a common date that way, would it make a difference if the call would be just 60 instead of 90 minutes? Are there other suggestions to solve our dilemma? Best wishes, Martina

2 3

Travis ne Jenkins ne local
by Syd Bauman 05 Oct '18

05 Oct '18

The dev branch now has all the deprecations valid until 2018-10-01 removed, and its build working ala Travis. However, said build is not working in Jenkins (on either jenkins or jenkins2 -- for some reason the former does not have parsed console output, but it is the same error), and is working on my local system, after a fashion. The error on Jenkins, however, is completely mysterious. It has *nothing* to do with anything that I am aware of having changed. The ONVDL validation of Exemplars/tei_enrich.odd against Exemplars/tei_enrich.nvdl is failing with error: bad value for attribute "columns" where the value for @columns is "1", and thus is perfectly fine. I can, with some effort, reproduce this error on my local system. All of the @columns attrs in tei_enrich.odd are on elements in the teix: namespace, i.e. within <egXML>. I am pretty sure the only schema tei_enrich.nvdl runs against that namespace is tei_enrich-examples.rng. And lo and behold, when I look at that schema the definition of @columns of <layout> is obviously screwball: | <attribute name="columns"> | <a:documentation xmlns:a="http://relaxng.org/ns/compatibility/annotations/1.0">specifies | the number of columns per page</a:documentation> | <list> | <rng:empty xmlns:rng="http://relaxng.org/ns/structure/1.0"/> | </list> | </attribute> I poked around and found that the tei_enrich.odd file changes the definition of <layout> a teeny bit: | <elementSpec ident="layout" mode="change" module="msdescription"> | <attList> | <attDef ident="columns" mode="change" usage="req"/> | </attList> | </elementSpec> But that specification is in a paragraph of prose that essentially negates it: | <p>Note that if (as in the last example above) no value is given for | the <att>columns</att> attribute, the assumption is that there is a | single column of writing on each page. (And is incorrect, in that the prior example does have a value for layout/@columns.) So I claim that a) This is a Stylesheets issue. Somehow changing @columns to required has nuked its datatype, which is supposed to be ( data.count, data.count? ) b) The Enrich ODD has other problems, too I'm too tired now to do much more on this tonight.

4 5

cannot build
by Lou Burnard 04 Oct '18

04 Oct '18

I updated Stylesheets, and pulled the latest P5 sources, and ran "make clean; make" Everything worked up to the point where the "special purpose" validity checks began. At that point I got a shed load of annoying errors, starting with BUILD: Check validity with special-purpose XSL code, looking for bad links etc ANT_OPTS="-Xss2m -Xmx752m -Djava.awt.headless=true" ant -q -lib Utilities/lib/saxon9he.jar -f antbuilder.xml -DXSL=/usr/share/xml/tei/stylesheet validators [echo] Run Schematron script (normal part of Guidelines) [echo] Run Schematron script (Examples in Guidelines marked as valid) [echo] Run ad hoc XSLT validators BUILD SUCCESSFUL Total time: 27 seconds <Messages> <ERROR>Schematron error: The data.certaintyconstruct is outdated (as of 2018-10-01); ODD processors may ignore it, and its use is no longer supported [Test: @validUntil cast as xs:date ge current-date()] Location: /TEI[1]/text[1]/body[1]/div[1]/div[6]/macroSpec[1]</ERROR> <WARNING>Schematron warning: The data.certainty construct becomes outdated on 2018-10-01 [Test: @validUntil cast as xs:date ge $advance_warning_period] Location: /TEI[1]/text[1]/body[1]/div[1]/div[6]/macroSpec[1]</WARNING> [and so on for a few screens, concluding with] <WARNING>Schematron warning: The macro.anyXML construct becomes outdated on 2018-06-12 [Test: @validUntil cast as xs:date ge (current-date() + (60*xs:dayTimeDuration('P1D')))] Location: /TEI[1]/text[1]/body[1]/div[1]/div[4]/div[1]/specGrp[1]/macroSpec[7]</WARNING> > <ERROR>Schematron error: > Error: both the versionDate and xml:lang attributes on "remarks" are required when it is a child of "attDef". > [Test: not( @xml:lang and @versionDate )] Location: /TEI[1]/text[1]/body[1]/div[22]/div[3]/specGrp[1]/elementSpec[4]/attList[1]/attDef[1]/remarks[1]</ERROR> Makefile:185: recipe for target 'valid' failed make: *** [valid] Error 1 lou@foxglove:~/Public/TEI/P5$ Tell me, what have I done to deserve this?

3 6

Spring F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 04 Oct '18

04 Oct '18

Dear all, picking up on the minutes from our last call I would ask everyone who offered to host the next Spring F2F meeting to confirm their willingness to do so and to set out the possibilities in terms of place and date before our next call. We should figure out what is feasible as soon as possible. We have offers from: Elli at Brown University in Providence James at Newcastle University Magdalena in Warsaw Raff at Folger Library in Washington D.C. Best wishes, Martina

2 1

Re: [Tei-council] Stylesheets v7.46.0 released
by James Cummings 03 Oct '18

03 Oct '18

re: council responsibility. Council responsibility for stylesheets is for those that we use to generate the website and those that we use to process ODDs. Everything else is optional but nice for the community (IMHO) 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 Raffaele Viglianti <raffaeleviglianti(a)gmail.com> Sent: 02 October 2018 15:35:45 To: Peter Stadler Cc: tei-council(a)lists.tei-c.org; Martin Holmes Subject: Re: [Tei-council] Stylesheets v7.46.0 released I added a couple paragraphs to the document, let me know what you think. This conversation we're having echos the worry I expressed in my first email: > I don't know if stylesheets releases need to be announced on TEI-L, especially since we don't assemble a document listing changes besides a generated changelog. Perhaps the paragraph I added are enough, but it's easy to go down a rabbit hole. The Stylesheets are important, but it's still unclear how much of a responsibility council has towards them since our primary goal is maintaining and improving the TEI Guidelines. All best, Raff On Tue, Oct 2, 2018 at 8:18 AM Peter Stadler <stadler(a)edirom.de<mailto:stadler@edirom.de>> wrote: I agree that the current draft is not very helpful except for saying "there is a new release“. We should add a) the main motivation. It is unusual that we are doing a Stylesheets release out of sync with the Guidelines. AFAIK, the main motivation is Raff’s work on RomaJS and his need for p5subset.json, leading to various changes to odd2json.xsl in the Stylesheets repo. That need to be mentioned. @raff: could you elaborate a little bit on those changes? what’s different now in the resulting p5subset.json? (and what’s the difference to p5subset.js?) b) nothing more. The rest is indeed technical stuff and won’t improve any research. Best Peter > Am 02.10.2018 um 13:01 schrieb Vanessa Bigot-Juloux <vanessa.bigot-juloux(a)ephe.psl.eu<mailto:vanessa.bigot-juloux@ephe.psl.eu>>: > > Dear all, > > I have added a comment on the doc two days ago. However, it needs further explanations: > I have looked to TEI council profiles; from what I understood, you have a lot of knowledge in encoding, more than a lot of digital practitioners who use TEI (and other encoding languages needed to work with TEI) mostly for their investigation in a text/corpus/artefact. This is my case: I use TEI and other languages because I need these tools for investigating my corpus. By saying this, I have not the same background/knowledge (and goal) than most of you. Thus, if you agree, my first remarks will rather be (at least for now) to make sure than beginners or digital practitioners (but no experts in programming languages) will be able to understand not only encoding but also how it can help them to improve their research. In addition, I think we need to take advantage of each opportunity for doing a little pedagogy and the Stylesheets released is a good opportunity. > When you did the release of the Guidelines http://www.tei-c.org/release/doc/tei-p5-doc/readme-3.1.0.html (thanks James), you tried to give a few helpful information—although we can always be improved. > As for this Stylesheets release, I think we need to give further information regarding the issues resolved--not for all topics since a few of them will not be as much interest for beginners or average level. For example, something like: > “Among other issues resolved in the last stylesheets v7.46.0 released: > - In order to avoid a schematron [link] processor (in other words rule-based validation language) error regarding @ageAtDeath [link], rather used teidata.count [link] attribute group instead of teidana.numeric [link] (https://github.com/TEIC/Stylesheets/issues/322)”--I don’t know if it was updated on TEI website, but if this is the case, also add the TEI link updated. > - …” > > However, we need to ask ourselves the following question: how the issues resolved can be helpful to beginner and average level practitioners, in order to choose the issues which need more information. > Lastly, I’m not convince all readers will understand what is “stylesheets released.” —maybe under bracket something like “improvements according to issues resolved.” > > I suggest that the message has two sections: one for experts and one for beginners and average levels practitioners. > > Hope my explanation is clear enough… and that I’m not getting wrong in TEI council goals. > > Best, > Vanessa > > >> Le 30 sept. 2018 à 17:19, Scholger, Martina (martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>) <martina.scholger(a)uni-graz.at<mailto:martina.scholger@uni-graz.at>> a écrit : >> >> Ah, thanks. Changed the milestone to 7.46 in Github. >> >> Best, Martina >> >> -----Ursprüngliche Nachricht----- >> Von: Tei-council <tei-council-bounces(a)lists.tei-c.org<mailto:tei-council-bounces@lists.tei-c.org>> Im Auftrag von Syd Bauman >> Gesendet: Samstag, 29. September 2018 21:56 >> An: tei-council(a)lists.tei-c.org<mailto:tei-council@lists.tei-c.org>; Martin Holmes <mholmes(a)uvic.ca<mailto:mholmes@uvic.ca>> >> Betreff: Re: [Tei-council] Stylesheets v7.46.0 released >> >> Sorry, hit "send" before I was even done writing, let alone editing, that. >> >> Martina -- I don't know if you created a 7.45, 7.46, or 7.47 milestone. You may need to tweak the GiHub milestones or the e-mail to fit. >> _______________________________________________ >> 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

3 2

Adding or Editing an Appendix - TCW20
by Scholger, Martina (martina.scholger＠uni-graz.at) 03 Oct '18

03 Oct '18

Dear all, Martin asked me to forward a message: "I've added a section to TCW20 on how to add or edit appendices to the Guidelines, since Syd and I have just been figuring out how that works for issue #1657: <http://teic.github.io/TCW/tcw20.html#appendices>" Thanks Martin for adding this! Best wishes, Martina

1 0