08.05.08

Reminder: OOXML Still Seems Free Software-Hostile

Posted in Free/Libre Software, FSF, GPL, ISO, Law, Microsoft, Open XML at 9:31 am by Dr. Roy Schestowitz

flickr:2400865918

Several months ago, thanks to the SFLC it was shown that OOXML is not suitable for implementation by Microsoft's #1 competitor. A solicitor specialising in Free/open source software, Brendan Scott, has taken a look at Microsoft’s reassurances and formal licence, but he is not convinced much has changed. Loose ends remain in the OOXML OSP.

One of the reasons that the GPL ignorance line was trotted out for so long might have been concern over the the SFLC’s criticism of the OSP. To put it in simple terms, the OSP does not travel with the code. So writing a (eg) GPL* implementation of an OSP covered specification in the expectation that the code may be re-used for other things (which is a cornerstone of interactions in the free software community) creates a problem. That code becomes encumbered by a patent mine which arms itself when the code is (non-conformingly) reused. At best, even with this addition to the FAQ, the OSP still fails to respect the freedom of free software implementations (whether GPL or otherwise) of covered specifications.** It is unclear, for example, what effect the “no surrender of others’ freedom” clauses of the relevant GPLs would be in the event of a successful patent action against a non-conforming implementation.

Here is another good article about bad OOXML. The headline, which poses a question, is overly optimistic, but the body is a concise and accurate summary of recent developments.

Is Microsoft’s Office Open XML a functional standard, and if not, why is it being rushed through the process?

Microsoft’s problems with OOXML just won’t go away. MS-OOXML was supposed to supplant the Open Document Format (ODF), but is becoming an embarrassment. As a format it betrays its hurried origins, and is over-complex. At best, it has technical problems. At worst, it is barely fit for purpose.

Questions are being asked in Europe about the way that Microsoft went about the standardisation process. At least four countries have succeeded in having their objections raised to the fast-tracking of OOXML through the International Standards Organisation (ISO), and as a consequence, the ISO has put the standard on hold, at least for the time being.

Microsoft has no date for implementing OOXML on its own platform, but has agreed to implement the rival ODF format on Microsoft Office. Microsoft has given its blessings to ODF by joining the OASIS committees, and to cap it all, a senior Microsoft spokesman has conceded that “ODF has clearly won”.

Clearly, there is a pressing need for an open standard for document formats. Documents that can be shared across platforms, across products, and across time. The solution to the problem is ODF, which was created by a technical committee of the OASIS industry consortium and has benefited from industry wide participation in its development. ODF gained acceptance as an ISO standard in May 2006.

Some time this month, having already coped with leaks, ISO will probably confirm that it has lost its dignity by permitting itself to be exploited by Microsoft for self benefit.

ISO Sold Out to ECMA

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

If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

Pages that cross-reference this one

