[OASIS Issue Tracker] Updated: (ODATA-528) $entity should require cast segment in order to apply $select/$expand

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

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

Stefan Drees updated ODATA-528:
-------------------------------

    Resolution: 
https://www.oasis-open.org/committees/download.php/50850/odata-v4.0-wd04-part1-protocol-2013-09-27.docx

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=477
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=477

Applied: https://www.oasis-open.org/committees/download.php/50877/odata-meeting-54_on-20131001-minutes.html#ga_01

  was:
https://www.oasis-open.org/committees/download.php/50850/odata-v4.0-wd04-part1-protocol-2013-09-27.docx

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-construction-rules.txt?rev=477
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-abnf-testcases.xml?rev=477


> $entity should require cast segment in order to apply $select/$expand
> ---------------------------------------------------------------------
>
>                 Key: ODATA-528
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-528
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData Protocol 
>    Affects Versions: V4.0_CS01
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_CSD03
>
>
> Given an opaque id for an entity, the client can get the instance using the new /$entity resource and providing the id through the $id query option, such as:
> http://host.service/$entity?$id=urn:mysvc5304-98001-7832-4425
> This can be cast to a particular type:
> http://host.service/$entity/myservice.Customer?$id=urn:mysvc5304-98001-7832-4425
> And any of the query options supported for a single resource can be applied:
> http://host.service/$entity/myservice.Customer?$id=urn:mysvc5304-98001-7832-4425?$select=LastName&$expand=Orders
> However the text current does no require the cast in order to apply $select and $expand. This is a bug, because without the cast a parser cannot determine whether the $select and $expand are valid without actually retrieving the object and discovering its type.
> Everywhere else we consistently require casting to the correct type in order to access members of that type.
> Also, I think there is a bug in the ABNF as it doesn't appear to allow for the cast segment:
> '$entity' "?" entityOptions  

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