Academic

Three long days working with the TEI Council in Paris.

Posting time spent on TEI tickets and discussions while travelling this weekend.

Filed an SF ticket on the use and possible deprecation of attributes having data.word and data.key values, in favour of @ref and friends, with private urn schemes.

Checked through my SSHRC CV (still OK) and updated the 4-page attachment, adding this year's presentations and software output. Ready to go for the Moses application now.

Council Skype meeting at 6am (!), and also spent some time looking at tickets in SF and trying to resolve some (none resolved so far, but I made some hopefully-helpful comments).

I discovered that I had to add indents and extra spaces to the XML in <egXML> tags to make it display correctly (i.e. pretty-printed). I've also made a couple of other changes, and there will be more when we've sorted out the @type or @rend issue on <ptr>.

When adding a new XML file to SVN, you need to do the following, to ensure that the headers get added. First, add this manually:

<!--
    Copyright TEI Consortium.
    Dual-licensed under CC-by and BSD2 licences
    See the file COPYING.txt for details
    $Date: 2011-07-06 22:07:54 +0100 (Wed, 06 Jul 2011) $
    $Id: notatedMusic.xml 9072 2011-07-06 21:07:54Z rahtz $
-->

Then run this command:

svn propset svn:keywords 'LastChangedRevision LastChangedBy Id LastChangedDate HeadURL' filename.xml

Build failed in Jenkins, and SR eventually explained why: I'd neglected to include the entity &notatedMusic; inside the FT-TablesFormulaeGraphics.xml file. Without that, using the element itself inside <egXML> will generate an error because the processor can't find its <elementSpec>.

Now seems to be building OK, and I've fixed a few more typos in the content, but there's more work to be done finding other locations where the new element ought to be mentioned.

TEI Council work: working with JC to edit and integrate the description of the new <notatedMusic> element into the Guidelines. This is the first major edit I've done, so I'm going cautiously. Waiting to see if it builds OK in Jenkins. If it's OK, there's more work to be done: one more example to integrate, and then a trawl through the rest of the guidelines to see if there are other places it needs to be mentioned.

MVP and EMiC will be needing to do XML diffing in order to produce critical apparatus/variant encoding, so I've started looking at the options. Juxta looks fanciest, and promises to handle TEI files, but I was unable to get it to accept a second file once I'd loaded one into a collation; that just seems to be a bug, but even so the output it creates is HTML and not very useful. I found several other programs (stored in ~/Applications/xml_diff_tools) and managed to get two of them working pretty well, one called diffxml and one called fuego (there's also one from IBM which is very old, and wouldn't run). The two that worked produce potentially useful XML output files which could be processed into something a human could use to check a list of differences and encode variants.