> In a world where cloud computing and mesh services (where data is > shared between multiple devices of the same person) are gaining > ground, i think we have to think of how to solve all the three > scenarios > 1. single desktop > 2. p2p > 3. central server > > I understand that a single URI might not be possibly used in all the > scenarios. But, why not have multiple URIs for the above scenarios for > the same object? > > We can retain the current URI scheme for the single desktop scenario. > Then, we can use an additional GloballySharedURI for resources shared > via a central server. And, maybe a PeerSharedURI for p2p scenarios. > all the above URIs can be mapped to a single resource as needed and > the corresponding URI could be used for the corresp scenario.
technical question: how do we implement this? I mean, not everybody has a jabber id and asking all users to create a jabber id before they can start tagging their stuff seems overkill. So how is this handled? Start out with plain URIs like nepomuk:/foobar or with local ones like nepomuk:/[EMAIL PROTECTED]/foobar? And what to do once we have a jabber id and want to exchange? Update all the URIs? And Leo, please don't say again that we cut this issue since it is important. We are in the real world here, not in an academic prototype. Users will get angry and spam the help and bug forums if we force them to create a jabber account on first login. We need to start from a disconnected solution. Sad but true. Cheers, Sebastian _______________________________________________ nepomuk-kde mailing list [email protected] http://lists.semanticdesktop.org/mailman/listinfo/nepomuk-kde
