OOXML vs ODF: where next for interoperability?
'A diversion from the real end game – the taking of the internet'
It is in places a rare voice of sanity:
People continue to insist that if only Microsoft would implement ODF natively in MSOffice, we could all hop on down the yellow brick road, hand in hand, singing kumbaya to beat the band. Sadly, life doesn’t work that way. Wish it did.
Sure, Microsoft could implement ODF - but only with the addition of application specific extensions to the current ODF specification … Sun has already made it clear at the OASIS ODF TC that they are not going to compromise (or degrade) the new and innovative features and implementation model of OpenOffice just to be compatible with the existing 550 million MSOffice desktops.
The simple truth is that ODF was not designed to be compatible – interoperable with existing Microsoft documents, applications and processes. Nor was it designed for grand convergence. And as we found out in our five years participation at the OASIS ODF TC, there is an across the boards resistance to extending ODF to be compatible with Microsoft documents, applications and processes.
Summary: in Edwards’ opinion, there are technical and political reasons why seamless ODF interop cannot be baked into Microsoft Office. Therefore the Foundation is now working on interop with the W3C’s Compound Document Format, about which I know little.
Surprisingly, Edwards also says that ODF will fail in the market:
If we can't convert existing MS documents, applications and processes to ODF, then the market has no other choice but to transition to MS-OOXML.
Edwards is thoroughly spooked by the success of Sharepoint in conjunction with Exchange, and overstates his case:
If we can't neutralize and re purpose MSOffice, the future will belong to MS-OOXML and the MS Stack. Note the MS Stack noticeably replaces W3C Open Web technologies with Microsoft's own embraced “enhancements”. Starting with MS-OOXML/Smart Tags as a replacement for HTML-XHTML-RDF Metadata. HTML and the Open Web are the targets here. ODF is being used as a diversion from the real end game – the taking of the Internet.
I find this implausible. At the same time, I agree about the importance of interoperability with Microsoft Office.
I would also like clarification on what are the limitations of OOXML / ODF conversion. Here's a technique that does a reasonable job. Open OOXML in Microsoft Office, save to binary Office format. Open binary Office format in Open Office, save as ODF. The same works in reverse. Not perfect perhaps, but a whole lot better than the Microsoft-sponsored add-in that works through XSLT. Could this existing Open Office code be made into a Microsoft Office plug-in, and if so, what proportion of existing documents would not be satisfactorily converted?
Note that Sun's ODF converter seems to be exactly this, except that it does not yet work with Office 2007. It could presumably be used with Office 2003 and the OOXML add-in, to provide a way to convert OOXML to ODF in a single application. Some further notes on Sun’s converter here.
A freelance writer since 1992, Tim Anderson specialises in programming and Internet development topics. He is a contributor to lots of publications, including Register Developer. You can find his blog here.
Sponsored: Protecting mobile certificates