Under 10.1.3 we have the following paragraph on tunnel parameters:

"When a template accesses the value of a tunnel parameter by declaring it with <xsl:param tunnel="yes">, this does not remove the parameter from the base set of tunnel parameters that is passed on to any templates called by this template."


I don't quite understand this line, though I think it is meant to say declaring you want to use a tunnel parameter does not clear it (that is, remove it from scope to deeper calls).

In particular this part:

> When a template accesses the value of a tunnel parameter by declaring
> it with <xsl:param tunnel="yes">
I think my confusion comes from "accesses the value", which in my mind can only happen when a variable reference is used, in this case with the name of the tunnel param.

In line with that, "by declaring it with" suggests that "declaring" means the variable is accessed.

The language in the opening line in this section (after the first definition) uses clearer wording for the same.

Perhaps we can change it? For instance:

<proposal>
When a template brings a tunnel parameter in scope by declaring it with <xsl:param tunnel="yes">, this does not remove...
</proposal>

Or:

<proposal>
"When a template declares it wants access to the value of a tunnel parameter (by declaring it with <xsl:param tunnel="yes">), this does not remove..."
</proposal>