Added '00' as valid procedure code for production tests in relevant schematrons rules (R-EB-EVI-C012, R-EB-REQ-C012, R-EB-SUB-C023, R-EDM-REQ-C003, R-EDM-REQ-C081)

b6795cbb

Aligned Schematron (R-EDM-ERR-C011) with Business Rules and Specifications to allow more than one Exception in Evidence Error Response

f444381c

Alignment of description of schematron rule (R-EDM-REQ-C055, R-EDM-ebMS-006, R-EDM-ebMS-021) with description of business rules

Related Artifacts

Correction

Relax rules R-DSD-RESP-C015 and R-DSD-SUB_RF-C023

CS 1.1.0 is not aware of EDM 1.2.0 entries in ConformsTo statement of Access Services. This was a development that was not foreseen when the 1.1.0 rules were created.

The patch 1.1.1 will make that rule flexible and to allow oots-edm:v1.2 and other versions in sdg:AccessService/ sdg:ConformsTo

• The value of 'ConformsTo' of the Access Service MUST point to the underlying eDelivery Profile 'oots-edm:<MAJOR>: <MINOR>'.

8fd181a4

Chapter 1

Correction

Clarifications to better reflect the requirements of Article 11 and the use of the eIDAS nodes.

1.4.4

Correction

Correct reference to section where there is more information on eIDAS.

1.4.4

Correction

Update on Unique Identifier for natural person to reflect the updates in chapter 2.

1.8.3

Correction

Update to reflect the changes in Article 3 of Regulation (EU) No 910/2014 amended by Regulation (EU) 2024/1183.

1.8.6

Correction

Remove status of OOTS sector specific attribute to reflect the fact that it has been published.

1.8.6

Chapter 2

New content

Updates to reflect the new type of person identification data from Article 3 of Regulation (EU) No 910/2014 amended by Regulation (EU) 2024/1183, in particular natural person representing another natural person.

2.1

2.3

New content

Added support for transliteration for some of the eIDAS attributes.

2.1.2.2

2.1.2.4

2.1.2.5

New content

Update to reflect the support of eIDAS Profile v 1.4.

2.1

2.3

New content

Added clarifications on the scope of the provision of additional attributes related to Article 16(1) of Commission Implementing Regulation (EU) 2022/1463.

2.1.3.2

Correction

Renamed section 2.4. and added a new one 2.7. to separate the sector specific attribute from optional eIDAS attributes.

2.1.2.4

2.1.2.7

Correction

Clarifications about the level of assurance and the scope of reauthentication as stated in Article 16 of Commission Implementing Regulation (EU) 2022/1463.

2.1.2.1

Correction

Update the information on when to send the eIDAS Unique Identifier for Natural Person and clarify that this doesn’t apply for Legal Person.

 2.1.2.3

New content

Updated information on the cases where the eIDAS Unique Identifier for Natural Person is sent or not and it is an incident.

2.1.2.3

2.1.2.5

Correction

Corrected PlaceOfBirth notes.

2.1.2.2

Correction

Updated title to reflect the section name from eIDAS Profile.

2.1.2.6

Correction

Changed title and simplified text to address the comments made.

2.1.3.1

Removed

Removed section 2.1.5.

2.1.5

New content

Added more explanation on the use of Power of Representation Scope.

2..3.4

Correction

Removed the value ALL from the possible values of “Power of Representation Scope”.

2.3.4

Correction

Updated reference to the approved OOTS sector-specific attribute - Power of Representation Scope.

2.3.6

Reference to the new codelist UIDSuppressionCountry-CodeList.gc.

2.1.2.3

Clarified the possible values contained in “Power of Representation Scope”.

2.3.4

Update reference to the latest eIDAS profile version.

2.1.2.2

Chapter 3

Included some content of the separate "deployment configuration data for OOTS" page in the Common Services distribution section.

3.4.5

Introduction of HTTP header versioning for Common Services

