But no.  The userId has to be globally unique, and immutable.  So no,
their ids should have nothing to do with a url on the site.  Change
your url scheme and voila all apps stop working because they can't
identify users..

as to the sha(email)
Yeah.  That works.  But I just don't think it's the purpose nor the
goal of OpenSocial to start unifying the social networks.  It might
sound like a nice idea, but really having to dictate interdependencies
between social networks like that.. just heading for trouble.. but
maybe there are only a few surmountable issues.. that is besides user
privacy, user identities and personas, allowing for user's choice, and
allowing for social network choice, and then not to mention that
emails are also not immutable nor reverse-unique: having multiple
emails on one account ( which we all do ), changing emails during the
life of the account ( which probably most of us have done ).

Anyway, that is why you can't have a uuid for a user.. you can't just
tell the user, here this is you uuid from now on, on all networks that
you will ever sign up with.  Just doesn't make sense.  You can give
the user the choice to essentially link up or associate accounts, but
maybe they don't want that to happen, for whatever reason..  opt-in,
intead of forced on you..

g'night



On Nov 9, 2007 12:08 AM, Julian Bond <[EMAIL PROTECTED]> wrote:
>
> 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
-~----------~----~----~----~------~----~------~--~---

Reply via email to