LabProtocol DRAFT Profile
Version: 0.4-DRAFT-2020_07_23 (23 July 2020)
Bioschemas profile describing a LabProtocol in Life Sciences
If you spot any errors or omissions with this type, please file an issue in our GitHub.
| Group | Use Cases | Cross Walk | Task & Issues | Examples | Live Deploys |
|---|---|---|---|---|---|
| Laboratory Protocols |
|
|
|
|
|
You can read the release version of this specification here.
Key to specification table
- Green properties/types are proposed by Bioschemas, or indicate proposed changes by Bioschemas to Schema.org
- Red properties/types exist in the core of Schema.org
- Blue properties/types exist in the pending area of Schema.org
- Black properties/types are reused from external vocabularies/ontologies
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 | |
| bioSampleUsed |
BioChemEntity BioSample DefinedTerm Text URL Taxon |
Schema: BioSample 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 | NCBI Taxonomy, Uberon |
|
| keywords |
Text |
Schema: Keywords or tags used to describe this content. Multiple entries in a keywords list are typically delimited by commas. |
ONE | ||
| labEquipmentUsed |
DefinedTerm Text URL |
Schema: A laboratory equipment used by a person to follow one or more steps described in this LabProtocol. |
MANY | BAO, EFO, ERO, OBI |
|
| protocolPurpose |
CreativeWork Text |
Schema: The purpose of the protocol enables readers to make a decision as to the suitability of the protocol to their experimental problem. (see more information here) |
ONE | ||
| reagentUsed |
BioChemEntity DefinedTerm Text URL |
Schema: Reagents used in the protocol. ChEBI and PubChem entities can be used whenever available. Commercial names are also acceptable |
MANY | ChEBI, PubChem |
|
| Marginality: Recommended. | |||||
| author |
Organization Person |
Schema: The author of this content or rating. Please note that author is special in that HTML 5 provides a special mechanism for indicating authorship via the rel tag. That is equivalent to this and may be used interchangeably. |
MANY | ||
| citation |
CreativeWork Text |
Schema: A citation or reference to another creative work, such as another publication, web page, scholarly article, etc. |
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 | ||
| isPartOf |
CreativeWork Trip |
Schema: Indicates an item or CreativeWork that this item, or CreativeWork (in some sense), is part of. Inverse property: hasPart. |
MANY | ||
| license |
CreativeWork URL |
Schema: A license document that applies to this content, typically indicated by URL. |
ONE | ||
| protocolAdvantage |
CreativeWork Text |
Schema: Situations where the Protocol has been successfully employed (see more information here) |
MANY | ||
| protocolApplication |
CreativeWork Text |
Schema: 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. (see more information here) |
MANY | ||
| protocolLimitation |
CreativeWork Text |
Schema: Situations where the Protocol would be unreliable or otherwise unsuccessful (see more information here) |
MANY | ||
| protocolOutcome |
CreativeWork Text |
Schema: Outcome or expected result by a protocol execution (see more information here) |
MANY | ||
| softwareUsed |
SoftwareApplication URL |
Schema: Software or tool used as part of the lab protocol to complete a part of it. |
MANY | ||
| step |
CreativeWork HowToSection HowToStep Text |
Schema: A single step item (as HowToStep, text, document, video, etc.) or a HowToSection. |
MANY | ||
| totalTime |
Duration |
Schema: The total time required to perform instructions or a direction (including time to prepare the supplies), in ISO 8601 duration format. |
ONE | ||
| Marginality: Optional. | |||||
| 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. Bioschemas: Last modified date |
ONE | ||
| datePublished |
Date |
Schema: Date of first broadcast/publication. Bioschemas: Many is used to cover original printed and electronic publication dates. |
MANY | ||
| isBasedOn |
CreativeWork URL |
Schema: 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. Bioschemas: Note: Bioschemas has removed Product from the Expected Types |
MANY | ||