W3C home > Mailing lists > Public > www-tag@w3.org > June 2005

Re: [httpRange-14] Resolved

From: Jan Algermissen <jalgermissen@topicmapping.com>
Date: Sun, 19 Jun 2005 10:30:33 +0200
Message-Id: <82709DB0-4E4F-4E80-ACCD-1393D236E923@topicmapping.com>
To: W3C TAG <www-tag@w3.org>

TAG members,

two immediate questions:

Given the resolution below, it is not good practice and not in sync  
with Web architecture
to issue a URI for a dog and have the server deliver 2xx responses, yes?

What about URIs with fragment identifiers? If a GET to http:// 
returns 2xx does that also imply that ttp://www.example.org/list-of- 
my-stuff#my-dog is
an information resource?

Or asked in another way: is the server's response code to a URI also  
considered the response code of any fragment identifier URIs 'based'  
on this URI?


On Jun 19, 2005, at 6:25 AM, Roy T. Fielding wrote:

> As everyone here knows, the TAG has spent a great deal of time
> discussing the httpRange-14 issue, as described at
>    http://www.w3.org/2001/tag/issues.html#httpRange-14
> I am happy to report that we came up with a reasonable
> compromise solution at the recent TAG f2f meeting at MIT.
> <TAG type="RESOLVED">
> That we provide advice to the community that they may mint
> "http" URIs for any resource provided that they follow this
> simple rule for the sake of removing ambiguity:
>   a) If an "http" resource responds to a GET request with a
>      2xx response, then the resource identified by that URI
>      is an information resource;
>   b) If an "http" resource responds to a GET request with a
>      303 (See Other) response, then the resource identified
>      by that URI could be any resource;
>   c) If an "http" resource responds to a GET request with a
>      4xx (error) response, then the nature of the resource
>      is unknown.
> </TAG>
> I believe that this solution enables people to name arbitrary
> resources using the "http" namespace without any dependence on
> fragment vs non-fragment URIs, while at the same time providing
> a mechanism whereby information can be supplied via the 303
> redirect without leading to ambiguous interpretation of such
> information as being a representation of the resource (rather,
> the redirection points to a different resource in the same way
> as an external link from one resource to the other).
> Cheers,
> Roy T. Fielding                            <http://roy.gbiv.com/>
> Chief Scientist, Day Software              <http://www.day.com/>

Jan Algermissen, Consultant & Programmer                              
Tugboat Consulting, 'Applying Web technology to enterprise IT'        
Received on Sunday, 19 June 2005 08:30:38 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 22:56:09 UTC