[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:comment-tabpanel&focusedCommentId=67317#comment-67317 ] 

Ramesh Reddy commented on ODATA-1109:
-------------------------------------

Unless we are trying to implement support for dynamic expressions I am not sure I understand the need for this feature. If it simply replaces like

{code}
$filter=Name eq @x&@x=concat('Jo','e')
is same as 
$filter=Name eq concat('Jo','e')
{code}

What is the need for the simplification? Typically IMO the parameters are used when you want to box in some functionality where others are supplying the values for those parameters. If the intention is dynamic querying then, this brings additional parsing/validation burdens in implementations, which may be cumbersome but doable.

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