[not sure if the sf mailing list is still functioning, so apologies for re-send] -------- Forwarded Message -------- Subject: formatting pure odd specs Date: Sat, 19 Sep 2015 18:10:46 +0100 From: Lou Burnard <lou.burnard@retired.ox.ac.uk> To: tei-odds@lists.sourceforge.net <tei-odds@lists.sourceforge.net> The Guidelines HTML pages as currently produced don't do a good job of handling the changes introduced with Pure ODD. In particular, here's a (not necessarily complete) list of the things that ought to happen (in my view) but currently don't... 1. The <datatype> component of an attribute spec (whether in an attribute class or an element spec) currently produces some text saying "n to m occurrences of" (depending on the values of minOccurs and maxOccurs) , followed by an empty white box, optionally followed by the phrase "separated by whitespace". If you toggle the display of the empty white box from "compact" to "XML syntax", it will show the full content of the <content> of the <datatype> e.g. <datatypemaxOccurs="unbounded"> <dataRefkey="teidata.pointer"/></datatype> The box is redundant, I think. It should be replaced simply by the @key value from the <dataRef> which should be an HTML link to the appropriate teidata spec. 2. The "Declaration" component of an elementSpec currently (still!) displays its RelaxNg declaration, in either compact or XML syntax. I think this should be replaced by the pureODD content, displayed in the same way as an XML example. There is an argument for retaining the Relaxng declarations as well, as there is for also providing the XSD or DTD declarations, but I ain't making either of them. 3. Individual specs for the teidata definitions need to be generated and included in the lists of datatypes. I have been poking around in the stylesheets trying to see how to make these things happen, and have so far (more or less) succeeded in achieving no 3 above. The others are more of a challenge so offers of help would be much appreciated.