[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=60532#comment-60532 ] 

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

How would this link from an known project area URL to a service provider? Wouldn't the RDF representation have to include the project area URI, an oslc:describes property with the URL of the resource the service provider describes?

If the project area is an LDPC, wouldn't it be easier to simply do an OPTIONS request on the project area URL and get the Link headers for discovery directly?

Is this proposal appropriate for OSLC2, not OSLC3?


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