- From: Norman Walsh <ndw@nwalsh.com>
- Date: Mon, 27 Apr 2009 07:06:33 -0400
- To: public-xml-processing-model-comments@w3.org
- Message-ID: <m2r5zemk3q.fsf@nwalsh.com>
"Toman_Vojtech@emc.com" <Toman_Vojtech@emc.com> writes:
> 1. The default namespace is "http://foo.com",
> 2. the default namespace is included in the set of in-scope namespaces of the processor XPath context (section 2.6.1.1),
> 3. the local function name contains() resolves to {http://foo.com}contains(), which of course does not exist
> 4. ... and the XPath expression fails
Like XSLT, the default namepace doesn't apply to names without a colon
in them. I expect we should be more explicit that that includes not
only element names, but also function names.
We don't provide a mechanism for changing the default function
namespace, but I'm not sure it's really important enough in our spec.
Be seeing you,
norm
--
Norman Walsh <ndw@nwalsh.com> | All the labors of the ages, all the
http://nwalsh.com/ | devotion, all the inspiration, all the
| noonday brightness of human genius, are
| destined to extinction.--Bertrand
| Russell
Received on Monday, 27 April 2009 11:07:26 UTC