What is Interoperability?

Within the European Interoperability Framework [EIF-V1], Interoperability was defined as “The ability of information and communication technology (ICT) systems and of the business processes they support to exchange data and to enable the sharing of information and knowledge.” In the Draft document as basis for the EIF v2 [EIF-DraftBasisV2] this definition has been reworked into a more comprehensive one "the ability of disparate and diverse organizations to interact towards mutually beneficial and agreed common objectives, involving the sharing of information and knowledge between the organisations via the business processes they support, by means of the exchange of data between their respective information and communication technology (ICT) systems."

For the “United Nations e-Government Survey 2008 From e-Government to Connected Governance” [UN-Survey] means “the ability of government organizations to share and integrate information by using common standards.”

The delivery of eGoverment services typically involves the interaction between actors, citizens, business and administrations, in a scenario of large diversity, not only in terms of technology, but also in terms of how the relationships and the processes are organized and of how the necessary data and information are structured and handled. The following types of interaction cover most of eGovernment services:

Interoperability is a relevant requirement which has been scaling steps in the political agenda in recent years. In the European Union for instance several policy documents and acts refer to interoperability, like the COM(2006) 45 final.

The achievement of interoperability requires a global approach which should take into account issues like types of interactions, dimensions of interoperability (organizational, semantic, technical, in time), the interoperability chain, standards, common infrastructures and services and conditions for share, re-use and collaborate.

The dimensions of interoperability:

The interoperability chain. Interoperability behaves like a chain when systems and services are deployed across boudaries of entities or governments; there is a succession of interconnected elements, in a rather dynamic way, through interfaces and with projection to the interoperability dimensions. Interoperability may break at the weakest point elements individually adequate are deficiently joined. The delivery of complex services requires interoperability between all the links of the chain, end to end, including back-office and front-office environments. The interoperability chain might include basic links like infrastructures and associated services; data models and data integration; systems and services integration; and secure integrated multi-channel access with accessibility; together with some transversal aspects.

Standards are applicable in the dimensions of interoperability, they are used in common infrastructures and services, and they are used in certain links of the interoperability chain. The use of open standards allows that the actors providing and receiving eGovernment services may take part using their preferred technological choices. Governments are taking into account open standards in their policies and interoperability frameworks and in some cases, like the Netherlands for instance, are developing coherent strategies towards openness [NL-OSOSS].

Common infrastructures and services propagate interoperability producing economies of scale and using synergies that stem from cooperative work in similar areas of action and respecting the subsidiarity of the participating entities in the provision of complex services. They offer integrating solutions that ensure interoperability in the dominion of their implementation with the rest of users, putting the focus on the corresponding interfaces. They facilitate the development of new services, as well as the interoperability of the existing ones.

Share, re-use and collaborate. The voice 'sharing' is present in the interoperability definition mentioned above; together with re-use, both of them are important for interoperability. The terms 'share' and 're-use' are connected, for instance, with the corresponding policy in the European Union shaped in the Action plan on electronic administration i2010 [i2010]. The openness approach benefits interoperability and it is a condition that favours sharing and reusing. Putting in practice the sharing approach may require the support of platforms like - Open Source Observatory and Repository [OSOR] and the application by governments of adequate licensing conditions, as in the case of the EUPL [EUPL].

What Public Policy Outcomes are related to interoperability.

Interoperability policies developed by governments generally address the following goals:

This outcomes drive to benefits which are described in the following paragraphs.

What Are the Main Benefits of Interoperability?

Interoperability offers important benefits to governments, to business and industry and to citizens. Within [EIF-DraftBasisV2] there is a whole section on this question which is helpful to identify in summary the main benefits:

How Can Interoperability Be Achieved?

Interoperability is by its own nature a joint effort. Sharing information requires sharing a set of common principles among all participants. The best way to achieve interoperability is through standardization.

Open Standards

It is of paramount importance to use open standards where available – for instance, use XML and related standards (xml schema, etc.) when / if possible, as opposed to proprietary formats. According to the Berkman Center for Internet and Society at the Harvard Law School [Roadmap Open ICT], a standard is considered to be open if:

The workload to select standards for eGovernment services may be considerable and in fact all the governments that maintain lists of standards for their interoperability frameworks are carrying out similar tasks. That's why the IDABC Programme of the European Union started on the proposal of Denmark the work to develop a Common Assessment Method of Standards and Specifications, CAMSS [CAMSS]. This method has been elaborated on the basis of commonalities of existing practices in some European countries in relation to the assessment of standards for interoperability frameworks with the aim to facilitate this task and share the results. CAMSS identifies several criteria such as the adequation of the standard to the required function, its potential in terms of stability, scalability and others, the degree of openness and the market conditions.

Open Source

It is essential that open standards be compatible with a variety of licensing and development models, including open source. Whenever possible, Open Source Solutions should be evaluated and considered an option along with proprietary alternatives.

Government Interoperability Frameworks

Though it is possible to start by means of bilateral approaches, greater value usually lies in multi-lateral solutions. This principle sets the ground for the creation of a Government Interoperability Framework (GIF).

A GIF is an instrument shared by different Governmental Organizations that provides a global approach to interoperability and which enables them to interact with each other, share information and business processes and cooperate for the delivery of eGovernment services. A GIF usually deals with the following:

