Details

    • Type: Bug
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.0, ODF 1.0 (second edition), ODF 1.1, ODF 1.2, ODF 1.2 Part 1 CD 4
    • Fix Version/s: ODF 1.2 Part 1 CD 5
    • Component/s: Schema and Datatypes
    • Labels:
      None
    • Environment:

      This issue applies to all definitions and use of namespaceToken since its introduction in OASIS OpenDocument 1.0

    • Proposal:
      Hide

      Redefine namspacedToken:


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

      Show
      Redefine namspacedToken: — A namespacedToken value is an [xmlschema-2] QName that matches the definition of PrefixedName in §4 of [xml-names] .
    • Resolution:
      Hide

      Redefined namspacedToken:


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

      Show
      Redefined namspacedToken: — A namespacedToken value is an [xmlschema-2] QName that matches the definition of PrefixedName in §4 of [xml-names] .

      Description

      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

        Attachments

          Activity

            People

            • Assignee:
              michael.brauer Michael Brauer (Inactive)
              Reporter:
              orcmid Dennis Hamilton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: