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

 


Help: OASIS Mailing Lists Help | MarkMail Help

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: [xml-dev] storing XML files



I would certainly appriciate any reading on this topic.
 
Repeating elements will cause issues with the crosstab/pivot type query if I want to create a 1 row per document type view of the data.  But database structure will still support storing this type of data.
 
You are correct in that the current documents that I'm looking at are relatively simple.  I'll have to look into the other problem areas that you mention with ID and IDREFs and mixed content.
 
The question I would ask though is this - Can an XPath correctly and uniquely identify all the critical pieces of any XML document?  If it can then the basis of my solution is still valid.
 
Dave
-----Original Message-----
From: Soumitra Sengupta [mailto:soumitra@b-bop.com]
Sent: Wednesday, October 10, 2001 11:36 AM
To: Dave Simmonds
Cc: xml-dev
Subject: Re: [xml-dev] storing XML files

 
Hi Dave:

It may work for your particular application and the types of document you are getting but you will quickly run into problems with recursive elements, mixed content, ID and IDREFs, not to mention a query language and other adjacent standards.  In the gneral case ii would be advisable to use a XML database (IMHO).

Mike has pointed you to couple of open source initiatives that you can look at if you need more ideas.  I have come across at least 2 academic papers dealing with this, one from a Korean lab. and another from a U.S. University.  I will look them up and forward them to you.

Regards,

Soumitra

In solving this problem I've come up with a base of approximantly 5 tables that are needed.  In order to accomplish this task - each XML document must be able to validate against a Schema (or DTD) and the db must support crosstab/pivot type queries.