[OASIS Issue Tracker] Commented: (ODATA-307) Return odata.etag in collections also for odata=minimalmetadata

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

Michael Pizzo commented on ODATA-307:
-------------------------------------

Propose instead defining a default convention for constructing the etag as a comma separated list of concurrency values.

Services must return the etag if they don't follow this convention.

> Return odata.etag in collections also for odata=minimalmetadata
> ---------------------------------------------------------------
>
>                 Key: ODATA-307
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-307
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Bug
>          Components: OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> For single entity responses the ETag is contained in the ETag response header.
> For multi-entity responses the header is not sufficient, instead clients need to receive the ETag in the entity metadata, i.e. the odata.etag annotation.
> We do have a Core annotation that tells clients which entity properties influence the ETag, but we currently have no way of telling the client which algorithm the server uses to calculate the ETag.

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