Thanks for the clarification Arne. I guess I was confused by the fact that Orkut has a separate OpenSocial user ID in addition to the Orkut user ID.
Alex On Mon, Jul 14, 2008 at 5:14 PM, Arne Roomann-Kurrik (Google) <[EMAIL PROTECTED]> wrote: > > Hi Alex, > > The spec says that IDs must be unique to a container, but this > means that collisions are certainly possible. The spec advises to > prefix IDs with the name of the container and a colon if you need a > GUID. For example, if the user with ID 12345 on hi5 is different from > the user 12345 on orkut, you could store both without collision using > the following format: > > orkut.com:12345 > hi5.com:12345 > > Hope this helps, > ~Arne > > > On Jul 14, 1:07 pm, Alex E <[EMAIL PROTECTED]> wrote: >> The OpenSocial spec says that Person.getId() >> "Gets an ID that can be permanently associated with this person." >> >> Orkut returns an "OpenSocial" user ID that is different from the Orkut >> user ID, and this ID is supposed to be different from any user ID on >> any OpenSocial platform. Hi5, on the other hand returns the Hi5 user >> id (the same on that goes in the profile URL). >> >> If you're building a cross-platform application, it seems you can get >> a collision this way with a user on a different social network. >> >> Is this correct? > > > --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "OpenSocial Application Development" 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 -~----------~----~----~----~------~----~------~--~---
