[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: Notation for capability assignments and others
Hi, I have been discussing this internally and our understanding is that each of the capability assignments within a node template should
not be preceded by â-â. And thatâs because they are not really a list (in the sense of the TOSCA YAML type âlistâ) but rather a map. Do you agree with that? If yes: 1. I find it rather misleading for many of the keynames in certain type definitions to define them as âlist ofââ when they are actually not encoded as lists. Examples: properties, capabilities, interfaces and artifacts
keynames in the node template definition 2. It is only those keynames for which the description column says âsequenced listâ that they are encoded as lists. And these may use either the bullet or the square bracket notation. This is also misleading, because
according to the list definition grammar (3.3.4.1) âsequenced listâ or âbullet listâ is just a notation of a list, i.e. there is no semantical difference with a list that uses the square bracket notation, IMO. 3. The examples in clause 2.13 (pages 43 and 44) are incorrect because they show â-â before the capability assignment. Best regards, Arturo From: Arturo Martin De Nicolas Hi Claude, Maybe we can also get clarity during the call on a small issue (offline answers are also good). In a node template you can have a list of capability assignments under âcapabilities:â. Should each capability assignment be preceded by a dash â-â ? My understanding is they should, as per the normal list members notation. But in the TOSCA Simple Profile in YAML I find examples with and without dashes. Thanks. Best regards, Arturo From: NOSHPITZ, CLAUDE <cn5542@att.com> For discussion this week: . Presentation from Priya on Artifact Attribute issues . Editing and work assignments Thanks. --Claude === |
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]