The Event Programme Vocabulary

IRI:
http://purl.org/prog/
Authors :
http://id.ecs.soton.ac.uk/person/1248
http://id.ecs.soton.ac.uk/person/1269
Publisher :
http://id.southampton.ac.uk/
Other visualisation :
Ontology source - WebVowl

Table of Content

  1. Classes
  2. Named Individuals
  3. Annotation Properties
  4. Namespace Declarations

Classes

Activityc back to ToC or Class ToC

IRI: http://purl.org/prog/Activity

is defined by
http://purl.org/prog/
This 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.

Programmec back to ToC or Class ToC

IRI: http://purl.org/prog/Programme

is defined by
http://purl.org/prog/
A 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.

TimeSlotc back to ToC or Class ToC

IRI: http://purl.org/prog/TimeSlot

is defined by
http://purl.org/prog/
This 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.

Named Individuals

1248ni back to ToC or Named Individual ToC

IRI: http://id.ecs.soton.ac.uk/person/1248

belongs to
personc

1269ni back to ToC or Named Individual ToC

IRI: http://id.ecs.soton.ac.uk/person/1269

belongs to
personc

http://id.southampton.ac.uk/ni back to ToC or Named Individual ToC

IRI: http://id.southampton.ac.uk/

belongs to
organizationc

Annotation Properties

nameap back to ToC or Annotation Property ToC

IRI: http://xmlns.com/foaf/0.1/name

Namespace Declarations back to ToC

default namespace
http://purl.org/prog/
foaf
http://xmlns.com/foaf/0.1/
owl
http://www.w3.org/2002/07/owl#
person
http://id.ecs.soton.ac.uk/person/
rdf
http://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfs
http://www.w3.org/2000/01/rdf-schema#
terms
http://purl.org/dc/terms/
xsd
http://www.w3.org/2001/XMLSchema#

This HTML document was obtained by processing the OWL ontology source code through LODE, Live OWL Documentation Environment, developed by Silvio Peroni .