Mano a Mano with Microsoft: Update

A couple of weeks ago, I wrote about an impending meeting with Microsoft to discuss some of its actions during the standardisation process of OOXML at the ISO. I asked Linux Journal readers for some help in preparing for this, and you responded with a generosity entirely in keeping with the spirit of free software. The many helpful comments to that post give some indication of the scale of the response, but that overlooks the extraordinary emails I received from others, packed with useful information, which clearly represented many hours' work. To everyone, I'd like to express my thanks. The bad news is that the meeting is not going to take place after all.

That's not because either I or Microsoft chickened out, but a consequence of the fact that the CIO of Newham, Richard Steel, for whose benefit the meeting was being held, has rather suddenly and unexpectedly announced that he is retiring. In the wake of this news, I contacted Microsoft, and we agreed that there was little point holding the meeting as originally planned.

However, I was very conscious of the huge amount of effort that people had put into this matter, and so I wondered how that might be salvaged. Since the issue of how Microsoft behaved during the ISO process is still a very live one, it seemed to me a worthwhile exercise trying to pull together a summary of certain aspects of what happened last year. Since the whole point of doing this was to hear Microsoft's response, I asked the company whether they would be interested in writing a reply to my post, and they have agreed to do so. Quite what this will produce, I don't know, but I think it's worth trying. At the very least, there will be some more documentation of what happened, and maybe some new points from Microsoft too.

To clarify: what I aim to concentrate on is not the technical side – what was and still is wrong with OOXML as an ISO standard – so much as the procedural issues at the national level. Sifting through the wonderful resources provided by Linux Journal readers, I aim to pull out what seem to me the clearest cases of Microsoft bending the system to produce the result that it wanted.

I will omit the many vague accusations that were flying around at the time, simply because it wouldn't be fruitful to include them. Microsoft could rightly say that they are merely unsubstantiated rumours. Even though this will mean leaving out some of the more egregious flouting of rules, I think it will make the case stronger by virtue of concentrating on those incidents that are most substantiated and least easy to dismiss.

I'm currently putting that document together; I will then post it here and send the link to Microsoft for comments, which can be in whatever form they wish. I then aim to publish the comments, unedited, alongside my original post in some way, depending on what format Microsoft chooses. It will be interesting to see what, if anything, all this will produce.

Follow me @glynmoody on Twitter or


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

In an unusual devotion of time

Gregory Dumenil's picture

Sen. John Kerry has made it in politics. Now he wants to be a movie producer.

Feel better about your achievements: Michelangelo at 12

Richard Hogg's picture

I sat in a mock-up of the new Cirrus Jet today alongside Alan Klapmeier, the companys co-founder, who was visiting Hanscom Field (KBED). The interior reflects some truly brilliant design. The seats slide back and forth on long tracks, allowing a lot of flexibility. People could swap seats with the pilots without knocking the thrust

MySQL and Percona Conferences Rocked

Ivie Ginn's picture

Hey cool! Go Scott!

The apartment life

Anne-Marie's picture

This is just wonderful. For her final year project at the Glasgow School of Art, Eleanor Stewart created a stop motion music video for Aaron Copelands Hoedown. In it cowboys, horses, and the wild west come to life from the very pages of the musical score: Hoedown from Rodeo

Big picture: it is ISO itself that Microsoft was attacking

Anonymous's picture

Microsoft, like many other multinational companies, believe that it is _they_ who should be setting the rule, parameters, specifications, and regulations by which all others live. Microsoft's aim here was either to 1) replace ODF entirely; or 2) render ISO itself irrelevant by trashing the ISO approval process itself.

The important thing to recognize here is that Microsoft sees not only ODF competing with OOXML; but indeed, ISO itself. How dare a "bureacracy" like ISO attempt to establish the parameters by which a market leader like Microsoft should behave? It trammels the free market! Government is not the solution, government is itself the problem! That applies even to non-governmental standards bodies like ISO.

Microsoft's behavior during the ISO process is merely a symptom of something much deeper -- Microsoft's contempt for anything and anyone who interferes with its illegal monopoly and thus its divine right to seek exorbitant profit margins. Microsoft refuses to compete. It is the free market itself of which Microsoft is contemptful. The checks and balances of the free market have been destroyed in the desktop PC software market, and that is the problem. All other behaviors are mere reflections of the fact that Microsoft has broken the market. Ironically, Microsoft touts the same free market that it has broken, in an exercise of Orwellian double-speak. "War is Peace; Freedom is Slavery; Ignorance is Strength; and Microsoft supports the free market."

Christian Einfeldt

good question

Glyn Moody's picture

Everything's up in the air: we'll have to see who takes over, whether they're interested in having a conversation etc.

depending on what format Microsoft chooses

James Arnold's picture

"depending on what format Microsoft chooses"
OOXML? hehehe

It's a pity Richard is leaving, would have made for a nice face-off. But glad you are getting it all together for posterity, absolutely great idea.

What happens now re the council's future IT plans?