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

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ http://tools.oasis-open.org/issues/browse/ODATA-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=33069#action_33069 ] 

Ralf Handl commented on ODATA-322:
----------------------------------

Can we use metadata:service-document to be consistent with metadata:function-import?
Or jiust metadata:service similar to app:service?

> 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