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. Kather Augenstein and Bristows Shift Attention to Germany in an Effort to Ram the Dying UPC Down Everyone's Throats

    Down the throat, hopes Team UPC, the Unitary Patent system will go, even though Britain cannot ratify, throwing the whole thing into grave uncertainty



  2. United for Patent Reform Defends USPTO Director Michelle Lee From Attacks by the Patent Microcosm

    Michelle Lee is finally (if not belatedly) shielded by a bunch of large technology companies; The deep-pocketed industry finally steps in line with our position, which is usually when things turn out the way we advocate for



  3. Team UPC and CIPA Are Lobbying, Publishing Puff Pieces, and Rewriting the Law for Unitary Patent (UPC) Behind Closed Doors

    A collection of the latest news and views on the UPC, which is being lied about by those who stand to benefit from it and is probably going nowhere because Brexit means that the UK stays out, in which case it must be reset and pertinent ratifications done all over again



  4. China's Suffering From Patent Maximalism Has Europe Forewarned

    The parasitic elements inside China -- those that just want lots of litigation (even if from patent trolls) -- are winning over, much to the detriment of the Chinese economy, and Team UPC threatens to do the same in Europe with help from Battistelli



  5. Links 27/4/2017: Mesa 17.0.5 RC1, Git 2.13.0 RC1, and Linkerd 1.0

    Links for the day



  6. The Latest Expensive PR Blitz of the EPO, Led by Jana Mittermaier and Rainer Osterwalder Under the 'European Inventor Award' Banner

    The PR agencies of the Corsican in Chief, who appears to be buying political support rather than earning any, are very busy this week, as yet another reputation laundering campaign kicks off



  7. Links 26/4/2017: SMPlayer 17.4.2, Libreboot Wants to Rejoin GNU

    Links for the day



  8. PatentShield is Not the Solution and It Won't Protect Google/Android From Patent Trolls Like Microsoft's

    A new initiative called "PatentShield" is launched, but it's yet another one of those many initiatives (Peer-to-Patent and the likes of it, LOT Network, OIN, PAX etc.) that serve to distract from the real and much simpler solutions



  9. Patent Quality Crisis and Unprecedented Trouble at the European Patent Office (EPO) Negatively Affect Legitimate Companies in the US As Well

    The granting en masse of questionable patents by the EPO (patent maximalism) is becoming a liability and growing risk to companies which operate not only in Europe but also elsewhere



  10. Blog 'Takeovers' by Bristows and Then Censorship: Now This Firm Lies About the Unitary Patent (UPC) and Then Deletes Comments That Point Out the Errors

    Not only are Bristows employees grabbing the mic in various high-profile IP blogs for the purpose of UPC promotion (by distortion of facts); they also actively suppress critics of the UPC



  11. Links 25/4/2017: Kali Linux 2017.1 Released, NSA Back Doors in Windows Cause Chaos

    Links for the day



  12. Astoundingly, IP Kat Has Become a Leading Source of UPC and Battistelli Propaganda

    The pro-UPC outlets, which enjoy EPO budget (i.e. stakeholders' money), are becoming mere amplifiers of Benoît Battistelli and his right-hand UPC woman Margot Fröhlinger, irrespective of actual facts



  13. EPO Fiasco to be Discussed in German Local Authority (Bavarian Parliament) Some Time Today as the Institution Continues Its Avoidable Collapse

    Conflict between management and staff -- a result of truly destructive strategies and violations of the law by Benoît Battistelli -- continues to escalate and threatens to altogether dismantle the European Patent Office (EPO)



  14. In the US and Elsewhere, Qualcomm's Software Patents Are a Significant Tax Everyone Must Pay

    The state of the mobile market when companies such as Qualcomm, which don't really produce anything, take a large piece of the revenue pie



  15. In South Asia, Old Myths to Promote Patent Maximalism, Courtesy of the Patent Microcosm

    The latest example of software patents advocacy and patent 'parades' in India, as well as something from IPOS in Singapore



  16. Links 24/4/2017: Linux 4.11 RC8, MPV 0.25

    Links for the day



  17. Why Authorities in the Netherlands Need to Strip the EPO of Immunity and Investigate Fire Safety Violations

    How intimidation and crackdown on the staff representatives at the EPO may have led to lack of awareness (and action) about lack of compliance with fire safety standards



  18. Insensitivity at the EPO’s Management – Part IX: Testament to the Fear of an Autocratic Regime

    A return to the crucial observation and a reminder of the fact that at the EPO it takes great courage to say the truth nowadays



  19. For the Fordham Echo Chamber (Patent Maximalism), Judges From the EPO Boards of Appeal Are Not Worth Entertaining

    In an event steered if not stuffed by patent radicals such as Bristows and Microsoft (abusive, serial litigators) there are no balanced panels or even reasonable discussions



  20. EPO Staff Representatives Fired Using “Disciplinary Committee That Was Improperly Composed” as Per ILO's Decision

    The Board of the Administrative Council at European Patent Organisation is being informed of the union-busting activities of Battistelli -- activities that are both illegal (as per national and international standards) and are detrimental to the Organisation



  21. Links 23/4/2017: End of arkOS, Collabora Office 5.3 Released

    Links for the day



  22. Intellectual Discovery and Microsoft Feed Patent Trolls Like Intellectual Ventures Which Then Strategically Attack Rivals

    Like a swarm of blood-sucking bats, patent trolls prey on affluent companies that derive their wealth from GNU/Linux and freedom-respecting software (Free/libre software)



  23. The European Patent Office Has Just Killed a Cat (or Skinned a 'Kat')

    The EPO’s attack on the media, including us, resulted in a stream of misinformation and puff pieces about the EPO and UPC, putting at risk not just European democracy but also corrupting the European press



  24. Yann Ménière Resorts to Buzzwords to Recklessly Promote Floods of Patents, Dooming the EPO Amid Decline in Patent Applications

    Battistelli's French Chief Economist is not much of an economist but a patent maximalist toeing the party line of Monsieur Battistelli (lots of easy grants and litigation galore, for UPC hopefuls)



  25. Even Patent Bullies Like Microsoft and Facebook Find the Patent Trial and Appeal Board (PTAB) Useful

    Not just companies accused of patent infringement need the PTAB but also frequent accusers with deep pockets need the PTAB, based on some new figures and new developments



  26. Links 21/4/2017: Qt Creator 4.2.2, ROSA Desktop Fresh R9

    Links for the day



  27. At the EPO, Seeding of Puff Piece in the Press/Academia Sometimes Transparent Enough to View

    The EPO‘s PR team likes to 'spam' journalists and others (for PR) and sometimes does this publicly, as the tweets below show — a desperate recruitment and reputation laundering drive



  28. Affordable and Sophisticated Mobile Devices Are Kept Away by Patent Trolls and Aggressors That Tax Everything

    The war against commoditisation of mobile computing has turned a potentially thriving market with fast innovation rates into a war zone full of patent trolls (sometimes suing at the behest of large companies that hand them patents for this purpose)



  29. In Spite of Lobbying and Endless Attempts by the Patent Microcosm, US Supreme Court Won't Consider Any Software Patent Cases Anymore (in the Foreseeable Future)

    Lobbyists of software patents, i.e. proponents of endless litigation and patent trolls, are attempting to convince the US Supreme Court (SCOTUS) to have another look at abstract patents and reconsider its position on cases like Alice Corp. v CLS Bank International



  30. Expect Team UPC to Remain in Deep Denial About the Unitary Patent/Unified Court (UPC) Having No Prospects

    The prevailing denial that the UPC is effectively dead, courtesy of sites and blogs whose writers stood to profit from the UPC


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