02.19.08

Gemini version available ♊︎

Site Reader Explains Why Microsoft Released Its Office Binary Formats Specifications

Posted in Deception, Formats, Linspire, Microsoft, Novell, Office Suites, Patents, Red Hat, Turbolinux, Ubuntu, Xandros at 8:17 am by Dr. Roy Schestowitz

An anonymous reader has contributed his insights for us to publish in the spirit of helping the fight against FUD.

So, what do we have here? A new maneouver of the monopoly: Now they publish the specifications of legacy (97,2000) Microsoft Office documents (they arrive 10 years late). Now that thanks to ODF we are on the verge of not needing them anymore. Ever.

Timeo Danaos et dona ferentes.” Fear the Greeks even if they bear gifts. This is absolutely a “Trojan horse” (poison pill) for Free/Libre Software. Let me explain:

There is an absolutely critical question for Free/Libre Software (and, by the way, if you must pay/negotiate patent racket eer… royalties as Novell has agreed to do, it cannot be deemed Free/Libre anymore)

Are these formats freely implementable in projects licensed under the GPLv3 (and notice that version 3 here acquires a crucial importance)? Are they available absolutely royalty-free and absolutely software patents-free? If that is not the case this is plain yet-another-trap-from-Microsoft(tm).

Moreover the specs are published at a critical moment when Microsoft desperately needs to see endorsed by ISO its Frankenstein-Format MSOOXML (which includes undocumented binary blobs, at least undocumented until now, -and it remains to be seen if the documentation just published is useful with them at all-) after they have corrupted the whole standarization process by playing every little dirty trick in the book to rig the Technical Committees in order to see their format approved.

***Why NOW?, I am sure things would have been a lot EASIER for them should they have published the specs from the beginning… ah, but then the very format’s “Raison d’etre”, i.e. LEGACY COMPATIBILITY MOTIVATION THEY JUSTIFIED FOR THE EXISTENCE A SECOND UNNECESSARY ISO STANDARD FOR DOCUMENT FORMATS, AN “ISOED”-MSOOXML CONFLICTING WITH THE EXISTING ODF-IETF/ISO26300 WOULD NOT BE VALID ANYMORE: IN FACT NOW THAT THEY HAVE PUBLISHED THE LEGACY SPECS IT IS NOT VALID ANYMORE***

“They desperately need to stop the adoption of ISO26300-ODF by governments and public institutions…”They desperately need to stop the adoption of ISO26300-ODF by governments and public institutions, which, by the way, are probably the biggest captive customers and Cash-Cows of Microsoft (there are already some precedents that should have made them scared to death, like in Massachusetts)

They have said that they “cannot guarantee” legal safety if you use their OSP-published products in a GPL Free/Libre project [ODF], and that they leave the question to be asked “to your lawyers”, what a superb exercise of cynicism! (OSP=”Open Specification Promise”, notice this is a “promise” -and, as such, coming from Microsoft, bound to be broken-, OSP is not a licence nor a contract, and it is not legally binding whatsoever)

GNU logoWhat they have made clear is that, even if ISO endorses their MSOOXML format, they are not committed with it in future versions (we will see EEE at play again). The documentation of this attempt-at-a-standard already comprises 6000+ pages of specifications plus more that 2000 extra pages of errors and suggested amendments.

Be very aware, that when talking about Microsoft you always have to look for “side effects” and “collateral damages”.

In this case I can see a two-pronged attack to Open Standards and Free/Libre Software. For the first, as I have explained, they are trying to discourage ODF adoption as much as they can. For the second, think about the consequences of injecting their OSP’ed products -not-quite-GPL-compatible-and-of-course-GPLv3-incompatible- (since you cannot pass the rights to the recipients of the software -and that’s why they love the BSD-like licenses while they shun the GPL-like licences), I say, injecting them in some Gnu/Linux distro: Novell (Xandros, Linspire, Turbolinux) is a first candidate, whereas for Red Hat, Ubuntu, Mandriva, Debian, Slackware and others… have you paid our patent protection racket yet? No? Well, see you in court.

