Using Graph Groups to virtual import multiple graphs into one works fine, but unfortunately in the DBpedia VAD, in the description.vsp, data is retrieved directly from the RDF_QUAD table, which circumvents the SPARQL query expansion.
I tried refactoring this a bit, altering the SQL query: whereever a query restricts like G = _G i put G IN (SELECT RGGM_MEMBER_IID as gr FROM DB.DBA.RDF_GRAPH_GROUP, DB.DBA.RDF_GRAPH_GROUP_MEMBER WHERE RGG_IID = RGGM_GROUP_IID and RGG_IRI = project_home_page) instead. Just in case somebody else wants to do this (for example multiple DBpedia editions). I think its very handy to have the possibility to query the global graph and get multilingual results, but if you only want one language (or want to compare two languages) you can still query them individually... > Am Montag, den 16.07.2012, 16:18 +0100 schrieb Tim Haynes: > > On 07/02/2012 05:35 PM, Jonas Brekle wrote: > > > i wondered, can I configure Virtuoso to virtuall import a graph into > > > another? What I mean is: > > > /-- A > > > G <------- B > > > \-- C > > > > > > Where G, A, B, C are graphs and when I query G, I get results as if I > > > queried G, A, B, C (four FROMs). Implementing a owl:import inference. > > > If I query A or B or C alone, I get only results from this single > graph. > > > > > > How can I do this? > > > > Sounds suspiciously like our Graph Groups: > > > http://docs.openlinksw.com/virtuoso/rdfgraphsecurity.html#rdfgraphsecuritygroups > > > > > > That any use? > > > > HTH, > > > > ~Tim > > >
