[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (ODATA-1012) Represent nested deltas as an annotation
[ https://issues.oasis-open.org/browse/ODATA-1012?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-1012: --------------------------------- Fix Version/s: V4.01_WD01 Environment: [Proposed] Proposal: Expose nested deltas as a delta representation on the property, rather than through a context url. Component/s: OData JSON Format > Represent nested deltas as an annotation > ---------------------------------------- > > Key: ODATA-1012 > URL: https://issues.oasis-open.org/browse/ODATA-1012 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: Bug > Components: OData JSON Format > Environment: [Proposed] > Reporter: Michael Pizzo > Fix For: V4.01_WD01 > > > In 4.01 CSD01 we have proposed that a nested collection within a delta payload can be represented either as a replacement of the collection (where omitted values are removed from the collection) or as a delta payload (where only enumerated values are changed, and removed entities are represented as tombstones). > The way we differentiate between these two is, in the case of a nested delta, by annotating the collection property with a context url specifying a delta: > "members@contextUrl":"#$delta", > "members": [ ... ] > Alternatively, we could just use a delta annotation prefixed with the property name, as in: > "members@delta": [ ... ] > Which wouldn't require using the contextUrl annotation to interpret the property. -- 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]