From the Sys Admin Tips Newsletter by Chris Miller:


This is a new word to many of you so I am going to steal a couple of lines from Wikipedia about this open initiative. Google was a major partner in launching these common APIs back in 2007.

"OpenSocial is public specification that defines a component hosting environment (container) and a set of common application programming interfaces (APIs) for Web-based applications. In more recent times it has become adopted as a general use runtime environment for allowing untrusted and partially trusted components from third parties to run in an existing Web application."

The OpenSocial Wiki is a great place to see how apps are built and get the specifications on how integration will begin. OpenSocial has containers to gather information on people, relationships, groups, application data, media data and more. There was an area that is being moved into what you have heard called Activity Streams. This is key to you as an administrator, when thinking about topology and integration that will occur.

Recent changes include the inclusion of oAuth 2 support. Picture this as an alternate form of authentication besides the Domino Directory. While its current state does not support you moving your Domino public/private key structure, you could use alternate forms of authentication and data inclusion for users against public social networks that support oAuth.

One last beginning part for this issue is the idea of templates. We know how they function in Domino, and OpenSocial has the same schema developed. OpenSocial Templating (OST) lets developers make templates and then change code as needed when deploying a gadget. This is a simplified way to think about how your developers can build and deploy OpenSocial Gadgets (think databases) into your environment.

Look for more in this series as I try and include topics that will help you see the direction IBM is including in future business plans.

Comments [0]

No Comments Found


Discussion for this entry is now closed.

This is the Blog of Martin Leyrer, currently employed as an Senior Lab Services Consultant at HCL Digital Solutions.

The postings on this site are my own and do not represent the positions, strategies or opinions of any former, current or future employer of mine.