7

对于一个项目,我们正在研究一种从其他站点导入小工具(朋友列表、待办事项列表等)的机制,这是 OpenSocial 应该擅长的。但是,我担心 OpenSocial 是否已死。OpenSocial 0.9 的许多 API 页面自 2009 年 4 月以来就没有更新过。我看到的最近的少数更新只是发布廉价德国药品链接的垃圾邮件机器人(例如,请参阅此历史页面)。

OpenSocial 还活着吗?或者它是否像许多其他宏伟的想法一样被互联网所抛弃?

4

1 回答 1

2

Indeed OpenSocial is definetely not dead. Although the OpenSocial spec has started as an alternative or competitor to Facebook platform to be used in consumer oriented social networks, the spec and accompanying open source implementation Shindig evolved into a more general API framework and a common data model which adresses use cases from consumer to enterprise portals and groupware solutions. While Facebook platform dominates consumer web and may be a natural choice for external identity support or content distribution, OpenSocial is being used inside ever increasing products and integrated to various cloud applications.

Current work in progress spec version is 2.0 and an active community discusses several new features that contribute to building a more open social web. You may see what is being developed here (http://wiki.opensocial.org/index.php?title=Spec_Changes) or join the community to monitor progres or contribute to the spec here (http://groups.google.com/group/opensocial-and-gadgets-spec).

Regarding your use case, OpenSocial may help you by supplying a client side JS based mash up container. With recent Open Ajax support and a JS container, OpenSocial (and Shindig) may easily serve as a dashboard or client side portal. We could sucessfully developed on top of Shindig a self service portal that can integrate gadgets from third parties or of our own developed ones. The Rest API also helps in developing server side applications.

So I strongly recommend to look deeper in OpenSocial for your specific needs.

于 2011-03-05T16:03:56.807 回答