Home » Blog »
Google Wave: a hypothetical case study
Here's my prediction: Google's wave federation protocol will be the new way to edit and publish shared unstructured data on the web. Waves will store data for blogs and documents. Waves will replace many documents now stored in custom content management systems.
I recently developed a career helper (C2C Advantage) where students log in and complete assignments related to career planning. If I were starting the project now instead of six months ago, I would use waves.
Content creators would log into the website and create CMS pages as waves. A robot would publish these pages to the web. For the assignments, which include instructions and resources but are basically rich text, I would create an extension that provides instructions and resources fields, and a robot that publishes the pages.
So far, the system hasn't really needed wave features. But student responses are ideal for waves. Students would log in and view the assignments. They would write their responses in a wave that was shared with their career advisor When they were done, an extension would let them alert the advisor that they were done. The advisor could then go in and write comments. The student or the advisor could share the wave with others: faculty, friends, potential employers, etc.
The system gives everyone a common editing interface that is better than TinyMCE. Also, everyone gets an interface where they can see incoming waves.
Posted: October 17, 2009
Category: News
