[OASIS Issue Tracker] (ODATA-825) AnnotationPath expression: traversal of multiple collection-valued scalar or navigation properties

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

Martin Zurmuehl updated ODATA-825:
----------------------------------

    Description: 
When applying https://issues.oasis-open.org/browse/ODATA-418 we missed to adapt CSDL 14.5.2. (Specification of edm:AnnotationPath).  restricts path expressions to contain at most one multi-valued navigation property which can only be followed by a single type cast or term cast.

This is overly restrictive: drilling into a complex type path after a navigation is straight-forward, and even multiple multi-valued navigations could be resolved by building the union of all targeted collections.

  was:
CSDL 14.5.12 restricts path expressions to contain at most one multi-valued navigation property which can only be followed by a single type cast or term cast.

This is overly restrictive: drilling into a complex type path after a navigation is straight-forward, and even multiple multi-valued navigations could be resolved by building the union of all targeted collections.


> AnnotationPath expression: traversal of multiple collection-valued scalar or navigation properties
> --------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-825
>                 URL: https://issues.oasis-open.org/browse/ODATA-825
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData CSDL
>    Affects Versions: V4.0_ERRATA02
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             Fix For: V4.0_ERRATA03
>
>
> When applying https://issues.oasis-open.org/browse/ODATA-418 we missed to adapt CSDL 14.5.2. (Specification of edm:AnnotationPath).  restricts path expressions to contain at most one multi-valued navigation property which can only be followed by a single type cast or term cast.
> This is overly restrictive: drilling into a complex type path after a navigation is straight-forward, and even multiple multi-valued navigations could be resolved by building the union of all targeted collections.



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)