On 18/06/15 07:26, Claude Warren wrote:
I seem to be going around in circles with the fuseki documentation.
Does Fuseki support the POST command as noted at
http://www.w3.org/TR/2013/REC-sparql11-http-rdf-update-20130321/#http-post
To reword slightly to make the boundary clear: my emphasis:
[[
POST /rdf-graph-store?default HTTP/1.1
Host: example.com
Content-Type: text/turtle
** RDF payload **
is considered to have the same effect as:
INSERT DATA { ** RDF payload ** }
]]
There are two sections there.
(I believe it does from reading the docs)
It does.
I am attempting to execute an INSERT
which is not in the Graph Store Protocol.
http://www.w3.org/TR/sparql11-protocol/#update-operation
for sending SPARQL Updates.
I have started fuseki on my linux system using
fuseki-server -mem /tst
I am using the Apache httpcomponents library
I am posting to http://localhost:3030/tst/data?default
Graph Store Protocol != SPARQL Update over HTTP
The SPARQL Update endpoint is usually:
http://localhost:3030/tst/update
whereas you can POST RDF data to the default graph, with conneg:
http://localhost:3030/tst/data?default
I have set the content type to text/turtle
the text that is being posted is
INSERT DATA
{
<urn:foo:s> <urn:foo:p> <urn:foo:o> .
}
The fuseki log shows:
[2015-06-18 07:20:32] Fuseki INFO [1] POST
http://localhost:3030/tst/data?default
[2015-06-18 07:20:32] Fuseki INFO [1] POST /tst :: 'data' ::
[text/turtle charset=UTF-8] ? default
Conneg has decided on
text/turtle
INSERT DATA
is not Turtle.
[2015-06-18 07:20:32] Fuseki ERROR [line: 1, col: 1 ] Out of place:
[KEYWORD:INSERT]
[2015-06-18 07:20:32] Fuseki INFO [1] 400 Parse error: [line: 1, col:
1 ] Out of place: [KEYWORD:INSERT] (62 ms)
The BasicHttpResponse I am getting back is:
HTTP/1.1 400 Parse error: [line: 1, col: 1 ] Out of place: [KEYWORD:INSERT]
[Fuseki-Request-ID: 2, Server: Fuseki (2.0.0-SNAPSHOT), Content-Type:
text/plain; charset=UTF-8, Cache-Control:
must-revalidate,no-cache,no-store, Pragma: no-cache, Content-Length: 147]
ResponseEntityProxy{[Content-Type: text/plain;
charset=UTF-8,Content-Length: 147,Chunked: false]}
I must be doing something silly. Does anyone see what the issue is?
Claude
Andy
