Summary
The model presented below is an application profile of Core Public Organization Vocabulary (CPOV), built in the context of the ICEG thematic working group regrouping experts from the federal and regional level as well as communities. It was designed through a series of workshops and a final open consultation.
The objective was to standardize the terms defined for public organizations at regional and federal level, starting from CPOV. It serves the purpose to make data accessible as linked open data and to define standard interfaces (APIs) to simplify collaboration and integration of the various services and tools.
The Core Public Organization Vocabulary is designed to support the exchange of basic information about public organizations. Using the vocabulary – with sector- or country-specific information – will make it easier for institutions publishing data about public organizations.
The Core Public Organization Vocabulary is designed to describe the organization itself. Whilst the vocabulary may support links to staff members other resources such as relevant legislation, policies and jurisdictional coverage, it will not describe those resources in detail.
As the name suggests, the vocabulary is not concerned with features associated with commercial entities such as shareholdings and ownership.
Whenever possible, the CPOV will reuse existing vocabularies to avoid defining new terms. As such, it reuses schema, org, foaf, core location, core person, amongst others.
Please find below the namespaces used in the model:
Prefix | Namespace IRI | Source |
---|---|---|
dcat |
http://www.w3.org/ns/dcat# |
[[VOCAB-DCAT]] |
dct |
http://purl.org/dc/terms/ |
[[DCTERMS]] |
foaf |
http://xmlns.com/foaf/0.1/ |
[[FOAF]] |
schema |
http://schema.org/ |
[[schema-org]] |
rdf |
http://www.w3.org/1999/02/22-rdf-syntax-ns# |
[[RDF-SYNTAX-GRAMMAR]] |
rdfs |
http://www.w3.org/2000/01/rdf-schema# |
[[RDF-SCHEMA]] |
vcard |
http://www.w3.org/2006/vcard/ns# |
[[VCARD-RDF]] |
xsd |
http://www.w3.org/2001/XMLSchema# |
[[XMLSCHEMA11-2]] |
adms |
http://www.w3.org/ns/adms# |
[[VOCAB-ADMS]] |
skos |
http://www.w3.org/2004/02/skos/core# |
[[SKOS-REFERENCE]] |
locn |
http://www.w3.org/ns/locn# |
[[LOCN]] |
Status of this document
This model has the status of Working Draft published on 2021-12-22.
Conformance
To be defined
Overview
This document describes the usage of the following entities for a correct usage of the data model:
|
Address |
Administrative Territorial Units |
Change Event |
Contact Point |
Foundation Event |
Geometry |
Identifier |
Image Object |
Opening Hours Specification |
Organization |
Organizational Unit |
Person |
Post |
Public Organization |
Reference Framework |
Role |
Site |
Entities
Address
- Description
- A spatial object that in a human-readable way identifies a fixed location of a property.
- 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. At the time of publication, work is progressing on ISO 19160-1 that defines 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 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.
- Properties
- For this entity the following properties are defined: address area, address ID, administrative unit level 1 (country), administrative unit level 2 (country/region/state), full address, locator designator, locator name, post code, post name (city), post office box, thoroughfare.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
address area
|
Text | 0..1 | The name or names of a geographic area or locality that groups a number of addressable objects for addressing purposes, without being an administrative unit. | This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. | |
address ID
|
String | 0..1 | 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 Location Core 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 Location Core Vocabulary provides the extra property of full address and makes use of INSPIRE's addressID. |
|
administrative unit level 1 (country)
|
Code | 0..1 | The name or names of a unit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance. Level 1 refers to the uppermost administrative unit for 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 (country/region/state)
|
Text | 0..1 | The name or names of a unit of administration where a Member State has and/or exercises jurisdictional rights, for local, regional and national governance. Level 2 referst to the region of the address, usually a county, state or other such area that typically encompasses several localities. | Some recommended codelists from the EU Publications Office include: Administrative Territorial Units (ATU), NUTS and Local Administrative Units (LAU). The first arrondissement of Paris is for example expressed as "http://publications.europa.eu/resource/authority/atu/FRA_AR_PAR01" in the ATU controlled vocabulary. | |
full address
|
Text | 0..1 | The complete address written as a formatted 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
|
String | 0..1 | A number or a sequence of characters which allows a user or an application to interpret, parse and format the locator within the relevant scope. A locator may include more locator designators. | 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 | 0..1 | 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 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
|
String | 0..1 | The post/zip code of an address. (INSPIRE's definition is "A 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 (city)
|
Text | 0..1 | The key postal division of the address, usually the city. (INSPIRE's definition is "One or more names created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.) For example, "Paris". | ||
post office box
|
String | 0..1 | The Post Office Box 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 | 0..1 | An address component that represents the name or names of a passage or way through from one location to another. A thoroughfare is not necessarily a road, it might be a waterway or some other feature. | For example, "Avenue des Champs-Élysées". |
Administrative Territorial Units
- Description
- Lists of codes that represent the administrative territorial units of the EU Member States, based on national official / legal information and the ISO 3166-2 standard.
- Properties
- For this entity the following properties are defined: geometry.
Change Event
- Description
- Represents an event which resulted in a major change to an Organization such as a merger or complete restructuring. It is intended for situations where the resulting Organization is sufficiently distinct from the original Organizations that it has a distinct identity and distinct URI.
- Properties
- For this entity the following properties are defined: description, ended at time, has formal framework, original organization, resulting organization, started at time.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
description
|
Text | 0..1 | A textual description of the event. | ||
ended at time
|
DateTime | 0..1 | The time at which the Change Event ended. | ||
has formal framework
|
Reference Framework | 0..* | The property hasFormalFramework links a Change Event or Foundation Event to a piece of legislation or a policy document that prompted the change. | ||
original organization
|
Organization | 0..* | The original organization property links a Change Event to the Organization that existed before the change. Although the Foundation Event class is defined as a subclass of Change Event, it is inappropriate to use the original organization property with the Foundation Event class. | ||
resulting organization
|
Organization | 0..* | This property links a Change Event or a Foundation Event to the Organization that resulted from it. | ||
started at time
|
DateTime | 0..1 | The time at which the Change Event started. | If only one time is known and it is unclear whether it represents the start or end time, use only the startedAtTime property. |
Contact Point
- Description
- A class representing a point of contact.
- 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, has email, has telephone, opening hours, website.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
availability restriction
|
Opening Hours Specification | 0..1 | The availability restriction property links a Contact Point to details of specific details of its opening hours that override the general case. | ||
has email
|
Literal | 0..1 | A property through which an e-mail address for the Public Organization, or a representative of it, can be contacted. | ||
has telephone
|
Literal | 0..1 | A property through which a phone number for the Public Organization, or a representative of it, can be contacted. | ||
opening hours
|
Literal | 0..1 | The value of this property is structured text that gives the hours at which the contact point is normally available. | Days are specified using two-letter combinations: Mo, Tu, We, Th, Fr, Sa, Su. For example, if the contact point is open Monday-Friday, 9 -5, the value of the openingHours property would be Mo-Fr 09:00-17:00. If the Contact Point is only available on Tuesday and Thursday between 6 and 8pm, the value would be Tu,Th 16:00-20:00. | |
website
|
URL | 0..1 | A WebSite is a set of related web pages and other items typically served from a single web domain and accessible via URLs. |
Foundation Event
- Description
- Public Organizations are formed and changed in response to events. This may be the result of new legislation, new policies, taking on new obligations etc. The CPOV captures this in its Change Event class but recognises the specific case of an Organization's foundation as being sufficiently distinct to require a subclass of Change Event.
- Subclass of
- Change Event
- Properties
- No properties have been defined for this entity.
Geometry
- Description
- The Geometry class provides the means to identify a Location as a point, line, polygon, etc. expressed using coordinates in some coordinate reference system.
- Usage
- This class defines the notion of "geometry" at the conceptual level, and it shall be encoded by using different formats (see usage note of the locn:geometry property). We also refer to the Examples section of this specification for a number of different geometry examples expressed in different formats.
- Properties
- For this entity the following properties are defined: coordinates, crs, geometry type, gml, latitude, longitude, wkt.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
coordinates
|
String | 0..1 | The coordinate list. | ||
crs
|
URI | 0..1 | An identifier for the coordinate reference system. | ||
geometry type
|
Code | 0..1 | The geometry type, e.g. point, line or polygon. | ||
gml
|
Literal | 0..1 | The geometry written in Geography Markup Language. | Use "http://www.opengis.net/ont/geosparql#gmlLiteral" as type for the literal. | |
latitude
|
String | 0..1 | The latitude. | ||
longitude
|
String | 0..1 | The longitude. | ||
wkt
|
Literal | 0..1 | The well-known text representation string describing the point, line or polygon. | Use "http://www.opengis.net/ont/geosparql#wktLiteral" as type for the literal. |
Identifier
- Description
- The Identifier class represents any identifier issued by any authority, whether a government agency or not. It captures the identifier itself, the type of identifier, and details of the issuing authority, the date on which the identifier was issued.
- Usage
- The Identifier class is based on the UN/CEFACT class of the same name and is defined under the ADMS namespace.
- Properties
- For this entity the following properties are defined: date of issue, identifier, issuing authority name, issuing authority URI, scheme name, scheme URI.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
date of issue
|
DateTime | 0..1 | The date on which the Identifier was assigned. | ||
identifier
|
Literal | 1 | The value of this property is the Identifier itself. | Example: "abc-12345-de"^^<https://belgium.be/scheme/nationalIDnumber>. | |
issuing authority name
|
Text | 0..1 | The name of the agency responsible for issuing the Identifier. | Example: "Federal Public Service Interior"@en. | |
issuing authority URI
|
URI | 0..1 | The URI of the issuing authority. | ||
scheme name
|
Text | 0..1 | Name of the scheme used to construct the identifier. | ||
scheme URI
|
URI | 0..1 | URI of the scheme used to construct the identifier. |
Image Object
- Description
- An image object can be used as logo to describe / represent a public organization.
- Properties
- No properties have been defined for this entity.
Opening Hours Specification
- Description
- The Opening Hours Specification class can be used to provide details of exceptional circumstances, such as being closed on public holidays.
- Usage
- The Core Public Organization Vocabulary makes full use of schema.org's openingHours property to provide details of regular operations. The Opening Hours Specification class can be used to provide details of exceptional circumstances, such as being closed on public holidays. Note that the property schema:opens is not used, therefore the contact point is closed. More specific closures can be indicated by including the schema:validFrom and schema:validThrough properties.
- Properties
- For this entity the following properties are defined: day of week, valid from, valid through.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
day of week
|
URI | 1 | The day of the week for which these opening hours are valid. | ||
valid from
|
DateTime | 1 | The date when the Opening Hours Specification becomes valid. | ||
valid through
|
DateTime | 1 | The date after when the Opening Hours Specification is not valid. |
Organization
- Description
- Represents a collection of people organized together into a community or other social, commercial or political structure. The group has some common purpose or reason for existence which goes beyond the set of people belonging to it and can act as an Agent. Organizations are often decomposable into hierarchical structures.
- Properties
- For this entity the following properties are defined: alternative label, certification, changed by, contact point, description, ex officio striking off, has member, has member, has post, has site, has sub organization, has unit, identifier, links to database, logo, member of, next, preferred label, prev, resulted from, start date of this data, status, sub organization of.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
alternative label
|
Text | 0..1 | In line with ORG and SKOS itself, an organization may have any number of alternative or informal names, irrespective of language. | ||
certification
|
Code | 0..* | Certifications, licences or registrations that are of importance for third parties or whose publication is mandatory | ||
changed by
|
Change Event | 0..* | The changed by organization property links an Organization to the Change Event that changed the Organization. | ||
contact point
|
Contact Point | 0..* | The contact point property links to a Contact Point that provides contact information, in particular 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 | 0..1 | Statement or account giving the characteristics of the company. | ||
ex officio striking off
|
Code | 0..1 | Ex officio striking off of the entity for failure to submit their financial statements | Companies which have not complied with the obligation to deposit their annual accounts with the National Bank of Belgium for at least three consecutive accounting years can be struck off ex officio | |
has member
|
Organization | 0..* | One Organization may be a member of another without being a sub organization, i.e. they are independent entities. | The memberOf and hasMember properties are very simple and don't support statements describing the nature of the membership. The W3C Organization Ontology provides both this simple method and a more sophisticated model25 that does make it possible to, for example, provide information about the period of time in which one Organization was a member of another, the level of membership etc. That more sophisticated model should be used where necessary and may be used in addition to the simple memberOf/hasMember properties. | |
has member
|
Person | 0..* | Indicates that Person is a member of the Organization with no indication of the nature of that membership or the role played | ||
has post
|
Post | 0..* | Indicates the post that belongs to the Organization. | ||
has site
|
Site | 1..* | Indicates a site at which the Organization has some presence even if only indirect (e.g. virtual office or a professional service which is acting as the registered address for a company). | ||
has sub organization
|
Organization | 0..* | Public Organizations are often large and complex and may be a collection of smaller Organizations, each of which has a specific identity that may be legally defined. The hasSubOrganization and subOrganizationOf properties express the relationships between Organizations in a hierarchical structure. | ||
has unit
|
Organizational Unit | 0..* | The properties hasUnit and unitOf are used to link to operational departments within an Organization that may not generally exist in their own right. | Organizations typically comprise many departments, units, teams etc. Each of these is modelled in the CPOV as a unit that is linked from the parent Organization with hasUnit and to the parent with unitOf. | |
identifier
|
Identifier | 0..1 | Many organizations are referred to by an acronym or some other identifier | ||
links to database
|
Text | 0..* | Links to databases containing data not recorded in the CBE/KBO | ||
logo
|
Image Object | 0..* | A property to link an Organization to its logo. | The value of this property can simply be the URL of the logo but it is better for developers if it links to an object that provides the URL of the image and essential metadata about it, notably its dimensions. | |
member of
|
Organization | 0..* | One Organization may be a member of another without being a sub organization, i.e. they are independent entities. | The memberOf and hasMember properties are very simple and don't support statements describing the nature of the membership. The W3C Organization Ontology provides both this simple method and a more sophisticated model25 that does make it possible to, for example, provide information about the period of time in which one Organization was a member of another, the level of membership etc. That more sophisticated model should be used where necessary and may be used in addition to the simple memberOf/hasMember properties. | |
next
|
Organization | 0..* | In some cases, it is necessary to be able to create an ordered sequence of organizations that precede and succeed each other. To support this, the CPOV includes the well-known relationships of previous and next to allow such sequences to be captured and computed. | ||
preferred label
|
Text | 1 | As defined in the ORG Ontology, a preferred label is used to provide the primary, legally recognised name of the organization | An organization may only have one such name in any given language. Primary names may be provided in multiple languages with multiple instances of the preferred label property. | |
prev
|
Organization | 0..* | In some cases, it is necessary to be able to create an ordered sequence of organizations that precede and succeed each other. To support this, the CPOV includes the well-known relationships of previous and next to allow such sequences to be captured and computed. | ||
resulted from
|
Change Event | 0..* | This property link an Organization to the Change Event it resulted from. | ||
start date of this data
|
DateTime | 0..1 | The date on which the Organization-related information was provided. | ||
status
|
Code | 0..1 | Entity status, e.g. active, closed, cancelled, identified legal creation, stopped | ||
sub organization of
|
Organization | 0..* | Public Organizations are often large and complex and may be a collection of smaller Organizations, each of which has a specific identity that may be legally defined. The hasSubOrganization and subOrganizationOf properties express the relationships between Organizations in a hierarchical structure. |
Organizational Unit
- Description
- An Organization such as a department or support unit which is part of some larger Organization and only has full recognition within the context of that Organization. In particular the unit would not be regarded as a legal entity in its own right.
- Usage
- Units can be large and complex, containing other Units. An alternative name is "Department". An Organizational Unit is in contrast to a suborganization that, although part of the larger Organization, may be legally distinct or otherwise enjoy a degree of autonomy.
- Subclass of
- Organization
- Properties
- For this entity the following properties are defined: unit of.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
unit of
|
Organization | 0..* | The properties hasUnit and unitOf are used to link to operational departments within an Organization that may not generally exist in their own right. | Organizations typically comprise many departments, units, teams etc. Each of these is modelled in the CPOV as a unit that is linked from the parent Organization with hasUnit and to the parent with unitOf. |
Person
- Description
- An individual person who may be dead or alive, but not imaginary.
- Usage
- The fact that a person in the context of Core Person Vocabulary cannot be imaginary makes person:Person a subclass of both foaf:Person and schema:Person which both cover imaginary characters as well as real people. The Person Class is a subclass of the more general 'Agent' class that encompasses organizations, legal entities, groups etc. - any entity that is able to carry out actions.
- Subclass of
- Person
- Properties
- For this entity the following properties are defined: alternative name, birth name, date of birth, date of death, family name (surname), full name, given name (forename), holds, identifier, member of, patronymic name, registered address , title.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
alternative name
|
Text | 0..1 | Any name by which an individual is known other than their full name. | Many individuals use a short form of their name, a 'middle' name as a 'first' name or a professional name. For example, the British politician and former UN High Representative for Bosnia and Herzegovina, Jeremy John Durham Ashdown, Baron Ashdown of Norton-sub-Hamdon, is usually referred to simply as 'Paddy Ashdown' or 'Lord Ashdown.' It is not the role of the alternative name property to record nick names, pet names or other 'familiar names' that will be of no consequence in public sector data exchange. Furthermore, some individuals have more than one legal name in which case the full name property should be used multiple times. Alternative name gives a means of recording names by which an individual is generally known, or professionally known, even though such names are no more than secondary from a legal point of view. | |
birth name
|
Text | 0..1 | Full name of the Person given upon their birth. | All data associated with an individual are subject to change. Names can change for a variety of reasons, either formally or informally, and new information may come to light that means that a correction or clarification can be made to an existing record. Birth names tend to be persistent however and for this reason they are recorded by some public sector information systems. There is no granularity for birth name - the full name should be recorded in a single field. | |
date of birth
|
DateTime | 0..1 | The day on which the Person was born. | ||
date of death
|
DateTime | 0..1 | The day on which the Person died. | ||
family name (surname)
|
Text | 1 | A family name is usually shared by members of a family. | This attribute also carries prefixes or suffixes which are part of the family name, e.g. "de Boer", "van de Putte", "von und zu Orlow". Multiple family names, such as are commonly found in Hispanic countries, are recorded in the single family name property so that, for example, Miguel de Cervantes Saavedra's family name would be recorded as "de Cervantes Saavedra". | |
full name
|
Text | 1 | The full name contains the complete name of a person as one string. | In addition to the content of given name, family name and, in some systems, patronymic name, this can carry additional parts of a person's name such as titles, middle names or suffixes like "the third" or names which are neither a given nor a family name. The full name is the most reliable label for an individual and as such its use is strongly encouraged, irrespective of whether that name is broken down using the more granular elements. It is anticipated that some systems will only provide or process the full name of a person. Where an individual has more than one full legal name (a relatively rare but not unknown phenomenon), the full name property can be used more than once. In this case, however, the granular name elements should not be used since the intention is that these provide a breakdown of the full name and it will not be clear of which full name this is true. Note that the vocabulary provides an alternative name property. This allows name(s) to be recorded that have no legal status but that nevertheless are the names by which an individual is generally known. A name usually sticks with a person for a long time period. In some European countries a name may only be changed according to certain laws and life events, e.g. marriage. The name denominates a natural person even if he/she changes their address. Documents like birth certificate or diploma usually don't carry an address but always the name. Thus the name is one of the core attributes. However it is not sufficient to identify a person since there are combinations of very common names like Smith in the UK, Meier in Germany, or Li in China. |
|
given name (forename)
|
Text | 1 | A given name, or multiple given names, are the denominator(s) that identify an individual within a family. | These are given to a person by his or her parents at birth or may be legally recognised as 'given names' through a formal process. All given names are ordered in one property so that, for example, the given name for Johann Sebastian Bach is "Johann Sebastian". | |
holds
|
Post | 1..* | Indicates a Post held by a Person. | ||
identifier
|
Identifier | 0..1 | The identifier relation is used to link a Person to any formally issued Identifier for that Person. | ||
member of
|
Organization | 0..* | Indicates a Person who is a member of the subject Organization | ||
patronymic name
|
Text | 0..1 | Name based on the given name of the Person's father. | Patronymic names are important in some countries. Iceland does not have a concept of 'family name' in the way that many other European countries do, for example. Erik Magnusson and Erika Magnusdottir are siblings, both offspring of Magnus, irrespective of his patronymic name. In Bulgaria and Russia, patronymic names are in everyday usage, for example, the "Sergeyevich" in "Mikhail Sergeyevich Gorbachev". Note that patronymic names refer to a father's given name, not the family name inherited from the mother and father as is the case in countries such as Spain and Portugal. Again referring to the example of Miguel de Cervantes Saavedra's, the patronymic name element would be unused. | |
registered address
|
Address | 0..1 | The registered address of the Person. | ||
title
|
Text | 0..1 | The approriate values for title are not formally constrained, and will vary across community and context. Values such as 'Mr', 'Mrs', 'Ms', 'Dr' etc. are expected. |
Post
- Description
- A Post represents some position within an organization that exists independently of the person or persons filling it. Posts may be used to represent situations where a person is a member of an organization ex officio
- Properties
- For this entity the following properties are defined: post in, role.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
post in
|
Organization | 0..* | Indicates the Organization whose post belongs to. | ||
role
|
Role | 1..* | Indicates the Role that the Person plays in a Membership relationship with an Organization. Can also be used on a org:Post to indicate the role that any holder of the Post plays. |
Public Organization
- Description
- Any Organization that is defined as being part of the public sector by a legal framework at any level.
- Usage
The Public Organization class represents the organization. One organization may comprise several sub-organizations and any organization may have one or more organizational units. Each of these is described using the same properties and relationships.
This definition is consistent with the more detailed definition of a "public sector body" as given in the PSI Directive: "the State, regional or local authorities, bodies governed by public law and associations formed by one or several such authorities or one or several such bodies governed by public law". It further defines a body governed by public law as any body "(a) established for the specific purpose of meeting needs in the general interest, not having an industrial or commercial character; and (b) having legal personality; and (c) financed, for the most part by the State, or regional or local authorities, or other bodies governed by public law; or subject to management supervision by those bodies; or having an administrative, managerial or supervisory board, more than half of whose members are appointed by the State, regional or local authorities or by other bodies governed by public law".
- Subclass of
- Organization
- Properties
- For this entity the following properties are defined: jurisdiction, legal form.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
jurisdiction
|
Administrative Territorial Units | 0..* | This property links an Organization to the Administrative Region(s) that it covers. | The value of the properly should be the URI of the region as defined in an authoritative list of regions. In Europe, this is likely to be the Administrative Territorial Units Named Authority List maintained by the Publications Office's Metadata Registry. The ATU list does not include a geometry. That is, the territory is only identified by its name not its spatial coordinates. This is likely to be the case for similar lists. If geometries are available for the Public Organization's territory, they can be linked from the territorial unit using the Core Location Vocabulary's locn:geometry property. |
|
legal form
|
Text | 0..1 | The type of entity as defined by the Belgian law |
Reference Framework
- Description
- A source from where Requirements are identified and derived.
- Usage
- Usual Reference Frameworks are legal and non-legal specifications. Examples include procedures, tendering legislation, etc.
- Properties
- For this entity the following properties are defined: identifier, implements.
Property | Expected Range | Cardinality | Description | Usage | Codelist |
---|---|---|---|---|---|
identifier
|
Literal | 1 | An unambiguous reference to a Reference Framework. | ||
implements
|
Change Event | 0..* | The implements property links a Change Event to relevant legislation or policy documents i.e. the formal framework under which the Change Event is defined. |
Role
- Description
- Denotes a role that a Person or other Agent can take in an organization. Instances of this class describe the abstract role; to denote a specific instance of a person playing that role in a specific organization use an instance of org:Membership.
- Properties
- No properties have been defined for this entity.
Site
- Description
- An office or other premise at which the organization is located. Many organizations are spread across multiple sites and many sites will host multiple locations.
- Properties
- For this entity the following properties are defined: address.
Changelog w.r.t. previous version
(non-normative)No changelog defined.
JSON-LD context
(non-normative)A reusable JSON-LD context definition for this Core Vocabulary is retrievable at: /thematic/models/public%20services/context/iceg-public-organisation_en.jsonld