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

Unihan etc.
by Martin Holmes 10 Dec '19

10 Dec '19

Hi all, Following today's discussion, I posted a brief summary on the pull request: <https://github.com/TEIC/TEI/pull/1901> Please read and feel free to edit/expand where necessary. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

1 0

Triangle SCI and possible Mellon grant
by Hugh Cayless 10 Dec '19

10 Dec '19

Hi all, I was supposed to send this a couple of weeks ago. My apologies. In October, Martina and I, along with several other folks, were at the Scholarly Communications Institute here in NC. Our group was focused on doing something about better internationalizing the TEI, including improving the translation process, introductory materials, etc. At the end, we were approached by Patricia Hswe, who’s a program officer at Mellon about possibly putting together a proposal to do some of this work. The following document is a kind of summary of our conclusions plus some ideas for how extra funding might help: https://docs.google.com/document/d/1TPuMHN4ZxklX5JlLo7HEFmEgTiUvuRD0cxDFE65… Patricia would like us to submit a prospectus, which would lead to a grant proposal if it is accepted. Your thoughts are, of course, welcome. So, interesting times! Hugh Sent from my phone.

1 0

delete git branch?
by Syd Bauman 10 Dec '19

10 Dec '19

I re-named the "nest_TEI_deprecate_teiCorpus" branch to "sydb_standOff". That really means, of course, that I copied it. If we delete the old one, is the history still kept in the new one? (Looking at [1] it looks like the history would be kept, and we can just delete the old one.) Notes ----- [1] https://github.com/TEIC/TEI/commits/sydb_standOff/P5/Source/Specs/TEI.xml

2 1

Next call: Tuesday, December 10
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Dec '19

10 Dec '19

Dear all, this is a reminder for our next call on Tuesday, December 10 (PST 6:00-7:30, EDT 9:00-10:30, GMT 14:00-15:30, CEST 15:00-16:30) We will start with the discussion on uniHan and standoff since Martin will kindly be joining us and has to head off to work at 7. Please have a look at the agenda and add your topics: https://docs.google.com/document/d/10zJFdN-p2WxGFTiRC8dMySCKe8QQ043lam1WFxz… Best, Martina

3 3

Spring F2F meeting
by Scholger, Martina (martina.scholger＠uni-graz.at) 10 Dec '19

10 Dec '19

Dear all, yet again we have a number of great locations to choose from for our next spring F2F meeting. To get an idea about our preferences I ask you to fill in the doodle before our call tomorrow: https://doodle.com/poll/xaf3f4exhy6geyqf Best, Martina

4 3

oxygen-tei framework fix
by Martin Holmes 05 Dec '19

05 Dec '19

Hi all, Those of you on the Stylesheets call on Tuesday will remember that we discovered in the course of it that Syd's TEI for TEI Customizations template/ODD was available in the TEI P5 framework in Oxygen but not in the TEI ODD framework. I raised a ticket for that at the time, and I just figured it out and fixed it: <https://github.com/TEIC/oxygen-tei/issues/39> I put an explanation of the problem on the ticket, because we're sure to stumble over this again. If you're using the bleeding-edge version of the plugin, you should now be able to update and see Syd's thing in the TEI ODD framework options. Cheers, Martin -- ------------------------------------------ Martin Holmes UVic Humanities Computing and Media Centre

2 1

Re: [Tei-council] release dates, some findings
by James Cummings 05 Dec '19

05 Dec '19

No objections to that. For the record some of these may have been instances where we had done a full release, realised that there was some corrigible error (in the build/release process), and then manually or otherwise did a re-release without changing the actual date of release. That is, we did the release, announced it, noticed an important error (like the non-English pages having not generated properly) and then silently fixed it without mentioning it publicly. ;-) There were also instances where stumbling blocks in the release meant that it went over midnight in the timezone where the build was happening. Not saying we shouldn't update the webpages to match the XML reality, just explaining. (Now off strike, but working to contract.) 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: 29 November 2019 06:39 To: TEI Council <tei-council(a)lists.tei-c.org> Subject: [Tei-council] release dates, some findings for the record: While working through the Guidelines releases for the Zenodo ingest I discovered and fixed some inconsistencies regarding release dates at [1]. A few dates differed from what is mentioned in the respective release notes, so I fixed it to match the release notes. Lastly, one release note has the wrong date [2] which I already fixed in the xml [3]. I propose to adjust the date in the html version in the vault, as well, which I’ll do as soon as I get access to the vault. Best Peter [1] https://tei-c.org/guidelines/P5/ (table: „Version Date of Release (& Release Notes)“) [2] https://tei-c.org/Vault/P5/current/doc/tei-p5-doc/readme-3.2.0.html [3] https://github.com/TEIC/TEI/commit/9150346745c0057d74a20d0a36bcbbb09260d865

2 1

missing council reports
by Lou Burnard 04 Dec '19

04 Dec '19

To be exact: reports for the following years are missing: 2003, 2004, 2005, 2006, 2007, 2014 I have the first three.

1 0

vault.tei-c.org
by Peter Stadler 04 Dec '19

04 Dec '19

Dear all (Council and infrastructure group), here’s yet another update on the move to humanum: In our strive to separate out concerns and services we added another subdomain vault.tei-c.org where you can find – drumroll!" – the Vault. The data stems from a mounted volume which also feeds the ’traditional’ host at https://tei-c.org/Vault/. So, at present this is purely an additional service for us to test and sort things out. The vault.tei-c.org is run by an nginx docker container and the service description can be found in the infrastructure repo [1]. I already added CORS and some mime types for XML files – if anything is missing, drop me a line! Looking at the vault I found that the last three releases of the Stylesheets were missing at [2]. I just added them (as you can see from the timestamp) and updated the symlinks to „current“ and „current-old“. Second, I fixed the release date for 3.2.0 in the respective readme files (as I promised in my last mail). Looking at the P5 releases in the vault [3] I see „current-broken“, "current.03.04.2019“, and „X.X.X“. Is this in use by anyone? I suspect these are just leftovers from the migration which I’d like to delete. And there’s is a hidden „.svn“ folder which looks like it could be deleted as well. If no-one objects, I’ll do so. Best Peter [1] https://github.com/TEIC/infrastructure/tree/master/humanum [2] https://tei-c.org/Vault/Stylesheets/ or https://vault.tei-c.org/Stylesheets/ [3] https://vault.tei-c.org/P5/

3 6

Stylesheets meeting tomorrow, Tue 03 Dec 14:00Z
by Syd Bauman 03 Dec '19

03 Dec '19

Sorry I'm late on this. (I try to post these 24 to 72 hours in advance.) We have a Stylesheets Group meeting scheduled for this coming Tue 2019-12-03 14:00Z. timing ------ It will be: * 06:00 PST (Victoria) * 09:00 EST (New York) * 14:00 GMT (London) * 15:00 CET (Berlin) place ----- I am expecting we will use Google Hangouts. (I *think* I have my Google Hangouts life working. :-) topics ------ Main topics are the carry-over from last month: 1) Ticket 393.[1] 2) Ticket 399.[2] Martin has posted where he thinks the problem is on the ticket. If he's right (and I have no reason to believe he isn't), I'm not sure I like his proposed solution. So this may require some discussion. notes ----- [1] https://github.com/TEIC/Stylesheets/issues/393 [2] https://github.com/TEIC/Stylesheets/issues/399

5 5