Skip to content

Commit 8d0232b

Browse files
authored
Merge pull request #87 from elichad/wroc-spec-updates
Workflow RO-Crate spec updates
2 parents d52e9c4 + d2c0aac commit 8d0232b

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

Workflow-RO-Crate/1.1-DRAFT/index.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -85,7 +85,7 @@ For historical reasons, in Workflow RO-Crates conforming to RO-Crate version 1.1
8585

8686
### Main Workflow
8787

88-
The _Crate_ MUST contain a data entity of type `["File", "SoftwareSourceCode", "ComputationalWorkflow"]` as the _Main Workflow_.
88+
The _Crate_ MUST contain a _Main Workflow_ data entity whose types MUST include `File`, `SoftwareSourceCode` and `ComputationalWorkflow`.
8989

9090
The _Crate_ MUST refer to the _Main Workflow_ via `mainEntity`.
9191

@@ -107,6 +107,10 @@ The _Crate_ COULD contain a _Main Workflow Diagram_, indicated as a data entity
107107

108108
If _Main Workflow Diagram_ is present, the _Main Workflow_ MUST refer to it via `image`.
109109

110+
### Main Workflow Steps
111+
112+
Individual steps of the _Main Workflow_ MAY be described in the crate, in addition to the description of the workflow as a whole. Each step MUST be represented as a `HowToStep`, and the workflow MUST reference any `HowToStep` instances that represent its steps via `step`. Each `HowToStep` instance MAY indicate its position in the execution order via `position`. In addition to `File`, `SoftwareSourceCode` and `ComputationalWorkflow`, a workflow that points to step metadata via `step` MUST have a type of `HowTo`.
113+
110114
### Crate
111115

112116
The _Crate_ MUST specify a `license`. The license is assumed to apply to any content of the crate, unless overriden by `license` on individual `File` entities.
@@ -123,6 +127,8 @@ The `ComputationalWorkflow` description of the _Main Workflow_ SHOULD comply wit
123127

124128
Conformance with the Bioschemas profile SHOULD be indicated with a `conformsTo` on the _Main Workflow_ entity.
125129

130+
Workflows can have multiple input and output parameter slots that have to be mapped to actual files, directories or other values (e.g., a string or a number) before they can be executed. It is OPTIONAL to define such entities for a `ComputationalWorkflow`. If included, parameter definitions MUST be provided as `FormalParameter` entities and referenced from the `ComputationalWorkflow` via `input` and `output`.
131+
126132
**Tip**: See [RO-Crate 1.2: Complying with Bioschemas Computational Workflow profile](https://www.researchobject.org/ro-crate/specification/1.2/workflows.html#complying-with-bioschemas-computational-workflow-profile)
127133

128134
## WorkflowHub-specific Features/Requirements

0 commit comments

Comments
 (0)