This is a read-only archive. Find the latest Linux articles, documentation, and answers at the new!


Where ODF stands in the EU

By Tom Chance on October 26, 2006 (8:00:00 AM)

Share    Print    Comments   

A battle over Open Document Format (ODF) and the treatment of open standards is taking place deep in the bureaucracy of the European Commission. The information came to light during aKademy, the KDE world summit, in Dublin last month.

An entire day of aKademy was devoted to the OpenDocument movement, placing technical discussions alongside political presentations. KDE has good reason to be interested in the status of ODF in Europe, since a number of contributors and companies use KDE on the continent. Moreover, KOffice uses ODF as its default file format and is leading the way both in the implementation and development of some OpenDocument standards.

A key presentation on the ODF day came from Dr. Barbara Held, who is the Enterprise and Industry Directorate-General of the European Commission Program for Interoperable Delivery of pan-European eGovernment Services to Public Administrations, Businesses and Citizens (IDABC). Got that? Right. The IDABC basically exists to smooth over the technical problems within the European Union caused by the 25 member states exchanging data. The existence of multiple, incompatible file formats poses a formidable problem for the EU, so the IDABC was tasked with developing a strategy to overcome this.

As with anything in European politics, the IDABC's approach is multifaceted and complex. It funds and implements various networks and services, including those of common interest across the EU and those that are prioritised because of their high impact. It also makes available generic services and tools that support interoperability across the EU.

The scope of the IDABC's remit on this matter and its overall approach can be discerned from the following statement, to be found in the EU's eEurope Action Plan 2005. It commits the Commission to an "interoperability framework" that "will be based on open standards" and that will "encourage the use of open source software," which Held says is a necessity given the EU's transnational structure. That's a high-level statement of support for the free software community, and it gets better.

The IDABC drafted something called the European Interoperability Framework, which serves as a guideline to member states and EU bodies. It identifies the core requirements of administrations, which are: availability and reliability, security, accessibility, sustainability (including availability over the long term), independence from vendor lock-in, value for money (including the cost of software implementation and licensing), scalability, and re-usability. By accounting for these comprehensive requirements, the EIF was a strong statement in support of the kinds of open standards that the free software community favours. Namely, a standard should be adopted and managed by a non-profit organisation and be open to all interested parties. It should be fully published, with the specifications being made available free of charge. Any intellectual property contained within the standard, or irrevocably connected to it, should be made available on a royalty-free basis. Finally, there should be no constraints on the re-use of the standard.

Such a strong framework is the result of the factors that influenced its development. In the first place, there was a political impulse from the IDABC, and previous statements such as those in the eEurope Action Plan 2005. But there were also pressures from member states, the IDABC, and other stakeholders who needed to develop and maintain their own internal policies on exchange formats. These two factors led to a framework that accounted for a wide range of demanding requirements.

The upshot of this complicated process was a set of recommendations that the IDABC made to the high-level member state officials in 2004. They specifically said that states should adopt revisable XML-based formats, but stopped short of recommending the OASIS Open Document Format.

Why would they go so far, arriving at a framework that surely recommends ODF, and then fail to follow through? So far as the IDABC were concerned, ODF met all of their requirements. In fact, Held said in her talk that "in the view of the European administrations and Member States, the ODF standard is at the very top of the pile by far from all other proposed open standards." So why not just recommend ODF? Held said she was unable to comment officially on the matter, but she did explain the general reasoning that led to this decision.

To begin with, the legal definition of an open standard in the EU excludes those controlled by industry consortia; ODF is controlled by the OASIS consortium. The EU only recognises standards published by international bodies such as the ISO and the IEC. Whilst version 1.0 of the ODF was accepted as an ISO standard in May 2006, subsequent versions need to be resubmitted, and it is unlikely that this will happen again until the release of version 1.2 in 2008. The second problem is that the intellectual property models of European standardisation bodies and key players usually include RAND, which makes them incompatible with the stipulations of the EIF.

Third, and most troubling of all, is that the Commission must remain neutral between competing international standards. Whilst member states and EU bodies can certainly discriminate between such standards, the EU itself cannot embed such a decision in a European requirement to use, for example, ODF rather than Microsoft's OOXML. The background of this neutrality is fair competition, which is found in directive 98/34. This directive may be revised, since this is such a hot topic at the moment, so there is room to overcome this barrier to ODF becoming the official format of the EU.

To summarise the labyrinthine complexity of this, the EU is currently moving toward the standardisation of document formats, and internally many EU bodies and member states prefer ODF. But the EU is unable to require the use of ODF across the board.

So where do we go from here? The more stakeholders voice their support for ODF, the more likely it is that Europe will standardise on it, either with a legally binding decision or a series of unambiguous recommendations. Citizens of the EU can talk to their representatives in the European Parliament, pressing home the advantages of ODF by referring to the EIF and the IDABC's recommendations made in 2004, and also talk to their national representatives, increasing the pressure to standardise on ODF on a national and even local level.

