RE: [tosca] Managing TOSCA type profiles in github

As an alternative, we could try to create sub-directories along functional areas, for example

/examples

/examples/type_definitions

/examples/type_definitions/node_types

/examples/type_definitions/relationship_types

/examples/entity_definitions

/examples/entity_definitions/parameter_definitions

â.

/examples/entity_refinements

/examples/entity_refinements/property_refinements

Or, we could try to align with Chapter and Section titles (or shorthands for those) without being tied to specific numbering schemes.

Chris

From: Tal Liron <tliron@redhat.com>
Sent: Thursday, January 30, 2020 9:00 AM
To: Chris Lauwers <lauwers@ubicity.com>
Cc: Chet Ensign <chet.ensign@oasis-open.org>; tosca@lists.oasis-open.org
Subject: Re: [tosca] Managing TOSCA type profiles in github

On Thu, Jan 30, 2020 at 10:19 AM Chris Lauwers <lauwers@ubicity.com> wrote:

Having version-specific subdirectories doesnât really solve the issue. Itâs true that once a version has been released, the section numbers wonât change, but that isnât really the problem. The problem exists during the editing process of a new version. During the editing phase (over the course of 6-9 months), sections may be reorganized several times. Each of these reorganizations will require most if not all of the examples to be renamed.

Well, if you can think of a better way to name them, please suggest. :) We can also just give it a try and see what works.

Quick thought is that some sections might have multiple examples, so the names might need some kind of number postfix.

tosca message