You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by "Stian Soiland-Reyes (JIRA)" <ji...@apache.org> on 2018/02/08 13:58:00 UTC
[jira] [Updated] (TAVERNA-877) Parser for Common Workflow Language
workflows
[ https://issues.apache.org/jira/browse/TAVERNA-877?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stian Soiland-Reyes updated TAVERNA-877:
----------------------------------------
Labels: cwl gsoc2016 gsoc2018 (was: cwl gsoc2016)
> Parser for Common Workflow Language workflows
> ---------------------------------------------
>
> Key: TAVERNA-877
> URL: https://issues.apache.org/jira/browse/TAVERNA-877
> Project: Apache Taverna
> Issue Type: New Feature
> Components: Taverna Language
> Reporter: Stian Soiland-Reyes
> Priority: Minor
> Labels: cwl, gsoc2016, gsoc2018
>
> Common Workflow Language
> http://common-workflow-language.github.io/
> ..is an emerging standard for computational workflows with a focus on bioinformatics command line tools using Docker.
> The semantics of CWL are inspired by Taverna's SCUFL2 model and the Wf4Ever wfdesc vocabulary.
> A good first approximation for integration of CWL for Taverna would be to parse/read CWL workflows into the SCUFL2 model of Taverna Language.
> Running CWL workflows can be achieved by interpreting CWL Tools (which are described in JSON) as a way to configure the Tool Activity with docker commands.
> But this SCUFL2 reader can just represent the CWL configurations as-is.
> There's an early Java SDK for CWL parsing just made, under development at https://github.com/common-workflow-language/cwljava/
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)