Details

    • Proposal:
      Hide

      This is a suggestion how to improve the readability of the schema. It should be considered if we restructure the schemas in the next ODF version.

      Show
      This is a suggestion how to improve the readability of the schema. It should be considered if we restructure the schemas in the next ODF version.
    • Resolution:
      Hide

      Adapt schema with style sheet attached to OFFICE-2531 or a modified version of it.

      Show
      Adapt schema with style sheet attached to OFFICE-2531 or a modified version of it.

      Description

      Copied from office-comment list

      Original author: "MURATA Makoto (FAMILY Given)" <eb2m-mrt@asahi-net.or.jp>
      Original date: 17 Nov 2009 02:31:09 -0000
      Original URL: http://lists.oasis-open.org/archives/office-comment/200911/msg00003.html

        Attachments

          Activity

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

          This is a suggestion how to improve the readability of the schema. It should be considered if we restructure the schemas in the next ODF version.

          The schemas in ODF 1.2 are valid and restructuring the schema would result in a equivalent schema. I therefore suggest that we keep them as they are for ODF 1.2.

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - This is a suggestion how to improve the readability of the schema. It should be considered if we restructure the schemas in the next ODF version. The schemas in ODF 1.2 are valid and restructuring the schema would result in a equivalent schema. I therefore suggest that we keep them as they are for ODF 1.2.
          Hide
          orcmid Dennis Hamilton (Inactive) added a comment -

          DISCUSSION REQUESTED

          I think the public comment is more than about readability. It is about compactness, ease of comprehension, and avoidance of errors and misunderstandings.

          The current OpenDocument-manifest-schema-v1.2-cd1.rng RNG Schema file has rote use of multiple layers of reference indirection to express the schema. Part of this involves having separate definitions for each component that is combined into a single element definition, even if there is only one place where the separate definition is combined in. This form of heavy "goto"-like style requires that the entire schema be scanned for combinations when they could easily be placed in-line in the one place they are used.

          This separation may have been valuble when the schema was presented in fragments laced throughout the specification. It allowed having schema-carried definitions near in proximity to the relevant text. This is no longer the case since (1) we no longer have schema fragments interleaved in the text and (2) the organization of the attribute descriptions in the current organization of the ODF 1.2 Part 3 text is done in a way that would be maddening if also followed in the schema.

          The ODF 1.2 Part 3 Manifest Schema is not very large. It should be easy to rewrite it in a more-compact and readily-understandable form. I suggest that we should attempt the simplification to confirm whether the improvements justify the change. This is not an automatic precedent for Part 1, since the ODF 1.2 Part 1 main schema has definitions that are separated out for sharing and re-use in multiple parts of the schema.

          Since consultation of a separate schema file (or a schema all in one place in the specification) is now required, I recommend that we give serious attention to making the schema more compact and straightforward.

          Show
          orcmid Dennis Hamilton (Inactive) added a comment - DISCUSSION REQUESTED I think the public comment is more than about readability. It is about compactness, ease of comprehension, and avoidance of errors and misunderstandings. The current OpenDocument-manifest-schema-v1.2-cd1.rng RNG Schema file has rote use of multiple layers of reference indirection to express the schema. Part of this involves having separate definitions for each component that is combined into a single element definition, even if there is only one place where the separate definition is combined in. This form of heavy "goto"-like style requires that the entire schema be scanned for combinations when they could easily be placed in-line in the one place they are used. This separation may have been valuble when the schema was presented in fragments laced throughout the specification. It allowed having schema-carried definitions near in proximity to the relevant text. This is no longer the case since (1) we no longer have schema fragments interleaved in the text and (2) the organization of the attribute descriptions in the current organization of the ODF 1.2 Part 3 text is done in a way that would be maddening if also followed in the schema. The ODF 1.2 Part 3 Manifest Schema is not very large. It should be easy to rewrite it in a more-compact and readily-understandable form. I suggest that we should attempt the simplification to confirm whether the improvements justify the change. This is not an automatic precedent for Part 1, since the ODF 1.2 Part 1 main schema has definitions that are separated out for sharing and re-use in multiple parts of the schema. Since consultation of a separate schema file (or a schema all in one place in the specification) is now required, I recommend that we give serious attention to making the schema more compact and straightforward.
          Hide
          michael.brauer Michael Brauer (Inactive) added a comment -

          I have applied the style sheet that is attached to comment (after modifying it slightly). See

          http://lists.oasis-open.org/archives/office/201004/msg00270.html

          I propose that we use the adapted schemas for ODF 1.2.

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - I have applied the style sheet that is attached to comment (after modifying it slightly). See http://lists.oasis-open.org/archives/office/201004/msg00270.html I propose that we use the adapted schemas for ODF 1.2.
          Hide
          michael.brauer Michael Brauer (Inactive) added a comment -

          I'm setting the issue to resolved, but add a "NEEDS-DISCUSSION"

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - I'm setting the issue to resolved, but add a "NEEDS-DISCUSSION"
          Hide
          michael.brauer Michael Brauer (Inactive) added a comment -

          This is the part 3 counterpart to OFFICE-2531. OFFICE-2531 was discussed in the 05/03/2010 call. No objections for refactoring the schema was raised. I'm therefore resetting the NEEDS-DISCUSSION.

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - This is the part 3 counterpart to OFFICE-2531 . OFFICE-2531 was discussed in the 05/03/2010 call. No objections for refactoring the schema was raised. I'm therefore resetting the NEEDS-DISCUSSION.
          Hide
          michael.brauer Michael Brauer (Inactive) added a comment -

          Correction appears in the OpenDocument-v1.2-part3-cd01-rev03 schemas.

          Show
          michael.brauer Michael Brauer (Inactive) added a comment - Correction appears in the OpenDocument-v1.2-part3-cd01-rev03 schemas.

            People

            • Assignee:
              michael.brauer Michael Brauer (Inactive)
              Reporter:
              rcweir Robert Weir (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: