An event is an occurrence that people may attend.
The Event class should have properties for:
1st Session of the 41st Parliament
Parliament convened on June 2, 2011, with the election of Andrew Scheer as Speaker, followed the next day with the Speech from the Throne.
start date and time
June 2nd, 2011
end date and time
September 13, 2013
House of Commons
the organization responsible for the event
Parliament of Canada
Members of Parliament
Dublin Core, Schema.org and NEPOMUK Calendar Ontology terms are retained from the inventory of terms.
According to Schema.org, an event can be organized and attended by either people or organizations; in this data specification, only organizations can organize events, and only people can attend events.
||An occurrence that people may attend|
||The event's name|
||The event's description|
||The time at which the event starts|
||The time at which the event ends|
||The event's location|
||The event's status|
||An issued identifier, e.g. an Open Civic Data Division Identifier|
||The event's category|
||The organization organizing the event|
||A person attending the event|
||An event that this event is a part of|
JSON differences from other RDF serializations:
locationproperty is a string, instead of a
statusis used instead of
eventStatus, as the class name prefix is unnecessary and inconsistent with all other properties.
statusproperty is a string, instead of a
identifiersis used instead of
identifierand is serialized as an array of identifier objects.
classificationis used instead of
categories, to be consistent with the Organization class.
organizationis used instead of
organizer, to be consistent with the Membership class.
attendeesis used instead of
attendee, to agree with the grammatical number of other properties.
parentis used instead of
superEvent, due to its popularity among ORMs.
Implementations may use values from outside the following lists.
The following is a copy of RFC 5545 (iCalendar)’s code list.
The following is a copy of Schema.org’s EventStatusType enumeration.