[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:all-tabpanel ]

Michael Pizzo updated ODATA-961:
--------------------------------

    Proposal: 
Clarify text of 10.9 -- 
if nav prop is in select, appears without parens. 
if nav prop is in expand with no select, expand, or recursion MAY NOT appear in the context url for 4.0, MUST appear for 4.01 (with empty parens if no nested select).
If nav prop is in expand with recursion, it's followed by a +
If nav prop is in expand with select list (or expand with select) then it's followed by parens (following the +, if present)
If both, both appear

Make sure 10.10 is consistent with clarified wording from 10.9.

  was:
Clarify text of 10.9 -- if nav prop is in select, appears without parens. If nav prop is in expand, appears with parens. If both, both. Parens contain any nested select/expand, or is empty if no nested select/expand. Remove "Additionally" in description of recursion.

Make sure 10.10 is consistent with clarified wording from 10.9.


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