|Subtitle||Bioschemas specification describing LabProtocol in the life-science.|
For instructions please see:
|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 . Experimental protocols describe how the data were produced, the steps undertaken and conditions under which these steps were carried out.
 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||BSC Description||Marginality||Cardinality||Controlled Vocabulary|
|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.||Bioschemas usage.|
Optional for LabProtocol as it has its own type in schema.org. If used, the recommended URL is SmartProtocols (http://purl.org/net/SMARTprotocol#ExperimentalProtocol)
|description||Text||A description of the item.|
Bioschemas usage. Use in LabProtocol to include the step by step process followed in this protocol.
|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.||Recommended||ONE|
|citation||CreativeWork or URL||A citation or reference to a creative work, such as a publication, web page, scholarly article, etc.||Recommended||MANY|
|license||CreativeWork or URL||A license document that applies to this content, typically indicated by URL.||Recommended||ONE|
|isBasedOn||CreativeWork or |
|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. Supersedes isBasedOnUrl.||Optional||MANY|
|isPartOf||CreativeWork||Indicates a CreativeWork that this CreativeWork is (in some sense) part of.||Optional||MANY|
|hasPart||CreativeWork||Indicates a CreativeWork that is (in some sense) a part of this CreativeWork.|
Inverse property: isPartOf.
Bioschemas usage. A particular case in Bioschemas is LabProtocol where structural elements are used to described advantages (situations the Protocol has been successfully employed), limitations (situations the Protocol would be unreliable or otherwise unsuccessful), applications (Applications of the protocol list the full diversity of the applications of the method and support if is possible to extend the range of applications of the protocol. e.g. northern blot assays, sequencing, etc.), and outcomes (outcome or expected result by a protocol execution). For LabProtocol, in the applicationType, please use http://purl.org/net/SMARTprotocol#AdvantageOfTheProtocol for advantages, http://purl.org/net/SMARTprotocol#LimitationOfTheProtocol for limitations, http://purl.org/net/SMARTprotocol#ApplicationOfTheProtocol for applicability, and http://purl.org/net/SMARTprotocol#OutcomeOfTheProtocol for outcomes.
Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas.
|reagent||PhysicalEntity, Text or 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)||Minimum||MANY|
A goal towards an action is taken. Can be concrete or abstract.
|instrument||Thing, Text or 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.
|sample||PhysicalEntity, Text or 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.
An application that can complete the request.
The time it takes to actually carry on the protocol, in ISO 8601 duration format.