EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

11.26.07

One Life, One App (Corrected)

Posted in Formats, GNOME, GNU/Linux, Microsoft, Office Suites, Open XML, OpenDocument, Patents, Standard at 6:33 pm by Dr. Roy Schestowitz

Just 150 years to go. Just do it.

OOXML is a sensitive subject, but if issues are not raised out in the open, we are destined to be locked down in another digital dark age. Although one man has attempted to implement rudimentary OOXML support in Gnumeric, it is estimated that it would take 150 man years to implement OOXML as it stands at moment (incomplete).

…we’re now looking at 150 man years to do the job for a competitive PPA.

”In fact, not even Microsoft Office 2007 implements something which complies with the existing specification.“There is no source code available for reuse (Microsoft Office is purely closed-source and proprietary) and there is no proper reuse of existing standards (e.g. for dates) inside OOXML. Also remember that Microsoft admitted that it is not committed to sticking to its own specification (OOXML), which makes it a moving target. In fact, not even Microsoft Office 2007 implements something which complies with the existing specification. It’s merely a derivative which ensures no compatibility through a ‘golden’ reference (a written document, spread across over 6,000 pages). There are serious patent issues to consider, but sadly enough, no-one seems to notice.

I fail to see why Gnumeric has very, very basic support for OOXML while ODF support (the ISO standard) does not have any support yet. That’s just what I was told yesterday. Are non-standards given precedence over international and open standards, which are suddenly/temporarily worth neglecting? [Correction: ODF support is coming shortly. See comments below.] The following assessment seems unrealistic.

Among the many other topics discussed at Ontario LinuxFest was a completely objective comparison of Microsoft’s OOXML document standard and OpenOffice.org’s ODF document standard by Gnumeric maintainer Jody Goldberg, who has had to wade through both in depth. His summary is that OOXML is not the spawn of Satan, and ODF is not the epitome of perfection. Both have their strengths and weaknesses, and he sees no reason why we could not go forward with both standards in use.

See the aforementioned remarks about the complexity involved in implementing OOXML, which carries a patent burden and will probably be ignored by Microsoft, which will ‘extend’ things its own way in order to ensure obsolescence (forced upgrades) and poor compatibility with other applications (technical sabotage).

Share this post: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Digg
  • del.icio.us
  • Reddit
  • co.mments
  • DZone
  • email
  • Google Bookmarks
  • LinkedIn
  • NewsVine
  • Print
  • Technorati
  • TwitThis
  • Facebook

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

