|
[XSL-LIST Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message] Re: Tricky inclusion match
Karl,
At 03:37 PM 3/30/2005, you wrote: I was able to put most of your stuff to work in my "real" scenario but got a little stuck because my data looks like this (hierarchely) Yes, in this case the XPath would be more complicated ... sth like field[@fieldname='color'][not(.=preceding-sibling::field[@fieldname='color'])][.=$colors] etc. When things get really gnarly, variables are a big help. I hope that nobody gets upset because I inquired with a simplified example of my data, It was easier than trying to describe the real data I had. Not at all: actually, I think that's generally a good idea. As long as you don't simplify the problem away! since it's *not* cool to say "thanks for the help, but that wasn't the real problem". But if you represent the problem properly, not only is no harm done, it's easier for everyone. Cheers, Wendell
|
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
|

Cart








