Hello Henning, I think that xslt is very useful when you (your company) want
to develop an aplication to communicate your Data Model with another or more
Data Models (companies) that have one different.

More specific, my supplier have a model A and I have the model B, and so
that my applications can work appropriately (one option) I receive its xml
document, I transform it in a xml document that my application can accept.

CompanyDatabase (Oracle, MySQL, SQLServer2005, etc.) -- xmlDoc -- xmlDoc +
myXsltDoc = myXmlDoc -- myDatabase (Oracle, MySQL, SQLServer2005, etc.)

Obviously don't forget to implement text encrypting methods.

Is this concept correct?

Dagoberto Flores

-----Original Message-----
From: Henning Waack [mailto:henning.waack@xxxxxx]
Sent: January 13, 2005 1:37 PM
To: xsl-list@xxxxxxxxxxxxxxxxxxxxxx
Subject:  when to use xslt


Dear all.

I'am looking for argument for and against xslt, that is when
is it useful to use (the functional language) xslt, when to
use some imperative programming language? Right now I am not
getting very far, except for some standard arguments like
xslt is slow, but xml itself etc. Can you point me to some
sophisticated points concerning this topic?

Thank you very much in advanced,

greetings,

Henning