I've got to say I completely agree with Kornel here - XSLT is very useful, but keep it on the server side. Its all about what you send over the wire.
By all means create XML (schemas) for your own use in your own applications - these may have very precise semantic meaning in your environment, but they are truly meaningless in the wild. Perform your transformations at your end and send your content over the wire in some widely understood vocabulary such as HTML/XHTML. Arguments about bandwidth are really not relevant in this context. I could, for example, send all my content through to the browser in a special XYZ format that I have devised and that happens to work in a couple of browsers. This format may have huge advantages in terms of bandwidth and rendering time, but it is still a Very Bad Idea (TM) because it breaks the whole concept of web standards. Optimise your bandwidth by all means, but draw the line at sending non-standard formats (like proprietary XML vocabularies) over the wire. On another note, personally I'm a little tired of people thinking of HTML/CSS as the *only* web standards - it is so much broader than that. HTTP, ECMA Script, P3P, SVG (and to a lesser extent XSL) are all true web standards and are completely relevant on this list, IMHO. -- Mark Stanton Gruden Pty Ltd http://www.gruden.com ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
