Steve Gillmor talks about spam and collaboration models, and says that pointing at a single copy of data from multiple spaces violates the OHIO principle. In fact, a good OHIO architecture might involve using a tool that – as a side-effect of content creation – posts a single copy of the content to a public store. Then, assuming uniform visibility, people can collaborate with one another in private spaces, referencing the public resource.
In fact, this is largely the picture painted by John Stenbit (from whom I learned the term OHIO, btw), whose vision is to migrate the DoD to a world of more effective information sharing by giving power to the edge, as opposed to leaving it locked up within the stovepipe where the originating entity might potentially keep it from being acted upon by someone else. Publish, notify … discover, collaboratively analyze, decide, act.
Which is why I’m such a big believer in client-side tools that work the way that people want them to work. If you work on your documents naturally in a personal environment tailored to a certain natural workstyle – e.g. Radio, or the “shared canvas” of the Groove transceiver – a ‘bot’ in that space can move or stream it automatically to the Web, SharePoint, to Siebel or SAP, or to your repository of choice. If someone had to “post” the information as a separate step, they won’t.
We have to see how we can apply some of these ideas to our Digital Dashboard project.