Ralf Handl created ODATA-1575: --------------------------------- Summary: Remove restriction on Partner navigation Key: ODATA-1575 URL:
https://issues.oasis-open.org/browse/ODATA-1575 Project: OASIS Open Data Protocol (OData) TC Issue Type: Improvement Components: CSDL JSON , CSDL XML Affects Versions: V4.01_OS Reporter: Ralf Handl Fix For: V4.02_WD01 CSDL section [8.3 Partner Navigation Property
https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html#sec_PartnerNavigationProperty ] requires that {quote} If a partner navigation property is specified, this partner navigation property MUST either specify the current navigation property as its partner to define a bi-directional relationship or it MUST NOT specify a partner navigation property. The latter can occur if the partner navigation property is defined on a complex type, or if the current navigation property is defined on a type derived from the type of the partner navigation property. {quote} This restriction is harmful in the following situation * Foo ** allBar Type=Collection(Bar) Partner=foo ** redBar Type=Collection(Bar) Partner=foo ** greenBar Type=Collection(Bar) Partner=foo * Bar ** foo Type=Foo Partner=allBar These partner navigation properties satisfy the basic rules {quote} If the partner navigation property is single-valued, it MUST lead back to the source entity from all related entities. If the partner navigation property is collection-valued, the source entity MUST be part of that collection. {quote} -- This message was sent by Atlassian Jira (v8.3.3#803004)