EditorsAbout the SiteComes vs. MicrosoftUsing This Web SiteSite ArchivesCredibility IndexOOXMLOpenDocumentPatentsNovellNews DigestSite NewsRSS

02.11.08

ECMA’s and Microsoft’s Mistake in Geneva

Posted in Deception, ECMA, Europe, ISO, Microsoft, Open XML, Standard at 10:51 pm by Dr. Roy Schestowitz

Article authored by Russell Ossendryver

ISOMicrosoft’s position is hardening as the ISO vote on OOXML (DIS 29500) in Geneva approaches at the end of this month. We know more clearly now how Microsoft and its proxy group, ECMA, will position Microsoft’s OOXML specification in advance of the vote. In short, Microsoft is betting that its influence with National Bodies will allow it to push through a specification which elevates its own interests over that of truly competitive, open international standards. In the end, it will be Microsoft’s own inflexibility that will be its undoing, and that undoing means knocking the OOXML out of approval for ISO status.

“ECMA, a RIAA-like industry group dedicated to advancing its members’ interests…”ECMA, a RIAA-like industry group dedicated to advancing its members’ interests, published its responses to comments of the ISO National Bodies in response to Microsoft’s Office Open XML application for ISO standardization. The ECMA proposals will be discussed at a Ballot Resolution Meeting (BRM) in Geneva after which the National Bodies may reconsider their original vote.

Download the PDF

ECMA makes an apparently false statement several times throughout its response: “Although no reference implementation or interoperability test suite is available at this time, a growing number of implementations of ECMA-376 are becoming available.”

That statement is not true. What ECMA does not say is that no one has implemented ECMA-376 OOXML in full or even close to it. In fact most ECMA referenced implementations are just using filters, converters or a file viewer. And as we know, Office 2007 is writing its own custom XML. Office 2007 lacks a “Save As OOXML (ECMA 376)” write that would make it possible to conform, verify and validate applications relying on the specifications.

So there is still no present implementation of what may or may not become an international and/or U.S. national standard.

It is strange indeed that the OOXML format submitted to ECMA and ISO is not implemented even in MS Office 2007: Nor does it appear that OOXML can ever be implemented in Office 2007 or future versions, at least not in the proposed ECMA form as it exists today. And that’s the only form under evaluation for the time.

Since OOXML appears impossible to either implement or interoperate with, and this situation has persisted since day one of the specification, it is possible to conclude that Microsoft does not intend to implement OOXML itself as an open standard nor to make it available to competitors for purposes of interoperability.

Microsoft Office 2007 also appears too brittle to handle the required changes proposed by ECMA; and a lot of the national standards bodies’ comments call for changes that Microsoft would not nor could ever implement. It is expected it won’t try. For example, subdocument types in Microsoft Word such as footnotes, endnotes, tables, and frames that must span page breaks have apparently long been largely off-limits to Microsoft developers for repair of serious bugs.

Technically, it would be seem much easier for Microsoft to implement ODF than to even begin to try to standardize the diverse file formats in Office 2007 or to conform later versions of Microsoft Office with OOXML.

Microsoft will make you chase OOXML forever: Not even one complete OOXML has been implemented and they making developers and consumers chase up to six versions already:

1) OOXML 1.0 (i.e. ECMA 376 today)
2) MS-OOXML 2007 (i.e. OOXML 1.0 + all undocumented bits -unimplemented features)
3) OOXML 1.0 Second Edition (whatever is the outcome of Feb’s BRM)
4) MS-OOXML 2007 Service Pack X (Whatever parts of OOXML 1.0 Second Edition implemented by MS Office)
5) Office 2009 Beta 1 (MS-OOXML 2007 + undocumented extensions)
6) Office 2009 (????)

OOXML can never be Interoperable or Implemented: A decision to push the OOXML specification as an ISO standard would launch the beginning of a true Digital Divide between countries, institutions, businesses and regular folks who adopt open standards. This doesn’t include those individuals and businesses who have opted to use vendor-controlled formats and are now locked into those choices. Think of a “black hole” for your data. In other words, it would become a new interoperability nightmare between office suites.

