GitHub Twitter

Workflow DRAFT Profile

Version: 0.3-DRAFT-2020_03_03 (03 March 2020)

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.


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 > SoftwareSourceCode

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

Latest draft: 0.3-DRAFT-2020_03_03

Previous profiles

Previous version: 0.2-DRAFT-2019_11_29


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

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


View all examples
Property Expected Type Description CD Controlled Vocabulary Example
Marginality: Minimum.
creator Organization
Person
Schema:

The creator/author of this CreativeWork. This is the same as the Author property for CreativeWork.


MANY
View ≪creator≫ example
dateCreated Date
DateTime
Schema:

The date on which the CreativeWork was created or the item was added to a DataFeed.


ONE
View ≪dateCreated≫ example
input Thing
Schema:

the input required to use the workflow (eg. xl spreadsheet, xml file, …)


MANY
name Text
Schema:

The name of the item.


Bioschemas:

The name of the item as input

ONE
View ≪name≫ example
output Thing
Schema:

the output produced by the workflow


MANY
programmingLanguage ComputerLanguage
Text
Schema:

The computer programming language.


MANY
sdPublisher Organization
Person
Schema:

Indicates the party responsible for generating and publishing the current structured data markup, typically in cases where the structured data is derived automatically from existing published content but published on a different site. For example, student projects and open data initiatives often re-publish existing content with more explicitly structured metadata. The sdPublisherproperty helps make such practices more explicit.


ONE
View ≪sdPublisher≫ example
url URL
Schema:

URL of the item.


ONE
version Number
Text
Schema:

The version of the CreativeWork embodied by a specified resource.


Bioschemas:

version is a release, date modified may not warrant a release, but last date modified and access to all versions is important

ONE
View ≪version≫ example
Marginality: Recommended.
contributor Organization
Person
Schema:

A secondary contributor to the CreativeWork or Event.


MANY
View ≪contributor≫ example
description Text
Schema:

A description of the item.


ONE
View ≪description≫ example
hasPart CreativeWork
Schema:

Indicates an item or CreativeWork that is part of this item, or CreativeWork (in some sense). Inverse property: isPartOf.


MANY
keywords Text
Schema:

Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.


ONE
license CreativeWork
URL
Schema:

A license document that applies to this content, typically indicated by URL.


ONE
View ≪license≫ example
softwareRequirements Text
URL
Schema:

Component dependency requirements for application. This includes runtime environments and shared libraries that are not included in the application distribution package, but required to run the application (Examples: DirectX, Java or .NET runtime). Supersedes requirements.


Bioschemas:

Renaming schema.org/requirements as softwareRequirements

MANY
targetProduct SoftwareApplication
Schema:

Target Operating System / Product to which the code applies. If applies to several versions, just the product name can be used.


MANY
Marginality: Optional.
alternateName Text
Schema:

An alias for the item.


MANY
dateModified Date
DateTime
Schema:

The date on which the CreativeWork was most recently modified or when the item’s entry was modified within a DataFeed.


ONE
View ≪dateModified≫ example
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.


MANY
View ≪identifier≫ example
image ImageObject
URL
Schema:

An image of the item. This can be a URL or a fully described ImageObject.


MANY

Top ▲