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.
Today’s modular x86 servers are compute-centric, designed as a least common denominator to support a wide range of IT workloads. Those generic, virtualized IT workloads have much different resource optimization requirements than hyperscale and cloud applications. They have resulted in a “one size fits all” enterprise IT architecture that is not optimized for a specific set of IT workloads, and especially not emerging hyperscale workloads, such as web applications, big data, and object storage. In this report, you will learn how shifting the focus from traditional compute-centric IT architectures to an innovative disaggregated fabric-based architecture can optimize and scale your data center.
Sponsored by AMD
Built-in forensics, incident response, and security with Red Hat Enterprise Linux 6
Every security policy provides guidance and requirements for ensuring adequate protection of information and data, as well as high-level technical and administrative security requirements for a system in a given environment. Traditionally, providing security for a system focuses on the confidentiality of the information on it. However, protecting the data integrity and system and data availability is just as important. For example, when processing United States intelligence information, there are three attributes that require protection: confidentiality, integrity, and availability.
Learn more about catching the bad guy in this free white paper.
Sponsored by DLT Solutions
| Making Linux and Android Get Along (It's Not as Hard as It Sounds) | May 16, 2013 |
| Drupal Is a Framework: Why Everyone Needs to Understand This | May 15, 2013 |
| Home, My Backup Data Center | May 13, 2013 |
| Non-Linux FOSS: Seashore | May 10, 2013 |
| Trying to Tame the Tablet | May 08, 2013 |
| Dart: a New Web Programming Experience | May 07, 2013 |
- New Products
- Making Linux and Android Get Along (It's Not as Hard as It Sounds)
- Drupal Is a Framework: Why Everyone Needs to Understand This
- A Topic for Discussion - Open Source Feature-Richness?
- Home, My Backup Data Center
- RSS Feeds
- What's the tweeting protocol?
- New Products
- Trying to Tame the Tablet
- Validate an E-Mail Address with PHP, the Right Way
- IT industry leaders
1 hour 53 min ago - Reply to comment | Linux Journal
18 hours 41 min ago - Reply to comment | Linux Journal
21 hours 14 min ago - Reply to comment | Linux Journal
22 hours 31 min ago - great post
23 hours 6 min ago - Google Docs
23 hours 28 min ago - Reply to comment | Linux Journal
1 day 4 hours ago - Reply to comment | Linux Journal
1 day 5 hours ago - Web Hosting IQ
1 day 6 hours ago - Thanks for taking the time to
1 day 8 hours ago
Enter to Win an Adafruit Prototyping Pi Plate Kit for Raspberry Pi

It's Raspberry Pi month at Linux Journal. Each week in May, Adafruit will be giving away a Pi-related prize to a lucky, randomly drawn LJ reader. Winners will be announced weekly.
Fill out the fields below to enter to win this week's prize-- a Prototyping Pi Plate Kit for Raspberry Pi.
Congratulations to our winners so far:
- 5-8-13, Pi Starter Pack: Jack Davis
- 5-15-13, Pi Model B 512MB RAM: Patrick Dunn
- Next winner announced on 5-21-13!
Free Webinar: Linux Backup and Recovery
Most companies incorporate backup procedures for critical data, which can be restored quickly if a loss occurs. However, fewer companies are prepared for catastrophic system failures, in which they lose all data, the entire operating system, applications, settings, patches and more, reducing their system(s) to “bare metal.” After all, before data can be restored to a system, there must be a system to restore it to.
In this one hour webinar, learn how to enhance your existing backup strategies for better disaster recovery preparedness using Storix System Backup Administrator (SBAdmin), a highly flexible bare-metal recovery solution for UNIX and Linux systems.



Comments
In an unusual devotion of time
Sen. John Kerry has made it in politics. Now he wants to be a movie producer.
Feel better about your achievements: Michelangelo at 12
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
Hey cool! Go Scott!
The apartment life
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
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
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
"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?