Source files of,,,,, and Contribute:
You can not select more than 25 topics Topics must start with a letter or number, can include dashes ('-') and can be up to 35 characters long.

47 lines
3.6 KiB

<?xml version="1.0" encoding="UTF-8"?>
<html newsdate="2010-12-16">
<title>FSFE welcomes revised European Interoperability Framework (EIF)</title>
<h1>FSFE welcomes revised European Interoperability Framework (EIF)</h1>
<p>The European Commission today published its long-awaited revision of
the <a href="">European Interoperability Framework</a>. This document aims at promoting interoperability in the European public sector.
The document is the result of a prolonged and hard-fought process. Free Software Foundation Europe accompanied this process and offered input to the European Commission at <a href="/news/2009/news-20091127-01.html">various</a> <a href="/freesoftware/standards/bsa-letter-analysis.html">stages</a>. </p>
<p>"During the history of the EIF, we had reason to worry that Free Software would effectively be shut out of the European public sector. FSFE has worked hard to prevent this, and we have succeeded," says Karsten Gerloff, FSFE's President. "With this document, the Commission shows that it is willing to lead. We will support and accompany the EC in this effort."</p>
<p>We are happy that the effort which FSFE has invested in the EIF
revision process has brought results. The document has improved
markedly over <a href="/freesoftware/standards/eifv2.html">previous versions</a> from a Free Software point of view:</p>
<li>The document explicitely states that <a href="/freesoftware/standards/def.html">Open Standards</a> (called "open specifications") must be implementable in Free Software. </li>
<li>The document states that public administrations should prefer Open Standards.</li>
<li>The document calls on public administrations to reuse and share solutions. Free Software is by far the most practical way to achieve this.</li>
<p>Some points of the document could be improved. There is considerable wriggle room for public bodies to avoid making changes to inefficient IT systems and practices.<br/>
The document's definition of "open specifications" demands that such standards must be implementable in Free Software, but allows the patents in those standards to be licensed under so-called FRAND conditions. Such FRAND conditions normally <a href="/freesoftware/standards/bsa-letter-analysis.html#3 ">make it impossible to implement a standard in Free Software</a>. FSFE will closely accompany the European Commission in reconciling this apparent conflict.</p>
<p>"While FSFE would have wished for a more forceful push for Open Standards and Free Software, we congratulate the EC on producing a useful document out of a heated debate", says Gerloff. </p>
<p>This document ties in with the Commission's eGovernment Action Plan, announced yesterday, which makes Open Standards a political priority for European Member States and defines clear actions and deadlines. As a key action, national governments are expected to align their national interoperability frameworks with the EIF by 2013.</p>
<p>FSFE has visualised the changes among the <a href="/freesoftware/standards/eifv2.html">various versions</a> of the document. This has been a key tool for many people's work on EIFv2. The table is currently being updated to reflect the final version of the document.</p>
<description>A new revision of the European Interoperability Framework has today been published with improvements for Open Standards resulting from the work of FSFE and other organisations</description>
<tag key="front-page"/>
<tag key="eif"/>
<tag key="european-commission">European Commission</tag>
<tag key="policy"/>