On Mon, Sep 22, 2008 at 9:35 PM, Leo Sauermann <[EMAIL PROTECTED]> wrote: > The desktop uris are addressed here: > http://aperture.wiki.sourceforge.net/SemdeskUris > > The semdesk-uris here: > http://dev.nepomuk.semanticdesktop.org/repos/trunk/doc/2008_09_semdeskurischeme/index.html > > The second approach shows how we wanted to have a global identification > scheme, retrievable, > secure, and ready to cope with multiple devices and users. > Its based on a trick: we use XMPP underneath. > This is probably the best way to do it, but its not clearly defined yet,
I think it would be better if we can use both XMPP and the aperture (Desktop uris) for generating URIs. As XMPP requires an explicit server, it makes more sense in an environment where user ids are more controlled (like in corporates or schools), but still for desktops, I think we need something like aperture (with user, host and maybe application ids in URI). And we need to identify how to handle the scenario where there are clashes in the URI parts when things are transfered to another machine or user... On Tue, Sep 23, 2008 at 12:40 PM, Leo Sauermann <[EMAIL PROTECTED]> wrote: > for files, we should stick to the iana-registered file:// uri scheme > for the information elements inside files we may use hash-based identifiers > or embedded uuids in files (such as email message-ids) > for elements stored in desktop applications already, and accessible via > dbus, and never shared or sent with other computers or people, we may come > up with something like kde:// or desktop:// makes perfect sense ;) > for things defined inside the user's personal information model (= tags, > people, topics) which can be shared across computers and people, the > "nepomuk URI scheme" is needed, exactly. > ok, for nepomuk-uris (or "thing"-URIs): > * a once-auto-generated 128 bit key (either UUID with MAC, or GPG) will not > help to identify the user, machine, etc. or dereference the URI for > retrieval in the future what would be the possible usecase where dereferencing the URI might make sense ? > > Therefore I proposed the "semdesk" uri scheme, as described here: > http://dev.nepomuk.semanticdesktop.org/repos/trunk/doc/2008_09_semdeskurischeme/index.html > which: > * is globally unique because of the underlying [EMAIL PROTECTED] scheme taken > from > XMPP/Jabber (thus covers the UUID/MAC approaches) > * allows using multiple devices for one user (also technically for > dereferenciation, as XMPP allows multiple agents connect using the same > identifier but different "profiles") > * but is human readable ([EMAIL PROTECTED], thats easy to read and to debug if > something goes wrong) > Perfectly valid. But, this alone might not work in scenarios where the control is not handled by a server (like in jabber case). We may also have to think of scenarios where adhoc groups of people transfer files from one pc to another (like why can't I transfer my photo albums and related metadata to my sister's pc. here there may not be an internet connection (and hence a jabber server) available at all) Cheers, Hari _______________________________________________ nepomuk-kde mailing list [email protected] http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde
