Details

    • Type: Bug
    • Status: Applied
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: ODF 1.0
    • Fix Version/s: ODF 1.0 Errata CD 5
    • Component/s: Conformance
    • Labels:
      None
    • Environment:

      This issue remains applicable to Errata 01 CD04

    • Proposal:
      Hide

      Research the rules for validation that is explicitly stated for XML Documents consumed by ODF processors and determine whether there is anything to be addressed with regard to DTD processing and how it influences the XML.

      Show
      Research the rules for validation that is explicitly stated for XML Documents consumed by ODF processors and determine whether there is anything to be addressed with regard to DTD processing and how it influences the XML.
    • Resolution:
      Hide

      2.1.2 Document Root Attributes
      Delete:
      "If the file has a version known to an XML processor, it may validate the document. Otherwise, it is optional to validate the document, but the document must be well formed."

      Show
      2.1.2 Document Root Attributes Delete: "If the file has a version known to an XML processor, it may validate the document. Otherwise, it is optional to validate the document, but the document must be well formed."

      Description

      Submitter ID
      GB-26300-38
      Nature of defect
      Technical
      Document
      ISO/IEC 26300:2006
      Clause
      2.1.2
      Page
      38
      Description of issue

      It is stated that:

      The version number is in the format revision.version. If the file has a version known to an XML processor, it may validate the document. Otherwise, it is optional to validate the document, but the document must be well formed.

      However:

      • No "XML Processor" has an understanding of such attributes. Perhaps what is meant here is "ODF processor"?
      • There is a false opposition between the two given behaviours here since one is governed by the word "may" and the other is described as optional. So as stated, both behaviours are in fact optional; furthermore there is an implication that a document with an unrecognized version attribute may not be well-formed. This is confusing.
      • DTD-governed MathML content within ODF documents may have different content depending on how the DTD is processed, since the DTD contains attribute defaulting; so the different behaviours given here may result in different documents. The behaviour in such circumstances should be clarified (even if to state it is application-dependent).

      Proposal

      Amend the text to resolve the above defects.

        Attachments

          Activity

            People

            • Assignee:
              svante.schubert Svante Schubert
              Reporter:
              rcweir Robert Weir (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: