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-1010) Represent deleted entities similar to added/changed entities


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

Ralf Handl commented on ODATA-1010:
-----------------------------------

Feedback from implementation team: 
- combine "removed" and "reason" into one annotation
- do not use a special context URL for entities annotated as "deleted"
- place custom annotations directly within the deleted entity:

    { 
      "@odata.id":"Customers('ANTON')", 
      "@odata.removed":"deleted",                        /* and "@odata.removed":"changed" */
      "@myannotation.user":"Mario", 
      "@myannotation.justification":"he didn't pay his bill", 
      /* optionally properties of the deleted entity */ 
      "CustomerID": "ANTON", 
      ... 
    } 

This also reserves context URLs with the suffix /$deletedEntity for V4-style "tombstones".

> Represent deleted entities similar to added/changed entities
> ------------------------------------------------------------
>
>                 Key: ODATA-1010
>                 URL: https://issues.oasis-open.org/browse/ODATA-1010
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: New Feature
>    Affects Versions: V4.01_WD01
>            Reporter: Ralf Handl
>             Fix For: V4.01_CSD02, V4.01_WD01
>
>
> Allow representing deleted entities similar to added/changed entities
>     {
>       "@odata.context":"#Orders/$entity",
>       "@odata.id":"Orders(10643)",
>       "ShippingAddress":{
>         "Street":"23 Tsawassen Blvd.",
>         "City":"Tsawassen",
>         "Region":"BC",
>         "PostalCode":"T2F 8M4"
>       },
>     },
>     {
>       "@odata.context":"#Customers/$entityDeletion",
>       "@odata.id":"Customers('ANTON')",
>       "@odata.reason":"deleted",
>       /* optionally properties of the deleted entity */
>      "CustomerID": "ANTON",
>      ...
>     }
> This would allow using the same serialization template. And it looks more consistent :-)



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