OpenSocial 是一个可行的 API 选择吗？
对于一个项目，我们正在研究一种从其他站点导入小工具（好友列表、待办事项列表等）的机制，这正是 OpenSocial 所擅长的。然而，我担心 OpenSocial 是否已经消亡。自 2009 年 4 月以来，OpenSocial 0.9 的许多 API 页面都没有更新过。我看到的最近的几个更新只是垃圾邮件机器人发布廉价德国药品的链接 (例如，请参阅此历史记录页面）。
OpenSocial 还活着吗？或者它是否像许多其他宏伟的想法一样，被遗弃在互联网的废墟中？
For a project we're looking at a mechanism to import gadgets (friends lists, todo lists, etc) from other sites, something that OpenSocial is supposed to be great at. However, I'm concerned about whether or not OpenSocial is dead. Many of the API pages for OpenSocial 0.9 haven't been updated since April 2009. The few recent updates I have seen are just spambots posting links to cheap german pharmaceuticals (for example, see this history page).
Is OpenSocial alive? Or has it, like so many other grandiose ideas, been abandoned to the wastes of the Internet?
如果你对这篇内容有疑问，欢迎到本站社区发帖提问 参与讨论，获取更多帮助，或者扫码二维码加入 Web 技术交流群。
绑定邮箱获取回复消息
由于您还没有绑定你的真实邮箱，如果其他用户或者作者回复了您的评论，将不能在第一时间通知您！
发布评论
评论（1）
事实上，OpenSocial 绝对没有消亡。尽管 OpenSocial 规范已开始作为 Facebook 平台的替代品或竞争对手，用于面向消费者的社交网络，但该规范和随附的开源实现 Shindig 已发展成为更通用的 API 框架和通用数据模型，可解决从消费者到社交网络的用例。企业门户和群件解决方案。虽然 Facebook 平台在消费者网络中占据主导地位，并且可能是外部身份支持或内容分发的自然选择，但 OpenSocial 正在不断增加的产品中使用，并集成到各种云应用程序中。
当前正在进行的规范版本是 2.0，活跃的社区讨论了一些有助于构建更加开放的社交网络的新功能。您可以在此处查看正在开发的内容 (http://wiki.opensocial.org/index.php?title=Spec_Changes)，或者加入社区以监控进度或在此处为规范做出贡献 (http://groups.google.com /group/opensocial-and-gadgets-spec）。
关于您的用例，OpenSocial 可以通过提供基于客户端 JS 的混搭容器来帮助您。借助最近的 Open Ajax 支持和 JS 容器，OpenSocial（和 Shindig）可以轻松用作仪表板或客户端门户。我们可以在 Shindig 之上成功开发一个自助服务门户，可以集成第三方或我们自己开发的小工具。 Rest API 还有助于开发服务器端应用程序。
因此，我强烈建议您深入了解 OpenSocial，以满足您的特定需求。
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.