[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1104) Make "@" optional for parameters
[ https://issues.oasis-open.org/browse/ODATA-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=67177#comment-67177 ] Ralf Handl commented on ODATA-1104: ----------------------------------- I would restrict this to implicit parameter aliases introduced with ODATA-763, see Part 1: Protocol, section 11.5.3.1.1 Inline Parameter Syntax - http://docs.oasis-open.org/odata/odata/v4.01/csprd02/part1-protocol/odata-v4.01-csprd02-part1-protocol.html#sec_InlineParameterSyntax GET http://host/service/EmployeesByManager?ManagerID=3 Explicitly introduced parameter aliases should still require an @ in the path part as well as in the query part: GET http://host/service/EmployeesByManager(ManagerID=@p1)?@p1=3 > Make "@" optional for parameters > -------------------------------- > > Key: ODATA-1104 > URL: https://issues.oasis-open.org/browse/ODATA-1104 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: URL Conventions > Affects Versions: V4.01_CSD02 > Reporter: Michael Pizzo > Fix For: V4.01_CS01 > > > Similar to making the $ optional for system query options, make the "@" optional for query options representing parameters. Define precedence rules for resolving potential ambiguity. -- 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]