08.05.08

Gemini version available ♊︎

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

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.

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.

DecorWhat Else is New


  1. Links 22/10/2021: Global Encryption Day

    Links for the day



  2. [Meme] Speaking the Same Language

    Language inside the EPO is misleading. Francophones Benoît Battistelli and António Campinos casually misuse the word “social”.



  3. António Campinos Thinks Salary Reductions Months Before He Leaves is “Exceptional Social Gesture”

    Just as Benoît Battistelli had a profound misunderstanding of the concept of “social democracy” his mate seems to completely misunderstand what a “social gesture” is (should have asked his father)



  4. IRC Proceedings: Thursday, October 21, 2021

    IRC logs for Thursday, October 21, 2021



  5. Links 21/10/2021: MX Linux 21 and Git Contributors’ Summit in a Nutshell

    Links for the day



  6. [Meme] [Teaser] Miguel de Icaza on CEO of Microsoft GitHub

    Our ongoing series, which is very long, will shed much-needed light on GitHub and its goals (the dark side is a lot darker than people care to realise)



  7. Gemini Protocol and Gemini Space Are Not a Niche; for Techrights, Gemini Means Half a Million Page Requests a Month

    Techrights on gemini:// has become very big and we’ll soon regenerate all the pages (about 37,500 of them) to improve clarity, consistency, and general integrity



  8. 'Satellite States' of EPO Autocrats

    Today we look more closely at how Baltic states were rendered 'voting fodder' by large European states, looking to rubber-stamp new and oppressive measures which disempower the masses



  9. [Meme] Don't Mention 'Brexit' to Team UPC

    It seems perfectly clear that UPC cannot start, contrary to what the EPO‘s António Campinos told the Council last week (lying, as usual) and what the EPO insinuates in Twitter; in fact, a legal challenge to this should be almost trivial



  10. The EPO’s Overseer/Overseen Collusion — Part IXX: The Baltic States

    How unlawful EPO rules were unsurprisingly supported by Benoît Battistelli‘s friends in Baltic states; António Campinos maintained those same unlawful rules and Baltic connections, in effect liaising with offices known for their corruption (convicted officials, too; they did not have diplomatic immunity, unlike Battistelli and Campinos)



  11. Links 21/10/2021: GIMP 2.99.8 Released, Hardware Shortages, Mozilla Crisis

    Links for the day



  12. How Oppressive Governments and Web Monopolists Might Try to Discourage Adoption of Internet Protocols Like Gemini

    Popular movements and even some courageous publications have long been subverted by demonisation tactics, splits along unrelated grounds (such as controversial politics) and — failing that — technical sabotage and censorship; one must familiarise oneself with commonly-recurring themes of social control by altercation



  13. [Meme] Strike Triangulations, Reception Issues

    Financial strangulations for Benoît Battistelli‘s unlawful “Strike Regulations”? The EPO will come to regret 2013…



  14. [Meme] Is Saying “No!” to Unlawful Proposals Considered “Impolite”?

    A ‘toxic mix’ of enablers and cowards (who won’t vote negatively on EPO proposals which they know to be unlawful) can serve to show that the EPO isn’t a “social democracy” as Benoît Battistelli liked to call it; it’s just a dictatorship, currently run by the son of a person who actually fought dictatorship



  15. IRC Proceedings: Wednesday, October 20, 2021

    IRC logs for Wednesday, October 20, 2021



  16. [Meme] EPO Legal Sophistry and Double Dipping

    An imaginary EPO intercept of Administrative Council discussions in June 2013...



  17. Links 21/10/2021: PostgreSQL JDBC 42.3.0 and Maui Report

    Links for the day



  18. [Meme] [Teaser] “Judge a Person Both by His Friends and Enemies”

    Fervent supporters of Team Battistelli or Team Campinos (a dark EPO era) are showing their allegiances; WIPO and EPO have abused staff similarly over the past decade or so



  19. 'Cluster-Voting' in the European Patent Office/Organisation (When a Country With 1.9 Million Citizens Has the Same Voting Power as a Country With 83.1 Million Citizens)

    Today we examine who has been running the Finnish patent office and has moreover voted in the EPO during the ballot on unlawful "Strike Regulations"; they voted in favour of manifestly illegal rules and for 8.5 years after that (including last Wednesday) they continued to back a shady regime which undermines the EPO's mission statement



  20. The EPO’s Overseer/Overseen Collusion — Part XVIII: Helsinki's Accord

    The Finnish outpost has long been strategic to the EPO because it can help control the vote of four or more nations; evidence suggests this has not changed



  21. [Meme] Living as a Human Resource, Working for Despots

    The EPO has become a truly awful place/employer to work for; salary is 2,000 euros for some (despite workplace stress, sometimes relocation to a foreign country)



  22. Links 20/10/2021: New Redcore Linux and Hospital Adoption of GNU Health

    Links for the day



  23. IRC Proceedings: Tuesday, October 19, 2021

    IRC logs for Tuesday, October 19, 2021



  24. Links 19/10/2021: Karanbir Singh Leaves CentOS Board, GPL Violations at Vizio

    Links for the day



  25. [Meme] Giving the Knee

    The 'knee' champion Kratochvìl and 'kneel' champion Erlingsdóttir are simply crushing the law; they’re ignoring the trouble of EPO staff and abuses of the Office, facilitated by the Council itself (i.e. facilitated by themselves)



  26. Josef Kratochvìl Rewarded Again for Covering Up EPO Corruption and the EPO Bribes the Press for Lies Whilst Also Lying About Its Colossal Privacy Violations

    Corrupt officials and officials who actively enable the crimes still control the Office and also the body which was supposed to oversee it; it's pretty evident and clear judging by this week's press statements at the EPO's official Web site



  27. [Meme] Sorry, Wrong Country (Or: Slovenia isn't Great Britain)

    Team UPC is trying to go ahead with a total hoax which a high-level European court would certainly put an end to (if or when a referral is initiated)



  28. How Denmark, Iceland, Finland, Norway and Sweden Voted on Patently Unlawful Regulations at the EPO

    We look back and examine what happened 8 years ago when oppressed staff was subjected to unlawful new “regulations” (long enjoyed by António Campinos, the current EPO autocrat)



  29. The EPO’s Overseer/Overseen Collusion — Part XVII: The Non-Monolithic Nordic Bloc

    We start our investigation of how countries in northern Europe ended up voting on the unlawful “Strike Regulations” at the EPO and why



  30. Proof That Windows “11” is a Hoax

    Guest post by Ryan, reprinted with permission


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