[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: [OASIS Issue Tracker] Commented: (TOSCA-7) Alternative Encodings of TOSCA Service Templates
[ http://tools.oasis-open.org/issues/browse/TOSCA-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=34089#action_34089 ]
Derek Palma commented on TOSCA-7:
---------------------------------
It seems important that the TC agree on a direction for this effort such as:
1) An alternate encoding of TOSCA in YAML/JSON. This would enable YAML/JSON to represent everything in XML and translation back and forth would be possible without loss of information.
2) A partial expression of TOSCA semantics in YAML/JSON to enable service template authors to consume a subset of TOSCA semantics in YAML/JSON. I.e. one could create less sophisticated service templates in YAML/JSON but would have to revert to XML to take advantage of the advanced features of TOSCA not exposed in the YAML/JSON encoding.
3) A consumer oriented approach allowing a TOSCA model consumer to express aspects of a TOSCA model (in XML) they want to consume and express customization for the templates. This could focus YAML/JSON as a mechanism for consuming types and templates defined in XML but leave management of complex XML creation to tools. The assumption here is that if you want to edit text you'd prefer YAML/JSON but would not try to edit complex documents at which point you'd go with tooling anyway.
> 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
> Affects Versions: V1.1_CSD01
> Reporter: Derek Palma
> Assignee: Krishna Raman
> Fix For: V1.1_CSD01
>
>
> 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
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]