The Legal view models the most salient public policy development enablers and implementation instruments that shall be considered in order to support the End to End design of interoperable digital public services.

Narrative: A [Public Policy] aims at addressing the needs of a group of stakeholders, and it associated with a [Public Policy Objective].  The policy is formulated and implemented with the help of [Legal Act] which contain [European Legal act] and [National Legal act] in the form of either [Binding Instrument] or [Non-Binding Instrument]. A key type of legislation for behavioral interoperability is the [Legislation on Data Information and Knowledge Exchange] which together with the [Legislation Catalogue] and [Legal Agreement] aggregate a [Shared Legal Framework]. [Legislation Catalogue] aggregates [Legal Act] which contain [European Legal act] and [National Legal act] and realised the [Public Policy] and [Granularity of Legal Requirements]. Also [Legislation on Data Information and Knowledge Exchange] aggregate [Legal Act]. [Legal Interoperability Agreement] are a specialisation of the [Legal Agreements] focused on formalizing governance rules enabling collaboration between digital public services. 

These different Architecture Building Blocks define the [Legal Governance content] and the [Legal Functional content] and have their interoperability aspects defined by [Interoperability Specification].

The Semantic view models the most salient Architecture Building Blocks that should be considered in order to support semantic aspects for the End to End design of interoperable Digital Public Services.

Narrative: [Data] is stored as [Representation]. [Data] can be grouped in [Data Sets], which can be documented in [Data Set Catalogues] or in [Ontology] which can be grouped in [Ontologies Catalogue] or in [Data Mappings] which can be grouped in [Data Mapping Catalogue].[Virtual Data Set] are composed with [Data Set] and [Base Registry], [Reference Data] and [ Data Policies] are specialization of [Data Set].[Metadata] is a specialization of [Data].[Forms Strictures], [Data Syntax], [Data Model], [Controlled Vocabulary] and [Hash Code] are specialization of [Metadata] . [Open Data] are specialization of [Data], and [Legal Act Representation] is specialization of Representation]. [Data] has a specific [Data Owner] that is responsible of its management, together with [Digital Public Service Delivery Consumer] and [Digital Public Service Delivery Provider Provider] and all negotiate and reach a [Semantic Agreement] and/or a [Semantic Interoperability Agreement], which is a specialisation of [Semantic Agreement].Also [Specific Agreement] is composed with [Semantic Agreement]. [Data] is subject to [Data Policy], which also influence its [Representation]. Specific cases of [Data Policy] are [Master Data Policy], [Data portability Policy], [Open Data Policy], [Privacy Policy] and [Security Policy]. [Data], [Data Policy] and [Semantic Agreement] are aggregated with [Shared Knowledge Base]

These different Architecture Building Blocks define the [Semantic Functional content] and [Semantic Governance Content], each of these Architecture Building Blocks can have any [Architecture Requirement] associated, of which [Solution Specification] is a realisation. The [Interoperability Specification], which is a specialisation of [Solution Specification], is divided in [Data Model], of which [Core Data Model] and [Data Entities] are specialisations, [Controlled Vocabulary] and [Data Syntax].

The Technical - Application Domain specific view contains the most salient application Architecture Building Blocks that need to be considered in order to support technical aspects for the End to End design of Digital Solutions. A Digital Solution can support one or more public policies.

