[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:comment-tabpanel&focusedCommentId=64925#comment-64925 ] 

Michael Pizzo commented on ODATA-1013:
--------------------------------------

The question here is what to do if the service represents changes to related entities as inline collections. In that case, specifying a nav property in the $select list (but not $expand) presumably includes inline (minimally) the @odata.ids (or key properties) of the current membership.

> 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.



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