[odf-discuss] A Pit Bull in the Mix

[Damon Anderson]

Hoo boy howdy! Sounds like Marbux and Daniel need a pitbull in the mix.

So maybe I'll be the pitbull...

MOOX, Ecma 376, whatever flavor it comes in, as a software developer there  
is no possible way I am going to implement a 6000 page specification.  
Simply isn't going to happen.

Now here's the irony. ODF... not going to happen either. Also still too  
complicated. The only way I'm going to implement ODF is if I can get it  
simplified down to a maximum of 10 pages that is pure and simple step by  
step implementation instructions. All I want to be able to do is implement  
the minimum simplest subset of the specification to include the most basic  
requirements for Corporate Documents. E.g. sections for header footer,  
title, contents, and footer. Alignment, left, right, center, bullets and  
numbered lists. End of story. Basically all I need is simple XHTML and  
CSS. Hmm... Why bother with ODF when I can simple XHTML and CSS and get  
99% of all the functionality I need?

You see I think ODF is the right answer for the wrong question. ODF is a  
common office format, which is great. Woo hoo. What we programmers are  
looking for, though, is a common format that is simple and easy to  
implement that GOES TO all other formats. ODF is a great destination  
format, no doubt about it. But not of much interest to me as my goal is a  
single format that I can send to a million other formats and have it  
understood.

This is why I say all hail XHTML CSS (and maybe a little XSLFO thrown in).  
If only Silk was easier to implement. sigh... more comlicated  
documentation.

-Damon