Copyright © 2024
The Proof of nationality data model provides a minimum set of classes and properties for describing a proof of nationality evidence. This data model has been designed to support the different requirements of the OOTS action. The different classes and properties defined in this document are based on the OOTS data dictionary.
This Application Profile has the status Draft published at 2024-11-18.
Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog.
Copyright © 2024 European Union. All material in this repository is published under the license CC-BY 4.0, unless explicitly otherwise mentioned.
An Application Profile (AP) is a specification that reuses terms from one or more base standards, adding more specificity by identifying mandatory, recommended and optional elements to be used for a particular application, as well as recommendations for controlled vocabularies to be used.
A Core Vocabulary (CV) is a basic, reusable and extensible data specification that captures the fundamental characteristics of an entity in a context-neutral fashion. Its main objective is to provide terms to be reused in the broadest possible context. More information can be found on the SEMIC Style Guide.
This specification uses the following prefixes to shorten the URIs for readibility.Prefix | Namespace IRI |
---|---|
cv | http://data.europa.eu/m8g/ |
dct | http://purl.org/dc/terms/ |
foaf | http://xmlns.com/foaf/0.1/ |
locn | http://www.w3.org/ns/locn# |
rdf | http://www.w3.org/1999/02/22-rdf-syntax-ns# |
rdfs | http://www.w3.org/2000/01/rdf-schema# |
skos | http://www.w3.org/2004/02/skos/core# |
This document describes the usage of the following main entities for a correct usage of the Application Profile:
|
Proof of nationality |
The main entities are supported by:
|
Evidence Type |
Location |
Person |
And supported by these datatypes:
| GenericDate | Text |
Property | Range | Card | Definition | Usage | ||
---|---|---|---|---|---|---|
![]() |
geographic name | Text | 0..* | A textual description for a Location. | A geographic name is a proper noun applied to a spatial object. Taking the example used in the INSPIRE document (page 18), the following are all valid geographic names for the Greek capital: - "A?n?a"@gr-Grek (the Greek endonym written in the Greek script) - "Athína"@gr-Latn (the standard Romanisation of the endonym) - "Athens"@en (the English language exonym) INSPIRE has a detailed (XML-based) method of providing metadata about a geographic name and in XML-data sets that may be the most appropriate method to follow. When using the Core Location Vocabulary in data sets that are not focussed on environmental/geographical data (the use case for INSPIRE), the Code datatype or a simple language identifier may be used to provide such metadata. The country codes defined in ISO 3166 may be used as geographic names and these are generally preferred over either the long form or short form of a country's name (as they are less error prone). The Publications Office of the European Union recommends the use of ISO 3166-1 codes for countries in all cases except two: - use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; - use 'EL' in preference to the ISO 3166 code GR for Greece. Where a country has changed its name or no longer exists (such as Czechoslovakia, Yugoslavia etc.) use the ISO 3166-3 code. |
Property | Range | Card | Definition | Usage | ||
---|---|---|---|---|---|---|
![]() |
country of birth | Location | 0..* | The country in which the Person was born. | The Location Class has two properties: a Geographic Name and a Geographic Identifier. Plain codes like "DE" should be provided as values for Geographical Names whereas URIs should be provided as value of the Geographical Identifier. Ideally, provide both. Providing a simple country name is problematic and should be avoided whereas using a standardised system that allows the use of a code list for country names has a lot of potential for increasing semantic interoperability. Known diversity that one has to deal with when exchanging country names between different communication partners without relying on an agreed code list are: (a) long form vs. short form of a country name (e.g. Federal Republic of Germany vs. Germany), (b) different languages (Italy vs. Italia), (c) historic name vs. current name (Burma vs. Myanmar), (d) ambiguity of similar sounding countries (Republic of the Congo vs. Democratic Republic of the Congo). The Publications Office of the European Union recommends and uses ISO 3166-1 codes for countries in all cases except two: use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; use 'EL' in preference to the ISO 3166 code GR for Greece. See Publications Office list of countries for details of the OPOCE's full list of countries, codes, currencies and more. Where a country has changed its name or no longer exists (such as Czechoslovakia, Yugoslavia etc.) use the ISO 3166-3 code. | |
![]() |
date of birth | GenericDate | 0..* | The point in time on which the Person was born. |
The date of birth could be expressed as date, gYearMonth or gYear, example:
|
|
![]() |
family name | Text | 0..* | The hereditary surname of a family. | Usually referring to a group of people related by blood, marriage or adoption. 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". | |
![]() |
given name | Text | 0..* | The name(s) that identify the Person within a family with a common surname. | Usually a first name or forename. Given to a person by his or her parents at birth or 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". | |
![]() |
place of birth | Location | 0..* | The Location where the Person was born. | The Place of Birth and Place of Death are given using the Location class which is associated via the appropriate relationship. The Location Class has two properties: (1) the geographic name of the place, which is given as a string such as "Amsterdam" or "Valetta" and (2) an identifier, such as a geonames URI http://sws.geonames.org/2759794 (which identifies Amsterdam) or http://sws.geonames.org/2562305 (which identifies Valetta). The use of identifiers is preferred as these are unambiguous, however, public sector data typically uses simple names to record places and this is fully supported. |
Class | Definition | |
---|---|---|
![]() | The date data type is the union of xs:date, xs:gYearMonth and xs:gYear | |
![]() | The text data type is a combination of a string and a language identifier. |
No examples defined
Class | Class IRI | Property Type | Property | Property IRI |
---|---|---|---|---|
Evidence Type | http://data.europa.eu/m8g/EvidenceType |
|||
Location | http://purl.org/dc/terms/Location |
geographic name | http://www.w3.org/ns/locn#geographicName |
|
Person | http://www.w3.org/ns/person#Person |
country of birth | http://www.w3.org/ns/person#countryOfBirth |
|
Person | http://www.w3.org/ns/person#Person |
date of birth | http://data.europa.eu/m8g/birthDate |
|
Person | http://www.w3.org/ns/person#Person |
family name | http://xmlns.com/foaf/0.1/familyName |
|
Person | http://www.w3.org/ns/person#Person |
given name | http://xmlns.com/foaf/0.1/givenName |
|
Person | http://www.w3.org/ns/person#Person |
place of birth | http://www.w3.org/ns/person#placeOfBirth |
|
Proof of nationality | http://data.europa.eu/p4s/ProofOfNationality |
is about | http://purl.org/dc/terms/subject |
Please provide feedback on the general discussion forum