[OASIS Issue Tracker] (ODATA-961) 10.10 Projected Expanded Entity - be more explicit in combined $select/$expand cases

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

    [ https://issues.oasis-open.org/browse/ODATA-961?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=63161#comment-63161 ] 

Michael Pizzo commented on ODATA-961:
-------------------------------------

Consider: for 4.01, should we include expanded properties in the context url to better describe the payload? This would be useful, for instance, in using the context url to request the subset of required metadata.

If you are able to omit nulls for expanded navigation properties, then we need to include the expanded nav prop in the context url.
(to differentiate null from non expanded)

Obvious syntax would be expand nav property followed by an empty parens (need to add support for this to ABNF).

> 10.10 Projected Expanded Entity - be more explicit in combined $select/$expand cases
> ------------------------------------------------------------------------------------
>
>                 Key: ODATA-961
>                 URL: https://issues.oasis-open.org/browse/ODATA-961
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01, V4.0_ERRATA04
>
>
> 10.9 describes that a navigation property appears twice in the context URL if it is specified in $select as well as in $expand with a nested $select. The text is somewhat vague, but one of the examples 
> 10.10 doesn't repeat that (almost) explicit statement, and also lacks a corresponding example



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)