Interoperability model for the Public Administration

A service therefore consists of an activity, or a series of activities, of a more or less intangible nature, which take place in an exchange between a supplier and a customer, in which the object of the transaction is an intangible asset.

Data sharing, Inter public administration notification, inter public administration composition

So each application server offers service interfaces, however it is still significant to distinguish whether the service interface is offered to interoperate within the domain..., towards other administrations or other subjects with whom a relationship of trust is established ... or externally....

The European Interoperability Framework (EIF) provides guidance to European public administrations on how to operate initiatives related to the issue of interoperability;

In the following chapter the non-blocking interaction profiles will be shown, in which a user submits a request and this is only taken in charge immediately, while its satisfaction can take place in a deferred manner.

This particular case, called RPC PUSH, can be used if the user in turn has the possibility to expose a service interface for receiving replies.

the provider provides a searchable address to verify the processing status of a request

the payload of a response containing more than one entry returns an object containing a list and not directly a list.

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

Although, depending on the implementations, the different REST service interfaces for accessing message brokers differ in functionality offered and ways of modeling queues, topics / subscriptions, the following behaviors of HTTP methods can be abstracted

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

the GET method is used to consume messages from queues and topics / subscriptions;

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

The PUT method is usually used to modify the properties of topic / subscriptions and queues.

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

the POST method is used for sending messages and creating topics / subscriptions and queues;

The REST service interface must use the HTTP verb most suitable for the operation as indicated in RFC 7231

the DELETE method is used for deleting topics / subscriptions and queues and in some cases to signal the fact that a message has been consumed.

Where necessary, especially for caching and concurrent access to resources, ETag (of unique version identifiers of resources) should be leveraged

HTTP status 422 if the representation of the request is syntactically correct but semantically non-processable.

According to this approach, by accessing a resource, the server's response contains hyperlinks to other actions that can be performed on the resource

For these reasons the ModI imposes the use of OpenAPI v3. An OpenAPI file allows you to describe the entire interface (available endpoints and operations on each endpoint, input and output parameters for each operation, authentication methods, contact information, license, terms of use, etc.).

snake_case camelCase

We can identify the types of properties, functional property, which expresses "what" we get from service; quality of the service, referring to characteristics (for example, delivery time) that specify benefits or perceived utility associated with the service; non-functional properties, expressing "how" the service is delivered to us.

GET /resources/123?fields=(name,partner(name))

the section focuses on the use of security protocols and techniques based on the manipulation of network messages. The section will also refer to how the security requirements can be variable depending on the application scenario and the use case.

This document describes the security profiles identified by AgID that the providers must use to satisfy the needs expressed through functional and non-functional requirements.

This profile extends IDAS01 or IDAS02 , adding to the communication between user and provider at the message level integrity of the message payload.

This profile extends IDAR01 or IDAR02 , adding to the communication between user and provider at the message level integrity of the message payload.

JOSE, JWT

The Basic Security Profile 1.1, based on the WS-Security extension, suggests the use of SAML 2.0. As mentioned, with respect to authentication and authorization technologies, there are some application domains for which OAuth2 or OpenID are more appropriate.