Working on creating a template for the <front> element, I discovered that the <argument> tag would be appropriate in <titlePage> and we should use it. However, it wasn't permitted by our schema, partly because we'd never used it in that context, and partly because it was only added to model.titlepagePart earlier this year (our schemas dated from 2009). Also, we had two separate schemas, with a sort of splinter schema used by the Agreemens texts and Complaintes, while the main schema was used for all the others. Time to generate a new schema. These are the steps:

• Copy all the XML files from the anthology into a temporary directory. Also copy in a new file which includes the new feature that you need to make available in the generated schema (in this case, <argument> inside <titlePage>).
• Open a terminal in that directory.
• Run oddbyexample.xsl like this:

  java -jar /home/mholmes/apps/apache-tomcat-6.0.26/webapps/mariage/WEB-INF/lib/saxon9he.jar -it:main -o mariage2010.odd /home/mholmes/WorkData/tei/1.8/xml/tei/stylesheet/tools2/oddbyexample.xsl   corpus=`pwd`/
  

• Upload the generated .odd file into Roma, and add title and description.
• Save the .odd file again from Roma.
• Generate the schema.
• Validate all the existing files against the new schema, before replacing the old one with it.

In the process of validating, I found a couple of errors in files which I've corrected (duplicate @xml:id attributes in two image markup files, and one mistyped attribute name in Sonnet 1609). I also discovered that I seem to have a broken Saxon jar in my cocoon_with_exist setup (which explains many things), so the path above is to a known working one inside the Mariage Cocoon.