Showing posts with label ODF. Show all posts
Showing posts with label ODF. Show all posts

Tuesday, March 13, 2007

Glimmer of Hope for Desktop Linux?

In the last week or so, I have read three different articles that talked about different government agencies that are banning Microsoft's Vista operating system, along with other Microsoft products in some cases. The National Institute of Standards and Technology (NIST) is the latest, and this follows the US Department of Transportation (DOT) and the Federal Aviation Administration (FAA).

So, what makes this a glimmer of hope for desktop Linux. Well, at least in one of those cases, the FAA, is seriously looking at a combination of Linux desktops with Google's new enterprise applications as a replacement for Windows and Microsoft Office! When you combine this type of interest with other government initiatives to adopt open standard file formats, you can see a glimmer of hope that the Microsoft lock is being broken by some large government agencies.

You could say, so what! It's only some public sector organizations! What makes this a glimmer of hope, in my mind, is the carry over affect it could have on the private sector.

If enough government agencies start adopting open technologies like Linux and ODF, then the private sector companies that have to do business with them will have to adopt technologies that inter-operate. This in turn loosens the grip that Microsoft has on a larger portion of the market.

I sincerely hope that these government organizations aren't just bluffing to get concessions out of Microsoft. With large scale adoption of open technologies, such as Linux and ODF, we will all be better off. True competition on the market for desktop operating systems and applications could become a reality someday.

Wednesday, February 14, 2007

Is OOXML Open as Microsoft Claims?

Microsoft recently posted an "open letter", complaining that IBM is not in favor of open standards, and that they are all hypocrites. It is noted that IBM was the only one to vote no in the ECMA process for the standardization of OOXML. I find this to be disingenuous to say the least.

Microsoft claims that OOXML is open because of its acceptance as an ECMA standard. In my opinion, that hardly makes it open. The rules by which ECMA standards are created are very loose indeed, and I don't blame IBM one bit for voting against it. I just can't believe that everyone else involved didn't vote no too!

File formats have become an interesting topic of conversation, ever since ODF (Open Document Format) came on the scene. Before ODF became an OASIS and ISO standard there were no open standards for office document formats. With Microsoft controlling the majority of the market for office productivity applications, their proprietary file format has been lock-in heaven for them, and lock-in hell for their customers.

ODF threatens to break that lock-in, and free customers to choose alternatives, without the problems associated with proprietary file formats (lost formatting, can't edit with a different application, etc.). So, Microsoft had to act to protect its franchise, because they simply are afraid to, or maybe they can't, compete on the quality of their implementation of office productivity software. Of course, it would also commoditize the market, and drive down prices. With Office being almost half of Microsoft's profits, that's a hard pill to swallow.

With that as the backdrop, is OOXML truly open?

The short answer is an emphatic NO!

The reason for this is simple. The specification clearly references proprietary Microsoft Office technology that cannot be implemented by anyone other than Microsoft. Truly open standards, need to be able to be implemented by anyone that desires to do so, and this is simply not the case with OOXML.

Without the ability for competing products to implement the file format, Microsoft can claim to have an open standard file format, and keep the lock-in they have enjoyed for years. As they say in the Guiness commercials, "brilliant!".

Of course, I hope the ISO will put an end to this charade, and vote this down as an ISO standard. That is the only just thing that can happen. If Microsoft gets away with this, Microsoft will have won again, and the joke is on us.

What's the old saying? Fool me once, shame on you, fool me twice, shame on me!

Well, if the ISO members are fooled into accepting OOXML as a standard, it will not only be the shame of the ISO members, but a shame on the entire world!