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. Links 29/9/2016: Russia Moving to FOSS, New Nmap and PostgreSQL Releases

    Links for the day



  2. Team UPC is Interjecting Itself Into the Media Ahead of Tomorrow's Lobbying Push Against the European Council and Against European Interests

    A quick look at the growing bulk of UPC lobbying (by the legal firms which stand to benefit from it) ahead of tomorrow's European Council meeting which is expected to discuss a unitary patent system



  3. IP Kat is Lobbying Heavily for the UPC, Courtesy of Team UPC

    When does an IP (or patent) blog become little more than an aggregation of interest groups and self-serving patent law firms, whose agenda overlaps that of Team Battistelli?



  4. Leaked: Conclusions of the Secretive EPO Board 28 Meeting (8th of September 2016)

    The agenda and outcome of the secretive meeting of the Board of the Administrative Council of the EPO



  5. Letter From the Dutch Institute of Patent Attorneys (Nederlandse Orde van Octrooigemachtigden) to the Administrative Council of the EPO

    The Netherlands Institute of Patent Attorneys, a group representing a large number of Dutch patent practitioners, is against Benoît Battistelli and his horrible behaviour at the European Patent Office (EPO)



  6. EPO's Board 28 Notes Battistelli's “Three Current Investigations/Disciplinary Proceedings Involving SUEPO Members in The Hague."

    The attack on SUEPO (EPO staff representatives) at The Hague appears to have been silently expanded to a third person, showing an obvious increase in Battistelli's attacks on truth-tellers



  7. Links 28/9/2016: Alpine Linux 3.4.4, Endless OS 3.0

    Links for the day



  8. Cementing Autocracy: The European Patent Office Against Democracy, Against Media, and Against the Rule of Law

    The European Patent Office (EPO) actively undermines democracy in Europe, it undermines the freedom of the press (by paying it for puff pieces), and it undermines the rule of law by giving one single tyrant total power in Eponia and immunity from outside Eponia (even when he breaks his own rules)



  9. Links 28/9/2016: New Red Hat Offices, Fedora 25 'Frozen'

    Links for the day



  10. Team Battistelli Intensifies the Attack on the Boards of Appeal Again

    The lawless state of the EPO, where the rule of law is basically reducible to Battistelli's ego and insecurities, is again demonstrated with an escalation and perhaps another fake 'trial' in the making (after guilt repeatedly fails to be established)



  11. After the EPO Paid the Financial Times to Produce Propaganda the Newspaper Continues to Produce UPC Puff Pieces, Just Ahead of EU Council Meeting

    How the media, including the Financial Times, has been used (and even paid!) by the EPO in exchange for self-serving (to the EPO) messages and articles



  12. Beware the Patent Law Firms Insinuating That Software Patents Are Back Because of McRO

    By repeatedly claiming (and then generalising) that CAFC accepted a software patent the patent microcosm (meta-industry) hopes to convince us that we should continue to pursue software patents in the US, i.e. pay them a lot more money for something of little/no value



  13. The US Supreme Court Might Soon Tighten Patent Scope in the United States Even Further, the USPTO Produces Patent Maximalism Propaganda

    A struggle brewing between the patent 'industry' (profiting from irrational saturation) and the highest US court, as well as the Government Accountability Office (GAO)



  14. Patent Trolling a Growing Problem in East Asia (Software Patents Also), Whereas in the US the Problem Goes Away Along With Software Patents

    A look at two contrasting stories, one in Asia where patent litigation and hype are on the rise (same in Europe due to the EPO) and another in the US where a lot of patents face growing uncertainty and a high invalidation rate



  15. The EPO's Continued Push for Software Patents, Marginalisation of Appeals (Reassessment), and Deviation From the EPC

    A roundup of new developments at the EPO, where things further exacerbate and patent quality continues its downward spiral



  16. The Battistelli Effect: “We Will be Gradually Forced to File Our Patent Applications Outside the EPO in the Interests of Our Clients”

    While the EPO dusts off old files and grants in haste without quality control (won't be sustainable for more than a couple more years) the applicants are moving away as trust in the EPO erodes rapidly and profoundly



  17. Links 27/9/2016: Lenovo Layoffs, OPNFV Third Software Release

    Links for the day



  18. The Moral Depravity of the European Patent Office Under Battistelli

    The European Patent Office (EPO) comes under heavy criticism from its very own employees, who also seem to recognise that lobbying for the UPC is a very bad idea which discredits the European Patent Organisation



  19. Links 26/9/2016: Linux 4.8 RC8, SuperTux 0.5

    Links for the day



  20. What Insiders Are Saying About the Sad State of the European Patent Office (EPO)

    Anonymous claims made by people who are intimately familiar with the European Patent Office (from the inside) shed light on how bad things have become



  21. The EPO Does Not Want Skilled (and 'Expensive') Staff, Layoffs a Growing Concern

    A somewhat pessimistic look (albeit increasingly realistic look) at the European Patent Office, where unions are under fire for raising legitimate concerns about the direction taken by the management since a largely French team was put in charge



  22. Patents Roundup: Accenture Software Patents, Patent Troll Against Apple, Willful Infringements, and Apple Against a Software Patent

    A quick look at various new articles of interest (about software patents) and what can be deduced from them, especially now that software patents are the primary barrier to Free/Libre Open Source software adoption



  23. Software Patents Propped Up by Patent Law Firms That Are Lying, Further Assisted by Rogue Elements Like David Kappos and Randall Rader (Revolving Doors)

    The sheer dishonesty of the patent microcosm (seeking to bring back software patents by misleading the public) and those who are helping this microcosm change the system from the inside, owing to intimate connections from their dubious days inside government



  24. Links 25/9/2016: Linux 4.7.5, 4.4.22; LXQt 0.11

    Links for the day



  25. Patent Quality and Patent Scope the Unspeakable Taboo at the EPO, as Both Are Guillotined by Benoît Battistelli for the Sake of Money

    The gradual destruction of the European Patent Office (EPO), which was once unanimously regarded as the world's best, by a neo-liberal autocrat from France, Benoît Battistelli



  26. Bristows LLP's Hatred/Disdain of UK/EU Democracy Demonstrated; Says “Not Only Will the Pressure for UK Ratification of the UPC Agreement Continue, But a Decision is Wanted Within Weeks.”

    Without even consulting the British public or the European public (both of whom would be severely harmed by the UPC), the flag bearers of the UPC continue to bamboozle and then pressure politicians, public servants and nontechnical representatives



  27. Released Late on a Friday, EPO Social 'Study' (Battistelli-Commissioned Propaganda) Attempts to Blame Staff for Everything

    The longstanding propaganda campaign (framing staff as happy or framing unhappy staff as a disgruntled minority) is out and the timing of the release is suspicious to say the least



  28. Links 23/9/2016: Latest Microsoft and Lenovo Spin (Now in ‘Damage Control’ Mode)

    Links for the day



  29. White Male-Dominated EPO Management Sinks to New Lows, Again

    Benoît Battistelli continues to make the EPO look like Europe's biggest laughing stock by attempting to tackle issues with corny photo ops rather than real change (like SUEPO recognition, diverse hiring, improved patent quality, and cessation of sheer abuses)



  30. Journalism 102: Do Not Become Like 'Managing IP' or IAM 'Magazine' (the Megaphones of the EPO’s Management)

    Another look at convergence between media and the EPO, which is spending virtually millions of Euros literally buying the media and ensuring that the EPO's abuses are scarcely covered (if ever mentioned at all)


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