GitHub Twitter

Workflow DRAFT Profile

Version: 0.1-DRAFT (08 February 2019)

Bioschemas specification for describing a workflow in the Life Sciences


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)
Other team members

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





Key to specification table

Schema.org properties where the Expected Types have been changed, or new (i.e., Bioschemas created) properties/types are green.

Schema.org properties/types are red.

Pending Schema.org properties/types are blue.

External (i.e., from 3rd party ontology) properties/types are black.


CD = Cardinality


Property Expected Type Description CD Controlled Vocabulary Example
Marginality: Minimum.
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

Top ▲