[OASIS Issue Tracker] (ODATA-613) Allow PATCH to entity sets using the delta-response format

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

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

Michael Pizzo commented on ODATA-613:
-------------------------------------

In GET, the $expand specifies the extent of the graph, and any changes/added/deleted links or tombstones are valid for any members of that graph.

For PATCH,  you don't specify a $expand so the extent of that graph is undefined.  Therefore, it is presumably valid to have added/deleted links to anything reachable from the target.

> Allow PATCH to entity sets using the delta-response format
> ----------------------------------------------------------
>
>                 Key: ODATA-613
>                 URL: https://issues.oasis-open.org/browse/ODATA-613
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData JSON Format, OData Protocol
>    Affects Versions: V4.0_OS
>         Environment: Set Operations, [Proposed]
>            Reporter: Ralf Handl
>            Assignee: Ralf Handl
>              Labels: Usability
>             Fix For: V4.01_WD01
>
>
> This will allow easy synchronization between services with same model
> Previous proposal (for sanity check):
> Document changes:
> part1-protocol
> Add section: 11.4.10 Update an Entity Set
> To update a collection, the client sends a PATCH request to that collection's URL. The PATCH body MUST contain a valid delta response consisting of appropriate representations for 
> If the target URL for the collection is a navigation link, any added entity is automatically linked to the entity containing the navigation link, and any deleted entity is automatically unlinked.



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