Slashdot Mirror


RTF Vs. OOXML

Rob Weir has an interesting essay comparing the viciousness of RTF and OOXML: "The [document format standard] concerns of 2004 (or 1995 even) are very similar to the concerns of 2007... 'RTF is defined as whatever Word saves when you ask it to save as RTF.' This should sound familiar. OOXML is nothing more than the preferences of Microsoft Office. Whenever Word changes, OOXML will change. And if you are a user or competitor of Word, you will be the last one to hear about these changes. The coding of Office 14 a.k.a. Office 2009 is well underway. Beta releases are expected in early 2008. But are file format changes needed to accommodate the new features being discussed in Ecma? No. Are they being discussed in ISO? No. Are they being discussed anywhere publicly? No. By owning the 'standard' and developing it in secret, in an Ecma rubber-stamp process, Microsoft rigs the system so they can author an ISO standard with which they are effortlessly compatible, while at the same time ensuring that their products maintain an insurmountable head start in implementing these same standards. Is this how an open standard is developed?"

2 of 141 comments (clear)

  1. Office 2007 not even compliant by Bayesela · · Score: 5, Interesting

    On top of OOXML being developed in a closed environment, MS Office is not even using the proposed ECMA or ISO spec, they including all types of tie-ins. This article explains more: not even compliant

  2. Re:well, not effortlessly by Maxo-Texas · · Score: 4, Interesting

    That's really not the case.

    In fact, look up how it went down for Word95 and Windows 98.
    Word violated the api standards but was given the "approved" mark anyway.
    Corel which followed the standards was much slower.

    Microsoft cheats all the time. They are commensurate scammers.

    Sometimes, it feels like the world is crazy because no one seems to recall things like
    1) specifically checking if DR Dos was installed- and if so give a hard installation failure.
    2) "Dos isn't done until Lotus won't run"
    3) Doublestac
    4) The entire "95" certification scandal.
    5) The *numerous* partnerships where they robbed every bit of technology from the technology partner and then brought out a competing product.
    6) The numerous times that they added a 50 to 60% functional but "free" version of something of a competitor's product to the operating system.

    and so many more examples like this.

    They are extremely competitive scammers. Which is okay if you own their stock. But not okay if you want to do something for the common good like standard.

    --
    She was like chocolate when she drank... semi-sweet at first and then increasingly bitter.