From fea5faed23bdeec2ee8616ae9fcc014b33fed926 Mon Sep 17 00:00:00 2001 From: Toby Hodges Date: Tue, 28 Nov 2017 11:26:26 +0100 Subject: [PATCH] added subworkflowfeaturerequirement note --- _extras/recommended-practices.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/_extras/recommended-practices.md b/_extras/recommended-practices.md index d911bc02..3a5cc4d0 100644 --- a/_extras/recommended-practices.md +++ b/_extras/recommended-practices.md @@ -38,6 +38,8 @@ Below are a set of recommended good practices to keep in mind when writing a Com ☐ Give the tool description to a colleague (preferably at a different institution) to test and provide feedback. +☐ CWL implementations which also implement [`SubworkflowFeatureRequirement`][subworkflow] can support nesting workflows as a step within others. Complex workflows with individual components which can be abstracted should utilise this to make their workflow modular and allow sections of them to be easily reused. + [apache-license]: https://www.apache.org/licenses/LICENSE-2.0#apply [license-example]: https://github.com/ProteinsWebTeam/ebi-metagenomics-cwl/blob/master/workflows/emg-assembly.cwl#L200 [scicrunch-issue]: https://github.com/common-workflow-language/common-workflow-language/issues/scicrunch.org @@ -45,3 +47,4 @@ Below are a set of recommended good practices to keep in mind when writing a Com [iana-types]: http://www.iana.org/assignments/media-types/media-types.xhtml [file-prop]: http://www.commonwl.org/v1.0/CommandLineTool.html#File [orcid]: https://orcid.org +[subworkflow]: http://www.commonwl.org/v1.0/Workflow.html#SubworkflowFeatureRequirement