There is a premise with this company (Microsoft) and it is that any of their products -even those provided cost-free- are devised to try to tie you to some other of their products.

To finish with, the published specs don’t include either Access, Visio or Outlook. And ironically, they are published in .PDF and .XPS (“metro”) formats (so beware, Adobe!)

Also see: http://fsfeurope.org/documents/msooxml-idiosyncrasies

This illustrates the impossibility of obtaining interoperability with real implementations of MSOOXML by Microsoft even after (and if) endorsed by ISO.

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.

4 Comments

  1. Sam Hiser said,

    February 19, 2008 at 11:38 am

    Gravatar

    Roy -

    Looks like Microsoft took my June 2007 advice …

    Microsoft’s Legacy Binary Formats
    http://fussnotes.typepad.com/plexnex/2007/06/microsofts-lega.html

    And the world has picked up on my Jan 2007 analysis …

    Analyzing the Microsoft Office Open XML License
    http://fussnotes.typepad.com/plexnex/2007/01/analyzing_the_m.html

    If I’m right on this, how can you doubt the veracity & validity of my interest in CDF?

  2. Roy Schestowitz said,

    February 19, 2008 at 11:51 am

    Gravatar

    Looks like Microsoft took my June 2007 advice …

    Yes, I think I pointed this out before (here or elsewhere).

    If I’m right on this, how can you doubt the veracity & validity of my interest in CDF?

    We have been through this before.

  3. Stephane Rodriguez said,

    February 19, 2008 at 2:25 pm

    Gravatar

    Roy,

    The problem is that there is material for a post, but not with the content you have posted. There is a number of innacuracies.

    The documents that Microsoft has made available through direct download were available FOREVER by sending an email at officeff@microsoft.com

    The timing is certainly suspect, and you can certainly view it as a way to provoke a strong positive reaction from national bodies later this month (many of which may not be up-to-date on the subject, thus easily subverted) . But, as a matter of fact, experts in national bodies know what is new, and what isn’t.

    I have posted elsewhere that those documents are incomplete. So from a strict point of view of interoperability, Microsoft is not giving access to a finished work. In fact, I believe these are the documents that they use internally, which is handy when you are taking a look at the source code.

    The problem is, of course, that only they have the source code.

    And that’s what brings me to the only solution to the interoperability issue. You know Microsoft is starting a bogus “translator” open source project that will never get finished. This and the documents are in fact a way to avoid giving access to the source code of the Office compatibility pack, a component they ship to convert formats back and forth.

    It’s key to understand that this compatibility pack includes everything we need, including the undocumented details. It remains purely document-centric, Microsoft keeps a hold on the application-level (the compatibility pack has no UI).

    Microsoft should give access to the source code of the compatibility pack.

    Anything else is just noise.

  4. Roy Schestowitz said,

    February 19, 2008 at 6:18 pm

    Gravatar

    At the end of the day, they need to control the ‘standard’. That’s just what they say and they are unlikely to give it away to ensure 100% fidelity in translation (impossibility given dependence on a platform). As long as you know fidelity is poor, there’s that FUD you get whenever you move away from Microsoft Office (“OMG. I lost something. Silently!”).