12 Comments

  1. Jody Goldberg said,

    November 26, 2007 at 11:03 pm

    Gravatar

    You have been mis-informed.
    Gnumeric 1.8.0 (due in a week or so) has reasonable ODF and MOOX import. Not quite as good as our xls import, but reasonable. Export is rougher for both formats, although MOOX holds the edge.

  2. Roy Schestowitz said,

    November 26, 2007 at 11:08 pm

    Gravatar

    Thanks, Jody. I’ll correct the text. My understanding was based on this information.

  3. Jody said,

    November 27, 2007 at 8:15 am

    Gravatar

    I should have been clearer.

    Gnumeric 1.6.x (the previous stable release) has had ODF import for years. It was not superb, there have been significant improvements since then, but it was enough for content, styles, and basic charting. What it lacked was export. 1.8 improves ODF import, and adds basic export. It also adds MOOX import at a level similar to ODF, and export that is somewhat better than ODF.

    The ’150 year’ number is unrealistic. The XLS filters in Gnumeric or OO.o provide a huge chunk of the functionality required to map MS data structures onto native content. Our MOOX filters represent days-weeks of part time work. I’d be generous and call it a month of evenings. ODF filters have taken longer because we need to write the mapping from scratch, and have larger differences from our feature set, requiring more complex translation.

    For 2.0 I plan to have both filters at the level of our xls support. While it is not 100% (no more than OO.o is) it seems to be ‘good enough’ for most use cases. Having actually worked with (and on) both formats I’m going to trust my judgment here rather than some talking point.

  4. Roy Schestowitz said,

    November 27, 2007 at 1:09 pm

    Gravatar

    Jody,

    The figure about the complexity and time of implementation was actually estimated by more than just this one site (the one which is cited). Be aware that there are undocumented bits too (yes, I know that you claimed on Slashdot that there are no proprietary extensions, but I beg to differ).

  5. Hefe said,

    November 27, 2007 at 1:59 pm

    Gravatar

    You beg to differ? What, may I ask, is your credibility to make such a claim? Jody Goldberg has at least read and understands both specs much better than pretty much anyone else out there in existence.

    Can you or anyone you’ve quoted who states “150 man-years” say the same? I doubt it.

    Perhaps the “expert” that quotes 150 man-years is a poor programmer with little-to-no experience actually implementing a spec?

    The funny thing about people who “beg to differ” with Jody is that when you compare credibility, it’s like night and day. You have Jody who is a very competent programmer who has 10ish+ years experience developing Office software and has read/contributed to both ODF/MOOX and you have Joe “Expert” who has 0 years experience implementing specs, 0 experience writing software (nevermind Office software), and hasn’t actually even bothered to read either spec, but instead relies on anonymous Slashdot comments for their “insight”.

    If it’s not clear who actually has a clue, it’s Jody.

  6. Roy Schestowitz said,

    November 27, 2007 at 2:08 pm

    Gravatar

    Hefe, from what I can gather, implementing something that corresponds to these 6,000+ pages is not sufficient for interoperability (and Microsoft too know it).

    The “Excel Macro-Enabled Workbook” option saves as an “xlsxm” extension. It is OOXML plus proprietary Microsoft extensions. These extensions, in the form of binary blob called vbaProject.bin, represent the source code of the macros. This part of the format is not described in the OOXML specification. It does not appear to be a compiled version of the macro. I could reload the document in Excel and restore the original text of my macro, including whitespace and comments. So source code appears to be stored, but in an opaque format that defied my attempts at deciphering it.

    (What’s so hard about storing a macro, guys? It’s frickin’ text. How could you you[sic] screw it up? )

    This has some interesting consequences. It is effectively a container for source code that not only requires Office to run it, but requires Office to even read it. So you could have your intellectual property in the form of extensive macros that you have written, and if Microsoft one day decides that your copy of Office is not “genuine” you could effectively be locked out of your own source code.

  7. 2234e534e4355t6546 said,

    November 27, 2007 at 5:40 pm

    Gravatar

    That’s pure humbug. If you embed a Windows Media stream into you website HTML doesn’t become proprietary from that.

    About topic that you don’t understand you should try to remain silent. You’re just an embarrassment for everyone who love Linux.

    Note: comment has been flagged for arriving from a known, pseudonymous, nymshifting, abusive Internet troll

  8. Jody said,

    November 27, 2007 at 8:05 pm

    Gravatar

    1) The 150 years is nonsense. OOXML is much easier than the old binary formats which have taken no more than 10 years for several implementations

    2) Ahhh, at last a binary blob that makes sense. I keep hearing about them, but have yet to actually see any mentioned in the spec, or in the sample files. Rob Weir and by proxy you, are at least partially correct. The macro streams do actually exist. There are however several caveats.

    a) The macro enabled formats are explicitly different formats than than stock OOXML, Moreover they are not the default formats.

    b) The binary blobs are in exactly the same format as the old binary formats. Michael and I cracked it a few years back (see libgsf, or OO.o). We can read and write it.

    This was raised in the TC as part of the review process. The explanation given was that the VBA engine was in deep freeze, pending a move to something else. It would certainly be good to get this fixed. It is of less utility than the rest of the content to anyone accept virus checkers given that it requires an MS Office api implementation to actually interpret (the same way OO.o macros require OO.o uno interfaces) but it should still be addressed.

    The reality of it is much smaller than the ominous clouds of ‘proprietary extension’ suggest. It is more an indication of the weakness of the MS Office code base, than of evil intent.

  9. Roy Schestowitz said,

    November 27, 2007 at 9:13 pm

    Gravatar

    1) The 150 years is nonsense. OOXML is much easier than the old binary formats which have taken no more than 10 years for several implementations

    This is news to me. Could you please show me one complete implementation of Microsoft Office formats? The latest OpenOffice.org, for example, is not compatible with Microsoft Office. For that reason, I never touch office suites (a shame really) and stick to something open — LaTeX.

    2) Ahhh, at last a binary blob that makes sense. I keep hearing about them, but have yet to actually see any mentioned in the spec, or in the sample files. Rob Weir and by proxy you, are at least partially correct. The macro streams do actually exist. There are however several caveats.

    a) The macro enabled formats are explicitly different formats than than stock OOXML, Moreover they are not the default formats.

    Could I prevent my colleagues from sending these? This is OOXML we’re talking about here. Is Microsoft hiding a parallel OOXML universe somewhere (like… say… ‘OOS (OOXML on Steroids)’)? If so, I do not want this thing approved by the ISO and the GNOME Foundation’s involvement has already done a lot of damage (see recent press coverage).

    b) The binary blobs are in exactly the same format as the old binary formats. Michael and I cracked it a few years back (see libgsf, or OO.o). We can read and write it.

    In other words, Microsoft wishes to standardrise legacy from its “old binary formats”. Wonderful.

    This was raised in the TC as part of the review process. The explanation given was that the VBA engine was in deep freeze, pending a move to something else. It would certainly be good to get this fixed. It is of less utility than the rest of the content to anyone accept virus checkers given that it requires an MS Office api implementation to actually interpret (the same way OO.o macros require OO.o uno interfaces) but it should still be addressed.

    I am absolutely stunned and unable to understand how you are willing to accept some of this and acknowledge that you hacked something which interprets binaries. With standardisation, you basically pass on the burden for other groups (say… Google Apps) to backward engineer binaries and reconstruct/mimic Microsoft APIs (never mind the patent implications of this)

    The reality of it is much smaller than the ominous clouds of ‘proprietary extension’ suggest. It is more an indication of the weakness of the MS Office code base, than of evil intent.

    So please reject it. Explain to people that OOXML has a binary ‘umbilical cord’. As it stands, your feedback in Slashdot denies this. This is what I call Microsoft-serving FUD. Sorry.

  10. Roy Schestowitz said,

    November 27, 2007 at 9:45 pm

    Gravatar

    Addenda:

    ODF vs OOX : Asking the wrong questions

    Lot of answers there. To quote one

    What Brian claimed is “very rich support”. He was lying, and he didn’t try it either. What Rob meant was that usually you want to show the most complex case you support, not something simple.

    Another one: (sorry, I just can’t help it and it’s hard to leave some out)

    Wow. That’s FANTASTIC! What a great endorsing for ooxml! You must try provide this comments to Microsoft so they can used them in the BRM meeting for ISO approval.

    Sam Hiser:

    Jody-

    Your self-annihilating devotion to Microsoft is too evident. Filtering will be unnecessary when an authentic Universal Document Format exists.

    Sadly ‘Interoperability’ — the word — is being worn out while there are no self-respecting efforts to do anything except control the data of customers.

    Shame on the business!

    Lots more at:

    http://holloway.co.nz/

    See:

    Microsoft and Open Standards

    Can Other Vendors Implement Microsoft’s Office Open XML?

    15 August 2007

    http://holloway.co.nz/can-other-vendors-implement-ooxml.html

    I love this one by the way (it shows the type of people who must be patting on the Foundation’s shoulder):

    http://holloway.co.nz/sincerity-generator/

    This source not an antagonist. It’s someone who is truly trying to help us getting rid of OOXML/.doc because they are both proprietary. They can only be controlled ans mastered by a single abusive company that will carry on moving the goalposts for profit.

    http://holloway.co.nz/docvert/

    There is a lot of information in these pages: http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C0

    This page is also good: http://www.freesoftwaremagazine.com/articles/odf_ooxml_technical_white_paper?page=0%2C8

  11. Jody Goldberg said,

    November 27, 2007 at 10:23 pm

    Gravatar

    My apologies for being polite and instructive. You’ve clearly made your choices. Best wishes in your echo chamber.

  12. Roy Schestowitz said,

    November 27, 2007 at 10:41 pm

    Gravatar

    I rest my case then.

