This is a brief summary of the state of play on the project, before I go on vacation.
A large number of new elements and attributes have been added to the schema, including:
Rendering has been updated to take account of @cert (although Cameron says there's an intrusive space somewhere).
The schema includes all the values we discussed for revisionDesc/@status, along with full documentation of them (so Oxygen should show you helpful explanations when you're choosing one). All XML files now have this attribute, and as far as I know, the values are all currently correct.
The Schematron file has been substantially enchanced so that it enforces the use of @status, bullies you into using @calendar on historical dates, and does a bit more nifty checking. In order to do this, it has been reconfigured such that it requires a specific setup in Oxygen: XPath 2.0 and allow-foreign in the XML Parser screen. This gives us the ability to use XSLT functions in Schematron, which is a huge improvement. london_all.sch will be a useful model for Schematron use in other projects.
A new file exists in data/boilerplate called includes.xml. This currently contains the calendar definitions we're referring to with mol:julian and mol:gregorian, but it will ultimately include all the shared header information we plan to point to or include from various files, such as the common publicationStmt that explains our licensing and distribution terms, etc.
A new folder called "tests", containing a file called "validity_tests.xml" has been created. This is intended to house markup which tests the schema constraints. It will almost always contain code which is invalid (that's sort of the point of it), as well as valid code. Ignore this file, and in particular, don't upload it to the database.
WHAT HAS NOT BEEN DONE:
- Any additions or amendments to the documentation (XML Encoding instructions etc.) on the site, relating to these recent changes. Cameron will undertake some of that, but I'll also go through it and add some details when I get back.
- I haven't started creating the various blocks of XML for inclusion in headers yet (in includes.xml). JJ and I will have to sit down and write all that stuff, then I'll have to set up the schemas to allow the various XIncludes, and make sure they work.
- I haven't yet modified the web application to allow the various table-of-contents page changes we discussed. However, anyone could do that. For instance, to replace the current "litref_library_toc.htm" page with something else, this is what you'd do:
- Create a new document called e.g. library.xml in /info/, and make it into a list of links along the lines of about.xml.
- Add that page to SVN, and upload it into the db. Go to library.htm on the site and make sure it looks right.
- Edit boilerplate.xml to replace the target="litref_library_toc.htm" link with a link to target="mol:library".
- Upload boilerplate.xml to the site. The menu should now point to the new page.