10/04/08

Permalink 02:33:01 pm, by mholmes, 263 words, 330 views   English (CA)
Categories: Activity log; Mins. worked: 90

Outcome of editorial meeting

These are some points emerging from the editorial meeting:

  • Glossing will be handled through the use of <seg> elements with an @ana attribute pointing at a list item element in the back of the document, like this:
    [main doc]
    ...<seg ana="#blah">bleoh</seg>...
    [back matter]
    
    <list>
       ...
      <item xml:id="blah">blah, blah blah</item>
       ...
    </list>
    
    This will allow centralization of glossing, so one gloss can be referred to many times; and it will also allow us to generate links from the glossary back to all the items in the text.
  • Introductory notes in the <head> of a poem will be unified into a single, multi-paragraph editorial note, which will be rendered distinctly based on its context.
  • Other notes in the text will be distinguished as editorial or paleographic, using an @type attribute.
  • Scribal annotations will be <note type="annotation">. They often contain editorial notes, but these can presumably be rendered as normal, if their position inside marginalia doesn't cause problems.
  • All images (of glyphs etc.) will be moved to the Cocoon environment, so they can be shown without logging into ETCL's Webspace.
  • Much more material will be added to the header, especially editorial intro text, and some of that text may be referred to from (and optionally pulled into) the intro sections of individual poems.
  • I'll wait on a stable new version of the XML file before starting to make changes.
  • We'll aim to work on the redesign in the second week in June.

08/04/08

Permalink 02:38:31 pm, by mholmes, 121 words, 293 views   English (CA)
Categories: Activity log; Mins. worked: 200

Standalone Devonshire now working

Following our decision that projects like this ought to be able to function as standalone Cocoon-based Webapps, I've created a standalone version of the application living on the Lettuce Development Tomcat. We discussed whether this should be using Tomcat authentication, as we did for the IALLT Journal, but there are reasons to stick to the rather hokey Cocoon-based authentication we have, and in fact to improve it. If we do Tomcat-based authentication as described here, then there's a co-dependency between the roles defined in the Tomcat users file and the web app's web.xml file. This means the project isn't actually portable at all.

All in all, it's time I properly mastered Cocoon authentication; this is an opportunity to do it.

Permalink 01:02:07 pm, by mholmes, 174 words, 295 views   English (CA)
Categories: Activity log; Mins. worked: 60

Research into @corresp

KA raised the issue of what precisely is meant by the "URI" content of the @corresp attribute. According to the guidelines, the value is one or more of data.pointer, which is defined by RFC 2396. This is identical to the data type of ref/@target. The RFC does not mention XPath (it dates from 1998). According to the RFC, these are the components of a URI:

URI-reference = [ absoluteURI | relativeURI ] [ "#" fragment ]

However, the guidelines go on to specify a range of different options for the fragment component, including the use of XPath. According to the current incarnation of the guidelines (or at least, my reading of it), because the first component (absolute or relative URI) is optional, and its absence means that the current document is the target, we should be able to use XPath as in the following example:

#xpath1(//note[@xml:id='fn6']/p[1])

I think it's the case that my original formulations for the Devonshire look like this:

