[OASIS Issue Tracker] Commented: (OFFICE-1186) Public Comment: Re:[office-comment] ODFF: list of suggestions: TRIMMEAN

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Andreas Guelzow  commented on OFFICE-1186:
------------------------------------------

All function descriptions act after conversion of the arguments to the appropriate type. If we had an argument "Integer x", then the constraint  x= 1 or 2 would of course be applied after conversion, ie. the argument 1.2 would be converted to 1 which then satisfies the constraint. 

Similarly in this case we already have a NumberSequence (or NumberSequenceList in the current version) so conversions has already happened. 

So I would suggest to close this with "No Action".

> Public Comment: Re: [office-comment] ODFF: list of suggestions: TRIMMEAN
> ------------------------------------------------------------------------
>
>                 Key: OFFICE-1186
>                 URL: http://tools.oasis-open.org/issues/browse/OFFICE-1186
>             Project: OASIS Open Document Format for Office Applications (OpenDocument) TC
>          Issue Type: Bug
>          Components: OpenFormula
>    Affects Versions: ODF 1.2
>            Reporter: Robert Weir 
>            Assignee: Eike Rathke
>            Priority: Minor
>             Fix For: ODF 1.2
>
>
> Copied from office-comment list
> Original author: "David King" <openoffice@drking.plus.com> 
> Original date: 22 Dec 2008 23:28:57 -0000
> Original URL: http://lists.oasis-open.org/archives/office-comment/200812/msg00045.html
> > > TRIMMMEAN page 379
> > > * "Let n denote the number of elements in the data set" - that's 
> > > too vague - does it mean elements including or excluding non-
> > > numbers/blank cells? Calc ignores non-numbers. 
> > 
> > That is expressed by declaring the dataSet parameter as NumberSequence.
> I disagree :)
> This highlights my unease at having 'conversion types' - I would 
> be happier if all parameters were defined as 'types', so 
> NumberSequence would be a 'type' that triggered conversion. I'd 
> like to be able to look up any parameter type in the same place.
> In this case it's not clear whether the number of elements is 
> counted before or after conversion.
> "Let n denote the number of elements in dataSet after conversion 
> to NumberSequence" is a bit better, but still less than clear, 
> because dataSet is defined as a NumberSequence as well as being 
> converted to a NumberSequence.
> Actually that's the essence of the prob for me - you can't define 
> a parameter as a NumberSequence and then convert it to a 
> NumberSequence....

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