RE: [tosca] [OASIS Issue Tracker] (TOSCA-253) capability instead of property in Compute

[Chris Lauwers <lauwers@ubicity.com>]

Hi Luca, I agree that over time lots of tooling will be available to manage service templates. If that's the case, then you're correct that YAML vs. XML vs. JSON doesn't matter. The implication, however, is that keeping XML and YAML specs consistent might not be a good use of time. I would prefer that all of us focus exclusively on getting the Simple Profile spec as complete as possible and not get side-tracked with work on an XML spec.

Chris

-----Original Message-----
From: tosca@lists.oasis-open.org [mailto:tosca@lists.oasis-open.org] On Behalf Of OASIS Issues Tracker
Sent: Thursday, June 25, 2015 11:02 AM
To: tosca@lists.oasis-open.org
Subject: [tosca] [OASIS Issue Tracker] (TOSCA-253) capability instead of property in Compute


    [ https://issues.oasis-open.org/browse/TOSCA-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=59936#comment-59936 ] 

Luca Gioppo commented on TOSCA-253:
-----------------------------------

On another point on "usability" of the tosca file.
I understand that yaml is more readable than XML and that at the start we need to ease the work for people to get near tosca and XML was not helping BUT are we sure that we need to strive for usability at the sake of proper standard semantic?
For how long do we believe that people are going to write tosca file and csar by hand?
The standard is not going to take off untill there will be an editor for this, so in that moment XML, JSON or whatever will become less important, what will remain will be the power of the standard semantic and what you can do with it and if it makes sense.

> capability instead of property in Compute
> -----------------------------------------
>
>                 Key: TOSCA-253
>                 URL: https://issues.oasis-open.org/browse/TOSCA-253
>             Project: OASIS Topology and Orchestration Specification for Cloud Applications (TOSCA) TC
>          Issue Type: Bug
>          Components: Profile-YAML
>    Affects Versions: CSD03
>            Reporter: Luca Gioppo
>            Priority: Critical
>              Labels: misinterpretation
>
> In example H.1.2.4, but in general in all the specification the 
> Compute node has not properties and the properties inside the 
> Capability definition are used, but this does not respect the 
> spcification where the "expected state is written in the property 
> section" the Capability just state that that node offer the capability 
> of being a host and having a OS but should not used in place of 
> "state" declaration



--
This message was sent by Atlassian JIRA
(v6.2.2#6258)

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that generates this mail.  Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php