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

19.598: Table:Condition - location of namespace prefix seems scoped incorrectly

    XMLWordPrintable

    Details

    • Proposal:
      Hide

      1. The proposal is to affirm that the namespace bindings for the syntax and semantics of all places where "expression" is permitted is to be established with a prefix at the beginning of the attribute. OpenFormula is the default when there is no prefix.. This needs to be emphasized very clearly.
      2. The proposal is to also to add is-true-formula(<expression>) to the syntax.
      3. The OpenFormula SC also requests the ODF TCs concurrence that OpenFormula is intended to be the default in this way and that any prefix applies only to the syntax and semantics of the <expression> parts and not the overall condition syntax.

      Show
      1. The proposal is to affirm that the namespace bindings for the syntax and semantics of all places where "expression" is permitted is to be established with a prefix at the beginning of the attribute. OpenFormula is the default when there is no prefix.. This needs to be emphasized very clearly. 2. The proposal is to also to add is-true-formula(<expression>) to the syntax. 3. The OpenFormula SC also requests the ODF TCs concurrence that OpenFormula is intended to be the default in this way and that any prefix applies only to the syntax and semantics of the <expression> parts and not the overall condition syntax.
    • Resolution:
      Hide

      It is agreed that the namespace for syntax and semantics of each individual expression allowed in the table:condition formula is the namespace bound to the namespace prefix at the beginning of the attribute, or the default if no prefix is provided.

      [added 2010-10-26T22:07Z by dh] In the first paragraph, the change recommended in OFFICE-3491 is an appropriate wording. It is important, in whatever modification is made to the first paragraph, that it is clear that the particular syntactic patterns (with italicized names) within the table:condition syntax are where the established namespace applies.

      Other issues with regard to the syntax and semantics of such expressions and the use of arbitrary expressions are handled by sub-task issues.

      Show
      It is agreed that the namespace for syntax and semantics of each individual expression allowed in the table:condition formula is the namespace bound to the namespace prefix at the beginning of the attribute, or the default if no prefix is provided. [added 2010-10-26T22:07Z by dh] In the first paragraph, the change recommended in OFFICE-3491 is an appropriate wording. It is important, in whatever modification is made to the first paragraph, that it is clear that the particular syntactic patterns (with italicized names) within the table:condition syntax are where the established namespace applies. Other issues with regard to the syntax and semantics of such expressions and the use of arbitrary expressions are handled by sub-task issues.

      Description

      In section 19.598, it has the following text: "The value of this attribute should be a namespace prefix, followed by a ":" (COLON, U+003A), followed by Boolean expression. ". This implies placing the namespace prefix at the beginning of the condition string, immediately preceding the condition. For example:

      table:condition="of:cell-content-is-decimal-number() and cell-content-is-between(1,[.B1])"

      Given that the OF namespace specifies the syntax for an expression used as a value in a condition, is this the best place for it? Should it be as follows instead?

      table:condition="cell-content-is-decimal-number() and cell-content-is-between(1,of:[.B1])"

        Attachments

          Activity

            People

            • Assignee:
              orcmid Dennis Hamilton (Inactive)
              Reporter:
              ericpa Eric Patterson (Inactive)
            • Watchers:
              1 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: