On Nov 23, 2007 11:21 AM, Julian Bond <juli...@voidstar.com> wrote:
The specs for the People Data API seem to be very Orkut-centric. One
aspect in particular needs work and that's ID.
Indeed.
I need a way of specifying multiple IDs within the entry record.
Something like
- Local system ID (in this OpenSocial Container)
- Email-1, Email-2, Email-n, (optionally obfuscated with SHA1)
- OpenID-1, OpenID-2, OpenID-n,
- Unique ID on Service S as multiple pairs. eg Facebook-501829088,
Twitter-jbond, Skype-julian.bond, etc
Of the things you list, local ID is the only thing I would consider to
identify the user. It would be useful to make it global rather than
local, since there seems to be no way to identify the container from
within the gadget and therefore to distinguish between multiple ID
spaces. I would like the spec to normatively specify what is
essentially a user ID URI scheme or its functional equivalent.
The other things you mention are just identity/profile attributes. To
me, they are users' self-declared assertions, which the container does
not represent to be valid or unique or to refer to an identity
actually owned by the user. No app should rely on these to map user
identities across systems.
How do we resolve this and move Google to a more universally applicable
scheme?
Keep asking? :)
-Daniel
1 message in com.googlegroups.opensocial-containerRe: [OpenSocial] Towards a universal ...