[OASIS Issue Tracker] Commented: (TOSCA-7) Alternative Encodings of TOSCA Service Templates

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

    [ http://tools.oasis-open.org/issues/browse/TOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=29513#action_29513 ] 

Derek Palma commented on TOSCA-7:
---------------------------------

on 2/16 discussion resulted in:

1) As the result of a motion, the TC considers XML the canonical encoding and the spec will use this. The spec will not include alternative encodings. Separate documents will contain these.
2) Alternative encodings will be revisited when the spec (canonical form) is usable.
3) The TC agrees to support JSON/YAML alternative encodings. This is only feasible once validation requirements and their specification for the canonical form are available. The deliverables would consist of translation rules from the canonical form to the alternative forms along with a specification of validation constraints usable in the target encoding's object model.
4) This issue should be linked to TOSCA #4.

> Alternative Encodings of TOSCA Service Templates
> ------------------------------------------------
>
>                 Key: TOSCA-7
>                 URL: http://tools.oasis-open.org/issues/browse/TOSCA-7
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Improvement
>          Components: Spec
>            Reporter: Derek Palma
>            Assignee: Derek Palma
>            Priority: Minor
>
> At the last (Jan 26) TC meeting there was some discussion about Alternative Encodings of TOSCA Service Templates. It may be useful to augment the draft to explicitly address this issue so it is clear that TOSCA is not confining itself to only XML encodings.
> Below is some text which captures some of these ideas:
> Alternative Encodings of TOSCA Service Templates
> The Topology and Specification for Cloud Applications (TOSCA) is a metamodel which specifies the core concepts, entities, relations and constraints required for defining IT services. This metamodel is encoded in this specification using XML Schema and related standards. Service Templates are instances of entities compliant with the TOSCA metamodel  endcoded in XML following the syntactic rules governed by XML Schema and XML Specification.
> In order to further applicability and facilitate adoption, the TOSCA TC acknowledges the diversity of clouds, offering a diversity of languages and frameworks, with their respective user bases, and anticipates the need to represent Service Templates in encodings other than XML (e.g. YAML, JSON) as well as the need for API implementations  in multiple languages that can create and manipulate Service Templates serializing to/from these alternative encodings. Implementations of alternative encodings should adhere to the TOSCA semantics in order to consume/produce semantically valid Service Templates in a specific encoding and enable translations to/from the canonical XML encoding. 
> Because all alternative encodings must abide by the TOSCA semantics, they can only diverge in how they represent their alternative encoding. For example, two YAML implementations may be able to consume and produce a valid Service Template XML, but may encode the Service Template differently in YAML. These diverging YAML implementations can still interoperate by translating to XML. However, if YAML interoperability is desired a set of translation rules between canonical XML and YAML need to be agreed upon.

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