Working group meeting #4 - APIs4IPS (API strategy essentials and REST-based API extensions and Blockchain)
11 March 2021 / 10:00 - 13:00
Online meeting via Webex
Event summary
The CEF eDelivery team is organising the second subgroup meeting focusing on the work on the future of eDelivery. This work will include a focus on REST-based API extensions to eDelivery and possible use of Blockchain technology.
If you have any additional comments or questions on the workshop, or generally concerning CEF eDelivery, the Service Offering or grant funding, please reach out to us via Service Desk.
You will need to be logged in using an EU Login account to submit a request. Don't have an EU Login account yet? Sign up here.
Participants
European Commission
Member States' representatives
Maya Madrid (DG CNECT H4) – CEF eDelivery Business Owner
Bogdan Dumitriu introduced the work that was done on the REST API profile and gave the floor to Jerry Dimitriou who presented the REST API profile from a technical perspective (cf. slides).
Bogdan Dumitriu provided an update on the pilot (objectives, architecture overview and functionality) (cf. slides). Bogdan shared the timeline
Roberto Polli asked whether Jades define a way to provide "Signature" in multipart
Bogdan Dumitriu confirmed
Q&A
15 mins
Philip Helger asked whether the long term goal of the EC was to provide a long term maintenance for the specifications and thus establishing the EC as a specification organisation, or to hand over the maintenance to other organisation.
Bogdan Dumitriu precised that other stakeholders are involved to understand how this will be handled in the future.
Maya Madrid agreed
Christophe Gaie asked whether the EC will share the products with the governments to test them.
Bogdan Dumitriu precised that it is publicly funded work so the part 1 was already shared and the rest will be fully available by June/July.
Break (15 mins)
Pilot Domibus integration with CEF EBSI (blockchain):
Monica Posadapresented an update on the JRC’s work on API guidelines for government (cf. slides). Monicaalso presented the indicative timeline.
Mark Boyd then provided information on best practices in API lifecycle management (cf.slides). Mark precised that the key lifecycle issues regarding APIs are security and traceability.
Mark then started the interactive session on security and privacy asking first what were the main security threats faced by the countries.
RobertoPolli explained that in Italy security threats are mainly linked to information accidentally exposed by APIs which do not implement double checks.
Monica Posada asked Roberto whether it would be possible for his organisation to set up a security audit process.
Roberto replied that the problem is not only to establish processes but having thousands of agencies is complex for them to implement. Some agencies have the advantage of having great structures and lot of money to implement the security assessment, which is not the case for smaller agencies.
Mark Boyd then asked whether countries put in place traceability measures.
Manne Andersson answered that at the Swedish eHealth Agency, they are currently looking at profile APIs and talking about traceability over many APIs over many organisations because they see the need for that, but never deep into this. Manne added that this regards public sector but also private sector.
Maya Madrid finally thanked all participants and closed the meeting.
About the ISA² action on Innovative Public Services:
In the ISA² Work Programme for 2020, the action on Innovative Public Services has, among others, the objective of developing relevant legal, organisational and technical artefacts trialled through an extension and combination of the CEF eDelivery building block with blockchain based transactions’ log and a REST-based profile (a.k.a. APIs approach), that support new patterns of data access by request and data sharing.
The work related to the REST-based profile will take as input the JRC study on APIs4DGov that analysed the API technological landscape and its standards and technical specifications for general purpose use. This aims to support the definition of stable APIs for digital government services, avoiding the need to develop ad hoc solutions and helping stakeholders in the identification and selection of such solutions.
The scope of the ISA² action will be to develop the following:
A set of guidelines and specifications for establishing interoperable REST-based APIs for service invocation and publication of both open and protected data. Sample library implementation for API’s as well as software supporting central/core services such as service catalogues and service discovery could be also in scope.
Extension of eDelivery with other building blocks and innovative technical approaches such as blockchain and APIs. Should the pilots be successful, the CEF eDelivery building block will be enriched with a REST-based profile and a blockchain-based log of transactions. Every element will be modular so that it can be used in combination with the existing AS4-profile (of eDelivery) or on its own.
About CEF eDelivery:
The CEF eDelivery building block helps public administrations and businesses (and indirectly citizens) to participate in eDelivery Messaging Infrastructures which facilitate organisation-to-organisation messaging by enabling their systems to interact with each other in a secure, reliable and trusted way. The Connecting Europe Facility (CEF) Digital Programme, is currently promoting the adoption of common standards in the eDelivery Messaging Infrastructures in different policy domains (Business Registers, eJustice, eProcurement, etc.).