[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=60699#comment-60699 ] David Honey commented on OSLCCORE-20: ------------------------------------- The problem with Martin's counter proposal is that it requires that the user can GET the RDF of a project area to find its service provider(s), or that the OSLC client knows how to query for that data in an indexer such as LQE that indexes all project areas. > 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)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]