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: whereeve
yes indeed, that sounds good.
Thanks!
PS: maybe you should put a keyword like "import" on the page, I searched
just for that, but nevermind.
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 virtua
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
umh, can I haz a reply? :)
Am Montag, den 02.07.2012, 18:35 +0200 schrieb Jonas Brekle:
> Hi,
>
> 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
Hi,
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
