Re: Graph Store Protocol HTTP status for empty graphs

good morning;

> On 2020-09-05, at 11:24:55, Andy Seaborne <> wrote:
> On 04/09/2020 16:46, Martynas Jusevičius wrote:
>> OK. Shouldn't there be tests for this? At least for #1?
> Would you like to contribute some tests?
>> On Fri, Sep 4, 2020 at 5:40 PM Gregory Williams <> wrote:
>>> On Sep 4, 2020, at 2:24 AM, Martynas Jusevičius <> 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:
>>>> 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.
> Better to discuss that with "the other product" to see what they say first.

he did.
he did not appreciate our interpretation.
the initial objection being, because it is not what jena does.

i suggested that, given his use case - to determine whether a sparql endpoint is available, it would be more portable to probe that endpoint for a service description.
as that is a response which is well defined, that method should be preferred to probing a different service in the hope of eliciting some response which is not.

best regards. from berlin,
james anderson | |

Received on Saturday, 5 September 2020 09:51:25 UTC