[Home] [By Thread] [By Date] [Recent Entries]


A brave statement, Tim.  The triumph of tinkerism.

OTOH, the XML data model is pretty good for grabbing 
a snippet of the RDBMS content and working with it 
on the client.  I always think of it as my locally 
handy OODB for doing fast, non-scalable manipulations.

DOMs make fine semiotic storage models for a local 
focus of attention.  So does a relational view, but 
keeping one of those around means keeping the rest 
of the RDBMS handy, and that is expensive in several 
dimensions.

len


From: Tim Bray [mailto:tbray@t...]

Summary: XML for export and interchange is totally the way to go.  How 
you get there?  Acronyms that begin with X aren't that relevant.

Now all the XDBMS vendors are going to complain about my lack of 
fidelity to the religion of the XML data model, oh well.

Site Map | Privacy Policy | Terms of Use | Trademarks
Free Stylus Studio XML Training:
W3C Member