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.
The OOXML-standardization backstory is pretty convoluted, so I'm not sure I can give an accurate summary, but as far as I can tell this is basically another round in the ongoing fight that seems to have, for some reason, been more active in Norway than elsewhere. The article mentions that the main author of this report was involved in the controversy at the ISO, and there was also a related controversy in one of Norway's national standards bodies.
Strange, that the name of the consultancy is Hypatia. She, after all, was a mathematician-philosopher who ascribed to Plotinus's ideal... that empirical research is inherently flawed, and only logic and mathematics can achieve truth.
I mean, there's a clear relationship here that I find very amusing. Microsoft's OOXML, while sure to be empirically more interoperable with most users due to the pervasity of Microsoft Office, is not logically more interoperable due to the nature of what MS has done to the "open" standard.
Delicious allegory.
[1] DIFI is the Norwegian Agency responsible for the decision.
"Trolls they were, but filled with the evil will of their master: a fell race..." -- J.R.R. Tolkien on Olog-hai
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.
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
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.
Were you not around when Microsoft bribed and stacked the ISO meetings when voting for OOXML as a "standard"? Not only that, but it doesn't pass any kind of rigorous review as a standard... it is all but an XML representation of the original .doc format, just re-jiggered around, and is so convoluted that nobody but Microsoft has a hope of actually interoperating with it properly. And by the time someone might do so, they've got the next version out.
Seriously, just google around a bit:
http://arstechnica.com/old/content/2008/10/norwegian-standards-body-implodes-over-ooxml-controversy.ars
http://en.wikipedia.org/wiki/Standardization_of_Office_Open_XML
My blog. Good stuff (when I remember to update it). Read it.
Amusing little story:
"Norwegian" is split into two languages. "Bokmål" and "Nynorsk". Directly translated one is Book-language and New Norwegian.
Bokmål is based on danish with norwegian pronunciation (overly simplified of course).
Nynorsk is based on a multitude of dialects from a large area of Norway.
Microsoft used to only support office for Bokmål. They were told as long as it wasnt available as Nynorsk it could not be used in the public sector. They quickly produced a localized version in Nynorsk.
So the market has to be of -some- importance.