The template rule <xsl:template match="item[position() mod $thisnup = 1]"> should generate an error because the match attribute has a variable in it. http://www.w3.org/TR/xslt#section-Defining-Template-Rules I like that it does not generate an error. The variable can be resolved at runtime and the match's expression with the variable gives me a way to generate different results, based on the value at runtime. But it is not correct... I reported this to the mozilla folks http://bugzilla.mozilla.org/show_bug.cgi?id=134013 there are test cases there Gary
This raises that old debate about variables inside predicates. You quoted 5.3. Section 5.2 says "predicates in a pattern can use arbitrary expressions..."
Test case idkey43 can be used as an example. Some processors allow this use of a variable. Scott Boag thinks we should issue a warning but allow the usage.
Also see idkeyerr21, which is more universally agreed upon as an error. This case is reported in bug #5202, which may be deemed a duplicate only if one fix will swat both.
eeewwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwwww
Tried to reassign this to xalan, but don't have that in the product select box -> xmlcommons is the closest I could find... Sorry...
You couldn't find it in Bugzilla because Xalan now uses JIRA (http://issues.apache.org/jira) for bug tracking. If this bug report is still relevant, please re-open it there.