> It also means that anyone who tells you that they are using Javascript
> because "XSLT cannot do xxx" is wrong (though they might be correct if they
> argued instead that "XSLT can't do xxx easily/efficiently).

I guess that there are some xxx things that can be done using Javascript and the
DOM, and that cannot be done in XSLT.

Not even thinking about Turing-completeness we should first be aware that XSLT has
***limited*** access to certain kinds of data.  This affects what can be done with
XSLT, even though it is Turing-complete.

There are examples (including some in your book) of processing, which cannot be done
in "pure" XSLT due to the limited access to information -- the XML - Infoset model.

This is certainly a minor, but necessary correction.

Dimitre Novatchev.


__________________________________________________
Do You Yahoo!?
Get personalized email addresses from Yahoo! Mail - only $35 
a year!  http://personal.mail.yahoo.com/

 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list