James Eddy

Thanks @kaushik-work - we have a bit of overdue GH maintenance, including the latest tag/release. Will try to resolve soon.

Also, because we probably shouldn't overwrite the current `1.0.0` tag/release (it's archived in Zenodo too...), I propose describing the versions for files under `/openapi/v1/` (and similarly, in the future, keeping...

Should take a look and incorporate some of the suggestions from #122

This issue is partially solved by maintaining schema definitions in (separate files)[https://github.com/ga4gh/workflow-execution-service-schemas/tree/develop/openapi/components/schemas] (converting from YAML to JSON Schema should be a trivial extra step). We'd need to think about whether...

Revisiting this.... I propose something along the lines of the following: add the `supported_schemes` property to the `ServiceInfo` response body (and mark `supported_filesystem_protocols` for deprecation). Rather than specifying at which...

So, this is a bit odd, but I'm pretty sure that the `required: true/false` convention only applies to *parameters*. In contrast, for `properties` (or other object definitions), `required` should be...

@patmagee they're there, but as references to individual model YAMLs under [`components/schemas/`](https://github.com/ga4gh/workflow-execution-service-schemas/tree/develop/openapi/components/schemas). The [main OpenaAPI YAML](https://github.com/ga4gh/workflow-execution-service-schemas/blob/develop/openapi/workflow_execution_service.openapi.yaml) gets dereferenced when the docs are build, but the fix for components to show...

Hi @sumit-158 - apologies for the slow reply! I haven't had the bandwidth to pay as much attention to this repo for a while. You're definitely welcome to work on...

That was just so if someone were to navigate to the [`docs/` folder](https://github.com/ga4gh/workflow-execution-service-schemas/tree/develop/docs) within the GH repo, they could be directed to the full, rendered docs page. If there's a...

@susheel - what's the benefit of storing this separately from the `definitions` (or `components` in OpenAPI 3) section of the spec YAML? When converted to JSON, this section provides exactly...