Separation of Content and Structure

[Simon St.Laurent]

At 03:11 PM 7/23/99 -0500, Clinton Gallagher wrote:
>Do any of those who have a command of the use of XML remain using relational
>databases and in which context as a development tool might the relational
>database remain useful?

If your information is highly structured and can be fit into the normalized
table structure of relational databases easily, you'll probably find you're
best off using a relational database rather than piles of
difficult-to-search XML files or even a hierarchical object store.  They're
much quicker for raw search and retrieval if the information fits the rules.

On the other hand, if you've got lots of information that's more
'document-like', with unpredictable lengths of content, flexible structures
for marking up information on an as-needed basis, or information that shows
up in formats you don't always control, then XML, possibly stored in a
flexible hierarchical data manager of some sort, is probably a good idea.

In either case, it's not that hard to get your information into and out of
XML when needed.  Store the info the way that's most efficient for your
needs, and build bridges between your storage and transmission as required.

At least that's my take.

Simon St.Laurent
XML: A Primer / Building XML Applications
Inside XML DTDs: Scientific and Technical
Sharing Bandwidth / Cookies
http://www.simonstl.com

xml-dev: A list for W3C XML Developers. To post, mailto:xml-dev at ic.ac.uk
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/ and on CD-ROM/ISBN 981-02-3594-1
To (un)subscribe, mailto:majordomo at ic.ac.uk the following message;
(un)subscribe xml-dev
To subscribe to the digests, mailto:majordomo at ic.ac.uk the following message;
subscribe xml-dev-digest
List coordinator, Henry Rzepa (mailto:rzepa at ic.ac.uk)