No argument as far as OData goes. I thought it might be interesting to explore the UML model.
George
From: Handl, Ralf <ralf.handl@sap.com>
Sent: Tuesday, May 9, 2023 10:39 AM
To: Ericson, George <George.Ericson@dell.com>; OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>; odata@lists.oasis-open.org
Subject: RE: [odata] [OASIS Issue Tracker] (ODATA-1575) Remove restriction on Partner navigation
[EXTERNAL EMAIL]
There are no name collisions because OData v4 only has unidirectional ânavigation propertiesâ, not ânamed associations with named rolesâ:
Partner just means âyou can get back here if you followâ
From:
odata@lists.oasis-open.org <odata@lists.oasis-open.org>
On Behalf Of Ericson, George
Sent: Tuesday, 9 May 2023 15:45
To: OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>;
odata@lists.oasis-open.org
Subject: RE: [odata] [OASIS Issue Tracker] (ODATA-1575) Remove restriction on Partner navigation
I drew this to understand:
In this, to avoid name collisions, two of the partners named foo must belong to the associations, A_foo_redBar, and A_foo_greenBar.
Thanks,
George
-----Original Message-----
From: odata@lists.oasis-open.org <odata@lists.oasis-open.org> On Behalf Of OASIS Issues Tracker
Sent: Tuesday, May 9, 2023 9:12 AM
To: odata@lists.oasis-open.org
Subject: [odata] [OASIS Issue Tracker] (ODATA-1575) Remove restriction on Partner navigation
[EXTERNAL EMAIL]
Ralf Handl created ODATA-1575:
---------------------------------
Summary: Remove restriction on Partner navigation
Key: ODATA-1575
URL:
https://urldefense.com/v3/__https://issues.oasis-open.org/browse/ODATA-1575__;!!LpKI!gpKuv_zow2n7L-N606JqD9iM07q4mD81ChIfhTGk3g_AtixVzNCzEQYt6ZNtLIW_L8p7UF2nRhBg3xCZMAGwdBz53LB4CYlUvDVm2A$ [issues[.]oasis-open[.]org]
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://urldefense.com/v3/__https://docs.oasis-open.org/odata/odata-csdl-xml/v4.01/odata-csdl-xml-v4.01.html*sec_PartnerNavigationProperty__;Iw!!LpKI!gpKuv_zow2n7L-N606JqD9iM07q4mD81ChIfhTGk3g_AtixVzNCzEQYt6ZNtLIW_L8p7UF2nRhBg3xCZMAGwdBz53LB4CYnaZzUK5g$
[docs[.]oasis-open[.]org]] 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)
---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail. Follow this link to all your TCs in OASIS at: