On 12/02/12 17:44, Martynas Jusevicius wrote:
I've now come across Fuseki's DatasetAccessor
http://incubator.apache.org/jena/documentation/javadoc/fuseki/org/openjena/fuseki/DatasetAccessor.html
which seems to be the kind of interface I was thinking about.
But it doesn't look like there is an implementation over SPARQL Update?
It works over SPARQL 1.1 Graph Store Protocol.
That happens to have a mapping to SPARQL Update as given in the spec but
the whole graph protocol is more efficient.
It also works for non-SPARQL environments.
A third implementation of DatasetGraphAccessor could be added which used
SPARQL Update. Fuseki makes good use of the Graph Store Protocol already.
Andy
On Sun, Feb 12, 2012 at 6:02 PM, Martynas Jusevicius
<[email protected]> wrote:
Hey,
lets suppose I have a
1. Model m
2. graph name http://host/graph
3. remote SPARQL 1.1 endpoint URI http://host/sparql
I want to use Jena to do a SPARQL Update to insert the Model as a
named graph on the endpoint.
In other words, I want to save the Model on http://host/sparql so that
it later would be accessible in SPARQL via GRAPH<http://host/graph>.
Is there a way to do this? The only example I've found that comes
close to what I need is the following:
http://linuxsoftwareblog.com/?p=843
It involves NG4J however, I would rather avoid that.
In any case, the API workflow seems to be quite complicated to do
something as simple. Why not allow smth like this?
GraphstoreFactory.create("http://host/sparql";).addNamedModel("http://host/graph";,
m);
Martynas
graphity.org
