Today you will read the Commonwealth Governor's mid-year assessment on ODF. (Here is Martin Lamonica's (c|net) preview yesterday.) This assertive declaration for ODF will prove that at least one of Microsoft's FUD messaging points has been ill-conceived in that company's Lab of Disinformation with intent to confuse state legislators and the general public.
You will note that Mass ITD has stuck with its ODF policy (first espoused in the wide-ranging ETRM 3.5 policy document) and corrected the earlier disconnect with the disability community.
What is not directly obvious -- but self-evident -- is that ITD's policy is and always was a policy for open standards that would help the Executive Department gradually move its ICT architecture toward a modular Services Oriented Architecture ("SOA") design. The policy was decidedly not directed at software applications (and therefore it was not a policy that is malicious toward a particular software license model, nor was it a policy to hinder a particular software vendor).
The office document file format was one of many open standards highlighted in ETRM 3.5 and, because the policy implies disruption of a key Microsoft control-point on all its customers (the document file formats), this caused Microsoft much anxiety (due to the assumption of malice) and prompted intense lobbying in the Commowealth -- despite the fact that Microsoft was always encouraged to be the provider of ODF capabilities (and still has an open invitation to participate on the ODF technical committees at ODF's development consortium, OASIS). The most prominent efforts to stall and change the policy came directly under the bright golden dome on Beacon Hill immediately after ETRM 3.5 was finalized and ratified in late September, 2005.
Among the points of Microsoft's messaging script then was the idea that government policy should not use software business model to pre-emptively, unfairly, distinguish among software procurement choices.
This point was clearly stated in a December 14, 2005 speech by Microsoft's Alan Yates in the Commonwealth Senate chambers...
Next, public policy shouldn't necessarily favor one business model
over another. Commercial software can be quite, quite, quite open, just
as Open Source software can be quite open. They're simply different
business models. One business model relies more on the magic of
software, if you will, and one business model relies more on the magic
of services, if you will, gluing disparate parts together through
professional services to make it all work together. Two different
business models.
Microsoft's Alan Yates | Groklaw (from transcript)
The point contains an insidious inherent assumption -- like the famous question, "When did you stop beating your wife?" The inherent assumption is that ETRM 3.5 and the intent of the policy was to create a preference for open source solutions in Massachusetts state government IT procurement and to exclude Microsoft as a vendor of proprietary solutions. That self-centered assumption missed the point entirely.
Exclusion of Microsoft is decidedly not the case, as today's mid-year assessment of ODF will indicate. Mass ITD has found the open source alternative office suite software applications which are ODF-ready to be wanting in their ability to smoothly replace Microsoft Office in the business processes of the state. ITD is opting instead for the interim solution of a Plug-in. This action defies Microsoft's misanthropic assumption -- perpetuated in the media and impossible to erase from almost everyone's mind -- that the Governor's IT department was gunning for Microsoft's head.
Instead, the ODF Plug-in can be interpreted to be a generous gift to Microsoft to extend the life of the software it has sold.
The ODF Plug-in -- by inserting ODF capabilities seemlessly and natively into existing software -- will extend the useful life of MS Office installations in the Commonwealth; the ODF Plug-in will increase the ROI of a significant portion of the Commonwealth's desktop software investment; the ODF Plug-in will preserve existing business processes in the Commonwealth while introducing the wonderful XML data markup standard -- which Microsoft supports whole-heartedly; and significantly the ODF Plug-in will preserve the special workflow processes of disabled PC users in the Commonwealth to give time for alternative software products to compete fairly in all kinds of Assistive Technologies that will integrate with the common PC.
Unequivocally, Microsoft's expedient & disingenuous point about business model preferences is shown false in its fundamental assumption as the Governor's IT department has elected to keep its proprietry software in order to fulfill ETRM 3.5 responsibly for the benefit of citizens in government and across the Commonwealth.
Recent Comments