GitHub Twitter

TrainingMaterial DRAFT Profile

Version: 0.7-draft (08 November 2019)

A specification for describing training materials in life sciences.


If you spot any errors or omissions with this type, please file an issue in our GitHub.


Contributors

The following people have been involved in the creation of this specification document. They are all members of the Training group.

Group Leader(s)
Other team members

Schema.org hierarchy

This Profile fits into the schema.org hierarchy as follows:

Thing > CreativeWork

Description

The Life Science Training Materials specification provides a way to describe bioscience training material on the World Wide Web. It defines a set of metadata and vocabularies, built on top of existing technologies and standards, that can be used to represent events in Web pages and applications. The goal of the specification is to make it easier to discover, exchange and integrate life science training material information across the Internet.





Key to specification table

Schema.org properties where the Expected Types have been changed, or new (i.e., Bioschemas created) properties/types are green.

Schema.org properties/types are red.

Pending Schema.org properties/types are blue.

External (i.e., from 3rd party ontology) properties/types are black.


CD = Cardinality


View all examples
Property Expected Type Description CD Controlled Vocabulary Example
Marginality: Minimum.
description Text
Schema:

A description of the item.


ONE
View ≪description≫ example
keywords Text
Schema:

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


ONE
View ≪keywords≫ example
name Text
Schema:

The name of the item.


ONE
View ≪name≫ example
Marginality: Recommended.
about Thing
Schema:

The subject matter of the content.


Bioschemas:

The subject of this Training Material. Use the DefinedTerm type to add a controlled vocabulary term to describe the topic (such as from the EDAM ontology)

MANY

EDAM Topic Ontology

View ≪about≫ example
abstract Text
Schema:

A brief overview of the item.


ONE
View ≪abstract≫ example
audience Audience
Schema:

An intended audience, i.e. a group for whom something was created. Supersedes serviceAudience.


Bioschemas:

A succinct description of the intended target audience for your materials: e.g., graduates, postgraduates, clinicians.

MANY
View ≪audience≫ example
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.


Bioschemas:

Those involved in the preparation, creation and/or presentation of the published work, specifically creating the original version.

MANY
View ≪author≫ example
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.


Bioschemas:

An identifier for this Training Material, such as a DOI or compact URI

MANY
View ≪identifier≫ example
inLanguage Language
Text
Schema:

The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage. Supersedes language.


Bioschemas:

Defaults to English if not specified. Please choose a value from IETF BCP 47 standard. You can add multiple languages if the Training Material offers different translations

MANY

IETF BCP 47 standard

View ≪inLanguage≫ example
learningOutcome Text
Schema:

Statements that describe what knowledge, skills or abilities students should acquire on completion of this Training Material


MANY

It is recommended that you utilize terms from Blooms taxonomy

View ≪learningOutcome≫ example
learningResourceType Text
Schema:

The predominant type or kind characterizing the learning resource. For example, ‘presentation’, ‘handout’.


Bioschemas:

This may also include things such as video lecture, e-Learning module, or tutorial.

MANY
View ≪learningResourceType≫ example
license CreativeWork
URL
Schema:

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


Bioschemas:

If there is a licence it must be added.

MANY
View ≪license≫ example
mentions Thing
Schema:

Indicates that the CreativeWork contains a reference to, but is not necessarily about a concept.


Bioschemas:

Data-sets, tools, technologies, entities, other training materials in the series, etc., to which this Training Material makes reference.

See ‘uses’ for resources that are actively utilised in this training material.

MANY
View ≪mentions≫ example
skillLevel Text
Schema:

The students level of ability in the topic being taught. Examples of skill levels include ‘beginner’, ‘intermediate’ or ‘advanced’.


ONE
  • Beginner
  • Intermediate
  • Advanced
View ≪skillLevel≫ example
timeRequired Duration
Schema:

Approximate or typical time it takes to work with or through this learning resource for the typical intended target audience, e.g. ‘P30M’, ‘P1H25M’.


Bioschemas:

Please specify in ISO 8601 duration format.

ONE

ISO 8601 duration format.

View ≪timeRequired≫ example
url URL
Schema:

URL of the item.


Bioschemas:

The preferred URL of the Training Material. You must provide this value if it is known.

ONE
View ≪url≫ example
uses Thing
Schema:

Lists datasets, tools, technologies, or other entities used.


Bioschemas:

Data-sets, tools, technologies, entities, etc. that are actively utilised in this Training Material.

MANY
View ≪uses≫ example
Marginality: Optional.
accessibilitySummary Text
Schema:

A human-readable summary of specific accessibility features or deficiencies, consistent with the other accessibility metadata but expressing subtleties such as “short descriptions are present but long descriptions will be needed for non-visual users” or “short descriptions are present and no long descriptions are needed.”


ONE
View ≪accessibilitySummary≫ example
contributor Organization
Person
Schema:

A secondary contributor to the CreativeWork or Event.


Bioschemas:

Contributors are those who made non-authorship contributions: e.g., critical review, commentary or revision.

MANY
View ≪contributor≫ example
dateCreated Date
DateTime
Schema:

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


ONE
View ≪dateCreated≫ example
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
View ≪dateModified≫ example
datePublished Date
Schema:

Date of first broadcast/publication.


ONE
View ≪datePublished≫ example
featuredInEvent Event
Course
Schema:

The course instance or event where this training material was or will be featured. Inverse of workFeatured.


Bioschemas:

Use isPartOf to refer to a Course, unless this Training Material is unique to a specific Course Instance.

MANY
View ≪featuredInEvent≫ example
hasPart CreativeWork
Trip
Schema:

Event


Bioschemas:

A sub-Training Material or externally referenced Training Material.

MANY
View ≪hasPart≫ example
isPartOf CreativeWork
Schema:

Indicates a CreativeWork that this CreativeWork is (in some sense) part of. Inverse property: hasPart.


Bioschemas:

The Course in which this Training Material was/will be used, or the Training Material of which this Training Material is a part (e.g., the Training Material could be a chapter that isPartOf a book, or a slide-set that isPartOf a course).

If this varies in CourseInstances, use the featuredIn property

MANY
View ≪isPartOf≫ example
status Text
Schema:

The status of a training material. If this is not filled in it will be regarded as Active. Options are Active, Under development, and Archived.


ONE
  • Active
  • Under development
  • Archived
View ≪status≫ example
translatedInto Thing
Schema:

The language of the content or performance or used in an action. Please use one of the language codes from the IETF BCP 47 standard. See also availableLanguage. Supersedes language.


MANY
View ≪translatedInto≫ example
version Number
Text
Schema:

The version of the CreativeWork embodied by a specified resource.


Bioschemas:

If this Training Material is versioned, it is strongly recommended that you use this property to indicate its version name or number.

ONE
View ≪version≫ example

Top ▲