[ https://issues.oasis-open.org/browse/ODATA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61218#comment-61218 ]
Michael Pizzo commented on ODATA-763:
-------------------------------------
Yes; there are a variety of issues with trying to do this in the general case, which is why we moved away from it in OData V4.
A common case, though, is that you are invoking a function as the last segment in a request. If we supported the pattern for only that case, as an alternate to filing in the details, then we might get most of the benefit without introducing a lot of more difficult rules.
The services would continue to support the parens-syntax so that generic clients could generate common URL patterns, this would just provide a way that services could advertise a "friendlier" url pattern for a simple scenario.
> Allowing implicit aliasing of parameters (public comment c201412e00001)
> -----------------------------------------------------------------------
>
> Key: ODATA-763
> URL: https://issues.oasis-open.org/browse/ODATA-763
> Project: OASIS Open Data Protocol (OData) TC
> Issue Type: New Feature
> Components: OData URL Conventions
> Affects Versions: V4.0_ERRATA02
> Environment: Simplified Syntax
> Reporter: Ralf Handl
> Assignee: Michael Pizzo
> Labels: Usability
> Fix For: V4.01_WD01
>
>
> The public comment [c201412e00001] (https://lists.oasis-open.org/archives/odata-comment/201412/msg00001.html) with title "Parameter implicit aliasing" suggests to add a short-hand notation for parameter aliases, e.g.
> GET http://<serviceroot>/Add()?a=1&b=1
> instead of the currently necessary
> GET http://<serviceroot>/Add(a=@a,b=@b)?@a=1&@b=1.
--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
