[id: 1-16], [CONCEPT], [MINOR]: Following the basic examples (like in the Quickstart/Usage guide), all
function input parameters (here num) which are not provided by other tasks are automatically defined
as step inputs in the CWL result rather than workflow inputs. In other words they are automatically
considered as step configuration. Am I right? If so, an explanation of this concept in the docs would be
nice.
[id: 1-17], [CONCEPT], [MAJOR], This more a cwl-question: Why are given input values (for steps) are
always defined as default (i.e. default: )? Is the cwl idea that a configuration always needs
to have a default, i.e. is there no possibility to define required values? And if so, does this match the
Ansatz philosophy (not 100% about this right now).
[id: 1-16], [CONCEPT], [MINOR]: Following the basic examples (like in the Quickstart/Usage guide), all function input parameters (here num) which are not provided by other tasks are automatically defined as step inputs in the CWL result rather than workflow inputs. In other words they are automatically considered as step configuration. Am I right? If so, an explanation of this concept in the docs would be nice. [id: 1-17], [CONCEPT], [MAJOR], This more a cwl-question: Why are given input values (for steps) are always defined as default (i.e. default:)? Is the cwl idea that a configuration always needs
to have a default, i.e. is there no possibility to define required values? And if so, does this match the
Ansatz philosophy (not 100% about this right now).