[OASIS Issue Tracker] (ODATA-1109) Clarify that 'parameter' aliases can also be used to substitute expressions

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

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

Michael Pizzo updated ODATA-1109:
---------------------------------

    Proposal: 
Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter).  All other parameters defined as query options are evaluated in the context of the resource identified by the URL path segment in which they are used and passed as literals into the expression.

Add ability to assign values to parameter aliases within $expand, in which case they are evaluated relative to the resource context of the $expand. Also consider adding to $select when considering ODATA-1105.

  was:
Query parameters for $filter segment are always passed in as expressions (because that is the expected type of the parameter).  All other parameters are evaluated in the context in which they are defined and passed as literals, where "Context in which they are defined" is the resource identified by the path segment in which they are defined.

Add ability to nest parameters definitions within $expand, in which case they are relative to the resource context of the $expand. Also consider adding to $select when considering ODATA-1105


> Clarify that 'parameter' aliases can also be used to substitute expressions
> ---------------------------------------------------------------------------
>
>                 Key: ODATA-1109
>                 URL: https://issues.oasis-open.org/browse/ODATA-1109
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: Protocol
>    Affects Versions: V4.01_CSD02
>         Environment: [Proposed]
>            Reporter: Hubert Heijkers
>             Fix For: V4.01_CS01
>
>
> 11.2.6.1.3 Parameter Aliases specifies that "Parameter aliases allow the same value to be used multiple times in a request and may be used to reference primitive values, complex, or collection values" yet in both Example 67 and Example 79 we ourselves show that aliases can also be used to substitute expressions, something which my developers deem is against what's been specified in 11.2.6.1.3, hence the ask for clarification.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)