GitHub Twitter

CourseInstance DRAFT Profile

Version: 0.3-draft (16 November 2018)

Specification describing the instance of a course.


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 > Event > CourseInstance

Description

This specification can be used in tandem with a Course. A course is used to describe the broad, common aspects of a recurring training event - whereas a course instance is about the specific times and location of when that course is held.





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.
courseMode Text
URL
Schema:

The medium or means of delivery of the course instance or the mode of study, either as a text label (e.g. “online”, “onsite” or “blended”; “synchronous” or “asynchronous”; “full-time” or “part-time”) or as a URL reference to a term from a controlled vocabulary (e.g. https://ceds.ed.gov/element/001311#Asynchronous ).


MANY
  • “online”, “onsite” or “blend of online and onsite”
  • “synchronous” or “asynchronous”
  • “full-time” or “part-time”
View ≪courseMode≫ 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.


ONE
View ≪inLanguage≫ example
location Place
PostalAddress
Text
Schema:

The location of for example where the event is happening, an organization is located, or where an action takes place.


Bioschemas:

Location of the course instance. If the Course Instance is online, input the meetings URI as text in the location box.

ONE
View ≪location≫ example
Marginality: Recommended.
endDate Date
DateTime
Schema:

The end date and time of the item (in ISO 8601 date format).


ONE
View ≪endDate≫ example
instructor Person
Schema:

A person assigned to instruct or provide instructional assistance for the CourseInstance.


Bioschemas:

Person instructing course instance

MANY
View ≪instructor≫ example
offers Offer
Schema:

An offer to provide this item—for example, an offer to sell a product, rent the DVD of a movie, perform a service, or give away tickets to an event.


Bioschemas:

Cost to attend the course

MANY

Currency and value, Date specified price

View ≪offers≫ example
startDate Date
DateTime
Schema:

The start date and time of the item (in ISO 8601 date format).


ONE
View ≪startDate≫ example
url URL
Schema:

URL of the item.


Bioschemas:

The preferred URL of the course page. You must provide this value if it is known

ONE
View ≪url≫ example
Marginality: Optional.
alternateName Text
Schema:

An alias for the item.


MANY
contributor Organization
Person
Schema:

A secondary contributor to the CreativeWork or Event.


MANY
View ≪contributor≫ example
description Text
Schema:

A description of the item.


Bioschemas:

A description of the Course Instance. This description is for specific information about this particular instance. Preferably use the description in Course if this is generic information about the course.

ONE
View ≪description≫ example
duration Duration
Schema:

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


Bioschemas:

Use this for the actual duration of the Course Instance. The Student Learning Time (SLT) can be provided as the timeRequired of the Course.

ONE
View ≪duration≫ example
eventStatus EventStatusType
Schema:

An eventStatus of an event represents its status; particularly useful when an event is cancelled or rescheduled.


ONE
View ≪eventStatus≫ example
funder Organization
Person
Schema:

A person or organization that supports (sponsors) something through some kind of financial contribution.


MANY
View ≪funder≫ example
image ImageObject
URL
Schema:

An image of the item. This can be a URL or a fully described ImageObject.


ONE
View ≪image≫ example
mainEntityOfPage CreativeWork
URL
Schema:

Indicates a page (or other CreativeWork) for which this thing is the main entity being described. See background notes for details. Inverse property: mainEntity.


Bioschemas:

List different URLs that can be used to access the course

MANY
maximumAttendeeCapacity Integer
Schema:

The total number of individuals that may attend an event or venue.


Bioschemas:

Maximum number of attendees

ONE
View ≪maximumAttendeeCapacity≫ example
name Text
Schema:

The name of the item.


Bioschemas:

Name should primarily be added to the Course rather than CourseInstance

ONE
View ≪name≫ example
organizer Organization
Person
Schema:

An organizer of an Event.


MANY
View ≪organizer≫ example
subEvent Event
Schema:

An Event that is part of this event. For example, a conference event includes many presentations, each of which is a subEvent of the conference. Supersedes subEvents. Inverse property: superEvent.


Bioschemas:

For events within events e.g. guest lecture event within a workshop event

MANY
View ≪subEvent≫ example
superEvent Event
Schema:

An event that this event is a part of. For example, a collection of individual music performances might each have a music festival as their superEvent. Inverse property: subEvent.


Bioschemas:

For the event this course takes place within. e.g. Galaxy Workshop during the ISMB Conference.

MANY
View ≪superEvent≫ example

Top ▲