Versioning  in HTTP headers enables procedure portals of the Member States to issue query request for a particular version and receive query responses from the Common Services in the desired version. The HTTP request therefore shall contain an optional "Accept-version" header that is used by the client to indicate to the server the specification version, or versions, supported by the client.

3.6.2 (2.6)

New mandatory rim:slot "SpecificationIdentifier" in all Common Services transactions

A new mandatory rim:slot "SpecificationIdentifier" is introduced for in all Common Services transactions to better distinguish between different versions. The "SpecificationIdentifier" is used to indicate the version of the responses of the Common Services. The "SpecificationIdentifier" was introduced to all Data Models, Implementation Guidelines and XML examples of Common Services transactions: DSD Query Response, DSD Error Response, EB Query Response for the "Requirement Query", EB Query Response for the "Evidence Types", EB Error Response as well as LCM Successfull Response and LCM Error Response

Previously already containted an optional "SpecificationIdentifier" for the LCM Submit Objects to EB and a mandatory for the LCM Submit Objects to DSD (Refactored) . The "SpecificationIdentifier" for the LCM Submit Objects to EB is now mandatory.

The previous LCM specific scheme oots-LCM:v1.0 was deleted. For all transactions, Query and LCM, the same scheme was introduced oots-cs:v1.1. 

Corresponding structure and content Business Rules, to test for the presence and scheme of specification identifiers where introduced. 

3.1.4

3.1.6

3.2.4

3.2.5

3.6.2

3.6.3

3.1.7

3.2.6

Due to new EDM version oots-edm:v1.1, DSD business rules and schematrons now allow the use of the new value in 'ConformsTo'. Corresponding examples and descriptions were updated.

3.1.1

 The URI to declare the datamodel in the class "DistributedAs/ConformsTo" was changed from https://sr.oots.tech.ec.europa.eu/distributions/ to https://sr.oots.tech.ec.europa.eu/datamodels/

3.1.1

 Added the new query parameter "specification"  that can be used to filter DSD result sets for specific data exchange profiles and versions that are supported by an Access Service in the ConformsTo statement.

3.1.4

Reworded 'Default value "EN"' into 'Default choice "EN"'. EN is a preferred way but not a default way of describing information entities in the OOTS.

3.1.1

3.2.1

Removal

 Removal of deprecated feature and section "3.1.5 LCM Interface Specification of the DSD - Baseline (Draft)"

3.1.5

Chapter 4

 Included some content of the separate "deployment configuration data for OOTS" page in the eDelivery configuration section.

4.7.6

Included the clarification of possible interactions with the user in preview space. This clarification was provided in response to TDD discussion forum question 25.  

4.9.2

 Added new common attributes to legal and natural person that were introduced by the eIDAS SAML attribute profile version 1.4. The common attributes are optional and not part of the MDS. All relevant sections (data model, implementation guidelines, and XML examples where updated). Included attributes:

For Natural Person: Nationality, CountryOfBirth, TownOfBirth, CountryOfResidence, PhoneNumber, EmailAddress

For Legal Person: LegalPhoneNumber, LegalEmailAddress

4.5.1

Added new slot "AuthorizedRepresentativeLegalPerson" to support representation through legal persons

4.5.1

 Added an optional "nonLatin" attribute for eIDAS name attributes where transcription occurred and the original non-Latin value is available

4.5.1

Refined the use of PowerOfRepresentationScope. Absence of the SectorSpecificAttribute "PowerOfRepresentationScope" means full powers. The sdg:AttributeValue MUST use a single or comma separated code value from the SDG Procedure code list publicly available at the OOTS repository, meaning the representative person has power of representation for the represented (legal/natural) person in the specified SDG procedure that should match with the procedure context declared in the Evidence Request slot "Procedure". 

4.5.1

Removed business rules that test values for AdminLevelUnit2 against NUTS for eIDAS related attributes as eIDAS can use any value here. 

4.5.1