One of the many reasons OOXML cannot interoperate with third parties is that Microsoft is still hiding the migration tables that make it possible for them to create OOXML files from binary files. Those tables simply are not provided in the specifications, despite the stated goal that Microsoft is doing so openly. As a result, only Microsoft can reliably migrate binary formats to the new formats, which provides them with a competitive advantage (everybody else is excluded).

BSI (British Standards Institution) – “The compelling need exists for an open document-format standard that is capable of creating and preserving the billions of documents that have been created in the preexisting binary formats…” This does not mean that the standard has to be a new XML representation of the preexisting binary formats. There is already an open document-format standard that is capable of preserving the documents, and that already has widespread use and for some time its evolution has “enjoyed the checks and balances afforded by an open standards process.”

BSI (British Standards Institution) – “The OOXML could qualify if there is a need for another open document-format standard alongside existing established standards, and how the new standard would interoperate with established standards. OOXML has not yet been proven to be interoperable nor implemented, as no conforming consumers and producers have yet been created. Another claim which cannot be made is implementation of an application that produces and consumes conformant OOXML. Both interoperability and implementation are seemingly impossible.”

Using products from a single supplier that cannot be implemented by another party impedes innovation, competition and choice, which will increase costs through decreased competition and decreased flexibility.

The XML proposed in OOXML is not a general purpose language for Office documents: That’s the real irony. The whole point of XML is to create formats which can produce data which can be freely interchange between applications out there. That includes even those applications which don’t exist quite yet, but will soon. Therefore that an XML-based format should be designed in such a way as to contradict the fundamental purpose of XML should be heavy in clues about what’s going on. But, here is the problem: there is no such clue because OOXML is custom fit for Microsoft’s products only and ties consumers into the MS environment.

National Boards must also understand that OOXML is a different format. They must realize that using it implies the purchase of new software, in some cases the purchase of new hardware. In all cases, it involves the conversion of files to the new format, which only Microsoft can accomplish.

Office Open XML is not 6000 pages long: The complexity, extraordinary length, technical omissions and single-vendor dependencies combine to make alternative implementation legally and practically impossible. Add the additional 2300 pages in bug fixes and an annex part, then you add on the un-documented bits, stuff related to old binary codes to ensure “BACKWARD COMPATIBILTY LOCK-IN,” you have probably 100,000 pages once you include substantial semantics lacking in the current proposal.

One of the reasons people use XML in the real world is because this programming contains agreed-upon syntax and semantics. It’s implicit that, without an open XML design where everything is documented, Microsoft’s implementation is excluding others from reliably rendering documents like Office 2007 without using Office 2007.

The Closed Development Cycle of OOXML: Ecma International (”Ecma”) Technical Committee 45 (”TC45″), which maintains OOXML, works in an opaque manner. There are no public mails lists, voting, balloting and appeals policies not published. OOXML is a format that was pre-developed within Microsoft’s development group and Microsoft retains the right to veto any changes that are proposed in TC45. Further, the meeting activities of TC45, the committee’s work-in-progress, documents and e-mail are not public. It is also difficult to participate in the development of OOXML, membership requirements are high and limiting and generally only available by invitation through one of the corporate members. And all public comments are suppressed. Read More on Achieving Openness – ODF vs OOXML by Sam Hiser.

The development of Microsoft Office is also done in secrecy so we do not know what will be the default file format of Office 14 (Office 2009)? Will it be identical to that described in Ecma-376? We don’t know, because Microsoft does not provide a clear roadmap. This lack of direction provides Microsoft with a huge competitive advantage.

Language and Linguistics Problems in OOXML: Microsoft also did a bad job in creating a document format for the whole world, which is an important requirement for an ISO standard. Considerations for users in Israel and many Muslim countries were excluded in the specification of OOXML. The weekend continues being only Saturday and Sunday which effects Iraq, Algeria, Sudan, Bahrain, Qatar, Bangladesh, Israel, Jordan, Libya, Pakistan, Syria and the United Arab Emirates:

