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 188097
To view parent comment, click here.
To read all comments associated with this story, please click here.
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

hal2k1 Member since:
2005-11-11

//in both cases potentially tying that document to Windows if, for whatever reason, other platforms don't have the facillities to run that component. //

Misses the point entirely. Continues with "disingenious".

For ODF, all platforms are "permitted" to implement all of the required "facillities to run that component". It is entirely open, free to implement as there are no encumberances, either within the ODF spec itself or within any of the dependent facilities. Anyone is permitted to implement SVG, PNG or OGG, these are all open and unencumbered.

That is not the case at all for Open XML via its attendant dependencies.

If a Windows platform does not have a given facility (such as, for example, the ability to render SVG), then that is because Microsoft do not want to support open standards. It is not because Microsoft are not permitted to support SVG on their Windows platform.

If, OTOH, a Linux or OSX platform is missing a given facility (such as, for example, the ability to use ActiveX controls or to run Visual basic macros), it is because these facilities are Microsoft proprietary, and Microsoft do not allow anyone else to implement them, and they are restricted to Microsoft platforms only.

Therefore, via "inheritance" of the dependencies, Open XML is not open at all, whereas ODF in contrast is "open all the way down".

Open XML is indeed a "one way street", without any doubt at all. My very strong recommendation remains, DO NOT SAVE YOUR DOCUMENTS IN OPEN XML FORMAT.

Edited 2006-12-05 02:40

Reply Parent Score: 5