Created new business rules for common attributes to legal and natural person that were introduced by the eIDAS SAML attribute profile version 1.4 and for the support of new slot "AuthorizedRepresentativeLegalPerson"

4.5.4

Changed TDD release version in EDM artifacts (Business Rules, Schematrons, Examples) to version oots-edm:1.1

4.5.1-4.5.4

Making cardinality of "code" in "Exception" of Evidence Error Response mandatory. New Business Rule EDM-ERR-C026.

4.5.3- 4.5.4

The recommended preview method and return method is limited to GET, reflecting current implementation experience.  POST and PUT are still supported for backward compatibility reasons. 

4.9.4

4.9.5

The cardinality of LegalPersonIdentifier was changed from optional to mandatory, in both the Evidence Request and Evidence Response transaction. Corresponding Business Rules R-EDM-REQ-C084 and R-EDM-RESP-C033 have been changed from Warning to Fatal Errors. 

4.5.1

4.5.2

The URI to declare the datamodel in the class "DistributedAs/ConformsTo" was changed from https://sr.oots.tech.ec.europa.eu/distributions/ to https://sr.oots.tech.ec.europa.eu/datamodels/

4.5

Reworded 'Default value "EN"' into 'Default choice "EN"'. EN is a preferred way but not a default way of describing information entities in the OOTS.

4.5

Added a reference to the new code list UIDSuppressionCountry that list Member States for which the natural person unique identifier is not to be included in the evidence request.  

4.5.1.3.1.6

Updated Links in Requirements (REQ16-18) for eIDAS SAML Attribute Profile v1.4 and changed requirement R018 to support representation by legal persons. 

4.3

Adding "collectionType" in XML examples and testfiles where it was missing. New business rule was introduced in release 1.0.5 to test for presence of collectionType="urn:oasis:names:tc:ebxml-regrep:CollectionType:Set" in all 'xsi:type="rim:CollectionValueType"' .

4.5.1

4.5.2

4.5.4

Several dependencies between the Query Response of the DSD and the creation of the Evidence Request were further clarified

• It was clarified that the SpecificationIdentifier must match with the ConformsTo statement of the Access Service that has been chosen by the Evidence Requester during the DSD Query Process and to which the Evidence Request will be addressed. 
• It was clarified that the Publisher information of the Query Response of the DSD shall be adopted in the Evidence Provider slot of the Evidence Request.
• It was clarified that the the DataServiceEvidenceType of the Evidence Request is adopted from the QueryResponse of the Data Services Directory but the "AuthenticationLevelOfAssurance" and "Note" elements are omitted .

4.5.1

(2.2)

(3.3)

(3.5)

Related Artifacts

New OOTS Language Code list derived from the UBL language code list limited to the two letter language identifiers 

01f68488

Added an optional "nonLatin" attribute for eIDAS name attributes where transcription occurred and the original non-Latin value is available

a382731f

9b9d32f3

Regenerated XML schema documentation 

dfd3c385

Created version 1.1.0 of Generic metadata profile of the SDG XSD. Added new common attributes to legal and natural person that were introduced by the eIDAS SAML attribute profile version 1.4: 

Natural Person: Nationality, CountryOfBirth, TownOfBirth, CountryOfResidence, PhoneNumber, EmailAddress

Legal Person: LegalPhoneNumber, LegalEmailAddress

0588ff89

705459e2

Developed new tooling for handling codelists. 

In essence,  the tool generates  for each Genericode file in the codelist directory,  an importable Schematron fragment that only defines a variable named after the filename, for example "LanguageCode-Codelist.sch".  

All generated fragments are available in tdd_chapters/OOTS-EDM/sch/codelist-include folder.

Then for any Schematron that has a rule for a codelist,  is imported the relevant codelist fragment.  After the import, the value set is in a variable that can be used in any expression.

c6d8af39

1142d6d7

248710bf

bd9b2f06

e4b4d5c1