What Else is New


  1. The Whitewashing of the EPO Under António Campinos

    The charm offensive of the 'new and improved' EPO President seems to mostly boil down to a PR campaign, as we expected all along



  2. Links 22/1/2019: Kodachi 5.8, LibreOffice 6.2 Finished

    Links for the day



  3. Software Patents Are a Dying Breed, So Marks & Clerk and Other Legal Monoliths Promote the EPO's Buzzwords (Loopholes)

    Patents that courts would almost certainly reject (and invalidate) are routinely promoted as "AI", "SDV" and similar acronyms and buzzwords, either misleading or intentionally misplaced (nowadays "AI" is often just a synonym for "machine" or "algorithm")



  4. A Fortnight After His Diplomatic Immunity Ends Outgoing EPO Vice-President Željko Topić is in Court in Zagreb, Croatia

    Court minutes for a Željko Topić case heard 5 days ago



  5. Links 20/1/2019: Exo 0.12.4 and Libhandy 0.0.7 Released

    Links for the day



  6. JUVE Creates English Site, Promotes Unified Patent Court (UPC)

    The generally good press outlet has taken a turn for the worse; it looks like it's doing more lobbying than reporting nowadays



  7. The Indian Ministry of Commerce Tries to Bend Patent Law in Favour of Foreign Monopolies

    There's an attempt to tilt patent law against the interests of India; but vigilant few are observing and reporting it, even in English



  8. The EFF Must Return That 'Internship' Money to Google or It Would Disgrace the Patent Reform Movement (by Association)

    Whether real or perceived, the EFF’s alleged bias is at stake now that Google money — not just money from a billionaire (Cuban) — lands on its lap; it can, by extension or association, serve to discredit patent reformers



  9. EPO Defying Patent Restrictions/Limits From the European Parliament, the European Commission and the European Countries It Claims to Represent

    The departure from the EPC (and from the rule of law) at the EPO still means that patents are being granted on things that, as per the constitutions, should never have been patentable



  10. The UPC is Dead. But Bristows is Now Fully Engaged in Necrophilia.

    In an effort to float a dead project the deceiving folks from Team UPC pretend that everything is ready to go (commence) because they've managed to find some gowns and robes



  11. Links 19/1/2019: Wikipedia Cofounder Moves to GNU/Linux, Wine 4.0 RC7 Released, Godot 3.1 Beta 2, NomadBSD 1.2 RC1

    Links for the day



  12. Links 18/1/2019: Mesa 18.3.2, Rust 1.32.0

    Links for the day



  13. Links 17/1/2019: ZFS Debate Returns, AWS Pains Free Software

    Links for the day



  14. US Patent Lawyers Will Need to Change Profession or End up Becoming Abundantly Redundant, Unemployed

    In the age of Patent Trial and Appeal Board (PTAB) inter partes reviews (IPRs) and 35 U.S.C. § 101 it’s too risky to sue with dodgy patents; moreover, the Federal Circuit‘s growing adoption of Alice means that no recent cases have given hope to patent maximalists and litigation frequency has fallen again (at double-digit rates)



  15. Links 16/1/2019: Deepin 15.9 Released and Mozilla Fenix

    Links for the day



  16. Brexit Has Failed, But So Has the Unitary Patent (UPC)

    Even though all signs indicate that the Unified Patent Court (UPC) will never become a reality spin is to be expected from Team UPC, still looking to profit from more litigation and expanded scope



  17. IBM, Which Will Soon be Buying Red Hat, is Promoting Software Patents in Europe

    Even days apart/within confirmation of IBM's takeover of Red Hat IBM makes it clear that it's very strongly in favour of software patents, not only in the US but also in Europe



  18. Team UPC on Dead UPC: Choosing Gowns for Corpses

    The campaign of lies, long waged by Team UPC in order to manipulate politicians and courts, hasn’t stopped even in 2019 (IAM threw in the towel, but some of Team UPC is still ‘embalming’ UPCA)



  19. Links 15/1/2019: MX Linux MX-18 Continuum Reviewed, Mageia 7 Artwork Voting

    Links for the day



  20. Council of Europe (CoE) Recognises There's No Justice at the EPO

    It’s now the Council of Europe‘s turn to speak out about the grave state of international organisations that exist in Europe but aren’t subjected to European law (which they routinely violate with impunity)



  21. Dominion Harbor -- Armed by Microsoft's Biggest Patent Troll -- Goes After the World's Biggest Android OEMs, Huawei and Samsung

    Dominion Harbor, the patent troll that gets bucketloads of patents from Intellectual Ventures (a patent troll strongly connected to Microsoft and Bill Gates), is still suing using shell entities



  22. Links 14/1/2019: Linux 5.0 RC2 and DXVK 0.95 Released

    Links for the day



  23. Only the Higher Courts -- Not Trump's 'Poster Child' -- Can Bring Back Software Patents

    Software patents are not making a "comeback" as some like to claim; in fact, the latest court cases and notably their outcomes suggest that nothing has changed



  24. “Uniloc is a Lawsuit Factory”

    Apple is a very secretive company, so it is hard to know what goes on with the patent troll Uniloc



  25. European Patent Office a Textbook Example of Lawless, Rogue Institutions

    The tyrannical nature of the EPO is still being demonstrated by the sad fate of Patrick Corcoran; technical judges at the EPO are feeling intimidated by nontechnical politicians and bankers



  26. No, Software Patents Are Not Poised to Make a Comeback Under New US Patent Office Rules

    Poor understanding of the difference between patent courts and patent offices is to blame for widely-spread misinformation from Ars Technica (part of Condé Nast)



  27. IP Kat Has Turned From EPO Critic (to the Point of Being Blocked by the EPO) to EPO Whitewasher That Gags EPO Whistleblowers

    The EPO tried to forcibly gag (block) IP Kat like it blocks Techrights (since 2014); failing that, the EPO got the blog to just act as a whitewashing operation for Team Campinos (more or less the same as Team Battistelli)



  28. Linspire 'Reborn' is Still Working for Microsoft and Facilitating Surveillance on GNU/Linux Users

    GNU/Linux spyware scandals may be back (and it's not about Canonical and Amazon but Linspire and Microsoft); Microsoft is meanwhile exposing innocent kids to pedophiles and it refuses to explain or defend this



  29. Links 12/1/2019: Wine 4.0 RC6, X-Plane 11.30, SuperTuxKart 0.10 Beta, LibreOffice 6.2 RC2

    Links for the day



  30. The EPO's Low Patent Quality Can Kill the European Software Industry and Kill People Too

    The patents granted by the EPO are often invalid as per courts' decisions, which means that fake/illegitimate European Patents saturate the market and discourage development (e.g. of software and life-saving drugs)


CoPilotCo

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

CoPilotCo

Recent Posts