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-3024

ODF 1.1 Alignment Collisions with ODF 1.0 Errata 01

    XMLWordPrintable

    Details

    • Type: Bug
    • Status: Applied
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: ODF 1.0 Errata 01, ODF 1.1
    • Fix Version/s: ODF 1.1 Errata 01
    • Component/s: Public Review
    • Labels:
      None
    • Environment:

      This issue applies for the reconciliation of ODF 1.0 Errata 01 with the ODF 1.1 base text as part of creating ODF 1.1 Errata 01 and ensuring correct transposition in the IS 26300:2006 transposition to ODF 1.1.

    • Proposal:
      Hide

      1. In bringing ODF 1.0 Errata 01 (that is, Part 1) changes into Errata 01 for ODF 1.1, be careful how the four collisions with differences between ODF 1.1 and ODF 1.0 are handled.

      2. Depending on how the four items are brought over to ODF 1.1 Errata 01, be careful whether and how these changes need to be reflected in comments on the FPDAM ballot for alignment of IS 26300:2006 with ODF 1.1.

      Show
      1. In bringing ODF 1.0 Errata 01 (that is, Part 1) changes into Errata 01 for ODF 1.1, be careful how the four collisions with differences between ODF 1.1 and ODF 1.0 are handled. 2. Depending on how the four items are brought over to ODF 1.1 Errata 01, be careful whether and how these changes need to be reflected in comments on the FPDAM ballot for alignment of IS 26300:2006 with ODF 1.1.
    • Resolution:
      Hide

      1. The 9.3.11/Common Image Map Attributes and Elements avoids collision with any place where ODF 1.1 is different and is treated in AMD1.
      2. The 15.27.22 change not being needed in ODF 1.1 is accounted for in Appendix B of ODF 1.1 Errata 01 WD04 and it is confirmed that COR1 aligns with this.
      3. The changes to 16.1/Datatypes under custom datatypes is done in ODF 1.1 Errata 01 so that there is no disconnect with changes made by COR1 and AMD1 together.
      4. No changes are made concerning DOMEvents events in ODF 1.1 Errata 01, and this is accounted for in Appendix B of Errata 01. AMD1 rescinds the COR1 change and aligns with ODF 1.1

      Show
      1. The 9.3.11/Common Image Map Attributes and Elements avoids collision with any place where ODF 1.1 is different and is treated in AMD1. 2. The 15.27.22 change not being needed in ODF 1.1 is accounted for in Appendix B of ODF 1.1 Errata 01 WD04 and it is confirmed that COR1 aligns with this. 3. The changes to 16.1/Datatypes under custom datatypes is done in ODF 1.1 Errata 01 so that there is no disconnect with changes made by COR1 and AMD1 together. 4. No changes are made concerning DOMEvents events in ODF 1.1 Errata 01, and this is accounted for in Appendix B of Errata 01. AMD1 rescinds the COR1 change and aligns with ODF 1.1

      Description

      There are four items in the ODF 1.0 Errata 01 (that is, part 1) where the change is already reflected in the text of ODF 1.1 or else there is another difference in ODF 1.1:

      1. Section 9.3.11 sub-section Common Image Map Attributes and Elements.
      There is an Errata01 change nearby a place where ODF 1.1 is different. The errata instructions should be such that the area of change is not touched.

      2. Section 15.27.22 Errata01 change to style:wrap-dynamic-threshold
      (not -treshold) in the schema fragment has already been changed in 1.1 and
      it will already be handled in the IS 26300 alignment by COR1 and/or the FPDAM. This last should be confirmed, however.

      3. Section 16.1 Datatypes under custom data types has an errata change to
      -length and there are different changes (in other parts of the same text)
      made in 1.1 in contrast to IS 26300:2006. This collision will need to be resolved carefully.

      4. Appendix B Errata01 change to [DOMEvents] appears to be obsoleted by the replacement of [DOMEvents] with
      [DOMEvents2] and [DOMEvents3] in ODF 1.1. Here, the FPDAM may effectively cancel this change if it is made by COR1.

        Attachments

          Activity

            People

            • Assignee:
              orcmid Dennis Hamilton (Inactive)
              Reporter:
              orcmid Dennis Hamilton (Inactive)
            • Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: