03.12.08

Gemini version available ♊︎

Dirty OOXML Tricks Revisited; “Embrace, Extend, Extinguish” Strategy Redefined

Posted in Antitrust, Formats, ISO, Microsoft, Mono, Open XML, Standard at 12:27 am by Dr. Roy Schestowitz

The press is far from over discussing some of the misbehavior we have witnessed over the past couple of years. Although discussions about OOXML ought to have been just technical, they ended up getting mixed in the face of endless misconduct. Which shall one criticise more and bring more attention to: the technical hoax that is OOXML or the corruptions which OOXML has revealed?

Pieter has published a good new piece which looks at both aspects of this.

To conclude, Microsoft have, with OOXML, shot themselves in both feet, then put the bloody stumps into their big mouth and chewed, hard and long. They created a fradulent process by corrupting ISO at a high level. They engaged national bodies in this process, then bought and bullied those bodies into voting “properly”. And when the committees refused to be intimidated, they went to ministers and tried to bribe them. They used their press and astroturfing budgets to sell this as a fair and necessary process. They pretended that they were the victim, of an autocratic ODF and a manipulative IBM.

This excellent summary is all very truthful, and it can be accompanied by well-documented evidence to back the claims. IT Pro has published a new article as well and it emphasises the failures of the standardisation process. Here is a portion of the text:

A toxic leech

OOXML is controversial for a number of reasons. Critics argue that OOXML is not so much a specification as a description of Microsoft’s existing proprietary data formats, complete with the replication of historic bugs, the most notorious being the treatment of 1900 as a leap year. The specification was derived internally to describe Microsoft’s current data formats, and has not benefitted from the usual wide-ranging debate and participation from competing interests, hammering out their differences to find the points they have in common, that accompany the conventional definition of a standard.

A standard is intended to facilitate multiple implementations of a protocol or data format, not to give validation to the one existing implementation of that format. There have also been complaints that, despite the fact that over 3500 comments were raised against the original specification, delegates weren’t able to suggest amendments that contradicted Microsoft’s current implementation.

[...]

In truth, the opposition has come from all quarters, and has been most vocal among those interested in open standards, which includes everybody from governments through to representatives of the free and open source software movement, and also includes many parties with an interest in maintaining open access and network neutrality for civil or commercial reasons, including the likes of IBM, Google and Oracle.

OOXML translation

Rob Wier reminds his readers that OOXML is saturated with the same characteristics one typically finds in “Embrace, Extend and Extinguish” tactics. OOXML’s licence [1, 2, 3, 4, 5] and dynamicity, not to mention Mono dependencies in broken and lossy translation, may all be signs of things to come. They justify the need to intercept OOXML, which is falsely advertised as a case of opening up (realistically, more like broadening, as in ‘extending’ and moving goalposts).

Here begins the lesson on Embrace, Extend and Extinguish (EEE). Classically, this technique is used to perpetuate vendor lock-in by introducing small incompatibilities into a standard interface, in order to prevent effective interoperability, or (shudder) even substitutability of competing products based on that interface. This EEE strategy has worked well so far for Microsoft, with the web browser, with Java, with Kerberos, etc. It is interesting to note that this technique can work equally well with Microsoft’s own standards, like OOXML.

[...]

So, by failing to include this in their conformance clause, OOXML’s use of the term “implementation-defined” is toothless. It just means “We don’t want to tell you this information” or “We don’t want to interoperate”. Conformant applications are not required to actually document how they extend the standard. You can look at Microsoft Office 2007 as a prime example. Where is this documentation that explains how Office 2007 implements these “implementation-defined” features? How is interoperability promoted without this?

Groklaw has some good articles covering “Embrace, Extend, Extinguish”, so you are encouraged to read older stories such as this one.

You’ll hear some emails read aloud, one of Bill Gates’s, an email from 1996 about Java, where he says he was losing sleep over how great Java was, and you’ll see a strategy he suggested — “fully supporting Java and extending it in a Windows/Microsoft way”.

[...]

Well, when applets are cross-platform, it expands the number of applications that are available to you so you can go to a website. And if you have a Linux computer or a Macintosh computer or a Windows 3.1 computer, you can get an application and it will run.

You don’t have to either select a specific application or hope that the independent software vendor or the website created the application for your platform. So it would increase the number of applications available to you.

This one is good also:

“Ronald Alepin, an independent consultant and former CTO for Fujitsu, disputed the idea that Microsoft had been an innovator in the field. He said that interoperability protocols were developed by companies other than Microsoft, and that Microsoft has simply extended the protocols and then refused to disclose the extensions. In so doing, he told the court, Microsoft “has hijacked standard interoperability protocols agreed by the entire industry.”

