I myself am on the opposite end, I don't know much yet about XPathScript, and what I have tried has failed miserably. I understand XSLY quite well I think, and tend to keep my logic in special taglibs that I write. That way XSLT is just dealing with basic XML transforms.
My vote leans to the XSLT side; -Don -----Original Message----- From: Pavel Penchev [mailto:[EMAIL PROTECTED]] Sent: Friday, 09 August, 2002 12:45 To: [EMAIL PROTECTED] Subject: Re: XSLT vs XPathScript I prefer XPathScript. Not knowing well XSLT makes my opinion a bit useless, but anyway... When started with AxKit I was not quite familiar with XSLT (and still I'm not) so XPathScript was a wonderful replacement. It combines the power of the declarative programing and the ease of the perl syntax. I always disliked the XSLT syntax finding it to "clumsy". As an addition to the easy style transformations, you can still use the full Perl power in your stylesheets (regexp, string manipulations, etc.). The only aspect I'm not sure about is if a pipeline of XPathScript transformation is as quick as a pipeline of XSLT transformations. Anyone done such test? As a final word - I vote for XPathScript. Pavel ----- Original Message ----- From: Lyle Brooks To: [EMAIL PROTECTED] Sent: Friday, August 09, 2002 8:18 PM Subject: XSLT vs XPathScript Since both are "XML stylesheet languages", which one would/should you use? What are some of the parameters that would cause you to choose XSLT over XPathScript and vice-versa? Are there tasks that are extremely difficult in one, while easier in the other? Not being too familiar with either, I was wondering what criteria other people use for selecting the right tool for the job. Thanks. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
