November 1, 2005 6:56 AM PST
Mass. officials criticize OpenDocument decision
- Related Stories
-
OpenDocument could 'turn everything inside out'
October 3, 2005 -
Massachusetts moves ahead sans Microsoft
September 23, 2005
Marc Pacheco, the chairman of the Senate Committee on Post Audit and Oversight, on Monday held a hearing to probe into the process that led to a mandate to make OpenDocument the standard document format for all commonwealth agencies in the executive branch as of 2007.

Marc Pacheco,
state senator,
Massachusetts
The policy, finalized in September, was developed by the Information Technology Division, which is part of Massachusetts' Office of Administration and Finance.
The IT Division said OpenDocument-based products will improve interoperability between systems and ensure long-term archiving of official documents. The specification is developed at standards group OASIS (Organization for the Advancement of Structured Information Standards).
There are commercial products that support or will support OpenDocument, including Sun Microsystems StarOffice, IBM's Workplace and the open-source product OpenOffice.
But the IT Division's policy effectively shuts out Microsoft Office because the dominant supplier of productivity software does not support OpenDocument at this point.
During the hearing, Pacheco voiced a number of concerns regarding the IT Division's decision. He called into question the IT Division's authority in setting policy, saying the IT Division acted "unilaterally," and he expressed concern over the cost of walking away from Microsoft Office. He also contended that OpenDocument does not sufficiently address the needs of people with disabilities.
During questioning, the IT Division's chief information officer, Peter Quinn, and General Counsel Linda Hamel defended the decision, arguing that the move to OpenDocument would be in the commonwealth's best interest. Quinn said a standard, "open" format, rather than Microsoft's "proprietary XML" format, will ensure that electronic documents can be read hundreds of years from now.
Pacheco then called on Alan Cote, the state's supervisor of public records, as a witness. Secretary of State William Galvin has responsibility for public records.
Cote sharply criticized the IT Department's decision, urging that
86 comments
Join the conversation! Add your comment
Bizarre! Microsoft's "proprietary XML" format is the defacto standard used by the general public and is so widely distributed that it stands the greatest chance of "being read hundreds of years from now" compared with any other format. Archives and agencies of government, as well as private software developers, will have the greatest incentive to maintain readability of Microsoft products centuries from now because the vast majority of information created at this time is stored in that format.
The drive toward "open formats" as a way to combat Microsoft's perceived monopoly is a venture (and a belief system) engaged in by private parties that governments and public agencies should not be taking sides in. The vast, vast majority of Massachusetts citizens have only the capability of exchanging or reading documents in Microsoft's proprietary formats because Microsoft products dominate the current marketplace; Massachusetts agencies such as Universities and colleges are using Microsoft products for their work and all of their documents exist only in those formats. It would be a disservice to the public of that state who must interact with their state government electronically to be inexplicably blocked from use of state documents unless they are willing to buy into a little-known, little-used software to access public records.
Isn't politics strange? MA was one of the states that continued the monopoly suit against MS after the federal government settled, and now some people are saying let's use Office because it's the only game in town.
The point of standards is to be able to share data to anyone regardless of what platform and applications they run. That is exactly opposite of what MS does.
MS does not, and hopefully never will set standards. All they do is lock people into their substandard, buggy garbage.
its citizens, not just the perceived majority. Standardizing to an
open file format ensures no one is left out. For those who use
Windows, downloading a free version of OpenOffice in order to
view OpenDocument formats is not too much to ask as
compared to telling non-Windows/MS Office users to go out and
buy one or both in order to view a proprietary (hence closed) file
format is absurd. All public electronic documentation (records,
etc...) should be easily accessible by all citizens. There's no
rational argument against it, PERIOD!
Open documents can be used, writen and read without having to license the code you derive from others. That is what makes MS propriety software a trap. If next year or ten, they decide no longer wish to support the current document format, your **** out of luck.
'"de facto" standards' have a way of excluding non-users of the
platform on which they are applied & in addition to the
tendency to reinforce the monopoly they have acquired.
If one were to follow your argument, citizens who don't use use
Pcs, a Windows operating system and Internet Explorer, for
example, should be made to follow these "standards" since
those are the ones used by "the majority" & the best example of
this rationale's fallacy is the large number of web sites, private
and public, that are inaccessible to users of a browser other than
IE 6 for Windows .Should this now happen with MS's XML when it
starts implementing more and more MS specific "tweaks", to the
point that it won't be accessible to nothing but the latest version
of Windows installed on hardware blessed by MS ?
This type of reasoning is exactly what the original decision was
addressing: the defense of fundamental freedoms, and the
independence from any proprietary technology that would put
the general public at the mercy of any corporate monopoly.
I dont see how your argument for the public to "be inexplicably
blocked from use of state documents unless they are willing to
buy into a little-known, little-used software to access public
records" can stand, as the software needed to read the Open
format not only is widely available, getting wider notoriety all
the time, and best of all, available for free &
That is Microsoft's shortcoming, not the Massachusetts IT Division's. If Microsoft wants in on the deal, all they have to do is abandon their proprietary file formats, or at least support OpenDocument under the "File -> Save As" menu. Microsoft is loathe to do this because it breaks a major shackle on their victims, er uh, I mean "customers".
> During the hearing, Pacheco ... expressed concern over the cost of walking away from Microsoft Office.
Excuse me? The small amount it will cost to implement the OpenDocument strategy will be recouped many times over by ditching Microsoft Office and eliminating their forced upgrade schedule.
It looks to me like Microsoft has bought themselves yet another politician. Way to go, Senator Pacheco - you've sunk to a new low....
plug-ins for Office that implement a "Save As"
OpenDocument for Office.
office software to another (or more properly, from one set of file
formats to another) would magically solve the problems of
structure and archiving.
Neither the Microsoft Office file formats, nor OpenDocument,
nor PDF, provide (or can provide) a complete structure for
information content, and all require specialized software for
interpretation and display.
PDF concerns itself primarily with text formatting, text
placement, and graphics placement. The information content
isn't structured at all. It doesn't much help to know that a certain
word begins at position (x, y) on the page and is to be rendered
in 10-point bold Helvetica type. For search purposes, plain text
is actually better than PDF. With many PDF documents, one
cannot put the text elements back into their logical sequence
from positioning data alone, so search breaks down. It may not
be possible to find words that are hyphenated; multi-word
phrases that are split across two lines; or words or phrases
whose elements have different formats.
OpenDocument at least preserves the natural sequence of text
items. But what people are raving about is the opportunity to
(manually) tag their documents with descriptive information.
Alas, there is no structure within these items. For example,
Pages 56 and 57 of the standard [ <a class="jive-link-external" href="http://www.oasis-open.org/" target="_newWindow">http://www.oasis-open.org/</a>
committees/download.php/12572/OpenDocument-v1.0-os.pdf
] say that items like Subject and Initial Creator may exist in a
document. They are text strings! What should I put in the
Subject field, if I bother to fill it out at all? Should I use a Library
of Congress subject, pick something from some other standard
list of subjects, or express the subject in my own words? What if
the document covers multiple subjects? Should I pick one, or
make a list? If I make a list, how should I delineate the entries?
As for Initial Creator, should I let the system insert my login
name, or should I manually enter my first name? Wait, maybe I
should add my last name. Perhaps <Last Name>, <First Name>?
Maybe my employee number or Social Security Number would be
more specific. How one fills out these fields has big
consequences for search. (We haven't even broached the
question of how to structure the core information content of the
file. So far the core content is just sequences of text, suitable for
keyword searching. There's no difference between my name,
used as the recipient of a business letter, my name, used inside
that letter, my name, used on a presentation slide, and my
name, stuck in the "Employee" column of a spreadsheet.*)
This brings us to the Microsoft Office file formats. They are no
better and no worse, structurally-speaking, than
OpenDocument. They preserve text sequence and can be tagged
with information items. People make much of the fact that you
generally need Microsoft software to interpret and display such
files, whereas anyone can write software to interpret and display
OpenDocument files. So what? Microsoft offers free "viewer"
utilities for Word, PowerPoint and Excel. A first-time user would
likewise have to download and install special software to read
OpenDocument files.
If you want universal, direct access, use plain text!
If you want something that looks the same as the original, use
GIF or JPEG!
If you want something that prints nicely, use PDF or PostScript
(and be sure to buy a printer that speaks genuine PostScript;
there aren't many on the market these days).
If you want reliable classification and search capabilities, define
a database!
Paul Marcelin-Sampson
Santa Cruz, California, USA
* This spreadsheet example makes me cringe. Many computer
users still think spreadsheets are databases.
Just kidding, P Mar :)
I can't see any other reason why someone would oppose switching
Public information to an open standard. Especially one that works
with free software.
I'm not against the purchase of the product, I am against the fact that if the MS Office format is used, the only product that can satisfactorily read MS Office formats is MS Office. If it were OpenDocument format, I could open it in OpenOffice, KOffice, Sun's StarOffice, et al.
Of course to say that Microsoft format is a standard or defacto is decidedly stupid. Microsoft changes their format more often than not. If Microsoft really wants to make a better document format then they need to get with OASIS and try to make that format the best it can be.
You know, people who use Word at home and rarely send out documents probably don't care about what format it's saved under. For those of us that are constantly passing documents around a standard format would be great. I think the day will come when we have that standard. I also think that, aside from Microsoft, most companies will adopt and use that standard in some form or another.
understands more than an experienced IT professional? Of
course the IT department made their decisions without a lot of
interaction with other agencies - does the department of
licensing ask the IT department about the license plate fees for
next year? Obviously one is more affected by the decision than
the other, but you get my point.
viewer" is an adequate alternative to spending hundred of
pounds on software ...
tell me where to download the free Word & Excel viewers for
Mac, for Linux, for BSD, for ...
The assumption that you can download the free viewer relies on
the assumption that everyone uses Windows, and not everyone
does. So how is it right for any government agency to require it's
citizens to run a specific operating system ?
Also, just because OpenOffice can (mostly) read office files now
doesn't mean that it always will be able to. MS can, and does,
change the formats regularly - officially to support new features,
but you can be sure that there's an element of spoiling tactics to
make life hard for anyone using a competing product or old
version. Not to mention that sooner or later they will impose
drm (digital rights management) onto people - and then it will
be a criminal act (cf DMCA) for people such as the OpenOffice
team to attempt to worka round the encryption.
Sooner or later, IF shortsighted and narrow minded people allow
them by apologising for their monopolistic practices, MS will
impose a system where you pay to use their software, and when
you stop paying you will no longer be able to use YOUR data.
Then you will be well and truly screwed, and it will be you own
stupid fault.
The way to prevent this happening is for all government bodies
to apply the same rules and insist on the use of open document
standards. If MS choose to stay away from the trough, there's
others who will happily take their place. If MS Office is so damn
good, MS have nothing to fear from a little healthy competition
on a level playing field - have they ?
Having used OO.o I find the idea that it can replace MS Office today laughable and even more laughable is the notion it will be cheaper.
What is also highly disturbing it that this measure is proposed without having done any research on the actual costs (beyond licencing) of such a change and the impact on visually impaired workers.
In other words, a typical example of why IT departments are unsuitable for making decisions like this.
Are you telling me I have to wite one? And if I'm not a programmer I have to spend thousands of dollars paying someone to write one for me?
Please, don't take my argument literally. What I'm trying to prove here is that the fact that a "standard" has no readers available for a specific platform is moot unless that platform has a significant market share, free or not. Linux on the desktop, as of today, has not. Well over 90% of personal computers run either Windows or OSX, and most of those that don't also have Windows as a second OS (not all, I know, there are some dedicated Linux users, as well as some FreeBSD users, etc.). But changing laws because of a convenience issue for a small minority of users (and don't tell me that minority is growing, that's specultaion about future trends, reallistic or not) is not a good use of resources, as long as there are some other means to access the documents wich guarantee availability.
However, a State administration suggesting a sweeping change like this should be concerned with such issues and are even required by law to be. But then, OSS advocates generally only apply those laws that suit them.
Aren't most accessibility issues handled by the client? Larger Fonts, Braille interpreters, Text-to-Speech? How is the file format significant in these type of cases?
***The use of OpenDoc formats do not require such a license.
Hey Pacheco, go look at your website sometime! It's a disaster as far as 508 compliance and accessibilty are concerned. Try addressing the needs of your constituents with disabilities by updating your website. Start here...
<a class="jive-link-external" href="http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=-1&url1=http%3A//www.marcpacheco.org/volun.htm" target="_newWindow">http://www.contentquality.com/mynewtester/cynthia.exe?rptmode=-1&url1=http%3A//www.marcpacheco.org/volun.htm</a>
When you get your site fixed, maybe then you can talk about acessibility with only slightly more credibility than you have now (which is none). In the meantime, don't venture into areas of technology and standards where it's obvious you have no background.
<a class="jive-link-external" href="http://news.com.com/Judge+Microsofts+music+player+gaffe+is+concern/2100-1012_3-5915405.html" target="_newWindow">http://news.com.com/Judge+Microsofts+music+player+gaffe+is+concern/2100-1012_3-5915405.html</a>
I applaud our state's IT department for making a decision that not only opens the door to saving on software procurement and archival costs, but also on training costs. Moving to Office 12 has been shown to have a higher learning curve (e.g. retraining costs) than moving to OpenOffice 2.0!
MS obviously has Pacheco's ear -- and maybe his wallet...
Privatization IS the biggest deficit to society. It took decades and smart people to devise standards at the state department level. Now, some bureaucratic-wannabees enter the local governments and burden the taxpayer with their costly changes.
For example, a state like PA decided to privatize road construction. The company bids low, then skims pavement to "make a profit". A State-controlled department is designed NOT to make a profit, but to be consistent.
With software, they lock you intto contracts that are annual, and require costly hardware (see proprietary or expensive..your choice) updates.
Microsoft is STILL a monopolizer. Tower of Babel: part 2.
The ISO standard only pertains to PDF 1.4, nothing else, many 3rd party apps that generate PDF's do not generate 1.4 PDF files but older versions btw.
Standards are extremely critical, especially in computer and computer related products. Without standards, web sites would have to generate seperate forms depending on what OS and browser you use. A properly written web server doesn't care what you are using. In fact, without standards, you would not be able to connect and to the web site because you are using windows and most servers run on linux.
Imagine what would happen without all the transport protocols. No easy way to get email or download a file. What would happen if every DVD manufacture had its own storage and encryption scheme.
ALl this arguing about how this is unfair to MS and Office users is pointless. MS made their bed, and they can climb out of it without any hassles, but they refuse to. That is on them.
It seems that a government mandate is a chance for open document standards to gain market dominance with the hope that it will trigger a domino effect as transactions move to and/or from the executive office, to the government agencies and to the public -- individuals or companies.
This is of course in the same hope that the government does align IT investments from the executive down to the smallest government agency.
My contention has always been that this government intervention is unnatural directly challenging the readiness of the public to suddenly have this need to invest on supporting the government's open document standard requirements.
At the same time MA makes an exception for PDF which is not a standard at all but a propietary product which is wholly controlled by one company.
Those are arguments imho which have not been adressed so far neither has the issue of cost or the impact on usability.
<a class="jive-link-external" href="http://blog.freesoftwaremagazine.com/users/d.sugar/" target="_newWindow">http://blog.freesoftwaremagazine.com/users/d.sugar/</a>
2005/11/01/the_blind_leading_the_blind_in_massachus
*****************************************************************
David Sugar
Post details: FSM: The blind leading the blind in Massachusetts
(11/01/05 11:11:37 pm)
FSM: The blind leading the blind in Massachusetts
by David Sugar
For the moment, I will ignore the false statement of some that
specifying ODF requires one to run OpenOffice. In fact, there are
many products which already do so, including Koffice, AbiWord.
Anyone that wishes to can produce OpenDocument compatible
software, including proprietary software vendors, such as Corel,
who have chosen to do so. Microsoft alone insists not that it is
unable to do this, but rather that it is unwilling, and it alone
demands the state choose its products and its document format
instead. In doing so, it is requesting that the state join with it in
an illegal business practice.
[More:]
The principle complaint that some have used is trying to claim
that ODF cannot meet state mandates for blind accessibility. As
it happens, I am interested in this very issue, under the
sometimes active GNU Alexandria project. It is true: work has
been slow, but the basic idea was to write a server that could
access government documents and web sites in their current
form, and then provide a voice rendered representation of said
document or web site to a user, either locally through a
soundcard, or over the public telephone network as part of an
automated government service. GNU Alexandria is licensed
under the GNU GPL.
Microsoft claims that its patent license trumps the rights of
others to access even their own documents and data, and while
it offers its patent encumbered XML schema under a royalty free
license, it requires others to both engage in giving their rights to
access their own data away as part of it, and specifically denies
the right to sublicense their patent. This would legally require
the state to exclude using GNU GPL licensed software that may
access state generated documents, at least if they are produced
and distributed in the Microsoft schema.
Clearly the result would be that less products and services,
including those to enable blind accessibility, will be available to
the state if it were to choose Microsoft's XML rather than an
open standard like ODF. However, accessibility is just a Trojan
horse. There is a deeper and even more disturbing issue in this
as well if Microsoft's patent encumbered XML schema became a
mandated state standard.
From the point of view of a software vendor, adopting
Microsoft's XML schema would mean that Microsoft, and not the
state, would determine under what terms vendors can offer
goods and services or even engage in business with the state.
This would be something like Ford saying to Massachusetts that
it can also purchase Hondas, or cars from other companies, but
only under terms and conditions that are set by and from
companies that are approved by Ford.
While governments can specify terms and conditions of sale on
their own in a non-discriminatory fashion, to adopt Microsoft's
XML schema would require the state to discriminate against
some vendors, and to do so at the request of another. This is in
fact illegal. It most probably violates state law, and certainly
constitutes a scheme to engage in illegal restraint of trade as
per U.S. Code Title 15. Not only would Microsoft's scheme make
the state of Massachusetts itself a party to criminal behavior, but
also potentially liable to any civil actions that may result.
Clearly to mandate ODF as a government standard the state of
Massachusetts would enable all vendors who may wish to offer
interoperable goods and services (including Microsoft). And it
would assure that the population, the very citizens of
Massachusetts to which the state serves, have a legal and
uncontested right to access state documents in any manner they
choose without restraint, including blind users by whatever
software they may happen to use. To do anything less would
represent a failure of the state to serve even itself, or its duty to
meet the needs of all its citizens on a fair and equal basis.
(C) David Sugar, 2005. Verbatim copying and distribution of this
entire page is permitted in any medium without royalty provided
this notice is preserved.
*****************************************************************