[OASIS Issue Tracker] Created: (CAMP-79) Will OASIS manage/approve common artifact types in the future?

Will OASIS manage/approve common artifact types in the future?
--------------------------------------------------------------

                 Key: CAMP-79
                 URL: http://tools.oasis-open.org/issues/browse/CAMP-79
             Project: OASIS Cloud Application Management for Platforms (CAMP) TC
          Issue Type: New Feature
          Components: Public Review
            Reporter: Martin Chapman 


From the comment list:

https://lists.oasis-open.org/archives/camp-comment/201308/msg00000.html

In section 4.2.1 on Types, I found this text:

"Deployment Plans can contain descriptions of artifacts, services and their relationships. However, it is outside the scope of this specification to provide detailed definitions of these entities. Instead Deployment Plans use 'type' nodes to identify these things. 'Type' nodes are Strings that describe entities that are managed by CAMP, but whose value and semantics are defined outside the CAMP specification. For example, a group of PaaS providers could agree to use the artifact type "org.rpm:RPM" to identify RPM packages. Line 03 in Example 1, above, is an example of the use of such a type." ...

How will interoperability between vendors be achieved?  Will OASIS manage/approve common artifact types in the future?


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