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

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

We can distinguish a resource, from its various representations, and from a description of the resource. HTTP accesses and updates representations of the resource identified by a URL. Content negotiation allows the client to indicate the preferred representation.

A description of a resource is really another resource, at a different meta-level. Descriptions often use a different vocabulary than the resource itself, utilizing some standard descriptive language like RDFS or OWL. To me these are different, but related resources, each of which can have multiple representations. It may be best to clearly separate the representations of a resource from representations of its description as these are generally used for very different things in reflective tools.

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