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-881) Save Taverna workflows as CWL

     [ https://issues.apache.org/jira/browse/TAVERNA-881?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Stian Soiland-Reyes updated TAVERNA-881:
----------------------------------------
    Labels: cwl gsoc2016 gsoc2018  (was: cwl gsoc2016)

> Save Taverna workflows as CWL
> -----------------------------
>
>                 Key: TAVERNA-881
>                 URL: https://issues.apache.org/jira/browse/TAVERNA-881
>             Project: Apache Taverna
>          Issue Type: New Feature
>          Components: Taverna Language
>            Reporter: Stian Soiland-Reyes
>            Priority: Minor
>              Labels: cwl, gsoc2016, gsoc2018
>
> Many Taverna workflows can probably be represented in CWL - so this issue proposes to add support for serializing to CWL in Taverna Language.
> I propose a staged approach:
> a) Represent workflow structure only (A->B, B->C, B->D)
> b) Save back CWL activities (from TAVERNA-877)
> c) Save/Load other Taverna activities as TavernaRequirement
> d) Save/Load other Taverna activities as DockerRequirement using TAVERNA-879
> The semantics of CWL does not always allow all the iteration strategies of Taverna etc., so presumably only a subset of Taverna workflows could be saved correctly. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)