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-2250) Replace "required"and "not required" in all normative text

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

Dennis Hamilton commented on OFFICE-2250:

I was wondering how that replacement would apply to the text given as an example.  It appears that the appropriate restatement would be something like

replace "are not required to" with "need not".  Is that the sort of thing that is meant by carrying out of this task?

 - - - - - -


I don't know the context with regard to Complex type support.  I would want to know if Complex is required to be supported before I would tackle the "shall correctly work" in the first sentence.  The "can accept and generate it" certainly merits improvement. 

On reflection, the quoted passage raises all sorts of red flags for me, but I shall save that for an occasion where those issues are in context. -- Dennis

> Replace "required" and "not required" in all normative text
> -----------------------------------------------------------
>                 Key: OFFICE-2250
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2250
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2
>            Reporter: Patrick Durusau
> Global: Replace all usages of "required" or "not required" in normative text. See PI (for a function example) or 6.5 Traditional Complex Number Notation for a more challenging example in prose. 
> Not correcting all the issues but as an illustration:
> "In addition, to meet this capability, all standard infix arithmetic operators for numbers (+, -, *, /, ^), the comparison operators = and <>, postfix %, and prefix "+" and "-" shall correctly work with the Complex type (that is, they can accept and generate it, as appropriate), with the exception that they are not required to accept the Text type as equivalent. Thus, the following formula is true: =(2+3i)+(4+5i)=6+8i. All of these operators shall support complex numbers on either or both sides, in addition to Number on either side."
> Sorry, comparison (and other operators/functions) operators are not subject to "shall" statements. We are defining those operators/functions and it is on our watch what they do/don't support. 
> Rather, evaluators that claim to conform to some level of OpenFormula, support the operators/functions *as we define them.* The burden of making those definitions clear is on us. 

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]