Re: [tosca] sharing types between profiles

[Tal Liron <tliron@redhat.com>]

Thanks, Chris, this is useful, and indeed a different problem than the one we discussed.

In my view users should indeed not be allowed to refine this way: the "participant.yaml" must be updated to use profile v2 before. The issue, as I see it, is that profiles are not just versioned types -- they are collections of types designed to work together. There is a context to them. Otherwise, what we get here is a carte blanche to use "participant.yaml", written for v1, in environments for which it has not been validated.

However, there is still an opportunity for the profile designer to allow for such changes: create a "base" profile which both v1 and v2 imports from, and which contains Person. The "base" profile would stay in v1 while the main profile is bumped to v2.

On Tue, Oct 6, 2020 at 1:59 PM Chris Lauwers <lauwers@ubicity.com> wrote:

During this weekâs TOSCA Language Ad-Hoc meeting, we discussed at length the need for allowing type definitions to be shared between different versions of profiles. Tal kept us honest by reminding us we need to focus on the basic problems weâre trying to solve. We kept coming back to substitution mapping as the primary use case, since we may need to match node types defined in different profiles. This led us to consider solutions that are specific to substitution mapping.

Â

However, I remain convinced that substitution mapping is only one of a dozen or so use cases where type sharing may be required. In fact, I would argue that this feature may be necessary for all TOSCA features that identify types by name. To illustrate my point, Iâm attaching a document that illustrates the problem in the context of the new derivation rules weâve been discussing. I hope the text in the document is sufficiently clear, but please let me know if you have any questions.

Â

Thanks,

Â

Chris

Â

Â

---------------------------------------------------------------------
To unsubscribe from this mail list, you must leave the OASIS TC that
generates this mail. Follow this link to all your TCs in OASIS at:
https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php