Indeed, OpenSocial is definitely not dead. Although the OpenSocial specification began as an alternative or competitor to the Facebook platform, which will be used in consumer-oriented social networks, the Shindig specification and related open source implementation has evolved into a more general API structure and general data model that addresses use cases from consumers to corporate portals and teamwork solutions. Although the Facebook platform dominates the consumer network and may be a natural choice to support external identity or content distribution, OpenSocial is used in ever-growing products and integrates into various cloud applications.
Ongoing work on version 2.0, and the active community is discussing several new features that help create a more open social network. You can see what is being developed here (http://wiki.opensocial.org/index.php?title=Spec_Changes) or join the community to monitor progress or contribute to the specification here (http://groups.google.com/ group / OpenSocial-and-gadget specification).
For your use case, OpenSocial can help you by putting a JS-based container on the client side. Thanks to recent support for Open Ajax and the JS container, OpenSocial (and Shindig) can easily serve as a dashboard or client-side. We could successfully develop on top of Shindig a self-service portal that can integrate third-party gadgets or our own developed ones. The Rest API also helps with server-side application development.
Therefore, I highly recommend that you take a deeper look at OpenSocial for your specific needs.
Kaan bingol
source share