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 EFF Back to Tackling Software Patents, Not Just Patent Trolls

    Electronic Frontier Foundation lawyers start targeting large companies that exploit patents for intimidation and extortion, not just patent trolling



  2. Microsoft Wants to Devour the Competition (Linux), Devour People's Data

    Refuting the "new Microsoft" propaganda and some ludicrous concept that Microsoft is now "playing nice"



  3. Benoît Battistelli Thinks 'President' is Above the Law, Decides to Ignore the Court's Ruling

    Staff of the EPO is given yet more reasons to protest tomorrow at the British Consulate, for the so-called 'President' of the EPO reminds everyone of the very raison d'être for the protest -- a vain disregard for the rule of law



  4. Links 24/2/2015: Xfce 4.12 a Week Away, GNOME 3.16 Previewed

    Links for the day



  5. Links 23/2/2015: Ubuntu Kylin 14.04.2 LTS, Cinnamon 2.6 Previews

    Links for the day



  6. IRC Proceedings: February 8th - February 21st, 2015





  7. The EPO's Sham 'Internal Investigation' of EPO Vice-President Željko Topić's Affairs

    The EPO never investigated the Željko Topić affair, it only pretends to have investigated (one small aspect, i.e. cherry-picking) using a Benoît Battistelli-controlled group



  8. Links 21/2/2015: GNOME 3.15.90, Google Wins Android Lawsuit

    Links for the day



  9. Microsoft AstroTurfing War on GNU/Linux is Still Going On, But Hidden Better, Uses API as Instrument of Lock-in

    The corruptible press continues to describe blatant attacks (Embrace, Extend, Extinguish) against GNU/Linux and Free software as Microsoft 'embracing' Open Source



  10. Lenovo's Superfish Scandal is Spyware on Top of Spyware (Microsoft Windows), the Problem is Inherently Proprietary Software

    Shifting focus to the root problem, which is neither Lenovo nor its laptops but the non-free programs installed on hardware



  11. Benoît Battistelli Once Again Threatens EPO Staff That 'Dares' to Protest, Battistelli Exploits Terror Attacks to Pretend to Respect Free Speech

    The European Patent Office (EPO) President, Benoît Battistelli, reportedly started threatening -- as before -- staff that decides to exercise the right to assemble and protest against abuses, including the abuses of President Battistelli himself



  12. Links 20/2/2015: Android Studio v1.1, GDB 7.9

    Links for the day



  13. Links 20/2/2015: Bloomberg Joins Linux Foundation, ClearOS Community 6.6.0

    Links for the day



  14. The Chartered Institute of Patent Attorneys Slams the European Patent Office for Structural Failings

    An important letter which we overlooked while writing yesterday's 4 articles about the European Patent Office (EPO); yet another key stakeholder complains



  15. Links 19/2/2015: Hewlett-Packard on Cumulus Linux, Previews of GNOME 3.16 Beta

    Links for the day



  16. Techrights Under Attack Again, Shortly After Important EPO Articles

    Techrights highlights a pattern that is months old; Site faces availability issues shortly after reports about the European Patent Office and its abuses



  17. EPO Staff Protests Against Benoît Battistelli’s Lowering of Patents Quality (Scope Expansion and Software Patents for Profit)

    A protest in Munich in less than 6 days will target Mr. Sean Dennehey, who has helped Battistelli cover up his abuses and crush legitimate critics, whom he deemed illegal opposition as if the EPO is an authoritarian regime as opposed to a public service which taxpayers are reluctantly (but forcibly) funding



  18. Breaking: European Patent Office Sued by Its Own Staff in The Hague, Must Unblock Staff's Voices

    The crooked management of the European Patent Office (EPO) gets in legal trouble after repeated attempts to cover up abuses and suppress criticism



  19. Željko Topić's History in SIPO Leaves a Legacy of Alleged DZIV Vehicles (Bribes), Authorship Abuses, and Intimidation Against Reporters

    Another deep look at Željko Topić's background in Croatia, preceding his very notorious appointment to the EPO where he now serves as Benoît Battistelli's most controversial attack dog



  20. The Old Obsession With Patent Trolls Continues to Distract From Debate About Software Patenting

    A roundup of recent coverage about monopolies on algorithms in the United States



  21. Links 19/2/2015: 64-bit ARM Linux, Chinese New Year

    Links for the day



  22. Links 18/2/2015: Linux Report, FlightGear 3.4

    Links for the day



  23. EPO Scandals: The Story So Far

    An overview of articles about mischief, misconduct and breach of laws at the EPO



  24. Links 17/2/2015: TripleO, Pivotal

    Links for the day



  25. Links 17/2/2015: SystemD 219, Frugalware 2.0 (Rigel) Released

    Links for the day



  26. Željko Peratović Slammed for Whitewashing Željko Topić After Publishing Important Piece on Behalf of Key Sources

    Response from Ivan Kabalin to Zeljko Peratovic's so-called "apology" which is both mysterious and seemingly inadequate as it does nothing to actually explain what was wrong (if anything)



  27. Benoît Battistelli Has Made Oversight of European Patent Office Absolutely Impossible





  28. Microsoft Already Killed Nokia, Don't Let It Kill Android Players Too

    Microsoft's strategy against Android mirrors the company's evil strategy that derailed MeeGo and Nokia



  29. Intel Continues to Attack Software Freedom Through UEFI

    The Trojan horse that Microsoft uses to cement its monopoly on desktops and laptops (making it hard or impossible to install and run GNU/Linux) is also being misused to block Coreboot



  30. Links 16/2/2015: Netrunner 15, Bridge Linux

    Links for the day


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