GitHub Twitter

Tool DRAFT Specification v. 0.2-draft

Bioschemas specification for describing a SoftwareApplication in the Life Sciences


Contributors

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

Group Leader(s)
Other team members

Description

The Life Science Tools specification provides a way to describe bioscience tools and software on the World Wide Web. It defines a set of metadata and vocabularies, built on top of existing technologies and standards, that can be used to represent such tools in Web pages and applications. The goal of the specification is to make it easier to discover, exchange and integrate information about life science tools across the Internet.


Schema.org hierarchy

This is a new Profile that fits into the schema.org hierarchy as follows:

Thing > CreativeWork > SoftwareApplication



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.
description Text
Schema:

A description of the item.


ONE
View ≪description≫ example
featureList Text
URL
Schema:

Features or modules provided by this application (and possibly required by other applications).


Bioschemas:

Please choose values from EDAM:Operation.

MANY

EDAM:Operation

View ≪featureList≫ example
name Text
Schema:

The name of the item.


ONE
View ≪name≫ example
softwareVersion Text
Schema:

Version of the software instance.


ONE
View ≪softwareVersion≫ example
url URL
Schema:

URL of the item.


Bioschemas:

URL of the item. This property can be used on a page listing many software tools, to indicate each individual tool’s page.

ONE
View ≪url≫ example
Marginality: Recommended.
alternateName Text
Schema:

An alias for the item.


MANY
View ≪alternateName≫ example
citation CreativeWork
Text
Schema:

A citation or reference to another creative work, such as another publication, web page, scholarly article, etc.


Bioschemas:

Publication about this software.

MANY
View ≪citation≫ example
input URL
Bioschemas:

The input format of the data. Must be one of the EDAM:Data concept labels or one of its synonyms.

MANY

EDAM:Data

View ≪input≫ example
license Text
URL
Schema:

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


Bioschemas:

The applicable software license. Note: Bioschemas have changed the Expected Types to URL or Text.

MANY
View ≪license≫ example
output URL
Bioschemas:

The output format of the data. Must be one of the EDAM:Data concept labels or one of its synonyms.

MANY

EDAM:Data

View ≪output≫ example
publisher Organization
Person
Schema:

The publisher of the creative work.


MANY
View ≪publisher≫ example
Marginality: Optional.
applicationCategory Text
Schema:

Type of software application, e.g. ‘Game, Multimedia’.


Bioschemas:

Type of software e.g. database, tool, service. Note: Bioschemas have removed URL from the Expected Types.

MANY

Please choose terms from the ‘tool type’ table in the biotools documentation

View ≪applicationCategory≫ 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
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
downloadUrl URL
Schema:

If the file can be downloaded, URL to download the binary.


MANY
View ≪downloadUrl≫ example
hasPart CreativeWork
Schema:

Indicates a CreativeWork that is (in some sense) a part of this CreativeWork. Inverse property: isPartOf.


Bioschemas:

Used to describe tools included into suites/bundles/workflows.

MANY
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
View ≪identifier≫ example
keywords Text
Schema:

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


ONE

EDAM:Topic

View ≪keywords≫ example
operatingSystem Text
Schema:

Operating systems supported (Windows 7, OSX 10.6, Android 1.6).


Bioschemas:

Operating systems on which the app runs.

MANY
View ≪operatingSystem≫ example
softwareHelp CreativeWork
Schema:

Software application help.


Bioschemas:

A documentation for the tool.

MANY
View ≪softwareHelp≫ 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.


MANY
View ≪softwareRequirements≫ example

Top ▲