In "Common principles", "Storage of derived datasets":
it is RECOMMENDED to use the format <pipeline>-<variant> in cases where it is anticipated that the same pipeline will output more than one variant
The dash here acts as a delimiter in a comparable way to that of Entities in file names.
In the context of entities, the dash character must be excluded from both key and value strings in order for the delimitation to be unambiguous.
It seems to me that if it is desired for pipeline derivatives to be more standardised, then pipeline names and versions must also be explicitly forbidden by the specification from containing dash characters.
Quick vote:
:+1: : Modify specification to enforce that if a dash appears in a pipeline directory name, there must be only one, and its purpose must be to delimit pipeline name from version.
:-1: : Pipeline derivatives directory names remain freeform; this structure remains a recommendation for human navigation only; machine parsing of derivatives should rely not on these names but the metadata contained within.
In "Common principles", "Storage of derived datasets":
The dash here acts as a delimiter in a comparable way to that of Entities in file names. In the context of entities, the dash character must be excluded from both key and value strings in order for the delimitation to be unambiguous. It seems to me that if it is desired for pipeline derivatives to be more standardised, then pipeline names and versions must also be explicitly forbidden by the specification from containing dash characters.
Quick vote: