OASIS Open Document Format for Office Applications (OpenDocument) TCIcon indicating the project type

OASIS Open Document Format for Office Applications (OpenDocument) TC

Uploaded image for project: 'OASIS Open Document Format for Office Applications (OpenDocument) TC'
  1. OASIS Open Document Format for Office Applications (OpenDocument) TC
  2. OFFICE-2232

Part 3 Appendix B DSIG Schema is Invalid XML

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Duplicate
    • Affects Version/s: ODF 1.2 Part 3 CD 1
    • Fix Version/s: None
    • Component/s: Packaging, Schema and Datatypes
    • Labels:
      None
    • Environment:

      This issue applies to the ODF 1.2 Part 3 CD 01 under public review. The defect applies to OpenDocument-v1.2-part3-cd1.pdf and OpenDocument-v1.2-part3-cd1.odt

    • Proposal:
      Hide

      1. Change the xmlns declarations in this RNG schema to not use "xml" in the prefix names.

      2. "odf" would be a better choice, as in "odfdsig", because this is a specific profiling of the XML DSIG specification (ignoring the degree to which the profiling might be underspecified or not).

      Show
      1. Change the xmlns declarations in this RNG schema to not use "xml" in the prefix names. 2. "odf" would be a better choice, as in "odfdsig", because this is a specific profiling of the XML DSIG specification (ignoring the degree to which the profiling might be underspecified or not).
    • Resolution:
      Hide

      This is a duplicate to OFFICE-2233.

      Show
      This is a duplicate to OFFICE-2233 .

      Description

      The file at <http://docs.oasis-open.org/office/v1.2/part3/cd01/OpenDocument-dsig-schema-v1.2-cd1.rng> is invalid XML.

      The use of a namespace prefix beginning with the letters "xml" is in violation of the XML and XML Namespace specifications.

      Internet Explorer 8 points out the problem with this report:

      "The XML page cannot be displayed

      "Cannot view XML input using XSL style sheet. Please correct the error and then click the Refresh button, or try again later.

      "--------------------------------------------------------------------------------

      "The namespace prefix is not allowed to start with the reserved string "xml". Error processing resource 'http://docs.oasis-o...

      " xmlns:xmldsig="http://www.w3.org/2000/09/xmldsig#"
      "-^

        Attachments

          Activity

          Ascending order - Click to sort in descending order
          Hide
          Permalink
          orcmid Dennis Hamilton (Inactive) added a comment -

          Sorry about the peculiar JIRA report. I made this issue by cloning another one and modifying it. This updating of the clone creates a change report rather than a "new issue" report. I won't do that again.

          Show
          orcmid Dennis Hamilton (Inactive) added a comment - Sorry about the peculiar JIRA report. I made this issue by cloning another one and modifying it. This updating of the clone creates a change report rather than a "new issue" report. I won't do that again.
          Hide
          Permalink
          michael.brauer Michael Brauer (Inactive) added a comment -

          This is a duplicate to OFFICE-2233.

          That IE8 throws a fatal error actually seems to be a bug in IE. The XML 1.0 specification in sections 2.3 and 3.0 just states that names starting with "XML" are reserved. There are no well-formedness or validation constrains that state that they are an error. The XML Namespaces 1.0 specification in section 3 states explicitly: "processors must not treat them as fatal errors".

          But, yes, the namespace prefix should be changed as described in OFFICE-2233

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - This is a duplicate to OFFICE-2233 . That IE8 throws a fatal error actually seems to be a bug in IE. The XML 1.0 specification in sections 2.3 and 3.0 just states that names starting with "XML" are reserved. There are no well-formedness or validation constrains that state that they are an error. The XML Namespaces 1.0 specification in section 3 states explicitly: "processors must not treat them as fatal errors". But, yes, the namespace prefix should be changed as described in OFFICE-2233
          Hide
          Permalink
          michael.brauer Michael Brauer (Inactive) added a comment -

          Duplicate.

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - Duplicate.

            People

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

              Dates

              • Created:
                Updated:
                Resolved: