In: <1109697460.680750.263740@z...>, "Arfin" <arfinmail@y...> wrote:
>But since you can do the transformation with ASP/PHP/JSP with the same
>effort, why use XSLT?

Same effort? Some people might find XSLT easier, (well, for more complex
XML docs anyway)

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

XSLT can come in handy if you wanted to write a general purpose application
to transform XML to a native format, for example, suppose your application
expects

<plant>
	<fruit type="apple" />
</plant>

But someone hands you a:

<menu>
	<item type="fruit" name="apple" />
</menu>

Your application could accept as a parameter, a stylesheet to transform the input
document to something you can understand.

Another reason to use it is because it's "standard", if you were a consumer of
a web application and wanted to transform the XML to something else, XSLT is 
a standard sort of wedge, they don't need to know PHP or ASP. (or perhaps
as may be the case with java, you don't want them to have the source)

I myself don't use XSLT very often.

Jamie
-- 
http://www.geniegate.com                    Custom web programming
guhzo_42@l... (rot13)                User Management Solutions