Re: Compound filter in for-each
At 04:44 PM 3/26/2009, you wrote:
Out of interest (and to facilitate further understanding) would you be kind enough to illustrate how you would approach my filtering problem with template matching rather than with xsl:choose?
It's likely that you could inspire a small friendly competition along those lines, but might you post a small sample of input data, with a prose spec and/or sample of desired results, to encourage those who might be inclined to try their hand?
As I said, your problem isn't the kind of problem that lends itself to templates: it's more of a "pull" than a "push". Learn about this distinction at (just a more-or-less random grab)
http://www.xml.com/pub/a/2005/07/06/tr.html http://www.ibm.com/developerworks/xml/library/x-xdpshpul.html http://www.eddiewelker.com/2008/11/25/push-style-xslt-vs-pull-style/
Nonetheless it's quite possible that someone practiced in the arts could make some nice template-driven logic for your case. This would depend on the details of your spec. Keep in mind that template matching really becomes useful as transformation problems become complex; when they're simple there's not always much evident gain.
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format