AT THE BEGINNING of this week we learned that the British (UK) Cabinet Office, a highly influential department with technology imperatives, did the correct thing by no longer requiring British citizens to become clients of Microsoft (and users of expensive spyware) to merely communicate with their government. The Cabinet Office "goes open source" is how one news site put it, but ODF, the OpenDocument Format, is not necessarily about Free/Open Source software. ODF is about many applications working together, not via formats that are designed around a single application and its various versions (that's what OOXML is).
The U.K. Cabinet Office accomplished today what the Commonwealth of Massachusetts set out (unsuccessfully) to achieve ten years ago: it formally required compliance with the Open Document Format (ODF) by software to be purchased in the future across all government bodies. Compliance with any of the existing versions of OOXML, the competing document format championed by Microsoft, is neither required nor relevant. The announcement was made today by The Minister for the Cabinet Office, Francis Maude.
The open standards selected for sharing and viewing government documents have been announced by the Minister for the Cabinet Office, Francis Maude.
While celebrating this great news, I really want to emphasise Bracken's point about managing the switch properly. We can be absolutely certain that Microsoft will fight this decision in every way possible. It will certainly seize on any problems that arise during the implementation as "proof" that it was the wrong choice. That makes it crucial that the open source community do everything in its power to aid the Cabinet Office here.
One particular area that concerns me is cross-compatibility. I'm hearing stories about difficulty in transferring ODF files from LibreOffice to Apache OpenOffice, with formatting of things like tables being messed up in the process. This is completely unacceptable: one of the benefits of adopting an open standard is the ability to swap in and out different applications. If that theory proves impossible in reality, we have a huge problem.
I would therefore like to entreat all the open source projects and communities that work on ODF to get together and sort this out. In the wake of the fantastic - and brave - move by the Cabinet Office, providing full interoperability among open source implementations must be a priority.
Yesterday's news is truly a unique opportunity to show the power of open standards, to promote the benefits of open source, and to bring about its wider dissemination both in government, and among home users. The price of failure here would be extremely high: yet more years in the wilderness, as happened after the Massachusetts ODF fiasco a decade ago. So let's not mess it up.