[ODATA-322] Define how nested service documents are supported - OASIS Technical Committees Issue Tracker

XML

Word

Printable

Details

Type: New Feature
Status: Closed
Priority: Major
Resolution: Fixed
Affects Version/s: V4.0_WD01
Fix Version/s: V4.0_WD01
Component/s: ATOM Format, JSON Format, Protocol
Labels:
None
Environment:

[Applied]

Proposal:

Hide

1. In [JSON], add "ServiceDocument" as a new "Kind" to represent a link to a related service document.
2. In [ATOM], add "metadata:service-document" 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]

Approved: https://www.oasis-open.org/committees/download.php/48871/odata-meeting-33_on-20130418-minutes.html#odata-322

Show
1. In [JSON] , add "ServiceDocument" as a new "Kind" to represent a link to a related service document. 2. In [ATOM] , add "metadata:service-document" 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] Approved: https://www.oasis-open.org/committees/download.php/48871/odata-meeting-33_on-20130418-minutes.html#odata-322
Resolution:

Hide

https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=239
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48904/odata-json-format-v4.0-wd01-2013-4-23.docx
https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48905/odata-atom-format-v4.0-wd01-2013-4-23.docx

Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-322

Show
https://tools.oasis-open.org/version-control/browse/wsvn/odata/trunk/spec/schemas/metadata.xsd?rev=239 https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48904/odata-json-format-v4.0-wd01-2013-4-23.docx https://www.oasis-open.org/apps/org/workgroup/odata/download.php/48905/odata-atom-format-v4.0-wd01-2013-4-23.docx Accepted: https://www.oasis-open.org/committees/download.php/49026/odata-meeting-34_on-20130425_26-F2F-minutes.html#odata-322

Description

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.

Attachments

Activity

People

Assignee:

Unassigned

Reporter:

Michael Pizzo (Inactive)

Watchers:

0 Start watching this issue

Dates

Created:

03/Apr/13 4:02 PM

Updated:

01/May/13 8:45 AM

Resolved:

01/May/13 8:45 AM