Tomoya Tanjo

Related issue: There were two similar but different implementation of "Singularity". That is: - the original version by Lawrence Berkeley National Laboratory (that is now rebranded to [`Apptainer`](https://apptainer.org/)), and -...

Thank you for the explanation, @tetron! I'm curious about whether the message `sample.cwl is valid CWL.` is true (i.e. it is accepted by the current spec) or not (i.e., it...

> Question 1: What kind of output is expected for `ExpressionTool` instead of `CommandLineTool` ? > Question2: What kind of output is expected for `Operation` instead of `CommandLineTool` ? I...

I agree with @kinow that we leave the spec as is (at least in v1.2.0) because clarifying the evaluation strategy may break existing platforms. IMO it is better to fix...

It is a matter of the specification as well as the implementation. Related: https://github.com/common-workflow-language/cwl-v1.2/issues/177

In my understanding, it is to support lazy range of strings, Files and other objects. If so, what is the difference between a channel of `string` and `File` with `streamable:...

FYI: I developed a tool definition named `unwrap` as a workaround of this issue (a term `unwrap` comes from rustlang). https://github.com/pitagora-network/DAT2-cwl/blob/develop/tool/unwrap/unwrap.cwl It takes `Any?` and returns `Any` if it is...

I mean that there should be a description about how to specify the input parameters in external file. Currently, [the specification of CommandLineTool](http://www.commonwl.org/v1.0/CommandLineTool.html) describes how to write the definition of...

Thank you for the suggestion, @mr-c! I will send a request for it and will introduce my own namespace to override `hints` for my workflow engine until it is merged.

Thank you for the information and suggestion, @tetron! So how to do with this issue? Keep it open until v1.3 or close it?