LEMDO

JT and I talked at length about the work he's now doing renaming everything tagged with "ISE" that now needs to be LEMDO; and we devised a cunning plan for editor projects:

• When an editor is getting started we first send them out an Ant build file which they open in Oxygen to set up their project.
• When it runs, that file creates directory, checks out the svn repo, and then runs a second ant task that does this:
• svn update to get any changes to core files
• svn export to get local copies of schemas (avoids externals)
• That ant file is the one you open and press the red triangle before you start work.
• Another ant file is the after-work version, which does svn update and svn commit.

So: no need for svn externals; no problem if connectivity is temporarily down; no need to learn svn; everything happens in Oxygen.

...in keeping with our forward planning.

..for the benefit of other people who will be working on related texts. Results were valid, no errors.

I'm beginning the work on customizing the ISE3's ODD so that we can have a "standoff" element to store all of the database-like stuff that the rest of the Endings projects have been putting in the teiHeader. It is based off of the stdf proposal, but is less concerned about linguistic annotation.

Basically, the standoff element contains model.listLike and listBibl (which is part of model.biblLike) and spanGrp (for annotations).

Note to self: Adding the standoff element (or any custom namespace element) between the teiHeader and the TEI element requires adding that namespace to the @defaultExceptions attribute in the schemaSpec element.

Combined the two build files that we had in the ISE3 repo (ise3/diagnostics.xml and ise3/site/build.xml) and their associated ant_globals.xml files. It's now one build process, which by default goes through and:

1. Validates the TEI in ise3/data
2. Runs diagnostics on the TEI in ise3/data
3. Then begins the static build process

Working on the creation of the Standard XML, which for now means resolving pointers. Since the ISE has decided to use more granular prefixDefs (i.e. 'doc' for documents, 'pers' for person) instead of using general ones (like MoEML), prefix resolution can be more generalized. There's a template that matches every TEI attribute that has a pointer data-type and, like the Endings diagnostics code, resolves the pointer based off of prefixDefs. Seems to be working well.

Wrote a utility function for retrieving data from the taxonomies; this will be needed to complete the Dublin Core metadata in the pages.

I've decided we should build the HTML pages from a genuine template, so that anyone who knows HTML can easily edit such things as the menu items and the boilerplate content. I've set one up, and given it a basic flex-based CSS layout that shouldn't be too hard for later styling. I'm thinking about building in the small-format device rulesets from the beginning, so they don't end up being grafted on later. The basic process would be to load the template, and process it through XSLT templates, with the source XML document passed as a tunnelled parameter; that should mean we can pull anything we like from the source XML fairly easily, and meanwhile most of the boilerplate stuff will just fall through in an identity transform. XML will be processed under a distinct mode.

JM needed documentation for subversion so got a start on writing that. We already had some stuff in there, but a lot of it was unedited stuff from MoEML's. Rewrote it significantly with code blocks and clear instructions. It's a bit less discursive, but it should do the job for now, since JM needs it right away. Used the oXygen TEI P5 --> HTML conversion and then saved as a PDF.