d55d9d32

8c8799d4

633a4c5a 

96568ff3

Added new common attributes to legal and natural person XML examples that were introduced by the eIDAS SAML attribute profile version 1.4. Created additional slot and snippet for Authorized Representative Legal Person. 

 Removed business rules that test values for AdminLevelUnit2 against NUTS for eIDAS related attributes as eIDAS can use any value here. 

4392af85

Created new business rules for common attributes to legal and natural person that were introduced by the eIDAS SAML attribute profile version 1.4 and for the support of new slot "AuthorizedRepresentativeLegalPerson". Update of corresponding examples.

f74dac7c

Changed TDD release version in EDM artifacts (Business Rules, Schematrons, Examples, Regression Testing) to version oots-edm:1.1

1becf6b7

618a5993

f557f1f6

4e8b227f

e9fef060

8574dba4

Removed xsi:schemaLocation from all EDM-ebMS header examples and snippets as it is not used

e154ff9c

Updated distributions (XLSX and GC) of OOTS codelists:

• New semantic version scheme for internal codelist starting with 1.0.0
  
• New DIGIT name "Directorate-General for Digital Services" for internal codelist Agency,
  
• Updated LanguageCode headers in Procedure Codelist,
  
• Removed application/jpg in OOTSMediaTypes codelist
  
• Restrict LanguageCode to alpha-2 codes and created OOTS specific subset
• Updated Language, CountryCode and EEA Country codelist metadata,
  
• Updated codelist descriptions in XLSX for Business Rules,
• Updated OOTSMediaTypes codelist. Removed .jpg codes and values
• Added new 2024 version of EAS codelist

5837a669

907556af

2dd7dd6d

9bbcee5e

Making cardinality of "code" in "Exception" of Evidence Error Response mandatory. New Business Rule, Schematron and Regression test (EDM-ERR-C026).

90a5f621

New Schematrons and XML Examples for illustrating/testing new mandatory rim:slot "SpecificationIdentifier" in all Common Services transactions

The "SpecificationIdentifier" was introduced to all Common Services transactions: DSD Query Response, DSD Error Response, EB Query Response for the "Requirement Query", EB Query Response for the "Evidence Types", EB Error Response as well as LCM Successfull Response and LCM Error Response

Corresponding Schematrons, to test for the presence and scheme of specification identifiers, were introduced. 

New Rules: R-DSD-RESP-C050, R-DSD-RESP-S020, R-DSD-RESP-S021, R-DSD-RESP-S022, R-DSD-ERR-C029, R-DSD-ERR-S028, R-DSD-ERR-S029, R-DSD-ERR-S030, R-EB-EVI-C025, R-EB-EVI-S025, R-EB-EVI-S026, R-EB-REQ-C013, R-EB-REQ-S025, R-EB-REQ-S026, R-EB-ERR-018, R-EB-ERR-019, R-EB-ERR-020, R-EB-SUB-C024, R-EB-SUB-S070, R-LCM-ERR-018, R-LCM-ERR-019, R-LCM-ERR-020, R-LCM-SUC-009, R-LCM-SUC-010, R-LCM-SUC-011

Changed Rules: R-DSD-SUB_RF-C049, R-DSD-SUB_RF-S048, R-EB-EVI-S010, R-EB-REQ-S012, R-EB-ERR-017, R-LCM-SUB-S080, R-LCM-ERR-017, R-LCM-SUC-008

Also all XML examples were updated.

f95b809f

0eb7531a

5bd9aa06

Due to new EDM version oots-edm:v1.1, DSD business rules and schematrons now allow the use of the new value in 'ConformsTo'. Corresponding examples and descriptions were updated.

0f094fdd

The cardinality of LegalPersonIdentifier was changed from optional to mandatory, in both the Evidence Request and Evidence Response transaction. Corresponding Business Rules R-EDM-REQ-C084 and R-EDM-RESP-C033 have been changed from Warning to Fatal Errors. 

