We agreed on Tuesday to start using github to keep master copies of TOSCA type profiles (such as the Simple Profile). These master copies would act as the “single source of truth” from which other descriptions (such as type definitions
in Word documents) could be automatically generated.
We need to agree on some logistical issues before we can proceed:
- We currently have one TOSCA github repository at
https://github.com/oasis-open/tosca-test-assertions. I assume we don’t want to reuse this repo for managing type profiles. Is there agreement we will create a new repository? If so, what should
we name this repo?
- We’ll start with type definitions that are part of the Simple Profile. Which versions should we support? I assume we will want to manage Version 2.0 of the Simple Profile in this
repository. What about Version 1.3? What about older versions?
- How do we manage the directory structure in this repository? I suggest we use multiple top-level directories, one for each profile. Underneath these directories, will we have subdirectories
for different versions?
- How do we organize a type profile into YAML files? It seems to me we have different options:
- One YAML file for the entire profile
- One YAML file for each type of types (e.g. a datatypes.yaml, nodetypes.yaml, relationshiptypes.yaml, etc.)
- One YAML file for each individual type
Other issues we need to discuss and agree on?
Thanks,
Chris