Next in thread → Next in month →

[OASIS Issue Tracker] (ODATA-839) A recursive hierarchy annotation may also contain a navigation property to the children nodes

From
OASIS Issues Tracker <>
Date
2015-09-17T07:31:55+00:00
ID
Thread
[OASIS Issue Tracker] (ODATA-839) A recursive hierarchy annotation may also contain a navigation property to the children nodes
[ https://issues.oasis-open.org/browse/ODATA-839?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-839:
-----------------------------

        Fix Version/s: V4.0_CSD04
                           (was: V4.0_CSD03)
    Affects Version/s: V4.0_CSD03
                           (was: V4.0_CS01)

> A recursive hierarchy annotation may also contain a navigation property to the children nodes
> ---------------------------------------------------------------------------------------------
>
>                 Key: ODATA-839
>                 URL: https://issues.oasis-open.org/browse/ODATA-839
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Extension for Data Aggregation
>    Affects Versions: V4.0_CSD03
>         Environment: [Proposed]
>            Reporter: Gerald Krause
>             Fix For: V4.0_CSD04
>
>
> Consider a client processing entities according to their hierarchical structure imposed by the given hierarchy annotation.
> If the client wants to retrieve the descendants for the next three levels, this could be accomplished with a single request that makes use of a (cyclic) navigation property pointing to the children of a node. Assuming this navigation property has name childrenNodes, and the corresponding navigation property annotated as ParentNavigationProperty has name parentNode, the request would be:
>  GET set(nodeId)?$expand=childrenNodes($levels=3;$select=parentNode/nodeId,nodeId) 
> In order to let clients detect the availability of such navigations, the existing RecursiveHierarchy term needs to be Extended as proposed. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)
Next in thread → Next in month →