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-1013) Selected nav props in a defining query should specify interest in added/deleted links of a delta query


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

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

Updated proposal based on discussion 2017-1-19. Mike to check whether or not this still addresses scenario that caused issue to be open initially.  Semantics of revised proposal are much better aligned, but possible concern is use of $expand=nav/$ref is a bit more esoteric, where use of a nav prop in a select list is very straight-forward.

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


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