W3C home > Mailing lists > Public > public-lod@w3.org > November 2010

Re: 200 OK with Content-Location might work: But maybe it can be simpler?

From: Antoine Zimmermann <antoine.zimmermann@insa-lyon.fr>
Date: Fri, 05 Nov 2010 19:01:16 +0100
Message-ID: <4CD4466C.5040602@insa-lyon.fr>
To: public-lod <public-lod@w3.org>
I'm wondering about the implications of the httpRange-14 decision. In 
summary, it says:

a) if it's 2xx, then it's an information resource;
b) if it's 303, then it's whatever;
c) if it's 4xx, then it's whatever.

First, I'm wondering what is the difference between b) and c). Second, 
I'm wondering what it implies for other codes, such as 3xx and 5xx. And 
what about URIs that do not resolve (like hash-URIs)?

It seems to me that the absence of specification for these codes means 
that the URIs may mean whatever. So, is it correct to interpret 
httpRange-14 as follows:

a) if a GET request returns 2xx on a URI then the URI denotes an 
information resource;
b) a URI can be any kind of resource otherwise.

Antoine Zimmermann
Researcher at:
Laboratoire d'InfoRmatique en Image et Systèmes d'information
Database Group
7 Avenue Jean Capelle
69621 Villeurbanne Cedex
Lecturer at:
Institut National des Sciences Appliquées de Lyon
20 Avenue Albert Einstein
69621 Villeurbanne Cedex
Received on Friday, 5 November 2010 18:01:50 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:51 UTC