Some crazy idea( really crazy ):<br>What about using some kind of p2p
network for sharing metadata ? It might be usefull for sharing public
metadata - for example information about music, about books, about
films.<br><br><div class="gmail_quote">On Mon, Jun 28, 2010 at 11:12 PM, Vishesh Handa <span dir="ltr"><<a href="mailto:handa.vish@gmail.com">handa.vish@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;">
Hello Oszkar<br><br><div class="gmail_quote"><div class="im">On Tue, Jun 29, 2010 at 12:14 AM, Oszkar Ambrus <span dir="ltr"><<a href="mailto:aoszkar@gmail.com" target="_blank">aoszkar@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;">
Hi Vishesh,<br>
<div><br>
On 28 June 2010 18:50, Vishesh Handa <<a href="mailto:handa.vish@gmail.com" target="_blank">handa.vish@gmail.com</a>> wrote:<br>
> Metadata sharing implies that we should be able to see other people's<br>
> metadata and have it on are own system. Sebastian suggested that we store<br>
> user information ( who owns which statements ) as graph metadata. That's<br>
> totally feasible, and maybe we could also store the permission settings as<br>
> graph metadata.<br>
<br>
</div>I'm thinking of permissions settings similar to how you share stuff<br>
through Samba.<br>
You can share your stuff with guests (i.e. everyone, without<br>
authentication), with all known users (stored locally) or with a<br>
subset of existing users.<br>
The list of users could be stored locally as RDF and then, similarly<br>
to what Sebastian suggested, statements can be annotated with the<br>
graph meta-data to specify privileges.<br></blockquote></div><div><br>Yes. I had something similar in mind.<br> <br></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<div><br>
> I'm not too sure how we would choose whose metadata to store our on system<br>
> or why we would need to do that.<br>
<br>
</div>As for whose meta-data to store, would you like to go with a<br>
high-level protocol, such as Jabber? So no low-level stuff?<br></blockquote></div><div><br>Forget about Jabber. I think it would be better to go with
Telepathy. Daniele [0] is working on "Telepathy Tubes and File Transfer
in KDE", and it would be a lot better to support multiple protocols via
Telepathy instead just supporting Jabber. Once his project is complete
we should be able to export a Dbus interface to other contacts, so that
greatly simplifies the problem of how to connect/transfer stuff between 2
machines.<br><br>Please look at the attached conversation.<br>
<br></div><div class="im"><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
Because, as I understood, the RDF repository is going to be exposed<br>
through HTTP, so you could connect to anyone's repository and just<br>
insert their address in the graph metadata of the statements you store<br>
locally.<br></blockquote></div><div><br>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.<br>
<br>- Vishesh Handa<br></div></div><br>[0] <a href="http://blogs.fsfe.org/drdanz/" target="_blank">http://blogs.fsfe.org/drdanz/</a><br>
<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>
<br></blockquote></div><br><br clear="all"><br>-- <br>Sincerely yours,<br>Artem<br>