Even without a decision of recommendation from the Commission, ODF seems the clear leader amongst document formats, as confirmed by Held's statement in its favour.

Share    Print    Comments   


on Where ODF stands in the EU

Note: Comments are owned by the poster. We are not responsible for their content.

It's good to question odf too

Posted by: Anonymous Coward on October 27, 2006 02:13 AM
Thank you for a nice level headed, rational discussion of the issue, quite unlike the usual "We must use odf because M$ sucks!" stuff. Of course, I'm an odf supporter (although not European) but it would be a big mistake to enforce a standard purely based on politics.


Politics are a central issue!

Posted by: Anonymous Coward on October 27, 2006 05:11 AM
In an ideal world technical bodies would unite and happily write the ideal standard, perfect _and_ totally compatible with everyone and his dog.

In this Earth we live on, a standard is a political statement. It arises from annoying differences and as a way to counter someone who has gained too much control. Read Mr. Wheeler's "Why Openoffice won..." to understand this and other nuances.

It's naïve (naive) to think you gonna have success based only on technical merit. Hundreds of excellent products died because the major player wanted so.

In fact, at times, products are aimed at annihilating entire markets, as we've seen earlier in the browser wars, when Netscape 4 was made extinct.

I know you said "purely" in a way to mean there are more valid reasons; I contend there is not and we should be very wary that Politics is _the_ main reason to have a standard.

Or prepare to lose again.


Re:Politics are a central issue!

Posted by: Anonymous Coward on October 27, 2006 10:43 AM

You and ESR would either get along just fine, or you'd have a minor disagreement and he'd kill you.


Re:Politics are a central issue!

Posted by: Anonymous Coward on October 28, 2006 07:48 AM
>> You and ESR would either get along just fine, or you'd have a minor disagreement and he'd kill you.

That might be, as he is a fan of firearms and I'm not.

Come to think, are you thinking I'm RMS?

Because I'm not.

Now for the funny part: when you're in the Evil Corp. it's difficult to see its outside actions and the whole pic...

You may laugh now. And forgive me if I'm not in the mood...


ODF interoperability

Posted by: Anonymous Coward on October 27, 2006 07:58 PM
I wonder am I alone who struggle with ODF interoperability.

<a href="" title=""></a> &
<a href="" title=""></a>

OO.o apparently doesn't focus much on interoperability with other ODF suits/applications: interoperability with M$Office pays back better.

On other side, KOffice is yet too young to for any interoperability to be considered: feature completeness comes first.

I'd vote with both hands for KOffice - but it doesn't support Windows yet. It took some time to have customers install OpenOffice. And even if they have now OO.o installed, I still cannot send them documents made in KOffice: OO.o supports only OO.o. The situation looks really bad, especially when you tell people that OO.o would facilitate document exchange with other OSs.

And also fonts problem should deserve special attention: different platforms have different font sets. And that's affect of course the resulting document and how it looks. I yet to find any solution on how can I edit freely document simultaneously under Linux & Windows. Probably basic set of fonts has to be standardized and all OSs would need to provide the fonts or their substitutes. Something like that.


Re:ODF interoperability

Posted by: Anonymous Coward on October 29, 2006 04:04 PM
I just tested this out with:
StarOffice 8 2.0.2
KWord 1.5.0 (Kde 3.5.3 [KOffice])

All three of the above named applications produce ODF-compliant<nobr> <wbr></nobr>.odt documents which can be opened, edited and saved by any of the other 2 above named applications.

There is no interoperability issue to be had between any of these programs.

StarOffice and do have the full microsoft document compatability that KWord lacks; however, there is no reason that the three applications will not be document compatability equivalents upon the next iteration of the Koffice suite.

As to the issue of fonts:
It's a trivial matter to search the filesystem for all instances of<nobr> <wbr></nobr>.ttf files. Once found, you've got the game won. Simply merge the fonts, from both windoze and Linux platforms, onto a CD or over the network. Problem solved. Use what you want, when you want.

This is one of my first installation tasks, along with codecs and a uniform set of applications for each build.


EU-Directive in favour of open standards

Posted by: lowmeus on October 28, 2006 03:00 AM
There does exist an EU-directive that seems to point to open standards when publishing information as a public organisation: The EU-Directive on the re-use of public sector information. [1] The following text is a citation of that Directive.

"To facilitate re-use, public sector bodies should make their own documents available in a format which, as far as possible and appropriate, is not dependent on the use of specific software. Where possible and appropriate, public sector bodies should take into account the possibilities for the re-use of documents by and for people with disabilities."

[1] <a href="" title=""><nobr>?<wbr></nobr> uri=CELEX:32003L0098:EN:HTML</a>


This story has been archived. Comments can no longer be posted.

Tableless layout Validate XHTML 1.0 Strict Validate CSS Powered by Xaraya