[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-20) Service provider should describe domain/scope
[ https://issues.oasis-open.org/browse/OSLCCORE-20?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=60526#comment-60526 ] David Honey commented on OSLCCORE-20: ------------------------------------- We discussed this in the previous core TC meeting and I agreed to write a specific proposal. So here goes... Currently, an oslc:ServiceProvider may use zero or one oslc:details statement. However, the current description is: "A URL that may be used to retrieve a web page to determine additional details about the service provider.". This implies that only HTML media types need be supported. Proposed new description: "A URL of a resource that MUST provide additional information about the service provider. HTML media types MUST be supported. application/rdf+xml MUST be supported. text/turtle SHOULD be supported. The RDF representation of the resource MUST include one dcterms:title statement and one or more rdf:type statements." > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]