GitHub Twitter Bioschemas Bioschemas

Event Specification v. 0.1

Specification for describing an event in the Life Sciences


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

Alejandra Gonzalez-Beltran

Aleksandra Nenadic

Andra Waagmeester

Andy Jenkinson

Christa Janko

Claire Johnson

Dan Timmons

David van Enckevort

Dominique Batista

Federico López Gómez

Gianluigi Zanetti

Heimo Müller

Kaisa Silander

Manuel Corpas

Morris Swertz

Niall Beard

Peter McQuilton

Petr Holb

Philippe Rocca-Serra

Premysl Velek

Rafael C Jimenez

Susanna A Sansone

Vicky Schneider


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

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

Thing > Event

Key to specification table properties where the Expected Types have been changed, or new (i.e., Bioschemas created) properties/types are green. properties/types are red.

Pending properties/types are blue.

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

CD = Cardinality

Property Expected Type Description CD Controlled Vocabulary
Marginality: Minimum
contact Organization
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
Schema: The end date and time of the item (in ISO 8601 date format). ONE
eventType Text Bioschemas: This can be one of 4 options; see the Controlled Vocabulary column. 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 PostalAddress
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.
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 Missing!
startDate Date
Schema: The start date and time of the item (in ISO 8601 date format). ONE
Marginality: Recommended
accrediation Organization
Bioschemas: Type of accrediation or organization that accredits the event. ONE
alternateName Text Schema: An alias for the item.
Bioschemas: Can be used for the subtitle of the event.
audience URL Schema: An intended audience, i.e. a group for whom something was created.
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.
deadline Text Bioschemas: Deadline 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. ONE
maximumAttendeeCapacity Integer Schema: The total number of individuals that may attend an event or venue. ONE
prerequisite Text Schema: A list of prerequisites to be able to attend the event. MANY
programme Text
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.
Marginality: Optional
acceptanceNotification Date Bioschemas: Date for the organizer to confirm acceptance to applicants. MANY
attachment URL Bioschemas: Any files or related websites which give more information about this event. For example, flyers, third party sites handling tickets. MANY
dateModified Date
Schema: The date on which the CreativeWork was most recently modified or when the item's entry was modified within a DataFeed.
Bioschemas: Date when the event was last modified.
identifier PropertyValue
Schema: The identifier property represents any kind of identifier for any kind of Thing, such as ISBNs, GTIN codes, UUIDs etc. 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.
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
Schema: A performer at the event—for example, a presenter, musician, musical group or actor. MANY
registrationStatus Text Bioschemas: The status of registration for an event; choose a value from the Controlled Vocabulary column. ONE proposed,
review Review Schema: A review of the item. MANY
socialMedia URL Bioschemas: Link to a social media website like Twitter or Facebook. MANY
sponsor Organization
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.
submitter Organization
Bioschemas: The person or organization who submits an event to a respository or registry of events (such as iAnn or ISCB). 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. MANY
superEvent Event Schema: An Event that this event is part of. For example, a collection of individual music performances might each have a music festival as their superEvent. ONE

Top ▲