03.05.08

Gemini version available ♊︎

Technical Flaws in OOXML and Technical Flaws in ISO (When Subjected to Sheer Abuse)

Posted in Antitrust, Asia, Europe, GNU/Linux, IBM, Interoperability, ISO, Microsoft, Open XML, OpenDocument at 1:21 am by Dr. Roy Schestowitz

Uncomfortable Reality

The reaction — or clarification rather — in Tim Bray’s blog last night was interesting. He was not thrilled by what he called “cherry-picking” of words (e.g. "unadulterated bullsh*t"), so he prepended a copyrights-oriented disclaimer to his latest post which is fairly well-balanced.

“Harsh reality put bluntly can make the viewer (or listener, or reader) wish to look away; it doesn’t make any less real.”In his previous popular post he seems to have complained about me specifically and Sam Hiser made some similar accusations. Since when is it inappropriate to quote a person with link to the context? And since when is the highlighting of proven misconduct an iffy business that hurts one’s credibility?

Harsh reality put bluntly can make the viewer (or listener, or reader) wish to look away; it doesn’t make any less real. Some people continue to stare embarrassed at corruption, but one should truly be bold enough to face it because only this way it can be addressed. And no, we don’t live in a perfect world, but the least one can do is help improve it by identifying causes for harm and demanding change. The BRM was just as bad [1, 2, 3, 4, 5] as was anticipated [1, 2, 3, 4, 5].

In any event, shortly after the good announcement about Linux (not Ballnux, e.g. Novell) PCs arriving at Europe with ODF 'built in', IBMers proceed to discussing the technical deficiencies of OOXML, as opposed to the OOXML BRM and much of the OOXML-related misconduct.

OOXML Still Broken

Rob Weir posted a couple of good items that are worth keeping in mind. The first one makes another indirect approach toward the issue of legacy formats. As mentioned yesterday, binary Office format specifications render OOXML pretty much unnecessary, rationalising more than ever the need for Microsoft to embrace ODF and migrate its legacy in that unified direction. The company claims to have just done the same with IE8 and Web standards (promises, promises), so why not document formats?

Faithful representation of Microsoft Office 97-2008. I’ve learned it is rarely polite to ask a man what he means by “faithful”, but let me make an exception here. We have now the binary Office format specifications, not part of the standard, but posted by Microsoft. And we have OOXML specification. In what way does the OOXML “represent faithfully” the “existing corpus” of legacy documents?

Does OOXML tell you how to translate a binary document into OOXML? No. Does it tell you how to map the features of legacy documents in OOXML? No. Does it give an implementor any guidance whatsoever on how to “represent faithfully” legacy documents? No. So it is both odd and unsatisfactory that primary goal of the OOXML standard is so tenuously supported by its text.

Now, certainly, someone using the binary formats specifications, and using the OOXML specification, could string them together and attempt a translation, but the results will not be consistent or satisfactory. It is the Carolino Effect. Knowing the two endpoints is not the same as knowing how to correctly map between them. A faithful mapping requires knowledge not only of the two vocabularies, but also the interactions.

The second item from Weir alludes to the BRM, but only in the sense that it mentions a concern raised there (and unsurprisingly disregarded due to lack of time). It’s about macros, which Microsoft never liked talking about all that much. Microsoft hopes that nobody will spot and scrutinise for the weaknesses which only Microsoft has in mind, hoping to divert attention away from the parts most sensitive to unrebuttable criticism.

Finally, note that this lack of information on how to locate macros within a document makes it impossible for anyone to programmatically combine or divide OOXML documents which may contain macros. For example, imagine a 2-page spreadsheet, with a macro on sheet one only. How can it be split into two one-page documents, if there is no defined way to locate the script associated with page one? This is the type of automated composition and document manipulation that OOXML should be enabling. Similarly, how can one combine two single documents containing macros into one document, if there are no defined rules for locating and naming macros? Many basic types of applications,such as merging slide shows, etc., will break in the presence of macros.

The above topic was of interest to several NB’s in Geneva, but could not be discussed for lack of time at the BRM.

The Fast Track to the Wastebasket

Microsoft may have taken a wild gamble by choosing an inappropriate route to ISO-isation. As a result of this, under great pressure, Microsoft needed to resort to breaking the law (more on this in a moment). Here is Groklaw’s interpretation of Malaysia’s press release, which we mentioned yesterday.

