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

ODF 1.2-1 9.4.8 <table:error-macro> contradictory and not implementable

    XMLWordPrintable

    Details

    • Proposal:
      Hide

      [Dennis]

      1. Remove <table:content-validation> or deprecate it or specify that the entire thing is implementation-dependent; or

      2. Deprecate the use of <table:error-macro> and <office:event-listeners> in <table:content-validation> and allow <table:error-message> to be present and to pre-empt any <table:error-macro> and <office:event-listeners> elements when macros are not supported or the implementation-dependent use is not recognized by a consumer; or

      3. Specify that any use of <office:event-listeners> in conjunction with <table:error-macro> is implementation-dependent and identify the [DOMEvents2] Event Name that for ODF 1.2,shall apply to the case of input validation.

      • or -

      [Eike]

      In the schema of <element name="table:content-validation">, for "table-error-macro" remove <optional> from "office-event-listeners", so replace
      "
      <group>
      <ref name="table-error-macro"/>
      <optional>
      <ref name="office-event-listeners"/>
      </optional>
      </group>
      "
      with
      "
      <group>
      <ref name="table-error-macro"/>
      <ref name="office-event-listeners"/>
      </group>
      "

      Show
      [Dennis] 1. Remove <table:content-validation> or deprecate it or specify that the entire thing is implementation-dependent; or 2. Deprecate the use of <table:error-macro> and <office:event-listeners> in <table:content-validation> and allow <table:error-message> to be present and to pre-empt any <table:error-macro> and <office:event-listeners> elements when macros are not supported or the implementation-dependent use is not recognized by a consumer; or 3. Specify that any use of <office:event-listeners> in conjunction with <table:error-macro> is implementation-dependent and identify the [DOMEvents2] Event Name that for ODF 1.2,shall apply to the case of input validation. or - [Eike] In the schema of <element name="table:content-validation">, for "table-error-macro" remove <optional> from "office-event-listeners", so replace " <group> <ref name="table-error-macro"/> <optional> <ref name="office-event-listeners"/> </optional> </group> " with " <group> <ref name="table-error-macro"/> <ref name="office-event-listeners"/> </group> "
    • Resolution:
      Hide

      In the schema of <element name="table:content-validation">, for "table-error-macro" remove <optional> from "office-event-listeners", so replace
      "
      <group>
      <ref name="table-error-macro"/>
      <optional>
      <ref name="office-event-listeners"/>
      </optional>
      </group>
      "
      with
      "
      <group>
      <ref name="table-error-macro"/>
      <ref name="office-event-listeners"/>
      </group>
      "

      Show
      In the schema of <element name="table:content-validation">, for "table-error-macro" remove <optional> from "office-event-listeners", so replace " <group> <ref name="table-error-macro"/> <optional> <ref name="office-event-listeners"/> </optional> </group> " with " <group> <ref name="table-error-macro"/> <ref name="office-event-listeners"/> </group> "

      Description

      The description for 9.4.8 contradicts the schema and the possibilities of the <office:event-listeners> element.

      The contradictory text and unimplementable cases start with this text in 9.4.8:

      """
      "The <table:error-macro> element specifies if a macro should be executed upon an attempt to enter invalid content.

      Such a macro is specified by an <office:event-listeners> element. 14.4 The event name shall be one that specifies an event that is called on invalid user input.
      """

      Problem 1: The presence of a <table:error-macro> element in a <table:content-validation> element prevents the presence of a <table:error-message> element according to the current schema. There is therefore no means to determine whether a validation failure is merely informational or a warning.

      Problem 2: However, the <table:error-macro> table:execute attribute can specify that the macro is not to be executed. In this case, it appears that validation can silently fail.

      Problem 3: According to the schema for <table:content-validation>, it is optional for an <office:event-listeners> element to accompany the <table:error-macro> element. This appears to contradict the shall provision and the need to specify an appropriate macro.

      Problem 4: It would appear that the only meaningful case of <office:event-listeners> is with one or more (optional) <script:event-listener> elements.

      Problem 5: There is no defined script:event-name defined in the schema, in section 19.431, or in [DOMEvents2] establisehd for "invalid user input" (see above), so there is no specified way for the shall to be honored.

        Attachments

          Activity

            People

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

              Dates

              • Created:
                Updated:
                Resolved: