The specs for the People Data API seem to be very Orkut-centric. One aspect in particular needs work and that's ID.
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 At the moment, the People Data API doesn't seem to allow this sort of extensibility. And it really has to be done as part of the spec so that all OpenSocial Containers can generate the data in the same way and API apps can understand that data. How do we resolve this and move Google to a more universally applicable scheme? -- 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 Get _Sirius_ in 2008 --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
