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

Recommendations on values of @xml:id (FR #540)
by Raffaele Viglianti 31 May '15

31 May '15

Hi all, Martin Mueller asked on the list for recommendations on good uses of xml:ids, which resulted in a good discussion and a FR. I summarized the main suggestions on the ticket on SourceForge, but I post them here as well because I think we need to discuss this further, see below. The Guidelines already have some recommendations (numbering based on doc structure): * The Guidelines already suggest numbering based on doc structure ( http://www.tei-c.org/release/doc/tei-p5-doc/en/html/CO.html#CORS2) * Use 3 letters (e.g. from the title)+ 3 digits, incremental. E.g. HOL001, HOL002, etc.. * Same as above, but no fix number of digits. E.g. HOL1, HOL2, etc. * Prefix an id with name of element (this is simpler version of what the Guidelines already recommend) * Give tei:TEI an id and prefix every other id in the document with it (to guarantee cross-corpus uniqueness) These are all reasonable suggestions and there can be plenty more - which is why I think that the TEI should *not* give any recommendation on best practices for xml:id because it's a project management issue, not an encoding one. Myself, I prefer random ids, a practice that avoids introducing yet another level of complexity and data management. I understand the human readability, but sequences are too easily broken. And when parsing, relying on ID content instead of TEI content sounds like a bad idea.

7 16

agenda item / bug
by Syd Bauman 26 May '15

26 May '15

Julia just reminded me that <event> still is not allowed as a child or grandchild of <org>. Off the top of my head, I don't see why <listEvent> is not a member of model.orgPart. Not quite so obvious how to make <event> an eligible direct child of <org>, but it seems like a reasonable request. I plan to submit a bug report shortly, with hopes that we can tackle this and solve it for next release. (Although I have my suspicions that this will bring up other thorny issues.)

3 3

Fall F2F Dates
by Hugh Cayless 29 Apr '15

29 Apr '15

Hi All, Emmanuelle Morlock asks if we can nail down dates for the Fall F2F ASAP so that she can reserve rooms. Workshop dates may fall on Oct. 26, 27, or the morning of the 28th. There will probably be an EpiDoc one that I may need to help run. Options I see are: 1. Meeting on Sunday (25th) and Monday (26th) 2. Meeting the weekend before the conference (24th–25th) 3. Meeting concurrently with the workshops, and have some council members drop out for some of the time to deal with their workshops 4. Don't do any workshops 5. Don't meet before the conference. So what do you think? Is anyone else proposing a workshop?

7 9

updated framework not used in conversion
by Lou Burnard 29 Apr '15

29 Apr '15

I'm puzzled... I have installed all the recent updates to the TEI framework from the TEI site, and my local .com.oxygen.xml directory contains an updated version of one of the XSLT scripts provided as a result: -rw-rw-r-- 1 lou lou 13520 Apr 29 12:02 ./.com.oxygenxml/extensions/v16.1/frameworks/http___www.tei_c.org_release_oxygen_updateSite.oxygen/tei/xml/tei/stylesheet/profiles/oulipo/from_common.xsl However, when I actually run the conversion from within oXygen, it does not use this version, but instead the one released ages ago, which is still in the installation directory: -rw-r--r-- 1 lou lou 9612 Jan 22 13:43 ./OxygenXMLEditor16/frameworks/tei/xml/tei/stylesheet/profiles/oulipo/from_common.xsl The Ant script I am running in my transformation says "Loading stylesheet /home/lou/OxygenXMLEditor16/frameworks/tei/xml/tei/stylesheet/profiles/oulipo/docx/from.xsl" It also uses the build-from.xml file from the same directory, rather than the one one in the .com.oxygml tree, which is however identical. But since it uses relative paths, maybe that is the problem? Any advice much appreciated...

2 3

Teleconference April 24
by Hugh Cayless 24 Apr '15

24 Apr '15

Hi All, We have a telecon scheduled for next Friday, April 24th. Any chance we can push it back to 06:00 PDT / 09:00 EDT / 14:00 BST / 15:00 CEST? I have a conflict at 8:30 due to my own carelessness. We could make this change permanent in fact, if no-one objects. It would mean Martin doesn't have to get up so brutally early. I no longer have a conflict at 10:00 every Friday, so we could push it later. We're (as previously decided) going to attempt to do this in a Google Hangout. I will send an invite to the list a few minutes before start time. I've started an agenda at http://wiki.tei-c.org/index.php/Council_Agenda_2015-04 to which you should feel free to add items for discussion. I've got a couple more to put in myself. May's telecon will obviously be canceled because we'll be in Ann Arbor. Thanks, Hugh

12 19

Oxygen release
by Martin Holmes 20 Apr '15

20 Apr '15

George Bina confirms there will be no new Oxygen release before 17, scheduled for the end of April/beginning of May. That's perfect timing for us. It gives a window of three weeks for our version of the plugin to be out in the wild and in general use before the Oxygen guys build the version they'll be including with the Oxygen distro. Cheers, Martin

5 6

Fwd: [tei:bugs] #749 fatal bug in 2.8.0 apropos att.global.rendition
by Martin Holmes 14 Apr '15

14 Apr '15

Do we need a 2.8.1 to be done fairly quickly for this? This really is my fault, but I must admit I had no idea what @predeclare was about; I was assuming the regular tests would pick up anything problematic, and I had no trouble working with @rend and @rendition in my projects for several months before release. I don't use DTDs, of course. Cheers, Martin -------- Forwarded Message -------- Subject: [tei:bugs] #749 fatal bug in 2.8.0 apropos att.global.rendition Date: Tue, 14 Apr 2015 17:19:19 +0000 From: Sebastian Rahtz <rahtz(a)users.sf.net> Reply-To: Ticket 749 <749(a)bugs.tei.p.re.sf.net> To: Ticket 749 <749(a)bugs.tei.p.re.sf.net> --- ** [bugs:#749] fatal bug in 2.8.0 apropos att.global.rendition** **Status:** open **Group:** AMBER **Created:** Tue Apr 14, 2015 05:19 PM UTC by Sebastian Rahtz **Last Updated:** Tue Apr 14, 2015 05:19 PM UTC **Owner:** nobody I am afraid the `<classSpec>` at.global.rendition is missing the vital attribute predeclare="true". I have committed the appropriate change to fix it. This means that any ODD which redefines @rend, @rendition etc is going to fail when it comes to making a DTD. You may now formally curse the day DTDs were invented. I might note that a few existing ODD users are going to be mighty confused when they find their code to change @rend globally simply fails to work these days. In retrospect, it would have been good to highlight this in the release notes. --- Sent from sourceforge.net because you indicated interest in <https://sourceforge.net/p/tei/bugs/749/> To unsubscribe from further messages, please visit <https://sourceforge.net/auth/subscriptions/>

2 2

Fall meeting
by Martin Holmes 13 Apr '15

13 Apr '15

Hi all, The CfP for the fall Members Meeting is out, and we have to start making plans. I'd like us if we can to agree soon whether we want to have the fall Council meeting along with it (I think we'd all like to do that), and if so, whether it's going to be before or after, so we can plan work absences and travel. Can we have a show of hands on who would prefer before the main meeting and who would prefer after? I'd rather have Council meet before, so I'm fresh going into the Council meetings and so we can report informally on what we've been doing during the members meeting. Cheers, Martin

7 6

Release freeze *lifted*
by Raffaele Viglianti 06 Apr '15

06 Apr '15

Dear council, The release of 2.8.0 is completed and the commits freeze is now *lifted*. We are now working on 2.8.1a. Please feel free to go back to your bug fixing and general peruse of the SVN repository. Thanks, Raff

4 3

Release day instructions
by Martin Holmes 06 Apr '15

06 Apr '15

Hi all, This is meant mainly for Raff, James, Hugh and anyone else likely to be helping with the release process. I took a quick look through TCW 22, the release instructions, in advance of the release, and noticed some problems. The most obvious is that the oxygen-tei instructions were out of date; they pointed to the Google Code project. I've fixed that, but when I went to test out the rest of that instruction block, I found it doesn't work; the structure of the Vault seems to have changed a bit since those instructions were written, or perhaps they were never actually right. The instructions talked about a file x.x.x/updateSite.oxygen, where x.x.x is the version number, but actually the update file at in x.x.x/oxygen/updateSite.oxygen. I've fixed that. Since James's blog post has the right URL for the file: <http://blogs.it.ox.ac.uk/jamesc/2014/04/02/auto-update-your-tei-framework-i…> I assume the instructions have not been right for some time. James, you'll have to update your blog post to point to the new GitHub location for the oxygen-tei source code. Those same instructions in TCW 22 only take account of major releases (which luckily this is -- it's 2.7 -> 2.8) so they'll have to be elaborated a bit for situations in which you're actually changing a version within the same folder, as minor point-releases do. There's one other thing we'll need to work on. The original version of the instructions has point 8 like this: <quote> 8. Still in ~/private/P5/Utilities, run ./tei-database-rebuild.sh This will update the eXist-db used by Roma. The script takes no parameters but expects a configuration file in the user’s home directory at ~/etc/tei-exist.conf with the appropriate paths and credentials. For the main server at tei-c.org this should already be set and no adjustments should be needed. This is the database used by Roma, so this operation will ensure that Roma is using the new version. Temporary measure for version 2.7.0 only: ask Martin, Peter, James or Sebastian to check the version of P5 used by Roma, to ensure that this has succeeded, and fix it manually if it has not. This procedure is undergoing revision right now, so it has to be done there may be a problem here. Following the release of 2.7.0, a new process will be put in place and this instructions will be updated. </quote> We obviously dropped the ball there. I've edited this a bit so that it's less confusing, but we'll still have to make sure we know how to check the version of P5 which is in eXist when the script has been run. I know the URL to go to in order to do that, but we can't put it in the documentation for various reasons; I'd like to make sure enough other people know it so that there's always someone available to check when the time comes. I'm going to raise a bug that forces us to work on this; it's an aspect of the whole shebang which is very fragile. Anyone else likely to be on duty for the release might want to check that TCW 22 makes sense to them too: <http://www.tei-c.org/Activities/Council/Working/tcw22.xml> Raff, are you already set up with your SSH key for tei-c.org? Cheers, Martin

4 4