DecorWhat Else is New


  1. 2023 is the Year Taxpayers' Money Goes to War and Energy Subsidies, Not Tech

    Now that a lot of powerful and omnipresent ‘tech’ (spying and policing) companies are rotting away we have golden opportunities to bring about positive change and maybe even recruit technical people for good causes



  2. Getting Back to Productive Computer Systems Would Benefit Public Health and Not Just Boost Productivity

    “Smartphoneshame” (shaming an unhealthy culture of obsession with “apps”) would potentially bring about a better, more sociable society with fewer mental health crises and higher productivity levels



  3. Links 04/02/2023: This Week in KDE and Many More Tech Layoffs

    Links for the day



  4. Dotcom Boom and Bust, Round 2

    The age of technology giants/monopolies devouring everything or military-funded (i.e. taxpayers-subsidised) surveillance/censorship tentacles, in effect privatised eyes of the state, may be ending; the United States can barely sustain that anymore and raising the debt ceiling won't solve that (buying time isn't the solution)



  5. Society Would Benefit From a Smartphoneshame Movement

    In a society plagued by blackmail, surveillance and frivolous lawsuits it is important to reconsider the notion of “smart” phone ownership; these devices give potentially authoritarian companies and governments far too much power over people (in the EU they want to introduce new legislation that would, in effect, ban Free software if it enables true privacy)



  6. IRC Proceedings: Friday, February 03, 2023

    IRC logs for Friday, February 03, 2023



  7. IRC Proceedings: Thursday, February 02, 2023

    IRC logs for Thursday, February 02, 2023



  8. Links 03/02/2023: Proton 7.0-6 Released, ScummVM 2.7 Testing

    Links for the day



  9. Links 03/02/2023: OpenSSH 9.2 and OBS Studio 29.0.1

    Links for the day



  10. Links 03/02/2023: GNU C Library 2.37

    Links for the day



  11. Sirius Finished

    Yesterday I was sent a letter approving my resignation from Sirius ‘Open Source’, two months after I had already announced that I was resigning with immediate effect; they sent an identical letter to my wife (this time, unlike before, they remembered to also change the names!!)



  12. The Collapse of Sirius in a Nutshell: How to Identify the Symptoms and Decide When to Leave

    Sirius is finished, but it's important to share the lessons learned with other people; there might be other "pretenders" out there and they need to be abandoned



  13. Links 03/02/2023: WINE 8.1 and RapidDisk 9.0.0

    Links for the day



  14. Links 02/02/2023: KDE Gear 22.12.2 and LibreOffice 7.5

    Links for the day



  15. Linux News or Marketing Platform?

    Ads everywhere: Phoronix puts them at the top, bottom, navigation bar, left, and right just to read some Microsoft junk (puff pieces about something that nobody other than Microsoft even uses); in addition there are pop-ups asking for consent to send visitors’ data to hundreds of data brokers



  16. Daily Links at Techrights Turn 15, Time to Give Them an Upgrade

    This year we have several 15-year anniversaries; one of them is Daily Links (it turned 15 earlier this week) and we've been working to improve these batches of links, making them a lot more extensive and somewhat better structured/clustered



  17. Back to Focusing on Unified Patent Court (UPC) Crimes and Illegal Patent Agenda, Including the EPO's

    The EPO's (European Patent Office, Europe's second-largest institution) violations of constitutions, laws and so on merit more coverage, seeing that what's left of the "media" not only fails to cover scandalous things but is actively cheering for criminals (in exchange for money)



  18. European Patent Office Staff Votes in Favour of Freedom of Association (97% of Voters in Support)

    The Central Staff Committee (CSC) at the EPO makes a strong case for António Campinos to stop breaking and law and actually start obeying court orders (he’s no better than Benoît Battistelli and he uses worse language already)



  19. Links 02/02/2023: Glibc 2.37 and Go 1.20

    Links for the day



  20. IRC Proceedings: Wednesday, February 01, 2023

    IRC logs for Wednesday, February 01, 2023



  21. Links 01/02/2023: Security Problems, Unrest, and More

    Links for the day



  22. Links 01/02/2023: Stables Kernels and Upcoming COSMIC From System76

    Links for the day



  23. IRC Proceedings: Tuesday, January 31, 2023

    IRC logs for Tuesday, January 31, 2023



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

    Links for the day



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

    Links for the day



  26. 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



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

    Links for the day



  28. 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’



  29. 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



  30. 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”


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