[OASIS Issue Tracker] Commented: (ODATA-36) Make $expand implicit if navigation properties are mentioned in $select or $aggregate

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

Ralf Handl commented on ODATA-36:
---------------------------------

I was referring to the other comment extending $filter:

GET ~/PurchaseOrders?$filter=Status eq 'OPEN',Items(WeightInKg gt 5000),Items/ScheduleLines(not Shipped) 

Or in ABNF:

filter = "$filter=" filterExpression *(COMMA filterExpression)
filterExpression = boolCommonExpr / navigationPath "(" boolCommonExpr ")"

That way all filtering is done via $filter and not partially mixed into $expand.

> Make $expand implicit if navigation properties are mentioned in $select or $aggregate
> -------------------------------------------------------------------------------------
>
>                 Key: ODATA-36
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-36
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol v1.0, OData URL Conventions v1.0
>    Affects Versions: WD01
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>            Priority: Minor
>             Fix For: WD01
>
>
> Currently clients need to repeat themselves when projecting on expanded entities:
> GET http://services.odata.org/OData/OData.svc/Products?$select=*,Category/Name&$expand=Category
> This could be reduced to 
> GET http://services.odata.org/OData/OData.svc/Products?$select=*,Category/Name
> because the client explicitly requests Category/Name, and the server can only satisfy that if it expands the Category.

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