Google IO: Open Social

I many 10-5 developers not working directly with ajaxified web 2.0 applications I was not able to go to the Google I/O conference. I don’t feel so bad not going since Google has just released video recordings of over 70+ technical presentations from Google I/0. Most of the technical presentations are pushing Google’s APIs such as Android, Google App Engine, GWT, and Open Social.

As an aid for myself, and maybe other Open Social developers, I have organized the pertinent Open Social presentations as follows…

Meet the OpenSocial Containers
Representatives from current OpenSocial containers give an overview of their implementations, policies, and what’s unique about their container. They also share some of the fruits of their labors including high level stats. Team members from upcoming containers review their planned launches, policies, and timelines.



Apache Shindig: Make your Social Site an OpenSocial Container
Shindig is a new project in the Apache Software Foundation incubator and is an open source implementation of the OpenSocial specification and gadgets specification in multiple programming languages. The goal of Shindig is to make it easy for social sites to extend their functionality using the OpenSocial API, which makes it easier for developers to write to write those extensions.

Building on the Promise of OpenSocial
The goal of OpenSocial is to provide a framework for developers to build their applications once and run them in multiple social networks. To do this effectively, you need to architect your system to properly segment data and accommodate differences in networks, all while still maintaining a common code base. How do you scale this architecture out to multiple applications? Jeremiah Robison, CTO of Slide, will outline best practices for delivering multiple applications on multiple OpenSocial containers.

OpenSocial – Scaling and Analytics, Nuts & Bolts
iLike uses Ruby on Rails and a core “user”, “fan” and “music” metadata infrastructure to drive iLike services on it’s own site and on Facebook, OpenSocial, the iLike Sidebar for iTunes and Windows Media Player, and other UI projections across the web. Nat will give an overview of iLike‚Äôs infrastructure and the places they have invested to make the syndication and projection that are central to Web 2.5/3.0 world quick and easy, with a focus on social gadgets. He’ll also discuss the role of analytics and A/B testing on user acquisition and customer satisfaction.

OpenSocial Across Containers
OpenSocial provides a common set of APIs that developers can learn in order to create applications that run on multiple social sites. However, since social sites vary widely in functionality, OpenSocial provides ways to extend the core APIs so containers can implement site-specific functionality.

OpenSocial, OpenID, and OAuth: Oh, My!
A number of emerging technologies will soon collectively enable an open social web in which users control their information and it can flow between multiple sites and services. OpenID, OAuth, microformats, OpenSocial, the Social Graph API, friends-list portability, and more will be discussed, as well as a coherent vision for how the pieces fit together and how developers can start taking advantage of them now.

OpenSocial: A Standard for the Social Web
OpenSocial is an open specification defining a common API that works on many different social websites, including MySpace, Plaxo, Hi5, Ning, orkut, Salesforce.com and LinkedIn, among others. This allows developers to learn one API, then write a social application for any of those sites: Learn once, write anywhere.

URLs are People Too – Using the Social Graph API to Build a Social Web
Using email addresses to identify people has a problem – email addresses can be used to send, not receive. With the rise of blogs and social networks, millions of people are using URLs to refer to themselves and others. The Social Graph API indexes these sites and their connections, enabling this web-wide distributed social network to be used to make your sites better. Learn how XFN and FOAF express connections, how we index them, and how OpenID combines with The Social Graph API to help connect people on the web to your applications, and save your users from re-entering their friends over and over again.

Technorati Tags: , , , ,

Related posts:

  1. Tom Coates – Social Change On The Web
  2. Google IO: GWT
  3. Google IO: Android
  4. Google IO: Google App Engine
  5. Google IO 2009: Mobile
  6. Google IO 2009: Tech Talks


Leave a Reply