0a1b04fb

37a0a370

f74dac7c

Support for four procedures added to appendix II by SDGR amendments:

• X10: Notification of a data intermediation services provider
• X11: Registration as a data altruism organisation recognised in the Union
  
• AK1: Procedures for all relevant permits to build, expand, convert and operate net-zero technology manufacturing projects, and net-zero strategic projects, including building, chemical and grid connection permits, environmental assessments and authorisations where required, and encompassing all applications and procedures.
  
• AL1: Procedure related to all relevant permits to build and operate critical raw materials projects, including building, chemical and grid connection permits and environmental assessments and authorisations where these are required, and encompassing all applications and procedures from the acknowledgment that the application is complete to the notification of the comprehensive decision on the outcome of the procedure by the single point of contact concerned pursuant to Article 9 of Regulation (EU) 2024/1252.

These codes relate to regulations all currently in force for OOTS:

• REGULATION (EU) 2022/868 of May 2022 (Data Governance Act)
• REGULATION (EU) 2024/1252 adopted in April 2024 (Critical raw Materials Act ). 
• REGULATION (EU) 2024/1735 adopted in June 2024 (Net Zero Industry Act). 

42556a7e

dd01c058

New code list UIDSuppressionCountry-CodeList.gc listing countries for which the unique eIDAS person identifier for natural persons should not be included in evidence requests.

6dba2cc9

 The URI to declare the datamodel in the class "DistributedAs/ConformsTo" was changed from https://sr.oots.tech.ec.europa.eu/distributions/ to https://sr.oots.tech.ec.europa.eu/datamodels/

b2545ab0

16030d6f

Reworded 'Default value "EN"' into 'Default choice "EN"'. EN is a preferred way but not a default way of describing information entities in the OOTS.

275943d7

Create rules for Jurisdiction(CS and LCM) that check AdminLevel1 and AdminLevel2 must be present if AdminLevel3 is used and that AdminLevel1 is present if AdminLevel2 is used. Business rules and RegressionTesting snippets were created

36ed7655

Updated version information and metadata of codelist and schematron files in git.

QA of changes and new rules. 

Removed directories with old versions of codelists, XML examples and business rules.

Removed DSD-LCM Baseline artifacts and files in git.

8b577291

57e5c919

534bf854

75b94f16

bc7a6f0f

ed26b59e

309bb633

0c632933

2031fde5

Refined the use of PowerOfRepresentationScope. Absence of the SectorSpecificAttribute "PowerOfRepresentationScope" means full powers. The sdg:AttributeValue MUST use a single or comma separated code value from the SDG Procedure code list publicly available at the OOTS repository, meaning the representative person has power of representation for the represented (legal/natural) person in the specified SDG procedure that should match with the procedure context declared in the Evidence Request slot "Procedure". Changed corresponding schematrons. 

7fce8ba6

0c13a8cd

d34d3199

5a1bb003

Added "collectionType" in XML examples and testfiles where it was missing. New business rule was introduced in release 1.0.5 to test for presence of collectionType="urn:oasis:names:tc:ebxml-regrep:CollectionType:Set" in all 'xsi:type="rim:CollectionValueType"' .

ce844083

Removed string-lenth() from cross-validation schematrons as it caused errors in elements with 0..n or 1...n cardinality

551cd569

Fixed cross-message validation of the DSD Response and EDM Request.  Rule DSD-RESP_EDM-REQ_09 and missing snippets were added.

54acb2db

9439c78f

Final checks and edits for Business Rules files (EDM and cross-validation)

ff98dd0c

80b7fba4

1

Once-Only Technical System High Level Architecture

-

1.0.0

1.1.0

Wiki

HLA

Architecture

HLA

Mandatory

1.1.0

September 2024

2.1

Identity and Record Matching

-

1.0.0

1.1.0

Wiki

eID

Specification

eID

Mandatory

1.1.0

September 2024

