providing data once-only eu The Once-Only Principle Project Generic Federated OOP Architecture (1st version) Jaak Tepandi, J.P.C.(Jack) Verhoosel, Dimitrios Zeginis, Gunnar Wettergren, Jerry Dimitriou, Carmen Rotuna, Cagatay Carabat, Özlem Albayrak, Erol Yilmaz, Thomas Lampoltshammer, Ermo Täks, Andriana Prentza, Paul Brandt, Petros Kavassalis, Lefteris Leontaridis, Jan Willem Streefkerk www.toop.eu Submitted to the EC on 30/06/2017 Horizon 2020 The EU Framework Programmeprovidi for Research andng Innovation data once-only eu PROJECT ACRONYM: TOOP PROJECT FULL TITLE: The “Once-Only” Principle Project H2020 Call: H2020‐SC6‐CO‐CREATION‐2016‐2 H2020 Topic: CO‐CREATION‐05‐2016 ‐ Co‐creation between public administrations: once‐ only principle GRANT AGREEMENT n°: 737460 D2.1 Generic Federated OOP Architecture (1st version) Deliverable Id : D2.1 Deliverable Name : Generic federated OOP architecture (1st version) Version : V1.0 Status : Final Dissemination Level : Public Due date of deliverable : M6 (June 2017) Actual submission date : 30/06/2017 Work Package : WP2 Organisation name of lead partner for this Tallinn University of Technology deliverable: Jaak Tepandi Thomas J.P.C. (Jack) Verhoosel Lampoltshammer Dimitrios Zeginis Ermo Täks Gunnar Wettergren Andriana Prentza Author(s): Jerry Dimitriou Paul Brandt Carmen Rotuna Petros Kavassalis Cagatay Karabat Lefteris Leontaridis Özlem Albayrak Jan Willem Streefkerk Erol Yilmaz Partners contributing: All beneficiaries This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 737460 D2.1. Generic federated OOP architecture (1st version) 2 Abstract: This deliverable presents the first version of a generic federated OOP architecture, supporting interconnection and interoperability of national registries at providithe EU level. The architecture isng in line with existing EU frameworks (EIRA, EIF), takes into account the e-SENS European Interoperability Reference Architecture and is based on the CEF DSIs and the Building Blocks consolidated by the e-SENS project. The first version focuses on interoperability at business and information level, to be extended iteratively in the future versions. The deliverable includes, among others, the requirements, the initial building blocks, and the interface specifications of the generic federated architecture.data The overall logic of the deliverable emerges from the principle of reusing existing frameworks and building blocks provided by CEF, e-SENS, and other initiatives. As the first step, an initial inventory of existing e- Government Building Blocks is proposed. once-onlyThen the principles of selection of building blockseu for OOP applications and several types of high-level view of the architecture are provided. Finally, an analysis of selected building blocks with respect to their relevance, applicability, sustainability, need for further development, and external interfaces is presented. The next steps are to develop the architecture in more detail and to elaborate other tasks of TOOP T2.1 – development of a framework for specific OOP architectures and providing deployment profiles for building blocks. This deliverable contains original unpublished work or work to which the authors hold all rights except where clearly indicated otherwise. Acknowledgement of previously published material and of the work of others has been made through appropriate citation, quotation or both. All web-links referred to in this deliverable are valid on the submission date of the deliverable. This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 737460 D2.1. Generic federated OOP architecture (1st version) 3 Table of contents LIST OF FIGURES ................................................................providi................................ng.............................. 7 LIST OF TABLES ................................................................................................................................ 8 LIST OF ABBREVIATIONS .................................................................................................................. 9 EXECUTIVE SUMMARY ................................data.................................................................................. 10 1. INTRODUCTION ..................................................................................................................... 12 1.1. SCOPE AND OBJECTIVE OF DELIVERABLEonce-only ......................................................................................... eu 12 1.2. WP2 GENERAL OBJECTIVES AND VISION ........................................................................................ 12 1.3. METHODOLOGY OF WORK .......................................................................................................... 12 1.3.1. ASPECTS OF THE WORK METHODOLOGY ................................................................................ 12 1.3.2. ARCHITECTURE DEVELOPMENT METHODOLOGY ...................................................................... 13 1.3.3. AGILE APPROACH FOR THE ARCHITECTURE DEVELOPMENT PROJECT MANAGEMENT ..................... 14 1.4. RELATIONS TO INTERNAL TOOP ENVIRONMENT ............................................................................. 16 1.5. RELATIONS TO EXTERNAL TOOP ENVIRONMENT ............................................................................. 16 1.6. LEGAL ISSUES ............................................................................................................................ 16 1.7. STRUCTURE OF THE DOCUMENT ................................................................................................... 16 2. KEY CONCEPTS ...................................................................................................................... 17 2.1. GUIDING POLITICAL, LEGISLATIVE, AND TECHNICAL PRINCIPLES .......................................................... 17 2.2. ARCHITECTURE PRINCIPLES .......................................................................................................... 18 2.2.1. ARCHITECTURE DESCRIPTION ............................................................................................... 18 2.2.2. ARCHITECTURE VIEWPOINT .................................................................................................. 18 2.2.3. ARCHITECTURE FRAMEWORK ............................................................................................... 19 2.2.4. ARCHITECTURE DESCRIPTION LANGUAGE ............................................................................... 20 2.2.5. ARCHITECTURE APPROACHES IN TOOP DELIVERABLES ............................................................. 20 2.3. RELATIONSHIP BETWEEN THE ARCHITECTURE AND THE S/W DEVELOPMENT PROCESS ............................ 20 3. SUMMARY OF REQUIREMENTS FOR THE OOP ARCHITECTURE ............................................... 23 3.1. REQUIREMENTS RESULTING FROM THE TOOP GUIDING PRINCIPLES AND THE PROJECT ......................... 23 3.2. REQUIREMENTS RESULTING FROM ARCHITECTURE FRAMEWORK CONSIDERATIONS ............................... 23 3.3. REQUIREMENTS RESULTING FROM THE TOOP FOCUS AREA AND PILOT AREAS..................................... 24 3.4. REQUIREMENTS RESULTING FROM STANDARDS AND BEST PRACTICES ................................................. 25 4. EXISTING E-GOVERNMENT BUILDING BLOCKS ....................................................................... 27 4.1. CEF BUILDING BLOCKS ............................................................................................................... 27 4.1.1. EDELIVERY ........................................................................................................................ 27 4.1.2. EID BUILDING BLOCK .......................................................................................................... 30 4.1.3. ESIGNATURE BUILDING BLOCK.............................................................................................. 31 4.1.4. EINVOICING BUILDING BLOCK ............................................................................................... 31 4.1.5. ETRANSLATION .................................................................................................................. 31 4.1.6. E-HI (HUMAN INTERFACE) ................................................................................................... 33 This project has received funding from the European Union’s Horizon 2020 research and innovation programme under grant agreement No 737460 D2.1. Generic federated OOP architecture (1st version) 4 4.2. BUILDING BLOCKS CONSOLIDATED BY THE E-SENS PROJECT .............................................................. 34 4.2.1. EDELIVERY SAT ................................................................................................................. 34 4.2.2. EID SAT ................................................................providi................................ng........................... 37 4.2.3. ESIGNATURE SAT ............................................................................................................... 39 4.2.4. NON-REPUDIATION AND TRACEABILITY .................................................................................. 40 4.2.5. TRUST ESTABLISHMENT ................................data....................................................................... 40 4.2.6. EDOCUMENT ....................................................................................................................