LEMDO

After corresponding with JM, determined list of priorities for the conversion. I decided to do H5 first since it is one of the most densely annotated/collated and the editorial process should be swift.

Converted H5_FM and Q1M and got annotations working; there were a few bugs in the HTML code, which I fixed. Also discovered the issue with part lines; the IML usually flagged the part lines with an empty line preceding the inferred line (i.e. via one of the LNs), so re-wrote bits of the conversion to handle that. Also had to make various fixes to the apparatus linking code to handle supplied tags.

Discussed plans and evolved a new idea for an ODD for ODD/Documentation with its own processing, to be part of the Endings project. More coming on this.

I've been trying to figure out the best way to retrieve all nodes between two anchors; I'm not changing the document hierarchy (i.e. I'm not tagging them), but I want them for labelling purposes etc. But doing following:: and preceding:: or using the following/preceding operators (>>) operators with intersect isn't very efficient.

It's nice because we have @xml:ids on these things, so it's easy enough to know when to stop. It's not generalized for non-id'd things (although, I bet you could use generate-id(.)).

<xsl:function name="hcmc:betweenTwoAnchors" as="node()*"> <xsl:param name="anchor1" as="node()"/> <xsl:param name="anchor2" as="element(anchor)"/> <xsl:variable name="f1" select="$anchor1/following::node()[1]" as="node()"/> <xsl:variable name="f2" select="$f1/following::node()[1]" as="node()?"/> <xsl:copy-of select="$f1"/> <xsl:choose> <xsl:when test="($f2/self::anchor and $f2/@xml:id = $anchor2/@xml:id) or empty($f2)"/> <xsl:otherwise> <xsl:copy-of select="hcmc:betweenTwoAnchors($f1,$anchor2)"/> </xsl:otherwise> </xsl:choose> </xsl:function> <

Working on the ODD to allow teiCorpus (which was trivial), but then spent a long time trying to get a schematron rule in place to check the attributes of a processing-instruction. Note that XSL variables do work in schematron patterns, but functions and other bits (at least with the current stylesheets) do not.

The second issue was that the schematron building code (that I lifted from MH's Keats code) does not automatically process "foreign elements" (i.e. XSLT variables) in the final XSLT step (iso-to-svrl-2.xsl). You have to add an "allow-foreign=true" parameter to the XSLT for it to work as expected.

Following MoEML, I added the egXML and CSS validation steps to the buildValidate.xml build. Had to modify it slightly, since MoEML often uses collections whereas the builds currently rely more on filesets. It simplified things slightly.

Had to deal with quite a bit of fallout, since our egXMLs were either invalid or our schema wasn't handling things properly.

Phone and personal meetings with three people re the latest developments; slight reshuffling of plans.

Meetings today with MC, JJ and JT, with lots of planning and the writing of a sitrep to pass to MB.

Met with JJ and MH to discuss plans moving forward, particularly documentation and plans. We're going to make sure our documentation is easily navigable from the outset, with maps and decision trees giving multiple pathways to get to a particular bit of documentation.

Also made some headway on the build processes themselves; I've been able to modularize the builds so that the master build (lemdo/build.xml) calls a number of other builds (all with suffix '_master.xml') that themselves call either XSLTs or other modular build processes. Each of the smaller master builds can be run on its own (it also includes the globals module) or they can be run from the master one