Susheel Varma

Update: [ga4gh-discovery/ga4gh-service-info#how-to-use-and-extend-this-specification](https://github.com/ga4gh-discovery/ga4gh-service-info#how-to-use-and-extend-this-specification) The suggestion in workstream call is to create a PR but leave it pending discussion of loose ends

+1 @jaeddy A WES service may report that they are not able to access `workflow_*` due to an unsupported access protocol, as such I think we need a special Error...

It is mainly to allow a non-swagger client to still validate the JSON response without processing the swagger spec to extract the JSON schema. I am planning to raise this...

@briandoconnor @jaeddy Yes, I believe this can be generated from the build process. I use https://github.com/instrumenta/openapi2jsonschema

I don't think there is a convention. I was suggesting v1 and v1.1, but happy to limit to just major releases.

Happy with `vMAJOR`

Happy with `PUT` or `POST`. I suggested `POST` as it was similar to webhook conventions

@jaeddy The line below lists out the supported filesystem protocols in the new YAML spec. https://github.com/ga4gh/task-execution-schemas/blob/d55bf880062442288afc95665aa0e21fbba77b20/openapi/task_execution.swagger.yaml#L407

The `name` of the bundle is what you pass along. Expanding on @ddietterich snippet, see @delagoya's bundle example below: ```yaml { 'id' : '4562', 'name': 'foo.bam' ... 'contents' : [...

While I agree that we (Genomics Community) need the concept of related objects, IMO it is served by Bundles. Adding a dedicated concept of `secondary_files` directly into Objects muddies the...