Group items tagged

Good commentary from Frank Hayes of Computerworld concerning a very serious problem. Even if ISO somehow manages to approve MS-OOXML, Microsoft has reserved the right to implement whatever extension of Ecma-OOXML they feel like implementing. The whole purpose of this standardization exercise was to bring interoperability, document exchange and long term archive capability to digital information by separating the file formats from the traditions of application, platform and vendor dependence.

If Microsoft is determined to produce a variation of OOXML that meets the needs of their proprietary application-platform stack, including proprietary bindings and dependencies, any illusions we might have about open standards and interoeprability will be shattered.  By 2008, Microsoft is expected to have over a billion MS-OOXML ready systems intertwined with their proprietary MS Stack of desktop, server, device and web applications. 

How are we to interoperate/integrate non Microsoft applications and services into that MS Stack if the portable document/data/media transport is off limits?  If you thought the MS Desktop monopoly posed an impossible barrier, wait until the world gets a load of the MS Stack!

Good article Frank.

~ge~

I promise that within a few minutes of reading this OOXML Wiki you will be wondering if this is in fact an ODF Wiki!  This is incredible.

Fast forward to the section called, "Interoperability between ODF and OOXML", and enjoy.  They cite the problem and make an interop recommendation for each entry.  And what a recommendation it is.  Speaks volumes.

There is definately something going on in Europe.  The EU IDABC has rejected ODF, OOXML, OASIS, Ecma and ISO!  And are now trying to write their own highly interoperable XML file format, ODEF.  an effort we will fully support with our da Vinci plugin for MSOffice. 

Well, not only will we support ODEF, we'll write it for them if they really want to cut to the chase and get the kind of vendor independent interoperability the world hungers for.

The British Standards Institute (BSi) is responsible for the massive research that went into this OOXML Wiki.  They have hunted down and defined the interoperability problem areas between ODF and OOXML.  Surprise surprise.  They be many. 

The interesting part is that the BSi researchers have found massive, indeed overwhelming fault with OOXML!  Yet, instead of recommending that Ecma make the needed changes to OOXML, they instead recommend that ISO ODF make the changes!

Not OASIS ODF!  Not Ecma OOXML.

ISO ODf!

The difference is all the difference in the world.  Sun does not control ISO ODF the way they control OASIS ODF.   And at ISO, all the binding of ODF to OpenOffice/StarOffice that accounts for the zero interoperability of ODF applications can be broken as needed.

This is

This is the fifth of the six major iX - interoperability enhancement proposals submitted to the OASIS ODF TC - SC between July 2006 and February of 2007. This particular iX proposal lead to the "List Enhancement Proposal" donnybrook that consumed the OASIS ODF TC for the next six months, ending with the OpenDocument Foundation being booted out of OASIS in May of 2007. The six iX proposals were all different approaches to the same basic problem: ODF was not desinged to be interoperable with MSOffice documents, applications or bound processes. The proposals come out of the OpenDocument' Foundation's efforts to save ODF in Massachusetts. ODF iX repressents a subset of ODF designed to grealty improve compatibility with MS binary and XML formats. With the ODF iX subset, the da Vinci plug-in would be able to convert the billions of MSOffice binary and xml documents with a very high level of fidelity, and do so within the bounds of "round trip" business processes. The most basic iX approach was to add five generic elements to the existing ODF specification. The five generic elements would cover lists, tables, fields, sections, and page dynamics (breaks). It is a well known fact that these five areas of incompatibility between OpenOffice ODF and MSOffice binaries represent 95% of all conversion fidelity problems. MSOffice has one way of implementing lists, and, OpenOffice has another. These application specific implementation models are irreconcilably different. It's also true that the applicaiton specific implementation models are directly reflected in each file format. So applications implementing ODF must also implement the OpenOffice model for lists, fields, tables, sections and page dynamics-page positioning if they are to have any meaningful measure of exchange fidelity. Perhaps the best of the iX approaches was that based on the innovative use of metadata to describe presentation-layout attributes.

Jon Bosak, who founded the XML and ODF efforts among many other achievements, recently wrote an article concerning the position of ODF, Open XML and PDF Jon's public writings are rare, well-considered and always of interest. As with other Sun-affiliated people in recent times, Jon has been exemplary in that even though he has a side, he does not take sides. I think I can agree with much of what he says, though I would note Don't forget about HTML.

Excuse me!  Excuse me!  Does the right hand know what the left hand is doing?

NiST, the National Institute of Standards and Technology, is authorized by the USA Department of Commerce. 

Years ago, in conjunction with the Department of Defense (WWI), the Dept of Commerce joined with two manufacturing consortia to form ANSI.  Int eh aftemath of WWII and the formation of ISO/IEC, the US Congress, at the behest of the Department of Commerce, authorized the NiST subdiary.  NiST then authorized (and continues to oversee) ANSI to take on the USA representation at ISO/IEC.

ANSI in turn authorized INCITS to take on the ISO/IEC document processing specific standardization issues.  It is INCiTS that represents the citizens on the ISO/IE SCT 1 workgroups (wk1) responsible for both ISO 26300 (OpenDocument - ODF) and Ecma 376 (MOOX).

Okay, so now we have the technical staffers at NiST refusing to allow purchases of Vista, MSOffice 2007 and IE 7.0.  What's going on?  And why is this happenign near everywhere at this exact same moment in time?

The answer is that this is clearly plan B. 

Plan A was to force Microsoft to enable MSOffice native use of ODF.  The reasoning here is that governments could force Microsoft to implement ODF, the monopolist control over desktops would be broken, and the the threat of MS leveraging that monnopoly into servers, devices and Internet systems be averted.

The key to this plan A was to mandate purchase requirements comply with Open Standards.  And not just any "Open Standards".  Microsoft had previously demonstrated how easy it was to use ECMA as rubber stamp for standards proposals that were anything but open.  This is why in August of 2004 the EU asked the OASIS ODF Technical Committee to submit ODF to ISO/IEC.  ISO had not yet been corrupted in the same way as the hapless money hungry ECMA.

Plan A was going along

This is the official community gathering place and information resource for the OpenDocument Format (ODF) OASIS Standard (ISO/IEC 26300). Suitable for text, spreadsheets, charts, graphs, presentations, and databases, ODF frees documents from their applications-of-origin, enabling them to be exchanged, retrieved, and edited with any OpenDocument-compliant software or tool. This is a community-driven site, and the public is encouraged to contribute content.

Great inteview, i'll comment as i make my way down the page.  Hopefully others will do the same.

When did this happen? Th eonly thing markets and government pilot studies show is that it's IMPOSSIBLE to convert existing MSOffice documents to ODF. And even if you are able to do a lossy conversion, there is no way to convert back again without serious loss processing specific informaiton. (round tripping - which is critical to business process document exchange and routing).