GitHub Twitter

Event Specification v. 0.1

Specification for describing an event in the Life Sciences.


Contributors

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

Group Leader(s)
Other team members

Description

Specification for describing a Life Science event. This includes conferences, workshops, meetings, courses, receptions, networking and prizegivings.


Schema.org hierarchy

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

Thing > Event



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


Property Expected Type Description CD Controlled Vocabulary Example
Marginality: Minimum.
contact Organization
Person
Bioschemas:

Main point of contact that can be contacted for general queries. This would be an event organizer or an administrator.

MANY
description Text
Schema:

A description of the item.


MANY
endDate Date
DateTime
Schema:

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


ONE
eventType EventType
Bioschemas:

This can be one of 4 options. Please see controlled vocabulary

MANY
  • workshops and courses
  • meetings and conferences
  • receptions and networking
  • awards and prizegivings
hostInstitution Organization
Bioschemas:

The organization or institution responsible for hosting the event (not necessarily responsible for organizing).

MANY
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:

The location of the event. It is recommended to use Place, and within Place use the PostalAddress and GeoCoordinates.

ONE
name Text
Schema:

The name of the item.


MANY
rdf:type URL
Bioschemas:

This is used by validation tools to indentify the profile used. You must use the value specified in the Controlled Vocabulary column.

ONE
startDate Date
DateTime
Schema:

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


ONE
Marginality: Recommended.
accreditation Organization
Text
Bioschemas:

Type if accrediation or organisation that accredits the event

ONE
alternateName Text
Schema:

An alias for the item.


Bioschemas:

Can be used for the subtitle of the event.

ONE
audience URL
Schema:

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


Bioschemas:

The scientific background the participants should be from. Please use a term from EDAM: Topic.

Note: Bioschemas have changed the Expected Types from Audience to URL.

MANY

EDAM: Topic

deadline Text
URL
Bioschemas:

Deadlines dates for this event e.g. application deadline, poster submission, paper submission, early registration

MANY
eligibility Text
Bioschemas:

Defines the type of eligibility to attend this event e.g. first come first served. Please use one of the values from the Controlled Vocabulary column.

MANY
  • first come first served
  • registration of interest
  • by invitation
keywords Text
Schema:

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


Bioschemas:

NOTE: Keywords is not part of Event

ONE
maximumAttendeeCapacity Integer
Schema:

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


ONE
prerequisite Text
Bioschemas:

A list of prerequisites to be able to attend the event

MANY
programme Text
URL
Bioschemas:

A plan or schedule of activities or procedures to be followed.

ONE
topic URL
Bioschemas:

The scientific topic the event is about. Please use a term from EDAM: Topic.

MANY

EDAM: Topic

url URL
Schema:

URL of the item.


Bioschemas:

It is recommended you specify the URL even if it is the same as the current page.

ONE
Marginality: Optional.
acceptanceNotificationDate Date
Bioschemas:

Date for the host to confirm acceptance to applicants.

MANY
attachment URL
Bioschemas:

Any files or related websites which give more information about this event. e.g. flyers, third party sites handling tickets.

MANY
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:

NOTE: Keywords is not part of Event

ONE
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:

Unique id for the event.

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


ONE
performer Organization
Person
Schema:

A performer at the event—for example, a presenter, musician, musical group or actor. Supersedes performers.


MANY
registrationStatus Text
Bioschemas:

The status of registration for an event; choose a value from the Controlled Vocabulary column.

ONE
  • proposed
  • pre-open
  • open
  • cancelled
  • full
review Review
Schema:

A review of the item. Supersedes reviews.


MANY
socialMedia URL
Bioschemas:

Link to social media websites like twitter or facebook

MANY
sponsor Organization
Person
Schema:

A person or organization that supports a thing through a pledge, promise, or financial contribution. e.g. a sponsor of a Medical Study or a corporate sponsor of an event.


Bioschemas:

The organizations or institutions providing sponsorship for the event.

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


MANY
submitter Organization
Person
Bioschemas:

The person or organization who submits an event to a repository or registry of events (such as iAnn, ISCB).

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


ONE

Top ▲