[OASIS Issue Tracker] (OSLCCORE-20) Service provider should describe domain/scope

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

    [ https://issues.oasis-open.org/browse/OSLCCORE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60502#comment-60502 ] 

James Amsden commented on OSLCCORE-20:
--------------------------------------

Discussion: For OSLC3, this is not an issue since a resource that supports discovery would be an LDPC. Clients can use an OPTIONS or HEAD request directly on the LDPC to get discovery information from the link headers. There's no need to locate the Service Provider resource (or the LDPC is the Service Provider). Or the LDPC may be the ServiceProvider resource itself.

Recommendation: Since this is not currently provided in OSLC2, and is already supported in OSLC3 using LDPC discovery, this issue should be considered closed as already supported. It is not clear there is a need to retrofit the capability back into the OSLC2 Service Provider resource too. Just use the new OSLC3 feature to realize the requirement.

> Service provider should describe domain/scope
> ---------------------------------------------
>
>                 Key: OSLCCORE-20
>                 URL: https://issues.oasis-open.org/browse/OSLCCORE-20
>             Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC
>          Issue Type: Improvement
>            Reporter: David Honey
>            Assignee: James Amsden
>
> OSLC 2.0 supports a service declaring a domain or scope using oslc:domain and oslc:usage. Jazz applications frequently declare a service provider for each project area. However, there is no standard way for a client to determine which service provider to use for a known project area.



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