- From: Dan Connolly <connolly@w3.org>
- Date: Thu, 02 Mar 2000 11:58:55 -0600
- To: www-xml-linking-comments@w3.org
The spec is fairly clear about how this works:
"Note: The draft Character Model specification [CMOD] specifies that
XML-handling systems are required to treat any illegal
characters in URIs as if they
had been escaped with the %HH mechanism, whether or not they
have been. In
other words, this type of escaping may not be a necessity when
XPointers are
used in URI-references in XML documents. However, if the
URI-reference is
extracted from an XML document and then used, the escaping must
be applied."
-- http://www.w3.org/TR/1999/WD-xptr-19991206#escaping
but I'm concerned that this note might be drowned out by all the
examples in the spec that use unescaped spaces, quotes, etc.:
xpointer(id("chap1"))xpointer(//*[@id="chap1"])
Please show the equivalent URI fragment after escaping for each
example XPointer in the spec (or at least give 2 or three examples
of how the quoting works to make the concept clear.)
This one in '3.2 Evaluation Context Initialization' might be
particularly misleading,
since it includes a #, which suggests that it's ready-to-use as a URI
reference:
#xpointer(//*[local-name()='y' and
namespace-uri()='http://www.foo.com/bar'])
--
Dan Connolly, W3C http://www.w3.org/People/Connolly/
Received on Thursday, 2 March 2000 12:59:04 UTC