The enterprise implications of Google Wave | Enterprise Web 2.0 | ZDNet.com - 1 views
-
Peggy Collins on 01 Oct 09"What Google has done with the Wave protocol is essentially create a new kind of social media format that is distinctively different from blogs, wikis, activity streams, RSS, or most familiar online communication models except possibly IM. Both blogs and wikis were created in the era of page-oriented Web applications and haven't changed much since. In contrast, Google Wave is designed for real-time participation and editing of shared conversations and documents and is more akin to the simultaneous multiuser experience of Google Docs than with traditional blogs and wiki editing. Though Google is sometimes criticized for missing the social aspect of the Web, that is patently not the case with waves, which are fundamentally social in nature. Participants can be added in real-time, new conversations forked off (via private replies), social media sharing is assumed to be the norm, and connection with a user's contextual server-side data is also a core feature including location, search, and more. The result is stored in a persistent document known as a wave, access to which can be embedded anywhere that HTML can be embedded, whether that's a Web page or an enterprise portal. Users can then discover and interact with the wave, joining the conversation, adding more information, etc. Google has also leveraged its investments in Google Gadgets and OpenSocial, two key technologies for spreading online services beyond the original boundaries of the sites they came from. All in all, Google Wave is a smart and well-constructed bundle of collaborative capabilities with many of the modern sensibilities we've come to expect in the Web 2.0 era including an acutely social nature, rapid interaction, and community-based technology."