1) What relations should be copied ? E.g. music file has a relation nao:condutcor that points to some nco:contact. When copying resource,that represents this file should we copy nco:contact too ? If we don't copy nco:contact, then - as I see - when searching for "All music files that has XX as conductor" we must execute this query in almost all remote host - more exactly in all remote hosts we hold uri to via some remote music_file_resource.<br>
<br>* Sorry for my english. I mean that because we didn't copy nco:contact fist name and second name, then to search for all music files that has "Ennio Morricone" as conductor we must:<br>a) determinte all remote resources that represents a music file<br>
b) execute query in every such remote host.<br><br>2) May be I understand your idea wrong, but it seemes useless for me - even the resource type is a relation.<br><br>3) Then we should execute query in every available remote host?<br>
<br><div class="gmail_quote">On Tue, Jun 29, 2010 at 5:31 PM, Daniele E. Domenichelli <span dir="ltr"><<a href="mailto:daniele.domenichelli@gmail.com">daniele.domenichelli@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div class="im">On 06/29/2010 12:57 PM, Artem Serebriyskiy wrote:<br>
> Can you please describe your idea in more detail?<br>
> What information is stored localy ?<br>
> And how to perform queries ? For example:<br>
> "Select all resources that have a label <string literal> "<br>
> and<br>
> " Select all [music]files that has a <NCO:Contact | where this nco:contact<br>
> is stored localy> as author".<br>
<br>
<br>
</div>Well, I have 3 different scenarios in my mind:<br>
<br>
<br>
1: during synchronization both resources and relations are copied:<br>
<br>
* resources on remote nepomuk server can be stored locally, but, in<br>
order to avoid conflicts between uri, the name can be replaced, for<br>
example:<br>
from: nepomuk:/<resource><br>
to: telepathy:/contact/<name>/nepomuk/<resource><br>
(or nepomuk:/telepathy/contact/<name>/<resource>)<br>
<br>
* relations can be copied modifying the name of the subject and of the<br>
object using the new name, for example<br>
from: nepomuk:/<resource1><br>
<relation><br>
nepomuk:/<resource2><br>
to: telepathy:/contact/<name>/nepomuk/<resource1><br>
<relation><br>
telepathy:/contact/<name>/nepomuk/<resource2><br>
<br>
In this way:<br>
* queries can be done locally even if the contact is offline<br>
* the uri for a resource will always be unequivocal (but it might<br>
require some relation to represent, for example that a resource<br>
representing a file on my pc corresponds to a resource that represents<br>
the same file on my contact's pc<br>
* When the contact is online you could use dbustubes to execute (and to<br>
listen for changes to) a specific query<br>
<br>
<br>
2: Same as 1, but only resources are copied<br>
<br>
In this way:<br>
* queries executed when the contact is online can return results using<br>
both local and remote nepomuk server (using dbustubes to execute queries<br>
on the remote server), but queries executed when the contact is offline<br>
can return results using local server only.<br>
* The local database will contain less informations, so it will probably<br>
be smaller and faster, but the times for remote queries will be probably<br>
longer due to network latency<br>
<br>
<br>
3: No synchronization at all<br>
<br>
In this way queries on remote server can be executed only if the contact<br>
is online.<br>
<br>
<br>
<br>
In all cases queries will just be a normal query that returns some<br>
resources of type "nepomuk:/" and some resources of type<br>
"telepathy:/contact/<name>/nepomuk/", but they might need to be executed<br>
both on local and on remote servers using dbustubes (and resource from<br>
remote servers must be modified to represent the name of the contact<br>
that created it)<br>
<div><div></div><div class="h5"><br>
<br>
<br>
Cheers,<br>
Daniele<br>
_______________________________________________<br>
Nepomuk mailing list<br>
<a href="mailto:Nepomuk@kde.org">Nepomuk@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/nepomuk" target="_blank">https://mail.kde.org/mailman/listinfo/nepomuk</a><br>
</div></div></blockquote></div><br><br clear="all"><br>-- <br>Sincerely yours,<br>Artem<br>