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

XMLWordPrintable

    • Type: New Feature
    • Resolution: Unresolved
    • Priority: Major
    • None
    • Affects Version/s: None
    • Component/s: Public Review
    • None
    • Hide

      from scrum session 1:

      recommend close no action and respond that it is not our intention to have oasis manage this but to let communities manage bottom up e.g. openstack

      Show
      from scrum session 1: recommend close no action and respond that it is not our intention to have oasis manage this but to let communities manage bottom up e.g. openstack

      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?

            Assignee:
            Unassigned
            Reporter:
            Martin Chapman (Inactive)
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

              Created:
              Updated: