Re: Make its:param optional?

How about dropping it completely? It is handy, but it adds complexity (e.g.
how does it interact with query language?), and others might have the same
implementation issues like you.

- Felix

2012/10/10 Shaun McCance <shaunm@gnome.org>

> I was working with the DOM XPath API and noticed that it doesn't
> have a standard way of binding variables to an XPath evaluation
> context. That means you really can't support its:param if you're
> using that API.
>
> Would it make sense to make its:param an optional feature? We
> were careful to specify that no variables should be used unless
> specified in an its:param element. So I think we could safely
> say something like "an implementation that does not support
> its:param must not apply any rules from an its:rules element
> that contains any its:param elements".
>
> --
> Shaun
>
>
>
>


-- 
Felix Sasaki
DFKI / W3C Fellow