Hi,
While doing the âlistâ to âmapâ changes I managed to look through some sections and paragraphs that contained the word âlistâ. I also came to the following:
- Inconsistencies that need to be addressed:
- The occurrences definition in the capability definition (section 3.7.2) is nonsensical. We should change it to mean
dangling unmatched capability, that should not be allowed once the node with such a capability is matched and introduced in the instance model.
- In the definition of group type, in section 3.7.11.2 attributes are not in grammar example, capabilities are not in the following legend
- Requirement assignment is wrong and should not be allowed. The whole section 3.8.10 needs to be reviewed.
See comments in document.
- The context of several TARGETS should be of the requirement, not of the relationship (each relationship has only one TARGET), see comment in document. See section 4.2.1. Same for SOURCES and
capability instead of resource. See section 4.2.1.
- The usage of unordered list in sections 6.2.1 and 6.2.2 proposes a YAML wrong syntax. We should correct.
- I think also that the presentation of substitution_mappings is lacking:
- To improve the definition of the different mappings in the substitution_mappings description
i. section: 3.9.2.7 and 3.8.12
- To specify that the operation outputs mappings from section 3.6.17 are constrained as node name for the keyword SELF and as relationship name for the keyword SELF, SOURCE, TARGET
- Provide a hyperlink to attribute mappings in section 3.6.17.1, and 3.6.18.1.
- The previus is in addition to the mail thread on how to specify substitution mappings for requirements with several occurrences, where we would like to used different
nodes in the substitution template for different subsets/each of the occurrences.
- Regarding the document form, I think:
- we should replace some cross-references with hyperlinks in several examples.
i. the hyperlinks are clearly marked (blue underline) that they are clickable.
This should be used when pointing to definitions.
ii. cross-references are indistinguishable from normal text, this should be used when referring to section numbers, as they will be automatically updated
- question: why do we use bookmarks and the section headings for the hyperlinks in the text?
- Some additional questions:
- If an imperative workflow step evaluation filter is false, will the on_success still be triggered, or the step will silently be discarded. What will happen with the next step that is waiting
for this to finish?
- How can the parser differentiate between a key in a property of a complex type assignment and an intrinsic function to be evaluated?
BR,
/Calin
From:
<tosca@lists.oasis-open.org> on behalf of Calin Curescu <calin.curescu@ericsson.com>
Date: Thursday, 23 August 2018 at 12:31
To: "tosca@lists.oasis-open.org" <tosca@lists.oasis-open.org>
Subject: [tosca] Groups - TOSCA-Simple-Profile-YAML-v1.3-wd01-rev06-draft.docx uploaded
Submitter's message
Please find the draft proposal for rev06 of v1.3. The main change is to replace "list" with "map", and "sequenced list" with "list", to avoid confusion and conform to proper YAML denomination. See more detail in the document revision history.
-- Dr. Calin Curescu