[OASIS Issue Tracker] Updated: (ODATA-230) Support use of parameter aliases in $filter and $orderby

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

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

Ralf Handl updated ODATA-230:
-----------------------------

    Proposal: 
Propose to make @param a valid common expression that can be used throughout the URL syntax.

The parameter value must be a primitive value, complex value, or collection value.

Accepted: https://www.oasis-open.org/committees/download.php/48097/odata-meeting-23_on-20130130_31-F2F-minutes.html#odata-230

  was:
Propose to make @param a valid common expression that can be used throughout the URL syntax.

The parameter value must be a primitive value, complex value, or collection value.


> Support use of parameter aliases in $filter and $orderby
> --------------------------------------------------------
>
>                 Key: ODATA-230
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-230
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules v1.0, OData CSDL v1.0, OData Protocol v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Priority: Minor
>             Fix For: WD01
>
>
> Today parameter aliases can be used in the path portion of a request, but not the $filter or $orderby operations.
> We would like to add support for parameter aliases in $filter and $orderby, for example:
>   ~Movies?$filter=substringof(Title,@title)&@title='supercomputer'
>  or even 
> ~Movies?$filter=Title eq @title&@title='Wizard of Oz'

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