fernando padilla <[EMAIL PROTECTED]> Thu, 8 Nov 2007 23:42:04 >But the more I think of it, if this is going to be true opensocial, >then I truly believe the ids have to be the "GUID" that you mention >below, and essentially uris, but up to the container, really along the >lines of OpenId. Not the most optimal on our databases.. but it's >kinda a requirement.
The People Data API and the examples seem to show something like <id>http://www.ecademy.com/feeds/people/1<id> [1] as long as the trailing ID number is unique for the domain this ends up being a globally unique GUID. What this doesn't do is to match http://www.ecademy.com/feeds/people/1 with http://www.orkut.com/Profile.aspx?uid=11056323781708313949 who is actually the same person. What the foaf people did was to use sha1(mailto:[EMAIL PROTECTED]) and named it mbox_sha1sum. It's assumed that any one email address (used for identification) and hence it's hash, maps to only one person. And the Hash obfuscates the email address just enough to get over email privacy issues. And further that someone's primary email address will turn up somewhere on their profile on every social network they belong to. [1]That URL works and returns real data. -- Julian Bond E&MSN: julian_bond at voidstar.com M: +44 (0)77 5907 2173 Webmaster: http://www.ecademy.com/ T: +44 (0)192 0412 433 Personal WebLog: http://www.voidstar.com/ skype:julian.bond?chat *** Just Say No To DRM *** --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
