Contents
5.1 Classification Scheme and Nodes
The EB Service provides a Regrep 4.0 based LCM API, following the RegRep 4.0 LCM Manager Interface Specification. This section defines the Classification Scheme, Classification Nodes, Associations and Registry Objects of the SubmitObjects Request Message. After the introduction of the Classification Scheme, Classification Nodes, Associations a full LCM SubmitObjects transaction to the EB is illustrated as Data Model, Implementation Guideline and Example including its associated business rules. The Lifecycle Management Specification (see Chapter 3: Common Services - Common Services API Specification) provides a principle overview for such bulk update of the information stored in the Common Services of a Member State. It relates to this section as this section illustrates how the API is used to process an update to the EB.
| Definition Type | Value | Description |
|---|---|---|
| Classification Scheme | urn:fdc:oots:classification:eb | The classification scheme under which the specific classification nodes reside for the EBService |
| Classification Node | EvidenceType | A Node defining the registry object as an Evidence Provider Entity |
| Classification Node | EvidenceTypeList | A classification node defining the registry object as an Evidence Type List |
| Classification Node | Requirement | A classification node defining the registry object as a Requirement |
| Classification Node | ReferenceFramework | A classification node defining the registry object as a ReferenceFramework (Procedure) |
| Association | urn:oasis:names:tc:ebxml-regrep:AssociationType:containsEvidence | The association linking EvidenceTypes with EvidenceTypeLists Registry objects |
| Association | urn:oasis:names:tc:ebxml-regrep:AssociationType:fulfillsRequirement | The association linking EvidenceTypeList Registry objects with Requirements |
| Association | urn:oasis:names:tc:ebxml-regrep:AssociationType:derivesFromReferenceFramework | The association linking Requirements Registry objects with ReferenceFramework (Procedure) |
5.2 Registry Objects
The EB LCM Interface accepts two different registry objects in the SubmitObjectsRequest Message which are defined in the sections below:
5.2.1 EvidenceType
This Registry Object provides the information of the Evidence Type. The classification node used MUST be EvidenceType under the EB Classification Scheme urn:fdc:oots:classification:eb. The following diagram shows the structure of the registry object:
An example EvidenceType Registry Object in XML format is shown below. The example is embedded into a lcm:SubmitObjectsRequest (see Lifecycle Management Specification of Chapter 3: Common Services - 3.6 Common Services API Specification):
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<rim:RegistryObject id="urn:uuid:a1be6e74-e9ba-4d44-b04c-0376f367b8fd">
<rim:Slot name="EvidenceType">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:EvidenceType>
<!-- EvidenceTypeClassification Information - Provided by the Evidence Broker on the basis of the Semantic Repository. Used for linking with the Semantic Repository and Data Service Directory -->
<sdg:EvidenceTypeClassification>https://sr.oots.tech.ec.europa.eu/evidencetypeclassifications/DE/ca8afed6-2dc0-422a-a931-d21c3d8d370e</sdg:EvidenceTypeClassification>
<sdg:Title lang="EN">Certificate of Birth</sdg:Title>
<sdg:Title lang="DE">Geburtsurkunde</sdg:Title>
<sdg:Description lang="EN">An official certificate of birth of a person - with first name, surname, sex, date and place of birth, which is obtained from the birth register of the place of birth.</sdg:Description>
<sdg:Description lang="DE">Eine amtliche Bescheinigung über die Geburt einer Person – mit Vorname, Familienname, Geschlecht, Datum und Ort der Geburt, welche aus dem Geburtsregister des Geburtsortes erstellt wird.</sdg:Description>
<sdg:Jurisdiction>
<!-- Country - Mandatory - ISO code -->
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<!-- Regional Code not applicable for DE (Common Evidence for the country) -->
</sdg:Jurisdiction>
</sdg:EvidenceType>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 35c299d8-9383-47ce-ad8c-0ed70ea52827 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as EvidenceType -->
<rim:Classification id="urn:uuid:35c299d8-9383-47ce-ad8c-0ed70ea52827"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="EvidenceType"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.2.2 EvidenceTypeList
This Registry Object provides the information of the Evidence Type List. It works as an intermediate class linking multiple evidence types as an atomic proof to requirements and thus it MUST NOT contain any evidence types in its structure. The classification node used MUST be EvidenceTypeList under the EB Classification Scheme urn:fdc:oots:classification:eb. The following diagram shows the structure of the registry object:
An example EvidenceTypeList Registry Object in XML format is shown below. The example is embedded into a lcm:SubmitObjectsRequest (see Lifecycle Management Specification of Chapter 3: Common Services - 3.6 Common Services API Specification):
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<rim:RegistryObject id="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23">
<!-- List of Evidence Types that proof the Requirement in Germany -->
<rim:Slot name="EvidenceTypeList">
<rim:SlotValue xsi:type="rim:AnyValueType">
<!-- List of Evidence Types that proof the Requirement in Germany-->
<!-- Multiple List of Evidence Types might be part of the result - depending on the query paramters -->
<sdg:EvidenceTypeList>
<sdg:Identifier>970918e4-1b27-41f0-be20-0a7c5fe4059f</sdg:Identifier>
<sdg:Name lang="EN">List of Birth Certificates</sdg:Name>
<sdg:Name lang="DE">Liste der Geburtsurkunden</sdg:Name>
</sdg:EvidenceTypeList>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 4d44680b-432c-4b22-aa36-880d4ebd1b0d -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as EvidenceTypeList -->
<rim:Classification id="urn:uuid:4d44680b-432c-4b22-aa36-880d4ebd1b0d"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="EvidenceTypeList"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.2.3 Requirement
This Registry Object provides the information of a Requirement in any of its derivative forms (Criterion, Information Requirement). It MUST NOT contain any Evidence Type or Reference Frameworks (Procedures) as this are provided dynamically by the use of associations. The classification node used MUST be Requirement under the EB Classification Scheme urn:fdc:oots:classification:eb. The following diagram shows the structure of the registry object:
An example Requirement Registry Object in XML format is shown below. The example is embedded into a lcm:SubmitObjectsRequest (see Lifecycle Management Specification of Chapter 3: Common Services - 3.6 Common Services API Specification):
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<rim:RegistryObject id="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099">
<rim:Slot name="Requirement">
<!-- The underlying requirement -->
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:Requirement>
<sdg:Identifier>https://sr.oots.tech.ec.europa.eu/requirements/315cfd75-6605-49c4-b0fe-799833b41099</sdg:Identifier>
<sdg:Name lang="EN">Proof of Birth</sdg:Name>
<sdg:Name lang="DE">Geburtsnachweis</sdg:Name>
</sdg:Requirement>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 22333046-3429-4684-85de-d9db69e236a1 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as Requirement -->
<rim:Classification id="urn:uuid:22333046-3429-4684-85de-d9db69e236a1"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="Requirement"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.2.4 ReferenceFramework
This Registry Object ReferenceFramework provides the information of a Procedure. It MUST NOT contain any relations to other Reference Frameworks (Procedures) as this are provided dynamically by the use of associations. The classification node used MUST be ReferenceFramework under the EB Classification Scheme urn:fdc:oots:classification:eb.The following diagram shows the structure of the registry object:
An example ReferenceFramework Registry Object in XML Format is shown below. The example is embedded into a lcm:SubmitObjectsRequest (see Lifecycle Management Specification of Chapter 3: Common Services - 3.6 Common Services API Specification):
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<rim:RegistryObject id="urn:uuid:b0c90eb4-6b66-4dd8-8c79-6d964ac3b9a1">
<rim:Slot name="ReferenceFramework">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:ReferenceFramework>
<!-- Link to the Procedure as implemented in Germany, uniquely identified by the Identifier and Jurisdiction. The name of the procedure, as declared in the SDG Regulation; Is possibly extended or replaced with national reference frameworks when the procedure is implemented by a Member State regulation -->
<sdg:Identifier>118fd444-6443-42be-a084-c9fbfd1f674d</sdg:Identifier>
<sdg:Title lang="EN">Procedure #1 - Requesting proof of registration of birth</sdg:Title>
<sdg:Title lang="DE">Verfahren #1 - Beantragung des Nachweises über die Eintragung in das Geburtenregister</sdg:Title>
<sdg:Description lang="EN"> Procedure #1 "Requesting proof of registration of birth" belongs to the life event "Birth" of Annex II of the Regulation (EU) 2018/1724
of the European Parliament and of the Council of 2 October 2018 establishing a single digital gateway to provide access to information, to procedures and to assistance and problem-solving services and amending Regulation (EU) No 1024/2012
</sdg:Description>
<sdg:Description lang="DE"> Das Verfahren #1 "Beantragung des Nachweises über die Eintragung in das Geburtenregister" gehört zum Lebensereignis "Geburt" des Anhangs II der Verordnung (EU) 2018/1724 des Europäischen Parlaments und des Rates vom 2. Oktober 2018 über die Einrichtung eines einheitlichen digitalen Zugangstors zu Informationen, Verfahren, Hilfsund Problemlösungsdiensten und zur Änderung der Verordnung (EU) Nr. 1024/2012
</sdg:Description>
<!-- The Identifier of the SDGR Procedure which this procedure relates to encoded according to Procedures-CodeList.gc. In this case R1 relates to "Requesting a birth certificate" -->
<sdg:RelatedTo>
<sdg:Identifier>R1</sdg:Identifier>
</sdg:RelatedTo>
<!-- Country - Mandatory - ISO code. Requirement is connected to the implementation of Procedure 1 in Germany. Regional Codes (AdminUnitLevel 2 and 3) not applicable for DE in this Procedure (Common Reference Framework for the country) -->
<sdg:Jurisdiction>
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
</sdg:Jurisdiction>
</sdg:ReferenceFramework>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 750869ec-aeac-4cc6-9386-75c86544e433 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as ReferenceFramework -->
<rim:Classification id="urn:uuid:750869ec-aeac-4cc6-9386-75c86544e433"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="ReferenceFramework"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.3 Associations
The EB LCM Interface accepts three distict associations linking the Registry Objects (EvidenceType, EvidenceTypeList, Requirement and ReferenceFramework) within the SubmitObjectsRequest Message. The different associations are defined the sections below.
5.3.1. ContainsEvidence
This Association provides the link between an Evidence Type List and an Evidence Type. The type attribute MUST be urn:oasis:names:tc:ebxml-regrep:AssociationType:ContainsEvidence, with the source object pointing to an EvidenceTypeList RegistryObject through the use of its rim:RegistryObject id and the targetObject pointing to rim:RegistryObject id of an EvidenceType object. Evidence Types of an Evidence Type List are combined via the logic operator ‘AND’. An Evidence Type List is satisfied, if and only if, for all included Evidence Types in this List, corresponding conformant Evidence(s) are provided.
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with DataServiceEvidenceType "Certificate of Birth"-->
<!-- A unique id for this association 826a2206-5dd0-45ff-abbc-23ba8f38477f -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the EvidenceType "Certificate of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:826a2206-5dd0-45ff-abbc-23ba8f38477f"
sourceObject="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23"
targetObject="urn:uuid:a1be6e74-e9ba-4d44-b04c-0376f367b8fd"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:ContainsEvidence"/>
</lcm:SubmitObjectsRequest>
5.3.2 FulfillsRequirement
This Association provides the link between an Evidence Type List and a Requirement. The type attribute MUST be urn:oasis:names:tc:ebxml-regrep:AssociationType:FulfillsRequirement, with the source object pointing to an EvidenceTypeList RegistryObject through the use of its rim:RegistryObject id and the targetObject pointing to the rim:RegistryObject id of an Requirement object. Evidence Type Lists that fulfill the same Requirement are combined via the logic operator ‘OR’.
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other Registry Objects are ommitted for clarity-->
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f"-->
<!-- A unique id for this association 3da4288b-e2ca-4d40-bde2-d3fc2dd04bab -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the Requirement "Proof of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:3da4288b-e2ca-4d40-bde2-d3fc2dd04bab"
sourceObject="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23"
targetObject="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:FulfillsRequirement"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.3.3 DerivesFromReferenceFramework
This Association provides the link between a Requirement and a ReferenceFramework (Procedure). The type attribute MUST be urn:oasis:names:tc:ebxml-regrep:AssociationType:DerivesFromReferenceFramework, with the source object pointing to a Requirement RegistryObject through the use of its rim:RegistryObject id and the targetObject pointing to the rim:RegistryObject id of a ReferenceFramework object.
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
id="urn:uuid:e5af5ba0-39a2-43d7-89c0-04f623c59855"
checkReferences="true">
<rim:RegistryObjectList>
<!-- Other Registry Objects are ommitted for clarity-->
<!-- Associate the Requirement "Proof of Birth" with ReferenceFramework "Procedure #1 - Requesting proof of registration of birth"-->
<!-- A unique id for this association d650d08b-4ca3-4d04-a5d2-255d83b84ce1 -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the Requirement "Proof of Birth" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the ReferenceFramework "Procedure #1 - Requesting proof of registration of birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:d650d08b-4ca3-4d04-a5d2-255d83b84ce1"
sourceObject="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099"
targetObject="urn:uuid:b0c90eb4-6b66-4dd8-8c79-6d964ac3b9a1"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:DerivesFromReferenceFramework"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.4 LCM Submit Objects to the Evidence Broker
5.4.1. Data Model of the LCM Submit Objects Request to the EB
For the LCM submission, the profile uses the SubmitObjectsRequest message, as defined by the RegRep 4.0 LCM Manager Interface Specification SubmitObjects Protocol. The message MUST contain a unique id and one Registry Object List containing the Registry Objects under submission.
The following data model illustrates how a SubmitObjectsRequest to the EB is constructed based on the SDG OOTS LifeCycleManagementSpecification (see Chapter 3: Common Services - Common Services API Specification).
The LCM for the EB follows the logic of the ISA2 SEMIC The Core Criterion and Core Evidence Vocabulary (CCCEV). https://joinup.ec.europa.eu/collection/semantic-interoperability-community-semic/solution/core-criterion-and-core-evidence-vocabulary
- To fulfill a 'Requirement' at least one Evidence Type must be specified for an Evidence Type List.
- The 'Evidence Type List' are alternative methods proposed by the Evidence Broker to fulfill a requirement. Thus,
- Evidence Type Lists must have at least one but can combine different Evidence Types.
- Evidence Types of an Evidence Type List are combined via the logic operator ‘AND’.
- Evidence Type Lists that fulfill the same Requirement are combined via the logic operator ‘OR’.
- The 'Evidence Types' are described in detail with respect to their jurisdiction level.
The EB holds a mapping between the Requirements and their associated Evidence Type Lists and Evidence Types that are able to prove these requirements. An Evidence instance that is requested and provided throughout the OOTS Evidence Exchange process should refer to its corresponding Evidence Type.
5.4.2. Implementation Guideline of the LCM Submit Objects Request to the EB
The table below defines the elements of the data model illustrated above according to the RegRep 4.0 LCM Manager Interface Specification SubmitObjects Protocol which is adapted by the SubmitObjectsRequest to the EB. The data model contains Registry Objects being of "RegistryObjectType" or registryObjects being of "AssociationType". Registry Objects which are a RegistryObjectType either contain a rim:Slot "EvidenceType" or a rim:Slot "EvidenceTypeList" or a rim:Slot "Requirement" or a rim:Slot "ReferenceFramework". Registry Objects which are an AssociationType contain a sourceObject pointing to the id of the RegistryObject used to identify a RegistryObjectType and a target object pointing to the id of the RegistryObject used to identify another RegistryObjectType (see section 5.3 Associations).
Legend
The table below represent the tree structure of the data models illustrated in this section. Light grey rows describe classes and define their properties and attributes. Light green rows soley illustrate the classes that are subordinated or associated to a class and therewith illustrate the tree structure of the data model. Light green rows are thus always repeated as light grey rows to describe the properties and attributes of a class. The hierarchy of the tree structure is also indicated in the first column via the '+' symbol.
| Hierarchy | Name | Definition | Cardinality | Type | Data Type | Rules | Core Vocabulary / Domain | Element of Core Vocabulary |
|---|---|---|---|---|---|---|---|---|
lcm:SubmitObjectsRequest | root element | Structure: R-EB-SUB-S001, R-EB-SUB-S002, R-EB-SUB-S042, | ebRIM | |||||
| + | id | The unique identifier of the SubmitObjectsRequest. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S003, R-EB-SUB-S004 | ebRIM | - |
| + | checkReferences | Element to express that a server MUST check submitted objects and make sure that all references via reference attributes and slots to other RegistryObjects are resolvable. MUST be set to the value true. | 1..1 | Attribute | Boolean | Structure: R-EB-SUB-S063, R-EB-SUB-S064 | ebRIM | - |
| + | rim:slot "SpecificationIdentifier" | An identification of the specification for the LCM version containing the total set of rules regarding semantic content, cardinalities and business rules to which the data contained in the instance document conforms. If SubmitObjectsRequest is combined with DSD LCM Refactored, it MUST be used and set to the value oots-lcm:v1.0. | 0..1 | SlotType | StringValueType | Structure: R-EB-SUB-S061, R-EB-SUB-S062 Content: R-EB-SUB-C024 | ebRIM | - |
| + | rim:RegistryObjectList | Element to list the Registry Objects of the QueryResponse. | 1..1 | RegistryObjectListType | Structure: R-EB-SUB-S005 | ebRIM | - | |
| + | rim:RegistryObjectList | Element to list the Registry Objects of the QueryResponse. | 1..1 | RegistryObjectListType | Structure: R-EB-SUB-S005 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:Slot "EvidenceType"> | An Evidence Type is a type of evidence that can be provided to meet a requirement, within a certain jurisdiction. | 1..n | RegistryObjectType | Structure: R-EB-SUB-S044, EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:slot "EvidenceTypeList"> | A list of Evidence Types, that can be provided to meet a requirement, within a certain jurisdiction. | 1..n | RegistryObjectType | Structure: R-EB-SUB-S045, EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:slot "Requirement"> | The element describes specific aspects and metadata of the Requirement. | 0..n | RegistryObjectType | Structure: R-EB-SUB-S046, EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:slot "ReferenceFramework"> | The Reference Framework or Procedure that is responsible for the creation/initiation of the Requirement. | 0..n | RegistryObjectType | Structure: R-EB-SUB-S048, EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| ++ | rim:RegistryObject <xsi:type="rim:AssociationType"> | An association that links a RegistryObject with another RegistryObject within the SubmitObjectsRequest Message. Valid associations defined for the EB are containsEvidence, fulfillsRequirement and derivesFromReferenceFramework. | 1..n | AssociationType | Structure: R-EB-SUB-S047, R-EB-SUB-S030, EB-SUB-S060, R-EB-SUB-S066 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:Slot "EvidenceType"> | Element to control the type and structure of Registry Object within the SubmitObjectsRequest. | 1..n | RegistryObjectType | Structure: R-EB-SUB-S044, R-EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S006, R-EB-SUB-S043 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a DataServiceEvidenceType. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007 | ebRIM | ||
| +++ | rim:slot "EvidenceType" | The slot is a container to describe the specific aspects and metadata of the Evidence Type. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S014, R-EB-SUB-S018 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a DataServiceEvidenceType. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| ++++ | id | The unique identifier used to used for associating this target registry object with a source object (Evidence Type). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S008, R-EB-SUB-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the EB Service. FixedValue: urn:fdc:oots:classification:eb | 1..1 | Attribute | URI | Structure: R-EB-SUB-S010, R-EB-SUB-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Evidence Type. FixedValue: EvidenceType | 1..1 | Attribute | Code | Structure: R-EB-SUB-S011, R-EB-SUB-S013 | ebRIM | |
| +++ | rim:slot "EvidenceType" | The slot is a container to describe the specific aspects and metadata of the Evidence Type. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S014, R-EB-SUB-S018 | ebRIM | - |
| ++++ | EvidenceType | An Evidence Type is a type of evidence that can be provided to meet a requirement, within a certain jurisdiction. Evidence Types of an Evidence Type List are combined via the logic operator ‘AND’ to fulfill a requirement. | 1..n | EvidenceTypeType | Structure: R-EB-SUB-S022 | Core Criterion Core Evidence Vocabulary (CCCEV) | cccev:EvidenceType | |
| ++++ | EvidenceType | An Evidence Type is a type of evidence that can be provided to meet a requirement, within a certain jurisdiction. Evidence Types of an Evidence Type List are combined via the logic operator ‘AND’ to fulfill a requirement. | 1..n | EvidenceTypeType | Structure: R-EB-SUB-S022, R-EB-SUB-S026 | Core Criterion Core Evidence Vocabulary (CCCEV) | cccev:EvidenceType | |
| +++++ | EvidenceTypeClassification | An URI pointing to the Evidence Type. The classification is linking with the Evidence Type of the Semantic Repository (Evidence Broker). | 1..1 | Attribute | Code | Content: R-EB-SUB-C001 | Core Criterion Core Evidence Vocabulary | cccev:evidenceTypeClassification |
| +++++ | Title | A name to identify in common language the Evidence Type. Unbounded cardinality to support multiple languages. | 1..n | Attribute | Text | DCAT-AP | dct:title | |
| ++++++ | Title/@lang | The language of the title encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C002, R-EB-SUB-C003 | DCAT-AP | dct:title |
| +++++ | Description | A description of the Evidence Type. Unbounded cardinality to support multiple languages. | 0..n | Attribute | Text | DCAT-AP | dct:description | |
| ++++++ | Description/@lang | The language of the description encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C004, R-EB-SUB-C005 | DCAT-AP | dct:description |
| +++++ | Jurisdiction | The administrative level in which this EvidenceType applies. It can apply to multiple jurisdictions. | 1..n | JurisdictionType | Core Criterion Core Evidence Vocabulary | cccev:evidenceTypeJurisdiction | ||
| +++++ | Jurisdiction | The jurisdictions to which this EvidenceType applies. | 1..n | JurisdictionType | Core Location Vocabulary (CLV) | locn:Address | ||
| ++++++ | AdminUnitLevel1 | The name of the uppermost level of the address, almost always a country. | 1..1 | Attribute | Code | Content: R-EB-SUB-C006 | Core Location Vocabulary (CLV) | locn:adminUnitL1 |
| ++++++ | AdminUnitLevel2 | The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-EB-SUB-C007 | Core Location Vocabulary (CLV) | locn:adminUnitL2 |
| ++++++ | AdminUnitLevel3 | The name of a tertiary level/region of the address, usually a municipality or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-EB-SUB-C008 | Core Location Vocabulary (CLV) | locn:adminUnitL3 |
| ++ | rim:RegistryObject <rim:Slot "EvidenceTypeList"> | Element to control the type and structure of Registry Object within the SubmitObjectsRequest. | 1..n | RegistryObjectType | Structure: R-EB-SUB-S045, R-EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S006, R-EB-SUB-S043 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a EvidenceTypeList. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| +++ | rim:slot "EvidenceTypeList" | The slot is a container to describe the specific aspects and metadata of the EvidenceTypeList. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S015, R-EB-SUB-S019 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a EvidenceTypeList. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| ++++ | id | The unique identifier used to used for associating this target registry object with a source object (EvidenceTypeList). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S008, R-EB-SUB-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the EB Service. FixedValue: urn:fdc:oots:classification:eb | 1..1 | Attribute | URI | Structure: R-EB-SUB-S010, R-EB-SUB-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Evidence Type List. FixedValue: EvidenceTypeList | 1..1 | Attribute | Code | Structure: R-EB-SUB-S011, R-EB-SUB-S013 | ebRIM | |
| +++ | rim:slot "EvidenceTypeList" | The slot is a container to describe the specific aspects and metadata of the EvidenceTypeList. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S015, R-EB-SUB-S019 | ebRIM | - |
| ++++ | EvidenceTypeList | A list of Evidence Types, that can be provided to meet a requirement, within a certain jurisdiction. An Evidence Type List is satisfied, if and only if, for all included Evidence Types in this List, corresponding to conformant Evidence(s), are provided. The Evidence Type List describes thus an AND condition on the different Evidence Types within the list and an OR condition between two or more Evidence Type Lists. | 1..n | EvidenceTypeListType | Structure: R-EB-SUB-S023, R-EB-SUB-S027 | Core Criterion Core Evidence Vocabulary (CCCEV) | cccev:EvidenceTypeList | |
| ++++ | EvidenceTypeList | A list of Evidence Types, that can be provided to meet a requirement, within a certain jurisdiction. An Evidence Type List is satisfied, if and only if, for all included Evidence Types in this List, corresponding to conformant Evidence(s), are provided. The Evidence Type List describes thus an AND condition on the different Evidence Types within the list and an OR condition between two or more Evidence Type Lists. | 1..n | EvidenceTypeListType | Structure: R-EB-SUB-S023, R-EB-SUB-S027 | Core Criterion Core Evidence Vocabulary (CCCEV) | cccev:EvidenceTypeList | |
| +++++ | Identifier | The identifier of the Evidence Type List. | 1..1 | Attribute | Identifier | Content: R-EB-SUB-C009 | CCCEV | cccev:identifier |
| +++++ | Name | The name of the Evidence Type List. Unbounded cardinality to support multiple languages. | 0..n | Attribute | Text | CCCEV | cccev:name | |
| ++++++ | Name/@lang | The language of the title encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C010, R-EB-SUB-C011 | CCCEV | cccev:name |
| ++ | rim:RegistryObject <rim:Slot "Requirement"> | Element to control the type and structure of Registry Object within the SubmitObjectsRequest. | 0..n | RegistryObjectType | Structure: R-EB-SUB-S046, R-EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S006, R-EB-SUB-S043 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a EvidenceTypeList. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| +++ | rim:slot "Requirement" | The slot is a container to describe the specific aspects and metadata of the Requirement. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S016, R-EB-SUB-S020 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a Requirement. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| ++++ | id | The unique identifier used to used for associating this target registry object with a source object (Requirement). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S008, R-EB-SUB-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the EB Service. FixedValue: urn:fdc:oots:classification:eb | 1..1 | Attribute | URI | Structure: R-EB-SUB-S010, R-EB-SUB-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Requirement. FixedValue: Requirement | 1..1 | Attribute | Code | Structure: R-EB-SUB-S011, R-EB-SUB-S013 | ebRIM | |
| +++ | rim:slot "Requirement" | The slot is a container to describe the specific aspects and metadata of the Requirement. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S016, R-EB-SUB-S020 | ebRIM | - |
| ++++ | Requirement | The element describes specific aspects and metadata of the Requirement. | 1..1 | RequirementType | Structure: R-EB-SUB-S024, R-EB-SUB-S028 | Core Criterion and Core Evidence Vocabulary | cccev:Requirement | |
| ++++ | Requirement | The element describes specific aspects and metadata of the Requirement. | 1..1 | RequirementType | Structure: R-EB-SUB-S024, R-EB-SUB-S028 | Core Criterion and Core Evidence Vocabulary | cccev:Requirement | |
| +++++ | Identifier | The unique identifier of the Requirement. | 1..1 | Attribute | Identifier | Content: R-EB-SUB-C012 | CCCEV | cccev:identifier |
| +++++ | Name | A name to identify in common language the Requirement. | 1..n | Attribute | Text | CCCEV | cccev:name | |
| ++++++ | Name/@lang | The language of the title encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C013, R-EB-SUB-C014 | CCCEV | cccev:name |
| ++ | rim:RegistryObject <rim:Slot "ReferenceFramework"> | Element to control the type and structure of Registry Object within the SubmitObjectsRequest. | 0..n | RegistryObjectType | Structure: R-EB-SUB-S048, R-EB-SUB-S060, R-EB-SUB-S065 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S006, R-EB-SUB-S043 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a ReferenceFramework. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| +++ | rim:slot "ReferenceFramework" | The slot is a container to describe the specific aspects and metadata of the ReferenceFramework. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S017, R-EB-SUB-S021 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a ReferenceFramework. | 1..1 | ClassificationType | Structure: R-EB-SUB-S007, | ebRIM | ||
| ++++ | id | The unique identifier used to used for associating this target registry object with a source object (ReferenceFramework). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S008, R-EB-SUB-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the EB Service. FixedValue: urn:fdc:oots:classification:eb | 1..1 | Attribute | URI | Structure: R-EB-SUB-S010, R-EB-SUB-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as ReferenceFramework. FixedValue: ReferenceFramework | 1..1 | Attribute | Code | Structure: R-EB-SUB-S011, R-EB-SUB-S013 | ebRIM | |
| +++ | rim:slot "ReferenceFramework" | The slot is a container to describe the specific aspects and metadata of the ReferenceFramework. | 1..1 | SlotType | AnyValueType | Structure: R-EB-SUB-S017, R-EB-SUB-S021 | ebRIM | - |
| ++++ | ReferenceFramework | The Reference Framework or Procedure that is responsible for the creation/initiation of the Requirement. | 1..n | ReferenceFrameworkType | Structure: R-EB-SUB-S025, R-EB-SUB-S029 | Core Criterion and Core Evidence Vocabulary | cccev:ReferenceFramework | |
| ++++ | ReferenceFramework | The Reference Framework or Procedure that is responsible for the creation/initiation of the Requirement. | 1..n | ReferenceFrameworkType | Structure: R-EB-SUB-S025, | Core Criterion and Core Evidence Vocabulary (CCCEV) | cccev:ReferenceFramework | |
| +++++ | Identifier | The Identifier of the ReferenceFramework or Procedure. | 1..1 | Attribute | Identfier | Content: R-EB-SUB-C015 | CCCEV | cccev:identifier |
| +++++ | Title | The title of the ReferenceFramework orProcedure. | 0..n | Attribute | Text | - | - | |
| ++++++ | Title/@lang | The language of the title encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C016, R-EB-SUB-C017 | - | - |
| +++++ | Description | The description of the ReferenceFramework orProcedure. | 0..n | Attribute | Text | - | - | |
| ++++++ | Description/@lang | The language of the title encoded as ISO 639-1 two-letter code. Default value "en" | M | Attribute | Code | Content: R-EB-SUB-C018, R-EB-SUB-C019 | - | - |
| +++++ | RelatedTo | The Identifier of the SDGR Procedure which this ReferenceFramework or procedure relates to. | 1..n | ReferenceFrameworkType | Structure: R-EB-SUB-S029, R-EB-SUB-S049 | Core Criterion and Core Evidence Vocabulary (CCCEV) | cccev:ReferenceFramework | |
| +++++ | Jurisdiction | The administrative level in which this reference framework applies. It can apply to multiple jurisdictions. | 1..n | JurisdictionType | Structure: R-EB-SUB-S050 | Core Criterion Core Evidence Vocabulary (CCCEV) | cccev:evidenceTypeJurisdiction | |
| +++++ | RelatedTo | The Identifier of the SDGR Procedure which this ReferenceFramework relates to. | 1..n | ReferenceFrameworkType | Structure: R-EB-SUB-S029, R-EB-SUB-S049 | Core Criterion and Core Evidence Vocabulary (CCCEV) | cccev:ReferenceFramework | |
| ++++++ | Identifier | The Identifier of the Procedure. | 1..1 | Attribute | Identfier | Content: R-EB-SUB-C023 | CCCEV | cccev:identifier |
| +++++ | Jurisdiction | The Jurisdiction to which this ReferenceFramework (Procedure) applies. | 1..n | JurisdictionType | Structure: R-EB-SUB-S050 | Core Location Vocabulary (CLV) | locn:Address | |
| ++++++ | AdminUnitLevel1 | The name of the uppermost level of the address, almost always a country. | 1..1 | Attribute | Code | Content: R-EB-SUB-C020 | Core Location Vocabulary (CLV) | locn:adminUnitL1 |
| ++++++ | AdminUnitLevel2 | The name of a secondary level/region of the address, usually a county, state or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-EB-SUB-C021 | Core Location Vocabulary (CLV) | locn:adminUnitL2 |
| ++++++ | AdminUnitLevel3 | The name of a tertiary level/region of the address, usually a municipality or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-EB-SUB-C022 | Core Location Vocabulary (CLV) | locn:adminUnitL3 |
| ++ | rim:RegistryObject <xsi:type="rim:AssociationType"> | An association that links a RegistryObject with another RegistryObject in the SubmitObjectsRequest Message. | 1..n | AssociationType | Structure: R-EB-SUB-S047, R-EB-SUB-S030, R-EB-SUB-S060, R-EB-SUB-S066 | ebRIM | - | |
| +++ | xsi:type | Must be xsi:type="rim:AssociationType" to indicate that this RegistryObject is an association between two RegistryObjects. | 1..1 | Attribute | Code | Structure: R-EB-SUB-S031 | ebRIM | - |
| +++ | id | The unique identifier used to used for identifying this association. | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S006, R-EB-SUB-S043 | ebRIM | - |
| +++ | sourceObject | The unique identifier used as a pointer to a rim:RegistryObject (RegistryObjectType), being the source object (see section 5.3 Associations). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S051, R-EB-SUB-S054, R-EB-SUB-S055 | ebRIM | - |
| +++ | targetObject | The unique identifier used as a pointer to a rim:RegistryObject (RegistryObjectType), being the target object (see section 5.3 Associations). | 1..1 | Attribute | Identifier | Structure: R-EB-SUB-S052, R-EB-SUB-S053, R-EB-SUB-S056 | ebRIM | - |
| +++ | type | The name of the association (see section 5.3 Associations). | 1..1 | Attribute | URI | Structure: R-EB-SUB-S036, R-EB-SUB-S037, R-EB-SUB-S038, R-EB-SUB-S039, R-EB-SUB-S040, R-EB-SUB-S041, R-EB-SUB-S057, R-EB-SUB-S058, R-EB-SUB-S059 | ebRIM | - |
5.4.3. Example of the LCM Submit Objects Request to the EB
The following example shows a complete example of a possible bulk upload for a member state MS, submitting an EvidenceType, an EvidenceTypeList, Requirement, ReferenceFramework and associations that link these RegistryObjects together:
<lcm:SubmitObjectsRequest xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:rs="urn:oasis:names:tc:ebxml-regrep:xsd:rs:4.0"
xmlns:rim="urn:oasis:names:tc:ebxml-regrep:xsd:rim:4.0"
xmlns:query="urn:oasis:names:tc:ebxml-regrep:xsd:query:4.0"
xmlns:lcm="urn:oasis:names:tc:ebxml-regrep:xsd:lcm:4.0"
xmlns:sdg="http://data.europa.eu/p4s"
xmlns:xlink="http://www.w3.org/1999/xlink"
id="urn:uuid:6d51920f-04a7-4482-be34-153e01b0b7a3"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be the fixed value "oots-lcm:v1.0". -->
<rim:Value>oots-lcm:v1.0</rim:Value>
</rim:SlotValue>
</rim:Slot>
<!-- validated with sch/EB-SUB-C.sch and sch/EB-SUB-S.sch-->
<rim:RegistryObjectList>
<rim:RegistryObject id="urn:uuid:a1be6e74-e9ba-4d44-b04c-0376f367b8fd">
<rim:Slot name="EvidenceType">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:EvidenceType>
<!-- EvidenceTypeClassification Information - Provided by the Evidence Broker on the basis of the Semantic Repository. Used for linking with the Semantic Repository and Data Service Directory -->
<sdg:EvidenceTypeClassification>https://sr.oots.tech.ec.europa.eu/evidencetypeclassifications/DE/ca8afed6-2dc0-422a-a931-d21c3d8d370e</sdg:EvidenceTypeClassification>
<sdg:Title lang="EN">Certificate of Birth</sdg:Title>
<sdg:Title lang="DE">Geburtsurkunde</sdg:Title>
<sdg:Description lang="EN">An official certificate of birth of a person - with first name, surname, sex, date and place of birth, which is obtained from the birth register of the place of birth.</sdg:Description>
<sdg:Description lang="DE">Eine amtliche Bescheinigung über die Geburt einer Person – mit Vorname, Familienname, Geschlecht, Datum und Ort der Geburt, welche aus dem Geburtsregister des Geburtsortes erstellt wird.</sdg:Description>
<sdg:Jurisdiction>
<!-- Country - Mandatory - ISO code -->
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<!-- Regional Code not applicable for DE (Common Evidence for the country) -->
</sdg:Jurisdiction>
</sdg:EvidenceType>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 35c299d8-9383-47ce-ad8c-0ed70ea52827 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as EvidenceType -->
<rim:Classification id="urn:uuid:35c299d8-9383-47ce-ad8c-0ed70ea52827"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="EvidenceType"/>
</rim:RegistryObject>
<rim:RegistryObject id="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23">
<!-- List of Evidence Types that proof the Requirement in Germany -->
<rim:Slot name="EvidenceTypeList">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:EvidenceTypeList>
<!-- List of Evidence Types that proof the Requirement in Germany, indicated by the Jurisdiction - DE-->
<!-- Multiple List of Evidence Types might be part of the result - depending on the query paramters -->
<sdg:EvidenceTypeList>
<sdg:Identifier>970918e4-1b27-41f0-be20-0a7c5fe4059f</sdg:Identifier>
<sdg:Name lang="EN">List of Birth Certificates</sdg:Name>
<sdg:Name lang="EN">Liste der Geburtsurkunden</sdg:Name>
</sdg:EvidenceTypeList>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 4d44680b-432c-4b22-aa36-880d4ebd1b0d -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as EvidenceTypeList -->
<rim:Classification id="urn:uuid:4d44680b-432c-4b22-aa36-880d4ebd1b0d"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="EvidenceTypeList"/>
</rim:RegistryObject>
<rim:RegistryObject id="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099">
<rim:Slot name="Requirement">
<!-- The underlying requirement -->
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:Requirement>
<sdg:Identifier>https://sr.oots.tech.ec.europa.eu/requirements/315cfd75-6605-49c4-b0fe-799833b41099</sdg:Identifier>
<sdg:Name lang="EN">Proof of Birth</sdg:Name>
<sdg:Name lang="DE">Geburtsnachweis</sdg:Name>
</sdg:Requirement>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 22333046-3429-4684-85de-d9db69e236a1 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as Requirement -->
<rim:Classification id="urn:uuid:22333046-3429-4684-85de-d9db69e236a1"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="Requirement"/>
</rim:RegistryObject>
<rim:RegistryObject id="urn:uuid:b0c90eb4-6b66-4dd8-8c79-6d964ac3b9a1">
<rim:Slot name="ReferenceFramework">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:ReferenceFramework>
<!-- Link to the Procedure as implemented in Germany, uniquely identified by the Identifier and Jurisdiction. The name of the procedure, as declared in the SDG Regulation; Is possibly extended or replaced with national reference frameworks when the procedure is implemented by a Member State regulation -->
<sdg:Identifier>118fd444-6443-42be-a084-c9fbfd1f674d</sdg:Identifier>
<sdg:Title lang="EN">Procedure #1 - Requesting proof of registration of birth</sdg:Title>
<sdg:Title lang="DE">Verfahren #1 - Beantragung des Nachweises über die Eintragung in das Geburtenregister</sdg:Title>
<sdg:Description lang="EN"> Procedure #1 "Requesting proof of registration of birth" belongs to the life event "Birth" of Annex II of the Regulation (EU) 2018/1724
of the European Parliament and of the Council of 2 October 2018 establishing a single digital gateway to provide access to information, to procedures and to assistance and problem-solving services and amending Regulation (EU) No 1024/2012
</sdg:Description>
<sdg:Description lang="DE"> Das Verfahren #1 "Beantragung des Nachweises über die Eintragung in das Geburtenregister" gehört zum Lebensereignis "Geburt" des Anhangs II der Verordnung (EU) 2018/1724 des Europäischen Parlaments und des Rates vom 2. Oktober 2018 über die Einrichtung eines einheitlichen digitalen Zugangstors zu Informationen, Verfahren, Hilfsund Problemlösungsdiensten und zur Änderung der Verordnung (EU) Nr. 1024/2012
</sdg:Description>
<!-- The Identifier of the SDGR Procedure which this procedure relates to encoded according to Procedures-CodeList.gc. In this case R1 relates to "Requesting a birth certificate" -->
<sdg:RelatedTo>
<sdg:Identifier>R1</sdg:Identifier>
</sdg:RelatedTo>
<!-- Country - Mandatory - ISO code. Requirement is connected to the implementation of Procedure 1 in Germany. Regional Codes (AdminUnitLevel 2 and 3) not applicable for DE in this Procedure (Common Reference Framework for the country) -->
<sdg:Jurisdiction>
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
</sdg:Jurisdiction>
</sdg:ReferenceFramework>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 750869ec-aeac-4cc6-9386-75c86544e433 -->
<!-- The classification scheme under which the specific classification nodes reside for the EB Service -->
<!-- A classification node defining the registry object as ReferenceFramework -->
<rim:Classification id="urn:uuid:750869ec-aeac-4cc6-9386-75c86544e433"
classificationScheme="urn:fdc:oots:classification:eb"
classificationNode="ReferenceFramework"/>
</rim:RegistryObject>
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with DataServiceEvidenceType "Certificate of Birth"-->
<!-- A unique id for this association 826a2206-5dd0-45ff-abbc-23ba8f38477f -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the EvidenceType "Certificate of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:826a2206-5dd0-45ff-abbc-23ba8f38477f"
sourceObject="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23"
targetObject="urn:uuid:a1be6e74-e9ba-4d44-b04c-0376f367b8fd"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:ContainsEvidence"/>
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f"-->
<!-- A unique id for this association 3da4288b-e2ca-4d40-bde2-d3fc2dd04bab -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceTypeList "970918e4-1b27-41f0-be20-0a7c5fe4059f" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the Requirement "Proof of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:3da4288b-e2ca-4d40-bde2-d3fc2dd04bab"
sourceObject="urn:uuid:91197b3c-890b-475f-a07e-709742e59f23"
targetObject="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:FulfillsRequirement"/>
<!-- Associate the Requirement "Proof of Birth" with ReferenceFramework "Procedure #1 - Requesting proof of registration of birth"-->
<!-- A unique id for this association d650d08b-4ca3-4d04-a5d2-255d83b84ce1 -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the Requirement "Proof of Birth" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the ReferenceFramework "Procedure #1 - Requesting proof of registration of birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:d650d08b-4ca3-4d04-a5d2-255d83b84ce1"
sourceObject="urn:uuid:315cfd75-6605-49c4-b0fe-799833b41099"
targetObject="urn:uuid:b0c90eb4-6b66-4dd8-8c79-6d964ac3b9a1"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:DerivesFromReferenceFramework"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
5.4.4. Business Rules associated to the LCM Submit Objects Request to the EB
In order to facilitate interoperability of the successful Query Response of the EB (for the Requirements Query), a set of business rules is defined to guarantee the correct structure, use and format of information objects when receiving query responses from the EB. The rule IDs EB-SUB reference to the EB transaction "LCM Submit Objects Request to the EB" . The business rules are listed in section 3.2.6.
References
ETSI TS 119 182-1. Electronic Signatures and Infrastructures (ESI); JAdES digital signatures; Part 1: Building blocks and JAdES baseline signatures https://www.etsi.org/deliver/etsi_ts/119100_119199/11918201/01.01.01_60/ts_11918201v010101p.pdf.
OASIS. ebXML RegRep Version 4.0 Part 2: Services and Protocols (ebRS). http://docs.oasis-open.org/regrep/regrep-core/v4.0/os/regrep-core-rs-v4.0-os.pdf
RFC 4122. A Universally Unique IDentifier (UUID) URN Namespace. https://www.rfc-editor.org/rfc/rfc4122