[OASIS Issue Tracker] Commented: (OFFICE-2235) Part 3 section 6.3.1and manifest schema: datatype namespacedToken incorrectly defined

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/OFFICE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16926#action_16926 ] 

Dennis Hamilton commented on OFFICE-2235:
-----------------------------------------

Michael, I think the pattern "[^:]+:[^:]+" is great and we should use it.  According to xml-schema Part 2, the source of the datatype, that should work just fine.

I used the pattern "[\c-[:]]+:[\c-[:]]+" because pattern rules for the data type (also specified in xml-schema Part 2) define "\c" as a special multi-character escape for any character in the set of NameChar characters, including ":" (see http://www.w3.org/TR/xmlschema-2/#nt-MultiCharEsc at the end of Appendix F).   I think [^:] is cleaner than [\c-:].

> Part 3 section 6.3.1 and manifest schema: datatype namespacedToken incorrectly defined
> --------------------------------------------------------------------------------------
>
>                 Key: OFFICE-2235
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2235
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Packaging, Schema and Datatypes
>    Affects Versions: ODF 1.2 Part 3 CD 1
>         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
>            Reporter: Dennis Hamilton
>            Assignee: Michael Brauer
>             Fix For: ODF 1.2
>
>
> 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.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira