I've really only been able to think of one situation where browser-side transformation makes sense, and that's when there's a set of data that the client may wish to view different ways. Since the browser will (should) cache the XML document when it comes down, displaying a different view of that data would only require a download of a new stylesheet, rather than requiring the entire data set to be downloaded again. In my opinion, the "native" support for XML in IE5 is just a toy, really - to move any usable content to a client, it ultimately needs to wind up in some rich presentation format the client understands, such as HTML or WML. And, as Frank says, this is typically done by styling the XML on the server with an XSLT stylesheet.
- Kevin
------------------
Kevin Williams
Senior System Architect, Equient Corporation
author of:
Professional XML Databases
Kevin Williams<BR>Senior System Architect, Equient Corporation<BR>author of: <A HREF="http://www.amazon.com/exec/obidos/ASIN/1861003587/electricporkchop" TARGET=_blank rel="nofollow">Professional XML Databases</A>