RE: Children of p:choose - why are xpath-context and variable ordered?

> I thought that the main reason why p:variable comes after 
> p:xpath-context is to make sure that if you specify a 
> p:xpath-context in p:choose, it will be used as an XPath 
> context for p:variable/@select as well (if no binding is 
> specified there), and not only for the branches. If some 
> p:variables could be before p:xpath-context and some after 
> it, individual p:variables would potentially be using 
> different XPath contexts (which would be both confusing and 
> harder to implement).
> 
> But: I just read the spec again and I am not sure whether my 
> understanding was correct any more...

I take back what I just said. I think that p:variable/@select is always
evaluated against the readable input ports of the step, and this is not
affected by p:xpath-context at all.

Regards,
Vojtech