Linked by Thom Holwerda on Mon 4th Dec 2006 22:26 UTC
Novell and Ximian The first fruit of the recently announced Novell/Microsoft interoperability agreement arrived on Dec. 4, with Novell's announcement that its version of the OpenOffice productivity suite will now support the Microsoft Office Open XML format. The release candidate of Novell's modified version of OpenOffice.org 2.02 is now available for Windows for free download by registered Novell users.
Thread beginning with comment 188092
To view parent comment, click here.
To read all comments associated with this story, please click here.
n4cer
Member since:
2005-07-06

OOXML is dependent upon Windows in the same way ODF is dependent upon Windows. Both formats allow the embedding of elements that may not have a renderer for the specific platform which you're using. The solution in both cases is obvious -- if portability is your main concern, don't include non-portable elements. If you just need to read the document, you may still do so in many cases, with the document viewer ignoring elements it can't parse.

Is there any valid challenge to OOXML's openness from someone not pushing ODF?

Reply Parent Score: 4

hal2k1 Member since:
2005-11-11

//OOXML is dependent upon Windows in the same way ODF is dependent upon Windows. Both formats allow the embedding of elements that may not have a renderer for the specific platform which you're using. //

This is correct, but disingenious.

ODF does indeed have dependencies external to ODF itself, just as Open XML does.

The difference is, the dependencies of ODF are themselves open standards, such as PNG or SVG or ogg or SIML.

A good many of the dependencies of Open XML, however, are Microsoft proprietary and found only on Windows platforms.

//Is there any valid challenge to OOXML's openness from someone not pushing ODF?//

Yes, there is. See posts above, and this post.

Edited 2006-12-05 01:55

Reply Parent Score: 3

n4cer Member since:
2005-07-06

I can embed a COM component in an ODF document just as easily as I can embed one into an OOXML document, in both cases potentially tying that document to Windows if, for whatever reason, other platforms don't have the facillities to run that component.

Nothing in ODF excludes the creation of documents containing proprietary elements, just as nothing in OOXML mandates using proprietary elements.

The argument of the one-way street is disingenuous because it is mainly a matter of other office suites not offering feature parity and instead depending on the 5% or 10% theory. The people pushing ODF keep trying to turn Microsoft's feature advantage into a disadvantage. For the many people actually using Office in business processes and as a development platform, and even regular end users that have a need for certain features not available elsewhere, this criticism falls on deaf ears.

Reply Parent Score: 4

b3timmons Member since:
2006-08-26

"Is there any valid challenge to OOXML's openness from someone not pushing ODF?"

I.e., "Is there any valid challenge to [rigged game]'s openness from someone not pushing [fair game]?"

The bottom line here is not this kind of chronic intellectual dishonesty of Microsoft advocacy; no, what matters here is that we must feel these insults in order to grow more backbone to fight the injustice Microsoft perpetrates.

Reply Parent Score: 2

n4cer Member since:
2005-07-06

So the game is now rigged because MS has the majority of users and a format that moves those users forward without sacrificing their existing data wheras ODF has issues interoping with other ODF implementations? I see intellectual dishonesty, but it isn't eminating from me.

Do Sun/IBM have branch offices in OSNews forums now?

Reply Parent Score: 2