OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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



     [ http://tools.oasis-open.org/issues/browse/OFFICE-2235?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Hamilton updated OFFICE-2235:
------------------------------------

        Summary: Part 3 section 6.3.1 and manifest schema: datatype namespacedToken incorrectly defined  (was: Part 3 section 7.3.1 and manifest schema: datatype namespacedToken incorrectly defined)
       Proposal: 
1. Replace the text in Part 3 section 6.3.1 with 

"A namespacedToken value is an [xmlschema-2] QName that matches the definition of PrefixedName in §4 of [xml-names]."

2. In the Manifest Schema, replace the definition of namespacedToken by

    <define name="namespacedToken">
            <data type="QName">
                    <param name="pattern">[\c-[:]]+:[\c-[:]]+</param>
            </data>
    </define>

using a proper regular expression that requires the QName to have a ":" character so that only PrefixedNames work.   (The regexp shown is in the form that works as an  [xmlschema-2] restriction pattern where the "\c" escape refers to any XML Name character.)

  was:
1. Replace the text in Part 3 section 7.3.1 with 

"A namespacedToken value is an [xmlschema-2] QName that matches the definition of PrefixedName in §4 of [xml-names]."

2. In the Manifest Schema, replace the definition of namespacedToken by

    <define name="namespacedToken">
            <data type="QName">
                    <param name="pattern">[\c-[:]]+:[\c-[:]]+</param>
            </data>
    </define>

using a proper regular expression that requires the QName to have a ":" character so that only PrefixedNames work.   (The regexp shown is in the form that works as an  [xmlschema-2] restriction pattern where the "\c" escape refers to any XML Name character.)

    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  (was: This issue applies in 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)
    Description: 
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.

  was:
In 7.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 4.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.


Updated to refer to the correct sections of the Public Review editions of Part3 cd01.

> 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




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]