Re: Modeling Data for XML instead of SQL-DBMS

dawn wrote:
> If working on a software project where all data are persisted in XML
> documents and not in an SQL-DBMS, the tools would not require that the
> data model be in 1NF or the use of the SQL NULL.
>
> How would an excellent logical data model designed for this XML
> implementation differ from the corresponding data model developed for
> an SQL-DBMS? What would be some best practices for modeling data in
> this environment?
>
> I'm guessing some will think that the exact same logical data model
> would be appropriate for both targets, but hopefully many will agree
> that it is unlikely that the best implemented data model would be
> identical in each environment. In that case, what would the
> differences be? What best practices would apply to data modeling for
> XML documents compared to data modeling for a SQL-DBMS?
>
> Thanks. --dawn

I persist my data using the excellent C++ boost::serialize libraries, when I am working on such an 'island'. And in that case your organization of data can follow recommended OO design. Using XML for the sake of fashion, as all efficient coders know, does nothing but add processor cycles to parse the unwieldly crap.

If nothing else this highlights why codd named his paper for "large SHARED databanks". If your data isn't shared, and you are sure you are never, ever, ever going to use it in a different way then I guess you don't have to worry about query bias. As a caveat however, I'd say that situation is going to be pretty damn rare. Received on Wed Oct 25 2006 - 14:44:20 CEST