OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


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


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

Ralf Handl commented on ODATA-576:
----------------------------------

As the other set transformations use positional parameter syntax, I propose to change this to 

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

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

I.e. the first parameter of expand() is a navigation property path that could also be used in $expand, the optional parameter second parameter can be a filter() transformation or an expand() transformation, the other optional parameters can be expand() transformations:

expandTrafo = 'expand' OPEN BWS expandPath [ BWS COMMA BWS filterTrafo ] *( BWS COMMA BWS expandTrafo ) BWS CLOSE

> 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

        


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]