Commentary

Charles Babcock
InformationWeek  

Britain Endorses ODF; Why Not The U.S.?

The Open Document Format was adopted today by the British government as a basis for making future software purchases based on open standards. In general, Britain is requiring government agencies to use as much software based on standards as possible, based on its 10-point program to encourage open standards and open source. If Britain can do it, why can't we?

The Open Document Format was adopted today by the British government as a basis for making future software purchases based on open standards. In general, Britain is requiring government agencies to use as much software based on standards as possible, based on its 10-point program to encourage open standards and open source. If Britain can do it, why can't we?ODF was the subject of the fight in Massachusetts, a state whose CIO once attempted to adopt ODF, before he resigned in the face of opposition to go on to other things. Instead of backing away from ODF implementation, Britain is embracing it. That's bad news for those who like monopolies based on proprietary formats.

ODF already is the standard in several European countries, but it seemed to make headway initially with those with the least empathy for aggressive, free enterprise, say, Denmark, France, the Netherlands, Belgium, Poland, and Croatia. It's also at this point been adopted on the Continent by Germany, Norway, Switzerland, and two states in Spain.


More Software Insights

White Papers

More >>

Reports

More >>

Webcasts

More >>

Beyond Europe, ODF is the standard in Brazil, Uruguay, Venezuela, and the Argentinian state of Misiones in South America.

It's been adopted by Japan, Malaysia, and two states of India, as well as Hong Kong.

Other countries that have adopted it are South Africa and Russia, according to the ODF Alliance.

In this group of adopters, Britian is the country with the closest ties to North America. Its economy thrives, if that's the right word these days, on a similar liberal capitalism and technology-driven development. If Britain can adopt ODF, why not the U.S.?

I remember the arguments made against ODF in Massachusetts: if the state were to require it, that would be a sop to socialism, a strike against the time-honored business of proprietary software. But the software business is best justified when it takes place in a competitive environment. When it comes to desktop documents, there is little competition in general and within some organizations, no competition at all. Even where modest competition exists, a market dominated by a second Microsoft monopoly prevails.

Public agents can best serve the public interest by insuring government documents don't at some point disappear behind proprietary formats. What if, in the interest of driving sales of a new product line, a company announced that an older document format would no longer be supported? Government archives and personal computer users everywhere would be forced to migrate or invest in some conversion process that world restore their ability to display their own documents.

A group of open source practitioners recently wrote to President Obama, urging him to make mandatory the consideration of software that follows open standards. He could minimally support this proposal by issuing an executive order that open source products get considered alongside proprietary ones on a level playing field.

Or he could take a giant step forward and say, unlike Massachusetts, the federal government will require ODF as the document format for doing government business. Such a move would strike a blow for open standards in an arena where more openness would be a welcome change from the status quo.


Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

InformationWeek encourages readers to engage in spirited, healthy debate, including taking us to task. However, InformationWeek moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. InformationWeek further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.
T-Shirt Giveaway T-Shirt Giveaway: Each week we're selecting one great comment from our readers. The author of the comment will receive an InformaitonWeek Community t-shirt. So get posting!
Subscribe to RSS

Resource Links