2.2

OOTS eID additional security services

-

1.0.0

1.0.1

Wiki

eID

Specification

eID

Mandatory

1.1.0

September 2024

2.3

Representation

-

1.0.0

1.1.0

Wiki

eID

Specification

eID

Mandatory

1.1.0

September 2024

3.1.1.-3.1.4

Data Service Directory

-

1.0.0

1.1.0

Wiki

DSD

Specification

DSD

Mandatory

1.1.0

September 2024

3.1.4

Query Interface Specification of the DSD

4.2. Query: Find Data Services of Evidence Providers for a specific Evidence Type Classification

1.0.0

1.1.0

Wiki (Subsec.)

DSD

Specification

DSD

Mandatory

1.1.0

September 2024

3.1.4

Query Interface Specification of the DSD

4.3. Query Response of the DSD

1.0.0

1.1.0

Wiki (Subsec.)

DSD

Specification

DSD-RESP

Mandatory

1.1.0

September 2024

3.1.4

Query Interface Specification of the DSD

4.4 Query Error Response of the DSD

1.0.0

1.1.0

Wiki (Subsec.)

DSD

Specification

DSD-ERR

Mandatory

1.1.0

September 2024

3.1.5

LCM Interface Specification of the DSD - Baseline

-

0.9.0

-

Wiki

DSD

Specification

DSD-SUB

Deprecated

-

-

3.1.6

LCM Interface Specification of the DSD - Refactored

-

1.0.0

1.1.0

Wiki

DSD

Specification

DSD-SUB

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

1. DSD-RESP-C

1.0.1

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-RESP

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

2. DSD-RESP-S

1.0.2

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-RESP

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

3. DSD-ERR-C

1.0.0

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-ERR

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

4. DSD-ERR-S

1.0.3

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-ERR

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

5. DSD-SUB-C

1.0.0

-

Git

DSD

Schematron (Business Rule)

DSD-SUB

Deprecated

-

-

3.1.7

Business Rules (DSD)

6. DSD-SUB-S

1.0.2

-

Git

DSD

Schematron (Business Rule)

DSD-SUB

Deprecated

-

-

3.1.7

Business Rules (DSD)

7. DSD-SUB_RF-C

1.0.0

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-SUB_RF

Mandatory

1.1.0

September 2024

3.1.7

Business Rules (DSD)

8. DSD-SUB_RF-S

1.0.3

1.1.0

Git

DSD

Schematron (Business Rule)

DSD-SUB_RF

Mandatory

1.1.0

September 2024

3.2.1-3.2.4

Evidence Broker (EB)

-

1.0.0

1.1.0

Wiki

EB

Specification

EB

Mandatory

1.1.0

September 2024

3.2.4

Query Interface Specification of the EB

4.2. Get List of Requirements Query

1.0.1

1.1.0

Wiki (Subsec.)

EB

Specification

EB-REQ

Mandatory

1.1.0

September 2024

3.2.4

Query Interface Specification of the EB

4.3. Get Evidence Types for Requirement Query

1.0.0

1.1.0

Wiki (Subsec.)

EB

Specification

EB-EVI

Mandatory

1.1.0

September 2024

3.2.4

Query Interface Specification of the EB

4.4. Query Error Response of the Evidence Broker

1.0.0

1.1.0

Wiki (Subsec.)

EB

Specification

EB-ERR

Mandatory

1.1.0

September 2024

3.2.5

LCM Interface Specification of the EB

-

1.0.0

1.1.0

Wiki

EB

Specification

EB-SUB

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

1. EB-EVI-C

1.0.0

1.1.0

Git

EB

Schematron (Business Rule)

EB-EVI

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

2. EB-EVI-S

1.0.3

1.1.0

Git

EB

Schematron (Business Rule)

EB-EVI

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

3. EB-REQ-C

1.0.0

1.1.0

Git

EB

Schematron (Business Rule)

EB-REQ

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

