• Type: Bug
    • Resolution: Duplicate
    • Priority: Major
    • None
    • Affects Version/s: ODF 1.2 Part 3 CD 1
    • 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

    • 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).
    • Hide

      This is a duplicate to OFFICE-2233.

      Show
      This is a duplicate to OFFICE-2233 .

      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#"
      "-^

            Assignee:
            Michael Brauer (Inactive)
            Reporter:
            Dennis Hamilton (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated:
              Resolved: