Brazil Appeals OOXML Decision
I Don't Believe in Imaginary Property writes "Brazil is now appealing the ISO's decision to standardize OOXML, following South Africa's lead. Interestingly, part of the reason this took so long was that Microsoft supporters at the meetings kept asking for delays because they 'weren't prepared' to discuss the issues raised. And the ISO as a whole is moving rather slowly, after that delay in releasing the DIS. But at least the ISO is also rewriting the directives in a special working group so this doesn't happen again. Of course, they'd have to be strict about making sure the directives are followed for it to help."
And I am from Brasil! I could see this coming... Open source is taken VERY seriously her...
\m/
I don't care how ISO re-writes whatever.
The problem was NOT that they didn't have the rules in place.
The problem was that the rules were NOT followed. And ISO was unable (unwilling) to rectify the "errors" once they had been committed. And ISO is still unwilling to identify the individuals within its organization who committed the "errors" and take any action.
Oh, wait... sorry, forgot whose pocket my congresscritter was in. Carry on :)
My blog. Good stuff (when I remember to update it). Read it.
Why one earth should Brazil wait for MS to be ready? It is Brazil that is (theoretically) in charge here, not MS. If MS is not ready by the set date, too bad. After all, this isn't supposed to me MS's format anymore.
The word that you can buy ISO standards.
Unless a bunch of heads roll and replaced non-corp people, the ISO would have a more credibility if they showed a price list than doing this.
Obama's legacy: (N)othing (S)ecure (A)nywhere and (T)error (S)imulation (A)dministration
This isn't discussed much here, but even opendoc was rushed. In my opinion opendoc was not yet ready to be a standard. It needed more time to sort out some of the more underspecified things. I'm not even going to comment about why I think of OOXML.
If I see the effort that was put in the C standard, compared to the current standards, I can only be very very sad.
ISO doesn't look good for having accepted the bribery.
What I don't understand is how Microsoft can keep pulling these sorts of stunts, and not suffer for it. What most people think is this: Office file format lock? Never realized formats could be open. WGA? Excused and forgiven. Bundling? Barely noticed, and when it is, feel that's a good thing. The anti-trust lawsuit? Delayed to death, then watered down to nothing. The CPU tax? Under the radar. DRM, and the attempt to suppress all non-MS multimedia formats? Mostly swallowed, because artists deserve a chance to make a profit. Though I understand Zune isn't doing too well. Miserable security? Fooled. Think that's normal, just part of life to have to live with Norton AV, and all the slowness and inconvenience. Vista? Jury is still out on that one, maybe this is the big one that will finally get people to question MS. As for this shenanigan, it will go unnoticed.
Intellectual Property is a monopolistic, selfish, and defective concept. It is "tyranny over the mind of man"
Fixing the errors slowly means that ISO is worthless.
And WAITING for someone to APPEAL the process means that ISO is worse than worthless. They cannot even manage their own internal systems. For a "standards" organization, that is beyond unacceptable. That means they produce corrupted standards.
As evidence, I give you OOXML.
Brazil did not appeal, only protested.
This difference may very well matter as far as ISO procedures are concerned.
Well you probably know most of this, but I'll re-iterate it just in case. Basically there are a lot of organisations, particularly governments, who have recently either declared, or have indicated that they're likely to declare, a policy to only use open formats in various situations (such as document storage). This effectively rules out native MS Office formats because they haven't been open.
Such declarations have been treated as great for open formats (such as OASIS), and Open Source, and users generally, because it's much easier to write/maintain applications, open source or otherwise, which implement and use open formats. In other words, if you use an open format, you're much less likely to get locked into a particular software vendor, such as Microsoft, whose closed formats require you to use their software to open them reliably and accurately (at least in theory and according to popular belief in management circles). For the same reasons, open formats tend to be much more useful when exchanging documents. For example, it means that I don't have to buy Windows, install Windows, buy Office, and install Office, just so I can open some kind of law change proposition that a government department might have forwarded to me in an Office 2003 format.
Microsoft has been in danger of losing control over the market, because Office's dominance relies at least partially on format lock-in, and a cascading effect between organisations of document exchange. Organisations often standardise on Office and its formats specifically because they deal with many other businesses and organisations that also use Office. If some key organisations (such as governments) suddenly decide to standardise on open formats, it'll likely have a similar cascading effect whereby other organisations that deal with them will also adapt their systems to be able to interoperate with those open formats. Standardising on open formats means that even if people somehow use MS Office to produce them, organisations that set such a policy won't necessarily be locked into Office any more, and neither will all the organisations that deal with them.
Microsoft's answer was to declare that they'd be standardising and opening the Office 2007 formats, so that the key organisations would still be able to buy and use Office. (They probably could have claimed that Office 2007 would just support an existing open format such as OASIS, but they didn't.) Microsoft wanted to get the ISO to rubber-stamp their new OOXML format to prove to governments and other organisations that it really is open. The ISO (aka the International Standards Organisation) is a highly respected organisation on approving standards, so to get an ISO stamp is basically to declare to everyone that yes it is an open standard and it's been carefully peer reviewed to make sure of this.
The problem is that a lot of people think that OOXML really isn't open, for a variety of reasons which you've probably heard of, and that it's just a tool for Microsoft to keep control of the market using what's really a closed format whilst using double-speak and claiming that it's open, so it'll get accepted. There's also a lot of belief that Microsoft manipulated the ISO and its voting member organisations in some very despicable ways to get their Office 2007 formats rubber-stamped as an "open standard" when it really doesn't deserve to be.
Ultimately this means that employees of governments and organisations which declared they'll be using "open" formats might still standardise their work on Microsoft's OOXML formats, using the ISO's rubber-stamp to justify what they're doing, even though OOXML doesn't actually offer the interoperability benefits that a real open standard should offer, and arguably nobody would win except Microsoft.