> (...) anyone can freely adopt (...)

Microsoft asserts its "IP" is almost sacred all the time. Many patents are directly relevant to OOXML. Microsoft has been forced to admit the truth in memos detailing the use patents as weapons. Just having those patents makes OOXML a risk to everyone save Microsoft.

Then Microsoft played the game and offered an "Open Specification Promise" (which turned out to be "non-binding") and a "Covenant Not To Sue" (please notice that it followed Sun steps). In contrast with Sun's commitments, Microsoft's promises didn't stand even a little upon close inspection.

As long as Microsoft can assert its sacred "IP" to stop competition, OOXML is a no-no. ISO is most likely going to approve a patented (underspecified, ill-designed, et cetera) standard. In that case, the process would have failed horribly.

Yet I can't stop thinking this is all a diversion. Massachussets has already accepted OOXML, even if it's not open by its own definition, not standard (at least yet), not anything... Probably many others will follow suit.

nachokb