[OASIS Issue Tracker] (ODATA-685) Prepare clients in 4.0 to deal with nav property binding on containmnet

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

    [ https://tools.oasis-open.org/issues/browse/ODATA-685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=37836#comment-37836 ] 

Michael Pizzo commented on ODATA-685:
-------------------------------------

I realized, after apply this change, that in making this change we both made the definition of navpropbindings on containment properties harder than we needed to and violated the design principle of not having schema elements outside the entity container reference elements defined inside the entity container.

Instead of nesting a NavigationPropertyBinding under a containment NavigationProperty element, we should simply allow the path of the NavigationPropertyBinding nested under an entity set to traverse one or more containment navigation properties. This would be a reasonable reading of the current text, and we could simply spell it out rather than add the navigation property binding to the navigation property element.

In fact, I think that was the original intention when doing the navigation property binding, we just lost it along the way.

> Prepare clients in 4.0 to deal with nav property binding on containmnet
> -----------------------------------------------------------------------
>
>                 Key: ODATA-685
>                 URL: https://tools.oasis-open.org/issues/browse/ODATA-685
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Sub-task
>          Components: OData CSDL
>    Affects Versions: V4.0_OS
>         Environment: [Applied]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.0_ERRATA01
>
>
> OData V4 has a hole in that we never defined how navigation property bindings related to containment. OData-674 seeks to address that issue as a natural extension to current behavior, but because it couldn't be considered a non-material change we were unable to add it to 4.0.
> However, understanding how this will be addressed in the future, it would be nice to give direction to clients today such that they can anticipate the change and not break when services add support for navigation property bindings to contained nav props, and allow referencing contained sets as the target of a navpropbinding.



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