We are definitely going with "option A". ARIA aims to support all versions TOSCA, not just the latest.
The _extension section is not about version managements, but about providing a bridge between YAML and Python code, as well as various debugging information. Is is entirely internal to ARIA, as are all these YAML files. On Tue, Oct 24, 2017 at 5:12 PM, Steve Baillargeon < [email protected]> wrote: > Hi > I currently see a YAML document called tosca-simple-1.0.yaml that imports > the following files: > > > * artifactcs.yaml > * capabilities.yaml > * data.yaml > * groups.yaml > * interfaces.yaml > * nodes.yaml > * policies.yaml > * relationships.yaml > > Each imported file has a set of normative types and each type provides a > reference to a YAML profile specification version. > > YAML Profile 1.2 introduces new types. > YAML Profile 1.2 also makes changes to normative types while keeping the > same type name. > > Option A. Is the plan to create a tosca-simple-1.2.yaml (eventually) that > imports a completely different set of type definitions documents? > > Option B. Or is the plan to continue expanding on the existing normative > type documents by mixing multiple YAML Profile versions in the same type > definitions doc? > > I think I prefer option A. In addition, I think we should indicate the > YAML specific version in the filename for each definitions document, say > capabilities-1.0.yaml. > I also think the all type definitions documents including the main > document (e.g. tosca-simple-1.0.yaml) should include the > tosca_definitions_version in the first line. > This way we can remove the specification keyname in the _extension section > for each type definition. > What do you think? > > Regards > Steve Baillargeon > >
