India Decides to Vote "No" For OOXML
Indian writes to mention that after an intense meeting at Delhi's Manak Bhawan the 21-member technical committee has decided to vote against Microsoft's Open Office Extensible Mark Up Language (OOXML) standard at the September meeting of the International Standards Organization (ISO). "Microsoft said it respects the government's decision. 'There were only three options "Yes", "No" and "Abstain" to be taken and we respect the government's decision,' Microsoft's legal affairs head Rakesh Bakshi said. He, however, added that India's 'No' vote will become a 'Yes' if Microsoft is able to resolve all technical issues with OOXML before the ballot resolution committee of ISO."
The last time I looked at the OOXML spec, it was the most non-spec spec document I had ever seen. It was chock full of references to Microsoft's proprietary legacy code, failing to provide the details that would really allow for an open implementation. The only thing Microsoft opened up was letting developers know exactly what functionality they weren't being allowed to properly use. If this spec had been passed, it would have been an open invitation for more anti-spec specs down the road. Meanwhile, is it really a coincidence that with the advent of applications like OpenOffice, Office 2007 featured a complete revamp of the Office UI? Methinks not... Microsoft is the functional equivalent of that guy at the bar that can pick up just about any women he pleases, but is cursed with commitment issues that keep anything meaningful from developing. Bring something real to the table, billg.
Won't be surprised if a MAJOR investment from Microsoft in India is announced in the coming weeks and coincidentally the indian opposition to OOXML softened...
Germany's DIN has voted to vote YES (sorry, article in german) at ISO.
Same in Brazil:
Brazil says no
And OpenDocument is now a national standard!
You know what the worst part is? Even if there weren't any "technical issues," OOXML shouldn't be a standard because ISO already has an existing standard covering the same thing! And that preexisting standard leverages other standards (eg. SVG, MathML) while Microsoft's travesty doesn't! So even regardless of "technical issues," making OOXML a standard is ludicrously stupid!
"[Regarding the 'cloud,'] ownership was what made America different than Russia." -- Woz
Office Open XML, not Open Office
Ceci n'est pas une
This is the Right Thing to have happened. MS OOXML is not a standard:
- 6000 pages and still not a complete standard
- paraphrased: 'to comply with standard, you must implement these hundreds of features from previous versions, which are not in this standard, and which may be covered by patent'
- WTF!?!
Further evidence of MS's bad faith:KLAATU, BORADA, NIh*ahem*
Genesis 1:32 And God typed
Depending on one's definition of "technical problems" then there's a lot of patching to do because many of the problems are very deeply embedded. I don't just mean the infamous "auto space like Word 95" tags, but the lack of support for dates before 1900, the redefinition of the colourspace to clash with existing ISO standards and the hard-coded definition of non-working days to be Saturday and Sunday (which they are in Western culture but aren't in the Arabic world). A fairly comprehensive list of OOXML's failures is at http://www.grokdoc.net/index.php/EOOXML_Objections _Clearinghouse and it's an editable wiki as well.
ODFAlliance India Mirror on Wordprocessing-ML subcommittee discussions
Issue List submitted to the Technical Committee by the WordProcessing ML Sub Committee
Why ECMA OOXML is not a Free Document standard :Paper By Dr. Nagarjuna
My Earlier Post : Defeat M$ efforts to push Ecma OOXML in Bureau of Indian Standards (BIS) Economic Times Report says
Shame on You InfosysNo, Microsoft's statement was:
"We provided no financial incentives to Paramount or DreamWorks whatsoever,"Amir Majidimehr, head of Microsoft's consumer media technology group. Microsoft (and others) provided money to the HD DVD Promotion Group. The HD DVD Promotion Group provided money to the studios.
It's called "plausible deniability".
"I've got more toys than Teruhisa Kitahara."
great. another indicator that india has a really developing and conscious i.t. crowd.
Read radical news here
Some of those countries "participating" are observers.
This is the best explanation of the voting process I have seen.w ound.html
http://www.robweir.com/blog/2007/02/merely-flesh-
"I've got more toys than Teruhisa Kitahara."
ODF is fully specified, OOXML is not.
There's no comparison, ODF is a complete description of a document, OOXML has things like "use word 95 rules" or "important undocumented binary blob here". OOXML is a Trojan horse.
They did this same sort of thing in the web services realm with WS-ResourceTransfer even though WS-ResourceFramework already existed and did everything WS-RT does. They claimed it was a merging of their stuff (WS-Transfer) with WS-RF, but it was really a coup. With WS-RT my original feeling was that they simply didn't want to recode everything to a new standard, so they just forced everyone to accept a superset of what they were using. That's annoying enough as it is, but I can't help thinking it's more than that despite my skepticism of conspiracies.
I can only assume that Microsoft's stance on the open source community is to simply use their clout to get everyone to use their specifications, thus making it seem like they're cooperating with others. In reality they're just forcing their Johny-come-lately garbage down everyone's throat as usual. Unfortunately people want Microsoft on board with standards, so they apparently keep getting duped into doing whatever Microsoft wants them to do in the spirit of pseudo-cooperation. Yes India said "no" to OOXML, but it was qualified with room for negotiation. Don't think that this is a win for open standards just yet. It's not an open standard if only one company gets to dictate what that standard is.
"In reality they're just forcing their Johny-come-lately garbage down everyone's throat as usual"
It's worse than that.
Consider a manager making a decision of which implementation of a standard to use. Is that person going to select the implementation by the originator of the spec or an implementation by a third party? It's about using the standard to ensure market dominance and put any competition on uneven footing.
MRSH-Recording device, corned beef sandwich with kraut, seafaring bird, and the foamy top of a beverage.