Google published OpenSocial 1.0 specs

With so many different types of websites adopting OpenSocial it has become clear that a "one size fits all" approach isn't appropriate for the OpenSocial spec. “Modularity was a key goal in OpenSocial 1.0 iteration, allowing implementers to pick and choose elements of OpenSocial. OpenSocial 1.0 also defines extension points so containers can add functionality […]

With so many different types of websites adopting OpenSocial it has become clear that a "one size fits all" approach isn't appropriate for the OpenSocial spec. “Modularity was a key goal in OpenSocial 1.0 iteration, allowing implementers to pick and choose elements of OpenSocial. OpenSocial 1.0 also defines extension points so containers can add functionality not covered in spec, but do so in a standard way, making it easier to fold such extensions back into the spec or share extensions across containers. To accommodate varied use cases of OpenSocial containers, OpenSocial 1.0 has been revised to include four compliance models: Core API Server - For containers that wish to expose data in a standard way though web services; Core Gadget Server - For containers that simply want to be able to render gadgets; Social API Server - For containers that wish to expose social data through standard web services that’re consistent across containers; Social Gadget Server - For containers that want to render gadgets and provide them access to standard social data,” explain Google.