As of this week, there's a new participant in the process of standardizing the OpenDocument office file format: Say hello to Microsoft.
No, Redmond hasn't done an about-face. You still won't be seeing an OpenDocument filter added to Microsoft Office. This latest move takes place strictly behind the scenes.
Without fanfare, Microsoft has joined Incits V1, a subgroup of the International Committee for Information Technology Standards that's responsible for "Text Processing: Office and Publishing Systems Interface". To make a long story short, this is the group that will steer OpenDocument through the process of becoming a formal ISO standard.
Instantly the alarm bells rang. "There sits Microsoft, waiting, like a spider," blogged Groklaw's Pamela Jones; the obvious assumption being that Microsoft is planning to subvert the OpenDocument standardization process through some kind of procedural filibuster.
For its part, Microsoft says this isn't the case, insisting that it is interested only in shepherding its own file formats through the standardization process. Remember, Microsoft has based the default file format for Office 12 on XML, and it wants its new XML format to become an ISO standard. That means that it, too, must pass through Incits V1. Still, it's hard to believe that the participation of OpenDocument's most staunch opponent in a key standards committee will have no impact on the format.
Comparing Microsoft to a spider, however, is probably a bad analogy. Rather, arriving at standards is more like ordering a pizza for the whole family. Microsoft is that second cousin who loves pineapple, is allergic to cheese, and will only eat a pizza with pepperoni if it doesn't have tomato sauce.
Like it or not, Microsoft will have its say.
This is bound to be frustrating to some of OpenDocument's more staunch supporters.
Good standards take time because they're meant to stand the test of time. Microsoft's office document formats have not done that and there's little evidence that future standards strong-armed into existence by Microsoft will, either. That's why we needed a true standard in the first place, and it's why the process of standardization must continue in a fair and non-discriminatory way -- even with Microsoft at the table. Anything less would be hypocrisy.