The alarming thing is that Massachusetts is just one of several states that are in the same boat. Bill Gates and Company get wind that a state is thinking about adopting an open format and they send in the lobbyists.
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.
At first glance, Robertson's statement is fairly innocuous. He is referring to Massachusetts' decision to support OOXML (Open Office XML) formats. The best FUD isn't immediately obvious. Microsoft PR agency sent this statement proactively, with lots of additional information. Usually, I have to pull out information kicking and screaming; it doesn't come this easy. There is a reason, and it's FUD.
Microsoft is trying to fast track OOXML through ISO ratification, but there has been resistance. Even the United States ISO representative committee has, so far, failed to support OOXML standards ratification. Microsoft needed some good news, and Massachusetts delivered some—and powerful, because the Commonwealth had planned to dump Office altogether.
Microsoft's Doug Mahugh and Jason Matusow piped in with blogs about the OOXML support by Massachusetts, which was expected, by the way. It's all FUD because the reasoning is this: If Massachusetts now considers OOXML open, it must truly be open. The Commonwealth also considers Adobe's PDF as open, too. It's not.
My understanding is that there are ongoing discussions about the size of the group. IBM and others are not currently part of the TC and that concern has been raised within the TC. The NB as well as the TC are both focused on making sure they are operating precisely in respect to the rules of the process. From what I am hearing, the process is completely above board and being handled professionally with oversight from the NB. IBM and others are desirous of expanding the membership, and that issue will continue to be pressed by them I am sure. The TC has another meeting this week, so there will be more discussion on this as things progress.
There is no question that all over the world the competing interests in the Open XML standardization process are going to use all tactics available to them within the rules. Microsoft and its partners (particularly those who have bet their businesses on Open XML), continue to advocate that it is best to enable our customers to choose the technology that best meets the needs of their business.
Make no mistake; all parties are looking at the full picture to find strategies that will result in the outcome they desire. Provided - of course - that they do so within the context of the rules that apply to the process, this is exactly what one should expect to happen. It is going to be a very interesting next few months.
That primary source is a statement posted by Microsoft SA (as in South Africa) at a PR site called MyPressportal, urging the South African National Body to vote "yes" on OOXML. The version below is complete and unaltered.
So here's the game mentioned in the title to this blog entry: you've all seen those pictures in the paper where you are supposed to look for the things that aren't "right" in the picture (why does the man have two different color socks? How come the car is missing one tire?) If you are so inclined, read the statement below, and in the comments field tell us if you find anything that (how to say this delicately) doesn't sound quite "right," either because it is inaccurate or as a result of leaving out important facts.
Comments
Andre
2007-08-23 10:24:01
a) YES vote == current ECMA standard relabeled ISO standard
b) YES mit comments == current ECMA standard relabeled as ISO standard, and some suggestions
c) conditional disapproval == current ECMA standard has a change to get improved and technical comments get fixed. Microsoft will need to offer more.
d) rejection of the standard == no ISO approval, but ECMA standard is here to stay
No rational player, even when you are a partner of Microsoft or "really want" OOXML's ISO approval can support options a) and b). No player risks anything except Microsoft. We know that the current ECMA standard is broken, and full of errors. so even when you want OOXML you should disapprove as a matter of negotiation strategy.
The only explanaition for a YES vote (which is just not rational) is either an "idealistic" agenda to support Microsoft's monopoly or the existance of other means that compensate your self-interest.
A Yes or a "Yes with Comments" (which is formally non-existing) is a very bad business decision.