comparing IRI references, in http://www.w3.org/TR/xml-names11/#IRIComparison

I think there's quite a bit of discomfort with
section 2.3 because of its implication for IRI
deployment:

  http://www.example.org/rosé 
  http://www.example.org/ros%c3%a9 
  http://www.example.org/ros%c3%A9 
  http://www.example.org/ros%C3%a9 
  http://www.example.org/ros%C3%A9 


I think the problem is that the Candidate Recommendation
makes no recommendation about the possible simultaneous
use of all of these as namespace names.

I think the simplest way of resolving the possible
contradiction would be  disallow hex-escaping in
IRIs used for namespace names.

More generally, it would be a good idea to strongly
discourage the simultaneous use of multiple URIs
or IRIs that might, for some applications, be considered
equivalent:

  http://www.example.org and http://www.example.org/

should not both be used as namespace names even
though they are not string-equal.

Larry