Hi Claude, Chris,
Chris, thanks for confirming our understanding.
I have uploaded a contribution that we believe will improve the situation. We should also discuss if we want to have global change of list of to map of when they are not lists.
List types in TOSCA Simple Profile in YAML
Claude, can we have this in the agenda tomorrow?
Best regards,
Arturo
From: Chris Lauwers <
lauwers@ubicity.com>
Sent: Thursday, July 26, 2018 5:41 PM
To: Arturo Martin De Nicolas <
arturo.martin-de-nicolas@ericsson.com>;
claude.noshpitz@att.com;
mrutkows@us.ibm.com;
tosca@lists.oasis-open.org Cc: Calin Curescu <
calin.curescu@ericsson.com>
Subject: RE: Notation for capability assignments and others
Hi Arturo,
You re correct: capability assignments do not need the leading - since they are not a sequenced list.
I also agree that the terminology is confusing (I struggled with this as well when I first started implementing Tosca). Perhaps we should use set or map instead for any collection that is not sequenced.
Chris
From: Arturo Martin De Nicolas <
arturo.martin-de-nicolas@ericsson.com>
Sent: Thursday, July 26, 2018 4:41 AM
To:
claude.noshpitz@att.com; Chris Lauwers <
lauwers@ubicity.com>;
mrutkows@us.ibm.com;
tosca@lists.oasis-open.org Cc: Calin Curescu <
calin.curescu@ericsson.com>
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
Sent: Tuesday, July 24, 2018 5:44 PM
To: 'NOSHPITZ, CLAUDE' <
cn5542@att.com >;
alex.vul@intel.com ; KATZMAN, ANATOLY <
ak435s@intl.att.com >;
dmytro.gassanov@NetCracker.com ;
don.deel@netapp.com ;
dpalma@vnomic.com ; SHADMI, DAVID <
ds200p@att.com >;
hsurti@cisco.com ;
ifat.afek@alcatel-lucent.com ; D'ANDREA, JOE <
jdandrea@research.att.com >;
JDurand@us.fujitsu.com ;
jeremy@gigaspaces.com ;
jim.hunter@ca.com ;
kraman@redhat.com ;
lauwers@ubicity.com ;
lishitao@huawei.com ;
ljlamers@vmware.com ;
luca.gioppo@csi.it ;
Paul.Lipton@ca.com ;
priya.g@netcracker.com ;
rpenta@redhat.com ; Steve Baillargeon <
steve.baillargeon@ericsson.com >;
thinh.nguyenphu@nokia.com ;
xavier.degenne@fastconnect.fr ;
zhao.huabing@zte.com.cn ;
jpackett@us.ibm.com ;
mrutkows@us.ibm.com Subject: RE: TOSCA Simple Profile WG: Working session July 24 2018
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 >
Sent: Tuesday, July 24, 2018 5:08 PM
To:
alex.vul@intel.com ; KATZMAN, ANATOLY <
ak435s@intl.att.com >; Arturo Martin De Nicolas <
arturo.martin-de-nicolas@ericsson.com >;
dmytro.gassanov@NetCracker.com ;
don.deel@netapp.com ;
dpalma@vnomic.com ; SHADMI, DAVID <
ds200p@att.com >;
hsurti@cisco.com ;
ifat.afek@alcatel-lucent.com ; D'ANDREA, JOE <
jdandrea@research.att.com >;
JDurand@us.fujitsu.com ;
jeremy@gigaspaces.com ;
jim.hunter@ca.com ;
kraman@redhat.com ;
lauwers@ubicity.com ;
lishitao@huawei.com ;
ljlamers@vmware.com ;
luca.gioppo@csi.it ;
Paul.Lipton@ca.com ;
priya.g@netcracker.com ;
rpenta@redhat.com ; Steve Baillargeon <
steve.baillargeon@ericsson.com >;
thinh.nguyenphu@nokia.com ;
xavier.degenne@fastconnect.fr ;
zhao.huabing@zte.com.cn ;
jpackett@us.ibm.com ;
mrutkows@us.ibm.com Subject: TOSCA Simple Profile WG: Working session July 24 2018
For discussion this week:
. Presentation from Priya on Artifact Attribute issues
. Editing and work assignments
Thanks.
--Claude
===
This is an updated invitation to the weekly Simple Profile meeting.
Topic: TOSCA Simple Profile WG (weekly, ad-hoc) Spring 2018
Time: Every Tuesday, 9:00 AM Pacific Time (US and Canada)
Join from PC, Mac, Linux, iOS or Android:
https://zoom.us/j/875426495 Or iPhone one-tap :
US: +16468769923,,875426495# or +16699006833,,875426495#
Or Telephone:
Dial(for higher quality, dial a number based on your current location):
US: +1 646 876 9923 or +1 669 900 6833 or +1 408 740 3766
Meeting ID: 875 426 495
International numbers available:
https://zoom.us/zoomconference?m=BYYCJTh7voW4XksZYo85DJyC7gmJcqiL