Europe: interoperability frameworks, open standards and national policies
European government software policy combines several subjects: purchasing rules, copyright, public licensing, common standards, and the ability of administrations to exchange information. The Center for Strategic and International Studies policy survey records national and regional actions with different types and outcomes. Those distinctions matter alongside European frameworks: a rule about document exchange is not necessarily a preference for a software license, and an individual city's migration is not a policy for the whole continent.
From connections between systems to public services
The European Interoperability Framework concerns communication among administrations, businesses, and citizens, including exchanges across borders. Wikipedia's account of the framework dates its initial version to November 2004 and the European Commission's adoption of its next version to 16 December 2010. The subject extended beyond software compatibility: differences in administrative structure, the services governments supplied, and the way citizens interacted with the state also presented obstacles to common service delivery.
The official Interoperable Europe explanation presents guidance for designing interoperable digital public services. Its headings cover legal, organizational, semantic, and technical interoperability, as well as governance and a model for integrated services. The underlying principles include openness, transparency, reuse, technological neutrality, data portability, accessibility, and preservation of information. Together, those headings describe an administrative problem as well as a technical one: exchanging data depends on what information means and on how the participating bodies work.
Procurement, copyright and public licensing
Wikipedia's overview of EU public procurement explains how directives coordinated procedures for public works, supplies, and services. Their principles include transparency, equal treatment, nondiscrimination, mutual recognition, and proportionality. This framework concerns the procedure for awarding a contract and the treatment of suppliers. It provides context for national software measures without making every open-source initiative a separate procurement directive or settling an individual award decision.
The Computer Programs Directive overview in Wikipedia describes copyright protection of programs as literary works and limitations on the rights of a copyright owner. It includes decompilation when necessary for interoperability, subject to limits on using the results. By contrast, Wikipedia's European Union Public Licence article describes a free-software license written and approved by the European Commission for distributing software. Copyright rules and a public license therefore address related but different questions: what rights exist and what permissions the rights holder offers.
Measures within national and regional institutions
| Government | Branch or agency | Action | Date | Status |
|---|---|---|---|---|
| UK | OGC/ e-Government Unit | Advisory | Oct. 2004 | Approved |
| Denmark | Executive | Advisory | June 2003 | Approved |
| Belgium | Legislative | Mandatory | Apr. 2003 | Failed |
| Portugal | Council of Ministers | Advisory | Jan. 2002 | Approved |
| Portugal | Parliament | Mandatory | Oct. 2003 | Failed |
| Spain, Andalucia | Legislative | Preference | Mar. 2003 | Approved |
| Spain, Extremadura | Legislative | Preference | Nov. 2002 / May 2004 | Approved |
The descriptions show why the status column matters. Denmark's advisory strategy expressed no open-source preference. In Belgium, the Brussels community measure encountered a ruling that only the federal parliament could propose such a mandate. Portugal's nonbinding resolution and its rejected mandatory bill were separate actions. In Spain, Andalucia's measure required educational computers and public Internet sites to be compatible with free software, while Extremadura's entry concerned a migration decision. Each description comes from the CSIS tables; compatibility, advice, and mandatory adoption are different requirements.
The United Kingdom: value, reuse and standards
In its March 2009 entry, the CSIS survey recorded a UK policy of considering open-source and proprietary solutions fairly, assessing lifetime ownership costs, and including exit and transition costs. It also recorded a preference for open source when there was no significant overall cost difference. The policy combined capability and value requirements with that conditional preference; describing it only as neutrality or only as mandatory open source would lose those qualifications.
GOV.UK's action-plan publication identifies an open-source strategy for government published on 27 January 2010. Its open standards principles publication says the principles followed consultation between February and June 2012 and concerned software interoperability, data, and document formats. The latter publication records later document changes while stating that the policy remained the same. These publications place procurement choices beside reuse and standards, rather than treating them as one licensing decision.
Munich’s decisions over time
Wikipedia's LiMux account describes Munich's Linux-based desktop project as launched in 2004. It records the city council's November 2017 decision to reverse the migration and return to proprietary desktop software by 2020, followed by a renewed emphasis on free software in May 2020. Those changes are part of the city's recorded policy sequence. They do not establish a general result for every government, and the disputed explanations for the reversal are separate from the council decision itself.
The Spanish-language overview explains Spain's interoperability framework and regional distributions. The computer-implemented inventions directive page follows the separate European patent proposal and its rejection. The interoperability and open standards page connects the meanings of open standards with these institutional examples.