Re: Update

Hello Andy

Here several examples about  the difference between the triplestore
about only the url of endpoint and the parameter HTTP for query and
update. I use a little script PHP [1] (the doc [2]) for my tests.

By default in my script, the parameter HTTP in a SPARQL query is
"query" and  the parameter HTTP in a SPARQL update is "update".

The results :
EXAMPLE : Virtuoso (uses the same endpoint for a query or a update)
./query -w -e http://localhost/tests/ -f ./example/queryWrite1.rq

./query -r -e http://localhost/tests/ -f ./example/queryRead1.rq

EXAMPLE : 4Store
./query -w -e http://localhost/ -f ./example/queryWrite1.rq

./query -r -e http://localhost/ -f ./example/queryRead1.rq

EXAMPLE : Sesame (uses a different endpoint for a query and a update)
./query -w -q http://localhost/openrdf-sesame/repositories/tests \
 -u http://localhost/openrdf-sesame/repositories/tests/statements \
-f ./example/queryWrite1.rq

./query -r -q http://localhost/openrdf-sesame/repositories/tests \
 -u http://localhost/openrdf-sesame/repositories/tests/statements \
-f ./example/queryRead1.rq

EXAMPLE : Fuseki
./query -w -q http://localhost/tests/query \
-u http://localhost/tests/update \
-f ./example/queryWrite1.rq

./query -r -q http://localhost/tests/query \
-u http://localhost/tests/update \
-f ./example/queryRead1.rq

EXAMPLE : Allegrograph  (uses a different endpoint for a query and a
update and the parameter HTTP for Update is query)
./query -w -q http://localhost/repositories/tests \
-u http://localhost/repositories/tests \
--nameParameterUpdate=query \
-f ./example/queryWrite1.rq

./query -r -q http://localhost/repositories/tests \
-u http://localhost/repositories/tests \
--nameParameterUpdate=query \
-f ./example/queryRead1.rq

(different also for Blazegraph...)

I know also that the parameter output format is different between the
triplestores... but I have not the time to test all the database
alone.

Bye
Karima

[1] https://github.com/BorderCloud/SPARQL/blob/master/query
[2] https://github.com/BorderCloud/SPARQL

2015-10-12 10:06 GMT+02:00 Andy Seaborne <andy@apache.org>:
> On 11/10/15 22:00, Karima Rafes wrote:
>>
>> Hello
>>
>> Before to change the SPARQL test suite, there is a more urgent
>> problem. I noted a lot of problems in the implementation of SPARQL
>> protocol in the triplestores (the federated query with SPARQL is of
>> the science fiction between editors of triplestores). Each editor has
>> his own definition of SPARQL protocol.
>
>
> Do you mean extensions to the protocol(s) or deviation from the protocol(s)?
> Please provide examples.
>
> http://www.w3.org/TR/sparql11-protocol/
> http://www.w3.org/TR/sparql11-http-rdf-update/
>
> (HTTP allows a fair amount of optional features as well.)
>
>         Andy
>
>
>> I propose to implement if you want in PHP a very simple library for
>> testing all the protocol query and update (via Get and Post with same
>> parameters). In parallel, I can test automatically their online
>> triplestores for helping the developers to converge.
>>
>> If I develop these new tests without participation of editors, no
>> triplestores would pass these new tests. So I'll let you decide if
>> it's useful to develop new tests for the protocol of SPARQL. If some
>> editors(minimum 2) are OK to converge, I can propose implement quickly
>> these tests via TFT [1].
>>
>> For info, the service http://sparqlscore.com/ uses the W3C's
>> repository in github. If you update the test suite SPARQL in your
>> repository, you will see the results after 24 hours on my service.
>>
>> Thanks for your help
>> Bye
>> Karima
>>
>> [1] https://github.com/BorderCloud/TFT
>>
>> 2015-10-10 19:04 GMT+02:00 Gregg Kellogg <gregg@greggkellogg.net>:
>>>
>>> Welcome to new people and organizations who have joined the CG; we now
>>> have 17 participants.
>>>
>>> Things are a bit slow right now, but we have some issues for updating
>>> tests pending [1]:
>>>
>>> * rename negative syntax tests to .err (Turtle)
>>> * missing prefixes in two negative syntax tests (Turtle)
>>> * invalid character in localName_…
>>> * Curate CWM/SWAP tests
>>> * Add Turtle, Trig, RDF/XML and SPARQL tests to better validate relative
>>> IRI resolution
>>>
>>> I would also be good for someone to propose changes to the SPARQL test
>>> suite for RDF 1.1 alignment, and other issues that have been noted.
>>>
>>> Anyone can propose issues, Pull Requests gladly accepted. Reminder: to
>>> merge such changes into the main branch requires consensus. See [2] for more
>>> information.
>>>
>>> Gregg Kellogg
>>> gregg@greggkellogg.net
>>>
>>> [1] https://github.com/w3c/rdf-tests/issues
>>> [2] http://w3c.github.io/rdf-tests/
>>>
>>>
>>
>
>

Received on Monday, 12 October 2015 08:51:26 UTC