[OASIS Issue Tracker] Updated: (ODATA-239) Allowing expressions to be passed as parameters to (super) functions

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

     [ http://tools.oasis-open.org/issues/browse/ODATA-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-239:
-----------------------------

       Proposal: 
Relax ABNF from

functionExprParameter  = functionParameterName EQ ( parameterValue / firstMemberExpr )

to

functionExprParameter  = functionParameterName EQ ( parameterValue / commonExpr )
    Environment: [Proposed]
    Description: 
To be able to use/extend the set of functions that can be used in a $apply query option functions need parameters of type expression, which expression can then be applied to each and every instance in the set they are processing. 
An very simple example of such a function would:

$apply=GroupBy()/TopN(N=5, Value=Revenue)

Where 5 is just a number indicating the top N we are interested in but were 'Revenue' is actually an expression referring to the Revenue property of the entity in the set the function is acting upon. A better example in which this becomes more apparent would be:

$apply=GroupBy()/TopN(N=5, Value=Revenue sub Cost)

For build in functions we can obviously simply define this but currently there is no way of defining a 'custom' function that could implement the same behavior because we can't pass in expressions.

We then could annotate these functions to signal to tools that they can be used in $apply.

  was:
To be able to use/extend the set of functions that can be used in a $apply query option functions need parameters of type (lambda) expression, which expression can then be applied to each and every instance in the set they are processing. 
An very simple example of such a function would:

$apply=GroupBy()/TopN( 5, Revenue )

Where 5 is just a number indicating the top N we are interested in but were 'Revenue' is actually an expression refering to the Revenue property of the entity in the set the function is acting upon. A better example in which this becomes more apparent would be:

$apply=GroupBy()/TopN( 5, Revenue - Cost )

For build in functions we can obviously simply define this but currently there is no way of defining a 'custom' function that could implement the same behavior because we can't pass in expressions.



> Allowing expressions to be passed as parameters to (super) functions
> --------------------------------------------------------------------
>
>                 Key: ODATA-239
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-239
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>          Components: OData CSDL
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>
> To be able to use/extend the set of functions that can be used in a $apply query option functions need parameters of type expression, which expression can then be applied to each and every instance in the set they are processing. 
> An very simple example of such a function would:
> $apply=GroupBy()/TopN(N=5, Value=Revenue)
> Where 5 is just a number indicating the top N we are interested in but were 'Revenue' is actually an expression referring to the Revenue property of the entity in the set the function is acting upon. A better example in which this becomes more apparent would be:
> $apply=GroupBy()/TopN(N=5, Value=Revenue sub Cost)
> For build in functions we can obviously simply define this but currently there is no way of defining a 'custom' function that could implement the same behavior because we can't pass in expressions.
> We then could annotate these functions to signal to tools that they can be used in $apply.

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