There a wide number of initiatives in this area:

What Are the Main Issues?

Interoperability presents a series of issues that need to be taken into account.


Standards is a rather complex issue which might require a longer discussion outside the scope of this document.

There is a wide number of standardization bodies producing plenty of standards producing plenty of standards, using this term loosely here, because we should talk about 'technical specifications'.

The definitions included in Directive 2004/18/EC may be useful:

"technical specification" means a specification in a document defining the required characteristics of a product or a service, such as quality levels, environmental performance levels, design for all requirements (including accessibility for disabled persons) and conformity assessment, performance, use of the product, safety or dimensions, including requirements relevant to the product as regards the name under which the product is sold, terminology, symbols, testing and test methods, packaging, marking and labelling, user instructions, production processes and methods and conformity assessment procedures.


standard” means “a technical specification approved by a recognized standardization body ...”

Therefore, the term 'standard' is usually applied to specifications produced by international or national legally recognized standardization bodies such as ISO, ITU, ETSI, CEN and others. These kind of specifications have a legal recognition with implications in the applicable law as it happens, for instance, in the case of the European Union with Directive 98/34/EC and Directive 2004/18/EC.

Anything else are specifications which may come from stakeholder forums or industry consortia such as W3C, OASIS, IETF, ... which are, in fact, producing a main part of specifications (or 'standards' loosely speaking) for information society in general an for eGovernment in particular. This being a reality that should be taken into account by governments.

Having said that, as [EIF-DraftBasisV2] states “Openness of standards or technical specifications is important for public administrations because of its relationship with interoperability, freedom and choice”.

In relation to this statement “W3C primarily pursues its mission through the creation of Web standards and guidelines...In order for the Web to reach its full potential, the most fundamental Web technologies must be compatible with one another and allow any hardware and software used to access the Web to work together. W3C refers to this goal as “Web interoperability.” By publishing open (non-proprietary) standards for Web languages and protocols, W3C seeks to avoid market fragmentation and thus Web fragmentation.” [W3C-Overview]

The selection of standards for eGovernment services and interoperability frameworks presents several issues which deserve to be pointed out:


Legal frameworks usually establish privacy and data protection obligations for governments and institutions that are entrusted with the administration of public services and the exchange of information about citizen's and business. The exchage of this kind of information requires conformity with the applicable legal framework and securit policies and requirements. Following [EIF-DraftBasisV2] citizens and business require a sufficient level of guarantees regarding their privacy and that their fundamental rights are preserved. “From the user perspective, functions associated with security (identification, authentic ation, authorisation, integrity, non -repudiation, confidentiality, etc.) should have a maximum level of transparency, involve a minimum of effort and provide the proper level of security.”


Security, in close relation with privacy, is also a transversal question. Being a quite difficult issue, it is important that required levels of security are in place in the different areas: data access, communications, etc. providing equivalent safeguards to non-interoperable scenarios.


The semantics of the information must be agreed beforehand, so all exchanging parties have a common understanding of the meaning of the data exchanged. At the international level, this can be a complex topic since some legal concepts may differ from one country to the other. The final goal is to be able to interpret data consistently across the different organizations and platforms involved in the data exchange.

Legal Aspects

Interoperability may require changes in current legislation, so this needs to be addressed as well.

Cultural/Political Aspects

In general and historically, public agencies have developed a culture that does not promote cross-agency sharing. In many cases, agencies are reluctant to change existing processes, open data and services to external parties and re-negotiate their way of operation with external parties, who owns and controls what, in the new environment that usually appears after the execution of an interoperability project that links together two or more agencies.



Common Assessment Method of Standards and Specifications


CEN/ISSS Draft Report of the Project Team of the CEN/ISSS eGovernment Focus Group on the eGovernment Standards Roadmap

Directive 98/34/EC

Directive 98/34/EC of the European Parliament and of the Council of 22 June 1998 laying down a procedure for the provision of information in the field of technical standards and regulations and Directive 98/48/EC of the European Parliament and of the Council of 20 July 1998 amending Directive 98/34/EC laying down a procedure for the provision of information in the field of technical standards and regulations

[Directive 2004/18/EC]

Directive 2004/18/EC of the European Parliament and of the Council of 31 March 2004 on the coordination of procedures for the award of public works contracts, public supply contracts and public service contracts


European Interoperability Framework (EIF)


Draft Document as basis for EIF v2


The European Union Public Licence (EUPL)


Action plan on electronic administration i2010


Australian Government Technical Interoperability Framework


Belgian Government Interoperability Framework


OIO Architecture Framework


Estonian IT Interoperability Framework


Standards and Architectures for eGovernment Applications (English)


Towards a Dutch Interoperability Framework – Recommendations to the Forum Standaardisatie


NZ eGovernment Interoperability Framework


eGIF- e-Government Interoperability Framework


The Netherlands in Open Connection – An action plan for the use of Open Standards and Open Source Software

[OSOR] - Open Source Observatory and Repository

[Roadmap Open ICT]

Roadmap of Open ICT ecosystems


SEMIC.EU - The Semantic Interoperability Centre Europe


United Nations e-Government Survey 2008 From e-Government to Connected Governance


W3C Overview