Subject: [xsl] Re: Ignoring ambiguous matches From: Ihe Onwuka <ihe.onwuka@xxxxxxxxx> Date: Thu, 13 Feb 2014 01:24:26 +0000 |
So I guess it's http://www.w3.org/TR/2006/PR-xslt20-20061121/#conflict and the extent to which next-match gets around it where multiple rules evaluate to the same priority/import precedence. On Thu, Feb 13, 2014 at 1:19 AM, Ihe Onwuka <ihe.onwuka@xxxxxxxxx> wrote: > hmmmm thinking about that for a moment that cunning plan will probably > not work . next-match applies the next best matching template rule, if > the next best was at the same priority then whats to stop it going > into an infinite loop - unless it is implemented not to apply the same > rule more than once. > > So it looks like some means of establishing different priority - > whether by template priority or import hierarchy is necessary. > > Then again who is to say (the spec) that next best necessarily > excludes rules at the same priority > > On Thu, Feb 13, 2014 at 1:06 AM, Ihe Onwuka <ihe.onwuka@xxxxxxxxx> wrote: >> I am about to write several template rules that will all match the >> same node but will each apply (or try to apply) a different edit. >> >> I don't care the order in which these are applied as long as each gets >> a shot at applying it's edit. >> >> I was wondering whether I can just ignore the ambiguous match warnings >> and be confident that everything is A - ok or whether I have to >> diligently invent template priorities to prevent that.
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
[xsl] Re: Ignoring ambiguous matche, Ihe Onwuka | Thread | Re: [xsl] Ignoring ambiguous matche, Graydon |
[xsl] Re: Ignoring ambiguous matche, Ihe Onwuka | Date | Re: [xsl] Ignoring ambiguous matche, Graydon |
Month |