Saxon

Legacy ID: #5361814 Legacy Poster: Michael Kay (mhkay)

I would recommend asking questions like this on the xsl-list at mulberrytech.com - it's not a Saxon-specific question, really, and there are plenty of people on xsl-list who are happy to answer XSLT 1.0 questions. The constructs you are referring to are not, technically speaking, XPath expressions, rather they are XSLT patterns. They deliberately use the same syntax, but they are evaluated in a different way. Let's look at your two patterns (a) [contains(@class, ' topic/indexterm ')] [not(child::[contains(@class,' topic/indexterm ')])] (b) *[contains(@class, ' topic/indexterm ')]/ [contains(@class, ' topic/indexterm ')] [not(child::[contains(@class, ' topic/indexterm ')])] It seems the second pattern matches a subset of the nodes that the first pattern matches. So you probably intended that if a node matches the second pattern, then this one should be chosen. I can tell that by examining the patterns, but the XSLT processor can't (at any rate, it isn't expected to). Instead, you have to tell it to use the second pattern by giving it a higher priority: for example set priority="1" on the first template rule and priority="2" on the second. The message from Saxon is actually a warning rather than an error, and the fallback rule if two templates match with the same priority is always to choose the second, which in this case is what you probably wanted. Michael Kay

Legacy ID: #5361967 Legacy Poster: Toshihiko Makita (tmakita)

Dear Michael, Thank you for your detailed explanation. I misunderstood that pattern (a) and (b) is exclusive. I will correct the stylesheets. Regards,