OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

odata message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: [OASIS Issue Tracker] Created: (ODATA-322) Define how nested service documents are supported

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 Extension for JSON Data , OData Protocol 
         Environment: [Proposed]
            Reporter: Michael Pizzo

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]