Narrative: [Interoperable Digital Solution] is composed with [Shared Platform], where it provides access to data .The [Interoperable Digital Solution] includes [Machine to Machine Interface] with [Human Interface] which both realize [Digital Public Service Delivery] which assign [Digital Public Service] which realize [Digital Business Capability]. Also [Machine to Machine Interface] and [Human Interface] assign [Digital Solution Service] which realized by[Outsourcing Strategy Solution] and  [Digital Solution Component] which serving by [Computing Hosting Networking, and Data Hosting In fracture] and realized by  [Outsourcing Strategy Solution]. [Interoperable Digital Solution] influenced by [Technical Agreement].[Technical Agreement] is composed with [Specific Agreement] and associate with [Digital Public Service Delivery Consumer] and [Digital Public Service Delivery Provider].  
[Shared Platform] includes [Discovery Enablers] enables to register the system services in which [Web Service] which is a specialization of [API] realizes [Machine to Machine Interface] and [Human Interface].[API Catalogue Component] realizes [API Discovery and Catalogue Service] which associate with [API Catalogue] which associate with [API]. [Service Registry] is associate with [Web Service] and [Service Discovery and Registry Service] which realized by [Service Registry Component]. [Software Components Catalogue] is associate with [Software Component Discovery and Catalogue Service] which realized by [Software Component Catalogue Component]. [Orchestration Enablers] in which [Orchestration Component] realizes [Orchestration Service].[ Security Enables] in which access control is managed through the services in which Firewall Component realizes [Firewall Service] and [Audit Component] realizes [Audit Service]. [Test Enablers] in which [Conformance Testing Component] accesses [Conformance Test Scenario] and realizes [Conformance Testing Service].Trust between systems is established with Identity management is realised with [Trust Enablers] in which [Trust Service Provisioning Component] realizes [e-Signature Creation Service],[e-signature Verification and Validation Service],[e-signature Preservation Service], [e-Seal Creation Service], [e-Seal Verification and Validation Service], [e-Seal Preservation Service], [e-Timestamp Creation Service], [e-Timestamp Verification and Validation Service], [Registered Electronic Delivery Service] and Integrity Verification Service]. Also [Blockchain Component] realizes [Blockchain Service].In [Identification and Access Enablers] , [Identification Component] realizes [Authentication Service],[Request Validation Service], [Registration Service] which all of three have access to [Directory].Also access here have [Access Management Service] which realized by [Access Management Component]. [ Identity Management Service], [Authorization Service] and [Accounting Service] are specializations of [Access Management Service].In [Data Exchange Enablers] exist [Data Exchange Component] which realizes [Data Exchange Service].In [Data Management Enablers] exist the [Ontological Class Mapping Catalogue Service] which realized by [Ontological Class Mapping Catalogue Component] and associate with [Ontological Class Mapping Catalogue]. Also the [Data Syntax Mapping Catalogue Service] realized by [Data Syntax Mapping Catalogue Component] and associate with [Data Syntax Mapping Catalogue]. [Metadata Management Component realizes [Metadata Management Service]. [e-Archiving Component] realizes [e-Archiving Service]. [Data Management Component] realizes [Data Management Service]. [Forms Management Component] realizes [ Content Management Service] and [Forms Management Service].[Data Publication Component] realizes [Data Publication Service]. [Data Extraction, Transformation, and Loading Component] realizes [ Data ,Extraction, Transformation, and Loading Service]. [Data Quality Component] realizes [Data Quality Service]. In [ Privacy Enablers] exist the [Privacy Component] which realizes the [Privacy Service]. In [Knowledge Discovery Enablers] the [Knowledge Discovery Component] realizes [Knowledge Discovery Component Service] which associate with [Knowledge Triple stone]. In [Analytics Enablers] [Data Analytics Component] realizes [Data Analytics Service] and [Artificial Intelligent Component] realizes [Artificial Intelligent Service] . In [Translation Enablers]enable the possibility to increase the accessibility to public service through [Machine Translation Component] realizes [Machine Translation Service]. In [Users Expierence Management Enablers] the [UX Management Component] in which exist the [MyDigitalPublicServicesDeliveryPreference Component],[MyInfo Component],[MyCalentar Component], [MySingleWindow Component] realizes the [UX Management Service] in which exist  the [MyDigitalPublicServicesDeliveryPreferencesServices],[MyInfoService],[MyCalendar Service] and [MySileWindowService] .In [Digital Workplace Enablers] exist [Digital Workplace Component] which realizes [Digital Workplace Service]. In [Financial Transaction Enablers] enables the use of  [e-Payment Component] which realizes [e-Payment Service]to digitally execute financial transactions. In [Public Procurement Enablers] exist [eProcurement Accessing Component] which realizes [eProcurement Accessing Service] . [eProcurement Contracting Component] which realizes [eProcurement Contacting Service], [eProcurement Evaluating Component] which realizes [eProcurement Evaluating Service], [eProcurement Notifying Component] which realizes [eProcurement Notifying Service], [eProcurement Quoting Service] which realizes [eProcurement Quoting Component],[eProcurement Awarding Component] which realizes [eProcurement Awarding Service], [eProcurement Discovering Component] which realizes [eProcurement Discovering Service], [eProcurement Fulfilling Component], which realizes [eProcurement Fulfilling Service], [eProcurement Ordering Component] which realizes [eProcurement Ordering Service], [eProcurement Submitting Component] which realizes [eProcurement Submitting Service]. In [eProcurement Enablers] exist [eProcurement Invoicing Component] which realized eProcurement Invoicing Service] 

