Change log - Version October 2022

The previous (Q2) release of the OOTS Technical Design Documents was published in June 2022. That release was not a public release.  For those who had access to that previous release, the following table lists changes made to the technical design documents after the Q2 2022 release. The changes were based on:

  • Publication of the Implementing Act as C/2022/5628 final. 
  • Feedback on the previous release provided by some Member States.
  • Feedback and other requests from the teams developing the OOTS test service and implementing the Common Services.
  • Addition of additional implementation guidelines.
  • Many other improvements from closer scrutiny of the existing text by the editors.


Chapter / Location 

Area / kind of change

Comments

Location (Chapter, Section)

General Editorial

Changed the bibliographic entry of the Implementing Regulation now that it is published

1

EditorialAdded EUPL license for content of all chapters.1, 2, 3, 4, 5, 6

EditorialRegRep identifiers of type URN UUID start with the prefix "urn:uuid"3, 4, GIT
High Level ArchitectureEditorialUpdated the links to GIT repositories for UML and Archimate to reflect the move to https://code.europa.eu/oots/1

ContextExplained the link of these documents to the sub-groups. 1.1.2
User identification and authenticationEditorial

Fix heading numbering in section on identity and record matching


2.1

ClarificationClarification on the processing of the unique identifier when re-authentication is performed by the Data Service.2.1.3.2
Common ServicesDSD query functionalityProvided detailed implementation guidelines for DSD 3.1.4.3.2, 3.1.4.4.2 

DSD life cycle managementCorrected LCM model, some missing attributes3.1.5

DSD data modelProvided detailed business rules and extended examples3.1

EB query functionalityProvided detailed implementation guidelines for EB3.2.4.2.2

EB life cycle managementRenamed the "Procedure" slot in the EB LCM section to "ReferenceFramework" for consistency 3.2.5.4

EB data modelDocumented language attritute and updated examples (snippets) using it3.2


Provided detailed business rules and extended examples3.2

Use of ebRSClarified that implementations of the REST query interfaces of DSD and EB are not required to support the ebRS canonical query parameters.3.1.4, 3.2.4

EditorialAdded reference sections to DSD and EB section3.1.6, 3.2.6

API The section on the LCM API incorrectly referred to the "lid" attribute. This should be the "id" attibute.3.6

API EditorialCorrected spelling of SubmitObjects protocol3.6

SecurityProvided additional detail on use of TLS3.1.4.7, 3.2.4.6

SecurityExplained ETSI reference for JAdES.3.1.6, 3.2.6
Evidence ExchangeEditorialUpdated the links to GIT repositories to reflect the move to https://code.europa.eu/oots/4.5.4


Updated/renumbered business rule identifiers4.5.*


Corrected spelling of RegRep requestId attribute

4.5.2

4.5.3


Request modelDocumented Member State business requirement to express a desire of the requester to limit responses to a particular language and how the use of the (existing)  "xml:lang" attribute of QueryRequest enables this.

4.3

4.5.1



Documented schemeID attributes4.5.1

Response modelDocumented slots , EvidenceProvider, EvidenceRequester, EvidenceMetadata4.5.2


Party identifier types to use EAS code list (likely to need further discussion) 4.5.2


Documented schemeID attributes4.5.2

Error response modelCorrected cardinality of relation of ErrorProvider to Agent is 1:1 instead of 1:n4.5.3


Improved documentation of severity attribute4.5.3


Documented schemeID attributes4/5/3

eDeliveryDocument that OOTS uses a trust model based on Mutual Exchange.4.7
OOTS Guidance and UX RecommendationsOOTS Guidance Including an updated version of OOTS Guidance6.1

UX RecommandationsIncluding an updated version of UX Recommandations6.2
Related ArtifactsEditorialThe GIT repositories for "hla" and "tdd_chapters" will be accessed from https://code.europa.eu/oots/tdd/GIT

SchemasXSD now has some additional global elements for the LCM interfaceGIT

SchemasSchematron definitions were created or expanded to better support validation  GIT

FunctionalityBusiness rules in spreadsheet format updated (will be reflected in Schematron rules and in specification sections)GIT

SamplesXML examples were created or improved GIT
  • No labels