VERSION 1.1.0 MANDATORY
Contents
6.1. Introduction
The DSD Service provides an Regrep 4.0 based LCM API, following the Regrep 4.0 LCM SubmitObjects Profile of the OOTS Common Services. 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 DSD is illustrated as Data Model, Implementation Guideline and Example. The Lifecycle Management Specification (see Chapter 3: Common Services - Common Services API Specification) provides a principle overview for a 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 DSD.
6.2 Classification Scheme and Nodes
| Definition Type | Value | Description |
|---|---|---|
| Classification Scheme | urn:fdc:oots:classification:dsd | The classification scheme under which the specific classification nodes reside for the DSD Service |
| Classification Node | EvidenceProvider | A Node defining the registry object as an Evidence Provider (Publisher) Entity |
| Classification Node | DataServiceEvidenceType | A classification node defining the registry object as Data Service Evidence Type |
| Classification Node | AccessService | A classification node defining the registry object as Access Service |
| Association | urn:oasis:names:tc:ebxml-regrep:AssociationType: | The association linking the EvidenceProvider Registry objects with the Data Service Evidence Types |
| Association | urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService | The association linking the Evidence Provider Registry objects with the Access Services |
6.3 Registry Objects
The DSD LCM Interface accepts two different registry objects in the SubmitObjectsRequest Message which are defined in the sections below:
6.3.1 DataServiceEvidenceType
This Registry Object provides the information on the Data Service Evidence Type along the sdg:DataServiceEvidenceType component of the SDG Generic Metadata Profile (SDG-Syntax). It MUST NOT contain the sdg:AccessService details, as these are provided within a seperate Registry Objects AccessService. The classification node used MUST be DataServiceEvidenceType under the DSD Classification Scheme urn:fdc:oots:classification:dsd.
The following diagram shows the structure of the registry object:
A rim:RegistryObject with classification node DataServiceEvidenceType uses a 'rim:Slot name="DataServiceEvidenceType"' with the a ValueType of AnyValueType and the sdg:DataServiceEvidenceType component of the SDG Generic Metadata Profile (SDG-Syntax). An example for the DataServiceEvidenceType Registry Object in XML format is shown below 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:ccbe6e99-abcd-1234-b04c-0376f367b8ff"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be the valid value, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<!-- This is the registry object id for the DataServiceEvidenceType "Certificate of Birth" -->
<rim:RegistryObject id="urn:uuid:61165d22-657b-45fa-9240-f1ed35837c23">
<rim:Slot name="DataServiceEvidenceType">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:DataServiceEvidenceType>
<!-- The Data Service assigned Unique Identifier of the Evidence Type. Must be used in the Evidence Exchange Request -->
<sdg:Identifier>2af27699-f131-4411-8fdb-9e8cd4e8bded</sdg:Identifier>
<!-- Classification Information - Used for linking with the Semantic Repository and Evidence Broker -->
<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>
<!-- Distribution Information - Multiple Distributions per Data Service Evidence Type -->
<!-- XML Distribution, conforming to the common data model on Birth Certificate -->
<sdg:DistributedAs>
<sdg:Format>application/xml</sdg:Format>
<sdg:ConformsTo>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0</sdg:ConformsTo>
</sdg:DistributedAs>
<!-- XML Distribution, conforming to the common data model on Birth Certificate, Linking to the subset "Age of Majority" only -->
<sdg:DistributedAs>
<sdg:Format>application/xml</sdg:Format>
<sdg:ConformsTo>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0</sdg:ConformsTo>
<sdg:Transformation>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0/age-of-majority</sdg:Transformation>
</sdg:DistributedAs>
<!-- PDF Distribution. PDF is unstructured data so there is no conformance to a data model -->
<sdg:DistributedAs>
<sdg:Format>application/pdf</sdg:Format>
</sdg:DistributedAs>
<!-- Level Of Assurance Required for the Evidence Type -->
<sdg:AuthenticationLevelOfAssurance>High</sdg:AuthenticationLevelOfAssurance>
<!-- Free text to include any other important information -->
<sdg:Note lang="EN">Payment: Free of charge</sdg:Note>
<sdg:EvidenceProviderJurisdictionDetermination>
<sdg:JurisdictionContextId>5ce148b9-5578-4049-aecf-af7bb55714b5</sdg:JurisdictionContextId>
<sdg:JurisdictionContext lang="EN">Place Of Birth</sdg:JurisdictionContext>
<sdg:JurisdictionContext lang="DE">Geburtsort</sdg:JurisdictionContext>
<!-- Codelist defining the jurisdiction levels, published in the semantic repository - JurisdictionLevel-CodeList.gc -->
<sdg:JurisdictionLevel>LAU</sdg:JurisdictionLevel>
</sdg:EvidenceProviderJurisdictionDetermination>
<!-- Determination of the EvidenceProviderClassification to the User's attributes. In this example the applicant must indicate if he has ever resided in the country. -->
<sdg:EvidenceProviderClassification>
<sdg:Identifier>b07146b6-1468-41a7-a10f-ee2a61429dbc</sdg:Identifier>
<!-- Value from a Codelist required -->
<sdg:Type>Codelist</sdg:Type>
<!-- Definition of the value expression. Must be published in the Semantic Repository. The codelist contains the values ApplicantHasNeverBeenResidentInGermany and ApplicantHasBeenResidentInGermany -->
<sdg:ValueExpression>https://sr.oots.tech.ec.europa.eu/ep-classification/de/countryresidence</sdg:ValueExpression>
<sdg:Description lang="EN">Rules of responsibility for the processing of personal status cases of German citizens without residence information
</sdg:Description>
<sdg:Description lang="DE">Zuständigkeitsregelungen für die Bearbeitung von personenstandsrechtlichen Vorgängen deutscher Staatsangehöriger ohne Wohnsitzinformation</sdg:Description>
</sdg:EvidenceProviderClassification>
</sdg:DataServiceEvidenceType>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 967d12d8-3c6b-4c8f-878b-da4c0a2f5561 -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as Data Service Evidence Type -->
<rim:Classification id="urn:uuid:967d12d8-3c6b-4c8f-878b-da4c0a2f5561"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="DataServiceEvidenceType"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.3.2 Evidence Provider (Publisher)
This Registry Object provides the information about an Evidence Provider along the component sdg:Publisher of the SDG Generic Metadata Profile (SDG-Syntax). The classification node used MUST be EvidenceProvider under the DSD Classification Scheme urn:fdc:oots:classification:dsd.
The following diagram shows the structure of the registry object:
A rim:RegistryObject with classification node EvidenceProvider uses a 'rim:Slot name="EvidenceProvider"' with the a ValueType of AnyValueType and the sdg:Publisher component of the SDG Generic Metadata Profile (SDG-Syntax). An example for the Evidence Provider Registry Object in XML format is shown below 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:ccbe6e99-abcd-1234-b04c-0376f367b8ff"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be a valid version of the common service, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<!-- This is the registry object id for the Evidence Provider "Civil Registration Office Berlin I" -->
<rim:RegistryObject id="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd">
<!-- The actual Evidence Provider Structure -->
<rim:Slot name="EvidenceProvider">
<rim:SlotValue xsi:type="rim:AnyValueType">
<!-- The Evidence Provider Information - Corner 4 (C4). C4 is the final recipient party, which can be selected to receive the Evidence Request Query. The scheme ID should point to a valid Electronic Address Scheme (EAS) from the codelist EAS.gc -->
<sdg:Publisher>
<sdg:Identifier schemeID="urn:cef.eu:names:identifier:EAS:9930">DE73524311</sdg:Identifier>
<sdg:Name lang="EN">Civil Registration Office Berlin I</sdg:Name>
<sdg:Description lang="EN">The registry office registers your birth, concludes your marriage or civil partnership and also issues the death certificate. In between, there are many services related to the registration of so-called "civil status issues".</sdg:Description>
<sdg:Address>
<sdg:FullAddress>Schönstedtstraße 5, 13357 Berlin, Germany</sdg:FullAddress>
<sdg:LocatorDesignator>5</sdg:LocatorDesignator>
<sdg:PostCode>13357</sdg:PostCode>
<sdg:PostCityName>Berlin</sdg:PostCityName>
<sdg:Thoroughfare>Schönstedtstraße</sdg:Thoroughfare>
<!-- Country Code -->
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<!-- NUTS Code -->
<sdg:AdminUnitLevel2>DE3</sdg:AdminUnitLevel2>
</sdg:Address>
<!-- The Publisher is only able to provide information for LAU 11000000, Berlin, City -->
<sdg:Jurisdiction>
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<sdg:AdminUnitLevel3>11000000</sdg:AdminUnitLevel3>
</sdg:Jurisdiction>
<!-- An Example of an Information Concept that can be used to distinguish the capabilities of the Evidence Provider. In this example the capablity of the publisher to provide information even if the applicant has never resided in the country is identified. The string values indicate that the Publisher is able to provide information even if the applicant has never resided in Germany.-->
<sdg:ClassificationConcept>
<sdg:Identifier>b07146b6-1468-41a7-a10f-ee2a61429dbc</sdg:Identifier>
<sdg:Type>Codelist</sdg:Type>
<!-- Definition of the value expression. Must be published in the Semantic Repository -->
<sdg:ValueExpression>https://sr.oots.tech.ec.europa.eu/ep-classification/de/countryresidence</sdg:ValueExpression>
<sdg:Description lang="EN">Rules of responsibility for the processing of personal status cases of German citizens without residence information
</sdg:Description>
<sdg:Description lang="DE">Zuständigkeitsregelungen für die Bearbeitung von personenstandsrechtlichen Vorgängen deutscher Staatsangehöriger ohne Wohnsitzinformation</sdg:Description>
<sdg:SupportedValue>
<sdg:StringValue>ApplicantHasNeverBeenResidentInGermany</sdg:StringValue>
<sdg:StringValue>ApplicantHasBeenResidentInGermany</sdg:StringValue>
</sdg:SupportedValue>
</sdg:ClassificationConcept>
</sdg:Publisher>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification a8bfb6c5-d8df-4a60-8351-2c5743e43481 -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as EvidenceProvider -->
<rim:Classification id="urn:uuid:a8bfb6c5-d8df-4a60-8351-2c5743e43481"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="EvidenceProvider"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.3.3 Access Service
This Registry Object provides the information about an Access Service along the component sdg:AccessService of the SDG Generic Metadata Profile (SDG-Syntax). It MUST NOT contain the sdg:Publisher details, as these are provided through another Registry Object. The classification node used MUST be AccessService under the DSD Classification Scheme urn:fdc:oots:classification:dsd.
The following diagram shows the structure of the registry object:
A rim:RegistryObject with classification node AccessService uses a 'rim:Slot name="AccessService"' with the a ValueType of AnyValueType and the sdg:AccessService component of the SDG Generic Metadata Profile (SDG-Syntax). An example for an AccessService Registry Object in XML format is shown below 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:ccbe6e99-abcd-1234-b04c-0376f367b8ff"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be a valid version of the common service, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<!-- Other registry objects are omitted for clarity -->
<!-- This is the registry object id for the AccessService that provides access to the DataServiceEvidenceType "Certificate of Birth" and is connecting the Evidence Providers "Civil Registration Office Berlin I" and "Civil Registration Office Hamburg" to the OOTS -->
<rim:RegistryObject id="urn:uuid:54da419f-8847-4410-b182-59e5bff2ab9d">
<!-- The actual AccessService Structure -->
<rim:Slot name="AccessService">
<rim:SlotValue xsi:type="rim:AnyValueType">
<!-- Access Service Metadata - - -->
<!-- Access Service represents the Data Service providing access to the piece of Evidence on behalf of an Evidence Provider -->
<!-- Multiple Access Services, one per Evidence Provider. In this example the same Access Service (e.g. an Intermediary Platform) is associated for both Evidence Providers (Publishers) -->
<sdg:AccessService>
<sdg:Identifier schemeID="urn:cef.eu:names:identifier:EAS:0060">8889909098</sdg:Identifier>
<!-- The identifier of the Access Service, using ebcore Party ID Type. Used in eDelivery Evidence Exchange for PMode Mapping - Corner 3 (C3). C3 is an Access Point that receives messages on behalf of C4. The scheme ID should point to a valid Electronic Address Scheme (EAS) from the codelist EAS.gc -->
<sdg:Name lang="EN">German Intermediary Platform I</sdg:Name>
<sdg:ConformsTo>oots-edm:v1.0</sdg:ConformsTo>
<!-- The Evidence Exchange Data Model profile versions which are supported by this access service (e.g. oots-edm:v1.0, oots-edm:v1.1) -->
</sdg:AccessService>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 584cb81b-40dd-4f33-8880-929cdd9a21ab -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as AccessService -->
<rim:Classification id="urn:uuid:584cb81b-40dd-4f33-8880-929cdd9a21ab"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="AccessService"/>
</rim:RegistryObject>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.4 Associations
The DSD LCM Interface accepts two associations that firstly link an EvidenceProvider with DataServiceEvidenceType (Association: ProvidesEvidenceType ) and secondly an EvidenceProvider with an AccessService (Association: ServiceEvidenceType) in the SubmitObjectsRequest Message. The two associations are defined in the following subsections.
6.4.1 ProvidesEvidenceType
This association provides the link between an EvidenceProvider and a DataServiceEvidenceType. The association must be expressed as rim:RegistryObject with xsi:type="rim:AssociationType" . The type attribute of that association MUST be urn:oasis:names:tc:ebxml-regrep:AssociationType:ProvidesEvidenceType, with the sourceObject pointing to an EvidenceProvider RegistryObject through the use of its id and the targetObject pointing to a DataserviceEvidenceType object through the id of the RegistryObject.
An example association for ProvidesEvidenceType between the registry objects of an EvidenceProvider and a DataServiceEvidenceType in XML format is shown below 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:ccbe6e99-abcd-1234-b04c-0376f367b8ff"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be a valid version of the common service, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<!-- Other Registry Objects are ommitted for clarity -->
<!-- Association: ProvidesEvidenceType -->
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with DataServiceEvidenceType "Certificate of Birth"-->
<!-- A unique id for this association 6201a6cf-54f8-4b4b-8abe-3ab5b1a77fe8 -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Berlin I" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the DataServiceEvidenceType "Certificate of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:6201a6cf-54f8-4b4b-8abe-3ab5b1a77fe8"
sourceObject="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd"
targetObject="urn:uuid:61165d22-657b-45fa-9240-f1ed35837c23"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:ProvidesEvidenceType"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.4.2 UsesAccessService
This association provides the link between an EvidenceProvider and an AccessService. The association must be expressed as rim:RegistryObject with xsi:type="rim:AssociationType" . The type attribute MUST be urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService, with the sourceObject pointing to an EvidenceProvider RegistryObject through the use of its id and the targetObject pointing to a AccessService object through the id of the RegistryObject.
An example association for UsesAccessService between an EvidenceProvider and an AccessService in XML format is shown below 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:ccbe6e99-abcd-1234-b04c-0376f367b8ff"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be a valid version of the common service, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<rim:RegistryObjectList>
<!-- Other Registry Objects are ommitted for clarity-->
<!-- Association: UsesAccessService -->
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with the AccessService "German Intermediary Platform I"-->
<!-- A unique id for this association 7c59a148-6b74-464a-971a-92e9e309c02f -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Berlin I" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the AccessService "German Intermediary Platform I" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:7c59a148-6b74-464a-971a-92e9e309c02f"
sourceObject="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd"
targetObject="urn:uuid:54da419f-8847-4410-b182-59e5bff2ab9d"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.5 LCM Submit Objects to the DSD (Refactored)
6.5.1 Data Model of the LCM Submit Objects Request to the DSD (Refactored)
For the LCM submission, the profile uses the lcm:SubmitObjectsRequest message, as defined by the RegRep 4.0 LCM Manager Interface Specification SubmitObjects Protocol. The lcm:SubmitObjectsRequest message MUST contain a unique id, an attribute checkReferences which is set to the value true, a rim:Slot "SpecificationIdentifier" and one Registry Object List containing the Registry Objects under submission.
The following data model illustrates how a SubmitObjectsRequest to the DSD is constructed based on the SDG OOTS LifeCycleManagementSpecification (see Chapter 3: Common Services - Common Services API Specification).
6.5.2. Implementation Guideline of the LCM Submit Objects Request to the DSD (Refactored)
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 DSD. The data model contains Registry Objects being of "RegistryObjectType" or Registry Objects being of "AssociationType". Registry Objects which are a RegistryObjectType either contain a rim:Slot "DataServiceEvidenceType" , rim:Slot "Evidence Provider" or rim:Slot "AccessService" . Registry Objects which are of "AssociationType" contain a sourceObject pointing to the id of the RegistryObject used to identify a "RegistryObjectType" and a targetObject pointing to the id of the RegistryObject used to identify another "RegistryObjectType" (see section 5.4 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: DSD-SUB_RF-S001, DSD-SUB_RF-S002, DSD-SUB_RF-S030 | ebRIM | |||||
| + | id | The unique identifier of the SubmitObjectsRequest. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S003, DSD-SUB_RF-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-DSD-SUB_RF-S050, R-DSD-SUB_RF-S051 | 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. MUST be a valid version of the common service, e.g. "oots-cs:v1.1". | 1..1 | SlotType | StringValueType | Structure: R-DSD-SUB_RF-S048, R-DSD-SUB_RF-S049 Content: R-DSD-SUB_RF-C049 | ebRIM | - |
| + | rim:RegistryObjectList | Element to list the Registry Objects of the QueryResponse. | 1..1 | RegistryObjectListType | Structure: DSD-SUB_RF-S005, | ebRIM | - | |
| + | rim:RegistryObjectList | Element to list the Registry Objects of the QueryResponse. | 1..1 | RegistryObjectListType | Structure: DSD-SUB_RF-S005, | ebRIM | - | |
| ++ | rim:RegistryObject <rim:Slot "DataServiceEvidenceType"> | The details and metadata of the DataServiceEvidenceType that is related to an Evidence Type. DataServiceEvidenceTypes are related to AccessService. | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S034, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:Slot "AccessService"> | The details of the AccessService that is able to provide access to the DataServiceEvidenceType. AccessServices can operate as gateways for several Evidence Providers | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S046, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:slot "EvidenceProvider"> | The details of the Evidence Provider or Publisher that is able to provide the Evidence Type. Evidence Providers must be associated to an AccessService. | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S033, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| ++ | rim:RegistryObject <xsi:type="rim:AssociationType"> | An association that links a RegistryObject with another RegistryObject in the SubmitObjectsRequest Message. | 1..n | AssociationType | Structure: DSD-SUB_RF-S022, DSD-SUB_RF-S035, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S053 | ebRIM | - | |
| ++ | rim:RegistryObject <rim:Slot "DataServiceEvidenceType"> | The details and metadata of the DataServiceEvidenceType that is related to an Evidence Type. DataServiceEvidenceTypes are related to AccessService. | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S034, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S006, DSD-SUB_RF-S032 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a DataServiceEvidenceType. | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| +++ | rim:slot "DataServiceEvidenceType" | The slot is a container to describe the specific aspects and metadata of the DataServiceEvidenceType. | 1..1 | SlotType | AnyValueType | Structure: DSD-SUB_RF-S015, DSD-SUB_RF-S017 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being a DataServiceEvidenceType. | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| ++++ | id | The unique identifier of this classification. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S008, DSD-SUB_RF-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the DSD Service. FixedValue: urn:fdc:oots:classification:dsd | 1..1 | Attribute | URI | Structure: DSD-SUB_RF-S010, DSD-SUB_RF-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Data Service Evidence Type. FixedValue: DataServiceEvidenceType | 1..1 | Attribute | Code | Structure: DSD-SUB_RF-S011, DSD-SUB_RF-S013 | ebRIM | |
| +++ | rim:slot "DataServiceEvidenceType" | The slot is a container to describe the specific aspects and metadata of the DataServiceEvidenceType. | 1..1 | SlotType | AnyValueType | Structure: DSD-SUB_RF-S015, DSD-SUB_RF-S017 | ebRIM | - |
| ++++ | DataServiceEvidenceType | The element describes specific aspects and metadata of the DataServiceEvidenceType. | 1..1 | DataServiceEvidenceTypeType | Structure: DSD-SUB_RF-S019, DSD-SUB_RF-S020 | SDGR Application Profile | - | |
| ++++ | DataServiceEvidenceType | The element describes specific aspects and metadata of the DataServiceEvidenceType. | 1..1 | DataServiceEvidenceTypeType | Structure: DSD-SUB_RF-S019, DSD-SUB_RF-S020 | SDGR Application Profile | - | |
| +++++ | Identifier | The unique identifier of the Evidence Type of the Data Service. Must be used in the Evidence Request. | 1..1 | Attribute | Identifier | Content: R-DSD-SUB_RF-C001 | DCAT-AP | dct:identifier |
| +++++ | EvidenceTypeClassification | A URI pointing to the Evidence Type that this Data Service is supporting. The classification is linked with the Evidence Type of the Semantic Repository (Evidence Broker). | 1..1 | Attribute | Code | Content: R-DSD-SUB_RF-C002 | Core Criterion Core Evidence Vocabulary | cccev:evidenceTypeClassification |
| +++++ | Title | A name to identify in natural 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. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C003, R-DSD-SUB_RF-C004 | 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. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C005, R-DSD-SUB_RF-C006 | DCAT-AP | dct:description |
| +++++ | AuthenticationLevelOfAssurance | The Minimum eIDAS Level Of Assurance Required for this Evidence Type, so that the Evidence can be released | 0..1 | Attribute | Code | Content: R-DSD-SUB_RF-C037 | SDGR-AP | |
| +++++ | DistributedAs | The representations that are supported by the Data Service Evidence Type. | 1..n | EvidenceTypeDistributionType | DCAT Application Profile | dcat:distribution | ||
| +++++ | EvidenceProviderJurisdictionDetermination | Contextual Information required for the jurisdiction determination of the correct Evidence Provider | 0..1 | JurisdictionDeterminationType | SDGR Application Profile | |||
| +++++ | EvidenceProviderClassification | The Evidence Provider required classifications mapped to this Evidence Type that need to be mapped to an EvidenceProvider Classification Concept for proper Evidence Provider Discovery | 0..n | InformationConceptType | Core Criterion Core Evidence Vocabulary | cccev:InformationConcept | ||
| +++++ | DistributedAs | The representations that are supported by the Evidence Type Dataset. | 1..n | EvidenceTypeDistributionType | DCAT Application Profile | dcat:distribution | ||
| ++++++ | Format | The technical representation of the Evidence Type. Declaration of the file types that provide structured content like PDF, XML, JSON, RDF etc | 1..1 | Attribute | Code | Content: R-DSD-SUB_RF-C007 | DCAT-AP | dct:format |
| ++++++ | ConformsTo | A registered schema or conformance profile in the OOTS semantic repository to which the described Distribution conforms. | 0..1 | Attribute | URI | Content: R-DSD-SUB_RF-C008, R-DSD-SUB_RF-C038, R-DSD-SUB_RF-C039 | DCAT-AP | dct:conformsTo |
| ++++++ | Transformation | The element points to a known and structured evidence type subset that would suffice the request. Evidence type subsets fulfil the principle of data minimization and can limit the collection to those information required for the execution of a procedure. | 0..1 | Attribute | URI | Content: R-DSD-SUB_RF-C009 | DCAT-AP | dct:conformsTo |
| +++++ | EvidenceProviderJurisdictionDetermination | Contextual Information required for the jurisdiction determination of the correct Evidence Provider | 0..1 | JurisdictionDeterminationType | SDGR Application Profile | |||
| ++++++ | JurisdictionContextId | A codified, mappable value of the Jurisdiction Determination Context of an Evidence Provider | 1..1 | Attribute | Identifier | Content: R-DSD-SUB_RF-C015 | SDGR-AP | |
| ++++++ | JurisdictionContext | The Jurisdiction Determination Context of an Evidence Provider in natural language. | 1..n | Attribute | Text | SDGR-AP | ||
| +++++++ | JurisdictionContext/@Lang | The Language used for the Jurisdiction Context. | M | Attribute | Code | Content: R-DSD-SUB_RF-C016, R-DSD-SUB_RF-C017 | SDGR-AP | |
| ++++++ | JurisdictionLevel | The minimum level of the jurisdiction Granularity Required for proper discovery of the Evidence Provider (MS, NUTS1-3, LAU) | 1..1 | Attribute | Code | Content: R-DSD-SUB_RF-C018 | SDGR-AP | |
| +++++ | EvidenceProviderClassification | An Evidence Provider Classification is a structured piece of information that is used to provide the context on the classification concepts defined the Data Service Evidence Type an Evidence Provider needs to provide | 0..n | InformationConceptType | Core Criterion Core Evidence Vocabulary | cccev:InformationConcept | ||
| ++++++ | Identifier | Unambiguous reference to the Information Concept. | 1..1 | Attribute | Identifier | Content: R-DSD-SUB_RF-C010 | CCCEV | cccev:identifier |
| ++++++ | Type | Category to which the Information Concept belongs. | 0..1 | Attribute | Code | Content: R-DSD-SUB_RF-C011 | CCCEV | cccev:type |
| ++++++ | ValueExpression | Formulation in a formal language of the expected value(s) for the Classification Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values. Currently, the Regular Expression language is supported for strings. | 0..1 | Attribute | Text | CCCEV | cccev:expressionOfExpected Value | |
| ++++++ | Description | Short explanation supporting the understanding of the Classification Concept. | 0..n | Attribute | Text | Content: R-DSD-SUB_RF-C012 | CCCEV | cccev:description |
| +++++++ | Description/@lang | The language of the description. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C013, R-DSD-SUB_RF-C014 | CCCEV | cccev:description |
| ++ | rim:RegistryObject <AccessService> | The details of the AccessService that is able to provide access to the DataServiceEvidenceType. AccessServices can operate as gateways for several Evidence Providers | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S046, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S006, DSD-SUB_RF-S032 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being an AccessService | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| +++ | rim:slot "AccessService" | The slot is a container to describe the specific aspects and metadata of AccessService that is able to provide access to the DataServiceEvidenceType. | 1..1 | SlotType | AnyValueType | Structure: R-DSD-SUB_RF-S038, R-DSD-SUB_RF-S039 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being an AccessService. | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| ++++ | id | The unique identifier of this classification. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S008, DSD-SUB_RF-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the DSD Service. FixedValue: urn:fdc:oots:classification:dsd | 1..1 | Attribute | URI | Structure: DSD-SUB_RF-S010, DSD-SUB_RF-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Data Service Evidence Type. FixedValue: AccessService | 1..1 | Attribute | Code | Structure: DSD-SUB-S011, DSD-SUB-S013 | ebRIM | |
| +++ | rim:slot "AccessService" | The slot is a container to describe the specific aspects and metadata of Evidence Provider that is able to provide the DataServiceEvidenceType. | 1..1 | SlotType | AnyValueType | Structure: R-DSD-SUB_RF-S038, R-DSD-SUB_RF-S039 | ebRIM | - |
| ++++ | AccessService | The details of the Data Service providing access to the Evidence Type. | 0..n | DataServiceType | Structure: R-DSD-SUB_RF-S040, R-DSD-SUB_RF-S041 | DCAT Application Profile | dcat:servesDataset | |
| ++++ | AccessService | The details of the Data Service providing access to the Evidence Type. | 0..n | DataServiceType | Structure: R-DSD-SUB_RF-S040, R-DSD-SUB_RF-S041 | DCAT Application Profile | dcat:servesDataset | |
| +++++ | Identifier | The identifier of the Access Service, using ebcore Party ID Type. Used in eDelivery Evidence Exchange for PMode Mapping. | 1..1 | Attribute | Identifier | DCAT-AP | dcat:endpointDescription | |
| ++++++ | Identifier/@schemeID | The schemeID of the ebcore Party ID Type The default value urn:cef.eu:names:identifier:EAS:[Code] SHOULD be used. If there is no appropiate EAS scheme for the postfix, the unregistered option urn:oasis:names:tc:ebcore:partyid-type:unregistered:[Code] MAY be also used together with a ‘ISO 3166-1 alpha-2 country code (EEA_country subset)’ postfix. | M | Attribute | Code | Content: R-DSD-SUB_RF-C020, R-DSD-SUB_RF-C022 | DCAT-AP | dcat:endpointDescription |
| ++++++ | Name | A short label for the Access Service. | 0..n | Attribute | Text | DCAT-AP | dct:title | |
| +++++++ | Name/@lang | The language of the name. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C043, R-DSD-SUB_RF-C044 | DCAT-AP | dct:title |
| +++++ | ConformsTo | The registered version(s) of the eDelivery profile and Exchange Data Model used by the access service (e.g. oots-edm:v1.0, oots-edm:v1.1) | 1..n | Attribute | URI | Content: R-DSD-SUB_RF-C023 | DCAT-AP | dct:conformsTo |
| ++ | rim:RegistryObject <EvidenceProvider> | The details of the Evidence Provider or Publisher that is able to provide the Evidence Type. Evidence Providers must be associated to an AccessService. | 1..n | RegistryObjectType | Structure: DSD-SUB_RF-S033, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S052 | ebRIM | - | |
| +++ | id | Unique UUID for each RegistryObject. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S006, DSD-SUB_RF-S032 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being an EvidenceProvider. | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| +++ | rim:slot "EvidenceProvider" | The slot is a container to describe the specific aspects and metadata of Evidence Provider that is able to provide the Evidence Type. | 1..1 | SlotType | AnyValueType | Structure: DSD-SUB_RF-S014, DSD-SUB_RF-S016 | ebRIM | - |
| +++ | rim:Classification | The classification of the Registry Object being an EvidenceProvider. | 1..1 | ClassificationType | Structure: DSD-SUB_RF-S007 | ebRIM | ||
| ++++ | id | The unique identifier of this classification. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S008, DSD-SUB_RF-S009 | ebRIM | |
| ++++ | classificationScheme | The classification scheme under which the specific classification nodes reside for the DSD Service. FixedValue: urn:fdc:oots:classification:dsd | 1..1 | Attribute | URI | Structure: DSD-SUB_RF-S010, DSD-SUB_RF-S012 | ebRIM | |
| ++++ | classificationNode | A classification node defining the registry object as Data Service Evidence Type. FixedValue: EvidenceProvider | 1..1 | Attribute | Code | Structure: DSD-SUB_RF-S011, DSD-SUB_RF-S013 | ebRIM | |
| +++ | rim:slot "EvidenceProvider" | The slot is a container to describe the specific aspects and metadata of Evidence Provider that is able to provide the Evidence Type. | 1..1 | SlotType | AnyValueType | Structure: DSD-SUB_RF-S014, DSD-SUB_RF-S016 | ebRIM | - |
| +++++ | Publisher | The organisation responsible for issuing Evidences via a Data Service. | 1..1 | EvidenceProviderType | Core Public Service Vocabulary Application Profile (CPSV-AP) | dct:Agent | ||
| +++++ | Publisher | The organisation responsible for issuing Evidences via a Data Service. | 1..1 | EvidenceProviderType | CPSV-AP | dct:Agent | ||
| ++++++ | Identifier | A unique identification for the Evidence Provider (Publisher) or agent. | 1..1 | Attribute | Identifier | CPSV-AP | dct:identifier | |
| +++++++ | Identifier/@schemeID | The schemeID of the unique idenfier of the Evidence Provider (Publisher). The default value urn:cef.eu:names:identifier:EAS:[Code] SHOULD be used. If there is no appropiate EAS scheme for the postfix, the unregistered option urn:oasis:names:tc:ebcore:partyid-type:unregistered:[Code] MAY be also used together with a ‘ISO 3166-1 alpha-2 country code (EEA_country subset)’ postfix. | M | Attribute | Code | Content: R-DSD-SUB_RF-C024, R-DSD-SUB_RF-C025 | CPSV-AP | dct:identifier |
| ++++++ | Name | A short label for the Evidence Provider (Publisher) or agent. | 1..n | Attribute | Text | CPSV-AP | dct:title | |
| +++++++ | Name/@lang | The language of the name. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C045, R-DSD-SUB_RF-C046 | CPSV-AP | dct:title |
| ++++++ | Description | A description of the publisher or agent. Unbounded cardinality to support multiple languages. | 0..n | Attribute | Text | CPSV-AP | dct:description | |
| +++++++ | Description/@lang | The language of the description. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C047, R-DSD-SUB_RF-C048 | CPSV-AP | dct:description |
| ++++++ | Address | A location of the Evidence Provider (Publisher) in the form of an address. | 1..1 | AddressType | Core Location Vocabulary (CLV) | ocn:Address | ||
| ++++++ | Jurisdiction | The Jurisdiction under which this Evidence Provider (Publisher) operates. | 1..1 | JurisdictionType | Core Location Vocabulary (CLV) | ocn:Address | ||
| ++++++ | ClassificationConcept | A Classification Concept is a structured piece of information that is used to provide the supported values on the classification concepts defined the Data Service Evidence Type | 0..n | InformationConceptType | Core Criterion Core Evidence Vocabulary | cccev:InformationConcept | ||
| ++++++ | Address | A location of the Evidence Provider (Publisher) in the form of an address. | 1..1 | AddressType | CLV | locn:Address | ||
| +++++++ | FullAddress | The complete address written as a string. | 0..1 | Attribute | Text | CLV | locn:fullAddress | |
| +++++++ | Thoroughfare | The name of a street, passage or way through from one location to another. | 0..1 | Attribute | Text | CLV | locn:thoroughfare | |
| +++++++ | LocatorDesignator | A number or sequence of characters that uniquely identifies the locator (building number, apartment number, etc.) within the relevant scope. | 0..1 | Attribute | Text | CLV | locn:locatorDesignator | |
| +++++++ | AdminUnitLevel1 | The name of the uppermost level of the address, almost always a country. | 1..1 | Attribute | Code | Content: R-DSD-SUB_RF-C026 | 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-DSD-SUB_RF-C027 | CLV | locn:adminUnitL2 |
| +++++++ | PostCode | The code created and maintained for postal purposes to identify a subdivision of addresses and postal delivery points. | 0..1 | Attribute | Code | CLV | locn:postCode | |
| +++++++ | PostCityName | The key postal division of the address, usually the city. | 0..1 | Attribute | Code | CLV | locn:postName | |
| ++++++ | Jurisdiction | The Jurisdiction under which this Evidence Provider (Publisher) operates. | 1..1 | JurisdictionType | Core Criterion Core Evidence Vocabulary | cccev:evidenceTypeJurisdiction | ||
| +++++++ | AdminUnitLevel1 | The name of the uppermost level of the jurisdiction, almost always a country. | 1..1 | Attribute | Code | Content: R-DSD-SUB_RF-C028 | CLV | locn:adminUnitL1 |
| +++++++ | AdminUnitLevel2 | The name of a secondary level/region of the jurisdiction, usually a county, state or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-DSD-SUB_RF-C029, R-DSD-SUB_RF-S055 | CLV | locn:adminUnitL2 |
| +++++++ | AdminUnitLevel3 | The name of a secondary level/region of the jurisdiction, usually a municipality or other such area that typically encompasses several localities. | 0..1 | Attribute | Code | Content: R-DSD-SUB_RF-C030, R-DSD-SUB_RF-S056 | CLV | locn:adminUnitL3 |
| ++++++ | ClassificationConcept | A Classification Concept is a structured piece of information that is used to provide the supported values on the classification concepts defined the Data Service Evidence Type | 0..n | InformationConceptType | Core Criterion Core Evidence Vocabulary | cccev:InformationConcept | ||
| +++++++ | Identifier | Unambiguous reference to the Information Concept. | 1..1 | Attribute | Identifier | Content: R-DSD-SUB_RF-C031, R-DSD-SUB_RF-S054 | CCCEV | cccev:identifier |
| +++++++ | Type | Category to which the Information Concept belongs. | 0..1 | Attribute | Code | Content: R-DSD-SUB_RF-C032 | CCCEV | cccev:type |
| +++++++ | ValueExpression | Formulation in a formal language of the expected value(s) for the Classification Concept which is aligned with the concepts from the Requirements defined and must be respected by the supplied Supported Values. Currently only Regular Expression is supported. | 0..1 | Attribute | Text | CCCEV | cccev:expressionOfExpected Value | |
| +++++++ | Description | Short explanation supporting the understanding of the Classification Concept. | 0..n | Attribute | Text | Content: R-DSD-SUB_RF-C033 | CCCEV | cccev:description |
| ++++++++ | Description/@lang | The language of the description. Default choice "EN" | M | Attribute | Code | Content: R-DSD-SUB_RF-C034, R-DSD-SUB_RF-C035 | CCCEV | cccev:description |
| +++++++ | SupportedValue | The value that is supported by the response | 0..1 | SupportedValueType | Structure: DSD-SUB_RF-S031 Content: R-DSD-SUB_RF-C036 | SDGR Application Profile | ||
| +++++++ | SupportedValue | The value that is supported by the response | 1..1 | SupportedValueType | Structure: DSD-SUB_RF-S031 | SDGR Application Profile | ||
| ++++++++ | StringValue | Textual field | 1..n | Attribute | String | SDGR-AP | XML Schema data types | |
| ++++++++ | DateValue | Date values (format YYYY-DD-MM) | 1..n | Attribute | Date | SDGR-AP | XML Schema data types | |
| ++++++++ | BooleanValue | "true" or 1 Representing "Yes" affirmative answers "false" or 0 representing "No" negative answers | 1..n | Attribute | Boolean | SDGR-AP | XML Schema data types | |
| ++ | rim:RegistryObject <xsi:type="rim:AssociationType"> | An association that links a RegistryObject with another RegistryObject in the SubmitObjectsRequest Message. | 1..n | AssociationType | Structure: DSD-SUB_RF-S022, DSD-SUB_RF-S035, R-DSD-SUB_RF-S036, R-DSD-SUB_RF-S053 | 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: DSD-SUB_RF-S023 | ebRIM | - |
| +++ | id | The unique identifier used to used for identifying this association. | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S006, DSD-SUB_RF-S032 | ebRIM | - |
| +++ | sourceObject | The unique identifier used as a pointer to a rim:RegistryObject (RegistryObjectType), being the source object (see section 6.4 Associations). | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S024, DSD-SUB_RF-S025, DSD-SUB_RF-S042 | ebRIM | - |
| +++ | targetObject | The unique identifier used as a pointer to a rim:RegistryObject (RegistryObjectType), being the target object (see section 6.4 Associations) . | 1..1 | Attribute | Identifier | Structure: DSD-SUB_RF-S026, DSD-SUB_RF-S027, DSD-SUB_RF-S043 | ebRIM | - |
| +++ | type | The name of the association. Either urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService or urn:oasis:names:tc:ebxml-regrep:AssociationType:ProvidesEvidenceType (see section 6.4 Associations). | 1..1 | Attribute | URI | Structure: DSD-SUB_RF-S028, DSD-SUB_RF-S029, DSD-SUB_RF-S044, R-DSD-SUB_RF-S045, R-DSD-SUB_RF-S037, R-DSD-SUB_RF-S047 | ebRIM | - |
6.5.2.1 Use of component sdg:DistributedAs to markup structured and unstructured sdg:DataServiceEvidenceTypes
The implementation guideline above describes the component sdg:DistributedAs that holds metadata about the accessible form of the sdg:DataServiceEvidenceType such as a the file format. Next to the file format, which can be either a structured or an unstructured file type, the component is used to mark up structured pieces of evidence. As structured piece of evidence needs to be agreed upon Evidence Providers and Evidence Requester in the OOTS eco-system. Therefore, they need to be accomodated by an OOTS data model which is described by the element sdg:ConformsTo that referes to a formal specification published in the Semantic Repository. In this way, an OOTS data model specification is thus associated to each structured evidence type. Subsets of an OOTS data model can be also assoicated to an sdg:DataServiceEvidenceType by using the element sdg:Transformation .
Thus, sdg:DataServiceEvidenceType is described by one distribution containing at least the sdg:Format.The element sdg:ConformsTo is only used if the Format for the sdg:DataServiceEvidenceType is marked as structured in the code list 'OOTSMediaTypes'. The element sdg:ConformsTo links to a conformance profile that relates to an OOTS data model to describe structured pieces of evidence, as it is received from the QueryResponse of the Data Services Directory. The sdg:Format MUST be part of the code list 'OOTSMediaTypes'. The sdg:ConformsTo MUST be a persistent URL with a link to a "DataModelScheme" of the sdg:DataServiceEvidenceType defined by the DSD LCM process and described in the Semantic Repository which uses the prefix "https://sr.oots.tech.ec.europa.eu/datamodels/[DataModelScheme]".
Optionally, the sdg:DistributedAs may also indicate that a specific identified sdg:Transformation is to be applied to the evidence by the Data Service. The format of a sdg:Transformation description MUST be a als persistent URL with link to a "DataModelScheme" and "Subset" of the sdg:DataServiceEvidenceType defined by the DSD LCM process and described in the Semantic Repository which uses the prefix "https://sr.oots.tech.ec.europa.eu/datamodels/[DataModelScheme]/[Subset]". The sdg:Transformation itself is defined in the Semantic Repository along the conformance profile expressed by sdg:ConformsTo . Thus, a sdg:Transformation can be only used if ConformsTo exists. A sdg:Transformation is used to minimize the information in the evidence to a specific information requirement. For example, to prove that a particular person has become an adult and acquired full legal capacity, the person identification and age-related information in a birth certificate is sufficient. Information on place of birth or about parents is not relevant and could therefore be omitted.
The figure below illustrates the process how the different components of the component sdg:DistributedAs are used to mark up sdg:DataServiceEvidenceType.The associated business rules of the component sdg:DistributedAs prove the adherence of instances with the rules of the mark up.
Note: In case a structured sdg:format shall be used without an apporiate OOTS data model, there MUST be an an alternative sdg:DistributedAs element for the same sdg:DataServiceEvidenceType which uses an unstructured sdg:format like jpeg, jpg, png, svg or pdf. In this way it will be ensured that for each structured EvidenceType there is a visual representation that can be selected by the Evidence Requester. This special aspect is not reflected in the illustration below.
6.5.2.2 Use of component sdg:ClassificationConcept and sdg:Jurisdiction to markup issuing capabilities of Evidence Providers
There could be occasions where the proper discovery of the Evidence Provider requires more data to be provided by the User or Evidence Requester. For example, there might be situations where the jurisdiction of the Evidence Provider MUST map to a specific location attribute of the user like the "Place of Birth" or the Evidence Provider serves evidence of specific contexts like the type of insurance, the type of company, etc. The DSD provides the mechanisms for discovering the Evidence Provider based on additional components sdg:EvidenceProviderJurisdictionDetermination and sdg:EvidenceProviderClassification which are associated as principle discovery component of a sdg:DataServiceEvidenceType (see section 3.1.3 and 3.1.4 (4.4.3)).
Evidence Providers which can provide a DataServiceEvidenceType that requires additional discovery component must in turn provide a corresponding value to mark up the capability of Evidence Providers. For example if a specific location attribute like "Place of Birth" will be required by the DataServiceEvidenceType, the Evidence Provider must associate a corresponding definition for its own jurisdiction which indicates the geographical area he has the authority to provide evidence. Likewise, for specific contexts that are described by sdg:EvidenceProviderClassification (e.g. type of insurance) of a sdg:DataServiceEvidenceType,the Evidence Provider must provide a sdg:ClassificationConcept with sdg:SupportedValue (e.g. private insurance) that he is able to issue evidence for.
In the LCM for the DSD however, the relations between the Registry Objects DataServiceEvidenceType and EvidenceProvider are not obviously reflected in a hierachy but through corresponding associations. It must therefore be ensured that when associating an EvidenceProvider with a DataServiceEvidenceType, care is taken to ensure that the corresponding values required by the DataServiceEvidenceType are also described in the EvidenceProvider component. The business rules of the LCM for the DSD therefore provide guidance and prove that instances respect the following dependencies:
| RuleID | Context | Rule | Role |
| R-DSD-SUB_RF-S031 | lcm:SubmitObjectsRequest/rim:RegistryObjectList/rim:RegistryObject/rim:Slot[@name='EvidenceProvider']/ rim:SlotValue/sdg:Publisher/sdg:ClassificationConcept/sdg:SupportedValue | A value for 'sdg:Publisher/sdg:ClassificationConcept/sdg:SupportedValue' MUST be provided if the 'sdg:DataServiceEvidenceType' which is associated to the 'sdg:Publisher' has the element 'sdg:DataServiceEvidenceType/sdg:EvidenceProviderClassification'. | FATAL |
| R-DSD-SUB_RF-S054 | lcm:SubmitObjectsRequest/rim:RegistryObjectList/rim:RegistryObject/rim:Slot[@name='EvidenceProvider']/ rim:SlotValue/sdg:Publisher/sdg:ClassificationConcept/sdg:Identifier | The value of 'sdg:Publisher/sdg:ClassificationConcept/sdg:Identifier' MUST match with one existing 'sdg:DataServiceEvidenceType/sdg:EvidenceProviderClassification/sdg:Identifier' provided by the 'sdg:DataServiceEvidenceType' which is associated to the 'sdg:Publisher'. | FATAL |
| R-DSD-SUB_RF-S055 | lcm:SubmitObjectsRequest/rim:RegistryObjectList/rim:RegistryObject/rim:Slot[@name='EvidenceProvider']/ rim:SlotValue/sdg:Publisher/sdg:Jurisdiction/sdg:AdminUnitLevel2 | The element 'sdg:Publisher/sdg:Jurisdiction/sdg:AdminUnitLevel2'' SHOULD be provided if the 'sdg:DataServiceEvidenceType' which is associated to the 'sdg:Publisher' has on of the values 'NUTS1', 'NUTS2' or 'NUTS3' in the element 'sdg:DataServiceEvidenceType/sdg:EvidenceProviderJurisdictionDetermination/sdg:JurisdictionLevel' . | WARNING |
| R-DSD-SUB_RF-S056 | lcm:SubmitObjectsRequest/rim:RegistryObjectList/rim:RegistryObject/rim:Slot[@name='EvidenceProvider']/ rim:SlotValue/sdg:Publisher/sdg:Jurisdiction/sdg:AdminUnitLevel3 | The element '/sdg:Publisher/sdg:Jurisdiction/sdg:AdminUnitLevel3'' SHOULD be provided if the 'sdg:DataServiceEvidenceType' which is associated to the 'sdg:Publisher' has the value 'LAU' in the element 'sdg:DataServiceEvidenceType/sdg:EvidenceProviderJurisdictionDetermination/sdg:JurisdictionLevel' . | WARNING |
6.5.3 Example of a LCM Submit Objects Request to the DSD (Refactored)
The following example shows a complete example of a possible bulk upload for a member state MS, submitting two EvidenceProviders, a DataserviceEvidenceType and two associations that link them 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:f7dc04fe-337c-4523-85c7-35a7ab95bbac"
checkReferences="true">
<rim:Slot name="SpecificationIdentifier">
<rim:SlotValue xsi:type="rim:StringValueType">
<!-- MUST be a valid version of the common service, e.g. "oots-cs:v1.1". -->
<rim:Value>oots-cs:v1.1</rim:Value>
</rim:SlotValue>
</rim:Slot>
<!-- validated by dsd_lcm_submit.sch-->
<rim:RegistryObjectList>
<!-- - - Evidence Providers - - -->
<!-- This is the registry object id for the Evidence Provider "Civil Registration Office Berlin I" -->
<rim:RegistryObject id="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd">
<!-- The actual Evidence Provider Structure -->
<rim:Slot name="EvidenceProvider">
<rim:SlotValue xsi:type="rim:AnyValueType">
<!-- The Evidence Provider Information - Corner 4 (C4). C4 is the final recipient party, which can be selected to receive the Evidence Request Query. The scheme ID should point to a valid Electronic Address Scheme (EAS) from the codelist EAS.gc -->
<sdg:Publisher>
<sdg:Identifier schemeID="urn:cef.eu:names:identifier:EAS:9930">DE73524311</sdg:Identifier>
<sdg:Name lang="EN">Civil Registration Office Berlin I</sdg:Name>
<sdg:Address>
<sdg:FullAddress>Schönstedtstraße 5, 13357 Berlin, Germany</sdg:FullAddress>
<sdg:LocatorDesignator>5</sdg:LocatorDesignator>
<sdg:PostCode>13357</sdg:PostCode>
<sdg:PostCityName>Berlin</sdg:PostCityName>
<sdg:Thoroughfare>Schönstedtstraße</sdg:Thoroughfare>
<!-- Country Code -->
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<!-- NUTS Code -->
<sdg:AdminUnitLevel2>DE3</sdg:AdminUnitLevel2>
</sdg:Address>
<!-- The Publisher is only able to provide information for LAU 11000000, Berlin, City -->
<sdg:Jurisdiction>
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<sdg:AdminUnitLevel3>11000000</sdg:AdminUnitLevel3>
</sdg:Jurisdiction>
<!-- An Example of an Information Concept that can be used to distinguish the capabilities of the Evidence Provider. In this example the capablity of the publisher to provide information even if the applicant has never resided in the country is identified. The string values indicate that the Publisher is able to provide information even if the applicant has never resided in Germany.-->
<sdg:ClassificationConcept>
<sdg:Identifier>b07146b6-1468-41a7-a10f-ee2a61429dbc</sdg:Identifier>
<sdg:Type>Codelist</sdg:Type>
<!-- Definition of the value expression. Must be published in the Semantic Repository -->
<sdg:ValueExpression>https://sr.oots.tech.ec.europa.eu/ep-classification/de/countryresidence</sdg:ValueExpression>
<sdg:Description lang="EN">Rules of responsibility for the processing of personal status cases of German citizens without residence information
</sdg:Description>
<sdg:Description lang="DE">Zuständigkeitsregelungen für die Bearbeitung von personenstandsrechtlichen Vorgängen deutscher Staatsangehöriger ohne Wohnsitzinformation</sdg:Description>
<sdg:SupportedValue>
<sdg:StringValue>ApplicantHasNeverBeenResidentInGermany</sdg:StringValue>
<sdg:StringValue>ApplicantHasBeenResidentInGermany</sdg:StringValue>
</sdg:SupportedValue>
</sdg:ClassificationConcept>
</sdg:Publisher>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification a8bfb6c5-d8df-4a60-8351-2c5743e43481 -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as EvidenceProvider -->
<rim:Classification id="urn:uuid:a8bfb6c5-d8df-4a60-8351-2c5743e43481"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="EvidenceProvider"/>
</rim:RegistryObject>
<!-- This is the registry object id for the Evidence Provider "Civil Registration Office Hamburg" -->
<rim:RegistryObject id="urn:uuid:20dc247f-c59f-4092-876f-24722f0a3ef2">
<!-- The actual Evidence Provider Structure -->
<rim:Slot name="EvidenceProvider">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:Publisher>
<!-- The Evidence Provider Information - Corner 4 (C4). C4 is the final recipient party, which can be selected to receive the Evidence Request Query. The scheme ID should point to a valid Electronic Address Scheme (EAS) from the codelist EAS.gc -->
<sdg:Identifier schemeID="urn:cef.eu:names:identifier:EAS:0204">02-CivilRegistration-66</sdg:Identifier>
<sdg:Name lang="EN">Civil Registration Office Hamburg</sdg:Name>
<sdg:Address>
<sdg:FullAddress>Hamburger Str. 31</sdg:FullAddress>
<sdg:LocatorDesignator>31</sdg:LocatorDesignator>
<sdg:PostCode>22083</sdg:PostCode>
<sdg:PostCityName>Hamburg</sdg:PostCityName>
<!-- Country Code -->
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<!-- NUTS Code -->
<sdg:AdminUnitLevel2>DE6</sdg:AdminUnitLevel2>
</sdg:Address>
<!-- The Publisher is only able to provide information for LAU 02000000, Hamburg City -->
<sdg:Jurisdiction>
<sdg:AdminUnitLevel1>DE</sdg:AdminUnitLevel1>
<sdg:AdminUnitLevel3>02000000</sdg:AdminUnitLevel3>
</sdg:Jurisdiction>
<!-- An Example of an Information Concept that can be used to distinguish the capabilities of the Evidence Provider. In this example the capablity of the publisher to provide information even if the applicant has never resided in the country is identified. The string values indicate that the Publisher is only able to provide information if the applicant has resided in Germany.-->
<sdg:ClassificationConcept>
<sdg:Identifier>b07146b6-1468-41a7-a10f-ee2a61429dbc</sdg:Identifier>
<sdg:Type>Codelist</sdg:Type>
<!-- Definition of the value expression. Must be published in the Semantic Repository -->
<sdg:ValueExpression>https://sr.oots.tech.ec.europa.eu/ep-classification/de/countryresidence</sdg:ValueExpression>
<sdg:Description lang="EN">Rules of responsibility for the processing of personal status cases of German citizens without residence information
</sdg:Description>
<sdg:Description lang="DE">Zuständigkeitsregelungen für die Bearbeitung von personenstandsrechtlichen Vorgängen deutscher Staatsangehöriger ohne Wohnsitzinformation</sdg:Description>
<sdg:SupportedValue>
<sdg:StringValue>ApplicantHasBeenResidentInGermany</sdg:StringValue>
</sdg:SupportedValue>
</sdg:ClassificationConcept>
</sdg:Publisher>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification ea70b1d9-44c2-4e70-ac4d-3c52da3c7335 -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as EvidenceProvider -->
<rim:Classification id="urn:uuid:ea70b1d9-44c2-4e70-ac4d-3c52da3c7335"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="EvidenceProvider"/>
</rim:RegistryObject>
<!-- - - Access Services - - -->
<!-- This is the registry object id for the AccessService German Intermediary Platform I that provides access for the Evidence Providers "Civil Registration Office Berlin I" and "Civil Registration Office Hamburg" to the OOTS -->
<rim:RegistryObject id="urn:uuid:54da419f-8847-4410-b182-59e5bff2ab9d">
<!-- The actual AccessService Structure -->
<rim:Slot name="AccessService">
<rim:SlotValue xsi:type="rim:AnyValueType">
<!-- Access Service Metadata - - -->
<!-- Access Service represents the Data Service providing access to the piece of Evidence on behalf of an Evidence Provider -->
<!-- Multiple Access Services, one per Evidence Provider. In this example the same Access Service (e.g. an Intermediary Platform) is associated for both Evidence Providers (Publishers) -->
<sdg:AccessService>
<sdg:Identifier schemeID="urn:cef.eu:names:identifier:EAS:0060">8889909098</sdg:Identifier>
<!-- The identifier of the Access Service, using ebcore Party ID Type. Used in eDelivery Evidence Exchange for PMode Mapping - Corner 3 (C3). C3 is an Access Point that receives messages on behalf of C4. The scheme ID should point to a valid Electronic Address Scheme (EAS) from the codelist EAS.gc -->
<sdg:Name lang="EN">German Intermediary Platform I</sdg:Name>
<sdg:ConformsTo>oots-edm:v1.0</sdg:ConformsTo>
<!-- The Evidence Exchange Data Model profile versions which are supported by this access service (e.g. oots-edm:v1.0, oots-edm:v1.1) -->
</sdg:AccessService>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 584cb81b-40dd-4f33-8880-929cdd9a21ab -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as AccessService -->
<rim:Classification id="urn:uuid:584cb81b-40dd-4f33-8880-929cdd9a21ab"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="AccessService"/>
</rim:RegistryObject>
<!-- - - Data Service Evidence Types - - -->
<!-- This is the registry object id for the DataServiceEvidenceType "Certificate of Birth" provided by the Evidence Providers "Civil Registration Office Berlin I" and "Civil Registration Office Hamburg"-->
<rim:RegistryObject id="urn:uuid:61165d22-657b-45fa-9240-f1ed35837c23">
<rim:Slot name="DataServiceEvidenceType">
<rim:SlotValue xsi:type="rim:AnyValueType">
<sdg:DataServiceEvidenceType>
<!-- - - Evidence Type Metadata - - -->
<!-- The Data Service assigned Unique Identifier of the Evidence Type. Must be used in the Evidence Exchange Request -->
<sdg:Identifier>2af27699-f131-4411-8fdb-9e8cd4e8bded</sdg:Identifier>
<!-- Classification Information - Used for linking with the Semantic Repository and Evidence Broker -->
<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>
<!-- Distribution Information - Multiple Distributions per Data Service Evidence Type -->
<!-- XML Distribution, conforming to the common data model on Birth Certificate -->
<sdg:DistributedAs>
<sdg:Format>application/xml</sdg:Format>
<sdg:ConformsTo>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0</sdg:ConformsTo>
</sdg:DistributedAs>
<!-- XML Distribution, conforming to the common data model on Birth Certificate, Linking to the subset "Age of Majority" only -->
<sdg:DistributedAs>
<sdg:Format>application/xml</sdg:Format>
<sdg:ConformsTo>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0</sdg:ConformsTo>
<sdg:Transformation>https://sr.oots.tech.ec.europa.eu/datamodels/certificate-of-birth-1.0.0/age-of-majority</sdg:Transformation>
</sdg:DistributedAs>
<!-- PDF Distribution. PDF is unstructured data so there is no conformance to a data model -->
<sdg:DistributedAs>
<sdg:Format>application/pdf</sdg:Format>
</sdg:DistributedAs>
<!-- Level Of Assurance Required for the Evidence Type -->
<sdg:AuthenticationLevelOfAssurance>High</sdg:AuthenticationLevelOfAssurance>
<!-- Free text to include any other important information -->
<sdg:Note lang="EN">Payment: Free of charge</sdg:Note>
<sdg:EvidenceProviderJurisdictionDetermination>
<sdg:JurisdictionContextId>5ce148b9-5578-4049-aecf-af7bb55714b5</sdg:JurisdictionContextId>
<sdg:JurisdictionContext lang="EN">Place Of Birth</sdg:JurisdictionContext>
<sdg:JurisdictionContext lang="DE">Geburtsort</sdg:JurisdictionContext>
<!-- Codelist defining the jurisdiction levels, published in the semantic repository - JurisdictionLevel-CodeList.gc -->
<sdg:JurisdictionLevel>LAU</sdg:JurisdictionLevel>
</sdg:EvidenceProviderJurisdictionDetermination>
<!-- Determination of the EvidenceProviderClassification to the User's attributes. In this example the applicant must indicate if he has ever resided in the country. -->
<sdg:EvidenceProviderClassification>
<sdg:Identifier>b07146b6-1468-41a7-a10f-ee2a61429dbc</sdg:Identifier>
<!-- Value from a Codelist required -->
<sdg:Type>Codelist</sdg:Type>
<!-- Definition of the value expression. Must be published in the Semantic Repository. The codelist contains the values ApplicantHasNeverBeenResidentInGermany and ApplicantHasBeenResidentInGermany -->
<sdg:ValueExpression>https://sr.oots.tech.ec.europa.eu/ep-classification/de/countryresidence</sdg:ValueExpression>
<sdg:Description lang="EN">Rules of responsibility for the processing of personal status cases of German citizens without residence information
</sdg:Description>
<sdg:Description lang="DE">Zuständigkeitsregelungen für die Bearbeitung von personenstandsrechtlichen Vorgängen deutscher Staatsangehöriger ohne Wohnsitzinformation</sdg:Description>
</sdg:EvidenceProviderClassification>
</sdg:DataServiceEvidenceType>
</rim:SlotValue>
</rim:Slot>
<!-- A unique id for this classification 967d12d8-3c6b-4c8f-878b-da4c0a2f5561 -->
<!-- The classification scheme under which the specific classification nodes reside for the DSD Service -->
<!-- A classification node defining the registry object as Data Service Evidence Type -->
<rim:Classification id="urn:uuid:967d12d8-3c6b-4c8f-878b-da4c0a2f5561"
classificationScheme="urn:fdc:oots:classification:dsd"
classificationNode="DataServiceEvidenceType"/>
</rim:RegistryObject>
<!-- - - Associations - - -->
<!-- Association: UsesAccessService -->
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with the AccessService "German Intermediary Platform I"-->
<!-- A unique id for this association 7c59a148-6b74-464a-971a-92e9e309c02f -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Berlin I" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the AccessService "German Intermediary Platform I" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:7c59a148-6b74-464a-971a-92e9e309c02f"
sourceObject="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd"
targetObject="urn:uuid:54da419f-8847-4410-b182-59e5bff2ab9d"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService"/>
<!-- Association: UsesAccessService -->
<!-- Associate the EvidenceProvider "Civil Registration Office Hamburg" with the AccessService "German Intermediary Platform I"-->
<!-- A unique id for this association bab0070e-a538-47b2-8e72-e283ecfccb4f -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Hamburg" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the AccessService "German Intermediary Platform I" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:bab0070e-a538-47b2-8e72-e283ecfccb4f"
sourceObject="urn:uuid:20dc247f-c59f-4092-876f-24722f0a3ef2"
targetObject="urn:uuid:54da419f-8847-4410-b182-59e5bff2ab9d"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:UsesAccessService"/>
<!-- Association: ProvidesEvidenceType -->
<!-- Associate the EvidenceProvider "Civil Registration Office Berlin I" with DataServiceEvidenceType "Certificate of Birth"-->
<!-- A unique id for this association 6201a6cf-54f8-4b4b-8abe-3ab5b1a77fe8 -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Berlin I" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the DataServiceEvidenceType "Certificate of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:6201a6cf-54f8-4b4b-8abe-3ab5b1a77fe8"
sourceObject="urn:uuid:a1be6e74-bbbb-4444-b04c-0376f367b8fd"
targetObject="urn:uuid:61165d22-657b-45fa-9240-f1ed35837c23"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:ProvidesEvidenceType"/>
<!-- Association: ProvidesEvidenceType -->
<!-- Associate the EvidenceProvider "Civil Registration Office Hamburg" with DataServiceEvidenceType "Certificate of Birth"-->
<!-- A unique id for this association 4933a144-6c11-4560-b082-f1c4b9d26f16 -->
<!-- The sourceObject is the 'rim:RegistryObject' id of the EvidenceProvider "Civil Registration Office Hamburg" -->
<!-- The targetObject is the 'rim:RegistryObject' id of the DataServiceEvidenceType "Certificate of Birth" -->
<rim:RegistryObject xsi:type="rim:AssociationType"
id="urn:uuid:4933a144-6c11-4560-b082-f1c4b9d26f16"
sourceObject="urn:uuid:20dc247f-c59f-4092-876f-24722f0a3ef2"
targetObject="urn:uuid:61165d22-657b-45fa-9240-f1ed35837c23"
type="urn:oasis:names:tc:ebxml-regrep:AssociationType:ProvidesEvidenceType"/>
</rim:RegistryObjectList>
</lcm:SubmitObjectsRequest>
6.5.4 Business Rules associated to a LCM Submit Objects Request to the DSD (Refactored)
In order to facilitate interoperability for the LCM SubmitObjectsRequest to the DSD, a set of business rules is defined to guarantee the correct structure, use and format of information objects when submitting objects to the DSD. The Rule IDs DSD-SUB_RF reference to the DSD transaction "LCM Submit Objects Request to the DSD ('Refactored)". The business rules are listed in section 3.1.7.
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