xpath1(//note[@xml:id='fn6']/p[1])

So we need to prepend the hash.

07/04/08

Permalink 04:57:01 pm, by mholmes, 124 words, 300 views   English (CA)
Categories: Activity log; Mins. worked: 75

Began building a standalone version of the DMS

The current version of the DMS is running as part of the single Cocoon/eXist stack on the main Tomcat on Lettuce. As part of our policy of separating out individual projects, I've started building a distinct Cocoon instance for it on the DEV tomcat. I got the latest 1.2 release of the Cocoon/eXist WAR file, unrolled it on Tomcat, and then brought down the resulting tree and made the edits to config files, jar repositories etc. which are listed in our previous instructions. However, I can't re-upload the changed files yet, because the default directory in which stuff is unrolled by Tomcat ends up being owned by apachsrv, so I have no write permissions. Still waiting for sysadmin to fix that for me.

17/03/08

Permalink 09:51:37 am, by mholmes, 53 words, 290 views   English (CA)
Categories: Activity log; Mins. worked: 60

Updating Apparatus files

Got three new apparatus files from CL (two brand-new, one replacement), and integrated them into the site. In the process, I discovered that P5 has changed the tag name <witList> to <listWit>. This doesn't affect much, but I changed all the existing files and tested everything to be sure.

27/02/08

Permalink 01:35:37 pm, by mholmes, 141 words, 320 views   English (CA)
Categories: Activity log; Mins. worked: 200

XSLT to update document structure

Carried out the following changes in consultation with KA and MC, through an XSLT transformation, to bring the document into conformance with the current status of TEI P5:

  • Created a new <msDesc> element in <sourceDesc>, with minimal required children, to provide a location for <handDesc>.
  • Converted old <handList> to <handDesc> in sourceDesc/msDesc/physDesc, and all child <hand> elements to handNote.
  • Converted space/@extent to @quantity.
  • Converted normalize/@method='tag' to 'markup'.
  • Converted add/@rend to @type.
  • Fixed parentheses not allowed in g/@type, by replacing them with underscores.
  • Converted <num> elements with @type attributes pointing to folios to <ref> elements with @target attributes pointing via XPath at the relevant <pb> tag.
  • Added a <revisionDesc> list item to describe these changes.

10/09/07

Permalink 04:22:01 pm, by mholmes, 99 words, 387 views   English (CA)
Categories: Activity log; Mins. worked: 120

Scribal and editorial notes

Editorial note anchors (numbers) are no longer floated to the right of the poem; this takes them too far out of context, and sometimes wraps them to another line, which is not good, and also it prevents proper display of anything when an editorial note is embedded in a scribal note (an "annotation"). Scribal notes are now positioned correctly as far as I can tell, and should work OK by and large, although there's not necessarily always enough space for them in the margins, and some can never be handled adequately (such as the one which is "vertical(ascending)".

Permalink 04:19:03 pm, by mholmes, 88 words, 360 views   English (CA)
Categories: Activity log; Mins. worked: 30

Fixed missing titles

A couple of titles were missing from the index page, and the contents of the last "poem" (an excerpt) were not showing up. This was because the XSLT was looking for a title[@type='incipit']; it now uses any title element it finds if there's nothing matching that. The body of this excerpt is les than a line, so it was wrapped in an <ab> tag rather than <lg> or <l>; I'm now handling <ab> elements in the XSLT too.

Permalink 12:56:50 pm, by mholmes, 66 words, 423 views   English (CA)
Categories: Activity log; Mins. worked: 90

Added rendering for @rend attributes on lines and segs

There's a wide variety of distinct values for @rend attributes. Some of these are combined, and many overlap between <l> and <seg> tags. I've taken a shot at providing some kind of decent rendering for most of the ones that can be rendered meaningfully; some which can't are ignored, and still others are awaiting conversion or normalization to another form of markup.

Permalink 12:53:49 pm, by mholmes, 110 words, 380 views   English (CA)
Categories: Activity log; Mins. worked: 30

Fixed the bug with ghostly lines appearing in line-numbering

This was another empty-span-tag issue, caused by the combination of Cocoon and Firefox. Cocoon spits out empty tags as self-closing tags (which is wrong according to W3C guidelines), and Firefox screws up rendering when it encounters a self-closing tag which can have content, such as <span/> (which is annoying but at least draws our attention to the problem). In the case of this error, the empty span tags were caused by lines which have no number (i.e. no @n attribute), because they're in some way a refrain or a tagline that shouldn't be numbered. Fixed this by adding non-breaking spaces where there are no line numbers.

:: Next Page >>

Devonshire

Reports

Categories

May 2013
Sun Mon Tue Wed Thu Fri Sat
 << <   > >>
      1 2 3 4
5 6 7 8 9 10 11
12 13 14 15 16 17 18
19 20 21 22 23 24 25
26 27 28 29 30 31  

XML Feeds