http://lists.w3.org/Archives/Public/xsl-editors/2004JanMar/0013.html
<script/> is not just inefficient, but introduces potential'side-effects' into the xslt transformation which introduces all sortsof fun problems for both XSLT processor implementators, as well ascreating non-portable xslt. The idea that XSLT does not have such an element means that it is morereliable, simple, and stable...not the opposite. XSLT primary purpose is to transform data into another set of data, notas a programming language...using XSLT in conjunction with otherprogramming languages means that marshaling data code usually movesacross to XSLT, though this doesnt mean that XSLT should becomeresponsible or 'host' another languages functionality.....though XSLT2.0 is looker more like a programmatic language its main job is still totransform data, and I think that the editors have done a good balancingact.Is it possible to describe a scenario or use case that absolutelyrequires <script/> ?reviewing the xslt list archives will reveal quite a few threads alongthis line.cheers, Jim
http://www.xml.com/pub/a/2001/02/14/deviant.html