Desmond File

Blog archive

ISO Denies OOXML Appeal

Back in the heat of the democratic presidential primary race, I used to joke that newly-minted front runner Barack Obama was running against the reanimated zombie corpse of Hillary Clinton. For months, it seemed, Obama would score an emphatic victory, only to give Clinton new life a week or so later with a sub-par result. Obama's failure to close out Clinton helped produce an unnecessary, months-long chase that nearly destroyed both candidates.

The lesson is simple: Let a candidate or an issue or a problem linger long enough, and it will take on a life of its own and strangle you, like something out of a Sam Raimi movie.

The International Organization for Standardization (ISO) has apparently decided not to make that mistake.

Back in April, the Office Open XML (OOXML) file format specification earned enough votes to gain ratification as an ISO standard. Four nations -- Brazil, India, South Africa and Venezuela -- later filed appeals alleging flaws in the process. Under the ISO process, OOXML was set aside while the appeals were reviewed. Now it appears the ISO is recommending that those appeals be denied.

Industry watcher Andy Updegrove, who blogs extensively about technology standards issues at consortiuminfo.org and co-founded the Digital Standards Organization, last week obtained a letter indicating the group's recommendation. He says the decision to ignore the valid complaints of member companies exacerbates a process that had been overwhelmed by the high-stakes OOXML effort.

"What we have seen is that the system really isn't that healthy when it comes to a hotly contested standards war. When that happens, rules and processes that may work well in a collegial environment can break down badly," Updegrove said in an e-mail exchange. "In my view, though, it goes deeper than this, however, in that I think that some of the judgments made by ISO in managing the process were terrible -- such as scheduling a one week Ballot Resolution Meeting to resolve 1200 issues."

The problem, Updegrove said, is that the ISO directives provide no mechanism for appealing ISO judgments. And Updegrove, for one, believes the ISO likes it that way.

"What I think you see here is a portrait of a comfortable management that has made some terrible calls, and yet is protected by rules that make them almost immune from being called to task," he complained. "Hundreds, if not thousands, of standards professionals around the world have been put through the wringer during this process, and those that have gone through the domestic heat to file appeals are now being told that their job is simply to take whatever they are told to do, no matter how ill-considered those requirements may be."

All that may well be true. But I think there may be another, more existential reason for the ISO's recommendation. The organization did not want to create the reanimated zombie corpse of the OOXML standards fight. The first go-around was bad enough.

Posted by Michael Desmond on 07/15/2008


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