a) There is no way to represent minority languages (does not use ISO 639)
b) There are still a lot of borderlines images that match only with US culture and doesn’t provide alternatives for other cultures.
c) It is not possible to make numerations in Greek, Tamil, Armenian, Ethiopian, etc. Only in Arabic numbers (occidental set) and Latin.
d) Doesn’t use W3C XLS: FO, a language for transforming XML documents and an XML vocabulary for specifying formatting semantics
e) Microsoft does not support, is the RFC 3987 specification, which defines UTF-8 capable Internet addresses. Consequently, OOXML does not support the use of Chinese characters within a Web address.

Office 2007 OOXML Spreedsheets is a closed binary format: Some of the binary blobs of .XLS are moved over .XLSX(M) as is, they are not XML which is in contradiction with what the standard is for in the first place. As for XML parts themselves, you can’t add your own XML within Microsoft spreadsheet’s XML (placeholders, markers,…). since it automatically corrupts the file. It undermines the reason why people use XML , and the regular XML tooling in particular (XSLT, tagging, templating, and so on). Read More at OOXML is Defective by Design by Stephane Rodriguez.

OOXML Offer No Second Need: The native and lossless support of ODF in Office 2007 would have been a fairly spectacular demonstration that the file format that Microsoft is proposing is superior to the existing ISO ODF standard. But that’s not what Microsoft chose to do, and neither the partners that joined Microsoft at ECMA.

Instead, Microsoft simply chose to proceed for economic reasons with an inferior file format that isn’t needed. For decades, third party vendors have had to reverse engineer Microsoft Office to work effectively with Microsoft Office, and OOXML will extend that problem into the future, as the crucial parts of the spec are not well-documented, despite its massive size.

From the start OOXML was inappropriate for Fast-Track processing: And now ECMA and Microsoft want to continue rushing it. They know that further review will only lead to revelations of more problems. It should be clear now that DIS 29500 needs more time in committee process to mature as a specification before consideration as an International Standard.

Furthermore, the ECMA proposed changes to DIS 29500 fail to address harmonization; naming confusions; consistency of fixes is a problem, support for legacy documents, IP Issues specifically in regards to GPL Licenses used by Open Source, Microsoft’s main competitor/antagonist; ECMA response to the date problem only has complicated matters; and many of these questions on OOXML remain unanswered.

Can we in good faith endorse a standard that is not technically sound with conflicting recommendations on technical remedies? Can we, in good conscience, give ISO approval to a specification which will benefit only one company that has subverted the standards process, which is submitting the specification only to drive sales of their office productivity suite, and which has no good faith interest in actually deploying the specification?

“The negative impact of standards for competition are mostly caused by a biased endowment with resources available for the standardization process itself. Therefore. even when the consensus rule is applied, dominant large companies are able to manipulate the outcome of the process, the specification of a standard, into a direction which leads to skewed distribution of benefits or costs in favor of their own interests.” Knut Blind

As the National Bodies contemplate their upcoming votes, it is important to remember that the true purpose of OOXML is to delay adoption of the current ISO document standard, ODF. We, the global community, should look askance at Microsoft’s bad faith ISO submission, and discourage the National Bodies from granting ISO status to this ill-conceived specification called OOXML.

Download the PDF or view original article at fanaticattack.com

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

