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

Martin Pain commented on OSLCCORE-20:
-------------------------------------

My proposal:
We close this ticket with no change to the spec or vocab. That the TCs advice to the team who raised this issue is to use the oslc:serviceProvider predicate to link from the other resource (the project area resource) to the Service Provider.

Additionally, we could document this somewhere else. it might be hard to put into official guidance such as best practices or a primer due to the vendor-specific nature of project areas, in which case a question on the forum or on Stack Overflow or similar, with this solution given as the answer, might be documentation enough in case someone searches for it in future.

> 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
>              Labels: ready-for-vote
>
> 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)