> Instead use one TDB dataset and update one graph using s-put
If I'm correct this works over HTTP; would this be a good fit for large graphs
as well (eg wikidata)?
The use case that I have in mind is "replace graph G from dataset D every once
in a while (week or month)", so I thought using a TDB2 store for each graph in
their own location was a good idea. Not different stores; all TDB2 stores. Like
this
<#dataset> rdf:type ja:RDFDataset ;
ja:namedGraph
[ ja:graphName <http://example.org/name1> ;
ja:graph <#graph1> ] ;
So I could just delete the graph folder and replace it with another directory
containing the new version of the graph created with tdb2.tdbloader.
