So please don't repeat it without discussion. There are no significant features of MS Office that cannot be mapped to ODF, if not to v1.0 then v1.2.

More importantly, it is absolutely and entirely the wrong approach in developing a standard to start by ensuring you can reproduce all the flaws of legacy pre-standardisation approaches. For certain you should examine existing approaches and learn from them, but not mimic them to satisfy a particular organisation, no matter how dominant.

Note: Microsoft personnel have already stated they could support ODF in discussions around Massachusetts - maybe that would be in a way that would inhibit those documents being used in Sharepoint. I care not if Sharepoint or other Microsoft technologies are so limited. What I demand is that we have a common, documented and unencumbered file format that allows for seamless interchange of documents.

Notes for those who see 550 million installed seats of a product as proof positive that is all we should care about:

(i) they ain't all the same product i.e. are not all compatible with each other in the seamless idealism Gary espouses;

(ii) within 5 years, 550 million will be less than a tenth of the devices in active use capable of read/writing an office-type document.