We are thinking of using the occupation element to describe someone's role/contribution to the project. The @code attribute could point to a formal taxonomy including Editorial Board Member, Author, etc., while the actual text content could provide a refined version of this specific to the person. Multiple occupation elements could be provide for people with multiple roles, and the Credits page could provide a list of all of the taxonomy types, as links which would generate or jump to detailed tables of the people in those roles.
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:
Added the following elements and attributes to the schema:
Met for about three hours, with lots of fruitful discussion and decisions made about encoding, schemas, and general procedures. I'll document them in detail tomorrow, as well as carrying out as many as possible before my vacation.
The latter is rendered in quotes, so interacts with level a titles and regular quotes; watch out for strange results if nested, especially when following punctuation needs to be pulled into the quotes.
This project allows literary and scholarly works (primary and secondary) to be associated with locations in London, providing the reader with a richer understanding of the works.
|<< <||Current||> >>|