Skip to content

Commit

Permalink
Merge branch 'release/0.1.0'
Browse files Browse the repository at this point in the history
  • Loading branch information
briandoconnor committed May 20, 2017
2 parents e0a59a6 + cf24029 commit b11f064
Show file tree
Hide file tree
Showing 2 changed files with 6 additions and 1 deletion.
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,7 +5,7 @@ Schemas for the Workflow Execution Service (WES) API

This is used by the Data Working Group - Containers and Workflows Task Team

<img src="swagger_editor.png" width="48">[View in Swagger](http://editor.swagger.io/#/?import=https://raw.githubusercontent.com/ga4gh/workflow-execution-schemas/feature/protobuf-bdo/swagger/proto/workflow_execution.swagger.json)
<img src="swagger_editor.png" width="48">[View in Swagger](http://editor.swagger.io/#/?import=https://raw.githubusercontent.com/ga4gh/workflow-execution-schemas/0.1.0/swagger/proto/workflow_execution.swagger.json)

The [Global Alliance for Genomics and Health](http://genomicsandhealth.org/) is an international
coalition, formed to enable the sharing of genomic and clinical data.
Expand Down
5 changes: 5 additions & 0 deletions USECASES.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,5 @@
Use cases for Workflow Execution Schema

* Federated computing: a researcher can submit an analysis workflow to run on a dataset owned by an external organization, instead of having to make a copy ("bring your own code")
* Web app integration: a web based user interface to a specific workflow can use WES to submit to workflow execution service ("bring your own data")
* Workflow interoperability: workflows written in different languages or running on different clusters can programmatically invoke one another

0 comments on commit b11f064

Please sign in to comment.