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] Commented: (OFFICE-3502) ODF 1.2 CD05-119.598: table:condition semantics over-specific

    [ http://tools.oasis-open.org/issues/browse/OFFICE-3502?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=22595#action_22595 ] 

Dennis Hamilton commented on OFFICE-3502:

Andreas, I agree with you about how this should work.  However, the "stop" default action on the error message says that the operation in progress (presumably entry of data) is stopped.  Also, I don't say the value can't be entered into a cell, although we have at least one member on the OpenFormula SC who say that table:condition does do that.  In fact, for there to be simply informational or warning messages, obviously the value is in the cell.

I don't agree with entry being prevented, but here under 19.958 does not seem to be the place to reconcile that.  The heavy lifting needs to be done in the tightening of what <table:content-validation> is specified to do.

Notice that my proposal does not suggest that entry of a value in a cell is prevented.  In fact, I preserve the idea that the condition applies to "the value of a cell" not something else, like "a value for a cell" or somesuch..

> ODF 1.2 CD05-1 19.598: table:condition semantics over-specific
> --------------------------------------------------------------
>                 Key: OFFICE-3502
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-3502
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: Part 1 (Schema), Table
>    Affects Versions: ODF 1.2 CD 05
>            Reporter: Dennis Hamilton
>            Assignee: Dennis Hamilton
>             Fix For: ODF 1.2 CD 06
> In ODF 1.2 CD05-1 19.598, the first paragraph begins with these sentences:
> """
> The table:condition attribute specifies the condition that determines whether a cell content is valid in regard to a validation rule or not. A cell content is valid if the condition evaluates to "true".
> """
> This statement is inaccurate and too strict.  The condtion can be used for other than the determination of the validity of a table cell's content.  According to the definition of the <table:content-validation> there are a variety of ways that the table:condition can be used.  In particular, the associated <table:error-message> element can specify that the table:condition produces a warning message or simply an information-only message.  Although it is the default to take the table:condition satisfaction as causing an operation to stop, that is not the only case.  (And stopping an operation is an odd way to say this, since the operation is the validation.)   I suspect the more-correct interpretation of "stop" is to require a different value to be entered for the cell, although that won't always be possible.  (E.g., consider a cell whose value is determined by a formula for which the table:condition applies and is satisfied.)
> The initial two sentences need to be softened to admit of other possibilities, including use for purposes other than determining that a value is invalid.

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]