Slashdot Mirror
ODF Toolkit Announced
Sweetshark writes "IBM and Sun joined at the 2008 OpenOffice.org conference in Beijing to announce the ODF Toolkit Union. The ODF Toolkit project will be independent of the development at OpenOffice.org, and will operate under the liberal Apache license. It goes from small tools that simplify using ODF in the software development process to large ODF Java and .NET libraries that can be used within other projects. 'The future of accessing and distributing software is here today,' said Michael Bemmer, senior director of Collaboration Engineering at Sun. 'It is no longer an acceptable business practice to have silos of office document data stored in proprietary formats. The industry has moved forward and is replacing the silos with business content, such as on-premise business applications, software solutions offered over the Internet and applications supported by mobile devices that are critical in Service Oriented Architectures.' Will this help ODF to make inroads in the business world after the successes on the desktops of users at home?"
Short answer: no.
Long answer: As long as there are PHBs who think "writing = Microsoft Word," good luck getting rid of DOC.
Jars are just zip files, they are completely documented, as the java class structure. Multiple JVM implementations exist. I'm unsure what your point is.
Well yeah except you don't need Sun to open your jar. You can use Winrar to extract the info so it's not like it's a closed format.
In an ideal world, beating Word won't be necessary. Word itself isn't the enemy here. The enemy here is the notion that document format X must imply program Y(read .doc and word respectively). I don't care what word processor people feel like using. I do care what format the documents they send me are in.
In this case, the ODF Toolkit mentioned isn't a word processor at all, it's just a layer that makes it easy(er) for any sort of program to interact with ODF documents. Whether that means server side programs that parse information out of ODF formatted resumes that get uploaded, programs that generate ODF documents for various purposes based on database input, somebody's eccentric hobby word processor that needs to speak a standard format, whatever.
I'm not a huge fan of word, personally, and I'm very glad indeed that there are Free alternatives; but word isn't a big issue. Undocumented, badly documented, or deliberately obfuscated formats, that force us to all use a particular program just to communicate are the issue.
Just that it's "proprietary". I don't get how people think that because something's proprietary that automatically makes it bad. All proprietary means is that it's owned by someone. JAR is a specification, owned by Sun, and as such it is proprietary -- however well-understood and documented it is. Shouldn't the discussion be on how well the format performs relative to business cost, since that is the target use?
#fuckbeta #iamslashdot #dicemustdie
Comparing ODF to Word is like comparing HTML to IE. A data format is not the same thing as a program! Sheesh!
If you want ODF and Word, try here (works for me) or maybe here (haven't tried that one).
Exactly. Where this really seems likely to help is in integrating ODF as a message format within the SOA/Messaging/Web Services world.
If you really want to be modded up (or to get votes), just remember the magic words: "my friends". It almost worked for McCain.
Try not to take me more seriously than I take myself.
Sun and IBM are opening a community that will help propel adoption of the ODF standard by making the format more useful. By providing free libraries to access the data inside the documents, they encourage applications that consider the importance of the content, and minimize lock-in for a single presentation tool.
IMHO, the enemy is the notion of using a glorified Paint for making structured documents. While I can't imagine everyone using TeX instead, there must be ways of promoting logical structure (e.g. with a TeX frontend like LyX) as opposed to WYSIWYG.
I think the problem of format X being tied to program Y is a symptom of this problem. Word processing has become monstrously complex, and while new features creep into the structure, people still expect a perfect preservation and control of the looks. Thus the logic of using the program becomes increasingly entangled with the storage format, as witnessed by Word documents being memory dumps.
Of course, a needless focus on the looks takes time and energy from the writing itself. It doesn't help that some universities here have ridiculously precise specifications for the looks of your final thesis.
Escher was the first MC and Giger invented the HR department.
that one day I will finally be able to use command line tools to work with odf documents -- like convert them to pdf or postscript, cause that would be awesome (it would also come about six years after I really really needed that kind of functionality, but oh well)
I'm sorry, your meme has been rejected as inappropriate to your user name.
Please restate Soviet Russia meme in the form of you.
whois gawk date unzip strip find touch finger mount join nice man top fsck grep eject more yes exit umount sleep dump
I'm a big FOSS fanboi but OOo does not have mature doc support. It doesn't support any complicated documents, or most of the important embedded attachemtns being sent to me from rich businessmen in Nigeria...if you catch my drift.
93rd rule of Slashdot: No matter how obvious my sarcasm is, my comment will be taken seriously by someone.
This person is being extremely rude, please do something about it or I will be forced to document it excessively.
http://www.mhall119.com
Erm I've *never* had a problem with OOo reading doc formats (or even ppt and xls).
Apparently there are the occasional glitch when saving complex documents in Microsoft's format, but I havent seen any.
Are you sure about that?.
I know Perl is not considered sexy by the fad-hunting 'programmers' that haunt sites like this, but it works. And OpenOffice::OODoc is a very nice toolkit to programmatically create and manipulate ODF documents.
Mart
"I know I will be modded down for this": where's the option '-1, Asking for it'?
I see. You're waiting for an official, branded 'ODF Toolkit'(tm). Sorry, no, but OpenOffice::OODoc is not part of that. I sincerely hope that is not what is stopping you from using it.
Mart
"I know I will be modded down for this": where's the option '-1, Asking for it'?