-
Type: Bug
-
Status: Applied
-
Priority: Major
-
Resolution: Fixed
-
Affects Version/s: ODF 1.2 Part 3 CD 1
-
Fix Version/s: ODF 1.2 Part 3 CD 2
-
Component/s: Packaging, Schema and Datatypes
-
Labels:None
-
Environment:
This issue applies in the Public Review documents ODF 1.2 Part 3 cd01 (files OpenDocument-v1.2-part3-cd1.pdf, OpenDocument-v1.2-part3-cd1.odt, and the HTML version at http://docs.oasis-open.org/office/v1.2/part3/cd01/OpenDocument-v1.2-part3-cd01.html) and the companion schema file, OpenDocument-manifest-schema-v1.2-cd1.rng
This issue applies in the Public Review documents ODF 1.2 Part 3 cd01 (files OpenDocument-v1.2-part3-cd1.pdf, OpenDocument-v1.2-part3-cd1.odt, and the HTML version at http://docs.oasis-open.org/office/v1.2/part3/cd01/OpenDocument-v1.2-part3-cd01.html ) and the companion schema file, OpenDocument-manifest-schema-v1.2-cd1.rng
-
Proposal:
-
Resolution:
In 6.3.1:
"A namespaced token is a token id that makes use of the XML namespace mechanism for modularization purposes."
is vague and uninformative. The form is not clear and the semantic conditions that apply are not stated (nor are modularization purposes explained and their achievement described).
In the Manifest Schema, the definition
<define name="namespacedToken">
<data type="string">
<param name="pattern">[0-9a-zA-Z_]:[0-9a-zA-Z._\-]</param>
</data>
</define>
is not appropriate for an attribute whose values may be a QualifiedName and which should be Namespace Well-Formed. The pattern does not properly allow NCName for the prefix and for the local name.
See also OFFICE-2157 where this problem is corrected for ODF 1.2 Part 1.
The only use of namespaceToken is as one of the alternative values of a manifest:preferred-view-mode attribute (section 3.8.11). This attribute is new for ODF 1.2 manifest files and their is no impact of a remedy on backward-compatibility with earlier versions of ODF.