I see that work is progressing on how an ODA component can be deployed. I see relatively little work on how to specify a system which comprises multiple interlinked ODA components. For example, a such a system is shown in https://projects.tmforum.org/wiki/display/TAC/Components+Interactions+in+Core+Commerce+Management
Hi Peter, apologies for the late response. I somehow lost track of your message.
In my opinion, the question isn't whether relationships in TOSCA are similar to ref's in JSON/YAML. The issue is what the intended use is of the language:
The main benefit of TOSCA, in my opinion, is the orchestration semantics defined *in the language*. Yes, one can associate orchestration semantics with data modeled using YANG or JSONSchema, but those semantics would have to be documented externally to the YANG/JSONSchema documents. They are not part of YANG or JSONSchema.
Hopefully that clarifies some of my earlier statements.
allOf: # Combines the main `Inventory ` schema with `Resource`specific properties
- $ref: '#/components/schemas/InventoryItem'
- type: object
allOf: # Combines the Resource ` schema with `Vendor`specific properties
- $ref: '#/components/schemas/Resource'
example: 'Yet Another object'