TOSCA YAML v1.2 bugs and recommendation changes

Hello Chris and Claude,

 

I may be able to attend today YAML call, due to my traveling.  Anyway, I would like to report to YAML team a list of bugs and recommendation of changes (ref: version 1.2), would you please add to do list for fix version 1.2:

 

Section 3.6.9.5: entry schema is required for collection types

Recommend to have “entry_schema” as required properties

Section 3.6.11.3:  “entry_schema” definition (gray box) is missing or not consistence with above table. Recommendation: add entry_schema to the defintion

Section 3.6.11.3:  the entry schema is required for collection types when the attribute does not have a corresponding property. Recommendation: to have “entry_schema” as required for attribute.

Section 3.6.15.2.1: the inputs should be <property_assignments>. Recommendation: update the section to illustrate property_assignments: (in the gray boxes).

Section 3.6.17: 
one of the two:

requirement and capability can not be defined simulatanously (preferred)

both requirement and capability must match the trigger

Section 3.6.18.1:is the event_type required or optional (the text and table contradict each other): Recommendation: update the table and definition to show required (yes).

Section 3.6.18.1: the type of the condition is not consistent (object [specified in short and extended notations] or list [ specified in keynames ] ). Recommendation:  “condition:    <list_of_condition_clause_definition>”.

Section 3.6.18.3.1:
the example in the short notation should be event_type: instead of event:. Recommendation: change to event_type.

Section 3.7.2.2.2: the occurrences is missing from extended notation. Recommendation: add “occurrences” the definition.

Section 3.7.7.2: the derived_from is required for except the "root capability".

Section 3.8.2.1:

occurrences is missing from the first table. Recommendation: update the table

interfaces is missing from the second table. Recommendation: update the table

Section 3.8.2.2.3:

the definition of the capability_symbolic_name is not consistent with 3.8.2.1 (the " ordered list of specific, " should be removed from the sentence.

Please interpret this of give an example.  interface_assignments: represents the optional list of interface definitions for the declared relationship used to provide property assignments on inputs of interfaces
 and operations.

Section 4.4.2.2: If the get_property contains more than two parameters, than the resolution of the parameters is the not defined.

Section 5.5.3.2: the shortname is not a possible attribute

Section 5.8.5.1: duplicate description property

Section 5.9.3.3: rename tosca.nodes.BlockStorage to tosca.nodes.Storage.BlockStorage

Section 5.9.10.2 add two space before maxsize

Section 5.9.13: rename tosca.capabilities.EndPoint to tosca.capabilities.Endpoint

Section 5.9.14.1: the requirement section can not have a description property (see. 3.7.3 ).

Section 11.1.7.3 rename tosca.nodes.BlockStorage to tosca.nodes.Storage.BlockStorage

Section 11.1.8.3: rename tosca.nodes.BlockStorage to tosca.nodes.Storage.BlockStorage

Section 11.1.9.3: rename tosca.nodes.BlockStorage to tosca.nodes.Storage.BlockStorage

 

 

Thinh Nguyenphu

Nokia Networks



+1 817-313-5189