Abstract

Introduction

The Proof of residence: domicile data model provides a minimum set of classes and properties for describing a proof of domicile 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.

Status

This Application Profile has the status Draft published at 2024-08-29.

Information about the process and the decisions involved in the creation of this specification are consultable at the Changelog.

License

Copyright © 2024 European Union. All material in this repository is published under the license CC-BY 4.0, unless explicitly otherwise mentioned.

Terminology

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.

Overview

Main Entities

Proof of domicile

Definition

Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile).

Subclass of

Evidence Type

Properties

For this entity the following properties are defined: is about .

	Property	Range	Card	Definition	Usage
	is about	Person	1	Agent that is the subject in the provided Evidence.

Supportive Entities

Address

Definition

A spatial object that in a human-readable way identifies a fixed location.

Usage Note

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 , administrative unit level 1 , administrative unit level 2 , locator designator , post code , post name , thoroughfare .

	Property	Range	Card	Definition	Usage
	address area	Text	0..*	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.
	administrative unit level 1	Text	0..*	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	0..*	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.
	locator designator	Literal	0..*	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".
	post code	Literal	0..*	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	0..*	A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.	Usually a city, for example "Paris".
	thoroughfare	Text	0..*	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".

Location

Definition

An identifiable geographic place or named place.

Properties

For this entity the following properties are defined: geographic name .

	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.

Person

Definition

A individual human being who may be dead or alive, but not imaginary.

Usage Note

The fact that a person in the context of Core Person Vocabulary cannot be imaginary makes person:Person a subclass of foaf:Person which cover imaginary characters as well as real people. The Person Class is a subclass of the more general 'Agent' class.

Properties

For this entity the following properties are defined: country of birth , date of birth , domicile , family name , given name , place of birth , sex .

	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: 1980-09-16^^xs:date 1980-09^^xs:gYearMonth 1980^^xs:gYear
	domicile	Address	0..*	The place that the Person treats as permanent home.
	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.
	sex	Code	0..*	The organism's biological sex.	The recommended controlled vocabulary for this property is the sex authority table of the Publications Office.

Datatypes

	Class	Definition
	Code	An idea or notion; a unit of thought.
	GenericDate	The date data type is the union of xs:date, xs:gYearMonth and xs:gYear
	Literal	The class of literal values, eg. textual strings and integers.
	Text	The text data type is a combination of a string and a language identifier.

Feedback

Please provide feedback on the discussion forum