Re: [MASSMAIL]Re: Splitting data into graphs vs datasets

In my opinion, a graph is like a schema in relational database, and a dataset is like a database instance. Regards, David -Daan Reid <osmo...@dds.nl> escribió: - Para: users@jena.apache.org De: Daan Reid <osmo...@dds.nl> Fecha: 22/03/2018 11:35 Asunto: [MASSMAIL]Re: Sp

Re: Splitting data into graphs vs datasets

I would say that using separate datasets is a good idea if you have sets of graphs that just don't belong together. The dataset as an organisational, abstract container is an excellent idea, in my opinion. Regards, Daan On 22-03-18 11:22, Mikael Pesonen wrote: Ok seems that using many

Re: Splitting data into graphs vs datasets

Ok seems that using many datasets is not a good idea. I had no bias and not having any issues with speed, just wanted to see what is best way to go. On 21.3.2018 20:48, ajs6f wrote: Those sure are good reasons for using named graphs. But what about using different datasets too? Consider

Re: Splitting data into graphs vs datasets

> Those sure are good reasons for using named graphs. But what about using > different datasets too? Consider that you may not be seeing such reasons because it may not actually be as good an idea. Here's another reason to prefer graphs: There is a standard management HTTP API for named

Re: Splitting data into graphs vs datasets

Is this example from web page (a bit modified) config_ds1.ttl: @prefix fuseki: . @prefix rdf: . @prefix rdfs: . @prefix tdb:

Re: Splitting data into graphs vs datasets

You can run many datasets by using the --config argument and specifying an appropriate configuration file. This should be used instead of the --loc argument which is a convenience short cut to run a server with a single dataset.

Re: Splitting data into graphs vs datasets

Those sure are good reasons for using named graphs. But what about using different datasets too? btw, I couldn't find info on how to run many datasets with Fuseki. is it just one dataset per fuseki process? -loc parameter for fuseki-server.jar? Br On 20.3.2018 14:22, Martynas Jusevičius

Re: Splitting data into graphs vs datasets

Provenance. With named graphs, it's easier to track where data came from: who imported it, when etc. You can also have meta-graphs about other graphs. Also editing and updating data. You can load named graph contents (of smallish size) in an editor, make changes and then store a new version in