Re: A proposed solution

> The process described below requires:
> - an understanding of protocol port numbers
> - an understanding of URI encoding
> - an understanding of which part of the URI is the hostname, and
therefore
> case-insensitive
>
> Does all of this additional information really belong in an XML parser?

The clarification [1] that I made hopefully made it clear (rule 2) that
you can do octet-by-octet comparison taking into account relative URIs but
that it is also allowed to be smarter and do more normalization if
desired. The point is that a provider of a name MUST NOT assign different
semantics to  http://WWW.MS.COM vs http://www.ms.com vs
http://www.ms.com:80 for example.

Henrik

[1] http://lists.w3.org/Archives/Public/xml-uri/2000Jun/0721.html