Open buchanae opened 7 years ago
+1
Is the purpose to avoid collisions with other, existing services at /v1/tasks
? Is this really necessary?
If it is necessary, can we at least use /tes/v1/tasks
?
@kellrott: I think this was already merged (using /ga4gh/v1/tes
now, just like other Cloud WS APIs)? I think we can close this
In https://github.com/ga4gh/workflow-execution-schemas/pull/9#issuecomment-285988194, an approach to API endpoint URL naming was mentioned. We should discuss and agree on adopting this pattern for TES.
The pattern would prefix service API endpoints with
/ga4gh/tes/v1
e.g. the cancel endpoint would be/ga4gh/tes/v1/tasks/1234:cancel