The XForms/XPath paradox

Not sure about a better subject line, but still surely apt for this list.

>Dave Pawson
>1. Getting W3C groups to listen to the XSL WG

How about getting the left hand to talk to the right hand?

Why is it that the XForms people have to invent the "boolean-from-string"
XPath extension function?

What is missing, or has been forgotten, from our beloved XPath 2 (& XQuery
Functions & Operators library) to require such an extension function and
that which is not core?

What about, by analogy, "number-from-string" then, or is that going from
the sublime to the rediculous?

Something paradoxical about this curly one; not even religous like the
0-based, 1-based index discussion.

Why doesn't XSLT need it?  Seems either so fundamentally required or
something so fundamentally broken at the conceptual level?

Justin Johansson