4. EB-REQ-S

1.0.3

1.1.0

Git

EB

Schematron (Business Rule)

EB-REQ

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

5. EB-ERR

1.0.0

1.1.0

Git

EB

Schematron (Business Rule)

EB-ERR

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

6. EB-SUB-C

1.0.0

1.1.0

Git

EB

Schematron (Business Rule)

EB-SUB

Mandatory

1.1.0

September 2024

3.2.6

Business Rules (EB)

7. EB-SUB-S

1.0.3

1.1.0

Git

EB

Schematron (Business Rule)

EB-SUB

Mandatory

1.1.0

September 2024

3.3.1

Semantic Repository (SR)

-

1.2.0

1.2.0

Wiki

SR

Specification

SR

Mandatory

1.1.0

September 2024

3.4

Common Services Distribution

-

1.0.0

1.0.1

Wiki

CS

Specification

CS-Distribution

Mandatory

1.1.0

September 2024

3.5

Code Lists

LanguageCode

2020-04-17

1.0.0

Git

Codelist

External Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

EAS

2023-11-15

1.0.0

Git

Codelist

External Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

Nuts

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

CountryIdentificationCode

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

EEA_Country

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

Procedures

2024-02

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

AgentClassification

2024-02

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

OOTSMediaTypes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

LoA

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

IdentifierSchemes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

JurisdictionLevel

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

DSDErrorCodes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

ErrorSeverity

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

EDMErrorCodes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

EBErrorCodes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

LCMErrorResponseCodes

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

LAU

2023-11

1.0.0

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

SRSearchErrorCodes

1.0.0

1.0.1

Git

Codelist

Internal Codelist

-

Mandatory

1.1.0

September 2024

3.5

Code Lists

UIDSuppressionCountry

-

1.0.0

Git

Codelist

Internal Codelist

-

Optional

1.1.0

September 2024

3.6

Common Services API Specification

2. Query Interface Specification

1.0.0

1.1.0

Wiki (Subsec.)

CS

Specification

CS-API

Mandatory

1.1.0

September 2024

3.6

Common Services API Specification

3. The Lifecycle Management Specification

1.0.1

1.1.0

Wiki (Subsec.)

CS

Specification

CS-LCM

Mandatory

1.1.0

September 2024

3.6

Common Services API Specification

3.6 eDelivery Configuration (LCM)

1.0.0

1.0.0

Wiki (Subsec.)

CS

Specification

CS-eDelivery

Mandatory

1.1.0

September 2024

3.6

.. / 3.7. Business Rules of the Regrep LCM

1. LCM-ERR

1.0.1

1.1.0

Git

CS

Schematron (Business Rule)

LCM-ERR

Mandatory

1.1.0

September 2024

3.6

.. / 3.7. Business Rules of the Regrep LCM

2. LCM-SUC

1.0.0

1.1.0

Git

CS

Schematron (Business Rule)

LCM-SUC

Mandatory

1.1.0

September 2024

3.6

.. / 3.7. Business Rules of the Regrep LCM

3. LCM-SUB-S

1.0.1

1.1.0

Git

CS

Schematron (Business Rule)

LCM-SUB

Mandatory

1.1.0

September 2024

3.7

Common Services Network and Transport Security

-

1.0.0

1.0.0

Wiki

CS

Specification

CS-Security

Mandatory

1.1.0

September 2024

3.8

Common Services Logging

-

1.0.0

1.0.0

Wiki

CS

Specification

CS-Logging

Mandatory

1.1.0

September 2024

4.1 - 4.4

Evidence Exchange Data Model

-

1.0.0

1.1.0

Wiki

EDM

Specification

EDM

Mandatory

1.1.0

September 2024

4.5.1

Evidence Request Syntax Mapping

-

1.0.0

1.1.0

Wiki

EDM

Specification

EDM-REQ

Mandatory

1.1.0

September 2024

4.5.2

Evidence Response Syntax Mapping

