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

Martin Pain commented on OSLCCORE-49:
-------------------------------------

What do you mean by a " means for some tool that provisions, deploys and integrates tools to be able to match client needs with server capabilities"? I can't picture it.

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