odf outside openoffice.org

Hello list 
I'm applying in GSoC for the odftoolkit project
I was looking at the CVS repo for the odftoolkit in odf4j
I'd like to help in odf4j.
I noticed that you use the SAX parser, which is good, but
can I suggest the
StAX parsing API ?
Since it has some advantages over SAX for example if we have
very large ODF
document and we wish to convert it to text and our
application is somehow
busy or our machine is slow also the ODF document might be
at some remote
host. In such cases might be better to use pull parsing like
StAX so the
application can pull an infoset whet it's ready. This could
bring better
performance.
Also I got an idea, I don't know how much useful it'll be
but I think that
it's cool if the application can convert ODF documents to
suitable format
for storing in a database.
Image we have many similar ODF documents and we wish to
store them in a
database, maybe the application can construct a suitable
table depending of
the ODF document and translate the content in SQL script.
Maybe the reversed
way would be more interesting and useful 
what if the application can create ODF documents from a
table dump ?
(e.g. SQL script)
Tell me what you think guys
thank you
take care

Soul Stealer schrieb:
> Hello list 
> I'm applying in GSoC for the odftoolkit project
> I was looking at the CVS repo for the odftoolkit in
odf4j
> I'd like to help in odf4j.
> I noticed that you use the SAX parser, which is good,
but can I suggest the
> StAX parsing API ?
> Since it has some advantages over SAX for example if we
have very large ODF
> document and we wish to convert it to text and our
application is somehow
> busy or our machine is slow also the ODF document might
be at some remote
> host. In such cases might be better to use pull parsing
like StAX so the
> application can pull an infoset whet it's ready. This
could bring better
> performance.
> Also I got an idea, I don't know how much useful it'll
be but I think that
> it's cool if the application can convert ODF documents
to suitable format
> for storing in a database.
> Image we have many similar ODF documents and we wish to
store them in a
> database, maybe the application can construct a
suitable table depending of
> the ODF document and translate the content in SQL
script. Maybe the
> reversed

Well that's going to be a tough thing. Storing
"Structured Documents" in
a relation database, it's not impossible but it's quite a
great bunch of
work. That's why people have invented XML-Databases like
http://xml.apache.org/
xindice/

Tom

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribeodftoolkit.openoffice.org
For additional commands, e-mail: dev-helpodftoolkit.openoffice.org

On 3/23/07, Tom Schindl <listombestsolution.at> wrote:
>
> Soul Stealer schrieb:
> > Hello list 
> > I'm applying in GSoC for the odftoolkit project
> > I was looking at the CVS repo for the odftoolkit
in odf4j
> > I'd like to help in odf4j.
> > I noticed that you use the SAX parser, which is
good, but can I suggest
> the
> > StAX parsing API ?
> > Since it has some advantages over SAX for example
if we have very large
> ODF
> > document and we wish to convert it to text and our
application is
> somehow
> > busy or our machine is slow also the ODF document
might be at some
> remote
> > host. In such cases might be better to use pull
parsing like StAX so the
> > application can pull an infoset whet it's ready.
This could bring better
> > performance.
> > Also I got an idea, I don't know how much useful
it'll be but I think
> that
> > it's cool if the application can convert ODF
documents to suitable
> format
> > for storing in a database.
> > Image we have many similar ODF documents and we
wish to store them in a
> > database, maybe the application can construct a
suitable table depending
> of
> > the ODF document and translate the content in SQL
script. Maybe the
> > reversed
>
> Well that's going to be a tough thing. Storing
"Structured Documents" in
> a relation database, it's not impossible but it's quite
a great bunch of
> work. That's why people have invented XML-Databases
like
> http://xml.apache.org/
xindice/
>
> Tom
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribeodftoolkit.openoffice.org
> For additional commands, e-mail: dev-helpodftoolkit.openoffice.org
>
>
yeah, I agree that it would be hard
it's just an idea
what about the reversed way - from DB to ODF ?
this should be much easier

thank you