Beyond that, the comparison rules for UTF8 strings look wrong --
I'm glad there's a matching rule specified, but from the little I
understand about such things there will be a lot of complaints
about the lack of more CJK-friendly matching rules.
Actually, they should not -- because URIs, as currently
defined, are strictly a subset of 0-127 ascii. If you
want anything else, you have to encode it (e.g., hex encoding).
OK -- but in that case, why does the document say that the identifier
can be a UTV8 string?