> But since you can do the transformation with ASP/PHP/JSP with the same
> effort, why use XSLT?

Again ASP is just a calling convention. If you are going to transform an
XML file to something most people will find it _much_ easier to use a
programming language that's designed to do transformations than one that
isn't. If you are more familiar with **P and want to program the 
the transfomration directly in some low level code that walks over a DOM
or some such structure than fine no one is stopping you doing that but
(apart from unfamiliarity with the language) it would almost certainly
be much easier and more maintainable in XSLT. An awful lot of XSLT
processing is totally unconnected with web server programming, so your
repeated comparison to **P seems rather strange.


> So far I think it's one of those things to have "stashed" just in case
> you need it one day...

I'm sure it is true that the vast majority of the world's population
will quite happily survive without ever needing to use XSLT, so that may
be stashed for a long time.


David