Now that Microsoft's attempt to ramrod its semi-open OOXML standard through the ISO standards body has fallen short, writes Bernard Golden, what happens next? Strangely, he says, Microsoft appears to be soft-pedaling its own standard.

"Despite having an open source strategy the South African government doesn't really understand how to benefit from OSS. This is according to Microsoft director of corporate standards, Jason Matusow." Stay tune for more FUD from Microsoft...

Microsoft’s position is hardening as the ISO vote on OOXML (DIS 29500) in Geneva approaches at the end of this month. We know more clearly now how Microsoft and its proxy group, ECMA, will position Microsoft’s OOXML specification in advance of the vote. In short, Microsoft is betting that its influence with National Bodies will allow it to push through a specification which elevates its own interests over that of truly competitive, open international standards. In the end, it will be Microsoft’s own inflexibility that will be its undoing, and that undoing means knocking the OOXML out of approval for ISO status.

A presentation from an IBM employee in Europe has just been shared a little more publicly. It describes the serious problems ISO will be facing after the countless OOXML scandals that worked in Microsoft’s favour.

For years Microsoft has had the de facto "standard" everything simpy because the majority of people use it and think it is the standard. Microsoft never did anything about this. It enjoyed the de facto standard position and never actually sought to makes it formats actual standards. But in 2006 something happened.

Alex Brown, the convenor of the ISO's Office Open XML (OOXML) Ballot Resolution Meeting, has accused Microsoft of failure in its efforts to transform the document format into a genuinely open standard

ECMA, the international IT standards association, recently published its responses to comments of the ISO National Bodies in response to Microsoft's Office Open XML application for ISO standardization (the actual 2,293-page response is closed to the public). The ECMA proposals will be discussed at a Ballot Resolution Meeting (BRM) in Geneva after which the National Bodies may reconsider their original vote. Microsoft's responses make clear that within one year, it will have four different OOXML specifications to implement and interoperate with, and each of those specs will be closed. Under no circumstances should such a flawed specification become an international standard.

It was a short presentation that focused dryly on "opportunities" for open source in something he called the "service-driven data center." But when he turned to the need for Linux to inter-operate with Windows in this service-driven data center, Novell's chief executive Ron Hovsepian delivered an apology - of sorts - for his company's controversial marriage to Microsoft in 2006.

Following criticism from the Open Source Industry Association (OSIA) over its ambition to have the Office Open XML (Open XML or OOXML) format accepted as an international (ISO) standard, Microsoft's group product manager for Microsoft Office, Gray Knowlton, spoke with Computerworld about why the world needs two standard document formats.