RE: possible ozone 0.6 bug?

["Jeff Kowalczyk" <jtk@adelphia.net>]

> > I am getting pessimistic about loading my 15Mb of
> > botanical descriptions in Ozone on my 64Mb Linux machine.
> 64Mb is probably not enough. Do you really need all
> the data in one XML document?

This always seems to come up between XML db developers and people who are
thinking of their specific application.

I think the question we as potentential users have is what can Ozone really
do with databases are partitioned into separate files? In terms of query
capability, is it equivalent to factoring into tables in a relational
database, or is it more akin to separate databases, which can't be queried
without a non-SQL linkage of some sort?

If you have 10K contact items in one doc, and a separate xml document for
their appointments and a third for to-do assignments, how well is Ozone
going to handle joined XPath queries? One sees ref/id techniques, but is the
Ozone DOM going to support that? It seems like DOM Level2 stuff.

It almost seems like we need to know what's in the future for XQL or
something equivalent before we can really know what a 'relational' select in
multiple XML docs will practical. Ozone's potential seems directly tied to a
way to work with multiple xml docs.