[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] (OSLCCORE-49) OSLC discovery supports discovering server capabilities, but not client needs
[ https://issues.oasis-open.org/browse/OSLCCORE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Crossley updated OSLCCORE-49: ---------------------------------- Component/s: Core > OSLC discovery supports discovering server capabilities, but not client needs > ----------------------------------------------------------------------------- > > Key: OSLCCORE-49 > URL: https://issues.oasis-open.org/browse/OSLCCORE-49 > Project: OASIS OSLC Lifecycle Integration Core (OSLC Core) TC > Issue Type: Bug > Components: Core > Reporter: James Amsden > Assignee: James Amsden > > Just something to think about. OSLC currently supports discovery of what a server provdes, but there is no way for a client to express what it needs. Therefore there is no means for some tool that provisions, deploys and integrates tools to be able to match client needs with server capabilities. > Possibly a client to use ServiceProvider resources to express the services it needs. -- 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]