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

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

Yes, hence resolving this issue depends on resolving whether SPCs are LDPCs or not. 

However, even if OSLC2 discovery resources are not LDPCs, an OSLC3 Project Area could be an LDPC would would provide discovery information through the link header. So a client client would be able to do discovery without having to read SPCs at all. So this issue might be resolved by OSLC3 in any case.


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