GitHub Twitter

CourseInstance DRAFT Specification v. 0.1-draft

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

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.


Schema.org hierarchy

This is a new Profile that fits into the schema.org hierarchy as follows:

Thing > Event > CourseInstance



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 ).


ONE

“online”, “onsite” or “blended”; “synchronous” or “asynchronous”; “full-time” or “part-time”

View ≪courseMode≫ example
instructor Person
Schema:

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


Bioschemas:

Faculty instructing course instance

MANY
View ≪instructor≫ 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

ONE
View ≪location≫ example
name Text
Schema:

The name of the item.


ONE
View ≪name≫ 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:

URL of the course instance

ONE
View ≪url≫ example
Marginality: Recommended.
description Text
Schema:

A description of the item.


ONE
View ≪description≫ example
duration Duration
Schema:

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


ONE
View ≪duration≫ example
endDate Date
DateTime
Schema:

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


ONE
View ≪endDate≫ example
Marginality: Optional.
contributor Organization
Person
Schema:

A secondary contributor to the CreativeWork or Event.


MANY
View ≪contributor≫ example
doorTime DateTime
Schema:

The time admission will commence.


ONE
View ≪doorTime≫ 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
maximumAttendeeCapacity Integer
Schema:

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


Bioschemas:

Maximum number of attendees

ONE
View ≪maximumAttendeeCapacity≫ 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

Top ▲