|
|
|
@jurijlotman asked me to have a look at #googlewave (should have a look at microsyntax as well). So I had a look at the video. For the moment that is the only thing we have access to. It looks like a very interesting approach to communication and interaction. We are really talking realtime Internet here. Slowly the real time Internet is for me becoming the Web3.0 subject. But have a look at the video for yourself.
The question is however the relation between MicroContent (the drops) and Google Wave. And I am inclined to concluded that there is no relation at all. The most important aspect of MicroContent, the permalink, seems to be missing in Google Wave. Google Waves is all about creating, sharing, editing and extending waves. These waves seems to be very large documents, which can be distributed to multiple readers and authors. It was not clear from me whether I could use parts of a wave in another one. This would imply referencibility and an important MicroContent aspect.
The other aspect is structure. Out of the box there does not seem to be any, although one can add it later on (example with forms in the video). However a piece of text can be split and be edited by multiple persons, so each piece of text could be seen as a piece of MicroContent. One can also add links, images and videos to the text to create rich text. The editing by multiple persons reminds of a Wiki, which did not have much to do with MicroContent either.
The examples of Twitter integration show that #googlewave can support MicroContent and add new levels to create mashups and threading. In order to be a good MicroContent environment also importing and exporting should be supported, which seems to be already partially done through the api’s. So for a final assessment we have to wait. It looks very interesting and can give a new idea to documents and wiki’s.
Excellent analysis, Arnaud. I think you’re right on to identify two microcontent connections of Wave: component bits, and microcontent generated by or extracted from Waves.