How good/bad is the final version (as in revision) of EIFv2? Well, it depends on who's asked. Glyn Moody looked at the difference between the different versions, which the FSFE also highlighted in its Web site. They stood up against Microsoft EIF lobbyists. Microsoft Florian, BSA, and ACT, for example, were promoting RAND using the exact same lies about Free software. Moody, who was actively rebutting these people, says that "the lobbyists won, free software loses badly [in] #eif #eu" and he writes an article titled "the Great Defeat":
Long-suffering readers of this blog will know that the European Interoperability Framework has occupied me for some time - I wrote about the first version back in 2008, and have been following the twists and turns of the revision process since.
These included the infamous leaked version that redefined “closed” as “nearly open”. Now we finally have the final version of EIF v2 - and it's not a pretty sight.
[...]
This issue of whether FRAND or royalty/restriction-free should be adopted for open standards is one that I've discussed much in recent columns, pointing out that FRAND is not generally compatible with free software implementations. It might seem that the European Commission has come up with a nicely-balanced compromise by specifying that both FRAND and royalty-free are acceptable. But if you think about it, “FRAND or royalty-free” is identical to FRAND, because FRAND includes royalty-free as a stricter subset. The European Commission has simply mentioned “royalty-free” as a sop to those who called for it.
But wait, you might say, doesn't it specify that even FRAND terms must be “in a way that allows implementation in both proprietary and open source software”? It certainly does, but that just means that it must be possible for some type of open source to implement the FRAND standard; it doesn't say that all kinds of open source must be able to.
So, in practice, this means that FRAND standards that shut out GPLv2 software, for example, are perfectly acceptable provided other open source licences - of which there are many - can accommodate them. Once again, the European Commission has adopted wording that seems to address the concerns of the open source community, but which in practice gives FRAND fans exactly what the want: the ability to lock out GPLv2 code - still the bulk of the free software world - while complying with EIFv2.
Yesterday, the European Commission finally published the new version of the European Interoperability Framework [pdf]. We at FSFE have been working on this document for a long time. When it was published yesterday, we gave it a welcome despite some reservations.
Glyn Moody points out a number of weak spots in the new document. Actually, I’m concerned about many of the same points as he is. Still, I don’t agree with his judgement that EIFv2 is a “great defeat”. The document would certainly have been a lot worse without the hard work of FSFE and others. Even though it leaves some key issues open, it represents some progress.
Whether to welcome EIFv2 or not is a question of what you take as a baseline for comparison, and if you view the document isolated or in context. A lot will also depend on how the EIF is implemented.
But let’s take the issues in turn.
So what we have now is a strategy statement, without the level of detail that made EIFv1 such a useful document. But this strategy generally goes in the right direction, and it’s much more powerful than before, thanks to its official status. I’m guessing that the change we’ll see across Europe will be slow, but that it will be continuous and very broad. EIFv1 provided a rallying point for those member states and public bodies that were interested in Free Software and Open Standards. EIFv2 is a general push for everyone to use more Open Standards, even though it contains generous get-out clauses.
On the whole, we welcome EIFv2. It’s not everything we wished for, but it’s far better than we feared. We’ll watch its implementation very carefully, and will nudge it along where necessary.
The European Commission today published its long-awaited revision of the European Interoperability Framework. 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 various stages.
"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."
On Tuesday December 7, we issued a press release about a contract awarded by the European Commission, under which the EC and other European institutions will spend up to 189 million Euro on proprietary software and related services. We are of the view that in issuing this contract, the EC has once more failed to live up to its own guidelines and recommendations about the use of Free Software and Open Standards, and has missed an opportunity to open up software procurement to competition from Free Software companies.
Is the new EIF perfect? No. Due to heavy lobbying by vested proprietary technology interests, some key sections of the EIF have been made confusing (indeed, the definition of 'open standards' has been watered down from the 2004 version and no longer includes the requirement of being 'royalty-free'). The definition of “open” standards or specifications remains a matter of some contention in the IT industry. An example of a more accurate definition of open standards can be found in the recently released India Standards Policy for E-Governance, which specifies that intellectual property should be licensed royalty-free and that any required specifications should be technology-neutral.
While the new definition does not give the open source and open standards community all it would have wished for, and some will certainly criticize the result, the EU's policy should still be applauded as an overall statement in favor of openness. At its heart is a reaffirmation of openness and the recognition that open source is not only a key element of – but also a growing factor in -- Europe's IT agenda.
Red Hat and the open source and open standards community will continue to work for royalty free IPR licensing policies that level the playing field and promote consumer choice. Given this latest announcement in EU policy, the open source and open standards community will have to be vigilant to ensure that this policy is implemented in a meaningful way and achieves its true goal: interoperability, vendor choice, portability, collaborative innovation and competition in providing products and services.
Landmark publication of the European Interoperability Framework by the European Commission. Of course, this is only guidance, and the political context is very complex as evidenced by the language around “FRAND” and patents. Let’s see if they can stick to this better than they can stick to their own procurement guidelines.
[...]
As if to provide caution for those welcoming the EIF publication, FSF Europe continues its very rational and well-argued assault on the European Commission’s failure to follow its own rules.
Comments
twitter
2010-12-21 06:14:21
twitter
2010-12-19 14:53:48
The FSF has explained how "RAND" discriminates against free software, but it should be obvious that software that can not be distributed without permission is not free.
The real test of defeat will be when state agencies continue using Microsoft fromats in public documents. That will prove that this framework fails to even provide interoperability, let alone software freedom, and represents no change. Microsoft's new phoney open document formats are even worse than their older binary formats but these are what Microsoft wants allowed rather than be forced to implement real standards like ODF.
Dr. Roy Schestowitz
2010-12-19 15:20:54