Review of Tite Scheme
Jump to navigation
Jump to search
Contents
Background
Comments
general comments
- Incorporate outside documentation (for example, Virginia's DLPS documentation) into this document so it can stand alone. (This was suggested by Andrew Rouner at the SIG meeting in London.) (Kshawkin)
comments on section 1
- “RelaxNG” should be spelled “RELAX NG” for short (or “ISO/IEC 19757-2: Document Schema Definition Languages part 2 — Regular-grammar-based validation” for long)
- We should either include Vesta as a tool that can generate schemas from the ODD, or at least prepare for doing so by replacing “The Roma web tool can generate all of these.” with “Software utilities, including the Roma web tool, can generate each of these derived products.” or some such.
- “… encoding through constraint, constraint via its …” would read better as just “… encoding through constraint via its …”.
- It would be nice if the CSS did something with .
comments on section 2.2
- It is probably worth saying how to encode hard and soft hyphens. Something like “Hard hyphens should be transcribed as the HYPHEN-MINUS character generally available on Wesetern keyboards (i.e. U+002D). Soft hyphens, when transcribed, should be transcribed as SOFT HYPHEN (i.e., U+00AD).”
comments on section 3.5
- Typo in the documentation: <titePart> instead of <titlePart>(Mholmes)