Abstract

Proof of birth of child is a simplified data model describing a request for evidence regarding the birth of a person's (evidence subject) child. This data model draws upon the birth public document description of REGULATION (EU) 2016/119Annex I .

Introduction

The Proof of birth of child data model provides a minimum set of classes and properties for describing a proof of birth of child 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.
PrefixNamespace IRI
cvhttp://data.europa.eu/m8g/
dcthttp://purl.org/dc/terms/
foafhttp://xmlns.com/foaf/0.1/
locnhttp://www.w3.org/ns/locn#
ootshttp://data.europa.eu/p4s/
personhttp://www.w3.org/ns/person#/
rdfhttp://www.w3.org/1999/02/22-rdf-syntax-ns#
rdfshttp://www.w3.org/2000/01/rdf-schema#
skoshttp://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 birth of child |

The main entities are supported by:
| Evidence Type | Location | Person |

And supported by these datatypes:
| Code | GenericDate | Text |

Main Entities

The main entities are those that form the core of the Application Profile.

Proof of birth of child

Definition
Request for evidence regarding the birth of a person's (evidence subject) child.
Subclass of
Evidence Type
Properties
For this entity the following properties are defined: is about .
Property Range Card Definition Usage
[o] 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
[o] 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 , has child , place of birth , sex .
Property Range Card Definition Usage
[o] 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.
[o] date of birth GenericDate 0..* The point in time on which the Person was born. The date of birth could be expressed as date, gYearMonth or gYear, example:
  • 1980-09-16^^xs:date
  • 1980-09^^xs:gYearMonth
  • 1980^^xs:gYear
[o] 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".
[o] 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".
[o] has child Person 0..* Connects a person to (one of) their children.
[o] 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.
[o] 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
(create issue) An idea or notion; a unit of thought.
(create issue) The date data type is the union of xs:date, xs:gYearMonth and xs:gYear
(create issue) 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 ProofOfBirthOfChild.

JSON-LD context file

One common technical question is the format in which the data is being exchanged. For conformance with the ProofOfBirthOfChild, 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 ProofOfBirthOfChild, 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 ProofOfBirthOfChild is available here.

UML representation

The UML representation from which the ProofOfBirthOfChild 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:

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:

After being taken into consideration the asset will be validated in three steps:

Once considered and validated an asset can be adopted if it is approved by the community.

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:

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, recommended, optional and deprecated. These terms have the following meaning.
ClassClass IRIProperty TypePropertyProperty 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
has child
http://data.europa.eu/p4s/hasChild
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 birth of child
http://data.europa.eu/p4s/ProofOfBirthOfChild
is about
http://purl.org/dc/terms/subject

Feedback

Please provide feedback on the discussion forum