Lists Home |
Date Index |
- From: James Robertson <email@example.com>
- To: firstname.lastname@example.org
- Date: Tue, 02 Feb 1999 10:13:24 +1000
At 20:29 1/02/1999 , Matthew Sergeant (EML) wrote:
| My problem was slightly different. I needed to be ready for the 5.0
| (probably IE5, although I'd prefer NS5), and XML seemed ideal because we
| would be displaying/editing documents that look like data (or data that
| looks like a document if you like). We really needed an object
| I needed to get moving quickly (a typical web project: "Can we have it
| yesterday"). Learning an object database wasn't a possibility. I already
| knew XML. So I looked at it like this - we could have it 2 ways:
| 1) Store XML now, process into HTML now, Transmit XML in the future.
| 2) Store in RDBMS now, process into HTML now, process into XML in the
I would personally recommend a third option:
3) Store in RDBMS now, process into XML, process this into HTML now.
Process the XML into whatever you want in the future.
I have been using this in an electronic publishing system, and while
it seems like overkill, it isn't. It both makes the generation of HTML
easier, and inserts a very nice level of abstraction into the whole
For example, you can change the structure of the RDBMS without having
to worry about the HTML, etc, as long as the XML DTD is still valid.
And if you want to generate paper, online help, etc it is much
easier from the XML.
Step Two Designs Pty Ltd
SGML, XML & HTML Consultancy
"Beyond the Idea"
ACN 081 019 623
xml-dev: A list for W3C XML Developers. To post, mailto:email@example.com
Archived as: http://www.lists.ic.ac.uk/hypermail/xml-dev/
To (un)subscribe, mailto:firstname.lastname@example.org the following message;
To subscribe to the digests, mailto:email@example.com the following message;
List coordinator, Henry Rzepa (mailto:firstname.lastname@example.org)