The Architecture Building Blocks defined in the [Digital Solution] can have [Interoperability Specification] associated, which is a specialisation of [Solution Specification] and also realises [Interoperability Requirement].

The Technical - Infrastructure view provides an architecture content metamodel for the most salient cross-sectorial infrastructure services, along with the supporting hosting and networking facilities, which shall be considered in order to support technical aspects for the End to End design of Digital Solutions. The difference with the application part of the Technical view is that the Architecture Building Blocks in the infrastructure view are considered to be relevant for solutions in any sector of government.

Narrative: 
A [Digital  Solution Service] which give access to [Data] is realized by [Digital Solution Component] which is serving by [Computing Hosting, Networking and Data Hosting Infrastructure] and realized by [Outsourcing] which serve [Server].[Computing Hosting, Networking and Data Hosting Infrastructure] providing all the necessary networks through [Application Service], [Data Access Service], [Intranet Service],[Remote Desktop Service],[VPN Service] and [Web Service].[Application Service] is assigned by [Application Interface] and realized by [Host Application] which is a composed of [Application Interface] and with [Application Server Software Environment] its part of [Application Server]. [Application Server] is associating with [Enterprise Service Bus] which flow information  with [Computing Hosting, Networking and Data Hosting Infrastructure].Also [High Performance Server] is a specialization of [Application Server]. [Data Access Service] is assigned with [Data Interface]. Also have access to [Data Space] and realized by [Host Data Management]. [Data Virtualization] is specialization of [Host Data Management] which is serving by [Data Server Software Environment]. [Triplestone], [Data Hub], [Data Lake] and [Data Warehouse] are specialization of [Data Space].[Data Space] and  [Host Data Management] are part of [Data Server] which associate with [Back end Firewall] which associate with [Enterprise Service Bus]. [Intranet Servise] is assigned with [Intranetwork Service] which is composed by [Intranet Application] which serves by [Intranet Server Environment] and realizes [Intranet Service], which have access to [Intranet Website], which have associate with [Intranet Application Database]. Both [Intranet Website] and [Intranet Application] are part of [Intranet Server] which associate with [Enterprise Service Bus].[Remote Desktop Service] is assigned with [Remote Desktop Interface] which is composed by [Remote Desktop Server], which realize [Remote Desktop Service] and associate with [Enterprise Service Bus]. [VPN] Service] assigned with [VPN Interface] which composed by [VPN Application] which served by [VPN Server Environment] which associate with [VPN Path] which realized [VPN Service]. Also [VPN Path] associate with [VPN Client] which is part of [VPN Client Device]. [VPN Application] is part of [Virtual Private Network Server] which associate with [Extranet Firewall] which associate with [Entersprise Service Bus]. [VPN Path] is part of the [Internet] which associate with [Sensors] and [Smart Devices]. [Web Service] are assigned with [Internet Interface] which is composed by [Web Application] which realizes [Web Service] and serving by [Web Server Environment], which have access to [External Website] which have associate with [External Application Database].[ External Website],[External Web Application Database], [Web Application] and [Front-end Firewall] are part of [Web Server] which associate with [Internet].All this [Technology Infrastructure Functional Content] is influenced by [Shared Legal Framework] which influence the [Technical Agreement] which composed by [Specific Agreement] and associate with [Digital Public Service Delivery Provider] and [Digital Public Service Delivery Consumer].

The Architecture Building Blocks defined in both the [Digital Service Infrastructure] and the [Computing Hosting, Networking, and Data Hosting Infrastructure] can have any [Interoperability Specification] associated, of which the [Solution Specification] is a specialization.

The EIRA© Highlevel viewpoint models an introductory overview of the focal Architecture Building Blocks of each view. It aligns the EIRA© with the service delivery model described within the Interoperability Maturity Model  (IMM), and the New European Interoperability Framework (EIF) conceptual model for public services.
The ABBs included in the high-level viewpoint represent the points that link the EIRA©’s views enabling traceability between their different Architecture Building Blocks. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.

The EIRA© with its views provides a set of Architecture Building Blocks, important to facilitate interoperability. Each view, one for each interoperability level, is represented with the Focal Architecture Building Blocks needed to deliver an interoperable solution. These focal Architecture Building Blocks are indicated with an accented colour.
In the high-level are represented the ABBs that link the EIRA©’s views enabling navigation between the different views. As such they should be considered as critical components of any interoperable public service. They are not necessarily mandatory but should always be considered by a user of the EIRA© when executing one of its use cases.
Narrative: This viewpoint selects Architecture Building Blocks from the five different views highlighting the focal building blocks of the EIRA©: 

1.    The selected Architecture Building Block of the legal view shows the [Public Policy] realized by the [Legal Act] and [Shared Legal framework] which are the mainspring of the solution. 

2.    The selected Architecture Building Blocks of the organizational view show a [Shared Governance Framework] that aggregates the [Organizational Functional Content] which considers a [Digital Public Service] which can be an aggregation of other [Digital Public Service]. The [Digital Public Service] realises [Digital Business Capability]. A [Digital Business Capability] describes key functions supporting the [Digital Public Service]. A [Digital Public Service] accesses [Information], which can be an aggregation of other [Information]. At the same time a [Digital Public Service] is assigned by a [Digital Public Service Delivery] which is connected through a serving relation with the [Digital Public Service Delivery Model].

3.    The selected Architecture Building Blocks of the semantic view shows the [Shared Knowledge Base] and that the [Semantic Functional Content] is composed of a [Representation], stored as [Data] and the [Ontology]. 

4.    The selected Architecture Building Blocks of the technical views - application shows that a [Interoperable Digital Solution Service] is composed of a [Digital Solution Service] realized by a [Digital Solution Component] and lets consumers access it via [Machine to Machine Interface] and/or [Human Interface], which are part of a [Application Presentation and Access Enablers]. A [Digital Solution] exposes one or more [Digital Solution Service] via its [Machine to Machine Interface] and/or [Human Interface]. The [Digital Solution] uses [Digital Service Infrastructure] which uses a [Computing Hosting, Networking, and Data Hosting Infrastructure]. 

5.    The selected Architecture Building Blocks of the technical views - infrastructure considers the [Computing Hosting, Networking and Data Hosting Infrastructure].
 

The Interoperability Privacy viewpoint highlights the EIRA building blocks that are relevant when implementing the EU General Data Protection Regulation (GDPR) or assessing an existing architecture against the GDPR principles. Public administrations must indeed guarantee the citizens’ privacy, and the confidentiality, authenticity, integrity and non-repudiation of information provided by citizens and businesses.

Narrative: The selected Architecture Building Blocks from the five different views highlight the Architecture Building Blocks of the EIRA that are that are relevant with respect to GDPR:

1. The selected Architecture Building Blocks of the legal view show that privacy requirements are coming from a [Public Policy] realised by a [Binding instrument].

2. The selected Architecture Building Blocks of the organisational view show that the [Privacy Framework] applies to the [Digital Public Service] which is assigned by the [Data Owner] and provided by the [Digital Public Service Provider]. The [Digital Public Service] serves the [Digital Public Service Delivery Consumer], assigned to an [Individual] that is associated to the [Information] accessible though the [Organisation] which is a specialissed by [Public Administration] and [Business].

3. The selected Architecture Building Blocks of the semantic view show that [Data] aggregates [Data Set], [Ontology] and [Data Mapping] and that it is subject to the [Data Policy].

4. The selected Architecture Building Blocks of the Technical View shows many service involving data impacted by the privacy regulation, such as
[Data Extraction,Transformation and Loading Service], [Data Quality Service], [e-Archiving Service], [Data Publication Service], [Data Exchange Service] and [Data Management Service]; all the services reported are realised by their specific Application Component. Additionally, a [Privacy Service], realised by a [Privacy Component] implementing GDPR principle can be used to ensure compliance.

5.    The selected Architecture Building Block of the EIF Underlying Principles view show the [EIF Principle], the general intended properties used to achieve interoperability, of which the [Security and Privacy] is a specialisation. The interoperability Specifications can be used to define the interoperability aspects for any of the Architecture Building Blocks.

Interoperability Governance viewpoint ABBs

The Interoperability Privacy viewpoint highlights the EIRA building blocks that are relevant when implementing the EU General Data Protection Regulation (GDPR) or assessing an existing architecture against the GDPR principles. Public administrations must indeed guarantee the citizens’ privacy, and the confidentiality, authenticity, integrity and non-repudiation of information provided by citizens and businesses.

Narrative: The selected Architecture Building Blocks from the five different views highlight the Architecture Building Blocks of the EIRA that are that are relevant with respect to GDPR:

1. The selected Architecture Building Blocks of the legal view show that privacy requirements are coming from a [Public Policy] realised by a [Binding instrument].

