 | This articlecontainspromotional content. Please helpimprove it by removingpromotional language and inappropriateexternal links, and by adding encyclopedic text written from aneutral point of view.See ouradvice if the article is about you and read ourscam warning in case someone asks for money to edit this article.(October 2019) (Learn how and when to remove this message) |
| OpenSocial | |
|---|---|
 | |
| Initial release | November 1, 2007; 18 years ago (2007-11-01) |
| Stable release | 2.5.1 / August 30, 2013 (2013-08-30) |
| Written in | Java,PHP,C#,JavaScript,HTML |
| Type | Web application framework |
| License | Apache License 2.0 |
| Website | opensocial |
OpenSocial is a public specification that outlines a set of commonapplication programming interfaces (APIs) forweb applications. Initially designed forsocial network applications, it was developed collaboratively byGoogle,MySpace and other social networks. It has since evolved into aruntime environment that allows third-party components, regardless of their trust level, to operate within an existing web application.
The OpenSocial Foundation has integrated or supported variousOpen Web technologies, includingOAuth andOAuth 2.0,Activity Streams, andPortable Contacts. Since its inception on November 1, 2007,[1] applications that implement the OpenSocial APIs caninteroperate with any social network system that supports them.
OpenSocial initially adopted a universal approach to development. As the platform matured and the user base expanded, it was modularized, allowing developers to include only necessary components of the platform.[2]Orkut, a Google client, was the first to support OpenSocial.[3]
On December 16, 2014, theWorld Wide Web Consortium (W3C) announced that the OpenSocial Foundation would transition its standards work to the W3C Social Web Activity.[4] This effectively integrated OpenSocial into the W3C's Social Web Working Group and Social Interest Group, thereby dissolving OpenSocial as a separate entity.
In its 0.9 version, OpenSocial incorporated support for atag-based language.[6] known as OSML. This language facilitates tag-based access to data from the OpenSocialAPIs, which previously necessitated an asynchronous client-side request. Additionally, it established a comprehensive tag template system and adopted an expression language that is loosely based on theJavaExpression Language.
From version 2.0 onwards, OpenSocial began supporting theActivity Streams format.[6]
OpenSocial is commonly described as a more opencross-platform alternative to theFacebook Platform, a proprietary service of the popularsocial network serviceFacebook.[7]
OpenSocial was rumored to be part of a larger social networking initiative by Google code-named "Maka-Maka",[8][9] which is defined as meaning an "intimate friend with whom one is in terms of receiving and giving freely" inHawaiian.[10]
Anopen-source project,Shindig, was launched in December 2007 to provide areference implementation of the OpenSocial standards. It has the support of Google, Ning, and other companies developing OpenSocial-related software. The Myspace OpenSocial parser was released as project Negroni in January 2011 and provides aC#—based implementation of OpenSocial.
Apache Rave is a lightweight and open-standards-based extensible platform for using, integrating, and hosting OpenSocial and W3C Widget-related features technologies, and services. It will also provide strong context-aware personalization, collaboration, and content integration capabilities and a high-quality out-of-the-box installation as well as be easy to integrate into other platforms and solutions.[11]
Both Shindig and Apache Rave are no longer in development and have been retired by the Apache Foundation.
Enterprise websites, such asFriendster,hi5,LinkedIn,MySpace,Orkut, andSalesforce.com are major users of OpenSocial.[12]
Friendster has deployed APIs from version 0.7 of the OpenSocial specification, making it easy for existing OpenSocial applications using version 0.7 to be launched on Friendster and reach Friendster over 75 million users. Friendster also plans to support additional OpenSocial APIs in the coming months, including the new 0.8 APIs.[13]
hi5 tapsWidgetbox support for OpenSocial to get access to the choice of web widgets Widgetbox provides.[14]
Myspace Developer Platform (MDP) is based on the OpenSocial API. It supports social networks to develop social and interacting widgets. It can be seen as an answer to Facebook's developer platform.[15]
Initial OpenSocial support experienced vulnerabilities in security, with a self-described amateur developer demonstratingexploits of theRockYou gadget onPlaxo, andNing social networks using theiLike gadget.[16] As reported byTechCrunch on November 5, 2007, OpenSocial was quickly cracked. The total time to crack the OpenSocial-based iLike on Ning was 20 minutes, with the attacker being able to add and remove songs on a user's playlist and access the user's friend information.[17]
Häsel and Iacono showed that “OpenSocial specifications were far from being comprehensive in respect to security”.[18] They discussed different security implications in the context of OpenSocial. They introduced possible vulnerabilities in Message Integrity and Authentication, Message Confidentiality, and Identity Management and Access Control.
Despite the initial fanfare & news coverage, OpenSocial encountered many issues initially; it only ran on the Google-ownedOrkut, and only with a limited number of devices, with multiple errors reported on other devices. Other networks were still looking into implementing the framework.
On December 6,TechCrunch followed up with a report by MediaPops founder Russ Whitman, who said, "While [they] were initially very excited, [they] have learned the hard way just how limited the release truly is." Russ added that "core functionality components" are missing and that "write once, distribute broadly" was not accurate.[19]
Legend: Discontinued Current
| Version | Release date | Release notes |
|---|---|---|
| 2.5.1[20] | August 30, 2013 (2013-08-30) | View Release Notes |
| 2.5.0[21] | August 28, 2012 (2012-08-28) | View Release Notes |
| 2.0.1[22] | November 23, 2011 (2011-11-23) | View Release Notes |
| 2.0.0[23] | August 18, 2011 (2011-08-18) | View Release Notes |
| 1.1.0[24] | November 18, 2010 (2010-11-18) | View Release Notes |
| 1.0.0[2] | March 9, 2010 (2010-03-09) | View Release Notes |
| 0.9.0[25] | April 15, 2009 (2009-04-15) | View Release Notes |
| 0.8.1[26] | September 25, 2008 (2008-09-25) | View Release Notes |
| 0.8.0[27] | May 27, 2008 (2008-05-27) | View Release Notes |
| 0.7.0[28] | January 25, 2008 (2008-01-25) | View Release Notes |
| 0.6.0[29] | December 21, 2007 (2007-12-21) | View Release Notes |
| 0.5.0[30] | November 9, 2007 (2007-11-09) | View Release Notes |
Changes to theREST API were made to address several issues that required changes in the OpenSocial specifications so theOpen Mobile Alliance could use it.[20]
Common Containers were added that provided "a set of common services that Container developers can leverage for features like in-browser Gadget lifecycle event callbacks, Embedded Experiences, selection handlers, and action handlers."[21] A new Metadata API gives OpenSocial applications the ability to adapt to the capabilities of different OpenSocial containers. TheWAP authentication extension was deprecated.
OAuth 2.0 support was finalized in this version of OpenSocial.[22]
OpenSocial introduced support forActivity Streams. JSON had emerged as the preferred data format and support forATOM was deprecated. The Gadget format was simplified to give the ability to define a template library within a Gadget specification.[23] While not finalized, the groundwork for OAuth 2.0 support was put in place.
In response to enterprise environment needs, OpenSocial added support for advanced mashup scenarios. It enabled gadgets to "securely message each other in a loosely coupled manner."[24] This new feature was called Inter-Gadget Communication.
OpenSocial acknowledged that the "one-size-fits-all" approach it was taking was not going to work for the diverse types of websites that had adopted the platform. To address this issue, OpenSocial is modularized into four compliance modules: Core API Server, Core Gadget Server, Social API Server, and Social Gadget Server.[2] This allowed a developer to pick and choose the modules they wanted to use while using other services that aren't part of OpenSocial. Extensions were introduced to allow developers to extend OpenSocial containers.
In response to feedback and observation of how developers were using the API, this version focused on making "application development, testing, and deployment easier and faster, while reducing the learning curve for new app developers."[25] The OpenSocial Javascript API was streamlined to make it lightweight while retaining the power of the old Javascript API. Proxied content was introduced to eliminate the need for developers to work around previousAJAX limitations. Proxied content allows content to be fetched from a URL and displayed in a <Content> tag. In response to a common use of sending data to a remote server immediately after a request, OpenSocial 0.9.0 introduced data pipelining. Data pipelining allows the developer to specify the social data the application will need and make the data immediately available. OpenSocial Templates were introduced to create data-driven UI with a separation of markup and programmatic logic. OpenSocial Markup Language (OSML Markup) is a new set of standardized tags to accomplish common tasks or safely perform normally unsafe operations within templates. OSML is extensible. Developers can create a library of their custom tags.
This minor release placed a major focus on server-to-server protocols as "the Person schema has been aligned with the Portable Contacts effort, and an optional RPC proposal has been added."[26]JSON-RPC protocol was added to increase server-to-server functionality. The RESTful protocol that was introduced in v0.8.0 underwent a large revision with several fields being added, modified, and deleted.
OpenSocial changed specifications for containers to implement aRESTful API. Many of the OpenSocial Javascript API changes made this version incompatible with previous versions. Existing gadgets continued to use v0.7.0. After updating the gadget, it would use v0.8.0. Security improved with the introduction of OAuth authorization andHTML sanitation, and container lifecycle events.[27] Persistence data was stored inJSON.
Released as the "first iteration that can fully support rich, social applications."[28] It added several standard fields for profile information, the ability to send a message to install an application, an Activity template to control activity notifications about what users have been doing, and a simplified persistence API to use feeds instead of global and instance-scoped application data. Another major announcement came fromApache Shindig. Apache Shindig-made gadgets are open-sourced. In coordination with this announcement, OpenSocial 0.7.0 introduced Gadget Specifications for developers to be able to define their gadgets using the Gadget API.
Security was a large focus in version 0.6.0. Permission controls were tightened to prevent a gadget from returning information if it is not authorized to do so. New classes were added, such as the Environment class to allow a gadget to respond differently according to its environment and the Surface class to support navigation from one surface to another. The Activities class was simplified based on developer needs and the Stream class was deprecated.[29]
Google announced the launch of OpenSocial with a pre-release of version 0.5.0. While unstable, this API introduced "various XML DTDs,JavaScript interfaces and other data structures"[30] to the OpenSocial platform.
