Microsoft denies OOXML has 'proprietary hooks'

As Australia and various other nations prepare to vote on whether Microsoft's Open Office XML becomes an ISO standard, the Redmond giant is attempting to downplay fears that OOXML adopters will be hooked into the company's technology.

Microsoft has come under attack recently from organisations such as the Free Software Foundation, which claims the OOXML specification includes "plenty" of proprietary code.

Earlier this week, the president of FSF's European operations Georg Greve said: "We've found plenty of proprietary material in OOXML so far. Governments could get locked into formats where they don't have control over the data. OOXML is dependent on implementations by Microsoft, so to use OOXML is essentially betting on the continued existence of Microsoft. Governments would also be dependent on Microsoft in a political sense".

However, Gray Knowlton, Redmond-based group project manager of Microsoft Office, told ZDNet Australia in a video interview that the company is hoping OOXML will become a standard precisely to lose any proprietary hooks.

"It's a very popular thing to say, that Microsoft owns or controls parts of these specifications -- the entire purpose of taking this format into a standards-based environment is to avoid this.

"It is precisely to ensure that people have the ability to read and write documents in this format, free from encumbrance of something Microsoft would own.

"We want to move into a standards based environment for the documents format because so much of the heritage and the history and the records of every country in the world are wrapped up in the documents that are created by our products that have used the binary file formats of Microsoft Office in the past," said Knowlton.

In the video, Knowlton claims that Microsoft wants to offer users a choice.

"We want to move this into a standard because people can get out of this environment of being locked into a proprietary file format, they have a little bit more choice about how they would choose to approach an archival or document management solution or other things that are involved," he said.

FSF Europe's Greve also described the OOXML specification as "extremely bad" because of rounding errors.

"As a technical specification, OOXML is extremely bad. Rounding errors are not normal in modern applications. If I was a financial organisation, or a governmental organisation that deals with finances, I'd be concerned about rounding errors," said Greve.

Advertisement

Talkback 5 comments

  1. Offers users a choice? Sly Coder -- 31/08/07

    Aww, get real Microsoft!

    When we create standards for train lines, or power plugs, do we push standards bodies to adopt multiple, incompatible standards? Not if we're sane. Not if we're looking out for the best interests of consumers.

    Look, you're free to create your own bastardized 6,000 page XML format spec. Just don't expect the world to be happy if you try and ram it through (with bribes it seems**) as an open standard.

    Especially when a perfectly viable, and extant, ISO open standard exists: ODF
    http://en.wikipedia.org/wiki/OpenDocument

    **The days of IT news being reported by yutzes like John Dvorak in PC Magazine are long gone. Those were the times when you could silence critics and pay off the journos. If you think that your astroturfing and slimeball tactics will continue to work in the days of the Internet, think again.

    Don't forget, the geeks who built the Internet are the self-same who are taking apart your software business, piece-by-piece, with Linux/FOSS. Consider it pay-back for 20 years of monopolistic practices.

    1. Multiple standards Anonymous -- 31/08/07

      Err, that's a joke, right? There ARE multiple standards for train lines and power plugs...

    2. Well yes Sly Coder -- 31/08/07

      But that's a screwed up historical mistake. Surely we've learnt from those mistakes. Let's not make the same mistake with doc formats.

  2. An example of just how broken OOXML is Anonymous -- 01/09/07

    As noted by a former Microsoft staffer:

    The work is published as a set of experiments. The first experiment takes a trivial spread sheet created with Microsoft Excel 2007. The next step is to unpack the Excel generated "standard OOXML" and make a trivial edit to it and repack it. Excel then complains violently about the result (i.e. to the point of not reading the document).

    This is a catastrophic failure on two fronts for Microsoft's "standard":
    It means Microsoft Office DOESN'T ACCEPT WELL FORMED OOXML documents not produced by Microsoft Office. This would be very bad for all those customers that believe the marketing and think they're buying a product implementing a "standard" that will [someday maybe] be supported by multiple implementations.
    It means the Microsoft OOXML specification has sufficient problems in what it isn't saying in that implementors can't implement it. (Changing a one character field in human readable XML with an editor is about as basic as it gets for implementation.)

    Game over. A standard that can't be implemented is WORSE THAN USELESS. It really demonstrates that this standard they rammed through ECMA is nothing more than a vendor's product specification. The rest of the experiments are equally telling in terms of the apparent use of product features outside the specification, etc.

    http://stephesblog.blogs.com/my_weblog/2007/08/microsofts-fail.html

  3. mixed messages Anonymous -- 03/09/07

    Interestingly an ooxml advocate at the SA meeting said that "we should know that there will always be proprietary material in MS formats, thats just life, and MS clients understand that...."
    Fair enough then, but why then call it OPEN xml and try and propose it as a standard if the intent is not to make it interoperable?

Add your opinion


Latest Videos

ZDNet's CIO Vision Series

Department of Defence | Greg Farr, CIO (part two)

In the second part of his interview, Defence CIO Greg Farr talks about outsourcing, the skills crisis and reveals his most urgent IT priority.

Sponsored content

Power Centre - Content from our premier sponsors

Blogs

  • Angus Kidman I'm a celebrity, don't back me up
    Celebrity comes with its perks — free alcohol, better-looking partners, lots of holiday time — and disadvantages — constant media intrusions, being forced to appear in films with Eddie Murphy for the long-term good of your career, and having to do mindless radio interviews with angry men who've been awake since 4am.
  • Array Lies, damned lies and telco stupidity
    Earlier this month, Telstra put out a press release trumpeting that it's come up with a new phone coaching service to help people who are "bamboozled" by their mobiles. Another excellent example of wrongheaded thinking from the mobile industry.
  • Array Dear carriers: More walking, less talking
    Sometimes, a well-placed and well-timed letter can make all the difference. Other times, it can make no difference at all — and even hurt your case. This week's missive by the Competitive Carriers' Coalition, I would suggest, falls into the latter category.
  • More blogs »

Tags

Back to top

Featured