[OASIS Issue Tracker] Updated: (ODATA-400) Allow JSON values also in common expressions, not only in parameter aliases

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

Ralf Handl updated ODATA-400:
-----------------------------

    Environment: [Applied]  (was: [Proposed])
     Resolution: 
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=322
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=322
       Assignee: Ralf Handl

> Allow JSON values also in common expressions, not only in parameter aliases
> ---------------------------------------------------------------------------
>
>                 Key: ODATA-400
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-400
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ABNF Construction Rules, OData URL Conventions 
>    Affects Versions: V4.0_CSD01
>         Environment: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>             Fix For: V4.0_CSD02
>
>
> Currently we allow JSON values (arrays, complex types, entities) only in parameter aliases. This leads to constructions like
> http://host/service/Orders?$filter=$it eq @ref&@ref={"odata.ref":"http://host/service/ZqV5t"}
> The "natural" form without the unnecessary alias
> http://host/service/Orders?$filter=$it eq {"odata.ref":"http://host/service/ZqV5t"}
> is not allowed.

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