Re: A proposed solution

Daniel,

There is nothing HTTP specific in the description of how to compare URIs -
it just happens that HTTP URIs "use" all features of the URI spec. This is
why the section is called "URI Comparison". The rules are general for any
URI.

The other point that I made was that "it is ok to do octet-by-octet
comparison if you take into account relative URIs". If an application
wants to do smarter comparison then it is free to do so but you don't have
to.

So, the answers to your questions are no and no but that is also not what
was said.

>   - why HTTP only ? what's happen if I want to put Schemas which are the
>     binding contract for my electronic commerce on a secure https server
?
>     should we duplicate all rules applying to HTTP to HTTPS in the
namespace
>     spec ?
>   - should all that protocol dependant rules be added to a data language
>     description ?

Henrik