-
-
-
-
-
-
-
-
-
-
-
- Summary
- - -- The Core Public Event Vocabulary provides a minimum set of classes and properties for - describing a public event , i.e. something that happens at a particular place and time, -organised by one or more agents for a particular purpose, and is of interest to a general - audience. This definition excludes natural events such as earthquakes and volcanic -eruptions. -
- -
-
-
-
-
-
- Status of this document
- -- This Core Vocabulary has the status of Semic Recommendation published on 2023-05-15. -
- -
-
-
- Overview
-
-
-
-
-
-
-
-
-
- This document describes the usage of the following entities for a correct usage of the Core Vocabulary:
-
- |
- Address |
- Agent |
- ContactPoint |
- Participation |
- Public Event |
- Temporal Entity |
-
-
- 
-
-
-
-
-
-
-
- Entities
-
-
-
- Address
-
-
-
- -
-
- Definition
- A spatial object that in a human-readable way identifies a fixed location. - -
- Usage
- An "address representation" as conceptually defined by the INSPIRE Address Representation data type: "Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.".
-
-The representation of Addresses varies widely from one country's postal system to another. Even within countries, there are almost always examples of Addresses that do not conform to the stated national standard. However, ISO 19160-1 provides a method through which different Addresses can be converted from one conceptual model to another. -
-This specification was heavily based on the INSPIRE Address Representation data type. It is noteworthy that if an Address is provided using the detailed breakdown suggested by the properties for this class, then it will be INSPIRE-conformant. To this very granular set of properties, we add two further properties: -
-- full address (the complete address as a formatted string)
-- addressID (a unique identifier for the address). -
-The first of these allows publishers to simply provide the complete Address as one string, with or without formatting. This is analogous to vCard's label property. -
-The addressID is part of the INSPIRE guidelines and provides a hook that can be used to link the Address to an alternative representation, such as vCard or OASIS xAL. -
-This class belongs to Core Location Vocabulary
-
-
- - Properties - -
- For this entity the following properties are defined: - address area, - address ID, - administrative unit level 1, - administrative unit level 2, - full address, - locator designator, - locator name, - post code, - post name, - post office box, - thoroughfare. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- address area
-
- |
- - - - Text - - - | -The name of a geographic area that groups Addresses. | -This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit. | -- |
-
-
- address ID
-
- |
- - - - Literal - - - | -A globally unique identifier for each instance of an Address. | -The concept of adding a globally unique identifier for each instance of an address is a crucial part of the INSPIRE data spec. A number of EU countries have already implemented an ID (a UUID) in their Address Register/gazetteer, among them Denmark. OASIS xAL also includes an address identifier. It is the address Identifier that allows an address to be represented in a format other than INSPIRE whilst remaining conformant to the Core Vocabulary.
- -The INSPIRE method of representing addresses is very detailed, designed primarily for use in databases of addresses. Whilst data that is published in full conformance with the INSPIRE data structure can be made available using the Core Location Vocabulary the reverse is not true since the Core Vocabulary allows much greater flexibility. - -Many datasets that include address data as one piece of information about something else are likely to have that data in simpler formats. These might be tailored to the specific need of the dataset, follow a national norm, or make use of a standard like vCard. - -To provide maximum flexibility in the Core Vocabulary, whilst remaining interoperable with INSPIRE Address Guidelines (which EU Member States are obliged to use), the Core Location Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID. - - |
- - |
-
-
- administrative unit level 1
-
- |
- - - - Text - - - | -The name of the uppermost level of the address, almost always a country. | -Best practice is to use the ISO 3166-1 code but if this is inappropriate for the context, country names should be provided in a consistent manner to reduce ambiguity. For example, either write 'France' or 'FRA' consistently throughout the dataset and avoid mixing the two. The Country controlled vocabulary from the Publications Office can be reused for this. | -- |
-
-
- administrative unit level 2
-
- |
- - - - Text - - - | -The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities. | -Values could be a region or province, more granular than level 1. | -- |
-
-
- full address
-
- |
- - - - Text - - - | -The complete address written as a string. | -Use of this property is recommended as it will not suffer any misunderstandings that might arise through the breaking up of an address into its component parts. This property is analogous to vCard's label property but with two important differences: (1) formatting is not assumed so that, unlike vCard label, it may not be suitable to print this on an address label, (2) vCard's label property has a domain of vCard Address; the fullAddress property has no such restriction. An example of a full address is "Champ de Mars, 5 Avenue Anatole France, 75007 Paris, France". | -- |
-
-
- locator designator
-
- |
- - - - Literal - - - | -A number or sequence of characters that uniquely identifies the locator within the relevant scope. | -In simpler terms, this is the building number, apartment number, etc. For an address such as "Flat 3, 17 Bridge Street", the locator is "flat 3, 17". - - | -- |
-
-
- locator name
-
- |
- - - - Text - - - | -Proper noun(s) applied to the real world entity identified by the locator. | -The locator name could be the name of the property or complex, of the building or part of the building, or it could be the name of a room inside a building.
- -The key difference between a locator designator and a locator name is that the latter is a proper name and is unlikely to include digits. For example, "Shumann, Berlaymont" is a meeting room within the European Commission headquarters for which locator name is more appropriate than locator. |
- - |
-
-
- post code
-
- |
- - - - Literal - - - | -The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points. | -Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example "75000". | -- |
-
-
- post name
-
- |
- - - - Text - - - | -A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points. | -Usually a city, for example "Paris". | -- |
-
-
- post office box
-
- |
- - - - Literal - - - | -A location designator for a postal delivery point at a post office, usually a number. | -INSPIRE's name for this is "postalDeliveryIdentifier" for which it uses the locator designator property with a type attribute of that name. This vocabulary separates out the Post Office Box for greater independence of technology. An example post office box number is "9383". | -- |
-
-
- thoroughfare
-
- |
- - - - Text - - - | -The name of a passage or way through from one location to another. | -A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, "Avenue des Champs-Élysées". | -- |
-
-
- Agent
-
-
-
- -
-
- Definition
- Entity that is able to carry out action - -
- Usage
- In compliance with the description from FOAF, an Agent is considered as any entity that is able to carry out actions. The Agent class acts as a generic element which can be further specified by implementers for their usages, for example by defining the Person class from the Core Person Vocabulary or Organization from W3C's Organization Ontology as subclasses of Agent. This Person or Organization can then issue a certain Requirement or be concerned by an Evidence provided. - - -
- Properties - -
- For this entity the following properties are defined: - address, - name, - participates, - type. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- address
-
- |
- - - - Address - - - | -Associates any Resource with the corresponding Address. | -- | - |
-
-
- name
-
- |
- - - - Text - - - | -The noun given to the Agent. | -- | - |
-
-
- participates
-
- |
- - - - Participation - - - | -The participation in which an Agent is involved. | -- | - |
-
-
- type
-
- |
- - - - Code - - - | -A classification assigned to an Agent. | -- | - |
-
-
- ContactPoint
-
-
-
- -
-
- Definition
- Information (e.g. e-mail address, telephone number) of a person or department through which the user can get in touch with. - -
- Usage
- The Core Public Organization Vocabulary defines properties for telephone number, e-mail address and opening hours although it is noteworthy that the class is based on schema.org's ContactPoint class (http://schema.org/ContactPoint) that has additional properties that some implementations may find useful. - - -
- Properties - -
- For this entity the following properties are defined: - availability restriction, - contact page, - has email, - has telephone, - opening hours. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- availability restriction
-
- |
- - - - Temporal Entity - - - | -The time during which the Contact Point is not available. | -- | - |
-
-
- contact page
-
- |
- - - - Document - - - | -A web page that could be used to reach out the Contact Point. | -- | - |
-
-
- has email
-
- |
- - - - Literal - - - | -An electronic address through which the Contact Point can be contacted. | -- | - |
-
-
- has telephone
-
- |
- - - - Literal - - - | -A telephone number through which the Contact Point can be contacted. | -- | - |
-
-
- opening hours
-
- |
- - - - Temporal Entity - - - | -The time at which the Contact Point is normally available. | -- | - |
-
-
- Participation
-
-
-
- -
-
- Definition
- The Participation class allows to define roles within a certain context. - - -
- Properties - -
- For this entity the following properties are defined: - description, - has participant, - has time, - identifier, - role. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- description
-
- |
- - - - Text - - - | -A textual explanation of the Participation. | -- | - |
-
-
- has participant
-
- |
- - - - Agent - - - | -The Agent involved in the Participation. | -- | - |
-
-
- has time
-
- |
- - - - Temporal Entity - - - | -The association of a temporal entity (instant or interval) to any thing. | -- | - |
-
-
- identifier
-
- |
- - - - Literal - - - | -The unambiguous structured reference for the Participation. | -- | - |
-
-
- role
-
- |
- - - - Code - - - | -The function of an Agent within a Participation. | -- | - |
-
-
- Public Event
-
-
-
- -
-
- Definition
- Something that happens at a particular place and time, -organised by one or more agents for a particular purpose, and is of interest to a general - audience. This definition excludes natural events such as earthquakes and volcanic -eruptions. - - -
- Properties - -
- For this entity the following properties are defined: - accessibility, - address, - audience, - contact point, - description, - event number, - event type, - format, - has next event, - has participation, - has previous event, - has time, - homepage, - identifier, - language, - parent event, - registration page, - sub event, - title, - topic. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- accessibility
-
- |
- - - - Text - - - | -Information about how the Public Event can be approached, reached or entered, in particular for people with special needs. | -This property may be provided in multiple languages with multiple instances of the accessibility property. | -- |
-
-
- address
-
- |
- - - - Address - - - | -Associates any Resource with the corresponding Address. | -Asserting the address relationship implies that the - Resource has an Address. | -- |
-
-
- audience
-
- |
- - - - Code - - - | -The target group of people for whom the Public Event is created. | -- | - |
-
-
- contact point
-
- |
- - - - ContactPoint - - - | -The main contact information of the resource. | -Usually a phone number and e-mail address. Other contact methods may be included, including online contact information, but this is conceptually distinct from the organization's homepage that may or may not provide contact information. | -- |
-
-
- description
-
- |
- - - - Text - - - | -A textual explanation of the Pulblic Event. | -Descriptions may be provided in multiple languages with multiple instances of the description property. | -- |
-
-
- event number
-
- |
- - - - Text - - - | -The sequence position of the Public Event. | -Examples could be the ''4th" or "2022". | -- |
-
-
- event type
-
- |
- - - - Code - - - | -The nature or genre of the Public Event. | -Examples include festivals, conferences, city council meetings and public consultations. The eventType property links the event to a SKOS Concept that provides a classification. - -An existing classification from Publications Office could be used, see Public Event Type. | -- |
-
-
- format
-
- |
- - - - Code - - - | -A plan of organisation or arrangement of the Public Event. | -Examples include conference call, physical meeting or hybrid. | -- |
-
-
- has next event
-
- |
- - - - Public Event - - - | -The Public Event that comes after this one. | -- | - |
-
-
- has participation
-
- |
- - - - Participation - - - | -The way how a resource is organized. | -- | - |
-
-
- has previous event
-
- |
- - - - Public Event - - - | -The Public Event that comes before this one. | -- | - |
-
-
- has time
-
- |
- - - - Temporal Entity - - - | -The association of a temporal entity (instant or interval) to any thing. | -This property can be used to specify date or time of a Public Event via the Temporal Entity class, see the date time example from the Time ontology. | -- |
-
-
- homepage
-
- |
- - - - Document - - - | -The website of the Public Event. | -The value of this property is a URL. | -- |
-
-
- identifier
-
- |
- - - - Literal - - - | -The unambiguous structured reference for the Public Event. | -- | - |
-
-
- language
-
- |
- - - - LinguisticSystem - - - | -The language in which the Public Event is given. | -The recommended controlled vocabularies for this property is the Language Authority Table of the Publications Office. | -- |
-
-
- parent event
-
- |
- - - - Public Event - - - | -A relation to another Public Event that encompasses it. | -- | - |
-
-
- registration page
-
- |
- - - - Document - - - | -A web page that provides means to attend the Public Event. | -- | - |
-
-
- sub event
-
- |
- - - - Public Event - - - | -A relation towards another Public Event that belong to it. | -- | - |
-
-
- title
-
- |
- - - - Text - - - | -The name given to the Public Event. | -Titles may be provided in multiple languages with multiple instances of the title property. | -- |
-
-
- topic
-
- |
- - - - Code - - - | -The subject of the Public Event. | -Examples include culture, sport or tourism. | -- |
-
-
-
-
-
-
-
- Temporal Entity
-
-
-
- -
-
- Definition
- A temporal interval or instant. - - -
- Properties - -
- For this entity the following properties are defined: - description, - frequency. - -
-
-
-
-
-
- | Property | -Expected Range | -Definition | -Usage | -Codelist | -
|---|---|---|---|---|
-
-
- description
-
- |
- - - - Text - - - | -A textual representation of the Temporal Entity. | -- | - |
-
-
- frequency
-
- |
- - - - Code - - - | -The recurrence of an instant or period. | -It is recommended to use the frequency from an existing vocabulary like the Frequency from the Publications Office. | -- |
-
-
- Changelog w.r.t. previous version
- (non-normative) - --This is the first major release of Core Public Event that includes the main class Public Event with the reuse of existing classes from other vocabularies such as locn:Address, cv:ContactPoint and cpsv:Participation. -
- -
-
-
- UML representation
- (non-normative) - -The UML representation from which this Core Vocabulary has been build is available here. -
- -
-
-
- RDF representation
- (non-normative) - -A reusable RDF representation (in turtle) for this Core Vocabulary is retrievable here.
-
- This RDF file contains only the terminology for which the URI is minted in the Core Vocabularies domain http://data.europa.eu/m8g.
- Terms that are mapped on an existing URI (hence reused from other vocabularies) are not included.
-
-
-
- JSON-LD context
- (non-normative) - -A reusable JSON-LD context definition for this Core Vocabulary is retrievable here.
- -
-
-
-
-
- SHACL template
- (non-normative) - -A reusable SHACL template for this Core Vocabulary is retrievable here.
- -