Slashdot Mirror
Study Says OOXML Unsuitable For Norwegian Government
angry tapir writes "Microsoft's XML-based office document format, OOXML, does not meet the requirements for governmental use, according to a new report published by the Norwegian Agency for Public Management and eGovernment (DIFI). The agency wants to start a debate over the report as part of its work on standards in the Norwegian government. (As we discussed a week ago, Denmark has already decided to choose ODF over OOXML.)"
If Microsoft can get enough lock-in, even a small market can end up making them a lot of money with long term support and maintenance.
Taxation is legalized theft, no more, no less.
Because software costs money to make; but virtually no money to reproduce.
The Norwegian government likely spends somewhere between some hundreds of thousands and some millions on software that must interpret their chosen document format(ie. actual copies of an office suite, server-side components that generate documents in response to web input, data archive widgetry that needs to be able to read inside the files it stores, etc.) Those who must exchange documents with the Norwegian government presumably spend some millions more.
If that money is being spent on ODF-supporting software, the cost of ODF-supporting software goes down for everybody(or, more precisely, if they chose to build on OSS foundations, the cost for everybody stays the same, and the amount and quality available rises. If they end up going with something commercial, that commercial offering now has more customers across the same roughly fixed cost of development).
It isn't so much that Norway is a vital source of Microsoft revenue, as they likely aren't. It's that their future software demand is going to subsidize improvements to Microsoft's competitors, rather than being high-margin purchases of licences to code that Microsoft has already developed.
OOXML.. I'm a regular user of Openoffice. I'm pretty interested in it succeeding, and was pretty aware of the OOXML v. ODF issues a year ago. And still, when I saw the title of this article, my first thought for 10 seconds was... oh shit.. they're ditching Openoffice in Scandanavia! Almost like someone deliberately named OOXML to create a little confusion, isn't it?
When trying to debunk an obvious lie (such as "OOXML is a standard"), one reasonably visible dis-believer might be enough. All governments and organizations believing, or pretending to believe, that OOXML is a standard now know they're fools, and/or not fooling anyone.
Plus hopefully the Norwegian government has produced a document explaining their position, that will be quotable for reference.
The Cloud - because you don't care if your apps and data are up in the air.
Doesn't interoperability mean ability to work with diverse systems?
If users of MS Office share documents, that's not interoperability since they all use the same software family. You have to look at users who transfer documents back and forth between diverse software systems, eg MS Office, Open Office, Lotus Symphony, AppleWorks, etc.
Interoperability is about making faithful conversions easy.
Why does this matter so much? Once one (now two) countries reject OOXML, it means it cannot become *the* international/European document standard for the public sector.
Please help publicise swpat.org - the software patents wiki
To summarize; Microsoft sabotaged the standards body with their own people to solidify OOXML as t h e standard. Despite their boldness in daylight to buy a standards body, the irony is; of all groups of people, governments are recognizing Microsoft to be nothing more than a Mobster/racketeer in shrink wrap.
My karma is not a Chameleon.
There are many parts of the OOXML 'standard' which refer to documents not available to the public, or which say something along the lines of 'do this the way office 97 does it'. A standard must contain all the information necessary to implement it, or else it is incomplete and thus not a standard.