[OASIS Issue Tracker] Updated: (ODATA-576) Aggregation: Can we find a better way to represent nested expands?

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

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

Michael Pizzo updated ODATA-576:
--------------------------------


Having special purpose parameters for filter and expand seems less intuitive to read (I have to remember what the parameters represent), brittle (I have to pass a "true" for the second parameter if I don't want to apply a filter) and limited (what happens if I want to apply other expand options in the future?

Also, it's confusing having different construction rules from $expand.

Why not use the same construction rules as $expand, but with a limited set of expand options; expand and filter?

This would also allow us to have a single expand take a list of navigation properties, rather than requiring multiple expand segments.

So in the examples above would look like:

    GET ~/Categories?$apply=expand(Products(filter=startswith(Name,'Ski');expand=Sales,Amount gt 1000))). 

    GET ~/Categories?$apply=expand(Products(expand=Sales)) 



> Aggregation: Can we find a better way to represent nested expands?
> ------------------------------------------------------------------
>
>                 Key: ODATA-576
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-576
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation 
>    Affects Versions: V4.0_CSD01
>         Environment: [Proposed][Applied]
>            Reporter: Michael Pizzo
>             Fix For: V4.0_CSD02
>
>
> The current aggregation specification use the old path syntax for nested expands. This is inconsistent with the new way to represent expands in core. Can we figure out a syntax for nested expands in aggregation that is consistent with core?

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