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 the same graph. You probably would not want to do this with a large default graph. On Tue, Mar 20, 2018 at 1:16 PM, Mikael Pesonen <mikael.peso...@lingsoft.fi> wrote: > > Hi, > > I'm using Fuseki GSP, and so far have put all data into one default > dataset and using graphs to split it. > > If I'm right there would be benefits using more than one dataset > - better performance - each query is done inside a dataset so less data = > faster query > - protection of data - can't "accidentaly" query data from other datasets > Downsides: > - combining data from various datasets is heavier task > > Is this correct? Any other things that should be considered? > > Thank you > > -- > Lingsoft - 30 years of Leading Language Management > > www.lingsoft.fi > > Speech Applications - Language Management - Translation - Reader's and > Writer's Tools - Text Tools - E-books and M-books > > Mikael Pesonen > System Engineer > > e-mail: mikael.peso...@lingsoft.fi > Tel. +358 2 279 3300 > > Time zone: GMT+2 > > Helsinki Office > Eteläranta 10 > <https://maps.google.com/?q=Etel%C3%A4ranta+10&entry=gmail&source=g> > FI-00130 Helsinki > FINLAND > > Turku Office > Kauppiaskatu 5 A > <https://maps.google.com/?q=Kauppiaskatu+5+A&entry=gmail&source=g> > FI-20100 Turku > FINLAND > >