[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Fix editorial inconsistencies in the specification
Tom has cataloged a list of inconsistent language used in various spots in the spec. I have added issue 241 and assigned it to Tom. Since these are all editorial fixes, I propose that the proposed fixes are approved. If nobody expresses dissent by Monday, noon, PDT, I will assume these to be approved by the TC.
1. Tables of attribute values use "Values" as the table heading.
22.214.171.124 type "Standard Values"
126.96.36.199 fs "fs attribute values"
2. For context-specific default values, six entries use "default values for this attribute depend on the element in which it is used:".
188.8.131.52 canOverlap - uses 'value' and 'depends'
184.108.40.206 srcDir - extra comma
3. The value description for most text attributes use "Text".
220.127.116.11 name "Text string".
4. Most content models for empty elements use "This element is always empty."
18.104.22.168 normalization "- empty element"
For all of the above, I propose changing the exceptions to use the most commonly used terminology.
5. Elements from other namespaces are expressed in various ways:
"- elements from any namespace, optional"
"- XML elements from any namespace"
"- Zero, one or more elements from other namespaces."
"Zero, one, or more elements from any namespace."
I propose that all of these be changed to "elements from other namespaces, optional". The rationale is that (a) 'XML' is implicit, (b) 'other' rather than 'any' is consistent with a previous change made to the schema, using '##other', and (c) "zero, one or more" is the same as "optional".
6. Content models that include 'text' express it in various ways.
"- Plain text."
"- Non-translatable text"
I propose that all of these be changed to "Text". I have no objection to retaining "Non-translatable" but it should be part of the accompanying description.