[OASIS Issue Tracker] (ODATA-1013) Selected nav props in a defining query should specify interest in added/deleted links of a delta query

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

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

Michael Pizzo updated ODATA-1013:
---------------------------------

    Proposal: 
Nav properties specified in the select list of a defining query are not used to define the scope or contents of the items being tracked. Clients can specify /$ref in $expand in order to specify interest in the set of related entities without interest in changes to the content of those related entities.

Delta responses contain AddedLinks and DeletedLinks entries (or, for nested collections, (at least) entity references representing the current membership) for navigation properties expanded with $ref in the defining request.

  was:
Nav properties specified in the select list of a defining query define the links for which the client is interested in receiving notifications.

Delta responses contain AddedLinks and DeletedLinks entries for navigation properties specified in the select list of the defining request.


> Selected nav props in a defining query should specify interest in added/deleted links of a delta query
> ------------------------------------------------------------------------------------------------------
>
>                 Key: ODATA-1013
>                 URL: https://issues.oasis-open.org/browse/ODATA-1013
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData Protocol
>    Affects Versions: V4.0_ERRATA03
>         Environment: [Proposed]
>            Reporter: Michael Pizzo
>            Assignee: Michael Pizzo
>             Fix For: V4.01_CSD02
>
>
> Today we say that expanded properties in the defining query define the scope of the graph for which the client is interested in receiving changes.
> It could be that the client is interested in knowing about added/deleted links, but doesn't care about the contents of the entities related through those links.
> This could easily by supported by saying that navigation properties in the select list define the links that the client is interested in knowing about changes for. If the service represents deltas to related entities through an inline collection, that inline collection would contain (minimally) the entity references (or key properties of entities) representing the current membership.



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