Whats the reasons against using a wave itself of some form to store the user information?
It would be somewhat neat if the same controls for who can access a wave effectively become also the controls for which company's or individuals can access your details. On 15 December 2010 22:23, Tad Glines <tad.gli...@gmail.com> wrote: > On Wed, Dec 15, 2010 at 11:19 AM, Zachary "Gamer_Z." Yaro <zmy...@gmail.com> > wrote: > >> I was under the impression OpenSocial was only for gadgets (I know the wave >> gadgets API extends OpenSocial) and it is meant to *connect* to a profile >> system rather than *being* the contacts system. > > > OpenSocial defines a > RESTful<http://www.opensocial.org/Technical-Resources/opensocial-spec-v081/restful-protocol>and > RPC<http://www.opensocial.org/Technical-Resources/opensocial-spec-v081/rpc-protocol>transport > that can be used to fetch and update profile data. > > On Wed, Dec 15, 2010 at 12:59 PM, Sevki Hasirci <se...@shacx.com> wrote: > >> Instead of opensocial how about a xml file that declares this information, >> which would be under the users control at all times. The reason I think this >> would be important is that my company doesn’t allow social networks to be >> used therefore opensocial is out of the question but I can craft a xml file >> from the active directory server within seconds.. > > > The WiaB server would implement > some<http://wiki.opensocial.org/index.php?title=Osapi.appdata_(v0.9)>of > the OpenSocial API's in order to serve up user > profile<http://wiki.opensocial.org/index.php?title=Opensocial.Person_(v0.9)>information. > > At the very least, we can look at the > opensocial.Person<http://wiki.opensocial.org/index.php?title=Opensocial.Person_(v0.9)>object > as a reference for what to include in our own user profile > implementation. > > -Tad >