2. The selected Architecture Building Blocks of the organisational view show that the [Privacy Framework] applies to the [Digital Public Service] which is assigned by the [Data Owner] and provided by the [Digital Public Service Provider]. The [Digital Public Service] serves the [Digital Public Service Delivery Consumer], assigned to an [Individual] that is associated to the [Information] accessible though the [Organisation] which is a specialissed by [Public Administration] and [Business].

3. The selected Architecture Building Blocks of the semantic view show that [Data] aggregates [Data Set], [Ontology] and [Data Mapping] and that it is subject to the [Data Policy].

4. The selected Architecture Building Blocks of the Technical View shows many service involving data impacted by the privacy regulation, such as
[Data Extraction,Transformation and Loading Service], [Data Quality Service], [e-Archiving Service], [Data Publication Service], [Data Exchange Service] and [Data Management Service]; all the services reported are realised by their specific Application Component. Additionally, a [Privacy Service], realised by a [Privacy Component] implementing GDPR principle can be used to ensure compliance.

5.    The selected Architecture Building Block of the EIF Underlying Principles view show the [EIF Principle], the general intended properties used to achieve interoperability, of which the [Security and Privacy] is a specialisation. The interoperability Specifications can be used to define the interoperability aspects for any of the Architecture Building Blocks.

The Interoperability Security and Privacy viewpoint models the most salient Architecture Building Blocks related to both security and privacy in the domain of interoperability. Citizens and businesses must be confident that when they interact with public authorities they are doing so in a secure and trustworthy environment and in full compliance with relevant regulations, e.g. the Regulation and Directive on data protection, and the Regulation on electronic identification and trust services. Public administrations must guarantee the citizens’ privacy, and the confidentiality, authenticity, integrity and non-repudiation of information provided by citizens and businesses.

Security and privacy are primary concerns in the provision of public services. When public administrations and other entities exchange official information, the information should be transferred, depending on security requirements, via a secure, harmonised, managed and controlled network. Transfer mechanisms should facilitate information exchanges between administrations, businesses and citizens. Appropriate mechanisms should allow secure exchange of electronically verified messages, records, forms and other kinds of information between the different systems; should handle specific security requirements and electronic identification and trust services such as electronic signatures/seals creation and verification; and should monitor traffic to detect intrusions, changes of data and other type of attacks.

Source: The New EIF
https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf

Narrative: This viewpoint selects Architecture Building Blocks from the five different view highlighting the Security and Privacy aspects of the EIRA©: 

1.    The selected Architecture Building Block of the legal view shows the [Public Policy], which is that mainspring of the solution

2.    The selected Architecture Building Block of the organisational view shows the [Security Framework], associated with the [Security Governance] which is that mainspring of the solution.

3.    The selected Architecture Building Block of the semantic view shows the [Security Policy], which is that mainspring of the solution.

4.    The selected Architecture Building Blocks of the technical view Application shows that a [Interoperable Digital Solution], which considers [Human Interface] and [Machine to Machine Interface] is supported by a [Shared platform] which uses [Trust Enablers], [Application Security Enablers], [Identification and Access Enablers] and [Data Exchange Enablers]. [Trust Enablers] such as [Integrity Verification Service], [e-Signature Creation Service], [e-Seal Creation Service], [e-Timestamp Creation Service], [e-Signature Verification and Validation Service], [e-Seal Verification and Validation Service], [e-Timestamp Verification and Validation Service], [e-Signature Preservation Service], [e-Seal Preservation Service] and [Registered Electronic Delivery Service], are all realised by a [Trust Service Provisioning Component]. [Identification and Access Enablers] is composed of [Authentication Service], [Request Validation Service] and [Registration Service] which are realised by [Identification Component] and that provides access to the [Directory], accessed also by the [Access Management Service], realised by the [Access Management Component]. [Application Security Enablers] is realised of [Firewall Service], composed of [Firewall Component] and [Audit Service], which is realised by an [Audit Component]. [Data Exchange Enablers] composed of Data Exchange Service] realised by the [Data Exchange Component].

5. The selected Architecture Building Blocks of the technical view Infrastructure shows an [Outsourcing Facility] and [On - Premise Facility] composed of [Back End Firewall] and [Extranet Firewall]. 

5.    The selected Architecture Building Blocks of the EIF Underlying Principles view show that [Interoperability Specifications] realises [EIF Principles], the general intended properties used to achieve interoperability, of which the [Security and Privacy] is a specialisation. The interoperability Specifications can be used to define the interoperability aspects for any of the Architecture Building Blocks.

