[OASIS Issue Tracker] Commented: (OFFICE-2157) 17.3.19namespaceToken incorrectly defined

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

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

Michael Brauer commented on OFFICE-2157:
----------------------------------------

We have a more restrictive definition of a namespaceToken than a QName since ODF 1.0. Switching to a QName may be possible and reasonable, but it permits values we have not permitted before. So, it is nothing that we in my opinion should do for ODF 1.2, but consider to so for ODF-Next.

For ODF 1.2, I suggest that we amend the description of 17.3.19 namespaceToken as follows:

-----
A namespaced token is a token id that makes use of the XML namespace mechanism for modularization purposes.

A namespaced token shall consist of a namepscace prefix, followed by a ":" (COLON, 0x003A), followed by a local identifier. The namespace prefix shall be declared. The namespace bound to the namespace prefix establishes a unique context in which the local identifier is to be understood.
----

> 17.3.19 namespaceToken incorrectly defined
> ------------------------------------------
>
>                 Key: OFFICE-2157
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2157
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Schema and Datatypes
>    Affects Versions: ODF 1.0, ODF 1.0 (second edition), ODF 1.1, ODF 1.2
>         Environment: This issue applies to all definitions and use of namespaceToken since its introduction in OASIS OpenDocument 1.0
>            Reporter: Dennis Hamilton
>             Fix For: ODF 1.2
>
>
> 1. The namespaceToken syntax is incorrect.  The schema specifies
>     <define name="namespacedToken">
>         <data type="string">
>             <param name="pattern">[0-9a-zA-Z_]+:[0-9a-zA-Z._\-]+</param>
>        </data>
>     </define>
> This is incorrect syntax for a PrefixedName [xml-names].  That is not the syntax of NCNames and Prefix and LocalName strings.  
> It is more correct to simply state that the value shall have PrefixedName syntax [xml-names].  
> 2. There is very little semantics for the namespaceToken.  In particular, the rules for conformance under [xml-names] should apply.  Something like the following would do the job:
>  ---
> The attribute value taken as a qualified name shall satisfy the "Namespace constraints [xml-names]" in the place where an attribute having a value of this type occurs.   The namespacedToken value signifies the expanded name that is the resulting interpretation of the qualified name.
>  ---
> 3. Ambiguity between PrefixedName and QualifiedName.
> In ODF 1.0 section 16.1, an example is provided to illustrate how namespacedTokens are used to provide unambiguous extensibility by using PrefixedNames.  This example ties into the illustration of predefined chart types that are available as values of the <chart:chart> chart:class attribute.  This is carried through into ODF 1.1.
> In ODF 1.2 Part 1 17.3.19 (cd03 rev03), there is no longer any explanation of the format or how it is to be understood, even with an example.  There is a vague indication of what it is for that is not very understandable.  The use of chart:class with <chart:chart> in section 18.15.1 omits the illustrations and the listed defined values do not show the required prefix.
> 4. It is desirable to have this defined in such a way that it will be clear what the form is for all values of namespacedToken type and how predefined values, if any, are expressed.
> Related Issues
> OFFICE-702 for discussion of namespacedToken and attributes having values of namespacedToken type.
> OFFICE-2148 XML Namespaces
> OFFICE-2156 [xml-names] ODF 1.2 Profile

-- 
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