On Nov 29, 2007 12:59 AM, Julian Bond <[EMAIL PROTECTED]> wrote: > Mostly. But Email is almost always validated, as is OpenID. And they're > universal IDs rather than tied to one Container.
1) so we need to distinguish between validated and unvalidated email address claims; 2) a simple solution would be to use a boolean XML attribute to denote validation status (whether container asserts that the user's claim is valid); 3) don't know if I would trust the container's validation claim -- I don't know when it was validated and how (i.e. whether it could be spoofed). My point is that these attributes make poor candidates as reliable user IDs. They are great for figuring out how to communicate or tune in to the user, where there is motivation for the user to be accurate. -Daniel --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Implementing OpenSocial Containers" 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-container?hl=en -~----------~----~----~----~------~----~------~--~---
