OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: [OASIS Issue Tracker] (ODATA-996) Added/deleted links: "relationship" should be navigation property path


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

Michael Pizzo updated ODATA-996:
--------------------------------

    Proposal: 
Use
* relationship – The path to the navigation property on the source object

instead of
* relationship – The name of the navigation property on the source object

For ordered collection-valued complex properties use nested representation.


  was:
Use
* relationship – The path to the navigation property on the source object

instead of
* relationship – The name of the navigation property on the source object

For ordered collection-valued complex properties the path contains the index of the complex instance.

Unordered collection-valued complex properties are only supported with V4.01, using nested representation and @odata.navigationLink annotations.



> Added/deleted links: "relationship" should be navigation property path
> ----------------------------------------------------------------------
>
>                 Key: ODATA-996
>                 URL: https://issues.oasis-open.org/browse/ODATA-996
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_ERRATA03
>            Reporter: Ralf Handl
>             Fix For: V4.01_WD01, V4.0_ERRATA04
>
>
> Sections 14.3 and 14.4 define the format for added/deleted links and state that the property "relationship" contains the name of the navigation property that is changed.
> The name alone isn't sufficient for navigation properties nested within complex properties, "relationship" should instead contain the path to the navigation property.
> Collection-valued complex properties with nested navigation properties need special attention.
> Maybe restrict change tracking to ordered collections of complex instances with nested navigation properties, or require "nested delta" format for these in V4.01



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


[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]