FW: Compiling information from several different triplestores

0 views
Skip to first unread message

Linde, A.E.

unread,
May 5, 2009, 10:12:11 AM5/5/09
to skd
SKUA’s next challenge...

T.

--
Tony Linde
Project Manager
Department of Physics & Astronomy
University of Leicester

------ Forwarded Message
From: Nicolas Raoul <nicolas.r...@gmail.com>
Date: Tue, 5 May 2009 11:33:13 +0100
To: <semant...@w3.org>
Subject: Compiling information from several different triplestores


Hello all,

How can I run a query over several different triplestores ?

For instance, I want to get a list of Anthony's friends.
Triplestore1 says Jack is Tony's friend.
Triplestore2 says Tony sameAs Anthony.
What clever mechanism would undestand that Jack is Anthony's friend?
Do I have to copy all information from both triplestores my own
triplestore, or is there something smarter to do ?

Copying all information from external triplestores seems awkward, and
in some cases might prove impossible (frequent updates, size, load on
servers).
Is there an easy solution that I am not aware of?
Can any triplestore implementation be configured to complement its
information with information from external triplestores?

Thank you!
Nicolas Raoul
http://nrw.free.fr




------ End of Forwarded Message

Norman Gray

unread,
May 5, 2009, 11:17:07 AM5/5/09
to skua-d...@googlegroups.com

Tony, hello.

On 2009 May 5, at 15:12, Linde, A.E. wrote:

> SKUA's next challenge...

> ------ Forwarded Message
> From: Nicolas Raoul <nicolas.r...@gmail.com>
> Date: Tue, 5 May 2009 11:33:13 +0100
> To: <semant...@w3.org>
> Subject: Compiling information from several different triplestores
>
>
> Hello all,
>
> How can I run a query over several different triplestores ?

This is very hard in general! Greg Williams, who's now working with
Peter Fox at RPI, was describing some stuff about this at the last
ESWC (did you meet him -- a quiet guy with a small mohican). I get
the impression from him that it's all a bit hairy, because you never
really know when to stop. We evade that, mercifully, by having pretty
homogeneous data in each SAC, so we don't really have any queries that
need to be run over the union of the SACs (we're only interested in
the union of the results from each SAC).

...but piggybacking on Greg's stuff would be nice for the future. And
probably good fun, too.

See you,

Norman


--
Norman Gray : http://nxg.me.uk
Dept Physics and Astronomy, University of Leicester

Reply all
Reply to author
Forward
0 new messages