The social gadget container specification includes a complete standardization of the feature set that allows a container to host OpenSocial applications that leverage its social data, but does not include the API server specifications of a social implementation.
This portion of the specification provides the functionality of the core gadget container specification, but does not exclude the social features. The features and functions in this specification include:
The core gadget XML file definitions for creating an application, and features for accessing proxied content, content rewriting, templating, and data pipelining
Making and handling OAuth and signed requests
This implementation is best for OpenSocial containers that want to allow developers to build applications within them but do not want to allow those developers to pull their social information onto third-party sites.
Full specification requirements for the core API server implementation are available at http://opensocial-resources.googlecode.com/svn/spec/1.0/Social-Gadget.xml.