-

1.0.0

1.1.0

Wiki

EDM

Specification

EDM-RESP

Mandatory

1.1.0

September 2024

4.5.3

Evidence Error Response Syntax Mapping

-

1.0.0

1.1.0

Wiki

EDM

Specification

EDM-ERR

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

1. EDM-REQ-C

1.0.2

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-REQ

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

2. EDM-REQ-S

1.0.2

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-REQ

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

3. EDM-RESP-C

1.0.1

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-RESP

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

4. EDM-RESP-S

1.0.3

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-RESP

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

5. EDM-ERR-C

1.0.2

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-ERR

Mandatory

1.1.0

September 2024

4.6

Business Rules (EDM)

6. EDM-ERR-S

1.0.2

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-ERR

Mandatory

1.1.0

September 2024

4.7

eDelivery Configuration (EDM)

-

1.0.1

1.1.0

Wiki

EDM

Specification

EDM-eDelivery

Mandatory

1.1.0

September 2024

4.7.1

ebMS Message Header Implementation Guide

-

1.0.2

1.1.0

Wiki

EDM

Specification

EDM-ebMS

Mandatory

1.1.0

September 2024

4.7.2

ebMS Message Header Business Rules

1. EDM-ebMS

1.0.4

1.1.0

Git

EDM

Schematron (Business Rule)

EDM-ebMS

Mandatory

1.1.0

September 2024

4.8

Evidence Exchange Logging

-

1.0.0

1.0.0

Wiki

EDM

Specification

EDM-Logging

Mandatory

1.1.0

September 2024

4.9

Evidence Preview

-

1.0.1

1.0.2

Wiki

EDM

Specification

EDM-Preview

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

ebms3

ebms-header-3_0-200704.xsd

3.0

3.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

rerep4

lcm.xsd

4.0

4.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

rerep4

query.xsd

4.0

4.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

rerep4

rim.xsd

4.0

4.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

rerep4

rs.xsd

4.0

4.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

rerep4

spi.xsd

4.0

4.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

s12

s12.xsd

1.2

1.2

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

sdg

oots_driver_v1.1.0.xsd

1.0.0

1.1.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

sdg

oots_driver_v1.1.0_local_imports.xsd

1.0.0

1.1.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

sdg

PowerOfRepresentationScopeType.xsd

1.1

1.1

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

sdg

SDG-GenericMetadataProfile-v1.1.0.xsd

1.0.0

1.1.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

xml

ws-addr.xsd

1.2

1.2

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

xml

xlink.xsd

1.1

1.1

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

xml

xml.xsd

1.0

1.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\XSD

xsd

XMLSchema.xsd

1.0

1.0

Git

XSD

XML Schema Definition

-

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

EB-REQ/EB-EVI

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EB-EVI/DSD-RESP

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EB-EVI/DSD-ERR

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.2

1.0.3

Git

Schematron (Business Rule)

EB-EVI/EDM-REQ

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

DSD-ERR/DSD-RESP

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

DSD-RESP/ebMS_REQ

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.2

1.0.3

Git

Schematron (Business Rule)

DSD-RESP/EDM-REQ

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.3

1.0.4

Git

EDM

Schematron (Business Rule)

EDM-REQ/EDM-RESP

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-REQ/EDM-ERR

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-ERR/EDM-REQ2

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.3

1.0.4

Git

Schematron (Business Rule)

EDM-REQ

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-ebMS/EDM-REQ

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.4

1.0.5

Git

Schematron (Business Rule)

EDM-ebMS/EDM-RESP

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-ebMS/EDM-ERR

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-ebMS

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Git

Schematron (Business Rule)

EDM-ebMS

Mandatory

1.1.0

September 2024

OOTS-EDM\crossvalidation

Business Rules (Cross-Message Validation)

1.0.1

1.0.2

Schematron (Business Rule)

EDM-ebMS

Mandatory

1.1.0

September 2024