Subject: RE: [xsl] how to: Conditionally call nested XSLs based on parameters or variables passed to it at a higher level?|
From: Wendell Piez <wapiez@xxxxxxxxxxxxxxxx>
Date: Fri, 12 Sep 2003 17:04:05 -0400
Please have a look at this. http://www.biglist.com/lists/xsl-list/archives/200309/msg00470.html
Here I have implemented with the help of a number of significant people, a parameter passing model that goes into nested templates ( basically templates that are called by others, i.e. where X calls Y but Y can never call X. It's kind of Y nested inside X.
I am trying to do the same for the entire document stylesheets I have so that I do not have to hard code the stuff.
Of course, Dimitre in effect I want to achieve the functional programming paradigm while maintaining XSL 1.0 specs ( the ones current supported by the System.Xml.Xsl transform ) ( I do know that Saxon supports XSLT 2.0 with Functions but I cannot use those things.)
Also, the FXSL project. Are they a set of XSL based extension libraries or will I actually need to install "extension" code with my XSLT processor.
I would like to remain "pure" xsl 1.0 as much as possible. So, any comments or ideas based on the (above URL) and improving that would be great. Any other "pure XSL" ideas would be nice.
I have printed out that whitepaper of yours that talks about " One particularly elegant way to deal with parameters scoping is by using partial application -- described in the second reference above. "
___&&__&_&___&_&__&&&__&_&__&__&&____&&_&___&__&_&&_____&__&__&&_____&_&&_ "Thus I make my own use of the telegraph, without consulting the directors, like the sparrows, which I perceive use it extensively for a perch." -- Thoreau