Example (refer to this "how we did it" post)NewsGator Social Sites 2.0 connects Microsoft SharePoint and Newsgator's Enterprise Server to add a collection of capabilities (e.g., tags, bookmarks, communities, social networking). Social Sites relies on Microsoft SharePoint AJAX Toolkit (found on CodePlex). Reliance on the AJAX toolkit commits this solution more deeply to SharePoint. It relies on, and extends, the user profile information in SharePoint (another product-specific dependency). NewsGator introduces a new feed reader (My Feeds) with Social Sites and it is unclear how unique this reader is to SharePoint (so for now, I assume that it is only for SharePoint). The community capability extends the Team Site capability within SharePoint (another dependency if Social Sites were to be duplicated for other vendors). So while Social Sites 2.0 represents a very solid and much-needed social computing extension for SharePoint, I would categorize it as an Enhancement model given the deep level of integration specific to SharePoint.
GatewayA Gateway integration model also extends SharePoint's social computing capabilities. The primary difference between a Gateway and Enhancement approach is that the Gateway's focus is primarily on attaining some level of interoperability with SharePoint. That is, the vendor's Gateway solution offers value in both a stand-alone situation as well as with SharePoint if Microsoft's social computing platform is deployed.
Example (refer to this "how we did it" post)Connectbeam's Spotlight Connect For SharePoint connects Microsoft SharePoint with Connectbeam's tag and social bookmark system. Spotlight For SharePoint relies on Web Parts that leverage Connectbeam's REST-based APIs. While Connectbeam integrates with SharePoint to deliver tag and bookmark capabilities, the integration is careful to maintain a level of technical separation while still providing a cohesive user experience. For instance, a My Profile Web Part shows user profile data from SharePoint along with tag, bookmark and other data from Connectbeam but tabs are used to segment the standard user profile display. Rather than dump the information all into the "About Me" area, the Spotlight data is contained with a tab labeled "Social Content". I can envision how Connectbeam can deliver specific integration with other social computing platforms (e.g., Spotlight For Oracle, Spotlight for SAP, Spotlight for Jive). This approach leads me to categorize this integration model as more of a Gateway solution. The Connectbeam application can stand alone, integrate with SharePoint, and possibly integrate with other platforms in the future.Atlassian, Awareness, Telligent and blueKiwi are also examples of vendors adopting a Gateway integration model.
OverlayThe Overlay integration model represents the deepest level of integration to extend SharePoint's social computing capabilities. In essence, a vendor pursuing this approach begins to use SharePoint itself as its base infrastructure platform. That is, the solution essentially "lives within" SharePoint. This integration model differs significantly from the Enhancement and Gateway model since the vendor becomes almost entirely dependent on SharePoint. There may be some distinct functions kept outside SharePoint (e.g., database) to enable the vendor to deliver functions not possible within SharePoint's current set of services.
Example (refer to this "how we did it" post)There is no vendor that currently has the depth of social computing integration that would quality it as delivering an Overlay model. Tomoye however is heading in that direction:"Since Ecco is a pure 100% ASP.NET 2.0 application with lots of business logic, we are experimenting with porting our application straight into SharePoint as a "_layouts application." This will allow us to keep leveraging our existing code as we transition to using more and more of the capabilities in the SharePoint platform such as Lists, Document and Picture Libraries, User Profiles, and the Business Data Catalog. So far, this approach has been easier than expected. Within only 3 days, we were able to deploy our application as a _layouts application and to run as-is with very little code changes!
Alter-Ego'sFor every EGO there is an equal and opposite "Alter Ego". These are a few key vendors that are battling Microsoft in terms of delivering an enterprise-grade social computing platform that spans multiple capabilities (e.g., blog, wikis, tags/bookmarks, feeds and social networking).IBM: Lotus Connections represents the most well-known alternative to Microsoft. IBM and Microsoft have been battling head-to-head in the collaboration and content markets for many years - it should be no surprise that the competition will be equally intense in the area of social computing.Jive Software: Clearspace represents the first independent vendor to deliver a cohesive mini-suite of social computing capabilities that has enabled it to break away from the pack of smaller vendors who have focused on just a few select social software components.Oracle: Oracle should be considered a credible social computing dark horse. Although the software company has failed in previous attempts to succeed in the collaboration market, it has gained credibility in the enterprise content management space. Given the trend towards contextually integrating social data and features within existing applications, it should be expected that Oracle will make a run at this market.
5 Top Federal Initiatives For 2015As InformationWeek Government readers were busy firming up their fiscal year 2015 budgets, we asked them to rate more than 30 IT initiatives in terms of importance and current leadership focus. No surprise, among more than 30 options, security is No. 1. After that, things get less predictable.