T3: Software - Githubissues

RenskeW / runcrate-analysis

2 stars 1 forks source link

T3: Software #3

Open RenskeW opened 1 year ago

RenskeW commented 1 year ago

The tools directly orchestrated by the workflow, and their dependencies.

SW1 Identification: PID, name, version, release date, and description of the software. Preferred citation. When the software is not FAIR: URL of repository, download date and/or git commit hash as substitutes for PID, version, or release date.
SW2 Documentation: URL of documentation or other metadata which is important to make informed use of the tool. URL to repository with source code of the software.
SW3 Access: URL to downloadable, executable form of the software. License.

RenskeW commented 1 year ago

What is represented in CWLProv RO Bundle in RDF:

The tools directly controlled by the workflow are not represented in RDF.

However, if SoftwareRequirement was specified in the Workflow or CommandLineTool description, this is contained in packed.cwl, including a specs field with a PID resolving to a landing page with metadata in a software repository or registry.

RenskeW commented 1 year ago

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

ro-crate-metadata.json does not mention the software coordinated by the workflow.
SoftwareRequirement can be found in packed.cwl.

RenskeW commented 1 year ago

Suggested enhancement 1:

Include the specs field in ro-crate-metadata.json, e.g. using https://schema.org/softwareRequirements (for SoftwareRequirement in CommandLineTool descriptions).

simleo commented 9 months ago

SoftwareRequirement is converted as of runcrate 0.5.0 (https://github.com/ResearchObject/runcrate/pull/72)