Working group meeting #4 - APIs4IPS (API strategy essentials and REST-based API extensions and Blockchain)
28 June 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 Dumitriuintroduced the work that was done on the REST API profile since the previous meeting and gave the floor toJerry Dimitriouwho presented the new sections of the REST API profile (the Editorial and Structural Changes, Signature Support, Common Semantics, Multipart, API endpoint mapping with MEP, User Message Definition, and Signal Message Definition) from a technical perspective (cf. slides).
Roberto Polli asked whether the profile also has content-type. Bogdan confirmed.
During the roundtable, Roberto explained that about the general layout of the document, he think that there is a lot to explain in regards of how HTTP works. Roberto suggested that DIGIT do some work to separate the explanation about how HTTP and REST works by design, and which are the actual requirements for the implementation. Roberto explained that he found it really hard to identify which were the normative part and which were the explanations related to the JAVA technology. Roberto also suggested to do additional work on the security side (regarding HTTP routine).
To reply to Roberto's comments, Bogdan explained that we also tried to have in mind the target audience. Bogdan explained that it might be useful for people that are not experts in reading standards (developers, etc.), to repeat a bit things and point out the most important rules. Bogdan added that a profile was done (which status quote we recommend to be used or shouldn't be used). On this points, Jerry confirmed and asked Roberto if we should remove and just provide references or being less strict when providing things that come from other standards.
Roberto suggested tp split the document with an introductory part (that can be descriptive) and having the normative part more short.
Sven Rasmussen pointed out that the document provides relevant information to guidelines and specifications. Regarding Roberto's remark on normative part, Sven explained that they tend to think that this profile is a little too descriptive and they would have prefer to be more normative in some areas. Sven added that it's a good specification but more work should be done on it (it's a bit unclear how work such as the open data directive implementation on APIs could benefit from this). Sven explained that a number of choices should be made to make it really helpful for cross-border interoperability.
Bogdan explained that Open data is a sample topic from REST APIs and that the team concentrate mainly on the REST API part but clearly they could be work done on the open data area that can somehow be made coherent with the specifications provided.
Bogdan presented the timeline.
Roberto explained that Italy is looking for a way to safely exchange with clients credentials without using passwords.
To answer one question raised by Roberto, Vlad Veduta explained that this would work with even asymmetric key for identifying and authorising the client application (passwords were only used because it's the simplest to implement)
Vlad suggested to set up a call to discuss this topic further with Roberto.
Monica Posadapresented an update on the JRC’s work on API guidelines for government Monicaalso presented the indicative timeline. and the accomplishments of 2021. (cf. slides).
Lorenzino Vaccari presented the technical essentials (Security, Privacy, and Traceability) and the APIs privacy and traceability.
Monica then presented the Legal and organisational essentials (API Legal and organisational considerations, legal framework, and API terms of service) (cf. slides).
Maya and Bogdan finally thanked all participants and closed this last working group 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.).