Malaysia Standards Says Most of Their Technical Concerns Unresolved at BRM; Fast Track Inappropriate

They were there. And they contradict the stories being put out by those in charge and by Microsoft. They did *not* have the opportunity to have their concerns addressed totally. Malaysia voted to disapprove the undiscussed bulk dispositions, although they had earlier voted to approve some dispositions that were discussed.

When All Else Fails, Break the Law

The OOXML scandal in India — one which we covered here before [1, 2, 3] — is finally receiving some press coverage. While the 'mainstream press' turns somewhat of a blind eye, Linux.com does a story.

Microsoft is encouraging its business partners to promote its Office Open XML specification (OOXML) to the Indian Bureau of Standards (BIS) and Ministry of IT. This move has incensed supporters of the rival OpenDocument Format (ODF) who fear that the “soft” Indian state may not be able to stand up to Microsoft pressure tactics.

It is encouraging to see that all these known and proven incidents get documented. Hopefully, the EU is watching this carefully and taking it into account (or Microsoft's accounting).

“If you flee the rules, you will be caught. And it will cost you dearly.”

Neelie Kroes (about Microsoft), February 27th, 2008

Neelie Kroes

Share in other sites/networks: These icons link to social bookmarking sites where readers can share and discover new web pages.
  • Reddit
  • email

Decor ᶃ Gemini Space

Below is a Web proxy. We recommend getting a Gemini client/browser.

Black/white/grey bullet button This post is also available in Gemini over at this address (requires a Gemini client/browser to open).

Decor ✐ Cross-references

Black/white/grey bullet button Pages that cross-reference this one, if any exist, are listed below or will be listed below over time.

Decor ▢ Respond and Discuss

Black/white/grey bullet button If you liked this post, consider subscribing to the RSS feed or join us now at the IRC channels.

DecorWhat Else is New


  1. IRC Proceedings: Thursday, December 08, 2022

    IRC logs for Thursday, December 08, 2022



  2. Links 08/12/2022: Deepin 20.8 and CERN, Fermilab Move to AlmaLinux

    Links for the day



  3. [Meme] Sirius Corporation Run by Dummies

    At Sirius ‘Open Source’, the fish rots from the head down



  4. Code of Conduct-Like Culture at Sirius ‘Open Source’ (Managers Never Held Accountable for Anything, Other Staff Blamed for Management's Failures)

    Sirius was abandoned a week ago (my wife and I resigned with immediate effect), leaving a skeleton crew that’s about 50% ‘management’ (barely qualified or not qualified at all) and 50% 'low-paid' geeks (what’s left of them); guess who’s blaming who and who always gets punished



  5. Virtually (i.e. Online) and for Only One Hour the EPO's Staff Representation Was Allowed to Discuss Many Lingering Concerns

    “Report on the LSCMN meeting with VP4 of 9 November 2022″ (i.e. one month ago) is being circulated this week; “On 9 November 2022,” says the union or the local officials (Staff Union of the EPO, or SUEPO for short, has overlaps), “the Local Staff Committee Munich (LSCMN) met with VP4, Ms Nellie Simon, to discuss a number of prevailing local matters in a virtual meeting which had been scheduled, as had the previous one, for one hour only.” (the usual; they intentionally don’t allocate sufficient time)



  6. [Meme] António Campinos-Controlled (EPO-Commissioned) Surveys Are Just for Show (to Help 'Validate' Lies)

    The real EPO survey is not that one conducted by (and for) António Campinos



  7. European Patent Office (EPO) on the Decline, According to the Fifth Edition of the Technologia Staff Survey

    Today we share some documents that circulated amongst EPO staff yesterday; it's about this year's staff survey that was not conducted by the EPO itself (to serve EPO management and its twisted agenda



  8. Free Software is So Robust That Its Opponents Need to Travel 12 Months Back in Time in Order to Find Fear, Uncertainty, and Doubt (FUD) Material

    Microsoft- and Linux Foundation-connected sites help smear or stigmatise Free software (citing hostile 'experts'); this week they borrow news from 12 months ago to make a point



  9. IDG Has Resorted to Microsoft Marketing SPAM Instead of Actual Journalism

    Microsoft puff pieces are published as "opinions", disguised as "news" while in fact serving no purpose other than marketing



  10. Open Invention Network (OIN) Protects Amazon and AWS From Activists Like Us Who Want to Abolish Software Patents Through Reforms of the Patent Systems

    The Open Invention Network (OIN) does not exist to serve the Free software community but to work against it; the latest joining (AWS) proves this



  11. Sirius ‘Open Source’ and the Money Missing From the Pension

    Sirius ‘Open Source’ is unable to cope with basic legal requirements such as sending payslips to staff (this hasn’t been done for months already!) and such issues have gone on for almost 4 years already



  12. IRC Proceedings: Wednesday, December 07, 2022

    IRC logs for Wednesday, December 07, 2022



  13. Links 07/12/2022: ArcoLinux Beta 23.01 and Cryostat 2.2

    Links for the day



  14. [Meme] Where Did the Money Go?

    Sirius ‘Open Source’ became a company that cannot even do accounting right; pertinent technical employees had to do a lot of chasing for years just to get the basics rectified



  15. Evidence of Sirius ‘Open Source’ (or Sirius Corporation) Failing to Pay Pensions, Failing to Inform Staff, Not Responding to Staff

    The job my wife and I left this past Friday (after about 21 years combined) had turned sour years ago; hoping that this serves as a cautionary tale to others, we've decided to show pension lapses, lack of payslips, and excuses that accompanied that for years



  16. Links 07/12/2022: Blender 3.4 and Apple GPU Drivers Now in Asahi Linux

    Links for the day



  17. IRC Proceedings: Tuesday, December 06, 2022

    IRC logs for Tuesday, December 06, 2022



  18. Links 07/12/2022: Kali Linux 2022.4, GNUnet 0.19.0, and Pgpool-II 4.4.0

    Links for the day



  19. Subsidising the Likes of Rupert Murdoch is Not Supporting Journalism

    There are yet more attempts to tax citations; not only does that make no practical or moral sense, it's being lumped in or joined together with a must-pass "defence" (military) bill in order to suppress opposition



  20. Microsoft Layoffs Again

    The company behind Windows is in a bad state, but it is being propped up by the taxpayers; if rumours are true, Microsoft might get a lot smaller next year



  21. Microsoft is Killing Hospital Patients With Its Insecure-by-design Windows Operating System

    Many people continue to needlessly die because many hospitals still foolishly deploy Windows on mission-critical life-saving machines



  22. Sirius ‘Open Source’ Failing at the Most Basic Employment Regulations

    The company we left behind last week was a repeat violator of employment laws; to make matters worse, it led to its long-term or long(time)-serving staff becoming very baffled, having to contact the pension provider for clarifications



  23. Sirius ‘Open Source’: When the Company Stops Paying Your Pension and You Don't Know Until the Pension Provider Keeps Sending Physical Post to Alert You

    Today we turn our attention to pension blunders at Sirius ‘Open Source’; in recent years even something basic like pension contributions wasn’t smooth sailing



  24. [Meme] Sirius Open Source, Closed-Minded Bossing

    At Sirius ‘Open Source’, decisions are made in the dark without consultation with staff and many things go wrong as a result; of course the culprits never hold themselves accountable



  25. Links 06/12/2022: LibreOffice 7.5 Alpha and digiKam 7.9.0

    Links for the day



  26. Rumour: Very Large Microsoft Layoffs (Another Round) Next Month, Lists Already Being Prepared





  27. Benoît Battistelli in 2015: EPO is Ready to Start Unified Patent Court (UPC), Expect UPC in 2016

    We’re almost in 2023 and UPC is being delayed again; this is what EPO President Benoît Battistelli said way back in 2015 (official video from the EPO; 3:45-4:34 cropped apart)



  28. IRC Proceedings: Monday, December 05, 2022

    IRC logs for Monday, December 05, 2022



  29. Links 06/12/2022: FreeBSD 12.4 and Inkscape 1.2.2

    Links for the day



  30. Sirius Not-So-‘Open Source’: Cannot Talk to Colleagues, Cannot Speak About Work

    Cover-up and lies became a corporate pattern at the company where I had worked since 2011; it was time to go in order to avoid cooperation in unethical activities


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

Recent Posts