- From: Martynas Jusevičius <martynas@atomgraph.com>
- Date: Fri, 4 Sep 2020 11:28:05 +0200
- To: public-sparql-dev@w3.org
- Cc: james anderson <james@dydra.com>
The only relevant text in the GSP spec is this AFAIK: "If the RDF graph content identified in the request does not exist in the server, and the operation requires that it does, a 404 Not Found response code MUST be provided in the response." https://www.w3.org/TR/sparql11-http-rdf-update/#status-codes On Fri, Sep 4, 2020 at 11:24 AM Martynas Jusevičius <martynas@atomgraph.com> wrote: > > Hi, > > I'd like to clarify what the HTTP status should be for these cases: > 1. GET default graph which is empty > 2. GET named graph which is empty > > I've looked at the GSP test suite, but I don't think they are covered: > https://www.w3.org/2009/sparql/docs/tests/data-sparql11/http-rdf-update/ > > Jena Fuseki returns 200 OK for #1 which makes sense to me (as the > default graph always exists in an RDF dataset), but we use another > product which returns 404 Not Found. > > Re. #2, is it different from a non-existing named graph which returns > 404 Not Found? That one is covered: > https://www.w3.org/2009/sparql/docs/tests/data-sparql11/http-rdf-update/#head_on_a_nonexisting_graph > > > Martynas > atomgraph.com
Received on Friday, 4 September 2020 09:28:28 UTC