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

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 11 Oct '18

11 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) 08 Oct '18

08 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) 08 Oct '18

08 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