Skip to content
GitHub
Twitter

Tool DRAFT Profile

Version: 0.2-DRAFT-2018_08_21 (21 August 2018)

Bioschemas specification for describing a SoftwareApplication 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
description Text
 Schema:

A description of the item.


 ONE
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
name Text
 Schema:

The name of the item.


 ONE
softwareVersion Text
 Schema:

Version of the software instance.


 ONE
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
Marginality: Recommended.
alternateName Text
 Schema:

An alias for the item.


 MANY
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
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
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
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
publisher Organization
Person
 Schema:

The publisher of the creative work.


 MANY
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
dateCreated Date
DateTime
 Schema:

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


 ONE
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
downloadUrl URL
 Schema:

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


 MANY
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
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
operatingSystem Text
 Schema:

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


Bioschemas:

Operating systems on which the app runs.

 MANY
softwareHelp CreativeWork
 Schema:

Software application help.


Bioschemas:

A documentation for the tool.

 MANY
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