Slashdot Mirror

← Back to Stories (view on slashdot.org)

Roadmap To the OOXML Process

Posted by ryuzaki0 on from the pay-no-attention-to-the-coming-media-blitz dept.

I Don't Believe in Imaginary Property writes "With all the pieces floating around on OOXML, it's been hard to get a good sense of where it is in the standardization process. Fortunately, IBM's Rob Weir has a provided us a road map. Today Microsoft is due to submit its set of proposals for resolving the 3,522 comments to JTC1, which controls OOXML. Tomorrow or soon after, we can expect a media blitz heralding these 'changes,' as numerous reporters are, reportedly, being flown to Redmond. But all those recommendations are non-binding, because only JTC1 can change the standard and that happens during the Ballot Resolution Meeting. And even if all of the recommendations are adopted, no one has to change their vote. The BRM, where all the real work will happen, isn't until February 25-29. Within the 30 days after that, everyone will be able to reconsider their vote. That's when we can expect the real fireworks."

6 of 48 comments (clear)

  1. Bureaucracy by Dan+East · · Score: 4, Insightful

    The sad part is that most of the great advancements in computing, be it software or hardware, were not the result of a bureaucratic process such as this.

    Dan East

    --
    Better known as 318230.
    1. Re:Bureaucracy by Simon+Brooke · · Score: 4, Insightful

      The sad part is that most of the great advancements in computing, be it software or hardware, were not the result of a bureaucratic process such as this.

      This isn't a great advancement in computing. It's a convicted monopolist's attempt to lock the world's documents up in a format which it can change arbitrarily at will to stifle competition.

      --
      I'm old enough to remember when discussions on Slashdot were well informed.
    2. Re:Bureaucracy by badfish99 · · Score: 2, Insightful

      So, if it's "just another format", how come Microsoft are paying for reporters to fly to Redmond? How come Microsoft have bribed whole countries to take part in previous votes? If we take your attitude, Microsoft will take over the world while we're not looking.

  2. Comparison by Ethanol-fueled · · Score: 4, Insightful

    OOXML is to ODF as the Zune is to the iPod: relatively incomplete, too hastily implimented, too late, and ugly.

    1. Re:Comparison by Anonymous Coward · · Score: 2, Insightful

      Hmmm...I'm thinking that if YOU'RE thinking the Zune is a good thing (tm), then YOU, sir, are the fanboi.

    2. Re:Comparison by ColourlessGreenIdeas · · Score: 2, Insightful

      This fails to deal with the main problem.

      Most criticisms of OOXML deal with the fact that it is a hastily implemented pile of incomprehensible rubbish that no-one in the world will ever implement correctly and that Microsoft is allowed to change at will without consultation. However, this actually utterly misses the point of the problem of OOXML, and the reason why MS is so opposed to ODF.

      The issue is that ODF forbids you from embracing and extending while OOXML allows you to. This means that if you've got an ODF document and an ODF reader, you can read the document. This is not true for OOXML as anyone (MS) is allowed to put random rubbish in the middle of the document, that a different application might not understand.

      MS criticises ODF for missing features, but never make clear that this 'problem' cannot be fixed by adding features; they are in fact criticising ODF for standardising what constitutes a valid ODF document.

      --
      In soviet russia stale jokes recycle you!