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-2251) Value requirements -DDB for example - "Must be a positive integer."



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

Andreas Guelzow  commented on OFFICE-2251:
------------------------------------------

I should have pointed out that in the specific example "DDB" there are currently no constraints listed which would be misleading since we have this "positive integer" mentioned in the semantics section. So it would not be clear (to me) what should happen. 

Note that we can call DBB with a lifeTime value of 3.4 since this, due to the Integer requirement of the argument, would be converted (truncated) to 3.

> Value requirements - DDB  for example - "Must be a positive integer."
> ---------------------------------------------------------------------
>
>                 Key: OFFICE-2251
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2251
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2
>            Reporter: Patrick Durusau
>
> Value requirements aren't "must"/"shall", etc. The current text under parameters reads: "lifeTime: the number of periods that the depreciation will occur over. Must be a positive integer."
> No, we are *defining* the function and so state: "lifeTime: the number of periods that the depreciation will occur over. A positive integer."
> Such that if I have an evaluator that properly implements DDB, by definition it only accepts a positive integer for lifeTime. 
> May seem like a small thing but the text becomes confusing when value types are may/will/must, etc. Simply state the requirement and then leave it alone.
> This is an example case. Will sweep for others.

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