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

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

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

Michael Pizzo updated ODATA-307:
--------------------------------

    Environment: [Applied]  (was: [Proposed])
       Assignee: Michael Pizzo

> 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: [Applied]
>            Reporter: Ralf Handl
>            Assignee: Michael Pizzo
>             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