Wave is not just a singular tool, it is also a communication protocol. There is no single way to use it.
If you watched the demo you would see that many of the issues you mentioned in your comment can be addressed simply by choosing to use wave in the manner that is appropriate for the specific communication's context. You are free to approach it as:
'Collaborative draft and then publish'
'off the cuff IM type conversations'
'Push type communication like email'
'Pull type conversation like a blog'
* etc...
Its really hard to explain without seeing the demo. When they publish the video for the day 2 keynote you should definitely watch it:
http://wave.google.com
I would just respond to your summary by saying that it does what existing communication types do already... but better... and throws in things like versioning (history and record/playback), collaboration, and concurrent modification for free.
If you watched the demo you would see that many of the issues you mentioned in your comment can be addressed simply by choosing to use wave in the manner that is appropriate for the specific communication's context. You are free to approach it as:
'Collaborative draft and then publish' 'off the cuff IM type conversations' 'Push type communication like email' 'Pull type conversation like a blog' * etc...
Its really hard to explain without seeing the demo. When they publish the video for the day 2 keynote you should definitely watch it: http://wave.google.com
I would just respond to your summary by saying that it does what existing communication types do already... but better... and throws in things like versioning (history and record/playback), collaboration, and concurrent modification for free.