Summary: The sham which is OOXML and what the past teaches us about it
THANKS to some funds from former Microsoft executives, Mono continues to be developed, giving the illusion that there is something “open source” about .NET. We saw the same thing being done to promote the idea that OOXML is “open”; companies like Novell were bribed to become participants. According to this new post from Andy Updegrove, only in 2012 did Microsoft actually get an implementation of OOXML. To quote: “Yesterday, Microsoft made an unobtrusive announcement that brings a degree of closure to a seven year long epic battle between some of the largest technology companies in the world. The same saga pitted open source advocates against proprietary vendors, and for the first time brought the importance of technical standards to the attention of millions of people around the world, and at the center of the action were Microsoft and IBM, the latter supported by Google and Oracle, among other allies.”
Just as we stated years ago, nobody had implemented OOXML; this was just an excuse for attacking ODF and keeping people stuck with Office. Looking further back we find that Microsoft used similar tactics against old Novell. To quote Pamela Jones: “When Judge J. Frederick Motz recently threw Novell’s WordPerfect antitrust case under a bus, ruling for Microsoft on its motion for judgment as a matter of law, his excuses seemed flimsy to me, at best. One of his reasons was that, in his view, when Microsoft withdrew support from certain APIs back in the ’90s, Novell could have just used what they already had to at least come up with a makeshift solution to tide them over so as to be ready for the Windows 95 launch. He also found it important that Novell bigwigs didn’t complain about the APIs to Microsoft at the time.
“Was he right?
“[I]n the process of corruption Microsoft managed to rip people out of their job (we provided example), simply because they stood up against Microsoft’s criminal activity.”“I want to show you some emails from 1994 and 1998 our volunteers have just transcribed as text, from the collection of PDF exhibits in Comes v. Microsoft. The 1994 internal Microsoft thread includes Jim Allchin saying, in effect, that the company should deliberately make sure competitors’ applications don’t work as well on Windows as their competing applications do. That is precisely what Novell claims happened with WordPerfect, and in that exact time frame. The Allchin email seems to match Bill Gates’ notorious email about deciding to pull back on the API support (“We should wait until we have a way to do a high level of integration that will be harder for the likes of Notes, Wordperfect to achieve, and which will give Office a real advantage.”). And then there are a couple of internal Novell emails from 1998 on problems with Microsoft, and finally a Gateway thread from the same general time frame, showing how Microsoft could really mess your business up, if Microsoft Help didn’t want to help, which Novell says is what happened right after Microsoft pulled the API support.”
This is very revealing. Microsoft does everything to sabotage interoperability and it still does not get punished for it. Rich criminals are rarely being jailed, even when they bribe, cheat, and bully. See the OOXML abuse index.
Glyn Moody says the latest news “means [Microsoft] *failed* to [implement OOXML] until now” and he links to this submission from Updegrove. Not a single person was sent to prison for what clearly was Microsoft corruption. Not a single person in Microsoft lost his or her job, either. On the contrary, in the process of corruption Microsoft managed to rip people out of their job (we provided example), simply because they stood up against Microsoft’s criminal activity. █