As the previous post from an anonymised contributor insists, it is very unlikely that Microsoft has changed its ways (nor that it ever will). It’s the same old tricks, with the addition of software patents. in a disguise named “open”, or “interop”. And there is always some invasive Microsoft agent who tries to sell this to us.

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New


  1. IRC Proceedings: Tuesday, January 31, 2023

    IRC logs for Tuesday, January 31, 2023



  2. Links 31/01/2023: Catchup Again, Wayland in Xfce 4.20

    Links for the day



  3. Links 31/01/2023: elementary OS 7

    Links for the day



  4. Intimidation Against Nitrux Development Team Upsets the Community and Makes the Media Less Trustworthy

    Nitrux is being criticised for being “very unappealing”; but a look behind the scenes reveals an angry reviewer (habitual mouthpiece of the Linux Foundation and Linux foes) trying to intimidate Nitrux developers, who are unpaid volunteers rather than “corporate” developers



  5. Links 31/01/2023: GNOME 44 Wallpapers and Alpha

    Links for the day



  6. Free and Open Source Software Developers' European Meeting (FOSDEM) and KU Leuven Boosting Americans and Cancellers of the Father of Free Software

    The Free Software Foundation (FSF) and its founder, Richard M. Stallman (RMS), along with the SFLC one might add, have been under a siege by the trademark-abusing FSFE and SFC; Belgium helps legitimise the ‘fakes’



  7. Techrights in the Next 5 or 10 Years

    Now that I’m free from the shackles of a company (it deteriorated a lot after grabbing Gates Foundation money under an NDA) the site Techrights can flourish and become more active



  8. 60 Days of Articles About Sirius 'Open Source' and the Long Road Ahead

    The Sirius ‘Open Source’ series ended after 60 days (parts published every day except the day my SSD died completely and very suddenly); the video above explains what’s to come and what lessons can be learned from the 21-year collective experience (my wife and I; work periods combined) in a company that still claims, in vain, to be “Open Source”



  9. IRC Proceedings: Monday, January 30, 2023

    IRC logs for Monday, January 30, 2023



  10. Taking Techrights to the Next Level in 2023

    I've reached a state of "closure" when it comes to my employer (almost 12 years for me, 9+ years for my wife); expect Techrights to become more active than ever before and belatedly publish important articles, based on longstanding investigations that take a lot of effort



  11. The ISO Delusion: When the Employer Doesn’t Realise That Outsourcing Clients' Passwords to LassPass After Security Breaches Is a Terrible Idea

    The mentality or the general mindset at Sirius ‘Open Source’ was not compatible with that of security conscientiousness and it seemed abundantly clear that paper mills (e.g. ISO certification) cannot compensate for that



  12. Links 30/01/2023: Plasma Mobile 23.01 and GNU Taler 0.9.1

    Links for the day



  13. EPO Management Isn't Listening to Staff, It's Just Trying to Divide and Demoralise the Staff Instead

    “On 18 January 2023,” the staff representatives tell European Patent Office (EPO) colleagues, “the staff representation met with the administration in a Working Group on the project “Bringing Teams Together”. It was the first meeting since the departure of PD General Administration and the radical changes made to the project. We voiced the major concerns of staff, the organization chaos and unrest caused by the project among teams and made concrete proposals.”



  14. Links 30/01/2023: Coreboot 4.19 and Budgie 10.7

    Links for the day



  15. IRC Proceedings: Sunday, January 29, 2023

    IRC logs for Sunday, January 29, 2023



  16. [Meme] With Superheroes Like These...

    Ever since the new managers arrived the talent has fled the company that falsely credits itself with "Open Source"



  17. Not Tolerating Proprietary 'Bossware' in the Workplace (or at Home in Case of Work-From-Home)

    The company known as Sirius ‘Open Source’ generally rejected… Open Source. Today’s focus was the migration to Slack.



  18. The ISO Delusion: A Stack of Proprietary Junk (Slack) Failing Miserably

    When the company where I worked for nearly 12 years spoke of pragmatism it was merely making excuses to adopt proprietary software at the expense of already-working and functional Free software



  19. Debian 11 on My Main Rig: So Far Mostly OK, But Missing Some Software From Debian 10

    Distributions of GNU/Linux keep urging us to move to the latest, but is the latest always the greatest? On Friday my Debian 10 drive died, so I started moving to Debian 11 on a new drive and here's what that did to my life.



  20. Stigmatising GNU/Linux for Not Withstanding Hardware Failures

    Nowadays "the news" is polluted with a lot of GNU/Linux-hostile nonsense; like with patents, the signal-to-noise ratio is appalling and here we deal with a poor 'report' about "Linux servers" failing to work



  21. Microsofters Inside Sirius 'Open Source'

    Sirius ‘Open Source’ has been employing incompetent managers for years — a sentiment shared among colleagues by the way; today we examine some glaring examples with redacted communications to prove it



  22. Links 29/01/2023: GNOME 43.3 Fixes and Lots About Games

    Links for the day



  23. The Hey Hype Machine

    "Hey Hype" or "Hey Hi" (AI) has been dominating the press lately and a lot of that seems to boil down to paid-for marketing; we need to understand what's truly going on and not be distracted by the substance-less hype



  24. IRC Proceedings: Saturday, January 28, 2023

    IRC logs for Saturday, January 28, 2023



  25. Unmasking AI

    A guest article by Andy Farnell



  26. The ISO Delusion/Sirius Corporation: A 'Tech' Company Run by Non-Technical People

    Sirius ‘Open Source’ was hiring people who brought to the company a culture of redundant tasks and unwanted, even hostile technology; today we continue to tell the story of a company run by the CEO whose friends and acquaintances did severe damage



  27. Links 28/01/2023: Lots of Catching Up (Had Hardware Crash)

    Links for the day



  28. IRC Proceedings: Friday, January 27, 2023

    IRC logs for Friday, January 27, 2023



  29. Microsoft DuckDuckGo Falls to Lowest Share in 2 Years After Being Widely Exposed as Microsoft Proxy, Fake 'Privacy'

    DuckDuckGo, according to this latest data from Statcounter, fell from about 0.71% to just 0.58%; all the gains have been lost amid scandals, such as widespread realisation that DuckDuckGo is a Microsoft informant, curated by Microsoft and hosted by Microsoft (Bing is meanwhile laying off many people, but the media isn’t covering that or barely bothers)



  30. This is What the Microsoft-Sponsored Media Has Been Hyping Up for Weeks (Ahead of Microsoft Layoffs)

    Reprinted with permission from Ryan


RSS 64x64RSS Feed: subscribe to the RSS feed for regular updates

Home iconSite Wiki: You can improve this site by helping the extension of the site's content

Home iconSite Home: Background about the site and some key features in the front page

Chat iconIRC Channel: Come and chat with us in real time

Recent Posts