[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-763) Allowing implicit aliasing of parameters (public comment c201412e00001)
[ https://issues.oasis-open.org/browse/ODATA-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60657#comment-60657 ]
Gerald Krause commented on ODATA-763:
-------------------------------------
What if a request includes invocations of multiple functions that have formal parameters with identical names ? For example, if fct1(a,b) returns a collection and fct2(a,c) operates on such a collection, the shortened request would be GET ~/fct1()/fct2()?a=...&b=...&c=... The reference to parameter "a" is ambiguous in this case.
> 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: [Proposed]
> Reporter: Ralf Handl
> Assignee: Ralf Handl
> 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]