OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help



   RE: XML data bases, document management

[ Lists Home | Date Index | Thread Index ]
  • From: Irsan Widarto <irsan@xhive.com>
  • To: xml-dev@lists.oasis-open.org
  • Date: Thu, 29 Jun 2000 08:10:12 +0200 (CEST)

Xhive is one of the products mentioned on Ronald's list of XML database 
products. We believe that Xhive fulfills all the requirements as put down by 
Ronald (see his message as attached).  In fact: we are currently working 
with some developers of document/content management systems who 
are using Xhive to (re-)build their products.

Xhive is currently in beta, please send me an e-mail if you need more info 
on Xhive or visit http://www.xhive.com


Irsan Widarto

--- In xml-dev@egroups.com, "Ronald Bourret" <rpbourret@h...> wrote:
> >does anybody have practical experiences with XML data bases? like 
> >poet, objectstore or tamino? what do you think about them? can you
> >recommend a product in this area?
> >
> >i want to setup a document management system based on such a 
data base,
> >therefore i'm interested in pointers to already existing applications.
> Here's two links you might be interested in:
> The first is a paper I've written (XML and Databases) explaining the 
> concepts behind using XML with databases. The second is a pretty 
> comprehensive list of products for using XML with databases -- from 
> middleware to XML databases to document management systems.
> If you're interested in writing a document management system, then you 
> should look pretty closely at exactly how any of these products saves an 
> document in a database. I'm not sure about the XML databases such as 
> you mention, but most of the middleware for working with XML and 
> probably isn't adequate for your needs. This is because such products, 
> well as XML-enabled databases like Oracle and DB2, tend to 
concentrate on 
> transferring the data (as opposed to document structure) from an XML 
> document to the database and vice versa.
> In particular, you will probably want to preserve the following information 
> in the database:
>    Elements and attributes (obviously)
>    Hierarchical structure (obviously)
>    PCDATA in mixed content
>    Order of sibling elements
>    Order of values in multi-valued attributes
>    Entity and character references
>    CDATA usage
>    Processing instructions
>    DTDs
>    etc.
> In addition, you will need the following capabilities:
>    Bidirectional transfer
>    The ability to model arbitrary (any) XML documents
>    Update and delete of existing documents
> My guess is that these requirements are going to wipe most existing 
> XML/database products off the list. In particular, most of the available 
> middleware has very limited abilities to model arbitrary XML documents 
> I'm not aware of any that preserves physical structure, such as entity and 
> CDATA usage.
> The XML-enabled databases (such as Oracle, DB2, etc.) generally do a 
> job of modeling arbitrary XML documents, although whether they can 
> *any* XML document is not clear to me. Similarly, I would be surprised if 
> they stored physical structure information or could handle things like PIs 
> and DTDs.
> Unfortunately, I don't know much about the so-called "native" XML 
> like Tamino, but these might have a better chance of meeting your 
> Again, it depends on whether they are designed to handle data or 
> structure.
> My best guess is that you will want to use a persistent DOM 
> such as that from GMD (http://xml.darmstadt.gmd.de/xql/index.html), or 
> your own.
> -- Ron Bourret

This is xml-dev, the mailing list for XML developers.
To unsubscribe, mailto:majordomo@xml.org&BODY=unsubscribe%20xml-dev
List archives are available at http://xml.org/archives/xml-dev/


News | XML in Industry | Calendar | XML Registry
Marketplace | Resources | MyXML.org | Sponsors | Privacy Statement

Copyright 2001 XML.org. This site is hosted by OASIS