Update on ODF and Massachusetts

As Andy points out, “Silence means consent”. If this is a topic that is important to you (and it should be), I’d also encourage to take a few minutes and make your opinion known.

A few days ago, I posted my comments to the Mass. ITD on whether or not it should include OOXML in its list of approved standards. I also urged anyone with an opinion on this issue to send their own comments to the ITD at this address: standards@state.ma.us. Now, Pamela Jones, who has contributed hugely to the ODF effort in the past, has just posted a long and informative entry at Groklaw, pointing her readers to various resources that they may wish to consult in preparing their own comments, as well as ideas on the various areas upon which comments may be relevant. PJ has done her usual great job on this, and I’d encourage you to read her entry to see how her observations strike you.

It’s particularly important for you to consider doing so, because I learned from a reporter today that only about 50 comments have been filed with the ITD so far. With only 8 days to comment left, this compares very poorly to the over 150 comments that were received by the ITD in 2005. I have no idea what percentage of these comments are pro OOXML and what percentage urge the ITD to stick only with ODF, but given the small number in total, it could easily be disproportionate in one direction or the other, especially if a concerted effort has been made by one constituency or the other to influence the outcome.

Regular readers will know that I think that this is an important issue. Right now, the default decision in the ITD’s new version of the Enterprise Technical Reference Model is to include OOXML. In my last post, I paraphrased one slogan from the activist 1960’s that helped to shape a lot of who I am today. I’d like to now offer another catchphrase from those braver and more involved times, this time a chant from the many protest rallies that punctuated the antiwar movement: “Silence means consent.”

That slogan is particularly apt now, because the fewer the comments the ITD receives, the more certain will be the result. After all, if people no longer care, why should the ITD stick its neck out? The past immediate experiences of both Peter Quinn and Louis Gutierrez have made the consequences all to obvious. These people aren’t paid combat pay to be controversial – they’re just supposed to keep the IT structure effective for our benefit. If we want them to do more than just do what they’re told by vendors, we owe it to them to back them up.

–jeremy

Massachusetts May Adopt OOXML – What Say You?

Andy continues his prodigious coverage of the Massachusetts OOXML/ODF debate. From a recent post:

The Massachusetts Information Technology Division (ITD), the state agency that effectively launched the voyage of ODF around the world in August of 2005, has released a new version of its Enterprise Technical Reference Model. And this new draft includes Microsoft’s OOXML formats as an acceptable “open format.” The new draft was posted today here, and the very brief comment period will end on July 20. The header to the announcement at the ITD Web site reads as follows:

A review draft of ETRM v. 4.0 is available for review and comment from July 2nd through July 20th, 2007. Comments should be submitted to standards@state.ma.us. This major release of the ETRM updates content published in version 3.6, introduces the new Management Domain, enhances the ETRM’s format for accessibility and usability as well as provides additions and updates to existing language and technical specifications. For a detailed outline of major revisions made in this version please consult the Major Revisions for ETRM v.4.0 document.

The announcement is not a surprise to me, as I’ve been following the progress of the ITD’s internal reviews over the past six months. I’ve not been commenting on this publicly in order to try to give Bethann Pepoli (once again the interim CTO, since the departure of Louis Gutierrez) and her team the space to do their internal evaluations with less pressure than Peter Quinn experienced the first time around. However, and as you can imagine, the ITD has been under as much pressure behind the scenes (and perhaps more) as the legislators of those states that have recently tried, and failed, to pass laws that would mandate open formats in government.

The OOXML-related changes to the text of the ETRM are deceptively insignificant. By my word search, there are only three references: the inclusion of the name of the standard in the introductory summary of changes, a brief description and migration section in the Domain: Information part of the draft (scroll down and look for the “Open Formats” section), and the listing of Ecma among the other standards bodies on a list of “Relevant Standards Organizations.” But the potential impact of these change if retained will be great.

How much pressure has the Massachusetts ITD been under to accept Ecma 376? I’ve been told by those in the know that the contacts reached all the way to Deval Patrick, our new governor. Here, as in the states where legislation was introduced, the point was forcefully and repeatedly made that Microsoft is the kind of company that can provide jobs and other economic support where and as it pleases. And, to be fair, the same points were been made in the past by representatives of IBM and Sun when they have spoke out in favor of ODF.

Now we are looking at a very short comment period, commenced with no advance warning, spanning a holiday, and contained within one of the busiest vacation months of the year (one can’t help wondering why).

That makes the comment period less than 14 business days in a month that, as Andy points out, is one that is very popular for vacationing. Assuming the addition of ECMA 376 moves forward, the question becomes how large of a blow is this to ODF? Opinions on that remain all over the map. Some seem to think it’s a minor setback while others say it could potentially relegate ODF to being a footnote in history. The fact remains that OOXML still only has a single implementation. It’s also unclear if the latest version of Office completely implements the spec or implements items not in the spec. This means that if ODF adoption doesn’t gain any traction, Microsoft will easily be able to move forward with proprietary extensions, let ECMA 376 languish or even drop support in the future altogether. In other words, we’ll be right back where we started. That’s a bad thing. Andy has further coverage on the topic, including reactions from around the industry.

–jeremy