[OASIS Issue Tracker] (OSLCCORE-46) Discovery of services through query rather than LDPC traversal

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

     [ https://issues.oasis-open.org/browse/OSLCCORE-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Amsden updated OSLCCORE-46:
---------------------------------

    Resolution: 
I added the following paragraph at the end of section "5. Discovery Capabilities":

<p>This specification specifies how servers respond to discovery requests through LDPC Link headers or ServiceProviderCatalog and/or ServiceProvider resources. It does not specify how servers organize their LDPCs, how they make distinguished LDPCs known to end users to start the discovery process, or how servers provide efficient access to discovery information that may be distributed over many LDPCs managed by the server. Servers may choose to support the OSLC Query capability on OSLC LDPCs and discovery resources in order to facilitate access to discovery information.</p>

Is this sufficient to close this issue?

> Discovery of services through query rather than LDPC traversal
> --------------------------------------------------------------
>
>                 Key: OSLCCORE-46
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-46
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: New Feature
>            Reporter: David Honey
>            Assignee: James Amsden
>
> The proposed 3.0 discovery requires that clients traverse a hierarchy of LPDCs to find service(s) of interest. Some OSLC 2.0 clients may [erroneously] assume they can discover such services through a single GET of the service provider catalog. When the OSLC client has significant network latency with the OSLC provider, having to iteratively GET LDPCs might lead to slow discovery performance. 



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)