Tuesday, February 5th, 2008>p>The latest version of the OpenSocial spec has been released, 0.7:
The best news is that, based on numerous discussions with both app developers as well as container sites, we believe OpenSocial 0.7 has all the necessary pieces to launch OpenSocial apps to users at scale. In fact, both hi5 and orkut will be using OpenSocial 0.7 for their upcoming user-facing launches.
There are two major pieces to this release:
The OpenSocial APIs have been upgraded:
Standardized profile information fields. This release adds a slew of standard fields that you can access about a
Person. These include location, schools, pets, movies, sports, and more. However, keep in mind that a container may not have all of this information available so your application should always check first by using the
Support for viral growth. Two new methods allow your application to send messages on behalf of a user. You can invite a user’s friends to install your application with the
requestShareAppmethod. You can also send an application-specific message with the
requestSendMessagemethod. Both of these methods require the user sending the message to authorize the request first.
Activity templates. You can now define activity messages with placeholders for pieces of applicaton or user data. This separation of data and presentation allows multiple activities to be combined into activity summariesâ€”consolidated bundles of activities that let users know what their friends are up to without having to wade through a flood of messages. For example, instead of seeing five new updates about friends that installed a new application, you would see one update that says five of your friends added the application. For details on how to use activity templates in your application, see
opensocial.Activityin the OpenSocial API reference.
Simplified persistence API. Support for global and instance-scoped application data has been removed from the API. Global application data can be implemented using feeds (that can be prefetched for performance) and other web standards. Instance-scoped application data can be implemented on top of user-scoped data by including the module ID of the application in the key.
Gadgets Open Sourced
As promised, the full Gadgets engine has been open sourced:
As part of the Apache Shindig project, gadgets have been open sourced. The new Gadgets Specification defines the
_IG_Adjust_IFrame_Heightis now available as
If you are in the bay area, you can visit a hackathon on February 7-8 and February 14-15 at the Googleplex in Mountain View where you can hang with the technical folk and get your apps approved for Orkut.
Posted by Dion Almaer at 5:35 am