[OASIS Issue Tracker] (OSLCCORE-49) OSLC discovery supports discovering server capabilities, but not client needs

[OASIS Issues Tracker <workgroup_mailer@lists.oasis-open.org>]

    [ https://issues.oasis-open.org/browse/OSLCCORE-49?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=61358#comment-61358 ] 

James Amsden commented on OSLCCORE-49:
--------------------------------------

When provisioning a project for development and deployment, a SaaS hosting provider might also offer the ability to provision and integrate development tools. These tools could follow typical patterns supporting the automated creation and consumption of work products governed by some SDLC method targeted at a particular platform architecture.

In order for the hosting provider to properly provision and integrate the tools, it would be helpful if the provisioning tool could discover the capabilities required by one candidate tool in the tool chain, and the capabilities provided by another candidate tool in the tool chain. OSLC discovery supports the latter, but not necessarily the former. 

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