[OASIS Issue Tracker] Created: (TOSCA-43) Type versioning

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

Type versioning
---------------

                 Key: TOSCA-43
                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-43
             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
          Issue Type: Sub-task
          Components: Spec
            Reporter: Derek Palma


Type versioning. A more general term is schema or type evolution. This idea would be applicable if a type A exists, and someone later wants to create a type A' which is intended to be like A but not A and not related in a typed manner . It is important to note that A' and A are completely different types with no way to reason the delta between them. If one wanted some type based on A, they'd create a subclass of A and specialize accordingly. The practical uses of schema versioning is usually to create a completely new set of types which offer a different set of semantics than the previous version, so this is more of a way of labeling schemas.

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