Protocol validator

I'm now at 30/34 failing these tests.

     update_dataset_default_graphs
     update_dataset_named_graphs
     update_dataset_full
     bad-update-missing-direct-type

The first 3 are for the same reason.

Issue 1:
     update_dataset_default_graphs
     update_dataset_named_graphs
     update_dataset_full

Could you explain these please?  From logging the Fuseki server requests 
received I don't see how they are supposed to return the ASK result of 
true that is expected:

To take
   update_dataset_default_graphs
as an example:

It has

...
INSERT {
   GRAPH <http://example.org/protocol-update-dataset-graphs-test/> {
     ?s a dc:BibliographicResource
}
...

Note the graph URI is ...dataset-graphs-test...

The query has:
ASK {
   GRAPH <http://example.org/protocol-update-dataset-test/> {
     <http://kasei.us/2009/09/sparql/data/data1.rdf> a 
<http://purl.org/dc/terms/BibliographicResource> .

which is a different GRAPH URI, hence GRAPH does not match and the 
FILTER NOT EXISTS does not matter.  Hence result is "false" from my reading.

Issue 2:
    bad-update-missing-direct-type

This test is sending a SPARQL Update without content type.

With a no "Content-type" request, Fuseki assumes 
"application/sparql-update" which makes it easier for simple clients to 
open a POST stream and send an update.

I don't see anything in the spec that requires an error if the content 
type is not 'application/x-www-url-form-urlencoded' and not 
'application/sparql-update'.

My reading is that it is simply outside the spec at this point so a 
server that does something is not non-conformant, just helpful.

     Andy

Received on Monday, 27 August 2012 16:03:31 UTC