> On the nighmare issue, originally all XForms XPath extension functions
> were in the XForms namespace, but we removed that as a result of public
> comments that showed that the XPath 1.0 Recommendation did not allow
> qualified names,
??? XPath1 (and now 2) specifies function names are QNames.
> and that neither XSLT nor XML Signature W3C
> recommendations specified qualified names as extension functions.
??? XSLT 1 mandates that all extension functions use qualified names with
a non empty prefix. xslt 1 says:
If a FunctionName in a FunctionCall expression is not an NCName
(i.e. if it contains a colon), then it is treated as a call to an
extension function
> extension functions would be namespaced in XPath 2.0. But the botch is
> with XPath 1.0 not allowing them.
In what way are they disallowed in XPath 1?
David
