>  > Of course, it's not just a matter of parsers, eh?  I know the
>  > basis of TransQuery is that one can have the XML database look
>  > sort of like an oversized EPE whereas each top-level node
>  > represents a separate document in the database, right?
>  
>  That was one idea, but things like IDs and base URIs that require document
>  identity to be maintained forced me to stick with viewing the XML database
>  as a simple node-set containing only root nodes.

Good point about IDs, but base URIs needn't have been a problem.  XPath provides for each no
de to have its own distinct base URI, to the XML DBMS could simply assign top-level node bas
e URIs according to their path within the repository.

And I'm not sure how your solution fixes the ID problem.  Isn't there still scope for incons
istency if IDs clash across documents?


-- 
Uche Ogbuji                           Fourthought, Inc.
uche.ogbuji@[...].com           http://fourthought.com
http://4Suite.org                     http://uche.ogbuji.net
Track chair, XML/Web Services One (San Jose, Boston): http://www.xmlconference.com/
RDF Query using Versa - http://www-106.ibm.com/developerworks/xml/library/x-think10/index.ht
ml
WSDL and the Wild, Wild West - http://adtmag.com/article.asp?id=6004
XML, The Model Driven Architecture, and RDF @ XML Europe - http://www.xmleurope.com/2002/ktt
rack.asp#themodel




-----------------------------------------------------------------
The xml-dev list is sponsored by XML.org <http://www.xml.org> , an
initiative of OASIS <http://www.oasis-open.org> 

The list archives are at http://lists.xml.org/archives/xml-dev/

To subscribe or unsubscribe from this list use the subscription
manager: <http://lists.xml.org/ob/adm.pl>