W3C home > Mailing lists > Public > www-rdf-interest@w3.org > May 2003

Answers to URIQA Questions + Appologies

From: Derrish Repchick <drepchick@intellidimension.com>
Date: Thu, 22 May 2003 18:51:01 -0400
Message-ID: <00bf01c320b4$ac0819c0$1ba672d8@dpr2000>
To: <www-rdf-interest@w3.org>

I'm sorry about the multiple postings of my original questions. I was having
a bad email day.

> Q1) Will proxy servers present problems w.r.t. the URI in the HTTP
> GET http:://example.com/document.html ----> GET /document.html
> URI-Resolution-Mode: Description

After looking over the HTTP1.1 spec I think URIQA is fine with proxy
servers. It looks like the proxy will turn the request URI into an absolute
path but host information is preserved in the header field Host (ex: Host:

GET /document.html
Host: example.com

So the original URI can be reconstructed by the server.

> Q2) How are equivalent URLs dealt with?
> GET http:://example.com/document.html
> URI-Resolution-Mode: Description
> GET http:://
> URI-Resolution-Mode: Description
> GET http:://example.com:80/document.html
> URI-Resolution-Mode: Description
> GET http:://example.net/document.html
> URI-Resolution-Mode: Description
> Should the server map these requests onto the same resource?

After thinking about this some more it seems to me from a trust standpoint
its important that the subject of the statements returned to the agent have
exactly the same URI that was used in the request. So if an agent requests
information about http://example.net/document.html then the server must
respond with statements about that URI and not some internal URI used to
store the information ( http://example.com/document.html). So if internally
the server performs some mapping before querying for the information then it
must reverse the mapping in the response.

Derrish Repchick
Intellidimension Inc
Received on Thursday, 22 May 2003 18:44:21 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:44:42 UTC