Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 7 additions & 1 deletion Workflow-RO-Crate/1.1-DRAFT/index.md
Original file line number Diff line number Diff line change
Expand Up @@ -85,7 +85,7 @@ For historical reasons, in Workflow RO-Crates conforming to RO-Crate version 1.1

### Main Workflow

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

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

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

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

### Main Workflow Steps

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`.

### Crate

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.
Expand All @@ -123,6 +127,8 @@ The `ComputationalWorkflow` description of the _Main Workflow_ SHOULD comply wit

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

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`.

**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)

## WorkflowHub-specific Features/Requirements
Expand Down
8 changes: 4 additions & 4 deletions _config.yml
Original file line number Diff line number Diff line change
@@ -1,10 +1,10 @@
title: WorkflowHub project

description: >
description: >
Project pages for developing and running WorkflowHub,
a registry of scientific workflows.

remote_theme: ELIXIR-Belgium/elixir-toolkit-theme
remote_theme: ELIXIR-Belgium/elixir-toolkit-theme@5.0.0

permalink: pretty

Expand Down Expand Up @@ -39,10 +39,10 @@ defaults:
values:
search_exclude: true

theme_variables:
theme_variables:
theme_color: 1f8787

plugins:
- jemoji
- jekyll-redirect-from
- jekyll-sitemap
- jekyll-sitemap
Loading