Slashdot Mirror


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."

9 of 120 comments (clear)

  1. Good news... by Philotechnia · · Score: 5, Insightful

    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.

    1. Re:Good news... by the_B0fh · · Score: 5, Insightful

      You may actually have a point, if Apple was trying to push whatever format keynote is, as a global *OPEN* standard.

  2. Wait and see by xra · · Score: 5, Interesting

    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...

  3. Brazilian says no too! by rsilva · · Score: 5, Interesting

    Same in Brazil:
    Brazil says no
    And OpenDocument is now a national standard!

  4. minor gripe by farlukar · · Score: 5, Informative

    Office Open XML, not Open Office

    --
    Ceci n'est pas une .sig
    1. Re:minor gripe by Fred_A · · Score: 5, Funny

      I think it's because of the name MOO-XML (Microsoft Office Open XML) that India voted against, since they found it offensive.

      --

      May contain traces of nut.
      Made from the freshest electrons.
  5. Details on Indian campaign by anivararavind · · Score: 5, Informative
    Some quick links on Background of this campaign:

    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

    "We unanimously agree on the disapproval of OOXML with comments. The same will be submitted to ISO," National Informatics Centre head and BIS technical committee chairperson Nita Verma said after a marathon meeting that lasted over six hours. There was no need for a voting as only Infosys Technologies and CSI supported Microsoft.
    Shame on You Infosys
  6. Re:Is ODF really much better? by Twinkle · · Score: 5, Informative

    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.

  7. Re:"Technical Issues" by MuffinSpawn · · Score: 5, Interesting

    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.