Can you please describe your idea in more detail? What information is stored localy ? And how to perform queries ? For example: "Select all resources that have a label <string literal> " and " Select all [music]files that has a <NCO:Contact | where this nco:contact is stored localy> as author".
On Tue, Jun 29, 2010 at 2:21 PM, Daniele E. Domenichelli < [email protected]> wrote: > On 06/28/2010 09:12 PM, Vishesh Handa wrote: > >> > Because, as I understood, the RDF repository is going to be exposed > >> > through HTTP, so you could connect to anyone's repository and just > >> > insert their address in the graph metadata of the statements you store > >> > locally. > >> > > > No, I don't think we should expose it via HTTP. ( Might be problematic ) > > There is a project in the playground called nsqd (Nepomuk Social Query > > Daemon ), which does something similar. I'll take a look at it. > > > As this is a brainstorming I'll propose a crazy idea that just came to > my mind working on telepathy kioslave :) > > Each remote resource could be stored locally using some uri like > telepathy:/contact/<name>/nepomuk/<resource> > or > nepomuk:/telepathy/contact/<name>/<resource> > > Queries implying a resource like that could contact the remote nepomuk > storage and execute both a local query using that address and a remote > query just changing the resource name to "nepomuk:/<resource>" > > > Cheers, > Daniele > > > _______________________________________________ > Nepomuk mailing list > [email protected] > https://mail.kde.org/mailman/listinfo/nepomuk > -- Sincerely yours, Artem
_______________________________________________ Nepomuk mailing list [email protected] https://mail.kde.org/mailman/listinfo/nepomuk