The Key Interoperability Enablers viewpoint models the most salient key interoperability enablers(*). The viewpoint uses the ArchiMate© motivation extension to assess the structural interoperability readiness, the behavioral interoperability readiness and the governance interoperability readiness of solutions that are necessary to enable the efficient and effective delivery of public services across administrations. European public service provision often requires different public administrations to work together to meet end users’ needs and provide public services in an integrated way. When multiple organizations are involved there is a need for coordination and governance by the authorities with a mandate for planning, implementing and operating European public services. Services should be governed to ensure: collaboration, seamless execution, reuse of services and data, and development of new services and ‘building blocks'.
 
(*)DECISION (EU) 2015/2240 OF THE EUROPEAN PARLIAMENT AND OF THE COUNCIL of 25 November 2015 establishing a programme on interoperability solutions and common frameworks for European public administrations, businesses and citizens (ISA2 programme) as a means for modernising the public sector.
 
The Key Interoperability Enablers viewpoint covers all EIF interoperability aspects: legal, organisational, semantic and technical. Ensuring interoperability when preparing legal instruments, organisation business processes, data/information/knowledge exchange, services and components that support European interoperable digital public services is a continuous task, as interoperability is regularly disrupted by changes to the environment, i.e. in legislation, the needs of businesses or citizens, the organisational structure of public administrations, the business processes, and by the emergence of new technologies.
 
Source: The New EIF
https://ec.europa.eu/isa2/sites/isa/files/eif_brochure_final.pdf

Narrative: This viewpoint selects Architecture Building Blocks of the EIRA© that are key enablers for the interoperability of public services:

1.    EIF [Interoperability Principles] are used to realise the overall goal of achieving interoperability. 

2.    Particularly, the goal of [Achieve Legal Interoperability] is realised by a [Shared Legal Framework] of [re]usable legal resources that enables:
structural interoperability by legal resources supporting reusing and/or sharing legislation (i.e. [Legislation Catalogue] enabling provisioning/consuming legal texts cross public administrations and cross borders);
behavioral interoperability by legal resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Legislation on Data Information and Knowledge Exchange] enabling data/information/knowledge to be provisioned/consumed cross public administrations and cross borders); and
governance interoperability by legislation supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Legal Interoperability Agreement] on legal terms assuring juridical certainty enabling agreed legal terms/conditions for sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders). 

3.    Particularly, the goal of [Achieving Organisational Interoperability] is realised by a [Shared Governance Framework] of [re]usable organisational resources that enables: structural interoperability by organisational resources supporting reusing and/or sharing of digital public services (i.e. [Digital Public Service Catalogue] enabling provisioning/consuming public services cross public administrations and cross borders); behavioural interoperability by organisational resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Digital Public Service Delivery Model], served by [Digital Public Service Delivery] enabling data/information/knowledge to be provisioned/consumed cross public administrations and cross borders); and governance interoperability by governance resources supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Organisational Interoperability Agreement] on organisational terms/conditions enabling sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders).

4.    Particularly, the goal of [Achieving Semantic Interoperability] is realized by a [Shared Knowledge Base] of usable data, information and knowledge resources that enables: structural interoperability by semantic resources supporting reusing and/or sharing of data, information and knowledge (i.e. [Data Set Catalogue], [Ontologies Catalogue] and [Data Mapping Catalogue] enabling provisioning/consuming data, information and knowledge cross public administrations and cross borders); behavioral interoperability by semantic resources supporting exchanging capabilities of data, information or knowledge with internal/external peers (i.e. [Open Data], [Distributed Ledger] and [Virtual Data Set]; and governance interoperability by semantic resources supporting the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Semantic Interoperability Agreement] on interpretations enabling sharing, reuse and exchange of data/information/knowledge cross public administrations and cross borders).  

5.    Particularly, the goal of [Achieving Technical Interoperability] is realised by a [Shared Platform] of [re]usable ICT resources (i.e. the platform) that enables structural interoperability by ICT resources supporting reusing and/or sharing of data, and that realises [Software component Discovery and catalogue Service], [API Discovery and Catalogue Service], [Service Discovery and Registry Service]; at the same time [Shared Platform] realises also [Machine to Machine], [Human Interface], [Data Exchange Service], [UX Management Service] and [Digital Workplace Service]. [Shared Platform] governance interoperability by ICT resources supports also the collaboration with internal/external peers exchanging data, information or knowledge (i.e. [Technical Interoperability Agreements] on technical terms/conditions enabling  provisioning/consuming back-office services cross public administrations and cross borders).