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-1021) Are additional values needed for the reason property of a removed Annotation


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

Matthew Borges updated ODATA-1021:
----------------------------------

    Proposal: 
Close without fixing.

Reasoning:

- Additional values are unnecessary from the point of view of a client applying a delta response because the net result in both cases is the same.

- Having a different value for the reason for a delta response and a delta upload request is an unnecessary complication that doesn’t add value and prevents easily passing the a delta response as a delta upload request.

- "change" is a very generic term that we did discuss changing to something more meaningful.  However, we were unable to come up with something better.  Further, changing this value could break backwards compatibility between 4.0 and 4.01 so it's best to leave it as is.

> Are additional values needed for the reason property of a removed Annotation
> ----------------------------------------------------------------------------
>
>                 Key: ODATA-1021
>                 URL: https://issues.oasis-open.org/browse/ODATA-1021
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: JSON Format
>    Affects Versions: V4.01_WD01
>            Reporter: Mark Biamonte
>            Assignee: Matthew Borges
>             Fix For: V4.01_CSD02
>
>
> In a nested Delta Payload, a removed annotation can include a reason property that indicates why the item was removed.  Currently the value can be one of deleted or changed.  The changed value can be used in one of two cases
> 1) If a property of the item changed such that the item no longer fits the filter of the delta query 
> 2) The item is no longer linked to the collection being acted on 
> The question came up as to whether an additional value is needed to distinguish between the two cases above.  In the discussion there was concern that not all data sources would be able to distinguish between the to cases.  
> Additionally when the Delta Payload is passed as the body of a PATCH request, only the second case above is valid.  In the discussion the question came up about whether the meaning of reason could be different when used as a request and a response.  The concern there is that it is desirable to be able to pass the Delta Payload received from one service on to a second service



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