5 Comments

  1. Jose_X said,

    August 5, 2008 at 10:36 pm

    Gravatar

    OOXML is such a waste of time. Anything anyone wants can be done with some other formats. [Eg, extend ODF and then submit the extensions to OASIS for standardization; use the ODF TC mailing list. This is MUCH more efficient than reimplementing a different looking set of (crooked) wheels.]

    [In addition to the patent issue described in this article/post above..] We know the technical mess and reinvention of the wheel that is OOXML, but as concerns patents, real patent traps will lie with MS-OOXML, and since this will not be unextended correct OOXML (currently, “correct” is meaningless), you will have no patent protections if you actually reverse engineer MS-OOXML in order to interoperate. Of course, attempting to interoperate with MSO is an interminable rat race that starts you and keeps you permanently in the tail position of that race. [OOXML will give way to XOXOML (TM) and then to something else, etc, each of which will be based on the closed patented extensions from earlier generations.]

    The way forward should be to continue to grow an ecosystem of interoperable ODF (and other good standards) products. Good interesting products in large numbers that interoperate with each other NEED NOT interoperate specifically with MSO or other Monopolyware. If these products truly are good (many will be FOSS), consumers will see the value of moving over to these products. At some point they will know not to use MSO or will revert to older versions that can be understood mostly by Openoffice filters. Meanwhile antitrust authorities should force Monopolysoft to meet the ODF spec as much as possible. Us, rather than to go run Monopolysoft’s rat race, should instead complain to authorities about their brokenness.

    I think this is the smartest path forward. Recap: ignore OOXML and MSOOXML in order to save LOTS of time to be spent instead on ODF (in practice, Sun probably won’t do this, but it’s their business how they spend their bucks). Work aggressively to grow ODF apps and documents that interoperate. Sell ODF and the apps to people.

    Oh, and one more thing. OASIS should have an *official* path to determine if docs meet ODF requirements without the use of extensions. This way buyers can demand this. Otherwise, there will be confusion because today almost anything will qualify as an ODF conforming document (see ODF 1.1). You can’t separate the wheat from the chaff if you don’t have a trustworthy way to identify these parts.

    Good luck.

  2. Jose_X said,

    August 5, 2008 at 11:16 pm

    Gravatar

    I should have added to earlier comment that I think a lot of ODF proponents are (and have been) working with goals similar to what was described above. [Obviously, Novell is not one of these, as they insist on trying to legitimize OOXML and other technologies that put the ball in Monopolysoft's court. It's their time and Monopolysoft's dollar, so I guess that's their business.]

    An important situation with ODF extensions is how do you allow the positives of extensions while defending against the abuses of extensions? Some of the larger corp backers of ODF have leaned towards being lenient. This reminds me of ISO. It’s a bit informal among friends and everything mostly works until Monopolysoft shows up and exploits everything possible to game the system. Will we wait to toughen ODF until after Monopolysoft has done its number on it? Surely, they can and will extend ODF. This will create “ODF” files in large numbers that only work with MSO and those apps that license MSO libraries. These numbers can be overwhelming and hence become the de facto ODF. All may work out, nevertheless, if the case is successfully made to antitrust authorities that the extension mechanisms are being leveraged illegally by Monopolysoft.

    We’ll see, but if ODF is not carefully worded ahead of time, we’ll hear the old “good for goose .. gander” song. It might be enough, however, to point out that Monopolysoft is neither a goose nor a gander but a monopolist. We’ll see.

  3. Roy Schestowitz said,

    August 5, 2008 at 11:51 pm

    Gravatar

    I should have added to earlier comment that I think a lot of ODF proponents are (and have been) working with goals similar to what was described above. [Obviously, Novell is not one of these, as they insist on trying to legitimize OOXML and other technologies that put the ball in Monopolysoft’s court. It’s their time and Monopolysoft’s dollar, so I guess that’s their business.]

    It’s unfortunate that Novell signed this deal in the first place. It supports OOXML because it has to. It’s a binding contract. In essence, Microsoft bought OOXML obedience from Novell.

  4. Stephane Rodriguez said,

    August 6, 2008 at 5:41 am

    Gravatar

    What is key is to ensure that ODF interoperates at the application level with as many applications as possible, including applications from Microsoft.

    Microsoft, on the other hand, is ensuring that not only it won’t work on application-level interoperability regarding ODF, but also according to reports from their “ODF workshop” they held in Redmond last week, they are botching an ODF implementation to ensure everyone touching it will have a miserable life. Two examples : 1) they remove formulas from spreadsheets. I wonder how good is a spreadsheet without its formulas. 2) they add many dialog boxes to warn or ask the user, making reading/writing ODF extremely painful for users.

    This is all written on the wall already.

  5. Roy Schestowitz said,

    August 6, 2008 at 5:53 am

    Gravatar

    They only need the “supports ODF” footnote (no matter the quality and version… 1.0) on the box and brochure. They make it harder for technical people to justify defection away from MSO.

