For a example of what you can do with the DOM in a heavy duty Industrial
site go to http://www.parker.com/indhose/ and
http://www.parker.com/indhose/applications/

These pages are built 'on the fly' from an XML file using the DOM.

The undelying XML file can be seen at

http://www.parker.com/indhose/xml/cat.xml

This XML file is also imported into FrameMaker to produce all their
catalogs, flyers, and other print products.

Frank
----- Original Message -----
From: "Christopher Higgs" <chiggs(at)unimelb.edu.au>
To: "Steve Mount" <steve(at)saltyrain.com>; <hwg-techniques(at)mail.hwg.org>
Sent: Thursday, November 07, 2002 10:04 PM
Subject: Re: What shall we do with the W3C DOM?


> At 07:53 PM 7/11/2002 -0500, Steve Mount wrote:
> >The real problem, as I see it, with using XML and XSLT to produce
documents
> >for end users is the complexity involved.
>
> I never said it would be easy :-)
>
> >Their customers may still be using version 4 broswers, or lower.
> >I sill have a few IE 3 and NN 2 users hit my sites every so often, not to
> >mention Lynx.  By using HTML, I know the latest browsers can see my
content,
> >and so can the older ones.
>
> But that's what I'm saying!  Let's say your XSLT transforms your page into
> two versions - "old HTML" and "CSS-enhanced".
>
> Or simply add a different CSS for NN vs IE viewers.  Yes, SSI can do this
> now, but only at a basic level.
>
>
> Chris Higgs
> Manager, New Learning Technology
> ILFR, University of Melbourne
> http://www.landfood.unimelb.edu.au/
> Phone: +61 3 8344 9749  Fax: + 61 3 9348 2156
>

• Web Designer Courses
• Off the Shelf Training Courses

HWG hwg-techniques mailing list archives, maintained by Webmasters @ IWA