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-2331) OpenFormula 3.1generally

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

Dennis Hamilton commented on OFFICE-2331:

Note that the described changes have been made to draft18-editor-revision.

1. Nuke the "portable document" statement.  The condition applies to any conforming formula and so associating it with the portable case is completely unnecessary.  It even seems to imply that a portable document can depend on all of the types, which is probably not the case.

2. We need to determine whether reference and reference list are actually types are are simply forms that determine operands.  In some case, the operand really is a reference, as in MULTIPLE.OPERATION) because the substitution rules require accessing the formula and then more formulas.  But that does not mean reference exists as a data type.  We need to sort that out.

> OpenFormula 3.1 generally
> -------------------------
>                 Key: OFFICE-2331
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2331
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 Part 2 CD 1
>            Reporter: Patrick Durusau
> The paragraphs of 3.1 are problematic in general. Rather that issue a flock of JIRA issues, here is how I propose to dispose of these paragraphs:
> 1) First paragraph. Delete entirely. That formulas/expressions always return values may need to be said but it doesn't fit under a discussion of types. That tables cells may or may not have values and that those values may be "constant" or the result of applying a formula, doesn't belong here, either. We agreed on the conference call earlier today to remove the last two sentences.
> 2) Second paragraph. Delete entirely. In part because of: "many functions," "some types," "different ways," etc. All of this is important but should be stated as either definitions or requirements under the functions in question. 
> 3) Third paragraph: If we keep the type v. pseudotype distinction, the statement would be: In OpenFormula a value is of one of the following types: (list types). And move it to the first paragraph. 
> The rest of that paragraph should be moved to appropriate locations and converted to evaluator language. 
> 4) Forth paragraph: I await resolution of the portable document issue on this one. 

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]