Descriptor type missing from TRS URIs

[uniqueg]

The Problem

The current specification for TRS URIs provides two different setups, an unversioned (e.g., trs://<server>/<id>) and a versioned one (e.g.,trs://<server>/<id>/<version_id>).

However, to unambiguously identify workflow resources, a third type that includes the DescriptorType should be defined as well, since various endpoints require it, e.g., GET /tools/{id}/versions/{version_id}/{type}/files.

This is because technically workflows and wrapped command line tools may be available in multiple flavors under the same tool record within the same TRS registry.

Note that this is not only a theoretical excercise - we have found real-world examples for that!

Possible Solution

Analogous to the unversioned and versioned TRS URIs, a typed TRS URI could be defined as trs://<server>/<id>/<version_id>/<type>

Additional Context

See #221, #220 and #164 for additional considerations.

@anuragxxd

┆Issue is synchronized with this Jira Story
┆Project Name: Zzz-ARCHIVE GA4GH tool-registry-service
┆Issue Number: TRS-73

[denis-yuen]

Interesting, we used to have a small number of workflows implemented in multiple workflow languages, but it stayed small.
What examples did you run into?

Makes sense to add.

[uniqueg]

I guess the ones from Dockstore 😂