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.

I'd rather make it optional than drop it.

The feature does add flexibility in real-life situations. So I don't think we should give it up simply because a badly designed API does not support properly XPath.

Cheers,
-yves

Received on Thursday, 11 October 2012 14:19:02 UTC