[OASIS Issue Tracker] Updated: (TOSCA-51) Define core set of Requirement and Capability Types

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

     [ http://tools.oasis-open.org/issues/browse/TOSCA-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Paul Lipton  updated TOSCA-51:
------------------------------

    Assignee: Ken Zink  (was: Derek Palma)

Changing the assignee, since Ken volunteered to write the chapter/step(s) in the Primer in TC meeting of 8/30. No objection from Derek or other TC members. 

> Define core set of Requirement and Capability Types
> ---------------------------------------------------
>
>                 Key: TOSCA-51
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-51
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Task
>          Components: Primer 
>            Reporter: Derek Palma
>            Assignee: Ken Zink
>
> A non-normative set of Requirement and Capability types needs to be defined to enable interoperability.
> These should support the core relationships which have appeared in discussions and presentations such as: 1) containment (hosts/hostedBy) 2) connectsTo (requires/provides) 3) dependsOn (existence)

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://tools.oasis-open.org/issues/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira