+ Copyright © 2024 +
+ + + + + + + + + + + + + + +Abstract
+Proof of domicle is a simplified data model describing a request for evidence regarding the birth of a person (evidence subject). This data model draws upon the domicile public document description of REGULATION (EU) 2016/119. ++ Introduction +
+ ++ The Proof of 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-10-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. +
+ +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# |
Overview
+ + +
+ This document describes the usage of the following main entities for a correct usage of the Application Profile:
+
+ |
+ Proof of domicile |
+
+ The main entities are supported by:
+
+ |
+ Address |
+ Evidence |
+ Location |
+ Person |
+
+ And supported by these datatypes:
+
+ | Code | GenericDate | Literal | Text |
+
+
+ + Main Entities +
+The main entities are those that form the core of the Application Profile. + + + + + + + + + + + + ++ 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 + + + +
- + Properties + + +
- + For this entity the following properties are defined: is about + . + + +
| + | ++ Property + | ++ Range + | ++ Card + | ++ Definition + | ++ Usage + | + +|
|---|---|---|---|---|---|---|
+
+
+ ![[o]](html/callout.png)
+
+ |
+ + + is about + | ++ + + Person + + + | ++ 1 + | ++ Agent that is the subject in the provided Evidence. + | ++ + | + ++ + | +
+ Supportive Entities +
+The supportive entities are supporting the main entities in the Application Profile. +They are included in the Application Profile because they form the range of properties. + + + + + ++ 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 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". + | + ++ + | +
+ Evidence + +
+ + +-
+
- + Definition + +
- + Proof that a Requirement is met. + + + +
- + Usage Note + +
- + The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV). + +Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces. + +Evidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. + +In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s). + + + +
- + Properties + + +
- + This specification does not impose any additional requirements to properties for this entity. + + +
+ 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:
+
|
+
+ + + | +
|
+
+
+
+
+ |
+ + + 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 +
+ + The following datatypes are used within this specification. + +| + | ++ 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. + |
Examples
+No examples defined
+Usage Guidelines
+Support for implementation
+ + The following section provides support for implementing the Proof of residence (all registered addresses). + + +JSON-LD context file
+ + One common technical question is the format in which the data is being exchanged. + For conformance with the Proof of residence (all registered addresses), it is not mandatory that this happens in a RDF serialisation, but the exhanged format SHOULD be unambiguously be transformable into RDF. + For the format JSON, a popular format to exchange data between systems, SEMIC provides a JSON-LD context file. + JSON-LD is a W3C Recommendation [[[json-ld11]]] that provided a standard approach to interpret JSON structures as RDF. + The provided JSON-LD context file can be used by implementers. + This JSON-LD context is not normative, i.e. other JSON-LD contexts are allowed. + + The JSON-LD context file downloadable here. + + +Validation
+ + To verify if the data is (technically) conformant to the Proof of residence (all registered addresses), the exchanged data can be validated using the provided SHACL shapes. + SHACL is a W3C Recommendation to express constraints on a RDF knowledge graph. + + To support the check whether or not a catalogue satisfies the expressed constraints in this Application Profile, the constraints in this specification are expressed using SHACL [[shacl]]. + Each constraint in this specification that could be converted into a SHACL expression has been included. + As such this collection of SHACL expressions that can be used to build a validation check for data. + + It is up to the implementers to define the validation they expect. + Each implementation happens within a context, and that context is beyond the SHACL expressions here. + + The shapes can be found here. + +RDF representation
+ The RDF representation of the Proof of residence (all registered addresses) is available here. + + +UML representation
+ The UML representation from which the Proof of residence (all registered addresses) has been build is available here. + + + +No XML schema defined
+ + + +Governance
+ +Versioning governance
+All specifications produced in SEMIC will follow the versioning rule described by the SEMIC Style Guide rule +PC-R3. +In case a SEMIC asset is deprecated the asset will remain available through its PURI. + +The serialisation will have: +-
+
- a dct:isReplacedBy referencing the new assets used instead and +
- an adms:status indicating its deprecated status. +
Governance requirements for re-used assets
+In order to adhere to the SEMIC Style Guide rule GC-R2 + a specification should have quality and governance standards for the assets that are being reused. + +In order for an asset to be considered for reuse within a SEMIC specification it can be requested by a community member or it requires to adhere to the following requirements: +-
+
- The asset is part of a recommendation by a major standards body or an EU institution. +
- The asset is actively being maintained. +
-
+
- Syntax validation will be performed on the relevant artefacts. +
- Constraint validation will be performed on the relevant artefacts. +
- The PURI will be validated. +
Lexicalisation rules
+ +In order to adhere to the SEMIC Style Guide rule SC-R3 a specification requires formal lexicalisation rules. +The Style Guide proposes two options either by using RDFS or SKOS lexicalisation. + +SEMIC uses and will use the RDFS lexicalisation for all of its specifications. More specifically: +-
+
- rdfs:label is used to provide a human-readable version of a resource's name. +
- The usage of certain resource can be clarified in a skos:usageNote. +
Quick Reference of Classes and Properties
+ +This section provides a condensed tabular overview of the mentioned classes and properties in this specification. +The properties are indicated as-
+
- Mandatory property: a receiver MUST be able to process the information for that property; a sender MUST provide the information for that property. +
- Recommended property: a receiver MUST be able to process the information for that property; a sender SHOULD provide the information for that property if it is available. +
- Optional property: a receiver MUST be able to process the information for that property; a sender MAY provide the information for that property but is not obliged to do so. +
- Deprecated property: a receiver SHOULD be able to process information about instances of that property; a sender SHOULD NOT provide the information about instances of that property. +
| Class | Class IRI | Property Type | Property | Property IRI |
|---|---|---|---|---|
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +address area | +http://www.w3.org/ns/locn#addressArea |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +administrative unit level 1 | +http://www.w3.org/ns/locn#adminUnitL1 |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +administrative unit level 2 | +http://www.w3.org/ns/locn#adminUnitL2 |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +locator designator | +http://www.w3.org/ns/locn#locatorDesignator |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +post code | +http://www.w3.org/ns/locn#postCode |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +post name | +http://www.w3.org/ns/locn#postName |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +thoroughfare | +http://www.w3.org/ns/locn#thoroughfare |
+
| Evidence | +http://data.europa.eu/m8g/Evidence |
+ + | + | + |
| 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 |
+ + | domicile | +http://data.europa.eu/m8g/domicile |
+
| 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 |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | sex | +http://data.europa.eu/m8g/sex |
+
| Proof of domicile | +http://data.europa.eu/p4s/ProofOfDomicile |
+ + | is about | +http://purl.org/dc/terms/subject |
+
Feedback
++ Please provide feedback on the discussion forum +
++ Copyright © 2024 +
+ + + + + + + + + + + + + + +Abstract
+Proof of domicle is a simplified data model describing a request for evidence regarding the birth of a person (evidence subject). This data model draws upon the domicile public document description of REGULATION (EU) 2016/119. ++ Introduction +
+ ++ The Proof of 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-10-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. +
+ +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# |
Overview
+ + +
+ This document describes the usage of the following main entities for a correct usage of the Application Profile:
+
+ |
+ Proof of domicile |
+
+ The main entities are supported by:
+
+ |
+ Address |
+ Evidence |
+ Location |
+ Person |
+
+ And supported by these datatypes:
+
+ | Code | GenericDate | Literal | Text |
+
+
+ + Main Entities +
+The main entities are those that form the core of the Application Profile. + + + + + + + + + + + + ++ 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 + + + +
- + 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 +
+The supportive entities are supporting the main entities in the Application Profile. +They are included in the Application Profile because they form the range of properties. + + + + + ++ 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 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". + | + ++ + | +
+ Evidence + +
+ + +-
+
- + Definition + +
- + Proof that a Requirement is met. + + + +
- + Usage Note + +
- + The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV). + +Although the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces. + +Evidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered. + +In some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s). + + + +
- + Properties + + +
- + This specification does not impose any additional requirements to properties for this entity. + + +
+ 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:
+
|
+
+ + + | +
|
+
+
+
+
+ |
+ + + 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 +
+ + The following datatypes are used within this specification. + +| + | ++ 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. + |
Examples
+No examples defined
+Usage Guidelines
+Support for implementation
+ + The following section provides support for implementing the Proof of residence (all registered addresses). + + +JSON-LD context file
+ + One common technical question is the format in which the data is being exchanged. + For conformance with the Proof of residence (all registered addresses), it is not mandatory that this happens in a RDF serialisation, but the exhanged format SHOULD be unambiguously be transformable into RDF. + For the format JSON, a popular format to exchange data between systems, SEMIC provides a JSON-LD context file. + JSON-LD is a W3C Recommendation [[[json-ld11]]] that provided a standard approach to interpret JSON structures as RDF. + The provided JSON-LD context file can be used by implementers. + This JSON-LD context is not normative, i.e. other JSON-LD contexts are allowed. + + The JSON-LD context file downloadable here. + + +Validation
+ + To verify if the data is (technically) conformant to the Proof of residence (all registered addresses), the exchanged data can be validated using the provided SHACL shapes. + SHACL is a W3C Recommendation to express constraints on a RDF knowledge graph. + + To support the check whether or not a catalogue satisfies the expressed constraints in this Application Profile, the constraints in this specification are expressed using SHACL [[shacl]]. + Each constraint in this specification that could be converted into a SHACL expression has been included. + As such this collection of SHACL expressions that can be used to build a validation check for data. + + It is up to the implementers to define the validation they expect. + Each implementation happens within a context, and that context is beyond the SHACL expressions here. + + The shapes can be found here. + +RDF representation
+ The RDF representation of the Proof of residence (all registered addresses) is available here. + + +UML representation
+ The UML representation from which the Proof of residence (all registered addresses) has been build is available here. + + + +No XML schema defined
+ + + +Governance
+ +Versioning governance
+All specifications produced in SEMIC will follow the versioning rule described by the SEMIC Style Guide rule +PC-R3. +In case a SEMIC asset is deprecated the asset will remain available through its PURI. + +The serialisation will have: +-
+
- a dct:isReplacedBy referencing the new assets used instead and +
- an adms:status indicating its deprecated status. +
Governance requirements for re-used assets
+In order to adhere to the SEMIC Style Guide rule GC-R2 + a specification should have quality and governance standards for the assets that are being reused. + +In order for an asset to be considered for reuse within a SEMIC specification it can be requested by a community member or it requires to adhere to the following requirements: +-
+
- The asset is part of a recommendation by a major standards body or an EU institution. +
- The asset is actively being maintained. +
-
+
- Syntax validation will be performed on the relevant artefacts. +
- Constraint validation will be performed on the relevant artefacts. +
- The PURI will be validated. +
Lexicalisation rules
+ +In order to adhere to the SEMIC Style Guide rule SC-R3 a specification requires formal lexicalisation rules. +The Style Guide proposes two options either by using RDFS or SKOS lexicalisation. + +SEMIC uses and will use the RDFS lexicalisation for all of its specifications. More specifically: +-
+
- rdfs:label is used to provide a human-readable version of a resource's name. +
- The usage of certain resource can be clarified in a skos:usageNote. +
Quick Reference of Classes and Properties
+ +This section provides a condensed tabular overview of the mentioned classes and properties in this specification. +The properties are indicated as-
+
- Mandatory property: a receiver MUST be able to process the information for that property; a sender MUST provide the information for that property. +
- Recommended property: a receiver MUST be able to process the information for that property; a sender SHOULD provide the information for that property if it is available. +
- Optional property: a receiver MUST be able to process the information for that property; a sender MAY provide the information for that property but is not obliged to do so. +
- Deprecated property: a receiver SHOULD be able to process information about instances of that property; a sender SHOULD NOT provide the information about instances of that property. +
| Class | Class IRI | Property Type | Property | Property IRI |
|---|---|---|---|---|
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +address area | +http://www.w3.org/ns/locn#addressArea |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +administrative unit level 1 | +http://www.w3.org/ns/locn#adminUnitL1 |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +administrative unit level 2 | +http://www.w3.org/ns/locn#adminUnitL2 |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +locator designator | +http://www.w3.org/ns/locn#locatorDesignator |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +post code | +http://www.w3.org/ns/locn#postCode |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +post name | +http://www.w3.org/ns/locn#postName |
+
| Address | +http://www.w3.org/ns/locn#Address |
+ Optional | +thoroughfare | +http://www.w3.org/ns/locn#thoroughfare |
+
| Evidence | +http://data.europa.eu/m8g/Evidence |
+ + | + | + |
| 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 |
+ + | domicile | +http://data.europa.eu/m8g/domicile |
+
| 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 |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | sex | +http://data.europa.eu/m8g/sex |
+
| Proof of domicile | +http://data.europa.eu/p4s/ProofOfDomicile |
+ + | is about | +http://purl.org/dc/terms/subject |
+
Feedback
++ Please provide feedback on the discussion forum +
+\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary" + }, + "ap-label-en": { + "en": "Address" + }, + "definition": { + "en": "A spatial object that in a human-readable way identifies a fixed location." + }, + "label": { + "en": "Address" + }, + "extra": { + "EA-Name": "Address", + "EA-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}", + "EA-Package": "locn", + "EA-Type": "CLASS", + "EA-Parents": "", + "EA-Parents2": [], + "parentclasses": "", + "label": { + "en": "Address" + }, + "definition": { + "en": "A spatial object that in a human-readable way identifies a fixed location." + }, + "usage": { + "en": "\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary" + }, + "ap-label-en": { + "en": "Address" + }, + "ap-definition-en": { + "en": "A spatial object that in a human-readable way identifies a fixed location." + }, + "ap-usageNote-en": "", + "ap-codelist": "", + "RawTags": [ + { + "key": "definition-en", + "value": "NOTE", + "note": "A spatial object that in a human-readable way identifies a fixed location." + }, + { + "key": "label-en", + "value": "Address", + "note": "null" + }, + { + "key": "uri", + "value": "http://www.w3.org/ns/locn#Address", + "note": "null" + }, + { + "key": "usageNote-en", + "value": "NOTE", + "note": "\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary" + } + ], + "Scope": "NOTHING" + }, + "name": "Address" + }, + { + "@id": "http://www.w3.org/ns/person#Person", + "@type": "http://www.w3.org/2002/07/owl#Class", + "inpackage": "OTHER_PACKAGE", + "ap-definition-en": { + "en": "A individual human being who may be dead or alive, but not imaginary." + }, + "usage": { + "en": "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." + }, + "ap-label-en": { + "en": "Person" + }, + "definition": { + "en": "A individual human being who may be dead or alive, but not imaginary." + }, + "label": { + "en": "Person" + }, + "extra": { + "EA-Name": "Person", + "EA-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}", + "EA-Package": "person", + "EA-Type": "CLASS", + "EA-Parents": "", + "EA-Parents2": [], + "parentclasses": "", + "label": { + "en": "Person" + }, + "definition": { + "en": "A individual human being who may be dead or alive, but not imaginary." + }, + "usage": { + "en": "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." + }, + "ap-label-en": { + "en": "Person" + }, + "ap-definition-en": { + "en": "A individual human being who may be dead or alive, but not imaginary." + }, + "ap-usageNote-en": "", + "ap-codelist": "", + "RawTags": [ + { + "key": "uri", + "value": "http://www.w3.org/ns/person#Person", + "note": "null" + }, + { + "key": "label-en", + "value": "Person", + "note": "null" + }, + { + "key": "definition-en", + "value": "A individual human being who may be dead or alive, but not imaginary.", + "note": "null" + }, + { + "key": "usageNote-en", + "value": "NOTE", + "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." + } + ], + "Scope": "NOTHING" + }, + "name": "Person" + } + ], + "externalproperties": [ + { + "@id": "http://data.europa.eu/m8g/birthDate", + "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty", + "name": "dateOfBirth", + "inpackage": "OTHER_PACKAGE", + "ap-definition-en": { + "en": "The point in time on which the Person was born." + }, + "usage": { + "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary" + }, + "parents": [], + "rawTags": { + "definition-en": "A spatial object that in a human-readable way identifies a fixed location.", + "label-en": "Address", + "uri": "http://www.w3.org/ns/locn#Address", + "usageNote-en": "\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary" + }, + "properties": [ + { + "uri": "http://www.w3.org/ns/locn#addressArea", + "name": "addressArea", + "sort": "address area", + "label": { + "en": "address area" + }, + "description": { + "en": "The name of a geographic area that groups Addresses." + }, + "usage": { + "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Text", + "range_uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "scopedrange": [ + { + "range_uri": "#Text", + "range_puri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString", + "range_label": { + "en": "Text" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "usageNote-en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit.", + "uri": "http://www.w3.org/ns/locn#addressArea", + "label-en": "address area", + "definition-en": "The name of a geographic area that groups Addresses.", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#adminUnitL1", + "name": "administrativeUnitLevel1", + "sort": "administrative unit level 1", + "label": { + "en": "administrative unit level 1" + }, + "description": { + "en": "The name of the uppermost level of the address, almost always a country." + }, + "usage": { + "en": "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." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Text", + "range_uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "scopedrange": [ + { + "range_uri": "#Text", + "range_puri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString", + "range_label": { + "en": "Text" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "usageNote-en": "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.", + "uri": "http://www.w3.org/ns/locn#adminUnitL1", + "label-en": "administrative unit level 1", + "definition-en": "The name of the uppermost level of the address, almost always a country.", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#adminUnitL2", + "name": "administrativeUnitLevel2", + "sort": "administrative unit level 2", + "label": { + "en": "administrative unit level 2" + }, + "description": { + "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities." + }, + "usage": { + "en": "Values could be a region or province, more granular than level 1." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Text", + "range_uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "scopedrange": [ + { + "range_uri": "#Text", + "range_puri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString", + "range_label": { + "en": "Text" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "usageNote-en": "Values could be a region or province, more granular than level 1.", + "uri": "http://www.w3.org/ns/locn#adminUnitL2", + "label-en": "administrative unit level 2", + "definition-en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities.", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#locatorDesignator", + "name": "locatorDesignator", + "sort": "locator designator", + "label": { + "en": "locator designator" + }, + "description": { + "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope." + }, + "usage": { + "en": "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\"." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Literal", + "range_uri": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ], + "scopedrange": [ + { + "range_uri": "#Literal", + "range_puri": "http://www.w3.org/2000/01/rdf-schema#Literal", + "range_label": { + "en": "Literal" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "usageNote-en": "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\".", + "uri": "http://www.w3.org/ns/locn#locatorDesignator", + "label-en": "locator designator", + "definition-en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope.", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#postCode", + "name": "postCode", + "sort": "post code", + "label": { + "en": "post code" + }, + "description": { + "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points." + }, + "usage": { + "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Literal", + "range_uri": "http://www.w3.org/2000/01/rdf-schema#Literal" + } + ], + "scopedrange": [ + { + "range_uri": "#Literal", + "range_puri": "http://www.w3.org/2000/01/rdf-schema#Literal", + "range_label": { + "en": "Literal" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "usageNote-en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\".", + "uri": "http://www.w3.org/ns/locn#postCode", + "label-en": "post code", + "definition-en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#postName", + "name": "postName", + "sort": "post name", + "label": { + "en": "post name" + }, + "description": { + "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points." + }, + "usage": { + "en": "Usually a city, for example \"Paris\"." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Text", + "range_uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "scopedrange": [ + { + "range_uri": "#Text", + "range_puri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString", + "range_label": { + "en": "Text" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "uri": "http://www.w3.org/ns/locn#postName", + "label-en": "post name", + "definition-en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.", + "usageNote-en": "Usually a city, for example \"Paris\".", + "property-usage-scope": "optional" + } + }, + { + "uri": "http://www.w3.org/ns/locn#thoroughfare", + "name": "thoroughfare", + "sort": "thoroughfare", + "label": { + "en": "thoroughfare" + }, + "description": { + "en": "The name of a passage or way through from one location to another." + }, + "usage": { + "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"." + }, + "domain": [ + { + "EA-Name": "Address", + "uri": "http://www.w3.org/ns/locn#Address" + } + ], + "range": [ + { + "range_label": "Text", + "range_uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString" + } + ], + "scopedrange": [ + { + "range_uri": "#Text", + "range_puri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString", + "range_label": { + "en": "Text" + } + } + ], + "cardinality": "0..*", + "codelist_uri": "", + "rawTags": { + "uri": "http://www.w3.org/ns/locn#thoroughfare", + "label-en": "thoroughfare", + "definition-en": "The name of a passage or way through from one location to another.", + "usageNote-en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\".", + "property-usage-scope": "optional" + } + } + ] + }, + { + "uri": "http://www.w3.org/ns/person#Person", + "name": "Person", + "label": { + "en": "Person" + }, + "sort": "Person", + "description": { + "en": "A individual human being who may be dead or alive, but not imaginary." + }, + "usage": { + "en": "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." + }, + "parents": [], + "rawTags": { + "uri": "http://www.w3.org/ns/person#Person", + "label-en": "Person", + "definition-en": "A individual human being who may be dead or alive, but not imaginary.", + "usageNote-en": "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": [ + { + "uri": "http://data.europa.eu/m8g/birthDate", + "name": "dateOfBirth", + "sort": "date of birth", + "label": { + "en": "date of birth" + }, + "description": { + "en": "The point in time on which the Person was born." + }, + "usage": { + "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
\r\nAn \"address representation\" as conceptually defined by the INSPIRE Address Representation data type<\/a>: \"Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.\"\r\n<\/p><\/br>\r\n\r\n \r\nThe 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<\/a> provides a method through which different Addresses can be converted from one conceptual model to another.\r\n<\/p><\/br>\r\n\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe addressID is part of the INSPIRE guidelines<\/a> and provides a hook that can be used to link the Address to an alternative representation, such as vCard<\/a> or OASIS xAL<\/a>.\r\n<\/p><\/br>\r\n\r\nThis class belongs to Core Location Vocabulary<\/a>"}, "ap-label-en" : {"en": "Address"}, "definition" : {"en": "A spatial object that in a human-readable way identifies a fixed location."}, "label" : {"en": "Address"},
+"extra": {"EA-Name" : "Address", "EA-Guid" : "{650BCC62-B5E6-4070-8DC6-A39F0953E191}", "EA-Package" : "locn", "EA-Type" : "CLASS", "EA-Parents" : "", "EA-Parents2" : [], "parentclasses" : "", "label" : "Address", "definition" : "A spatial object that in a human-readable way identifies a fixed location.", "usage" : " \r\nAn \"address representation\" as conceptually defined by the INSPIRE Address Representation data type<\/a>: \"Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.\"\r\n<\/p><\/br>\r\n\r\n \r\nThe 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<\/a> provides a method through which different Addresses can be converted from one conceptual model to another.\r\n<\/p><\/br>\r\n\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe addressID is part of the INSPIRE guidelines<\/a> and provides a hook that can be used to link the Address to an alternative representation, such as vCard<\/a> or OASIS xAL<\/a>.\r\n<\/p><\/br>\r\n\r\nThis class belongs to Core Location Vocabulary<\/a>", "ap-label-en" : "Address", "ap-definition-en" : "A spatial object that in a human-readable way identifies a fixed location.", "ap-usageNote-en" : "", "ap-codelist" : "", "RawTags" : [{ "key": "definition-en", "value": "NOTE", "note": "A spatial object that in a human-readable way identifies a fixed location." }, { "key": "label-en", "value": "Address", "note": "null" }, { "key": "uri", "value": "http:\/\/www.w3.org\/ns\/locn#Address", "note": "null" }, { "key": "usageNote-en", "value": "NOTE", "note": " \r\nAn \"address representation\" as conceptually defined by the INSPIRE Address Representation data type<\/a>: \"Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.\"\r\n<\/p><\/br>\r\n\r\n \r\nThe 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<\/a> provides a method through which different Addresses can be converted from one conceptual model to another.\r\n<\/p><\/br>\r\n\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe addressID is part of the INSPIRE guidelines<\/a> and provides a hook that can be used to link the Address to an alternative representation, such as vCard<\/a> or OASIS xAL<\/a>.\r\n<\/p><\/br>\r\n\r\nThis class belongs to Core Location Vocabulary<\/a>" }], "Scope" : "NOTHING", "ap-definition-en" : {"en": "A spatial object that in a human-readable way identifies a fixed location."}, "usage" : {"en": " \r\nAn \"address representation\" as conceptually defined by the INSPIRE Address Representation data type<\/a>: \"Representation of an address spatial object for use in external application schemas that need to include the basic, address information in a readable way.\"\r\n<\/p><\/br>\r\n\r\n \r\nThe 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<\/a> provides a method through which different Addresses can be converted from one conceptual model to another.\r\n<\/p><\/br>\r\n\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe addressID is part of the INSPIRE guidelines<\/a> and provides a hook that can be used to link the Address to an alternative representation, such as vCard<\/a> or OASIS xAL<\/a>.\r\n<\/p><\/br>\r\n\r\nThis class belongs to Core Location Vocabulary<\/a>"}, "ap-label-en" : {"en": "Address"}, "definition" : {"en": "A spatial object that in a human-readable way identifies a fixed location."}, "label" : {"en": "Address"}},
+"name": "Address"
+}
+, {
+"@id": "http://www.w3.org/ns/person#Person",
+"@type": "http://www.w3.org/2002/07/owl#Class",
+"inpackage": "OTHER_PACKAGE",
+"ap-definition-en" : {"en": "A individual human being who may be dead or alive, but not imaginary."}, "usage" : {"en": "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<\/a>."}, "ap-label-en" : {"en": "Person"}, "definition" : {"en": "A individual human being who may be dead or alive, but not imaginary."}, "label" : {"en": "Person"},
+"extra": {"EA-Name" : "Person", "EA-Guid" : "{25864841-22B7-4c9a-9D72-EFF902B16055}", "EA-Package" : "person", "EA-Type" : "CLASS", "EA-Parents" : "", "EA-Parents2" : [], "parentclasses" : "", "label" : "Person", "definition" : "A individual human being 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 foaf:Person which cover imaginary characters as well as real people. The Person Class is a subclass of the more general 'Agent' class<\/a>.", "ap-label-en" : "Person", "ap-definition-en" : "A individual human being who may be dead or alive, but not imaginary.", "ap-usageNote-en" : "", "ap-codelist" : "", "RawTags" : [{ "key": "uri", "value": "http:\/\/www.w3.org\/ns\/person#Person", "note": "null" }, { "key": "label-en", "value": "Person", "note": "null" }, { "key": "definition-en", "value": "A individual human being who may be dead or alive, but not imaginary.", "note": "null" }, { "key": "usageNote-en", "value": "NOTE", "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<\/a>." }], "Scope" : "NOTHING", "ap-definition-en" : {"en": "A individual human being who may be dead or alive, but not imaginary."}, "usage" : {"en": "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<\/a>."}, "ap-label-en" : {"en": "Person"}, "definition" : {"en": "A individual human being who may be dead or alive, but not imaginary."}, "label" : {"en": "Person"}},
+"name": "Person"
+}
+],
+"externalproperties": [
+{
+"@id": "http://data.europa.eu/m8g/birthDate",
+"@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+"name": "dateOfBirth",
+"inpackage": "OTHER_PACKAGE",
+"ap-definition-en" : {"en": "The point in time on which the Person was born."}, "usage" : {"en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n \r\nAn \"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.\"\r\n \r\nThe 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.\r\n \r\nThis 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\r\nproperties, we add two further properties:\r\n \r\nThe 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.\r\n\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\n
\r\nThe 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.\r\n\r\n
"
+ }
+ },
+ {
+ "EA-Guid": "{E2F8EB6A-D959-47b5-A56A-E8B7947A2119}",
+ "name": "domicile",
+ "label": {
+ "en": "domicile"
+ },
+ "definition": {
+ "en": "The place that the Person treats as permanent home."
+ }
+ },
+ {
+ "EA-Guid": "{AB3326D0-B0BD-4fc3-AFEA-A3120025327D}",
+ "name": "sex",
+ "label": {
+ "en": "sex"
+ },
+ "definition": {
+ "en": "The organism's biological sex."
+ },
+ "usage": {
+ "en": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ }
+ },
+ {
+ "EA-Guid": "{9E77DA77-7164-424f-811A-260426ACCF6A}",
+ "name": "isAbout",
+ "label": {
+ "en": "is about"
+ },
+ "definition": {
+ "en": "Agent that is the subject in the provided Evidence."
+ }
+ },
+ {
+ "EA-Guid": "{42A3291F-2C59-4432-9003-3E6719430A52}",
+ "name": "addressArea",
+ "label": {
+ "en": "address area"
+ },
+ "definition": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "usage": {
+ "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ }
+ },
+ {
+ "EA-Guid": "{EFCE2B24-F154-487f-BDC4-0C162CA80935}",
+ "name": "administrativeUnitLevel1",
+ "label": {
+ "en": "administrative unit level 1"
+ },
+ "definition": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "EA-Guid": "{958C6E0B-EB04-416c-BC1A-5B3459FD355A}",
+ "name": "administrativeUnitLevel2",
+ "label": {
+ "en": "administrative unit level 2"
+ },
+ "definition": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "usage": {
+ "en": "Values could be a region or province, more granular than level 1."
+ }
+ },
+ {
+ "EA-Guid": "{47322390-B650-43d1-927D-B3160DB699C8}",
+ "name": "geographicName",
+ "label": {
+ "en": "geographic name"
+ },
+ "definition": {
+ "en": "A textual description for a Location."
+ },
+ "usage": {
+ "en": "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.\r\n\r\nThe 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."
+ }
+ },
+ {
+ "EA-Guid": "{509BF1D0-4E76-4bee-B17F-AC883B236548}",
+ "name": "locatorDesignator",
+ "label": {
+ "en": "locator designator"
+ },
+ "definition": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ {
+ "EA-Guid": "{2EF6D767-8E3F-461c-AC37-772819BA21B6}",
+ "name": "postCode",
+ "label": {
+ "en": "post code"
+ },
+ "definition": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ }
+ },
+ {
+ "EA-Guid": "{F0699A53-4F4C-4e83-AF49-34E33744BF36}",
+ "name": "postName",
+ "label": {
+ "en": "post name"
+ },
+ "definition": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Usually a city, for example \"Paris\"."
+ }
+ },
+ {
+ "EA-Guid": "{2D384BE4-CFED-4f52-B1EC-3C84511ACCC6}",
+ "name": "thoroughfare",
+ "label": {
+ "en": "thoroughfare"
+ },
+ "definition": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "usage": {
+ "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ }
+ },
+ {
+ "EA-Guid": "{C58092CC-C21A-4932-A0EA-65E8519BA158}",
+ "name": "countryOfBirth",
+ "label": {
+ "en": "country of birth"
+ },
+ "definition": {
+ "en": "The country in which the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "EA-Guid": "{2F4217DC-565B-49da-9EBB-48719E9634B1}",
+ "name": "placeOfBirth",
+ "label": {
+ "en": "place of birth"
+ },
+ "definition": {
+ "en": "The Location where the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "EA-Guid": "{96E7483C-255D-4df5-91F7-77B219146F13}",
+ "name": "familyName",
+ "label": {
+ "en": "family name"
+ },
+ "definition": {
+ "en": "The hereditary surname of a family."
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ {
+ "EA-Guid": "{DDF3ED17-7415-4c6c-B208-7B642496AD2D}",
+ "name": "givenName",
+ "label": {
+ "en": "given name"
+ },
+ "definition": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ }
+ ]
+}
diff --git a/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/ProofOfAllResidence_en_merged.jsonld b/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/ProofOfAllResidence_en_merged.jsonld
new file mode 100644
index 000000000..1a59984bd
--- /dev/null
+++ b/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/ProofOfAllResidence_en_merged.jsonld
@@ -0,0 +1,2433 @@
+{
+ "@context": {
+ "affiliation": {
+ "@id": "http://schema.org/affiliation"
+ },
+ "authors": {
+ "@id": "foaf:maker",
+ "@type": "foaf:Person"
+ },
+ "classes": {
+ "@reverse": "rdfs:isDefinedBy"
+ },
+ "contributors": {
+ "@id": "dcterms:contributor",
+ "@type": "foaf:Person"
+ },
+ "datatypes": {
+ "@reverse": "rdfs:isDefinedBy"
+ },
+ "dcat": "http://www.w3.org/ns/dcat#",
+ "dcterms": "http://purl.org/dc/terms/",
+ "domain": {
+ "@id": "rdfs:domain"
+ },
+ "editors": {
+ "@id": "rec:editor",
+ "@type": "foaf:Person"
+ },
+ "externals": {
+ "@id": "rdfs:seeAlso",
+ "@type": "http://www.w3.org/2000/01/rdf-schema#Class"
+ },
+ "foaf": "http://xmlns.com/foaf/0.1/",
+ "generalization": {
+ "@id": "rdfs:subPropertyOf"
+ },
+ "issued": {
+ "@id": "dcterms:issued"
+ },
+ "label": {
+ "@container": "@language",
+ "@id": "rdfs:label"
+ },
+ "maxCardinality": {
+ "@id": "sh:maxCount"
+ },
+ "minCardinality": {
+ "@id": "sh:minCount"
+ },
+ "modified": {
+ "@id": "dcterms:modified",
+ "@type": "xsd:date"
+ },
+ "name": {
+ "@id": "rdfs:label"
+ },
+ "owl": "http://www.w3.org/2002/07/owl#",
+ "person": "http://www.w3.org/ns/person#",
+ "properties": {
+ "@reverse": "rdfs:isDefinedBy"
+ },
+ "qb": "http://purl.org/linked-data/cube#",
+ "range": {
+ "@id": "rdfs:range"
+ },
+ "rdf": "http://www.w3.org/1999/02/22-rdf-syntax-ns#",
+ "rdfs": "http://www.w3.org/2000/01/rdf-schema#",
+ "rec": "http://www.w3.org/2001/02pd/rec54#",
+ "sdmx-attribute": "http://purl.org/linked-data/sdmx/2009/attribute#",
+ "sdmx-concept": "http://purl.org/linked-data/sdmx/2009/concept#",
+ "sdmx-dimension": "http://purl.org/linked-data/sdmx/2009/dimension#",
+ "sh": "http://w3.org/ns/shacl#",
+ "skos": "http://www.w3.org/2004/02/skos/core#",
+ "vann": "http://purl.org/vocab/vann/",
+ "vlaanderen": "http://data.vlaanderen.be/ns/",
+ "void": "http://rdfs.org/ns/void#",
+ "xsd": "http://www.w3.org/2001/XMLSchema#"
+ },
+ "@id": "https://data.europa.eu/m8g",
+ "@type": "http://www.w3.org/2002/07/owl#Ontology",
+ "authors": [],
+ "baseURI": "https://data.europa.eu/m8g/",
+ "branchtag": "oots",
+ "classes": [],
+ "config": "config/config-ap.json",
+ "contributors": [],
+ "contributors-column": "OOTS",
+ "contributors-file": "stakeholders.csv",
+ "diagram": "ProofOfAllResidence",
+ "documentcommit": "d4cf057a731bf3011a881a4c2f9138b07b9ab0fa",
+ "documentconfig": {
+ "editorDocumentroot": "https://data-models-oots-tdd-8b6791fd33fcb1f29c7d6ad9c6173ba55d28c0a5f9.pages.code.europa.eu/Evidence/ProofOfAllResidence/releases/0.0.1",
+ "statuslabel": "Draft"
+ },
+ "dummy": "2",
+ "eap": "OOTS_ProofOfAllResidence.eap",
+ "editors": [
+ {
+ "@type": "foaf:Person",
+ "affiliation": {
+ "foaf:name": "PwC EU Services"
+ },
+ "foaf:firstName": "Emilien",
+ "foaf:lastName": "Caudron"
+ },
+ {
+ "@type": "foaf:Person",
+ "affiliation": {
+ "foaf:name": "PwC EU Services"
+ },
+ "foaf:firstName": "Faruk",
+ "foaf:lastName": "Karabulut"
+ },
+ {
+ "@type": "foaf:Person",
+ "affiliation": {
+ "foaf:name": "PwC EU Services"
+ },
+ "foaf:firstName": "Emidio",
+ "foaf:lastName": "Stani"
+ },
+ {
+ "@type": "foaf:Person",
+ "affiliation": {
+ "foaf:name": "PwC EU Services"
+ },
+ "foaf:firstName": "Claudio",
+ "foaf:lastName": "Valle"
+ }
+ ],
+ "externalproperties": [
+ {
+ "@id": "http://data.europa.eu/m8g/birthDate",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{0E297AAE-E6BA-42a0-A308-FC513C2D5EB1}",
+ "ap-definition-en": {
+ "en": "The point in time on which the Person was born."
+ },
+ "ap-label-en": {
+ "en": "date of birth"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The point in time on which the Person was born."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{0E297AAE-E6BA-42a0-A308-FC513C2D5EB1}",
+ "EA-Name": "dateOfBirth",
+ "EA-Package": "person",
+ "EA-Range": "GenericDate",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "EA-Name": "GenericDate",
+ "EA-Package": "DataTypes",
+ "uri": "http://data.europa.eu/m8g/GenericDate"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://data.europa.eu/m8g/birthDate"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "date of birth"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The point in time on which the Person was born."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n\r\n
",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The point in time on which the Person was born."
+ },
+ "ap-label-en": {
+ "en": "date of birth"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The point in time on which the Person was born."
+ },
+ "label": {
+ "en": "date of birth"
+ },
+ "usage": {
+ "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n\r\n
"
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "date of birth"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "dateOfBirth",
+ "range": [
+ {
+ "EA-GUID": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "EA-Name": "GenericDate",
+ "EA-Package": "DataTypes",
+ "uri": "http://data.europa.eu/m8g/GenericDate"
+ }
+ ],
+ "usage": {
+ "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n\r\n
"
+ }
+ },
+ {
+ "@id": "http://data.europa.eu/m8g/domicile",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "EA-Guid": "{E2F8EB6A-D959-47b5-A56A-E8B7947A2119}",
+ "ap-definition-en": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "ap-label-en": {
+ "en": "domicile"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "DestRoleTags": [
+ {
+ "key": "definition-en",
+ "note": "The place that the Person treats as permanent home.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "domicile",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://data.europa.eu/m8g/domicile",
+ "value": "NOTE"
+ }
+ ],
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{E2F8EB6A-D959-47b5-A56A-E8B7947A2119}",
+ "EA-Name": "domicile",
+ "EA-Package": "",
+ "EA-Range": "Address",
+ "EA-Type": "connector",
+ "RangeData": {
+ "EA-GUID": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Name": "Address",
+ "EA-Package": "locn",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ },
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "note": "The place that the Person treats as permanent home.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "domicile",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://data.europa.eu/m8g/domicile",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "ap-label-en": {
+ "en": "domicile"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "derived": "false",
+ "destRole": "domicile",
+ "label": {
+ "en": "domicile"
+ },
+ "sourceRole": "null",
+ "usage": ""
+ },
+ "generalization": [],
+ "inpackage": "UNKNOWN",
+ "label": {
+ "en": "domicile"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "domicile",
+ "range": [
+ {
+ "EA-GUID": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Name": "Address",
+ "EA-Package": "locn",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ]
+ },
+ {
+ "@id": "http://data.europa.eu/m8g/sex",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "EA-Guid": "{AB3326D0-B0BD-4fc3-AFEA-A3120025327D}",
+ "ap-definition-en": {
+ "en": "The organism's biological sex."
+ },
+ "ap-label-en": {
+ "en": "sex"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The organism's biological sex."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{AB3326D0-B0BD-4fc3-AFEA-A3120025327D}",
+ "EA-Name": "sex",
+ "EA-Package": "person",
+ "EA-Range": "Code",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "EA-Name": "Code",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/2004/02/skos/core#Concept"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://data.europa.eu/m8g/sex"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "sex"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The organism's biological sex."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office.",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The organism's biological sex."
+ },
+ "ap-label-en": {
+ "en": "sex"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The organism's biological sex."
+ },
+ "label": {
+ "en": "sex"
+ },
+ "usage": {
+ "en": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "sex"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "sex",
+ "range": [
+ {
+ "EA-GUID": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "EA-Name": "Code",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/2004/02/skos/core#Concept"
+ }
+ ],
+ "usage": {
+ "en": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ }
+ },
+ {
+ "@id": "http://purl.org/dc/terms/subject",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "EA-Guid": "{9E77DA77-7164-424f-811A-260426ACCF6A}",
+ "ap-definition-en": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "ap-label-en": {
+ "en": "is about"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "domain": [
+ {
+ "EA-Name": "ProofOfDomicile",
+ "uri": "http://data.europa.eu/p4s/ProofOfDomicile"
+ }
+ ],
+ "extra": {
+ "DestRoleTags": [
+ {
+ "key": "definition-en",
+ "note": "Agent that is the subject in the provided Evidence.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "is about",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://purl.org/dc/terms/subject",
+ "value": "NOTE"
+ }
+ ],
+ "EA-Domain": "ProofOfDomicile",
+ "EA-Domain-Guid": "{4D66240C-3C6D-49b6-811C-65782288501B}",
+ "EA-Guid": "{9E77DA77-7164-424f-811A-260426ACCF6A}",
+ "EA-Name": "isAbout",
+ "EA-Package": "",
+ "EA-Range": "Person",
+ "EA-Type": "connector",
+ "RangeData": {
+ "EA-GUID": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Name": "Person",
+ "EA-Package": "person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ },
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "note": "Agent that is the subject in the provided Evidence.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "is about",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://purl.org/dc/terms/subject",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "ap-label-en": {
+ "en": "is about"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "derived": "false",
+ "destRole": "isAbout",
+ "label": {
+ "en": "is about"
+ },
+ "sourceRole": "null",
+ "usage": ""
+ },
+ "generalization": [],
+ "inpackage": "UNKNOWN",
+ "label": {
+ "en": "is about"
+ },
+ "maxCardinality": "1",
+ "minCardinality": "1",
+ "name": "isAbout",
+ "range": [
+ {
+ "EA-GUID": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Name": "Person",
+ "EA-Package": "person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ]
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#addressArea",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{42A3291F-2C59-4432-9003-3E6719430A52}",
+ "ap-definition-en": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "ap-label-en": {
+ "en": "address area"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{42A3291F-2C59-4432-9003-3E6719430A52}",
+ "EA-Name": "addressArea",
+ "EA-Package": "locn",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit.",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#addressArea"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "address area"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The name of a geographic area that groups Addresses."
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "ap-label-en": {
+ "en": "address area"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "label": {
+ "en": "address area"
+ },
+ "usage": {
+ "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "address area"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "addressArea",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#adminUnitL1",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{EFCE2B24-F154-487f-BDC4-0C162CA80935}",
+ "ap-definition-en": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 1"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{EFCE2B24-F154-487f-BDC4-0C162CA80935}",
+ "EA-Name": "adminUnitL1",
+ "EA-Package": "locn",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "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.",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#adminUnitL1"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "administrative unit level 1"
+ },
+ {
+ "key": "definition-en",
+ "note": "The name of the uppermost level of the address, almost always a country.",
+ "value": "NOTE"
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 1"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "label": {
+ "en": "administrative unit level 1"
+ },
+ "usage": {
+ "en": "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."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "administrative unit level 1"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "administrativeUnitLevel1",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#adminUnitL2",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{958C6E0B-EB04-416c-BC1A-5B3459FD355A}",
+ "ap-definition-en": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 2"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{958C6E0B-EB04-416c-BC1A-5B3459FD355A}",
+ "EA-Name": "adminUnitL2",
+ "EA-Package": "locn",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "Values could be a region or province, more granular than level 1.",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#adminUnitL2"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "administrative unit level 2"
+ },
+ {
+ "key": "definition-en",
+ "note": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities.",
+ "value": "NOTE"
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 2"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "label": {
+ "en": "administrative unit level 2"
+ },
+ "usage": {
+ "en": "Values could be a region or province, more granular than level 1."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "administrative unit level 2"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "administrativeUnitLevel2",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "Values could be a region or province, more granular than level 1."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#geographicName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{47322390-B650-43d1-927D-B3160DB699C8}",
+ "ap-definition-en": {
+ "en": "A textual description for a Location."
+ },
+ "ap-label-en": {
+ "en": "geographic name"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "A textual description for a Location."
+ },
+ "domain": [
+ {
+ "EA-Name": "Location",
+ "uri": "http://purl.org/dc/terms/Location"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Location",
+ "EA-Domain-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Guid": "{47322390-B650-43d1-927D-B3160DB699C8}",
+ "EA-Name": "geographicName",
+ "EA-Package": "dct",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#geographicName"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "geographic name"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "A textual description for a Location."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "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.\r\n\r\nThe 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.",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "A textual description for a Location."
+ },
+ "ap-label-en": {
+ "en": "geographic name"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "A textual description for a Location."
+ },
+ "label": {
+ "en": "geographic name"
+ },
+ "usage": {
+ "en": "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.\r\n\r\nThe 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."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "geographic name"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "geographicName",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "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.\r\n\r\nThe 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."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#locatorDesignator",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{509BF1D0-4E76-4bee-B17F-AC883B236548}",
+ "ap-definition-en": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "ap-label-en": {
+ "en": "locator designator"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{509BF1D0-4E76-4bee-B17F-AC883B236548}",
+ "EA-Name": "locatorDesignator",
+ "EA-Package": "locn",
+ "EA-Range": "Literal",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "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\".",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#locatorDesignator"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "locator designator"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "ap-label-en": {
+ "en": "locator designator"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "label": {
+ "en": "locator designator"
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "locator designator"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "locatorDesignator",
+ "range": [
+ {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ }
+ ],
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#postCode",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{2EF6D767-8E3F-461c-AC37-772819BA21B6}",
+ "ap-definition-en": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-label-en": {
+ "en": "post code"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{2EF6D767-8E3F-461c-AC37-772819BA21B6}",
+ "EA-Name": "postCode",
+ "EA-Package": "locn",
+ "EA-Range": "Literal",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "null",
+ "value": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#postCode"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "post code"
+ },
+ {
+ "key": "definition-en",
+ "note": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.",
+ "value": "NOTE"
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-label-en": {
+ "en": "post code"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "label": {
+ "en": "post code"
+ },
+ "usage": {
+ "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "post code"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "postCode",
+ "range": [
+ {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ }
+ ],
+ "usage": {
+ "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#postName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{F0699A53-4F4C-4e83-AF49-34E33744BF36}",
+ "ap-definition-en": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-label-en": {
+ "en": "post name"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{F0699A53-4F4C-4e83-AF49-34E33744BF36}",
+ "EA-Name": "postName",
+ "EA-Package": "locn",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#postName"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "post name"
+ },
+ {
+ "key": "definition-en",
+ "note": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points.",
+ "value": "NOTE"
+ },
+ {
+ "key": "usageNote-en",
+ "note": "null",
+ "value": "Usually a city, for example \"Paris\"."
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-label-en": {
+ "en": "post name"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "label": {
+ "en": "post name"
+ },
+ "usage": {
+ "en": "Usually a city, for example \"Paris\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "post name"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "postName",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "Usually a city, for example \"Paris\"."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#thoroughfare",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{2D384BE4-CFED-4f52-B1EC-3C84511ACCC6}",
+ "ap-definition-en": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "ap-label-en": {
+ "en": "thoroughfare"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "domain": [
+ {
+ "EA-Name": "Address",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Guid": "{2D384BE4-CFED-4f52-B1EC-3C84511ACCC6}",
+ "EA-Name": "thoroughfare",
+ "EA-Package": "locn",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#thoroughfare"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "thoroughfare"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The name of a passage or way through from one location to another."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "null",
+ "value": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ },
+ {
+ "key": "property-usage-scope",
+ "note": "null",
+ "value": "optional"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "ap-label-en": {
+ "en": "thoroughfare"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "label": {
+ "en": "thoroughfare"
+ },
+ "usage": {
+ "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "thoroughfare"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "thoroughfare",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/person#countryOfBirth",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "EA-Guid": "{C58092CC-C21A-4932-A0EA-65E8519BA158}",
+ "ap-definition-en": {
+ "en": "The country in which the Person was born."
+ },
+ "ap-label-en": {
+ "en": "country of birth"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The country in which the Person was born."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "DestRoleTags": [
+ {
+ "key": "usageNote-en",
+ "note": "NOTE$ea_notes=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.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "country of birth",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://www.w3.org/ns/person#countryOfBirth",
+ "value": "NOTE"
+ },
+ {
+ "key": "definition-en",
+ "note": "The country in which the Person was born.",
+ "value": "NOTE"
+ }
+ ],
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{C58092CC-C21A-4932-A0EA-65E8519BA158}",
+ "EA-Name": "countryOfBirth",
+ "EA-Package": "",
+ "EA-Range": "Location",
+ "EA-Type": "connector",
+ "RangeData": {
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Name": "Location",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "NOTE$ea_notes=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.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "country of birth",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://www.w3.org/ns/person#countryOfBirth",
+ "value": "NOTE"
+ },
+ {
+ "key": "definition-en",
+ "note": "The country in which the Person was born.",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The country in which the Person was born."
+ },
+ "ap-label-en": {
+ "en": "country of birth"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The country in which the Person was born."
+ },
+ "derived": "false",
+ "destRole": "countryOfBirth",
+ "label": {
+ "en": "country of birth"
+ },
+ "sourceRole": "null",
+ "usage": {
+ "en": "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."
+ }
+ },
+ "generalization": [],
+ "inpackage": "UNKNOWN",
+ "label": {
+ "en": "country of birth"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "countryOfBirth",
+ "range": [
+ {
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Name": "Location",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ }
+ ],
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "@id": "http://www.w3.org/ns/person#placeOfBirth",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "EA-Guid": "{2F4217DC-565B-49da-9EBB-48719E9634B1}",
+ "ap-definition-en": {
+ "en": "The Location where the Person was born."
+ },
+ "ap-label-en": {
+ "en": "place of birth"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The Location where the Person was born."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "DestRoleTags": [
+ {
+ "key": "usageNote-en",
+ "note": "NOTE$ea_notes=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.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "place of birth",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://www.w3.org/ns/person#placeOfBirth",
+ "value": "NOTE"
+ },
+ {
+ "key": "definition-en",
+ "note": "The Location where the Person was born.",
+ "value": "NOTE"
+ }
+ ],
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{2F4217DC-565B-49da-9EBB-48719E9634B1}",
+ "EA-Name": "placeOfBirth",
+ "EA-Package": "",
+ "EA-Range": "Location",
+ "EA-Type": "connector",
+ "RangeData": {
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Name": "Location",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ },
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "note": "NOTE$ea_notes=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.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "place of birth",
+ "value": "NOTE"
+ },
+ {
+ "key": "uri",
+ "note": "http://www.w3.org/ns/person#placeOfBirth",
+ "value": "NOTE"
+ },
+ {
+ "key": "definition-en",
+ "note": "The Location where the Person was born.",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The Location where the Person was born."
+ },
+ "ap-label-en": {
+ "en": "place of birth"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The Location where the Person was born."
+ },
+ "derived": "false",
+ "destRole": "placeOfBirth",
+ "label": {
+ "en": "place of birth"
+ },
+ "sourceRole": "null",
+ "usage": {
+ "en": "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."
+ }
+ },
+ "generalization": [],
+ "inpackage": "UNKNOWN",
+ "label": {
+ "en": "place of birth"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "placeOfBirth",
+ "range": [
+ {
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Name": "Location",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ }
+ ],
+ "usage": {
+ "en": "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."
+ }
+ },
+ {
+ "@id": "http://xmlns.com/foaf/0.1/familyName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{96E7483C-255D-4df5-91F7-77B219146F13}",
+ "ap-definition-en": {
+ "en": "The hereditary surname of a family."
+ },
+ "ap-label-en": {
+ "en": "family name"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The hereditary surname of a family."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{96E7483C-255D-4df5-91F7-77B219146F13}",
+ "EA-Name": "familyName",
+ "EA-Package": "person",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://xmlns.com/foaf/0.1/familyName"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "family name"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The hereditary surname of a family."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "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\".",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The hereditary surname of a family."
+ },
+ "ap-label-en": {
+ "en": "family name"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The hereditary surname of a family."
+ },
+ "label": {
+ "en": "family name"
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "family name"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "familyName",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ {
+ "@id": "http://xmlns.com/foaf/0.1/givenName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "EA-Guid": "{DDF3ED17-7415-4c6c-B208-7B642496AD2D}",
+ "ap-definition-en": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "ap-label-en": {
+ "en": "given name"
+ },
+ "codelist": [],
+ "definition": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "domain": [
+ {
+ "EA-Name": "Person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "extra": {
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Guid": "{DDF3ED17-7415-4c6c-B208-7B642496AD2D}",
+ "EA-Name": "givenName",
+ "EA-Package": "person",
+ "EA-Range": "Text",
+ "EA-Type": "attribute",
+ "RangeData": {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://xmlns.com/foaf/0.1/givenName"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "given name"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The name(s) that identify the Person within a family with a common surname."
+ },
+ {
+ "key": "usageNote-en",
+ "note": "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\".",
+ "value": "NOTE"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "ap-label-en": {
+ "en": "given name"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "label": {
+ "en": "given name"
+ },
+ "usage": {
+ "en": "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\"."
+ }
+ },
+ "generalization": [],
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "given name"
+ },
+ "maxCardinality": "*",
+ "minCardinality": "0",
+ "name": "givenName",
+ "range": [
+ {
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "usage": {
+ "en": "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\"."
+ }
+ }
+ ],
+ "externals": [
+ {
+ "@id": "http://data.europa.eu/m8g/Evidence",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{F4749871-6F2D-4e38-B207-9CCACE847CF2}",
+ "ap-definition-en": {
+ "en": "Proof that a Requirement is met."
+ },
+ "ap-label-en": {
+ "en": "Evidence"
+ },
+ "definition": {
+ "en": "Proof that a Requirement is met."
+ },
+ "extra": {
+ "EA-Guid": "{F4749871-6F2D-4e38-B207-9CCACE847CF2}",
+ "EA-Name": "Evidence",
+ "EA-Package": "cv",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "CLASS",
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "note": "Proof that a Requirement is met.",
+ "value": "NOTE"
+ },
+ {
+ "key": "usageNote-en",
+ "note": "The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV).\r\n\r\nAlthough the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s).\r",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Evidence"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://data.europa.eu/m8g/Evidence"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "Proof that a Requirement is met."
+ },
+ "ap-label-en": {
+ "en": "Evidence"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "Proof that a Requirement is met."
+ },
+ "label": {
+ "en": "Evidence"
+ },
+ "parentclasses": "",
+ "usage": {
+ "en": "The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV).\r\n\r\nAlthough the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s).\r"
+ }
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Evidence"
+ },
+ "name": "Evidence",
+ "usage": {
+ "en": "The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV).\r\n\r\nAlthough the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s).\r"
+ }
+ },
+ {
+ "@id": "http://data.europa.eu/m8g/GenericDate",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "ap-definition-en": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ },
+ "ap-label-en": {
+ "en": "GenericDate"
+ },
+ "definition": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ },
+ "extra": {
+ "EA-Guid": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "EA-Name": "GenericDate",
+ "EA-Package": "DataTypes",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "DATATYPE",
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://data.europa.eu/m8g/GenericDate"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "GenericDate"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ },
+ {
+ "key": "literal",
+ "note": "null",
+ "value": "True"
+ },
+ {
+ "key": "class-usage-scope",
+ "note": "null",
+ "value": "datatype"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ },
+ "ap-label-en": {
+ "en": "GenericDate"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ },
+ "label": {
+ "en": "GenericDate"
+ },
+ "parentclasses": "",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "GenericDate"
+ },
+ "name": "Genericdate"
+ },
+ {
+ "@id": "http://data.europa.eu/p4s/ProofOfDomicile",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{4D66240C-3C6D-49b6-811C-65782288501B}",
+ "ap-definition-en": {
+ "en": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile)."
+ },
+ "ap-label-en": {
+ "en": "Proof of domicile"
+ },
+ "definition": {
+ "en": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile)."
+ },
+ "extra": {
+ "EA-Guid": "{4D66240C-3C6D-49b6-811C-65782288501B}",
+ "EA-Name": "ProofOfDomicile",
+ "EA-Package": "sdg",
+ "EA-Parents": "Evidence",
+ "EA-Parents2": [
+ {
+ "label": "Evidence",
+ "name": "Evidence",
+ "package": "cv",
+ "uri": "http://data.europa.eu/m8g/Evidence"
+ }
+ ],
+ "EA-Type": "CLASS",
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://data.europa.eu/p4s/ProofOfDomicile"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile)."
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Proof of domicile"
+ },
+ {
+ "key": "class-usage-scope",
+ "note": "null",
+ "value": "main"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile)."
+ },
+ "ap-label-en": {
+ "en": "Proof of domicile"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile)."
+ },
+ "label": {
+ "en": "Proof of domicile"
+ },
+ "parentclasses": "http://data.europa.eu/m8g/Evidence",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Proof of domicile"
+ },
+ "name": "ProofOfDomicile"
+ },
+ {
+ "@id": "http://purl.org/dc/terms/Location",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "ap-definition-en": {
+ "en": "An identifiable geographic place or named place."
+ },
+ "ap-label-en": {
+ "en": "Location"
+ },
+ "definition": {
+ "en": "An identifiable geographic place or named place."
+ },
+ "extra": {
+ "EA-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Name": "Location",
+ "EA-Package": "dct",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "CLASS",
+ "RawTags": [
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://purl.org/dc/terms/Location"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Location"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "An identifiable geographic place or named place."
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "An identifiable geographic place or named place."
+ },
+ "ap-label-en": {
+ "en": "Location"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "An identifiable geographic place or named place."
+ },
+ "label": {
+ "en": "Location"
+ },
+ "parentclasses": "",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Location"
+ },
+ "name": "Location"
+ },
+ {
+ "@id": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "ap-definition-en": {
+ "en": "The text data type is a combination of a string and a language identifier."
+ },
+ "ap-label-en": {
+ "en": "Text"
+ },
+ "definition": {
+ "en": "The text data type is a combination of a string and a language identifier."
+ },
+ "extra": {
+ "EA-Guid": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Name": "Text",
+ "EA-Package": "DataTypes",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "DATATYPE",
+ "RawTags": [
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Text"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The text data type is a combination of a string and a language identifier."
+ },
+ {
+ "key": "literal",
+ "note": "null",
+ "value": "true"
+ },
+ {
+ "key": "class-usage-scope",
+ "note": "null",
+ "value": "datatype"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The text data type is a combination of a string and a language identifier."
+ },
+ "ap-label-en": {
+ "en": "Text"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The text data type is a combination of a string and a language identifier."
+ },
+ "label": {
+ "en": "Text"
+ },
+ "parentclasses": "",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Text"
+ },
+ "name": "Text"
+ },
+ {
+ "@id": "http://www.w3.org/2000/01/rdf-schema#Literal",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{BEB2E07B-8BBD-4a89-B870-F21653DDEA3D}",
+ "ap-definition-en": {
+ "en": "The class of literal values, eg. textual strings and integers."
+ },
+ "ap-label-en": {
+ "en": "Literal"
+ },
+ "definition": {
+ "en": "The class of literal values, eg. textual strings and integers."
+ },
+ "extra": {
+ "EA-Guid": "{BEB2E07B-8BBD-4a89-B870-F21653DDEA3D}",
+ "EA-Name": "Literal",
+ "EA-Package": "DataTypes",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "DATATYPE",
+ "RawTags": [
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Literal"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "The class of literal values, eg. textual strings and integers."
+ },
+ {
+ "key": "literal",
+ "note": "null",
+ "value": "true"
+ },
+ {
+ "key": "class-usage-scope",
+ "note": "null",
+ "value": "datatype"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "The class of literal values, eg. textual strings and integers."
+ },
+ "ap-label-en": {
+ "en": "Literal"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "The class of literal values, eg. textual strings and integers."
+ },
+ "label": {
+ "en": "Literal"
+ },
+ "parentclasses": "",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Literal"
+ },
+ "name": "Literal"
+ },
+ {
+ "@id": "http://www.w3.org/2004/02/skos/core#Concept",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "ap-definition-en": {
+ "en": "An idea or notion; a unit of thought."
+ },
+ "ap-label-en": {
+ "en": "Code"
+ },
+ "definition": {
+ "en": "An idea or notion; a unit of thought."
+ },
+ "extra": {
+ "EA-Guid": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "EA-Name": "Code",
+ "EA-Package": "DataTypes",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "DATATYPE",
+ "RawTags": [
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Code"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/2004/02/skos/core#Concept"
+ },
+ {
+ "key": "definition-en",
+ "note": "null",
+ "value": "An idea or notion; a unit of thought."
+ },
+ {
+ "key": "class-usage-scope",
+ "note": "null",
+ "value": "datatype"
+ }
+ ],
+ "Scope": "NOTHING",
+ "ap-codelist": "",
+ "ap-definition-en": {
+ "en": "An idea or notion; a unit of thought."
+ },
+ "ap-label-en": {
+ "en": "Code"
+ },
+ "ap-usageNote-en": "",
+ "definition": {
+ "en": "An idea or notion; a unit of thought."
+ },
+ "label": {
+ "en": "Code"
+ },
+ "parentclasses": "",
+ "usage": ""
+ },
+ "inpackage": "OTHER_PACKAGE",
+ "label": {
+ "en": "Code"
+ },
+ "name": "Code"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#Address",
+ "@type": "http://www.w3.org/2002/07/owl#Class",
+ "EA-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "ap-definition-en": {
+ "en": "A spatial object that in a human-readable way identifies a fixed location."
+ },
+ "ap-label-en": {
+ "en": "Address"
+ },
+ "definition": {
+ "en": "A spatial object that in a human-readable way identifies a fixed location."
+ },
+ "extra": {
+ "EA-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Name": "Address",
+ "EA-Package": "locn",
+ "EA-Parents": "",
+ "EA-Parents2": [],
+ "EA-Type": "CLASS",
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "note": "A spatial object that in a human-readable way identifies a fixed location.",
+ "value": "NOTE"
+ },
+ {
+ "key": "label-en",
+ "note": "null",
+ "value": "Address"
+ },
+ {
+ "key": "uri",
+ "note": "null",
+ "value": "http://www.w3.org/ns/locn#Address"
+ },
+ {
+ "key": "usageNote-en",
+ "note": "\r\n
\r\nThe 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.\r\n\r\n
\r\nThe 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.\r\n\r\n
\r\nThe 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.\r\n\r\n
\r\nThe 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.\r\n\r\n
\r\nThe 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.\r\n\r\n
\r\nThe 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.\r\n\r\n
"
+ },
+ "ap-label-en": {
+ "en": "date of birth"
+ },
+ "definition": {
+ "en": "The point in time on which the Person was born."
+ },
+ "label": {
+ "en": "date of birth"
+ },
+ "extra": {
+ "EA-Name": "dateOfBirth",
+ "EA-Guid": "{0E297AAE-E6BA-42a0-A308-FC513C2D5EB1}",
+ "EA-Package": "person",
+ "EA-Type": "attribute",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "GenericDate",
+ "RangeData": {
+ "EA-Name": "GenericDate",
+ "EA-GUID": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "EA-Package": "DataTypes",
+ "uri": "http://data.europa.eu/m8g/GenericDate"
+ },
+ "label": {
+ "en": "date of birth"
+ },
+ "definition": {
+ "en": "The point in time on which the Person was born."
+ },
+ "usage": {
+ "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n\r\n
"
+ },
+ "ap-label-en": {
+ "en": "date of birth"
+ },
+ "ap-definition-en": {
+ "en": "The point in time on which the Person was born."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://data.europa.eu/m8g/birthDate",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "date of birth",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The point in time on which the Person was born.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n\r\n
"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "GenericDate",
+ "EA-GUID": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "EA-Package": "DataTypes",
+ "uri": "http://data.europa.eu/m8g/GenericDate"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://data.europa.eu/m8g/domicile",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "name": "domicile",
+ "inpackage": "UNKNOWN",
+ "ap-definition-en": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "ap-label-en": {
+ "en": "domicile"
+ },
+ "definition": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "label": {
+ "en": "domicile"
+ },
+ "extra": {
+ "EA-Name": "domicile",
+ "EA-Guid": "{E2F8EB6A-D959-47b5-A56A-E8B7947A2119}",
+ "derived": "false",
+ "EA-Package": "",
+ "EA-Type": "connector",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Address",
+ "RangeData": {
+ "EA-Name": "Address",
+ "EA-GUID": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Package": "locn",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ },
+ "sourceRole": "null",
+ "destRole": "domicile",
+ "label": {
+ "en": "domicile"
+ },
+ "definition": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "usage": "",
+ "ap-label-en": {
+ "en": "domicile"
+ },
+ "ap-definition-en": {
+ "en": "The place that the Person treats as permanent home."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The place that the Person treats as permanent home."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "domicile"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://data.europa.eu/m8g/domicile"
+ }
+ ],
+ "DestRoleTags": [
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The place that the Person treats as permanent home."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "domicile"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://data.europa.eu/m8g/domicile"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Address",
+ "EA-GUID": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Package": "locn",
+ "uri": "http://www.w3.org/ns/locn#Address"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://data.europa.eu/m8g/sex",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "name": "sex",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The organism's biological sex."
+ },
+ "usage": {
+ "en": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ },
+ "ap-label-en": {
+ "en": "sex"
+ },
+ "definition": {
+ "en": "The organism's biological sex."
+ },
+ "label": {
+ "en": "sex"
+ },
+ "extra": {
+ "EA-Name": "sex",
+ "EA-Guid": "{AB3326D0-B0BD-4fc3-AFEA-A3120025327D}",
+ "EA-Package": "person",
+ "EA-Type": "attribute",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Code",
+ "RangeData": {
+ "EA-Name": "Code",
+ "EA-GUID": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/2004/02/skos/core#Concept"
+ },
+ "label": {
+ "en": "sex"
+ },
+ "definition": {
+ "en": "The organism's biological sex."
+ },
+ "usage": {
+ "en": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ },
+ "ap-label-en": {
+ "en": "sex"
+ },
+ "ap-definition-en": {
+ "en": "The organism's biological sex."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://data.europa.eu/m8g/sex",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "sex",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The organism's biological sex.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "The recommended controlled vocabulary for this property is the sex authority table of the Publications Office."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Code",
+ "EA-GUID": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/2004/02/skos/core#Concept"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://purl.org/dc/terms/subject",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "name": "isAbout",
+ "inpackage": "UNKNOWN",
+ "ap-definition-en": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "ap-label-en": {
+ "en": "is about"
+ },
+ "definition": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "label": {
+ "en": "is about"
+ },
+ "extra": {
+ "EA-Name": "isAbout",
+ "EA-Guid": "{9E77DA77-7164-424f-811A-260426ACCF6A}",
+ "derived": "false",
+ "EA-Package": "",
+ "EA-Type": "connector",
+ "EA-Domain": "ProofOfDomicile",
+ "EA-Domain-Guid": "{4D66240C-3C6D-49b6-811C-65782288501B}",
+ "EA-Range": "Person",
+ "RangeData": {
+ "EA-Name": "Person",
+ "EA-GUID": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Package": "person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ },
+ "sourceRole": "null",
+ "destRole": "isAbout",
+ "label": {
+ "en": "is about"
+ },
+ "definition": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "usage": "",
+ "ap-label-en": {
+ "en": "is about"
+ },
+ "ap-definition-en": {
+ "en": "Agent that is the subject in the provided Evidence."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "Agent that is the subject in the provided Evidence."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "is about"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://purl.org/dc/terms/subject"
+ }
+ ],
+ "DestRoleTags": [
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "Agent that is the subject in the provided Evidence."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "is about"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://purl.org/dc/terms/subject"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://data.europa.eu/p4s/ProofOfDomicile",
+ "EA-Name": "ProofOfDomicile"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Person",
+ "EA-GUID": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Package": "person",
+ "uri": "http://www.w3.org/ns/person#Person"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "1",
+ "maxCardinality": "1"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#addressArea",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "addressArea",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "usage": {
+ "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ },
+ "ap-label-en": {
+ "en": "address area"
+ },
+ "definition": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "label": {
+ "en": "address area"
+ },
+ "extra": {
+ "EA-Name": "addressArea",
+ "EA-Guid": "{42A3291F-2C59-4432-9003-3E6719430A52}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "address area"
+ },
+ "definition": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "usage": {
+ "en": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ },
+ "ap-label-en": {
+ "en": "address area"
+ },
+ "ap-definition-en": {
+ "en": "The name of a geographic area that groups Addresses."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "This would typically be part of a city, a neighbourhood or village, e.g. Montmartre. Address area is not an administrative unit."
+ },
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#addressArea",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "address area",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The name of a geographic area that groups Addresses.",
+ "note": "null"
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#adminUnitL1",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "administrativeUnitLevel1",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 1"
+ },
+ "definition": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "label": {
+ "en": "administrative unit level 1"
+ },
+ "extra": {
+ "EA-Name": "adminUnitL1",
+ "EA-Guid": "{EFCE2B24-F154-487f-BDC4-0C162CA80935}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "administrative unit level 1"
+ },
+ "definition": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 1"
+ },
+ "ap-definition-en": {
+ "en": "The name of the uppermost level of the address, almost always a country."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "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."
+ },
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#adminUnitL1",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "administrative unit level 1",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The name of the uppermost level of the address, almost always a country."
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#adminUnitL2",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "administrativeUnitLevel2",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "usage": {
+ "en": "Values could be a region or province, more granular than level 1."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 2"
+ },
+ "definition": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "label": {
+ "en": "administrative unit level 2"
+ },
+ "extra": {
+ "EA-Name": "adminUnitL2",
+ "EA-Guid": "{958C6E0B-EB04-416c-BC1A-5B3459FD355A}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "administrative unit level 2"
+ },
+ "definition": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "usage": {
+ "en": "Values could be a region or province, more granular than level 1."
+ },
+ "ap-label-en": {
+ "en": "administrative unit level 2"
+ },
+ "ap-definition-en": {
+ "en": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "Values could be a region or province, more granular than level 1."
+ },
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#adminUnitL2",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "administrative unit level 2",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities."
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#geographicName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "geographicName",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "A textual description for a Location."
+ },
+ "usage": {
+ "en": "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.\r\n\r\nThe 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."
+ },
+ "ap-label-en": {
+ "en": "geographic name"
+ },
+ "definition": {
+ "en": "A textual description for a Location."
+ },
+ "label": {
+ "en": "geographic name"
+ },
+ "extra": {
+ "EA-Name": "geographicName",
+ "EA-Guid": "{47322390-B650-43d1-927D-B3160DB699C8}",
+ "EA-Package": "dct",
+ "EA-Type": "attribute",
+ "EA-Domain": "Location",
+ "EA-Domain-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "geographic name"
+ },
+ "definition": {
+ "en": "A textual description for a Location."
+ },
+ "usage": {
+ "en": "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.\r\n\r\nThe 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."
+ },
+ "ap-label-en": {
+ "en": "geographic name"
+ },
+ "ap-definition-en": {
+ "en": "A textual description for a Location."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#geographicName",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "geographic name",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "A textual description for a Location.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "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.\r\n\r\nThe 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."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://purl.org/dc/terms/Location",
+ "EA-Name": "Location"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#locatorDesignator",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "locatorDesignator",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "locator designator"
+ },
+ "definition": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "label": {
+ "en": "locator designator"
+ },
+ "extra": {
+ "EA-Name": "locatorDesignator",
+ "EA-Guid": "{509BF1D0-4E76-4bee-B17F-AC883B236548}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Literal",
+ "RangeData": {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ },
+ "label": {
+ "en": "locator designator"
+ },
+ "definition": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "locator designator"
+ },
+ "ap-definition-en": {
+ "en": "A number or sequence of characters that uniquely identifies the locator within the relevant scope."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "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\"."
+ },
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#locatorDesignator",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "locator designator",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "A number or sequence of characters that uniquely identifies the locator within the relevant scope.",
+ "note": "null"
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#postCode",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "postCode",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ },
+ "ap-label-en": {
+ "en": "post code"
+ },
+ "definition": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "label": {
+ "en": "post code"
+ },
+ "extra": {
+ "EA-Name": "postCode",
+ "EA-Guid": "{2EF6D767-8E3F-461c-AC37-772819BA21B6}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Literal",
+ "RangeData": {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ },
+ "label": {
+ "en": "post code"
+ },
+ "definition": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\"."
+ },
+ "ap-label-en": {
+ "en": "post code"
+ },
+ "ap-definition-en": {
+ "en": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "Post codes are common elements in many countries' postal address systems. One of the many post codes of Paris is for example \"75000\".",
+ "note": "null"
+ },
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#postCode",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "post code",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Literal",
+ "EA-Package": "",
+ "uri": "http://www.w3.org/2000/01/rdf-schema#Literal"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#postName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "postName",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Usually a city, for example \"Paris\"."
+ },
+ "ap-label-en": {
+ "en": "post name"
+ },
+ "definition": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "label": {
+ "en": "post name"
+ },
+ "extra": {
+ "EA-Name": "postName",
+ "EA-Guid": "{F0699A53-4F4C-4e83-AF49-34E33744BF36}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "post name"
+ },
+ "definition": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "usage": {
+ "en": "Usually a city, for example \"Paris\"."
+ },
+ "ap-label-en": {
+ "en": "post name"
+ },
+ "ap-definition-en": {
+ "en": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#postName",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "post name",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "A name created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points."
+ },
+ {
+ "key": "usageNote-en",
+ "value": "Usually a city, for example \"Paris\".",
+ "note": "null"
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/locn#thoroughfare",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "thoroughfare",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "usage": {
+ "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ },
+ "ap-label-en": {
+ "en": "thoroughfare"
+ },
+ "definition": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "label": {
+ "en": "thoroughfare"
+ },
+ "extra": {
+ "EA-Name": "thoroughfare",
+ "EA-Guid": "{2D384BE4-CFED-4f52-B1EC-3C84511ACCC6}",
+ "EA-Package": "locn",
+ "EA-Type": "attribute",
+ "EA-Domain": "Address",
+ "EA-Domain-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "thoroughfare"
+ },
+ "definition": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "usage": {
+ "en": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\"."
+ },
+ "ap-label-en": {
+ "en": "thoroughfare"
+ },
+ "ap-definition-en": {
+ "en": "The name of a passage or way through from one location to another."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://www.w3.org/ns/locn#thoroughfare",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "thoroughfare",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The name of a passage or way through from one location to another.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "A thoroughfare is usually a street, but it might be a waterway or some other feature. For example, \"Avenue des Champs-Élysées\".",
+ "note": "null"
+ },
+ {
+ "key": "property-usage-scope",
+ "value": "optional",
+ "note": "null"
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/locn#Address",
+ "EA-Name": "Address"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/person#countryOfBirth",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "name": "countryOfBirth",
+ "inpackage": "UNKNOWN",
+ "ap-definition-en": {
+ "en": "The country in which the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "country of birth"
+ },
+ "definition": {
+ "en": "The country in which the Person was born."
+ },
+ "label": {
+ "en": "country of birth"
+ },
+ "extra": {
+ "EA-Name": "countryOfBirth",
+ "EA-Guid": "{C58092CC-C21A-4932-A0EA-65E8519BA158}",
+ "derived": "false",
+ "EA-Package": "",
+ "EA-Type": "connector",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Location",
+ "RangeData": {
+ "EA-Name": "Location",
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ },
+ "sourceRole": "null",
+ "destRole": "countryOfBirth",
+ "label": {
+ "en": "country of birth"
+ },
+ "definition": {
+ "en": "The country in which the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "country of birth"
+ },
+ "ap-definition-en": {
+ "en": "The country in which the Person was born."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "NOTE$ea_notes=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."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "country of birth"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://www.w3.org/ns/person#countryOfBirth"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The country in which the Person was born."
+ }
+ ],
+ "DestRoleTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "NOTE$ea_notes=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."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "country of birth"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://www.w3.org/ns/person#countryOfBirth"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The country in which the Person was born."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Location",
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://www.w3.org/ns/person#placeOfBirth",
+ "@type": "http://www.w3.org/2002/07/owl#ObjectProperty",
+ "name": "placeOfBirth",
+ "inpackage": "UNKNOWN",
+ "ap-definition-en": {
+ "en": "The Location where the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "place of birth"
+ },
+ "definition": {
+ "en": "The Location where the Person was born."
+ },
+ "label": {
+ "en": "place of birth"
+ },
+ "extra": {
+ "EA-Name": "placeOfBirth",
+ "EA-Guid": "{2F4217DC-565B-49da-9EBB-48719E9634B1}",
+ "derived": "false",
+ "EA-Package": "",
+ "EA-Type": "connector",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Location",
+ "RangeData": {
+ "EA-Name": "Location",
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ },
+ "sourceRole": "null",
+ "destRole": "placeOfBirth",
+ "label": {
+ "en": "place of birth"
+ },
+ "definition": {
+ "en": "The Location where the Person was born."
+ },
+ "usage": {
+ "en": "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."
+ },
+ "ap-label-en": {
+ "en": "place of birth"
+ },
+ "ap-definition-en": {
+ "en": "The Location where the Person was born."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "NOTE$ea_notes=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."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "place of birth"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://www.w3.org/ns/person#placeOfBirth"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The Location where the Person was born."
+ }
+ ],
+ "DestRoleTags": [
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "NOTE$ea_notes=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."
+ },
+ {
+ "key": "label-en",
+ "value": "NOTE",
+ "note": "place of birth"
+ },
+ {
+ "key": "uri",
+ "value": "NOTE",
+ "note": "http://www.w3.org/ns/person#placeOfBirth"
+ },
+ {
+ "key": "definition-en",
+ "value": "NOTE",
+ "note": "The Location where the Person was born."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Location",
+ "EA-GUID": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "EA-Package": "dct",
+ "uri": "http://purl.org/dc/terms/Location"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://xmlns.com/foaf/0.1/familyName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "familyName",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The hereditary surname of a family."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "family name"
+ },
+ "definition": {
+ "en": "The hereditary surname of a family."
+ },
+ "label": {
+ "en": "family name"
+ },
+ "extra": {
+ "EA-Name": "familyName",
+ "EA-Guid": "{96E7483C-255D-4df5-91F7-77B219146F13}",
+ "EA-Package": "person",
+ "EA-Type": "attribute",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "family name"
+ },
+ "definition": {
+ "en": "The hereditary surname of a family."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "family name"
+ },
+ "ap-definition-en": {
+ "en": "The hereditary surname of a family."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://xmlns.com/foaf/0.1/familyName",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "family name",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The hereditary surname of a family.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "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\"."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ },
+ {
+ "@id": "http://xmlns.com/foaf/0.1/givenName",
+ "@type": "http://www.w3.org/2002/07/owl#DatatypeProperty",
+ "name": "givenName",
+ "inpackage": "OTHER_PACKAGE",
+ "ap-definition-en": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "given name"
+ },
+ "definition": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "label": {
+ "en": "given name"
+ },
+ "extra": {
+ "EA-Name": "givenName",
+ "EA-Guid": "{DDF3ED17-7415-4c6c-B208-7B642496AD2D}",
+ "EA-Package": "person",
+ "EA-Type": "attribute",
+ "EA-Domain": "Person",
+ "EA-Domain-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "EA-Range": "Text",
+ "RangeData": {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ },
+ "label": {
+ "en": "given name"
+ },
+ "definition": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "usage": {
+ "en": "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\"."
+ },
+ "ap-label-en": {
+ "en": "given name"
+ },
+ "ap-definition-en": {
+ "en": "The name(s) that identify the Person within a family with a common surname."
+ },
+ "ap-usageNote-en": "",
+ "ap-codelist": "",
+ "RawTags": [
+ {
+ "key": "uri",
+ "value": "http://xmlns.com/foaf/0.1/givenName",
+ "note": "null"
+ },
+ {
+ "key": "label-en",
+ "value": "given name",
+ "note": "null"
+ },
+ {
+ "key": "definition-en",
+ "value": "The name(s) that identify the Person within a family with a common surname.",
+ "note": "null"
+ },
+ {
+ "key": "usageNote-en",
+ "value": "NOTE",
+ "note": "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\"."
+ }
+ ],
+ "Scope": "NOTHING"
+ },
+ "codelist": [],
+ "domain": [
+ {
+ "uri": "http://www.w3.org/ns/person#Person",
+ "EA-Name": "Person"
+ }
+ ],
+ "range": [
+ {
+ "EA-Name": "Text",
+ "EA-GUID": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "EA-Package": "DataTypes",
+ "uri": "http://www.w3.org/1999/02/22-rdf-syntax-ns#langString"
+ }
+ ],
+ "generalization": [],
+ "minCardinality": "0",
+ "maxCardinality": "*"
+ }
+ ],
+ "name": "proofofallresidence",
+ "type": "ap",
+ "eap": "OOTS_ProofOfAllResidence.eap",
+ "diagram": "ProofOfAllResidence",
+ "template": "ProofOfAllResience_en.j2",
+ "title": "Proof of residence (all registered addresses)",
+ "publication-state": "Draft",
+ "publication-date": "2024-10-29",
+ "contributors-file": "stakeholders.csv",
+ "contributors-column": "OOTS",
+ "site": "site-skeleton/proofofallresidence",
+ "repourl": "https://code.europa.eu/oots/tdd/data_models/Evidence/ProofOfAllResidence/tree/master/releases/0.0.1",
+ "feedbackurl": "https://ec.europa.eu/digital-building-blocks/wikis/display/SDGOO/Discussion+Items+-+EM?src=contextnavpagetreemode",
+ "versionurl": "https://code.europa.eu/oots/tdd/data_models/Evidence/ProofOfAllResidence/tree/master/releases/0.0.1",
+ "standaardregisterurl": "https://code.europa.eu/oots/tdd/data_models/Evidence/ProofOfAllResidence/tree/master/releases/0.0.1/Changelog.md",
+ "translation": [
+ {
+ "language": "en",
+ "template": "ProofOfAllResidence_en.j2",
+ "title": "Proof of residence (all registered addresses)",
+ "translationjson": "ProofOfAllResidence_en.json",
+ "mergefile": "ProofOfAllResidence_en_merged.jsonld"
+ }
+ ],
+ "toolchainversion": "3",
+ "documentconfig": {
+ "statuslabel": "Draft",
+ "editorDocumentroot": "https://data-models-oots-tdd-8b6791fd33fcb1f29c7d6ad9c6173ba55d28c0a5f9.pages.code.europa.eu/Evidence/ProofOfAllResidence/releases/0.0.1"
+ },
+ "config": "config/config-ap.json",
+ "branchtag": "oots",
+ "dummy": "2",
+ "filename": "config/oots.json",
+ "navigation": {
+ "prev": "https://data-models-oots-tdd-8b6791fd33fcb1f29c7d6ad9c6173ba55d28c0a5f9.pages.code.europa.eu/Evidence/ProofOfAllResidence/releases/0.0.1",
+ "self": "https://data-models-oots-tdd-8b6791fd33fcb1f29c7d6ad9c6173ba55d28c0a5f9.pages.code.europa.eu/Evidence/ProofOfAllResidence/releases/0.0.1"
+ },
+ "repository": "git@uri.semic.eu-thema:SEMICeu/uri.semic.eu-thema.git",
+ "urlref": "/OOTS/ProofOfAllResidence/releases/0.0.1/",
+ "documentcommit": "d4cf057a731bf3011a881a4c2f9138b07b9ab0fa",
+ "toolchaincommit": "381c63dac19f2bfcc92dcc246da2619aa762bf4e",
+ "hostname": "https://semiceu.github.io"
+}
diff --git a/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/proofofallresidence_de.json b/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/proofofallresidence_de.json
new file mode 100644
index 000000000..41a1a846e
--- /dev/null
+++ b/report/OOTS/ProofOfAllResidence/releases/0.0.1/translation/proofofallresidence_de.json
@@ -0,0 +1,377 @@
+{
+ "baseURI": "https://data.europa.eu/m8g/",
+ "classes": [],
+ "properties": [],
+ "externals": [
+ {
+ "EA-Guid": "{F4749871-6F2D-4e38-B207-9CCACE847CF2}",
+ "name": "Evidence",
+ "label": {
+ "en": "Evidence",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "Proof that a Requirement is met.",
+ "de": "Enter your translation here"
+ },
+ "usage": {
+ "en": "The Evidence class is defined in the Core Criterion and Core Evidence Vocabulary (CCCEV).\r\n\r\nAlthough the wording of the definition is different, the semantics are an exact match for CPSV's Input class which it replaces.\r\n\r\nEvidence can be any resource - document, artefact - anything needed for executing the Public Service. In the context of Public Services, Evidence is usually administrative documents or completed application forms. A specific Public Service may require the presence of certain Evidence or combinations of Evidence in order to be delivered.\r\n\r\nIn some cases, the Output of one service will be Evidence for another service. Such relationships should be described in the associated Rule(s).\r",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "name": "Genericdate",
+ "label": {
+ "en": "GenericDate",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{4D66240C-3C6D-49b6-811C-65782288501B}",
+ "name": "ProofOfDomicile",
+ "label": {
+ "en": "Proof of domicile",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "Request for evidence proving the address of the place that the person (evidence subject) considers currently as their permanent home (domicile).",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "name": "Location",
+ "label": {
+ "en": "Location",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "An identifiable geographic place or named place.",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "name": "Text",
+ "label": {
+ "en": "Text",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "The text data type is a combination of a string and a language identifier.",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{BEB2E07B-8BBD-4a89-B870-F21653DDEA3D}",
+ "name": "Literal",
+ "label": {
+ "en": "Literal",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "The class of literal values, eg. textual strings and integers.",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{C819F639-92F4-4235-BE20-2252B3AAC098}",
+ "name": "Code",
+ "label": {
+ "en": "Code",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "An idea or notion; a unit of thought.",
+ "de": "Enter your translation here"
+ }
+ },
+ {
+ "EA-Guid": "{650BCC62-B5E6-4070-8DC6-A39F0953E191}",
+ "name": "Address",
+ "label": {
+ "en": "Address",
+ "de": "Enter your translation here"
+ },
+ "definition": {
+ "en": "A spatial object that in a human-readable way identifies a fixed location.",
+ "de": "Enter your translation here"
+ },
+ "usage": {
+ "en": "\r\n
\r\nThe 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.\r\n
- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n
\r\nAn \"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.\"\r\n
\r\n\r\n\r\nThe 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.\r\n
\r\n\r\n\r\nThis 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\r\nproperties, we add two further properties:\r\n
- \r\n
- full address (the complete address as a formatted string) \r\n
- addressID (a unique identifier for the address) \r\n
\r\nThe 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.\r\n
\r\n\r\nThis class belongs to Core Location Vocabulary", + "fr": "Enter your translation here" + } + }, + { + "EA-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}", + "name": "Person", + "label": { + "en": "Person", + "fr": "Enter your translation here" + }, + "definition": { + "en": "A individual human being who may be dead or alive, but not imaginary.", + "fr": "Enter your translation here" + }, + "usage": { + "en": "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.", + "fr": "Enter your translation here" + } + } + ], + "externalproperties": [ + { + "EA-Guid": "{0E297AAE-E6BA-42a0-A308-FC513C2D5EB1}", + "name": "dateOfBirth", + "label": { + "en": "date of birth", + "fr": "Enter your translation here" + }, + "definition": { + "en": "The point in time on which the Person was born.", + "fr": "Enter your translation here" + }, + "usage": { + "en": "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n- \r\n
- 1980-09-16^^xs:date \r\n
- 1980-09^^xs:gYearMonth \r\n
- 1980^^xs:gYear \r\n