[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:comment-tabpanel&focusedCommentId=61270#comment-61270 ] 

David Honey commented on OSLCCORE-46:
-------------------------------------

An alternative suggested by Jim was to support a Prefer header on the GET of the SPC for it to return the service providers inlined. This would require a new header value. While this approach appears simple, there are some issues:
1) If a client knows what it wants, it has to ask for everything to be inline and returned.
2) If a client wants something more selective , we end up having to invent other Prefer header values.

In order for OSLC clients to be able to use a query based discovery, recommending that OSLC 3.0 servers implement a query capability for resources of type oslc:ServiceProvider and oslc:Service explicitly in the spec would draw attention to this. I see common use cases might include:

1) What creation dialogs are available to create a resource of a specified type?
2) What are the resource shapes exposed across services?
3) What query capabilities are available for a specified resource type?

> 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)