- From: Erik Wilde <dret@berkeley.edu>
- Date: Wed, 30 Jul 2014 14:13:37 +0200
- To: Ruben Verborgh <ruben.verborgh@ugent.be>
- Cc: Andreas Kuckartz <a.kuckartz@ping.de>, "public-hydra@w3.org" <public-hydra@w3.org>
hello ruben. On 30 Jul 2014, at 11:24, Ruben Verborgh <ruben.verborgh@ugent.be> wrote: >> "The 4xx (Client Error) class of status code indicates that the client >> seems to have erred." >> http://tools.ietf.org/html/rfc7231#section-6.5 >> An empty page or fragment is (normally) not a result of an error. Any >> 4xx code therefore is (normally) inappropriate. > Depends on how you look at it. > Client: "Give me the fragment with selector ?x rdf:type ex:Alien." > Server: "You asked for something that didn't exist. That's an error." > In other words, 4xx errors are those that only a client can fix. > And indeed, the client can fix by asking a different fragment. an empty result set is not an error, at least not in the overwhelming majority of database-ish interaction schemes. actually, i cannot think of a single example where a query with no results is considered an error (and i think it's rather strange to think of such a query as "an error the client has to fix"). i think it would be much better to not treat it any differently than a query with a non-empty result. cheers, dret.
Received on Wednesday, 30 July 2014 12:14:13 UTC