[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (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:all-tabpanel ]
Ralf Handl updated ODATA-576:
-----------------------------
Resolution:
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-abnf.txt?rev=541
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/ABNF/odata-aggregation-testcases.xml?rev=541
> 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]