Update regarding Once-Only Technical System Technical Design Documents - Q1 2023 release
24 March 2023 | 5 minutes read
On 17 March 2023, the Once-Only Technical System (OOTS) Specifications – Technical Design Documents (TDD) sub-group to the Single Digital Gateway Coordination Group approved the working draft of the OOTS Technical Design Documents for release as the Q1 2023 release.
On 24 March 2023, the Commission published this minor incremental release on the Once-Only Hub, a few weeks ahead of the usual release date to provide Member States implementation teams more time to review and take advantage of this update for the upcoming OOTS Projectathon events.
As the project is getting closer to the go-live date of December 2023, the TDD subgroup has focused on incremental, fine-grained improvements, corrections, clarifications, and additional explanations rather than major new features. Most changes between the Q4 2022 and the Q1 2023 release do not affect evidence exchange processing and related structures. There is likely to be little impact on existing developed components as the first OOTS Projectathon focuses mainly on eDelivery evidence exchange flows and the use of pre-defined data sets for eID, common service queries, and evidence exchange.
The Once-Only Technical System Technical Design Documents are a combination of content on the Once-Only Hub and additional artifacts available on code.europa.eu. The editors have made updates throughout the Technical Design Documents, focusing on the user identification and authentication, common services, evidence exchange chapters, and on the related online repositories.
This release updates all XML samples and snippets. It also adds Schematron files for validation according to the business rules that were published in the previous release, and sample flow descriptions. A detailed change log summarises the changes compared to the previous release.
Furthermore, this release aligns to and is consistent with the current release of the Once-Only Technical System testing service. Implementers can use the testing service to validate and, if needed, improve their implementations of the Once-Only Technical System.
Consult the Once-Only Technical System Technical Design Documents.