LabProtocol DRAFT Profile

Reagent used in the protocol. It can be a record in a Dataset describing the reagent or a BioChemEntity 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)

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. Note: Bioschemas have added the following to the list of Expected Types: Text and URL.

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

A goal towards an action is taken. Can be concrete or abstract.

Note: Bioschemas have changed the Expected Types by removing MedicalDevicePurpose and Thing, and adding Text.

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.

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

The duration of the item (movie, audio recording, event, etc.) in ISO 8601 date format.

The time it takes to actually carry out the protocol, in ISO 8601 date format.

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

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.

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.

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

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

An application that can complete the request.

A single step item (as HowToStep, text, document, video, etc.) or a HowToSection.

Use in LabProtocol to include the step by step process followed in this protocol.

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.

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)

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.

Note: Bioschemas have removed Product from the Expected Types