You’ve read how Microsoft drove its tank through the international standardization process last year and this year, finally winning ISO approval for its legacy OOXML format. The OOXML event proved that we’re in a real fight, and that money and power can break down the existing polite rules and agreements that constitute the international standardization process.

The Apache Software Foundation concludes that that JCP is not an open specification process - that Java specifications are proprietary technology that must be licensed directly from the spec lead under whatever terms the spec lead chooses; that the commercial concerns of a single entity, Oracle, will continue to seriously interfere with and bias the transparent governance of the ecosystem; that i

Standards are supposed to be about a process of creating points of reference that people can rely upon, arrived at through a process of careful honing and consensus. Against this background, the manner in which Microsoft's OOXML has been put through the ISO has been astonishing.

You may have read our background article about ODF and OOXML and why Red Hat believes OOXML should not be approved as an ISO standard. This time, we focus on how the standardization process has been compromised at ISO.

In Part I of this OOXML update, my first post on the topic in over a year, I showed you how Microsoft maintains strong control over the OOXML standard.

It's been a while now, and I'm still trying to enforce HZN (Croatian national standards body, or CSI) to disclose the information on members of their TC that voted unconditional yes for Microsoft OOXML. It's no more about OOXML. It's about transparency, about my right to know who are the people that declare standards, and about my right to hold them responsible for their actions.

Is it time to standardize ISO? In light of the recent events relating to the standardization process of EOOXML, it seems appropriate to look into possible standardization of the process itself.

Microsoft is urging Indian NGOs to support OOXML (i.e. Office Open XML) format - and persuade Indian IT Secretary and the Additional Director General of the Bureau of Indian Standards with letters supporting MS’s OOXML proposal.

It turns out that not even Microsoft will comply with OOXML; more cracks in the ISO process