cmsmcq@a... (C. M. Sperberg-McQueen) writes:

> . . .
> One friend has said "but you just use XSLT to translate it into
> HTML -- that's not really serving XML, is it?  You should be using
> CSS to render the XML directly", but I think I disagree; HTML is
> perfectly serviceable as a rendering language for screens, and
> using XSLT means I can generate tables of contents and do text
> mirroring for things like cross references.  And it's been a long
> time since I generated a static HTML document in order to make
> a working paper I wrote available to people I was working with --
> so it's been a long time since we had problems owing to someone
> else reading an out-of-date snapshot instead of the current
> XML form of the document.

I think this is sensible for serving things to a known group of
collaborators, but I'm inclined to side with Peter in the case of
serving finished articles to the public.  The audience is unarguably
broader that way.  (For example, (1) some browsers on some platforms
will warn me about incoming "controls" when there's an xslt sheet, and
(2) on a bad network day I've been known to use w3m instead of
firefox.)

                                    -- Bill