Desmond File

Blog archive

The OOXML Odyssey: In Defense of Microsoft

Call it "Standardization Theater." Last week, I wondered about the lack of positive takes when it came to Microsoft's proposed Office Open XML (OOXML) standard, currently under review with the International Organization of Standardization (ISO). Having received a flood of decidedly critical opinions about OOXML, I wondered how it was that no one reading the RedDevNews newsletter -- an audience likely to be friendly to Microsoft technologies -- was saying anything good about OOXML.

Well, I heard a couple of responses. The first is from Jan Hansen, a developer out of Copenhagen, Denmark. "Your previous article was linked to from Groklaw," he writes. "Maybe only visitors who came from there bothered to respond to your question in that article."

Good point. Ben, an IT director in Leeds, England, contends that he and other Redmond supporters haven't written in because "[it's] not our job. Microsoft is a big company with a big budget and can look after itself."

He goes on with an interesting theory, which is that the ISO standardization push is simply a grandstanding maneuver. He says the open source community first gets its technology established as an ISO standard, then turns around and lobbies to require ISO ratification as a way to keep competing technologies (read: Microsoft) out of government contracts.

Writes Ben: "Best case for Microsoft, people will see through the tactic, and realize that being blessed by ISO is worth exactly nothing outside of politics. Worst case, MS will have to write a tip-top ODF import/export to get government contracts, and will have to write tip-top DOCX import/export for OpenOffice to ensure DOCX remains the interchange format -- which will basically mean massively improving OpenOffice."

Is ISO ratification just public theater in the ODF/OOXML contest? I spoke with Alexander Falk, CEO of Altova -- the company that makes XML-savvy software like XMLSpy -- and he seems to think so. Falk says that the ISO process is a good thing in that it helps improve the OOXML spec by bringing forward third-party input. But he says he expects Microsoft's XML-based file format implementation to gain widespread adoption with or without ISO sanction.

"At the end of the day, I think it will be in [Microsoft's] best interest to get through it and make those changes," Falk says. "But my gut feeling is they still have sufficient market share to push OOXML through as a de facto standard, even if it doesn't become an ISO standard."

What do you think? Does it even matter if Microsoft ends up providing an ISO-approved XML file format specification? Or will the mere existence of XML-based default file formats in Office be enough for most IT and dev shops to get behind? E-mail me at mdesmond@reddevnews.com.

Posted by Michael Desmond on 09/26/2007


comments powered by Disqus

Featured

  • Compare New GitHub Copilot Free Plan for Visual Studio/VS Code to Paid Plans

    The free plan restricts the number of completions, chat requests and access to AI models, being suitable for occasional users and small projects.

  • Diving Deep into .NET MAUI

    Ever since someone figured out that fiddling bits results in source code, developers have sought one codebase for all types of apps on all platforms, with Microsoft's latest attempt to further that effort being .NET MAUI.

  • Copilot AI Boosts Abound in New VS Code v1.96

    Microsoft improved on its new "Copilot Edit" functionality in the latest release of Visual Studio Code, v1.96, its open-source based code editor that has become the most popular in the world according to many surveys.

  • AdaBoost Regression Using C#

    Dr. James McCaffrey from Microsoft Research presents a complete end-to-end demonstration of the AdaBoost.R2 algorithm for regression problems (where the goal is to predict a single numeric value). The implementation follows the original source research paper closely, so you can use it as a guide for customization for specific scenarios.

  • Versioning and Documenting ASP.NET Core Services

    Building an API with ASP.NET Core is only half the job. If your API is going to live more than one release cycle, you're going to need to version it. If you have other people building clients for it, you're going to need to document it.

Subscribe on YouTube