T4: Workflow

[RenskeW]

The workflow and tool descriptions, but not the software they control.

• WF1 General software metadata: At workflow and step level, according to T3.
• WF2 Parameters: Type, format, and description, at workflow and step level.
• WF3 Requirements: Software and hardware resources required to execute the workflow or workflow steps.

[RenskeW]

What is represented in CWLProv RO Bundle in RDF:

• WF2 Parameters: The workflow and step parameters are mentioned, but not properly defined with their type, etc.

In addition, packed.cwl contains:

• WF1: If specified, label, doc, and intent fields for Workflow and CommandLineTool descriptions, see Scenario 1.
• WF2: Parameter type, and, if specified, format and description (label and doc), see Scenario 1.
• WF3: SoftwareRequirements and ResourceRequirements (software requirements)

[RenskeW]

Results of analysis of RO-Crates converted by runcrate from CWLProv RO Bundles:

• ro-crate-metadata.json:
  • WF1: The workflow language is specified.
  • WF2: Parameters are defined with their type and format, but label and doc fields are not propagated to RDF.
• packed.cwl contains the same information as in the CWLProv RO Bundle.

[RenskeW]

Suggested enhancement 1:

Include doc, label, and intent fields of Workflow and CommandLineTool descriptions and their parameters in ro-crate-metadata.json (also see T1)

--> Issue opened in runcrate repository: https://github.com/ResearchObject/runcrate/issues/10

[RenskeW]

Suggested enhancement 2:

Include SoftwareRequirement and ResourceRequirement in ro-crate-metadata.json.

[simleo]

As of runcrate 0.5.0, SoftwareRequirement and ResourceRequirement are converted. In the case of ResourceRequirement only ramMin is converted.