August 24, 2006 7:22 AM PDT
Mass. to use Microsoft Office in ODF plan
- Related Stories
-
Microsoft bends on OpenDocument
July 5, 2006 -
Mass. holding tight to OpenDocument
July 5, 2006 -
Massachusetts moves ahead sans Microsoft
September 23, 2005
As expected, Louis Gutierrez, chief information officer of Massachusetts' Information Technology Division, on Wednesday sent a letter seen by CNET News.com to advocates of people with disabilities. The letter was in response to their concerns about the commonwealth's plan to move to the OpenDocument format, or ODF, standard.
In addition, Gutierrez last week wrote to the state's Information Technology Advisory Board with an update on the OpenDocument format implementation plan, as had been planned.
Last year, Massachusetts caught international attention for its decision to standardize by January 2007 on ODF, a document format standard not supported in Microsoft Office.
Disability unfriendly?
The move was criticized by disability-rights groups, which complained that going to ODF-compliant products, such as the open-source OpenOffice suite, would not adequately address their needs. In general, Microsoft Office has better assistive technologies, such as screen enlargers.
Louis Gutierrez
Earlier this year, Massachusetts' IT division said it would adjust the dates of the OpenDocument adoption if the state could not find adequate accessibility products.
In his letter to disability-rights groups, Gutierrez said emerging Microsoft Office plug-ins will enable Massachusetts to stick to its standardization policy while meeting accessibility needs. Plug-ins act as converters, enabling people to open and save documents in the OpenDocument format from Microsoft Office.
"This approach to ODF implementation will fulfill our legal and moral obligations to the community of people with disabilities, acknowledges the practical requirements of implementation and enables the Executive Department to continue to pursue the benefits of using open standards for information technology," Gutierrez wrote.
The state had considered adopting other office suites, such as OpenOffice and StarOffice, but Gutierrez decided against those because they would not support accessibility requirements by the January 2007 target date.
State executive branch agencies will take a phased approach to using a plug-in. Gutierrez did not indicate which plug-in the state intends to use but that he expects them to be fully functional by 2007.
"Early adopter" agencies, including the Massachusetts Office on Disability, will use a selected plug-in starting in December of this year. The IT division will then move all executive branch agencies in phases to the OpenDocument standard by June of next year.
Gutierrez added that the state will consider OpenDocument format-compliant Microsoft Office alternatives as they become more mature.
Not "anti"-vendor
In his letter to the state's Information Technology Advisory Board, Gutierrez referred to the economic and political factors that have weighed on the state's planned move to ODF.
His predecessor, former CIO Peter Quinn, and other ITD officials were faulted by a state senate oversight committee for, among other things, not providing an adequate cost-benefit analysis. Meanwhile, Microsoft executives argued that the OpenDocument format favored the open-source business model over Microsoft's closed-source model.
Gutierrez told Massachusetts officials that keeping Microsoft Office on state desktops enables the state to "thread the needle" by adhering to a document standard created and supported by multiple software providers without being opposed to, "anti," any one vendor.
Because Microsoft Office and the forthcoming Office 2007 do not support OpenDocument natively, many expected the state to move to a different productivity suite.
Keeping Office, however, makes the ODF implementation more economical and less disruptive to end users, Gutierrez wrote to state officials. Microsoft started its own OpenDocument format plug-in effort earlier this year by sponsoring an open-source project.
"Technology that did not exist at the time of the policy formulation--namely various plug-in or translator components that can be added to Microsoft Office to allow it to read/write to OpenDocument format (ODF)--is at the heart of our near-term approach," Gutierrez said.
See more CNET content tagged:
Louis Gutierrez,
OpenDocument Format,
disability,
Massachusetts,
state
"As a point of reference here is an extract from a 1998 Lotus Development Corporation communication; Re: Concerning the issues with 1-2-3 that are talked about in the documentation you gave me, most of the issues are related to converting files between older and newer versions of product and converting documents between Lotus and Microsoft. Anytime a file is saved backwards or saved with an older file format than the format the file was created under, such as saving a 1-2-3 , 97 file for Windows 95 into a WK1 format for DOS, then naturally we are expected to loose certain features due to technology and features that are present now that were not present 8 - 10 years ago. Similarly, if we try to convert a file from Lotus into Excel or Excel into Lotus, due to differences in the products not every feature will be converted perfectly with the file filters that are available. Both Lotus and Microsoft create similar spreadsheet programs; however, there are several differences in both programs and these differences will remain to distinguish the products apart. We do try to design conversion filters that will allow as much of the file formats as possible to be exchanged and converted without disrupting the actual file design and format.
In one of your letters you made mention of the @IRR and @ERR functions in the 1-2-3 product. By design the @IRR (notably "absent" in Open Office) will calculate the Internal Rate of Return; where the @ERR is used in conjunction with other formulas, posted was an "ERR" showing an error was received in the calculations. As far as I can see in the program I cannot find an @ERR function that will allow us to calculate an Economic Rate of Return"... note carefully what was stated in the latter; "there are several differences in both programs and these differences will remain to distinguish the products apart", so, just where do the other OEM's products factor in, in this
Massachusetts OpenDocument equation! :-\
If Microsoft isn't a monopoly, we should retire the term.
Another brilliant government decision... nevermind choosing a product that works, when you can mash together two seperate pieces of technology, increase the overall cost, and maintain your ideological fascination with "open-anything." Talk about throwing a bone to the open-source community at the taxpayer's expense! sheesh.