- From: james anderson <james@dydra.com>
- Date: Mon, 12 Oct 2015 13:29:29 +0000
- To: public-rdf-tests@w3.org
- Message-ID: <000001505c3ddc1a-48876e71-3d49-4945-9a68-5ef294778b54-000000@eu-west-1.amazonse>
good afternoon; > On 2015-10-12, at 14:54, Karima Rafes <karima.rafes@gmail.com> wrote: > >>> (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… the protocol permits those variations for good reason. it also provides means to discover the respective capabilities. what is missing? > > […] best regards, from berlin, --- james anderson | james@dydra.com | http://dydra.com
Received on Monday, 12 October 2015 13:30:00 UTC