What Else is New


  1. IRC Proceedings: Sunday, January 17, 2021

    IRC logs for Sunday, January 17, 2021



  2. The Oligarchs' Parties Will Never Choose the Side of Software Freedom Because Free Software Cannot Bribe Officials

    The tough reality is that next week's (or this coming week's, depending on what Sunday counts as) inauguration ceremony is partly symbolic as all the same and important issues remain largely untouched, for corporations control almost everything of significance



  3. COVID-19 Has Actually Helped Software Freedom Due to Financial and 'Spare Time' Factors

    Developers and users are increasingly exploring what the Free software world has to offer; this is actually measurable and it contradicts claims to the contrary



  4. Future Plans and Using Videos to Complement Text

    Remarks on recent and impending site changes; We are not replacing text with video, we're just trying to enhance the presentation a bit, especially where visuals help make a point or where browsing through Web sites (or leaks) is more suitable than static, linear presentation



  5. InteLeaks – Part XVIII: Intel Does Not Know How to Properly Do Research and It Seems Apparent Unscientific Methods Are Used to Justify Poor Documentation

    There appears to be a severe crisis at Intel; they cannot recruit scientists (or those whom they recruited are walking away) and as a result the company produces bad products with poor documentation (or highly defective chipsets that top-notch marketing cannot compensate for); in this video we walk through some examples of how studies are being conducted (as already noted in Part XVII)



  6. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part III: The Free Software Foundation (FSF) Seems More Like a Victim of Destabilisation Campaigns

    The Free Software Foundation (FSF), which turns 36 later this year, is looking to raise money that helps support the GNU Project, soon 38 years old and likely the most important Free software project to exist (ever)



  7. Links 17/1/2021: EasyOS on Raspberry Pi and GNU libsigsegv 2.13

    Links for the day



  8. InteLeaks – Part XVII: The High Cost of Microsoft Windows Users in GNU/Linux Development Teams

    A look inside Intel explains what holds back the technical team, which bemoans the lesser technical people getting in the way and not even using the product that they are writing about



  9. IRC Proceedings: Saturday, January 16, 2021

    IRC logs for Saturday, January 16, 2021



  10. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part II: Why Bradley Kuhn Left the Free Software Foundation (FSF)

    The founder of the FSF is still at the FSF (albeit not publicly) and the person who lobbied to oust him has basically been 'banished' by the founder



  11. Links 16/1/2021: LibreOffice 7.1 Release Candidate, Zeroshell 3.9.5, FreeBSD Report, and GhostBSD 21.01.15

    Links for the day



  12. Free Speech on the Web Not Respected by Companies That Used to Support Software Freedom

    Mozilla does not have to make its Web browser about politics; it can just make an excellent piece of software that is neutral about the Web pages that it renders, based on the user's personal preferences



  13. Suppressed Facts of the Free Software Movement and Its Community of Volunteers – Part I: We Are Under Attack by Corporations and Their Salaried Facilitators

    The corporate takeover (taking over the Commons, produced by volunteers who are motivated by altruism) is a subject we must speak about and somehow tackle; this series will highlight uncomfortable or difficult truths



  14. InteLeaks – Part XVI: Intel Cannot Do Command Line, Even When It's Vastly Simpler and More Suitable for Development

    The Developer eXperience (DX) team at Intel seems to be full of Microsoft drones instead of developers and/or mildly technical people; this has not only harmed the quality of documentation but also upset staff, alienating people who actually understand what developers need (more than buzzwords like "DX")



  15. IRC Proceedings: Friday, January 15, 2021

    IRC logs for Friday, January 15, 2021



  16. Links 15/1/2021: KaOS 2021.01, Whisker Menu 2.5.2, Istio 1.8.2

    Links for the day



  17. InteLeaks – Part XV: Intel is Blind to Blind and Colour-Blind People

    Intel does not seem to grasp very basic concepts associated with accessibility; nevertheless, Intel shamelessly tries painting itself as "woke" and a "justice warrior" (policing speech while overlooking much-needed practical work)



  18. Links 15/1/2021: GStreamer 1.18.3 and Proton 5.13-5

    Links for the day



  19. IRC Proceedings: Thursday, January 14, 2021

    IRC logs for Thursday, January 14, 2021



  20. Links 14/1/2021: Wine 6.0, Debian 11 Freeze, and Alpine Linux 3.13

    Links for the day



  21. Patent Propaganda and UPC Jingoism Instead of Actual News

    Today's so-called 'news' about the EPO (Europe's second-largest institution) and the failed UPC is nothing short of shameless propaganda



  22. Links 14/1/2021: Season of KDE 2021 Selection, Mesa 21.0.0-RC1, Tor Browser 10.0.8

    Links for the day



  23. InteLeaks – Part XIV: Technical Incompetence and Incoherence Leading to Alienation and Brain Drain

    The idea that Intel "loves Linux" or "supports Linux" is somewhat of a sham; one needs only to consider what Intel insiders are saying about that, having witnessed it firsthand



  24. IRC Proceedings: Wednesday, January 13, 2021

    IRC logs for Wednesday, January 13, 2021



  25. Links 13/1/2021: $150 RISC-V Computer With GNU/Linux, Intel Replaces CEO Again, and New Fedora 34 Plans

    Links for the day



  26. Unitary Patent is Dead and Lies About the Unified Patent Court (UPC) Aren't Ending

    Not "Russian agents" but concerned European citizens are beginning to see the truth behind the Unified Patent Court, which the 'media' has wrongly called "Unitary Patent Court" three times in 2 days



  27. InteLeaks – Part XIII: GNU/Linux Documentation From People Who Never Even Use GNU/Linux

    Inside Intel there's a whole bunch of embarrassing secrets about the Developer/Development eXperience ("DX") team; no wonder documentation efforts have been lacking and far too much time wasted putting such documentation together



  28. Links 13/1/2021: Mozilla VPN, NeoChat 1.0.1 and Sci-Hub Under Attack

    Links for the day



  29. IRC Proceedings: Tuesday, January 12, 2021

    IRC logs for Tuesday, January 12, 2021



  30. GNOME Foundation is Still Participating in the Attack on Richard Stallman

    GNOME's supposed 'representatives' (close-knit friends with Microsoft connections) continue to attack RMS (Richard Stallman), the founder of GNU (the G in GNOME) and the Free Software Movement


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