W3C home > Mailing lists > Public > public-xml-processing-model-wg@w3.org > September 2010

Shouldn't p:choose report err:XD00026, too?

From: <vojtech.toman@emc.com>
Date: Mon, 20 Sep 2010 05:57:08 -0400
Message-ID: <997C307BEB90984EBE935699389EC41C024E0171@CORPUSMX70C.corp.emc.com>
To: <public-xml-processing-model-wg@w3.org>
Hi all,

For p:option, p:with-option, p:variable, p:with-param, the spec says:

"In an XPath 1.0 implementation, if p:empty is given or implied as the
document connection, an empty document node is used as the context node.
In an XPath 2.0 implementation, the context item is undefined. It is a
dynamic error (err:XD0026) if the select expression makes reference to
the context node, size, or position when the context item is undefined."

But for p:choose and p:xpath-context, it only says:

"In an XPath 1.0 implementation, if the context node is connected to
p:empty, or is unconnected and the default readable port is undefined,
an empty document node is used instead as the context. In an XPath 2.0
implementation, the context item is undefined."

Shouldn't p:choose report err:XD0026 if the expression makes a reference
to the context, too?

Regards,
Vojtech

--
Vojtech Toman
Consultant Software Engineer
EMC | Information Intelligence Group
vojtech.toman@emc.com
http://developer.emc.com/xmltech
Received on Monday, 20 September 2010 09:58:11 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 20 September 2010 09:58:11 GMT