It's offical: Massachusetts goes with standards based office software

The point of this article is simple. Going with standards based solutions
just makes sense. It prevents vendor dependence (and vendor abuse) as well
as helps prevent interoperability problems.


"The bottom line is this: whose documents are they? Do the people of
Massachusetts have the right to control their own documents? Does a
governmental agency have the right to decide what software it wishes to
use, particularly if it believes it can save money? If it does, then all
the hue and cry is pointless. And the real issue, as Kriss pointed out, is
the issue of sovereignty, and the very important issues of access and
control not only now but also in the distant future."

http://www.groklaw.net/article.php?s...50923142231938

Imhotep

Imhotep

Imhotep wrote:

> The point of this article is simple. Going with standards based solutions
> just makes sense. It prevents vendor dependence (and vendor abuse) as well
> as helps prevent interoperability problems.
>
>
> "The bottom line is this: whose documents are they? Do the people of
> Massachusetts have the right to control their own documents? Does a
> governmental agency have the right to decide what software it wishes to
> use, particularly if it believes it can save money? If it does, then all
> the hue and cry is pointless. And the real issue, as Kriss pointed out, is
> the issue of sovereignty, and the very important issues of access and
> control not only now but also in the distant future."
>
> http://www.groklaw.net/article.php?s...50923142231938
>
> Imhotep

A open letter from kde to Microsoft over the issue of Massachusetts ditching
MS Office...

http://dot.kde.org/1127515635/

Im

Imhotep