News for hackers. Stuff that matters.
Re:For your OOXML Conspiracy Theories - Miguel de Icaza by joe_the_user on Wednesday December 22, 2010 @04:00PM (#2032428)
Yes,

The argument against OOXML is that it cannot be a standard since it says things akin to "must work like Word XXX here" - ie, it's just a bundling of a proprietary format inside XML.

Moreover, this is just not the way to "clear the air". I know relatively little about all the events but this kind of ad hominem rant sure sounds like something someone in a conspiracy would write ...

Re:For your OOXML Conspiracy Theories - Miguel de Icaza by tzs on Wednesday December 22, 2010 @04:21PM (#2032504)
There is nothing whatsoever like that in OOXML, nor was there ever anything like that. That was just FUD (largely from IBM).

Here's what there actually was. There are older documents, from a variety of older programs (not all Microsoft, BTW), that do things that cannot be represented in OOXML (or ODF, for that matter).

There are many organizations that have documents in those formats, and have tools that understand those formats. E.g., a law office might have a lot of Word Perfect documents, and might have tools that understand WP format and can automate various things involving those documents.

Such organizations might want to update their document store to use a more modern format, like OOXML or ODF. However, they might need to preserve some of those things in the old documents that are not representable in the new format.

Suppose the standard says nothing about this. What should they do? Simple--they will find some way to add that extra information to the document. Both OOXML and ODF provide a couple of ways that one could include non-standrd. So what would likely happen is that everyone who deals with old documents would come up with their own in-house way of embedding this extra information.

Eventually, people would get smart. We'd realize that if you are embedding information about WP5 line spacing options in your OOXML or ODF conversions from WP5, and I'm embedding information about WP5 line spacing options in my OOXML or ODF conversions from WP5, then we should get together and agree to do it the same way--and we should get everyone else involved. We should come up with some kind of industry standard for storing WP5 line spacing options in documents converted from WP5 to OOXML or ODF.

Same goes for a bunch of other things from old word processors and spreadsheets. We'd eventually end up with a bunch of industry standards for all of these for OOXML and ODF. Hopefully, we'd combine them all and have one standard.

OK, now back to what they actually did in OOXML. They simply realized people would be doing this, and so reserved some names for them. That's all. Nothing in the OOXML spec said that you have to support WP5 line spacing, or know what it means, or have your OOXML programs be able to do it. All the spec said was IF you are going to extend the document to record WP5 line spacing (or the other specific features of old formats they identified), THEN use this as the name of your tag or attribute or whatever that marks it.

They also said that new documents should not use these things. It was strictly for people who were converting old documents and needed to keep that information.

I've yet to see anyone offer a rational objection to this.