I just created a JIRA sub-task for OpenSocial Person related SPI implementation.
The Person object is specified in OpenSocial spec 2.0
http://opensocial-resources.googlecode.com/svn/spec/2.0/Social-Data.xml#Person.
In RAVE, we have already had User class.  However, our existing User
class serves different purposes than OpenSocial Person object.
I am considering implementing Person related SPIs, at least GetPerson
SPI, if nobody else is implementing it.  In the first step, I will use
our existing User class and expose basic user information (e.g.
username) to Shindig.  Then I will extend User class (or write a
completely new class) to add more fields required by OpenSocial Person
data structure/model.
Any comments on this? Is the proposed implementation strategy appropriate?

Thanks,
Gerald

Reply via email to