OOXML Rumored to be Approved, Announcement Wednesday

dominux writes "Rumors are already circulating that Microsoft's OOXML has been voted in by the standards board. The Open Sourcerer claims to have results of the ballot on dis29500. According to the site Microsoft managed to flip enough countries to make it stick. 75% of the P members who didn't abstain voted for Microsoft (That is 58% of all the P members). 14% of all the P and O members voted to disapprove it, this includes all the new O members that joined just in time to cast their vote. Norway has asked that their vote be suspended due to voting irregularities, but it would take more than that to make a difference to the result. ZDNet is still playing it cautious, noting that an announcement either way is set to be made on Wednesday."

Comments

Basically...

[behe101]

if this is approved we can safely assume ISO is corrupt.

ISO dead, blog at 11

[ShieldW0lf]

So, ISO got an extremely high profile black eye in the credibility department from which it may never recover. Developers and purchasers who are not able to make their high-level decision makers realize that they shouldn't early-adopt OOXML despite this certification are going to end up being held responsible for the massive clusterfuck that eventuates. Information will become a lot harder to keep organized and accessible in countries that adopt this messy non-spec as a standard, and global productivity will shrink due to the ensuing chaos.

Thanks MS.

Re:ISO dead, blog at 11

[johnw]

Seriously.. what's the problem with it being approved? You mean you haven't been following the story? You should read up on it a bit.

Technical issues? Yes, dozens of them.

Lack of clarity? Yes, in spades.

There are hundreds of other standards that fall into those categories as well, yet they are still standards. Go on - name one that even comes close to Microsoft's pseudo-standard. The OOXML "standard" is so unlike a real ISO standard it's not true.

But no one cried corruption until now.. This looks dangerously like a feeble attempt at astro-turfing.

Re:Let's see

[ShieldW0lf]

Lets all vote that it's not fair to need to eat, then we can stop dealing with those messy farms.

Oh, wait... democracy doesn't override cold hard reality, does it. My bad.

Looks like a forgery

[Adaptux]

The claimed results of the ballot on dis29500 document looks like a blatant forgery to me. For example, the implied claim about the process having been managed by ISO/CS ("Central Secretariat") ist wrong; the process is managed by ISO/IEC ITTF ("Information Technology Task Force"). Also, there is no defined "Voting stage" of "enquiry" in the JTC1 directives, etc etc.

Re:With thanks

[Tom]

what company wouldn't have done in their position?

But it is to ISO's massive, disgusting and probably reputation-destroying shame they they simply laid back and allowed themselves to be corrupted, defiled and sodomised by a large multinational. And they didn't even get a kiss afterwards. Yes, I also put all the blame in a rape on the victim, usually. Most of them just don't really struggle, do they?

Now seriously, ISO is fucked (even if this is an April Fools news), but MS is still the party that did it. The blame should be on them.

Waiting until the 2nd

[mlwmohawk]

Well a few points:

If this is an April fools joke it isn't funny.

If this is real and the (gasp) "standard" was approved, we should all start calling it the "Fools Standard" in everything we write, thus putting the proper "spin" on it.

Seems to be true though...

[filbranden]

Unfortunately, it seems to be true.

I've been tracking this for the last few months, and it's clear that this was essentially a victory of corruption over merits.

What's being said now is that this will be a pyrrhic victory for Microsoft. Many will discredit this standard (even with the ISO stamp on it) because of the history of corruption that lead to its approval. Those who already disliked Microsoft will only hate it even more and become more vocal.

I hope this whole process served to show the world (once again) what "business as usual" means for Microsoft.

Re:Seems to be true though...

[ozmanjusri]

What's being said now is that this will be a pyrrhic victory [wikipedia.org] for Microsoft. Many will discredit this standard (even with the ISO stamp on it)

That is the goal.

Microsoft does not like being held to standards. The devaluation of ISO is as big a win for them as the acceptance of MSOOXML.

Penalty for cheating == break even?

[walterbyrd]

So when msft is caught red-handed, like in Norway, or Sweden, then that one particular vote is not counted. But it is assumed that everything else is just fine, in spite of dozen of irregularities?

That doesn't really seem fair to me. It seems like, if you cheat, then you either win, or at least break even. It's like saying that the penalty for shop-lifting is that you have to put the stuff you stold back.

In fact, it seems like, in the case of Norway, msft did better than break even. Instead of a "yes" msft rigged a "nothing" which is better for msft than a "no."

Considering the massive number of irregularities in the OOXML approval process, I think OOXML approval should be put on hold, until an investigation can be completed.

Unfortunately

[Chrisq]

Unfortunately to Microsoft discrediting ISO would be a bonus. If there are no reliable standards bodies then it just wakens the position of people trying to argue the advantage of standards compliance. For MS the best outcome would be that people would say "standards mean nothing anyway", because the alternative to de facto standards are de jura - and Microsoft sets most of these.

YEs it is

[Chrisq]

Why?
All they have to do is implement more than everyone else, then change the "standard" so that others are not compatible.

Re:Not all bad

[erroneus]

Here's why that's not very likely:

1. Microsoft's implementation of other standards is often [intentionally] broken. One needs to look no further than HTML for evidence of that.

2. As you pointed out, the Office 2007 documents do not comply with the OOXML spec, so currently, no one supports a rigidly defined implementation of OOXML. But it's rather telling that many "yes" voters are discussing "changes" "growth" or "evolution" of the standard. ISO does not support this notion. Standards are rigidly defined and adhered to. If there is a change that needs to be adopted, a new standard is created. But as evidenced by all prior Microsoft behaviors and methods, they can't leave a file format alone for 5 minutes, let alone 'forever.' For Microsoft and ISO to be compatible, they'd have to have a new standard adopted with every new service release of their office and Windows products. (Either that, or ISO will have to change everything it stands for... which has arguably happened already)

3. One of Microsoft's most identified behaviors has been to keep changing standards, methods, procedures and behaviors of its products and protocols. Some would suggest that is to prevent people from being "too compatible" and for the longest time, the Samba project, for example, was having a difficult time keeping up with the changes. (They did, and it would seem Microsoft ran out of ways to break SMB/CIFS to thwart Samba as that doesn't appear to have been an issue lately) Microsoft is more inclined to move the mountain closer to them than they would be to move closer to the mountain.

"Hope" and Microsoft have been words that rarely connect. I have hoped Microsoft would behave better than it does for quite a long time. they simply won't. The tragedy is that they have the resources to make really good stuff. They don't want to do it that way. Instead, they'd rather use tricks and tactics to get their way about things. It's really unfortunate that they'd take the less honorable approach, but clearly by keeping the competition suppressed, they have been far more successful which is good for share holders... just not so good for the rest of "technology" and the world that uses it.