- From: Norman Walsh <Norman.Walsh@Sun.COM>
- Date: Tue, 26 Apr 2005 10:30:21 -0400
- To: Elliotte Harold <elharo@metalab.unc.edu>
- Cc: public-xml-id@w3.org
- Message-id: <87acnlfw5e.fsf@nwalsh.com>
/ Elliotte Harold <elharo@metalab.unc.edu> was heard to say: | Norman Walsh wrote: | |> | //*/@xml:id when xml: is not bound. |> XPath context/API initialized incorrectly. Bug. | | What part of the XPath 1.0 specification justifies this interpretation? I can't | find it. Does 2.0 clear this up? | |> | //*/@foo:id when foo: is bound to the XML Namespace URI. |> XPath context/API initialized incorrectly. Bug. | | Ditto. What part of the XPath 1.0 specification says that the foo prefix can't | be mapped to the XML namespace URI? I think it follows from "The prefix xml is by definition bound to the namespace name http://www.w3.org/XML/1998/namespace." in the namespaces recommendation. I thought there was a statement somewhere that it was illegal to bind any other prefix to that URI but I can't find it quickly. I will endeavor to make sure that the XPath 2.0 spec is clear on this point. Be seeing you, norm -- Norman.Walsh@Sun.COM / XML Standards Architect / Sun Microsystems, Inc. NOTICE: This email message is for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply email and destroy all copies of the original message.
Received on Tuesday, 26 April 2005 14:30:32 UTC