[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [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 ] Michael Pizzo updated ODATA-319: -------------------------------- Proposal: Allow services to annotate the odata.metadata annotation with the odata.etag annotation to transport the current ETag of $metadata to clients: { "odata.metadata": "http://host/service/$metadata", "odata.metadata@odata.etag": "A1FF3E230954908F", ... } Allow services to return etag in metadata request and add a metadata link that MAY contain a metadata:etag attribute to Atom responses: <link rel="http://docs.oasis-open.org/odata/ns/metadata" metadata:etag="A1FF3E230954908F" href="http://host/service/$metadata" /> metadata is same as odata.metadata annotation in json. was: Allow services to annotate the odata.metadata annotation with the odata.etag annotation to transport the current ETag of $metadata to clients: { "odata.metadata": "http://host/service/$metadata", "odata.metadata@odata.etag": "A1FF3E230954908F", ... } Allow services to add a metadata link that MAY contain a metadata:etag attribute to Atom responses: <link rel="http://docs.oasis-open.org/odata/ns/metadata" metadata:etag="A1FF3E230954908F" href="http://host/service/$metadata" /> > 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]