The Wall Street Journal is publishing an article mentioning the OOXML fiasco, and the intention of IBM to leave some standards organisations (ECMA Microsoft-proxy is probably on the shooting line). With the disgusting Microsoft committee stuffing and the non-reaction of ISO, I would say this is something I should do now in terms of protest. The current way to define standards behind closed doors, closed rooms, and with archaic methods of patching standards proposals outside of the public eye is something that should be reformed. Remember, physical meetings are the way to exclude participation (oh, by the way, there was an SC34 meeting in South Korea where I forgot to blog about).
BRUSSELS — International Business Machines Corp. will review its membership in the bodies that set common standards for the technology industry and may withdraw from some, potentially undermining the system that makes electronic equipment and software interoperable world-wide.
The Armonk, N.Y.-based computer maker is expected to announce the review Tuesday, according to company officials. IBM has become frustrated by what it considers opaque processes and poor decision-making at some of the hundreds of bodies that set technical standards for everything from data-storage systems to programming languages, those officials said.
A recent battle over the selection as an international standard of the file format used in Microsoft Corp.'s Office software suite appears to have influenced IBM's decision. Microsoft, of Redmond, Wash., won that contest in April when its Open XML format was approved by the Geneva-based International Organization for Standardization, or ISO.
Standards are key to the tech industry, where they provide a common foundation for products from different manufacturers. Internet standards allow millions of computers to display a Web page the same way. IBM controls a vast cache of intellectual property in the high-tech field. As a result, its contributions and agreement are often critical to forming a standard.
IBM and open-source groups that support collaborative software development said Microsoft had stacked the national committees that make up the ISO with employees and sympathetic voters. They also said Open XML is so complicated and obscure that only Microsoft could fully exploit it, cementing the software company's already-considerable lead in office-document software. IBM backed a rival format called Open Document that was already certified as an ISO standard.
A Microsoft spokesman said standards bodies are "invaluable" because they provide "an even and predictable playing field" to the industry. Their decisions reflect the views of a preponderance of members, "not the interests of any single party," he said.
"There are lots of issues" with standards groups beyond the office-documents arena, said Bob Sutor, an IBM vice president who is the company's top standards official. He cited high membership fees that deter small players, complicated intellectual-property policies and opaque procedures.
In an interview, Mr. Sutor singled out for particular criticism Ecma International, a Geneva-based group of which IBM was a founding member more than 45 years ago. Ecma certified the Open XML standard over IBM's objection and submitted it to ISO for broader approval.
Getting a company-backed product approved as a standard can be a boon: In Microsoft's case, Open XML's certification eased hesitations by some government purchasing agents, who were reluctant to buy nonstandard software.
Istvan Sebestyen, Ecma's secretary-general, said he was "really amazed" at Mr. Sutor's contention that Ecma certification can be bought, and added he hadn't heard formally from IBM about any intention to withdraw. "Ecma didn't get one single dime more" from the Open XML approval, he said.
Write to Charles Forelle at moc.jsw|ellerof.selrahc#moc.jsw|ellerof.selrahc
Maybe ECMA can justify why they are producing so crappy standards with so many bugs inside?
Maybe someone reading this blog might want to draft an Open Letter to ECMA, asking them if they have not seen this guy redrafting the Fast Track rules in 2006 for a client from Redmond?