[OASIS Issue Tracker] (ODATA-981) ETag Header: Clarify meaning of "individual resource".

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

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

Michael Pizzo updated ODATA-981:
--------------------------------

    Environment: [Proposed]
       Proposal: Clarify that etags MAY be on collections.  If present on the collection, the service MUST support if-match/if-not-match on get, if-match on post; client MUST specify if-match when posting to the collection (i.e., action) (and can use if-match=* to force operation).

> ETag Header: Clarify meaning of "individual resource".
> ------------------------------------------------------
>
>                 Key: ODATA-981
>                 URL: https://issues.oasis-open.org/browse/ODATA-981
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData Protocol
>    Affects Versions: V4.01_WD01
>         Environment: [Proposed]
>            Reporter: Martin Zurmuehl
>             Fix For: V4.01_WD01
>
>
> Chapter 11.5.4.1 "Invoking an Action" reads:
> "...
> To request processing of the action only if the binding parameter value, an entity or collection of entities, is unmodified, the client includes the If-Match header with the latest known ETag value for the entity or collection of entities. The ETag value for a collection as a whole is transported in the ETag header of a collection response.
> ..."
> --> We support ETags for collections via the standart ETag Header. 
> Looking at the chapter 8.3.1 "Header ETag" we never mentioned collections; we described the usage of ETags for metadata responses, service document reponses and for requests that returns an "individual resource".
> The formulation "individual resource" is fuzzy and needs to be clarified.



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