+ 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-11-18. +
++ 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 nationality |
+
+ The main entities are supported by:
+
+ |
+ Evidence Type |
+ Location |
+ Person |
+
+ And supported by these datatypes:
+
+ | GenericDate | Text |
+
+
+ 
+
+
+
+
+ + Main Entities +
+The main entities are those that form the core of the Application Profile. + + + + + + + + + + ++ Proof of nationality + +
+ + +-
+
- + Definition + +
- + Request for evidence regarding the nationality of the person (evidence subject). + + + + +
-
+ Subclass of
+
- +
- Evidence Type + + + +
- + 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. + + + + + ++ Evidence Type + +
+ + +-
+
- + Definition + +
- + Information about the characteristics of an Evidence. + + + +
- + Usage Note + +
- + The Evidence Type and the characteristics it describes are not concrete individual responses to a Requirement (i.e. Evidence), but descriptions about the desired form, content, source and/or other characteristics that an actual response should have and provide (e.g. membership of a class of Evidences). + + + +
- + 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 + , family name + , given name + , place of birth + . + + +
+
+
+
+
+
+
+| + | ++ Property + | ++ Range + | ++ Card + | ++ Definition + | ++ Usage + | + +|
|---|---|---|---|---|---|---|
|
+
+
+
+
+ |
+ + + country of birth + | ++ + + Location + + + | ++ 0..* + | ++ The country in which the Person was born. + | ++ The Location Class has two properties: a Geographic Name and a Geographic Identifier. Plain codes like "DE" should be provided as values for Geographical Names whereas URIs should be provided as value of the Geographical Identifier. Ideally, provide both. Providing a simple country name is problematic and should be avoided whereas using a standardised system that allows the use of a code list for country names has a lot of potential for increasing semantic interoperability. Known diversity that one has to deal with when exchanging country names between different communication partners without relying on an agreed code list are: (a) long form vs. short form of a country name (e.g. Federal Republic of Germany vs. Germany), (b) different languages (Italy vs. Italia), (c) historic name vs. current name (Burma vs. Myanmar), (d) ambiguity of similar sounding countries (Republic of the Congo vs. Democratic Republic of the Congo). The Publications Office of the European Union recommends and uses ISO 3166-1 codes for countries in all cases except two: use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; use 'EL' in preference to the ISO 3166 code GR for Greece. See Publications Office list of countries for details of the OPOCE's full list of countries, codes, currencies and more. Where a country has changed its name or no longer exists (such as Czechoslovakia, Yugoslavia etc.) use the ISO 3166-3 code. + | + ++ + | +
|
+
+
+
+
+ |
+ + + date of birth + | ++ + + GenericDate + + + | ++ 0..* + | ++ The point in time on which the Person was born. + | +
+ The date of birth could be expressed as date, gYearMonth or gYear, example:
+
|
+
+ + + | +
|
+
+
+
+
+ |
+ + + family name + | ++ + + Text + + + | ++ 0..* + | ++ The hereditary surname of a family. + | ++ Usually referring to a group of people related by blood, marriage or adoption. This attribute also carries prefixes or suffixes which are part of the family name, e.g. "de Boer", "van de Putte", "von und zu Orlow". Multiple family names, such as are commonly found in Hispanic countries, are recorded in the single family name property so that, for example, Miguel de Cervantes Saavedra's family name would be recorded as "de Cervantes Saavedra". + | + ++ + | +
|
+
+
+
+
+ |
+ + + given name + | ++ + + Text + + + | ++ 0..* + | ++ The name(s) that identify the Person within a family with a common surname. + | ++ Usually a first name or forename. Given to a person by his or her parents at birth or legally recognised as 'given names' through a formal process. All given names are ordered in one property so that, for example, the given name for Johann Sebastian Bach is "Johann Sebastian". + | + ++ + | +
|
+
+
+
+
+ |
+ + + place of birth + | ++ + + Location + + + | ++ 0..* + | ++ The Location where the Person was born. + | ++ The Place of Birth and Place of Death are given using the Location class which is associated via the appropriate relationship. The Location Class has two properties: (1) the geographic name of the place, which is given as a string such as "Amsterdam" or "Valetta" and (2) an identifier, such as a geonames URI http://sws.geonames.org/2759794 (which identifies Amsterdam) or http://sws.geonames.org/2562305 (which identifies Valetta). The use of identifiers is preferred as these are unambiguous, however, public sector data typically uses simple names to record places and this is fully supported. + | + ++ + | +
+ Datatypes +
+ + The following datatypes are used within this specification. + +| + | ++ Class + | ++ Definition + | +
|---|---|---|
|
+
+
+
+ |
+
+
+ GenericDate
+
+
+ | + The date data type is the union of xs:date, xs:gYearMonth and xs:gYear + |
|
+
+
+
+ |
+
+
+ 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 Nationality. + + +JSON-LD context file
+ + One common technical question is the format in which the data is being exchanged. + For conformance with the Proof Of Nationality, 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 Nationality, 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 Nationality is available here. + + +UML representation
+ The UML representation from which the Proof Of Nationality 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 |
|---|---|---|---|---|
| Evidence Type | +http://data.europa.eu/m8g/EvidenceType |
+ + | + | + |
| Location | +http://purl.org/dc/terms/Location |
+ + | geographic name | +http://www.w3.org/ns/locn#geographicName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | country of birth | +http://www.w3.org/ns/person#countryOfBirth |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | date of birth | +http://data.europa.eu/m8g/birthDate |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | family name | +http://xmlns.com/foaf/0.1/familyName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | given name | +http://xmlns.com/foaf/0.1/givenName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | place of birth | +http://www.w3.org/ns/person#placeOfBirth |
+
| Proof of nationality | +http://data.europa.eu/p4s/ProofOfNationality |
+ + | is about | +http://purl.org/dc/terms/subject |
+
Feedback
+ ++ Please provide feedback on the general 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-11-18. +
++ 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 nationality |
+
+ The main entities are supported by:
+
+ |
+ Evidence Type |
+ Location |
+ Person |
+
+ And supported by these datatypes:
+
+ | GenericDate | Text |
+
+
+
+
+
+
+
+ + Main Entities +
+The main entities are those that form the core of the Application Profile. + + + + + + + + + + ++ Proof of nationality + +
+ + +-
+
- + Definition + +
- + Request for evidence regarding the nationality of the person (evidence subject). + + + + +
-
+ Subclass of
+
- +
- Evidence Type + + + +
- + Properties + + +
- + For this entity the following properties are defined: is about + . + + +
+
+
+
+
+
+
+| + | ++ Property + | ++ Range + | ++ Card + | ++ Definition + | ++ Usage + | + +|
|---|---|---|---|---|---|---|
|
+
+
+
+
+ |
+ + + is about + | ++ + + Person + + + | ++ 1 + | ++ Agent that is the subject in the provided Evidence. + | ++ + | + ++ + | +
+ Supportive Entities +
+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. + + + + + ++ Evidence Type + +
+ + +-
+
- + Definition + +
- + Information about the characteristics of an Evidence. + + + +
- + Usage Note + +
- + The Evidence Type and the characteristics it describes are not concrete individual responses to a Requirement (i.e. Evidence), but descriptions about the desired form, content, source and/or other characteristics that an actual response should have and provide (e.g. membership of a class of Evidences). + + + +
- + 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 + , family name + , given name + , place of birth + . + + +
+
+
+
+
+
+
+| + | ++ Property + | ++ Range + | ++ Card + | ++ Definition + | ++ Usage + | + +|
|---|---|---|---|---|---|---|
|
+
+
+
+
+ |
+ + + country of birth + | ++ + + Location + + + | ++ 0..* + | ++ The country in which the Person was born. + | ++ The Location Class has two properties: a Geographic Name and a Geographic Identifier. Plain codes like "DE" should be provided as values for Geographical Names whereas URIs should be provided as value of the Geographical Identifier. Ideally, provide both. Providing a simple country name is problematic and should be avoided whereas using a standardised system that allows the use of a code list for country names has a lot of potential for increasing semantic interoperability. Known diversity that one has to deal with when exchanging country names between different communication partners without relying on an agreed code list are: (a) long form vs. short form of a country name (e.g. Federal Republic of Germany vs. Germany), (b) different languages (Italy vs. Italia), (c) historic name vs. current name (Burma vs. Myanmar), (d) ambiguity of similar sounding countries (Republic of the Congo vs. Democratic Republic of the Congo). The Publications Office of the European Union recommends and uses ISO 3166-1 codes for countries in all cases except two: use 'UK' in preference to the ISO 3166 code GB for the United Kingdom; use 'EL' in preference to the ISO 3166 code GR for Greece. See Publications Office list of countries for details of the OPOCE's full list of countries, codes, currencies and more. Where a country has changed its name or no longer exists (such as Czechoslovakia, Yugoslavia etc.) use the ISO 3166-3 code. + | + ++ + | +
|
+
+
+
+
+ |
+ + + date of birth + | ++ + + GenericDate + + + | ++ 0..* + | ++ The point in time on which the Person was born. + | +
+ The date of birth could be expressed as date, gYearMonth or gYear, example:
+
|
+
+ + + | +
|
+
+
+
+
+ |
+ + + family name + | ++ + + Text + + + | ++ 0..* + | ++ The hereditary surname of a family. + | ++ Usually referring to a group of people related by blood, marriage or adoption. This attribute also carries prefixes or suffixes which are part of the family name, e.g. "de Boer", "van de Putte", "von und zu Orlow". Multiple family names, such as are commonly found in Hispanic countries, are recorded in the single family name property so that, for example, Miguel de Cervantes Saavedra's family name would be recorded as "de Cervantes Saavedra". + | + ++ + | +
|
+
+
+
+
+ |
+ + + given name + | ++ + + Text + + + | ++ 0..* + | ++ The name(s) that identify the Person within a family with a common surname. + | ++ Usually a first name or forename. Given to a person by his or her parents at birth or legally recognised as 'given names' through a formal process. All given names are ordered in one property so that, for example, the given name for Johann Sebastian Bach is "Johann Sebastian". + | + ++ + | +
|
+
+
+
+
+ |
+ + + place of birth + | ++ + + Location + + + | ++ 0..* + | ++ The Location where the Person was born. + | ++ The Place of Birth and Place of Death are given using the Location class which is associated via the appropriate relationship. The Location Class has two properties: (1) the geographic name of the place, which is given as a string such as "Amsterdam" or "Valetta" and (2) an identifier, such as a geonames URI http://sws.geonames.org/2759794 (which identifies Amsterdam) or http://sws.geonames.org/2562305 (which identifies Valetta). The use of identifiers is preferred as these are unambiguous, however, public sector data typically uses simple names to record places and this is fully supported. + | + ++ + | +
+ Datatypes +
+ + The following datatypes are used within this specification. + +| + | ++ Class + | ++ Definition + | +
|---|---|---|
|
+
+
+
+ |
+
+
+ GenericDate
+
+
+ | + The date data type is the union of xs:date, xs:gYearMonth and xs:gYear + |
|
+
+
+
+ |
+
+
+ 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 Nationality. + + +JSON-LD context file
+ + One common technical question is the format in which the data is being exchanged. + For conformance with the Proof Of Nationality, 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 Nationality, 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 Nationality is available here. + + +UML representation
+ The UML representation from which the Proof Of Nationality 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 |
|---|---|---|---|---|
| Evidence Type | +http://data.europa.eu/m8g/EvidenceType |
+ + | + | + |
| Location | +http://purl.org/dc/terms/Location |
+ + | geographic name | +http://www.w3.org/ns/locn#geographicName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | country of birth | +http://www.w3.org/ns/person#countryOfBirth |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | date of birth | +http://data.europa.eu/m8g/birthDate |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | family name | +http://xmlns.com/foaf/0.1/familyName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | given name | +http://xmlns.com/foaf/0.1/givenName |
+
| Person | +http://www.w3.org/ns/person#Person |
+ + | place of birth | +http://www.w3.org/ns/person#placeOfBirth |
+
| Proof of nationality | +http://data.europa.eu/p4s/ProofOfNationality |
+ + | is about | +http://purl.org/dc/terms/subject |
+
Feedback
+ ++ Please provide feedback on the general discussion forum +
+ +- \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\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<\/li>\r\n
- 1980-09^^xs:gYearMonth<\/li>\r\n
- 1980^^xs:gYear<\/li>\r\n<\/ul>"}, "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" : "date of birth", "definition" : "The point in time on which the Person was born.", "usage" : "The date of birth could be expressed as date, gYearMonth or gYear, example:\r\n
- \r\n
- 1980-09-16^^xs:date<\/li>\r\n
- 1980-09^^xs:gYearMonth<\/li>\r\n
- 1980^^xs:gYear<\/li>\r\n<\/ul>", "ap-label-en" : "date of birth", "ap-definition-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
- 1980-09-16^^xs:date<\/li>\r\n
- 1980-09^^xs:gYearMonth<\/li>\r\n
- 1980^^xs:gYear<\/li>\r\n<\/ul>" }], "Scope" : "NOTHING", "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<\/li>\r\n
- 1980-09^^xs:gYearMonth<\/li>\r\n
- 1980^^xs:gYear<\/li>\r\n<\/ul>"}, "ap-label-en" : {"en": "date of birth"}, "definition" : {"en": "The point in time on which the Person was born."}, "label" : {"en": "date of birth"}},
+"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://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" : "{8089B001-FF9B-4327-A323-A730BB3BA6C7}", "derived" : "false", "EA-Package" : "", "EA-Type" : "connector", "EA-Domain" : "ProofOfNationality", "EA-Domain-Guid" : "{69B5B533-151D-4a33-8E73-A0EC34841EE9}", "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" : "is about", "definition" : "Agent that is the subject in the provided Evidence.", "usage" : "", "ap-label-en" : "is about", "ap-definition-en" : "Agent that is the subject in the provided Evidence.", "ap-usageNote-en" : "", "ap-codelist" : "", "RawTags" : [{ "key": "label-en", "value": "NOTE", "note": "is about" }, { "key": "uri", "value": "NOTE", "note": "http:\/\/purl.org\/dc\/terms\/subject" }, { "key": "definition-en", "value": "NOTE", "note": "Agent that is the subject in the provided Evidence." }], "DestRoleTags" : [{ "key": "label-en", "value": "NOTE", "note": "is about" }, { "key": "uri", "value": "NOTE", "note": "http:\/\/purl.org\/dc\/terms\/subject" }, { "key": "definition-en", "value": "NOTE", "note": "Agent that is the subject in the provided Evidence." }], "Scope" : "NOTHING", "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"}},
+"codelist": [
+],
+"domain": [
+{ "uri": "http://data.europa.eu/p4s/ProofOfNationality", "EA-Name" : "ProofOfNationality" }
+],
+"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#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<\/a> (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\u00EDna\"@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<\/a> 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<\/a> 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" : "geographic name", "definition" : "A textual description for a Location.", "usage" : "A geographic name is a proper noun applied to a spatial object. Taking the example used in the INSPIRE document<\/a> (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\u00EDna\"@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<\/a> 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<\/a> 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" : "geographic name", "ap-definition-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<\/a> (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\u00EDna\"@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<\/a> 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<\/a> 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", "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<\/a> (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\u00EDna\"@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<\/a> 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<\/a> 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"}},
+"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/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<\/a> 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<\/a> 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<\/a>."}, "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" : "country of birth", "definition" : "The country in which the Person was born.", "usage" : "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<\/a> 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<\/a> 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<\/a>.", "ap-label-en" : "country of birth", "ap-definition-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<\/a> 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<\/a> 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<\/a>." }, { "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<\/a> 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<\/a> 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<\/a>." }, { "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", "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<\/a> 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<\/a> 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<\/a>."}, "ap-label-en" : {"en": "country of birth"}, "definition" : {"en": "The country in which the Person was born."}, "label" : {"en": "country of birth"}},
+"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<\/a> (which identifies Amsterdam) or http:\/\/sws.geonames.org\/2562305<\/a> (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" : "place of birth", "definition" : "The Location where the Person was born.", "usage" : "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<\/a> (which identifies Amsterdam) or http:\/\/sws.geonames.org\/2562305<\/a> (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" : "place of birth", "ap-definition-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<\/a> (which identifies Amsterdam) or http:\/\/sws.geonames.org\/2562305<\/a> (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<\/a> (which identifies Amsterdam) or http:\/\/sws.geonames.org\/2562305<\/a> (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", "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<\/a> (which identifies Amsterdam) or http:\/\/sws.geonames.org\/2562305<\/a> (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"}},
+"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" : "family name", "definition" : "The hereditary surname of a family.", "usage" : "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" : "family name", "ap-definition-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", "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"}},
+"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" : "given name", "definition" : "The name(s) that identify the Person within a family with a common surname.", "usage" : "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" : "given name", "ap-definition-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", "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"}},
+"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": "*"}
+]
+}
\ No newline at end of file
diff --git a/report/OOTS/ProofOfNationality/releases/0.0.1/proofofnationality.report b/report/OOTS/ProofOfNationality/releases/0.0.1/proofofnationality.report
new file mode 100644
index 000000000..40e57dc46
--- /dev/null
+++ b/report/OOTS/ProofOfNationality/releases/0.0.1/proofofnationality.report
@@ -0,0 +1,33 @@
+Load mapping config:config/config-ap.json
+WARNING:You shouldn't use 'user' reserved word as column name in the table t_datatypes (it refers to the database user).
+ Escape it in your SQL!
+(e.g. SELECT [USER] FROM TABLE WHERE [USER]='Joe')
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "baseURI" tag for "Model".
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "baseURI" tag for "Model.ISA Core Vocabularies.DataTypes".
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "baseURI" tag for "Model.ISA Core Vocabularies.oots".
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following packages map to the same URI (http://fixme.com#): Model, Model.ISA Core Vocabularies.oots, Model.ISA Core Vocabularies.DataTypes
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following elements map to the same URI (http://purl.org/dc/terms/Location): Model.ISA Core Vocabularies.dct:Location, Model.ISA Core Vocabularies.dct:Location
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following elements map to the same URI (http://www.w3.org/2004/02/skos/core#Concept): Model.ISA Core Vocabularies.DataTypes:Code, Model.ISA Core Vocabularies.skos:Concept
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/type): Model.ISA Core Vocabularies.cv:LifeEvent:type, Model.ISA Core Vocabularies.cpsv:PublicService:functionsOfGovernment, Model.ISA Core Vocabularies.cv:Output:type, Model.ISA Core Vocabularies.cv:BusinessEvent:type, Model.ISA Core Vocabularies.cv:Channel:type, Model.ISA Core Vocabularies.cpsv:Rule:type, Model.ISA Core Vocabularies.cv:Requirement:type
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/language): Model.ISA Core Vocabularies.cpsv:Rule:language, Model.ISA Core Vocabularies.cpsv:PublicService:language, Model.ISA Core Vocabularies.cv:Output:language
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/description): Model.ISA Core Vocabularies.cv:Participation:description, Model.ISA Core Vocabularies.time:TemporalEntity:description, Model.ISA Core Vocabularies.dcat:Dataset:description, Model.ISA Core Vocabularies.cpsv:Rule:description, Model.ISA Core Vocabularies.cv:Event:description, Model.ISA Core Vocabularies.cv:ServiceConcessionContract:description, Model.ISA Core Vocabularies.cpsv:PublicService:description, Model.ISA Core Vocabularies.cv:Output:description, Model.ISA Core Vocabularies.cv:Cost:description, Model.ISA Core Vocabularies.cv:Channel:description
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/spatial): Model.ISA Core Vocabularies.cv:PublicOrganisation:spatial, Model.ISA Core Vocabularies.cpsv:PublicService:spatial
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/title): Model.ISA Core Vocabularies.dcat:Dataset:title, Model.ISA Core Vocabularies.cv:Event:name, Model.ISA Core Vocabularies.cv:Requirement:name, Model.ISA Core Vocabularies.cpsv:PublicService:name, Model.ISA Core Vocabularies.cpsv:Rule:name, Model.ISA Core Vocabularies.foaf:Agent:name, Model.ISA Core Vocabularies.cv:ServiceConcessionContract:name, Model.ISA Core Vocabularies.cv:Output:name
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://purl.org/dc/terms/identifier): Model.ISA Core Vocabularies.cpsv:Rule:identifier, Model.ISA Core Vocabularies.cv:Output:identifier, Model.ISA Core Vocabularies.cv:Event:identifier, Model.ISA Core Vocabularies.cpsv:PublicService:identifier, Model.ISA Core Vocabularies.foaf:Agent:identifier, Model.ISA Core Vocabularies.dcat:Dataset:identifier, Model.ISA Core Vocabularies.cv:Channel:identifier, Model.ISA Core Vocabularies.cv:Participation:identifier, Model.ISA Core Vocabularies.cv:Cost:identifier, Model.ISA Core Vocabularies.cv:ServiceConcessionContract:identifier, Model.ISA Core Vocabularies.cv:Requirement:identifier
+11:41:13 WARN c.g.i.o.c.UriAssigner - The following properties (attribute or connector) map to the same URI (http://data.europa.eu/m8g/processingTime): Model.ISA Core Vocabularies.cpsv:PublicService:processingTime, Model.ISA Core Vocabularies.cv:Channel:processingTime
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "issued" tag for "Model.ISA Core Vocabularies".
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "license" tag for "Model.ISA Core Vocabularies".
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "issued" tag for "Model.ISA Core Vocabularies".
+11:41:13 WARN c.g.i.o.c.TagHelper - Missing "license" tag for "Model.ISA Core Vocabularies".
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "EvidenceType" .
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "ProofOfNationality" .
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "Person" .
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "GenericDate" .
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "Text" .
+11:41:13 INFO c.g.i.o.c.JSONLDOutputHandler - handle class "Location" .
+11:41:13 WARN c.g.i.o.c.UriAssigner - Ignoring connector "Model.ISA Core Vocabularies.person:Person:(Person -> Location)" since it lacks a defining package.
+11:41:13 WARN c.g.i.o.c.Converter - Package for connector Model.ISA Core Vocabularies.person:Person:placeOfBirth is unknown
+11:41:13 WARN c.g.i.o.c.UriAssigner - Ignoring connector "Model.ISA Core Vocabularies.oots:ProofOfNationality:(ProofOfNationality -> Person)" since it lacks a defining package.
+11:41:13 WARN c.g.i.o.c.Converter - Package for connector Model.ISA Core Vocabularies.oots:ProofOfNationality:isAbout is unknown
+11:41:13 WARN c.g.i.o.c.UriAssigner - Ignoring connector "Model.ISA Core Vocabularies.person:Person:(Person -> Location)" since it lacks a defining package.
+11:41:13 WARN c.g.i.o.c.Converter - Package for connector Model.ISA Core Vocabularies.person:Person:countryOfBirth is unknown
diff --git a/report/OOTS/ProofOfNationality/releases/0.0.1/shacl/proofofnationality-SHACL_en.report b/report/OOTS/ProofOfNationality/releases/0.0.1/shacl/proofofnationality-SHACL_en.report
new file mode 100644
index 000000000..a08633013
--- /dev/null
+++ b/report/OOTS/ProofOfNationality/releases/0.0.1/shacl/proofofnationality-SHACL_en.report
@@ -0,0 +1,25 @@
+start reading
+/tmp/workspace/report/OOTS/ProofOfNationality/releases/0.0.1//translation/ProofOfNationality_en_merged.jsonld
+/tmp/workspace/target/OOTS/ProofOfNationality/releases/0.0.1//shacl/proofofnationality-SHACL_en.jsonld
+en
+done
+start processing
+make shacl using individual mode
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#EvidenceTypeShape
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#GenericDateShape
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#ProofOfNationalityShape
+add nodeKind constraint
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#LocationShape
+add uniqueLanguage constraint
+add nodeKind constraint
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#TextShape
+https://semiceu.github.io/OOTS/ProofOfNationality/releases/0.0.1/#PersonShape
+add nodeKind constraint
+add nodeKind constraint
+add uniqueLanguage constraint
+add nodeKind constraint
+add uniqueLanguage constraint
+add nodeKind constraint
+add nodeKind constraint
+start writing
+Write complete, file saved to: /tmp/workspace/target/OOTS/ProofOfNationality/releases/0.0.1//shacl/proofofnationality-SHACL_en.jsonld
diff --git a/report/OOTS/ProofOfNationality/releases/0.0.1/translation/ProofOfNationality_en.json b/report/OOTS/ProofOfNationality/releases/0.0.1/translation/ProofOfNationality_en.json
new file mode 100644
index 000000000..56551f33f
--- /dev/null
+++ b/report/OOTS/ProofOfNationality/releases/0.0.1/translation/ProofOfNationality_en.json
@@ -0,0 +1,163 @@
+{
+ "baseURI": "https://data.europa.eu/m8g/",
+ "classes": [],
+ "properties": [],
+ "externals": [
+ {
+ "EA-Guid": "{F62262A4-6831-4684-A50A-2FCBBB91B6E8}",
+ "name": "EvidenceType",
+ "label": {
+ "en": "Evidence Type"
+ },
+ "definition": {
+ "en": "Information about the characteristics of an Evidence."
+ },
+ "usage": {
+ "en": "The Evidence Type and the characteristics it describes are not concrete individual responses to a Requirement (i.e. Evidence), but descriptions about the desired form, content, source and/or other characteristics that an actual response should have and provide (e.g. membership of a class of Evidences)."
+ }
+ },
+ {
+ "EA-Guid": "{F4582C0C-FB5E-48f4-8BA4-05D6AED23809}",
+ "name": "Genericdate",
+ "label": {
+ "en": "GenericDate"
+ },
+ "definition": {
+ "en": "The date data type is the union of xs:date, xs:gYearMonth and xs:gYear"
+ }
+ },
+ {
+ "EA-Guid": "{69B5B533-151D-4a33-8E73-A0EC34841EE9}",
+ "name": "ProofOfNationality",
+ "label": {
+ "en": "Proof of nationality"
+ },
+ "definition": {
+ "en": "Request for evidence regarding the nationality of the person (evidence subject)."
+ }
+ },
+ {
+ "EA-Guid": "{C76F43F4-6D4A-49ec-9C53-A7EA6970C41D}",
+ "name": "Location",
+ "label": {
+ "en": "Location"
+ },
+ "definition": {
+ "en": "An identifiable geographic place or named place."
+ }
+ },
+ {
+ "EA-Guid": "{E4045FE6-F5D2-4c3f-881E-800F8C9AF85E}",
+ "name": "Text",
+ "label": {
+ "en": "Text"
+ },
+ "definition": {
+ "en": "The text data type is a combination of a string and a language identifier."
+ }
+ },
+ {
+ "EA-Guid": "{25864841-22B7-4c9a-9D72-EFF902B16055}",
+ "name": "Person",
+ "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."
+ }
+ }
+ ],
+ "externalproperties": [
+ {
+ "EA-Guid": "{0E297AAE-E6BA-42a0-A308-FC513C2D5EB1}",
+ "name": "dateOfBirth",
+ "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
- 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\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\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