At 02:08 PM 4/28/99 -0400, Jonathan Borden wrote:
>    So you agree that, logically, the most open and semantically rich way to
>transmit information is via XML with conversion on the client into a
>presentation format. Whether the XSL sheet converts into XHTML+CSS or XFO on
>the client is irrelevent to the fact that the data started out as
>semantically rich, and perhaps arbitrary XML/RDF.

Actually, no.  I'd send XML+CSS and skip the XSL work, unless I had a case
which actually required transformation.  (Converting a table of data into
an SVG graphic would be a good case for that.)  There's no need to go to
HTML except to support legacy browsers.

>    In a perfect world, all browsers would support client side
>transformation.

In a perfect world, no one would send XFOs across a network.

Simon St.Laurent
XML: A Primer
Sharing Bandwidth / Cookies
http://www.simonstl.com


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list