Re: [xsl] Strict sequential identity rule?

Subject: Re: [xsl] Strict sequential identity rule?
From: Evan Lenz <evan@xxxxxxxxxxxx>
Date: Thu, 22 Sep 2005 08:39:13 -0700
andrew welch wrote:

Can your reporting system tell when one template has been chosen oven
another purely on import precendence, even though it has a higher

No, it is strictly limited to reporting what you could easily report as a stylesheet writer about the context and what is being invoked. I suppose it could do some kind of search among all the template rules to compare patterns and the like... But then we'd be getting a lot closer to implementing XSLT in XSLT, which is a bit more of an ambitious project ;-) For now, I am letting someone else's XSLT processor do all the work. I'm going to see how far this approach can take me in visualizing XSLT's processing model. Obviously, for things like visualizing XPath evaluation, I would need other tools (assuming I don't want to implement XPath in XSLT either; don't tempt me).

However it's not, but it would be really helpful to offer a warning
such as "A template with a higher priority conflicts with a template
with a higher import precendence" for when that happens, and then
usual ambiguous rule match for when the templates are equal priority.

A better approach for this kind of thing would be to use the API of an existing open-source XSLT processor, which I think is what debuggers usually do.

Thanks for the inquiry. Good food for thought.


Current Thread