Re: Update

>> (uses a different endpoint for a query and a update)
>> (uses the same endpoint for a query or a update)
>
> Where in the specs does it say one approach is right or wrong? Reference
> please.
>
> With the right HTTP conneg and/or parameter handling, query and update are
> distinguishable just from the request.  Or maybe a parser does both.
> Implementation choice.

There are no clear references but it's a problem if we want to make a
library agnostic at all the databases and easy to use for the
developpers. If the parameters HTTP for each triplestore are
differents, the reference of protocol SPARQL  is not enough...

>
>> parameter output format is different
>
> What output parameter? There isn't on in the specs - it is a common
> extension.
>
>
> Each of us may well think some choices are better than others, or that the
> specs should have said something else, but that's not the point when
> curating the W3C test suites.

For the tests, I can use the Request Content Type (in the reference)
in the header HTTP but the basic developer JS uses the specific
parameter HTTP GET of triplestore and each triplestore implement a
different manner:
output=json
output=application/sparql-json...
format=jsonp
etc...
the reference of protocol SPARQL  is again not enough...

> PS
> .rq is the query language registered extension.
> .ru is the udpate registered extension.

Thanks

Karima

Received on Monday, 12 October 2015 12:55:06 UTC