David Viner wrote:
>
> "proper encoding and lack of available metadata"
> am i correct in assuming that you mean the correct value for the encoding
> attribute?
No, I'm referring to the fact that XIndice stored textual stuff using a
specific encoding which was not general enough to handle all Unicode,
which is pretty serious issue for an XMl database given that XML can
contain all unicode codes.
But sounds like James just fixed this by using UTF-8 as the default
encoding for what Xindice stores so I'm happy on that side (I'm going to
test and try it out real soon)
> what metadata are you referring to? do you mean things like a DOCTYPE
> element or a schema?
> or do you mean something more like "last modified time"?
Sorry, I have to explain further: I'm talking about datastore-specific
metadata. Things like "last modified" and such.
There has been no agreement on this list about "what data is metadata"
since metadata is data anyway.
I agree that since Xindice has namespace support, most application level
metadata can be stored without Xindice knowing about it, but there is
some that simply cannot, without a serious and complex wrapper around
Xindice (which is something I'm going to seriously consider since I need
stuff that most people here would think it doesn't belong to a DB core,
but to a higher middleware, things like validation, security)
I'm seriously considering writing a big fat wrapper around XIndice to
provide all the functionality I need around a document-oriented XML
datastore, also without the problem of having an API to bind me.
What would you people think of such a thing?
--
Stefano Mazzocchi One must still have chaos in oneself to be
able to give birth to a dancing star.
<[EMAIL PROTECTED]> Friedrich Nietzsche
--------------------------------------------------------------------
