[OASIS Issue Tracker] Commented: (ODATA-345) Specify which nested query options can be used when expanding only references, and adapt syntax

[ http://tools.oasis-open.org/issues/browse/ODATA-345?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33051#action_33051 ] 

Michael Pizzo commented on ODATA-345:
-------------------------------------

I don't understand the issue with the current syntax NavProp(<nested options>)/$ref.

$ref just means "return entity references in place of the entities". Like a cast operator. Some of the nested options ($filter in particular) are meaningful (I only want references for related entities that match a particular criteria). Some of the nested options aren't meaningful and may be optimized out ($expand, $select) but that's okay; they are well defined, just not useful if followed by a /$ref. 

> Specify which nested query options can be used when expanding only references, and adapt syntax
> -----------------------------------------------------------------------------------------------
>
>                 Key: ODATA-345
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-345
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData ABNF Construction Rules, OData Protocol , OData URL Conventions 
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> $expand allows nesting query options after the name of the navigation properties to be expanded.
> When expanding only references $select, $expand, and $levels don't make sense as neither structural nor navigation properties are represented in references.

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