Re: Proposed resolution of HRRI/IRI discussion

> >> If LEIRIs said that square brackets in the fragment get %-escaped
> >> by the processor, and we changed the specs to refer to LEIRIs, that
> >> would be a normative change.

> That depends on the perspective ... (RFC 2732 Grammar vs. Prose)

But we're not talking about RFC 2732, we're talking about XML 1.0,
XInclude, the XPointer draft and so on.  And they don't rely on 2732
for the list of characters, even if they refer to it.  For example,
the XPointer draft http://www.w3.org/TR/2001/CR-xptr-20010911/#escaping
says:

  The disallowed characters include all non-ASCII characters, plus the
  excluded characters listed in Section 2.4 of [IETF RFC 2396], except
  for the number sign (#) and percent sign (%) and the square bracket
  characters re-allowed in [IETF RFC 2732]. Disallowed characters are
  escaped as follows: [...]

That says that square brackets are not in the set of disallowed
characters, regardless of what 2732 itself says.

Similarly, XML 1.0 http://www.w3.org/TR/REC-xml/#sec-external-ent says:

  The characters to be escaped are the control characters #x0 to #x1F
  and #x7F (most of which cannot appear in XML), space #x20, the
  delimiters '<' #x3C, '>' #x3E and '"' #x22, the unwise characters '{'
  #x7B, '}' #x7D, '|' #x7C, '\' #x5C, '^' #x5E and '`' #x60, as well as
  all characters above #x7F.

and square brackets are not in that list.  Even if 2732 is ambiguous,
these specs are not.

-- Richard

Received on Tuesday, 6 November 2007 09:11:44 UTC