Another idea has come to me that hands power back to the user: Identify people in a similar way to XMPP's JIDs: [EMAIL PROTECTED] is the same person across all platforms but [EMAIL PROTECTED]/23983274 is their instance on just one chat client.
For Open Social, we do similar: [EMAIL PROTECTED]/23983274 is their local instance ID (and so each container can use whatever ID system they want after the slash) and [EMAIL PROTECTED] is their global ID. The [EMAIL PROTECTED] can be a container host, or maybe something else like opensocialusers.com that allows you to register a global identity and grant different containers the rights to different pieces of that. The XMPP idea would allow you to register your 'primary' identity at orkut and be [EMAIL PROTECTED] when registering your single-ID to other containers. That account then becomes the reference point for all the others. If you change your email address, then you update your orkut account and every service gets the new email address. There'd be a backend protocol for containers to request and be granted access to information .. and of course, it's not an email address so you can't be spammed at that address. Only containers you've registered to can contact you using your registered email address. So this give us: * Single ID across all services (even if each requires it's own login stuff, it's the data sharing that's singlular) * Access control over which container gets what parts of that ID * Distinct IDs at each service * Universally unique identification as well as Service unique identification Cheers! Rick Measham --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Developers" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/opensocial-api?hl=en -~----------~----~----~----~------~----~------~--~---
