RECENT ARTICLES

Open Source Weblog

Microsoft rewrites history in Massachusetts
August 02, 2007

The other day I advocated giving Microsoft the benefit of the doubt with regards to its attutude to open source, with the proviso that even with that benefit the company’s actions would still sometimes inevitably be seen in a bad light.

The fact is that sometimes giving the company the benefit of the doubt is *really* hard work. Take the reaction of Doug Mahugh, Microsoft Office Open XML technical evangelist, to the news that Massachusetts has finalized its Enterprise Technical Reference Model 4.0 with the inclusion of Office Open XML alongside the OpenDocument Format.

“It's clear that they've been lobbied pretty hard by vendors, lawyers, and others with interests in document-format legislation,” writes Mahugh, linking to comments on the ETRM legitimately submitted by IBM’s Rob Weir,Gesmer Updegrove’s Andy Updegrove, and FSF member Sam Hiser.

To refer to legitimate comments to a public consultation document as “lobbying” is disingenuous, especially given Microsoft’s track record in this regard.

It’s worth remembering that in response to the proposed adoption of ODF, Microsoft’s government affairs director, Brian Burke, promoted an amendment to a state bill designed to remove the decision-making powers of the Massachusetts Information Technology Division.

Now that's lobbying. (And let's not forget Florida's own Men In Black).

Meanwhile Jason Matusow, Microsoft's director of corporate standards, covers the news that ETRM 4.0 includes both OOXML and ODF under the headline “Policy Makers Being Balanced & Reasonable“.

The suggestion that Massachusetts was previously somehow being unbalanced and unreasonable is pretty rich. As I wrote in September 2005:

“While the software giant continues to lobby the state government to change its mind and accept that Microsoft's forthcoming Office Open XML Formats are open enough to be considered, there are other, more long-term options open to the company. These include adopting OpenDocument as a format within Office, and opening up its file formats to an industry standards body.”

To some extent the company did both (although whether it did either to satisfaction is a matter of opinion). In the meantime, it is worth noting that Massachusetts’ definition of “open formats” has not changed at any point:

“The Commonwealth defines open formats as specifications for data file formats that are based on an underlying open standard, developed by an open community, affirmed and maintained by a standards body and are fully documented and publicly available.”

Whether OOXML meets that definition is a matter of opinion, but given the definition hasn’t changed and Microsoft has it is pretty clear that if anyone was being unreasonable, it wasn’t the ITD.


Digg!

  Email this entry to a friend

Posted by Matthew Aslett on August 2, 2007 02:28 PM

Comments

“The Commonwealth defines open formats as specifications for data file formats that are"

1) "based on an underlying open standard,"

ECMA claims to be a standards organizations but are they an "open standard" organization? I think not since they allow the inclusion of patented material and material requiring licensing fees. How open is that?

2) "developed by an open community,"

Please show me where anybody in the "community" did anything but approve Microsoft's work in putting together the 6,0000+ pages of the Office Open XML spec?

3) "affirmed and maintained by a standards body and"

ECMA does not maintain the spec, the owner does and for the Office Open XML spec, that is Microsoft

4) "are fully documented and publicly available.”

Not fully documented with parts which say things like "as implemented in Microsoft Word 95". Since those sections do not specify the operation but instead, to look at a closed source product, there are many parts of Office Open XML which are not publicly available.

OOXML does is NOT OPEN and does not meet the requirements stated in the ETRM 4.0 document. So how was it approved? Probably MS MIB's.

Posted by: Barney on August 4, 2007 07:12 PM

If this is part of the Mass. definition of open formats:

"developed by an open community, affirmed and maintained by a standards body"

how does Microsoft OOXML fit this description? OOXML is not developed by an open community, it is not even developed by a community. It is developed exclusively by Microsoft. While it might be affirmed by ECMA, it is not maintained by ECMA. It is maintained by Microsoft, exclusively.

Posted by: Danny Wall on August 5, 2007 03:36 AM

Microsoft has not earned the benefit of the doubt over the years. Quite the opposite if you review their track record.

Posted by: Robert MacEwan on August 5, 2007 11:11 PM

Post a comment

Name:

Email Address:

URL:

Remember Me?    Yes     No 

Comments: