This some good analysis. I had no idea of the bigger vision of the XMPP protocol. In the near term I've been working through how we could use Wave within some

This some good analysis. I had no idea of the bigger vision of the XMPP protocol. In the near term I've been working through how we could use Wave within some of our (relatively) simple content-creation processes at work, particularly around those items that require review by a number of stakeholders before being made public. The key thing for me around Google's implementation is how one Wave, full of modifications and history, can spawn a new Wave in the form of a published version. We continually struggle with content management, and the balance between easy-to-use and "actually-managed." Version history, content re-use, blah. If Wave can deliver that alone, it'll be worth our effort to use it. If it can deliver all of what Jason talks about this article, it'll be one of the most leveraged chunks of technology in the whole business . . . and insulate us from the whims of Big Software Companies. This is exciting.