Pro-ODF Legislation Loses In Six States

ajanp writes "Computerworld discusses the defeat of pro-ODF legislation in the states of California, Florida, Texas, Oregon, and Connecticut which 'would have required state agencies to use freely available and interoperable file formats, such as the Open Document Format for Office Applications, instead of Microsoft Corp.'s proprietary Office formats.' A similar bill in Minnesota was changed to study the issue instead. There was heavy lobbying being done in private on both sides with one problem being 'the jargon-laden disinformation that committee members felt they were being fed by lobbyists for both IBM and Microsoft. Although lobbyists would tell the committee one thing in private, they got cold feet when asked to verify the information publicly, under oath.' However, 'Despite the string of defeats, Marino Marcich, executive director of the Washington-based ODF Alliance, said the legislative fight has only begun.'"

Comments

Where have we heard this one before?

[jollyreaper]

First they ignore you, then they laugh at you, then they fight you, then they crack open a can of lobbyist whoopass and defeat your bill.

All kidding aside, what makes this fight different from the usual standards wars is that it's not between two companies trying to pitch different standards like Beta and VHS or BlueRay and HDDVD. In that kind of fight, whoever wins, the victor is still going to be a giant corporation. For the buying public it's truly a case of same shit, different pile. ODF isn't just a product being shilled by a single corporation and so there's no single company to bankrupt or buy out so victory can be declared. I think this is going to be more like guerrilla warfare than a conventional battle.

I predict that there will be many, many more defeats for ODF legislation, especially in the US. The question is whether there will be a victory or failure after all those defeats. Microsoft certainly has the dollars in this fight. There's the old quote from Vietnam, allegedly from when both sides were having a talk after the final peace was declared. A Col. Summers had a chat with General Giap. "You know you never defeated us in the field," Summers said. "That may be true, but it is also irrelevant," Giap replied.

No matter which way it goes, this war is going to be interesting to watch.

Re:Not practical

[cgenman]

All they have to do is explain that getting Office to output ot odf is not part of office but requires a downloaded addon, follow that with a breakdown of the man-hours required to get it installed on everyones machines,

Your client management suite should be able to do this in about an hour, including testing time. What, you don't push your software? Compared to the cost of 100 seat licenses for Office, a software push / update is trivial.

then top it off with a mention that there is no real way to regulate attachments coming from outside and this is DOA in any local govt.

You don't need to. You can keep going with Word for the time being for recieving attachments, but the agencies would be required to internally communicate and send out communications in a format that anyone could read.

The idea is not to kill microsoft. The idea is to push government agencies and the software suppliers that support them to use and create document formats that we have a hope of reading in 10 or 20 years (let alone 200). Can you imagine if the US constitution was written in Symantec Greatworks? Or if key data from 50 years in the past was written in GobeProductive on BeOS? If Microsoft adopts a truly open format that satisfies this need for transparency and readability, then that's great! But if not, we shouldn't be tying ourselves to them to fill a need they don't want to fill.

Re:UGH! Open Formats Do Not Limit Choice!

[SanityInAnarchy]

OOXML is built in to Office 2007. The files are zips, if you unzip them, they're generally plaintext XML. Which is to say, JUST AS READABLE AS ODF.

WMV support is built into Windows Media Player. The files are binary, if you look at them in a hex editor, they're generally plain numbers. Which is to say, JUST AS READABLE AS MPEG.

Except not, unless you are a fucking moron. I'm sorry, but XML is not magic open interoperability pixie dust.

MS looked at ODF, but felt that since it didn't support some functions of legacy Office applications, they wanted a broader definition set, which led to the ginormous OOXML standard.

Nope. Nice try, though.

What actually happened was, MS looked at ODF, but felt that since it threatened their monopoly of Office applications, they wanted their own "standard" that they could control.

Or maybe they did it by accident. (Yeah, right.)

ODF was designed to be all things to all office suites. OOXML was designed to basically be an XML dump of MS Office documents, and from what I have heard (and seen), it's little more than a straight 1:1 conversion of the binary Office format into XML.

I suggest you go actually try to read the OOXML "open standard", and understand why it is neither. It has little to do with the 6000 pages, it's about how little is actually in that 6000 page document.

Now, you can complain (not without significant justification) that OOXML is a hugely bloated standard

No. We complain that it is not a standard, and not suitable for implementation in anything but MS Office.

due to it's trying to be all things to all iterations of Office

The problem is not that it supports all these various iterations of Office, and even older things (WordPerfect, etc). The problem is that they support these by creating some sort of tag or attribute or something which flags a section as being formatted for Word95 or somesuch, and then don't define how to do that. They basically say it's "beyond the scope of this document", and that you should emulate the behavior of the software in question.

And this is not the right way to design a standard format anyway. Suppose different versions of Word came with different default heading styles. You could just put <word95heading> tags around something -- or you could use a format that supports defining custom styles.

but your comment that only MS can use MS formats is a red-herring.

That's true, we can reverse-engineer MS formats, and have done so. Most open office suites (OpenOffice, KOffice, AbiWord, etc) support the binary Office formats quite well. But it's still reverse-engineered, and still not complete.

It would be entirely possible to make a document standard that is just as flexible, concise, and transparent as ODF, but support all of the crap that OOXML does. The difference is, it would be much more difficult for MS to support such a standard, and much easier for everyone else. As it is, OOXML is much easier for Microsoft to implement than for anyone else.

Consider that, in order to fully support OOXML, you have to actually go and buy all of those different versions of Office, plus random crap like WordPerfect, and reverse-engineer their behavior. So OOXML is not any better than the binary formats, because in reality, you may actually have to reverse-engineer MORE products in order to make it work.