OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

office message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Updated: (OFFICE-3491) 19.598 table:conditionsyntax ambiguity

     [ http://tools.oasis-open.org/issues/browse/OFFICE-3491?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Hamilton updated OFFICE-3491:

1. In the last sentence of the first paragraph of 19.598 table:condition, replace

The XML namespace name bound to the namespace prefix specifies the syntax and semantics of the expressions and values occurring within the condition.

with the text

The XML namespace that applies to the table:condition attribute specifies the syntax and semantics of the expression occurrences in the table:condition syntax.
 ***NOTE: The word "expression" should be in italics in the above sentence.***

2.  Replace the list item for numberValue to read as follows:
numberValue is a whole or decimal number in the lexical form of the [xmlschema-2] decimal datatype.
[Ed.note: "numberValue" and "decimal" are in fixed-pitch.]
3. Replace the list item for string to read
string expresses a value of the [xmlschema-2] string datatype by surrounding the sequence of string characters in quotation marks (QUOTE, U+0022).  A quotation mark within the string itself is expressed with two consecutive quotation marks.
[Ed.Note: The first occurrence of "string" is in italic.  The remaining 3 occurrence of "string" are in fixed-pitch.]

3. In the list item for string, specify what the quotation marks are and also indicate if there is any way to specify a quotation mark within the string.  (" won't work because that changes the attribute value and breaks the table:condition formula.)

4. In the list item for expression replace

expression is an expression. Expressions defined by part 2 of this specification shall not start with an "=" (U+003D, EQUALS SIGN).


expression is a lexical form that is neither numberValue nor string and that is a well-formed expression determined by the namespace applicable to the table:condition value."""

*** Ed.Note: the first occurences of expression, numberValue, and string in the replacement text are in italics. ***

Provide a resolution that does not rely on the bound expression evaluator for recognition of numberValue and string.

> 19.598 table:condition syntax ambiguity
> ---------------------------------------
>                 Key: OFFICE-3491
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3491
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Needs Discussion, Part 1 (Schema), Table
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> The special syntax for table:condition is ambiguous.
> In the first paragraph, it is said that the namespace prefix (default or otherwise) applies to the syntax and semantics of values, strings, and expressions. 
> To then stipulate the syntax of *value* and *string* is peculiar. 
> I think the repair should be in the first paragraph, where the namespace governs only the syntax and semantics of the *expression* pattern. This allows simple table:condition forms that avoid dependence on any separate formula specification altogether. 
> However it does mean that we have trouble when an *expression* under the namespace has exactly the same lexical appearance as what is defined here as a *value* or *string* pattern. I would suggest that the *value* and *string* rules would have precedence and *expression* is to be considered only when the the occurence is not a well-formed *value* or *string*. 
> Finally, I note that the statement about leading "=" is worded as if it is a restriction on Part 2. I believe there is a separate proposal to strike that. 
> The repair to this should allow a table:condition that has simple values and strings as operands without any use of namespace-determined expressions.

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]