[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Updated: (ODATA-322) Define how nested service documents are supported
[ http://tools.oasis-open.org/issues/browse/ODATA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Pizzo updated ODATA-322: -------------------------------- Proposal: 1. In [JSON], add "ServiceDocument" as a new "Kind" to represent a link to a related service document. 2. In [ATOM], add "metadata:ServiceDocument" element with a required "href" attribute and required <atom:title> child element 3. In [ATOM], define a metadata:metadata attribute that can be present on a <workspace> element to specify the location of the $metadata that describes the service. 4. Describe nested service documents in the appropriate section of [CORE] was: 1. In [JSON], add "ServiceDocument" as a new "Kind" to represent a link to a related service document. 2. In [ATOM], call out that a <collection> element with a <app:accept> value of application/atom+xml;entry (or omitted) represents a collection of entities, while a <collection> with an <app:accept> value of application/atomsvc+xml represents a nested service document. Other content types are not defined in OData and clients should be prepared to ignore them. 3. In [ATOM], define a metadata:metadata attribute that can be present on a <workspace> element to specify the location of the $metadata that describes the service. 4. Describe nested service documents in the appropriate section of [CORE] Agree with Ralf that it is easier to have separate elements for service documents, rather than rely on content type. Updated proposal accordingly. > Define how nested service documents are supported > ------------------------------------------------- > > Key: ODATA-322 > URL: http://tools.oasis-open.org/issues/browse/ODATA-322 > Project: OASIS Open Data Protocol (OData) TC > Issue Type: New Feature > Components: OData ATOM Format , OData JSON Format, OData Protocol > Affects Versions: V4.0_WD01 > Environment: [Proposed] > Reporter: Michael Pizzo > Fix For: V4.0_WD01 > > > Service documents allow a hypermedia-driven client to dynamically explore services. Such clients should be able to navigate across services that may not share the same root metadata or service document. > Supporting nested service documents (service documents referencing other service documents) allows a federated experience including data from multiple loosely-coupled services. > In ATOM service documents clients today model this by exposing a collection whose type is application/atomsvc+xml. We should call out that usage explicitly, and support a similar "ServiceDocument" entry in JSON service documents. -- 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]