GitHub Twitter Bioschemas Bioschemas
Menu

LabProtocol Specification v. 0.1

Bioschemas specification describing LabProtocol in the life-science.

Profile

Thing > CreativeWork
Bioschemas specifications and types list.

Description:

An experimental protocol is a sequence of tasks and operations executed to perform experimental research in biological and biomedical areas. Experimental protocols are fundamental information structures that support the description of the processes by means of which results are generated in experimental research [1]. Experimental protocols describe how the data were produced, the steps undertaken and conditions under which these steps were carried out. [1] Giraldo, O., Garcia, A., Corcho, O.: SMART Protocols: SeMAntic RepresenTation for Experimental Protocols, Riva del Garda, Trentino, Italy (2014). 4th Workshop on Linked Science 2014- Making Sense Out of Data (LISC2014)


Property Expected Type Description CD Controlled Vocabulary
Cardinality: Minimum.
reagent PhysicalEntity, Text
URL
Reagent used in the protocol. It can be a record in a Dataset describing the reagent or a PhysicalEntity corresponding to the reagent or a URL pointing to the type of reagent used. ChEBI and PubChem entities can be used whenever available. Commercial names are also acceptable (URL if possible)
MANY
purpose Text
A goal towards an action is taken. Can be concrete or abstract.
MANY
instrument Thing, Text
URL
The object that helped the agent perform the action. e.g. John wrote a book with a pen. For LabProtocols it would be a laboratory equipment use by a person to follow one or more steps described in this LabProtocol.
MANY
sample PhysicalEntity, Text
URL
Sample used in the protocol. It could be a record in a Dataset describing the sample or a physical object corresponding to the sample or a URL pointing to the type of sample used.
MANY
Cardinality: Recommended.
description Text
A description of the item.
ONE
identifier PropertyValue, Text, URL
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
citation CreativeWork
URL
A citation or reference to another creative work, such as another publication, web page, scholarly article, etc.
MANY
license CreativeWork
URL
A license document that applies to this content, typically indicated by URL.
ONE
hasPart CreativeWork
Indicates a CreativeWork that is (in some sense) a part of this CreativeWork.
MANY
keywords Text
Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.
MANY
software SoftwareApplication
An application that can complete the request.
MANY
duration Duration
The time it takes to actually carry on the protocol, in ISO 8601 duration format.
ONE
Cardinality: Optional.
additionalType URL
An additional type for the item, typically used for adding more specific types from external vocabularies in microdata syntax. This is a relationship between something and a class that the thing is in. In RDFa syntax, it is better to use the native RDFa syntax - the 'typeof' attribute - for multiple types. Schema.org tools may have only weaker understanding of extra types, in particular those defined externally.
ONE SP
isBasedOn CreativeWork
URL
A resource that was used in the creation of this resource. This term can be repeated for multiple sources. For example, http://example.com/great-multiplication-intro.html.
MANY
isPartOf CreativeWork
Indicates a CreativeWork that this CreativeWork is (in some sense) part of.
MANY

Top ▲