- From: David Wagner <dwagner@kevric.com>
- Date: Fri, 4 Feb 2000 11:22:00 -0600
- To: <www-html@w3.org>
Suzanne Topping wrote > It seems to me that your decision should be based on how the > data you are > presenting will be used, and perhaps what the long term > strategy for the > site will be. > ... > Lastly, the two don't have to be mutually exclusive. XML and > HTML can be > used together on a site. The long term strategy I'm pursuing is to encode all my site content in a single XML file, then use XSL to generate all the pages in all the versions of the site needed (HTML4, XHTML, HTML32, WML, HTML for NS4, with and without JavaScript versions, and so on). This has the distinct advantage of automatically keeping these versions synchronized, as making changes to the source XML file propagates to all the different versions at once. If there is one thing I cannot stand, it's redoing the same old content into the file flavor of the month. This moves a lot of the work to the front end, so it's not a good strategy if your client is breathing down your neck and wants to see the work in progress. There is nothing to see until alpha testing the first complete version of the site but DTDs and Markup, and maybe a complete-site-in-a-document view, which won't look pretty. Regards -David
Received on Friday, 4 February 2000 12:26:31 UTC