Skip to content
GitHub
Twitter

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.


Key to specification table

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
@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
@id IRI Used to distinguish the resource being described in JSON-LD. For other serialisations use the appropriate approach. ONE
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
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