01.31.08
Gemini version available ♊︎Can the Broken OOXML be Rubbished and Microsoft Blobs be Put on Top of ODF Instead?
Why settle for a rickshaw when you already have a car?
A couple of weeks ago we stated that Microsoft is apprently willing to embrace ODF. The company actually said something along those lines. To quote the article, “if individual governments mandate the use of ODF instead of Open XML, Microsoft would adapt.” Rob Weir has just invited Microsoft to consider harmonization.
So we’ve agreed that this approach is technically feasible. We’re also agreed that extending ODF outside of the standards process is not a good idea. So the obvious solution is to extend ODF within the standards process. So, let’s do it! What are we waiting for?
There is no reason why, by a harmonization process, all of the functionality of Microsoft Office cannot be represented on a base of ISO 26300 OpenDocument Format. I personally, as Co-Chair of the OASIS ODF TC, stand ready and willing to sponsor such a harmonization effort in OASIS. So let’s start harmonization now, and avoid further divergence.
Microsoft’s response will be interesting.
To address the recent accusation (from Microsoft, by proxy) that IBM plots to shoot down OOXML, Bob Sutor has posted a response in his blog. The response took the form of a pointer to Slashdot where it is said quite correctly that Microsoft calls the kettle black. What again was the main purpose of OOXML? That’s right, to harm ODF. It’s really that simple. We have already accused the writer who made this by-proxy accusation of carrying water for Microsoft. He did this after receiving a gift and some brainwash. █
ᶃ Gemini Space
This post is also available in 
Content is available under CC-BY-SA