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 Darker Past of the Next President of the EPO - Part I: Introduction

    Some new details about Mr. Campinos, who is Battistelli’s successor at the EPO



  2. Confessions of EPO Insiders Reveal That European Patents (EPs) Have Lost Their Legitimacy/Value Due to Battistelli's Policies

    A much-discussed topic at the EPO is now the ever-declining quality of granted patents, which make or break patent offices because quality justifies high costs (searches, applications, renewals and so on)



  3. Patent Firms From the United States Try Hard to Push the Unitary Patent (UPC), Which Would Foment Litigation Wars in Europe

    The UPC push seems to be coming from firms which not only fail to represent public interests but are not even European



  4. In the Age of Alice and PTAB There is No Reason to Pursue Software Patents in the United States (Not Anymore)

    The appeal board in the US (PTAB) combined with a key decision of the Supreme Court may mean that even at a very low cost software patents can be invalidated upon demand (petition) and, failing that, the courts will invalidate these



  5. IAM is Wrong, the Narrative Isn't Changing, Except in the Battistelli-Funded (at EPO's Expense) Financial Times

    The desperate attempts to change the narrative in the press culminate in nothing more than yet another misleading article from Rana Foroohar and some rants from Watchtroll



  6. The Federal Circuit Continues Squashing Software Patents

    Under the leadership of Sharon Prost the Court of Appeals for the Federal Circuit (CAFC) continues its war on software patents, making it very hard to remember the last time it tolerated any



  7. SUEPO Representatives Like Elizabeth Hardon Vindicated as Battistelli's Detrimental Effect on Patent Quality is Widely Confirmed

    Feedback regarding the awful refusal to acknowledge patent quality crisis at the EPO as well as the appointment of a President so close to Battistelli (who most likely assures continuation of his policies)



  8. Links 17/10/2017: KDE Frameworks 5.39.0, Safe Browsing in Epiphany

    Links for the day



  9. Judge Bryson Rules Against Allergan After It Used Native American Tribes to Dodge Scrutiny of Patents (IPRs); Senator Hatch Does Not Understand IPRs

    Having attempted to dodge inter partes reviews (IPRs) by latching onto sovereign immunity, Allergan loses a key case and Senator Hatch is meanwhile attempting to water down IPRs albeit at the same time bemoaning patent trolls (which IPRs help neutralise)



  10. Rumours That António Campinos Initially Had No Competition at All (for Battistelli's Succession) Are Confirmed

    Succession at the EPO (mostly French) shows that there's little room for optimism and Battistelli's people are too deeply entrenched in the upper echelons of the EPO



  11. EPO Stakeholders Complain That the New Chairman Does Not Grasp the Issues at the EPO (or Denies These)

    Some information from inside the EPO’s Administrative Council, whose Chairman is denying (at least to himself) some of the core issues that render the EPO less competitive in the international market



  12. Another Misleading Article Regarding Patents From Rana Foroohar at the Financial Times

    In an effort to promote the agenda of patent maximalists, many of whom are connected to the Financial Times, another deceiving report comes out



  13. Monika Ermert's Reports About the Crisis at the EPO and IP Kat's Uncharacteristically Shallow Coverage

    News from inside the Council shows conflict regarding the quality of European Patents (granted by the EPO under pressure from top-level management)



  14. Patent Troll VirnetX a Reminder to Apple That Software Patents Are a Threat to Apple Too

    VirnetX, a notorious patent troll, is poised to receive a huge sum of money from Apple and Qualcomm is trying to ban Apple products, serving to remind Apple of the detrimental impact of patents on Apple itself



  15. Links 16/10/2017: Linux 4.14 RC5, Debian 9.2.1, End of LibreOffice Conference 2017

    Links for the day



  16. The Systematic Erosion of Workers' Rights and Holidays at the EPO Goes Years Back

    The legitimacy of the staff's concerns at the EPO, having seen basic labour safeguards being shredded to pieces by Battistelli for a number of years (predating even the escalation of the conflict)



  17. Articles in English and German Speak About the Decline in Quality of European Patents (Granted by the EPO)

    Heise and The Register, two sites that have closely watched EPO affairs for a number of years, speak about the real problem which is declining patent quality (or rushed examination) -- a recipe for frivolous litigation in Europe



  18. Software Patents and Patent Trolls Not a Solved Issue, But the US is Getting There

    A media survey regarding software patents, which are being rejected in the US in spite of all the spin from law firms and bullies such as IBM



  19. US Patent Trolls Are Leaving and the Eastern District of Texas Sees Patent Cases Falling by More Than Half

    The decline of patent aggression in the US and the patent microcosm's response to Justices, having ruled in TC Heartland, curtailing patent trolls



  20. Qualcomm's Nightmares Are Getting Worse as Antitrust Questions Are Raised and Assessed

    Qualcomm is getting itself deeper in trouble as fines pile up and its multi-billion dollar dispute with Apple isn't getting it anywhere



  21. Forget About Apple; Two of the Leading Phone Makers (Samsung and Huawei) Are Bickering Over Patents

    Massive Android OEMs, Huawei and Samsung, are in a big patent dispute and this time, for a change, China is a legal battleground



  22. Tim Heberden From the Glasshouse Advisory is Throwing Stones in a Glasshouse to Create Patent Litigation

    IAM's latest lobbying, aided by the patent microcosm, for a climate of feuds and disputes (to line the pockets of the litigation 'industry')



  23. Access to Medicine is More Important Than Patents

    Some of the latest news about patents that impede/deny access to crucial medication; strategic litigation from the generics sector, seeking to invalidate patents and then offer low-cost alternatives



  24. Links 14/10/2017: Windows Breaks Dutch Law, Wine 2.19 Released

    Links for the day



  25. The Patent Trial and Appeal Board (PTAB) Supported by Congress, a Federal Judge, Soon to be Supported by the Supreme Court Too?

    The Patent Trial and Appeal Board is still widely defended, except by the patent microcosm which likes (and profits from) patent trolls and litigation Armageddon



  26. Patents Are Turning BlackBerry and Nokia, Which Used Android, Into Anti-Android Fronts That Tax Android OEMs

    The Canadian BlackBerry has sued BLU in the US only to compel it to pay 'protection' money; Nokia's patents are being scattered to trolls, which are doing something similar (without risking litigation themselves)



  27. The Unified Patent Court (UPC) is Rotting Like the European Patent Office

    The Unitary Patent litigation pipe dreams (or prosecution/trolling fast lane), which Battistelli's EPO long relied on, turn out to be the road to nowhere



  28. Lying and Faking Now a Standard Procedure at the European Patent Office

    The European Patent Organisation (EPO) under the leadership (or chairmanship) of Christoph Ernst continues to relay lies from Battistelli's Office, SUEPO rejects these, the Office lies about SMEs, prioritises Microsoft (again), and probably buys fake Twitter "followers"



  29. Links 13/10/2017: X.Org Server 1.19.5, pfSense 2.4, Final Stages of Ubuntu 17.10

    Links for the day



  30. Truly Terrible 'Journalism' About António Campinos Boils Down to Lobbying and Agenda-Pushing

    The expectedly shallow coverage of the appointment (succession) of Battistelli's French pick, which will likely change nothing of significance at the European Patent Office (EPO)


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