RE: include vs. xsl:import

>Thanks Matt.  Which processor do you regularly use?  SAXON doesn't seem to
>be a help in this regard.  When two conflicting template rules are in the
>same stylesheet (by inclusion or not), SAXON gives priority to the one that
>is last in the stylesheet.  This isn't to say it is not conformant.  As
Mike
>Kay points out in his book, the W3C spec says, "It is an error if this
>leaves more than one match. An XSLT processor may signal the error; if it
>does not signal the error, it must recover by choosing, from amongst the
>matches that are left, the one that occurs last in the stylesheet."  My
>question is, why have this as an option at all?  It seems like for every
>option, there's a whole 'nother slew of headaches.

Hi Evan - 
yes, I use Saxon too, but to pick up the duplicate templates I used
sablotron.
In my (personal) opinion, there should not be an option to 'ignore' this
particular error, as in that case you might as well be using xsl:import.

Cheers,
Matt
******************************************************************
Warning: This email, including any attachments, 
is for the use of the intended recipient(s) only.
Republication and redissemination, 
including posting to news groups or web pages, 
is strictly prohibited without the express prior consent of Brooker's Limited.
******************************************************************


 XSL-List info and archive:  http://www.mulberrytech.com/xsl/xsl-list