Dr. Dobb's Journal - March 2008 - (Page 18) Strategic Vision SOCIAL NETWORKS FOR SOFTWARE DEVELOPERS So what would the firm do with this information? Would it actually change the formal structures to reflect the informal ones? Yes, Norton says: They do re-examine the formal structure and alter it to better support the individuals involved as well as the company/organization as a whole. For instance, when “bottlenecks” (individuals who are relied on heavily by other members of the organization—and disproportionately so) are revealed, organizations are able to focus knowledge sharing and crosstraining initiatives to relieve the burden on those individuals and reduce the institutional risk of having the bulk of the knowledge resting in the hands of the few. Then there’s Google’s OpenSocial, which Ryan Garver discusses in the accompanying sidebar “Google’s OpenSocial API.” Even Cisco is getting into the social networking tools business. And Microsoft is working with researchers at three universities to develop software that can identify experts in online social networks based on the structure of their interactions. Some of the results of the research suggest the kinds of things that Community Analytics teases out of its data, but perhaps less specific: People who offer the most useful information tend to be relatively taciturn, posting to many threads but only a few posts, responding to people who ask specific questions, rarely interacting with frequent posters. Tools like these, as well as the very existence of Community Analytics, a company entirely focused on the analysis of social networks, suggests that we are in the early days of exploring and exploiting the hidden power of social networks. The next stage could be pretty interesting. DDJ Google’s OpenSocial API By Ryan Garver GOOGLE’S OPENSOCIAL (code.google.com/apis/opensocial) was released in November of 2007 and has caused a stir in the social network widget space. Similar to the more mature Facebook API, OpenSocial lets third-party developers embed applications into the profile pages of their users across multiple social networks. Websites such as Friendster, MySpace, LinkedIn, Plaxo, Six Apart, and Wink.com are all claiming support for OpenSocial. OpenSocial is comprised of two core APIs: • The JavaScript API is designed to run within an OpenSocial container and be used by an OpenSocial application. • The REST API supports more general consumption. These APIs revolve around the basic concepts of People (including their relationships with other People), Activities, and Persistence. An OpenSocial application is a Google Gadget with an added . The tag contains a CData section with HTML fragments and JavaScript, which is written inside a within the container HTML. An OpenSocial container is any environment in which the JavaScript API is implemented and an OpenSocial application can be loaded and run. When embedded in a profile page or something similar, the container exists as an IFRAME, which shelters the host network’s private information from the executed application. The container loads the application’s preferences and content into the embedded IFRAME as raw HTML and JavaScript. In addition to the OpenSocial JavaScript API, the container also must implement most of the functionality supplied by Google Gadgets, also known as the “_IG functions.” OpenSocial caters to the mashup culture that has been skyrocketing since the early days of MySpace, and more recently with the Facebook application boom. Beyond the benefits to existing networks in promoting a richer user experience, OpenSocial opens the doors for smaller niche social networks by making user profile information easy to share. By lowering the gates, big networks are letting users move their profiles across multiple sites, thus enabling smaller networks to thrive. Ryan is CTO of ELC Technologies. He can be contacted at rgarver@elctech.com. The Year of Socnet Tools? There is one obvious area in which social networking offers something to software developers: the opportunity to develop software for social networking. Whether or not you ever make use of social networking tools or analytics yourself, you can certainly develop software for this booming area. Note that I didn’t say “booming market.” Is social networks a hot area? Undoubtedly. Does it present some interesting challenges in software development? It does. Is there money to be made? Sure, but first you have to figure out the model. Are you going to get rich doing mashups? Creating a social networking site, and competing with all the other socnet sites for attention? Maybe, like Community Analytics, you can focus on tools for mining information from social networks. Whatever you do, you’ll have company. CNet’s claim that social networking had got its geek on was a recognition of the tools that have arrived to make it easier to treat social networks as a platform for new tools. And the easier it is, the more competition you’ll have. As we reported in December, IBM has announced IBM Atlas for Lotus Connections, “a corporate social networking visualization and analysis tool designed to help organizations maximize their investment in social software by answering questions such as who the key experts are on a given topic, how they are connected, and whom a user’s contacts know that they do not.” 18 Dr. Dobb’s Journal l www.ddj.com l March 2008 http://code.google.com/apis/opensocial http://Wink.com http://www.ddj.com
Table of Contents Feed for the Digital Edition of Dr. Dobb's Journal - March 2008 Dr. Dobb's Journal - March 2008 Contents Hmmmm Alia Vox Developer Diaries Developer’s Notebook Social Networks and Software Development Conversations Detecting Bugs in Safety-Critical Code Change Code Without Fear Continuous Integration and Performance Testing Wt: A Web Toolkit Automating Release Notifications The Agile Edge Effective Concurrency Swaine’s Flames Dr. Dobb's Journal - March 2008 Dr. Dobb's Journal - March 2008 - (Page Belly1) Dr. Dobb's Journal - March 2008 - (Page Belly2) Dr. Dobb's Journal - March 2008 - Dr. Dobb's Journal - March 2008 (Page Cover1) Dr. Dobb's Journal - March 2008 - Dr. Dobb's Journal - March 2008 (Page Cover2) Dr. Dobb's Journal - March 2008 - Dr. Dobb's Journal - March 2008 (Page 1) Dr. Dobb's Journal - March 2008 - Dr. Dobb's Journal - March 2008 (Page 2) Dr. Dobb's Journal - March 2008 - Dr. Dobb's Journal - March 2008 (Page 3) Dr. Dobb's Journal - March 2008 - Contents (Page 4) Dr. Dobb's Journal - March 2008 - Contents (Page 5) Dr. Dobb's Journal - March 2008 - Hmmmm (Page 6) Dr. Dobb's Journal - March 2008 - Hmmmm (Page 7) Dr. Dobb's Journal - March 2008 - Hmmmm (Page 8) Dr. Dobb's Journal - March 2008 - Hmmmm (Page 9) Dr. Dobb's Journal - March 2008 - Alia Vox (Page 10) Dr. Dobb's Journal - March 2008 - Alia Vox (Page 11) Dr. Dobb's Journal - March 2008 - Developer Diaries (Page 12) Dr. Dobb's Journal - March 2008 - Developer Diaries (Page 13) Dr. Dobb's Journal - March 2008 - Developer’s Notebook (Page 14) Dr. Dobb's Journal - March 2008 - Developer’s Notebook (Page 15) Dr. Dobb's Journal - March 2008 - Social Networks and Software Development (Page 16) Dr. Dobb's Journal - March 2008 - Social Networks and Software Development (Page 17) Dr. Dobb's Journal - March 2008 - Social Networks and Software Development (Page 18) Dr. Dobb's Journal - March 2008 - Social Networks and Software Development (Page 19) Dr. Dobb's Journal - March 2008 - Conversations (Page 20) Dr. Dobb's Journal - March 2008 - Conversations (Page 21) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 22) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 23) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 24) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 25) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 26) Dr. Dobb's Journal - March 2008 - Detecting Bugs in Safety-Critical Code (Page 27) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 28) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 29) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 30) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 31) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 32) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 33) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 34) Dr. Dobb's Journal - March 2008 - Change Code Without Fear (Page 35) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 36) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 37) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 38) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 39) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 40) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 41) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 42) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 43) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 44) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 45) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 46) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 47) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 48) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 49) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 50) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 51) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 52) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 53) Dr. Dobb's Journal - March 2008 - Continuous Integration and Performance Testing (Page 54) Dr. Dobb's Journal - March 2008 - Wt: A Web Toolkit (Page 55) Dr. Dobb's Journal - March 2008 - Wt: A Web Toolkit (Page 56) Dr. Dobb's Journal - March 2008 - Wt: A Web Toolkit (Page 57) Dr. Dobb's Journal - March 2008 - Wt: A Web Toolkit (Page 58) Dr. Dobb's Journal - March 2008 - Wt: A Web Toolkit (Page 59) Dr. Dobb's Journal - March 2008 - Automating Release Notifications (Page 60) Dr. Dobb's Journal - March 2008 - Automating Release Notifications (Page 61) Dr. Dobb's Journal - March 2008 - Automating Release Notifications (Page 62) Dr. Dobb's Journal - March 2008 - Automating Release Notifications (Page 63) Dr. Dobb's Journal - March 2008 - Automating Release Notifications (Page 64) Dr. Dobb's Journal - March 2008 - The Agile Edge (Page 65) Dr. Dobb's Journal - March 2008 - The Agile Edge (Page 66) Dr. Dobb's Journal - March 2008 - The Agile Edge (Page 67) Dr. Dobb's Journal - March 2008 - Effective Concurrency (Page 68) Dr. Dobb's Journal - March 2008 - Effective Concurrency (Page 69) Dr. Dobb's Journal - March 2008 - Effective Concurrency (Page 70) Dr. Dobb's Journal - March 2008 - Effective Concurrency (Page 71) Dr. Dobb's Journal - March 2008 - Swaine’s Flames (Page 72) Dr. Dobb's Journal - March 2008 - Swaine’s Flames (Page Cover3) Dr. Dobb's Journal - March 2008 - Swaine’s Flames (Page Cover4)
For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.