Hi Tal Q1 I see normative node types in the YAML spec. Here it makes sense to call them normative node types :) I see non-normative node types in the YAML spec. Here it makes sense to call them normative node types :) I also know the template author can create its own node types. Should I call them custom node types (which are also classified as non-normative)?
Q2 Can you confirm ARIA will ensure all node types including non-normative and custom will support the Standard lifecycle interface since I see the Standard interface defined as part of tosca.nodes.Root? Q3 Do you have any guidelines about when it is best to create a new custom node type that is derived from root vs derived from an existing normative node type? Does ARIA care? Q4 I see the normative (generic) SoftwareComponent node type that must be hosted on a Compute node. If a "specific SW component" must be hosted on a VDU.Compute node instead, then I assume it is not possible to derive the specific SW component node type from the normative SoftwareComponent node type (?) Regards Steve
