[OASIS Issue Tracker] Commented: (ODATA-206) Rephrasing of section Delta Links in ODQP proposal page 1/2

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

    [ http://tools.oasis-open.org/issues/browse/ODATA-206?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32114#action_32114 ] 

Michael Pizzo commented on ODATA-206:
-------------------------------------

Applied slightly edited version:

For any request for which the OData Service can enumerate changes the service SHOULD support result maintenance*, if requested,* by including a "delta link" url in place of the next link on the last page of results returned. 

A response MAY contain *a next page link, a delta link, or neither,* but MUST NOT contain both. 

Clients can use this delta link to query the service for changes that have occurred to the result since the initial request. 

Delta links MUST only be returned upon requests whose responses contain a collection of zero or more entities. Requests for individual entities or property values MUST NOT include delta links. Corresponding examples for such requests are ~/Customers('ALFKI') and ~/Customers('ALFKI')/ContactName respectively.


> Rephrasing of section Delta Links in ODQP proposal page 1/2
> -----------------------------------------------------------
>
>                 Key: ODATA-206
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-206
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>    Affects Versions: WD01
>            Reporter: Stefan Drees
>            Assignee: Michael Pizzo
>            Priority: Minor
>             Fix For: WD01
>
>
> Inside the current revision of the proposal for an OData Delta Query Protocol i.e. [OData Delta Query Protocol Design 2012-12-19.docx](https://www.oasis-open.org/committees/download.php/47755/OData%20Delta%20Query%20Protocol%20Design%202012-12-19.docx) please consider rewriting:
> """
> Delta Links
> An OData Service supports result maintenance by including a "delta link" url in the last page of results returned from a request for which the service can enumerate changes. This delta link is generated in place of the next link on the last page of the result. It is illegal for a response to contain both a delta link and a next page link.
> Clients can use this delta link to query the service for changes that have occurred to the result since the initial request.
> Delta links are returned only on requests that return a collection of zero or more entities. Requests for individual entities (for example ~/Customers('ALFKI') or property values (for example, ~/Customers('ALFKI')/ContactName) do not include delta links."""
> into:
> """
> Delta Links
> For any request for which the OData Service can enumerate changes the service SHOULD support result maintenance by including a "delta link" url in place of the next link on the last page of results returned.
> A response MAY contain a next page or a delta link, but MUST NOT contain both.
> Clients can use this delta link to query the service for changes that have occurred to the result since the initial request.
> Delta links MUST only be returned upon requests whose responses contain a collection of zero or more entities. Requests for individual entities or property values MUST NOT include delta links. Corresponding examples for such requests are  ~/Customers('ALFKI') and ~/Customers('ALFKI')/ContactName respectively.""" 
> to ease understanding of main statements and extraction of conformance tests.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira