common-workflow-language / common-workflow-language/cwl-v1.2
Valid process requirements for ExpressionTool
- Dominant language
- Common Workflow Language
- Stars
- 45
- Forks
- 28
- PR merge metrics
- No merged PRs in 30d
Description
Some of process requirements that are accepted in [ExpressionTool#requirements](https://www.commonwl.org/v1.0/Workflow.html#ExpressionTool) (e.g., `SubworkflowFeatureRequirement`) are not meaningful for ExpressionTool.
What happens when they are specified in `ExpressionTool#requirements`?
For me, it is reasonable to restrict process requirements for ExpressionTool.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start with the linked ExpressionTool#requirements section in the CWL v1.2 Workflow specification and compare the accepted requirements with those meaningful for ExpressionTool. Determine the intended behavior for irrelevant requirements and whether the specification should restrict them; done means the requirement behavior and any restriction are clearly settled in the specification.
Written by the indexing model from the issue text.
Assessment
- Domain
- documentation
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100