2 Comments

  1. Stephane Rodriguez said,

    February 12, 2008 at 1:45 am

    Gravatar

    Look who is presenting at the Microsoft Office developer conference this week?

    http://blogs.msdn.com/erikaehrli/archive/2008/02/11/open-xml-at-the-microsoft-office-developer-conference-2008.aspx

    Someone who goes by the name “Peter O’Kelly (Burton Group Research Director)”, the so-called independent group (who simply repeated Microsoft propaganda in a recent study that claims among other things that ODF is simplistic). Ah!

    We also have Wouter Van Vugt. But this should be no surprise either.

    Whatever money buys…

  2. Roy Schestowitz said,

    February 12, 2008 at 2:16 am

    Gravatar

    Miguel de Icaza presented in some previous events too.

    As for Peter O’Kelly, he was part of the brainwash sessions in Redmond — sessions that were breeding brainwashed journalists who later attacked IBM and defended Microsoft in the intl’ press, having received a free trip (plus all expenses covered) across the globe.

    Virtually ALL OOXML support is PAID FOR. That cannot be stressed strongly enough.

    http://boycottnovell.com/2007/11/30/favours-for-ooxml-support/
    http://boycottnovell.com/2007/12/28/format-seige-money-dvd/

What Else is New


  1. Links 18/9/2019: Fedora Linux 31 Beta, PCLinuxOS 2019.09 Update

    Links for the day



  2. Links 17/9/2019: CentOS 7.7 and Funtoo Linux 1.4 Released

    Links for the day



  3. EPO is Not European

    Internationalists and patent trolls are those who stand to benefit from the 'globalisation' of low-quality and law-breaking patents such as patents on algorithms, nature and life itself; the EPO isn't equipped to serve its original goals anymore



  4. The EPO's Central Staff Committee and SUEPO (Staff Union) Respond to “Fascist Bills” Supported by EPO President António Campinos

    Raw material pertaining to the latest Campinos "scandal"; what Campinos said, what the Central Staff Committee (CSC) said, and what SUEPO said



  5. Storm Brewing in the European Patent Office After a Hot Summer

    Things aren't rosy in EPOnia (to say the least); in fact, things have been getting a lot worse lately, but the public wouldn't know judging by what media tells the public (almost nothing)



  6. Why I Once Called for Richard Stallman to Step Down

    Guest post from the developer who recently authored "Getting Stallman Wrong Means Getting The 21st Century Wrong"



  7. As Richard Stallman Resigns Let's Consider Why GNU/Linux Without Stallman and Torvalds Would be a Victory to Microsoft

    Stallman has been ejected after a lot of intentionally misleading press coverage; this is a dark day for Software Freedom



  8. Links 16/9/2019: GNU Linux-libre 5.3, GNU World Order 13×38, Vista 10 Breaks Itself Again

    Links for the day



  9. Links 16/9/2019: Qt Quick on Vulkan, Metal, and Direct3D; BlackWeb 1.2 Reviewed

    Links for the day



  10. Richard Stallman's Controversial Views Are Nothing New and They Distract From Bill Gates' Vastly Worse Role

    It's easier to attack Richard Stallman (RMS) using politics (than using his views on software) and media focus on Stallman's personal views on sexuality bears some resemblance to the push against Linus Torvalds, which leans largely on the false perception that he is sexist, rude and intolerant



  11. Links 16/9/2019: Linux 5.3, EasyOS Releases, Media Backlash Against RMS

    Links for the day



  12. Openwashing Report on Open Networking Foundation (ONF): When Open Source Means Collaboration Among Giant Spying Companies

    Massive telecommunications oligopolies (telecoms) are being described as ethical and responsible by means of openwashing; they even have their own front groups for that obscene mischaracterisation and ONF is one of those



  13. 'Open Source' You Cannot Run Without Renting or 'Licensing' Windows From Microsoft

    When so-called ‘open source’ programs strictly require Vista 10 (or similar) to run, how open are they really and does that not redefine the nature of Open Source while betraying everything Free/libre software stands for?



  14. All About Control: Microsoft is Not Open Source But an Open Source Censor/Spy and GitHub/LinkedIn/Skype Are Its Proprietary Censorship/Surveillance Tools

    All the big companies which Microsoft bought in recent years are proprietary software and all of the company’s big products remain proprietary software; all that “Open Source” is to Microsoft is “something to control and censor“



  15. The Sad State of GNU/Linux News Sites

    The ‘media coup’ of corporate giants (that claim to be 'friends') means that history of GNU/Linux is being distorted and lied about; it also explains prevalent lies such as "Microsoft loves Linux" and denial of GNU/Free software



  16. EPO President Along With Bristows, Managing IP and Other Team UPC Boosters Are Lobbying for Software Patents in Clear and Direct Violation of the EPC

    A calm interpretation of the latest wave of lobbying from litigation professionals, i.e. people who profit when there are lots of patent disputes and even expensive lawsuits which may be totally frivolous (for example, based upon fake patents that aren't EPC-compliant)



  17. Links 15/9/2019: Radeon ROCm 2.7.2, KDE Frameworks 5.62.0, PineTime and Bison 3.4.2

    Links for the day



  18. Illegal/Invalid Patents (IPs) Have Become the 'Norm' in Europe

    Normalisation of invalid patents (granted by the EPO in defiance of the EPC) is a serious problem, but patent law firms continue to exploit that while this whole 'patent bubble' lasts (apparently the number of applications will continue to decrease because the perceived value of European Patents diminishes)



  19. Patent Maximalists, Orbiting the European Patent Office, Work to 'Globalise' a System of Monopolies on Everything

    Monopolies on just about everything are being granted in defiance of the EPC and there are those looking to make this violation ‘unitary’, even worldwide if not just EU-wide



  20. Unitary Patent (UPC) Promotion by Team Battistelli 'Metastasising' in Private Law Firms

    The EPO's Albert Keyack (Team Battistelli) is now in Team UPC as Vice President of Kilburn & Strode LLP; he already fills the media with lies about the UPC, as one can expect



  21. Microsoft Targets GNU/Linux Advocates With Phony Charm Offensives and Fake 'Love'

    The ways Microsoft depresses GNU/Linux advocacy and discourages enthusiasm for Software Freedom is not hard to see; it's worth considering and understanding some of these tactics (mostly assimilation-centric and love-themed), which can otherwise go unnoticed



  22. Proprietary Software Giants Tell Open Source 'Communities' That Proprietary Software Giants Are 'Friends'

    The openwashing services of the so-called 'Linux' Foundation are working; companies that are inherently against Open Source are being called "Open" and some people are willing to swallow this bait (so-called 'compromise' which is actually surrender to proprietary software regimes)



  23. Microsoft Pays the Linux Foundation for Academy Software Foundation, Which the Linux Foundation is Outsourcing to Microsoft

    Microsoft has just bought some more seats and more control over Free/Open Source software; all it had to do was shell out some 'slush funds'



  24. Links 14/9/2019: SUSE CaaS Platform, Huawei Laptops With GNU/Linux

    Links for the day



  25. Links 13/9/2019: Catfish 1.4.10, GNOME Firmware 3.34.0 Release

    Links for the day



  26. Links 12/9/2019: GNU/Linux at Huawei, GNOME 3.34 Released

    Links for the day



  27. Links 12/9/2019: Manjaro 18.1 and KaOS 2019.09 Releases

    Links for the day



  28. EPO: Give Us Low-Quality Patent Applications, Patent Trolls Have Use for Those

    What good is the EPC when the EPO feels free to ignore it and nobody holds the EPO accountable for it? At the moment we're living in a post-EPC Europe where the only thing that counts is co-called 'products' (i.e. quantity, not quality).



  29. Coverage for Sponsors: What the Linux Foundation Does is Indistinguishable From Marketing Agencies' Functions

    The marketing agency that controls the name "Linux" is hardly showing any interest in technology or in journalism; it's just buying media coverage for sponsors and this is what it boils down to for the most part (at great expense)



  30. Watch Out, Linus Torvalds: Microsoft Bought Tons of Git Repositories and Now It Goes After Linux

    Microsoft reminds us how E.E.E. tactics work; Microsoft is just hijacking its competition and misleading the market (claiming the competition to be its own, having "extended" it Microsoft's way with proprietary code)


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