[OASIS Issue Tracker] Created: (TOSCA-57) Improve comsumability of TOSCA schema through re-organization based on roles and use cases

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

Improve comsumability of TOSCA schema through re-organization based on roles and use cases
------------------------------------------------------------------------------------------

                 Key: TOSCA-57
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-57
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Improvement
    Affects Versions: CSD05
            Reporter: Thomas Spatzier 
            Assignee: Thomas Spatzier 


In the current TOSCA schema and spec, all definitions go into a <ServiceTemplate> root element. This can be confusing, e.g. if someone has to define a <ServiceTemplate> when just wanting to provide a new NodeType. <ServiceTemplate> should really just be the service template, and all other definitions should go into a different root. The rough structure would be like:

<ServiceTemplate>
  ...
  <TopologyTemplate>
    ...
  </TopologyTemplate>

  <Plans>
    ...
  </Plans>
</ServiceTemplate>

and then a separate root element for definitions

<Definitions>
  ...
  (
   <NodeType>
     ...
   </NodeType>
  |
   <RelationshipType>
     ...
    </RelationshipType>
  |
   ...
  )+

</Definitions>

I will prepare a version of the spec and schema based on the next complete WD according to the outline above.

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