When we created ODF 20+ years ago, Microsoft first laughed at the committee at OASIS, then made OOXML to render it moot, then rigged ISO to make OOXML a standard, then implemented ODF and now participates in the ODF committee and helps fund its work through COSM.

is Twitter's OOXML to and it's at the "rigging ISO" stage.

ODF vs OOXML is not the only example.

In 1998, following the submission of VML and PGML (both vector graphics formats using XML) to W3C, a new standards working group was created, SVG, to take the best of both for the Web. Microsoft decided not to join largely because SVG used so much PGML & promoted VML in its products, implementing it in Internet Explorer and Office so SVG would suffocate and die.

24 years later, Microsoft has deprecated VML and fully implemented SVG.

I share these not to dig at Microsoft but because I was involved in both cases. There are others, by other vendors.

There are however more examples of embracing an existing standard and succeeding against competitors by driving its adoption than there are of creating a competing standard to retain monopoly control.

@webmink My impression is that Microsoft has gotten better on these things. It is still not a very Open Source friendly platform though.

In any case, I'm glad they support ODF, because it means my own open source project only needs to support ODT documents as an export format, and it works nearly everywhere.

Follow

@veronica I'd say they are now no worse than their peers!

· · Web · 0 · 0 · 1
Sign in to participate in the conversation
Meshed Mastodon

A server for Meshed Insights Ltd to join the Fediverse