The Event Programme Vocabulary

RDF/XML version of this vocabulary. Turtle version of this vocabulary.

Last update:

01 April 2014

Namespace URI:


This Vocabulary provides the means to create a document which describes a large event or other connected series of events. The primary purpose is to help humans comprehend the programme, not describe absolute truth. A single event (or even series) may have multiple programmes.

All terms at a glance

This vocabulary has been imported from


Class: prog:Activity

ActivityThis class represents the abstract content of an event, which may be repeated many times, once or never. For example a training course, or a play. The primary purpose is to indicate that several events will have very similar content, to aid planning what to attend. It does not indicate that there is any reason people could not attend more than one realisation. It should not be used to abstract a repeating event, such as morning coffee or a monthly meeting. Multiple Events may reference that they are realises of the same Activity. Activities are not Events and may not have a time or place.


Class: prog:Programme

ProgrammeA programme is a description of the parts of a complex event to aid understanding it. A single event may be described by several programmes, for example one may give a break down by day, another by rooms, another by topic. A programme should not have Timeslots or Events if it subprogrammes. In effect this means there are two subclasses of Programme, but there's no need to express that in the data. A simple application only needs to operate on a single Programme at once.


Class: prog:TimeSlot

TimeSlotThis is a property of a Programme to facilitate understanding by humans. There is no semantic relationship between events in the programme and TimeSlots as complex programmes often have events which ignore the published timeslots. A timeslot is effectively an event with nothing but a time interval and label. A Timeslot must have an rdfs:label and a event:time linking it to a tl:Interval. Timeslots are purely cosmetic and it is not recommended that events should not be artificially fitted into them.



Property: prog:has_event

programme includes eventIndicates that an Event is part of the specified programme, but not streamed in any particular way. This should not relate a programme to the event it is a programme of. This is used for events in programmes without streams, or for events which are listed in all streams, such as 'Lunch','Check into Accomodation' or 'Plenary'.


Property: prog:has_programme

event is described by programmeConnects an ev:Event with a prog:Programme which describes it.


Property: prog:has_sidebar_event

programme includes sidebar eventIndicates that an Event is part of the specified programme, but is not part of the normal grid and should be listed separately. Evening events, for example, may be included in this way. Other users include all-day events such as 'exhibition in main hall', for which you do not want to use up 'real-estate' in a grid-display of this programme.


Property: prog:has_streamed_event

programme includes streamed eventIndicates that an Event is part of the specified programme, and should appear in any relevant 'streams' based on its subject or location. If it matches no things for which the programme is prog:streamed_by_location, prog:streamed_by_parent_event or prog:streamed_by_subject then a tool may choose to report this as broken data.


Property: prog:has_timeslot

programme has timeslotIndicates that a TimeSlot is part of the specified programme.


Property: prog:realises

event realises activityRelates a concrete event:Event to the prog:Activity that it is a realisation of. For example this would relate the training course on Thursday to the prog:Activity of the laser safety lecure. All realisations of the laser safety lecture have generally the same content, although details may vary. It is not expected that a normal attendee will attend more than one realisation of an Activity, although certainly not precluded at the level of detail we're working with here.


Property: prog:streamed_by_location

programme has a stream for locationIndicates that one of the streams in this visualisation is events with a event:place relating them to the geo:SpatialThing indicated. This is the most common way an programme is designed.


Property: prog:streamed_by_parent_event

programme has a stream for sub-events ofIndicates that one of the streams in this visualisation is events that are event:sub_event of the event:Event indicated. This can be used to show several workshops in an event. This should only apply to things which are immediately stated explicitly as event:sub_event, it is assumed that the consumer will not treat this property as transitive, unless they are doing something weird or clever.


Property: prog:streamed_by_subject

programme has a stream for subjectIndicates that one of the streams in this visualisation is events with a dcterms:subject relating them to the skos:Concept indicated.