← Prev in month ← Prev in thread
Next in thread → Next in month →

[OASIS Issue Tracker] Commented: (OFFICE-2650) PROB

From
OASIS Issues Tracker <>
Date
2010-04-27T00:43:24+00:00
ID
884636179.1741272329004853.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Commented: (OFFICE-2650) PROB
[ http://tools.oasis-open.org/issues/browse/OFFICE-2650?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18865#action_18865 ] 

Andreas Guelzow  commented on OFFICE-2650:
------------------------------------------

There is nothing in the current statement that says that the data needs to be ordered. We have discussed this before. 

I think we should restrict ourselves to specifying conditions that have to hold rather than going on about conditions that need not hold.

We already say:
Note that if End Start then PROB returns 0 since in this case I d i , Start , End =0 for all i.



> PROB
> ----
>
>                 Key: OFFICE-2650
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-2650
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Sub-task
>          Components: OpenFormula
>    Affects Versions: ODF 1.2 Part 2 CD 2
>            Reporter: Robert Weir 
>
> PROB
> *This needs to specify if Data must be ordered or not (unordered?).
> *It would also be better to be clear about whether Data must be 
> sequential (is 1, 2, 3, 5 (missing 4) OK?) and/or integer (is 1, 2.5, 3, 
> 4 OK?).
> *It would also be better to be clear about whether Start and End need to 
> exist within Data (no?) and also whether they can be higher/lower than 
> the max/min values in Data (yes?)
> * It would also be better to be clear about whether Start can be higher 
> than End. Although they're defined as lower/upper bounds, is 'Start>End' 
> an error, or valid with a probability of 0 returned?
> * This needs to specify how the result is calculated if End is omitted 
> and Start is not present in Data (Calc returns 0).
> * This needs to specify the type of error returned - eg #N/A if Data, 
> Probability are different lengths. This is important because #N/A is a 
> specific (testable) type of error.

-- 
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
← Prev in month ← Prev in thread
Next in thread → Next in month →