[OASIS Issue Tracker] Updated: (ODATA-319) Allow services to include metadata links and metadata ETags into responses

From
OASIS Issues Tracker <>
Date
2013-04-22T17:19:55+00:00
ID
827348157.2701366651183844.JavaMail.tomcat55@mw00
Thread
[OASIS Issue Tracker] Updated: (ODATA-319) Allow services to include metadata links and metadata ETags into responses
[ http://tools.oasis-open.org/issues/browse/ODATA-319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Ralf Handl updated ODATA-319:
-----------------------------

    Resolution: https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=239

> Allow services to include metadata links and metadata ETags into responses
> --------------------------------------------------------------------------
>
>                 Key: ODATA-319
>                 URL: http://tools.oasis-open.org/issues/browse/ODATA-319
>             Project: OASIS Open Data Protocol (OData) TC
>          Issue Type: Improvement
>          Components: OData ATOM Format , OData JSON Format
>    Affects Versions: V4.0_WD01
>         Environment: [Proposed]
>            Reporter: Ralf Handl
>             Fix For: V4.0_WD01
>
>
> As we defined a list of compatible changes to the data model of a service, it would be useful to notify clients that the metadata has changed, so they can re-read $metadata.
> As the new JSON format in two of its flavors already includes the metadata link, we could just add a metadata etag that clients can compare to the etag of the cached version of $metadata.
> While we are at it, we can add a metadata link to Atom responses.

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