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-1127) clarify support for navigation properties on deleted entries

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

Matthew Borges commented on ODATA-1127:

It's not clear to me why this is needed.  If the related entity is no longer reachable by any entity identified by the defining query, then it is supposed to be removed from the client (or at least the client is supposed to be told it will not get further notifications about that entity).  If the related entity is still reachable by some other path in the graph, I would expect information about any changes to the related entity to come else where in the delta payload.

> clarify support for navigation properties on deleted entries
> ------------------------------------------------------------
>                 Key: ODATA-1127
>                 URL: https://issues.oasis-open.org/browse/ODATA-1127
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: JSON Format, Protocol
>    Affects Versions: V4.01_CS02
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>             Fix For: V4.01_CS02, V4.01_CS01
> In 4.01 we added support for properties within a deleted entry.  This allows us to omit the @odata.id, if key fields are included, and may provide other information about the deleted entry.
> We are not clear, however, whether "properties" includes navigation properties and what the semantics of navigation properties on a deleted entry should be.
> If you think of a delta payload as a graph of changes, the fact that a node within that graph has been deleted doesn't mean that you aren't interested in changes to other nodes within the graph; it's still interesting to report changes to nodes that may no longer be accessible (at least from the root) after applying changes.

This message was sent by Atlassian JIRA

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