Workflow DRAFT Profile

Version: 0.1-DRAFT-2019_02_08 (08 February 2019)

Bioschemas specification for describing a workflow in the Life Sciences

If you spot any errors or omissions with this type, please file an issue in our GitHub.

Schema.org hierarchy

This Profile fits into the schema.org hierarchy as follows:

Thing > CreativeWork > HowTo

Description

A workflow consists of an orchestrated and repeatable pattern of activity enabled by the systematic organization of resources into processes that transform materials, provide services, or process information. It can be depicted as a sequence of operations, the work of a person or group, the work of an organization of staff, or one or more simple or complex mechanisms. (source Wikipedia.org).

Latest profiles

Latest release: none

Previous profiles

Previous version: none

Contributors

The following people have been involved in the creation of this specification document. They are all members of the Workflow group.

Group Leader(s)

Alan Williams

Stuart Owen

Bert Droesbeke

Other team members

Group	Use Cases	Cross Walk	Task & Issues	Examples	Live Deploys
Workflow

You can read the release version of this specification here.

Key to specification table

Green properties/types are proposed by Bioschemas, or indicate proposed changes by Bioschemas to Schema.org
Red properties/types exist in the core of Schema.org
Blue properties/types exist in the pending area of Schema.org
Black properties/types are reused from external vocabularies/ontologies

CD = Cardinality

Property	Expected Type	Description	CD	Controlled Vocabulary	Example
Marginality: Minimum.
@context	URL	Used to provide the context (namespaces) for the JSON-LD file. Not needed in other serialisations.	ONE		Property ≪@context≫ example `{ "@context": "https://schema.org/" }`
@type	Text	Schema.org/Bioschemas class for the resource declared using JSON-LD syntax. For other serialisations please use the appropriate mechanism. While it is permissible to provide multiple types, it is preferred to use a single type.	MANY	Schema.org, Bioschemas	Property ≪@type≫ example `{ "@type": "HowTo" }`
@id	IRI	Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach.	ONE		Property ≪@id≫ example `{ "@id": "http://example.com/entity/A12345" }`
dct:conformsTo	IRI	Used to state the Bioschemas profile that the markup relates to. The versioned URL of the profile must be used. Note that we use a CURIE in the table here but the full URL for Dublin Core terms must be used in the markup (http://purl.org/dc/terms/conformsTo), see example.	ONE	Bioschemas profile versioned URL	Property ≪dct:conformsTo≫ example `{ "http://purl.org/dc/terms/conformsTo": { "@id": "https://bioschemas.org/profiles/ComputationalWorkflow/0.1-DRAFT-2019_02_08", "@type": "CreativeWork" } }`
identifier	PropertyValue Text URL	Schema: The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. Schema.org provides dedicated properties for representing many of these, either as textual strings or as URL (URI) links. See background notes for more details.	ONE
name	Text	Schema: The name of the item.	ONE
url	URL	Schema: URL of the item.	ONE
Marginality: Recommended.
description	Text	Schema: A description of the item.	ONE
image	ImageObject URL	Schema: An image of the item. This can be a URL or a fully described ImageObject.	MANY
Marginality: Optional.
accessibilityAPI	Text	Schema: Indicates that the resource is compatible with the referenced accessibility API (WebSchemas wiki lists possible values). Bioschemas: If an API is available for the whole workflow, all the available commands should be name	MANY
audience	Audience Text	Schema: An intended audience, i.e. a group for whom something was created. Supersedes serviceAudience. Bioschemas: Domain of field this workflow is intended for, e.g., life sciences, software devloper, genomics researchers, medical sciences	MANY
sameAs	URL	Schema: URL of a reference Web page that unambiguously indicates the item’s identity. E.g. the URL of the item’s Wikipedia page, Wikidata entry, or official website.	MANY