Interesting document on some of the technical details behind Stanford's
iRoom, part of the
larger iWork project. The iRoom is a room designed for highly mediated collaboration among real-world users. The description of the iRoom reads, in part
Emphasize co-location.
There is a long history of research on computer supported cooperative work for distributed access (teleconferencing support). To complement this work, we chose to explore new kinds of support for team meetings in single spaces, taking advantage of the shared physical space for orientation and interaction.
Reliance on social conventions.
Many projects have attempted to make an interactive workspace smart (usually called an intelligent environment). Rather than have the room react to users, we have chosen to focus on providing the affordances necessary for a group to adjust the environment as they proceed with their task. In other words, we have set our semantic Rubicon such that users and social conventions take responsibility for actions, and the system infrastructure is responsible for providing a fluid means to execute those actions.
Now they've published a paper on
the Event Heap, an attempt at making a coodination framework for all the different software users run in the iRoom.
The paper is about solving social coordination problems among software by giving every piece of software access to a shared "space" where all the software can see the messages being passed around and acted on by the other software.
One app written in this way is a display tool that coordinates presentation in the physical environment of the iRoom:
While traditional presentation programs coordinate the display of slides across time, SmartPresenter coordinates the display of information across both time and display surfaces. For example, a presentation might specify that at time-step 4, slide 17 from a Power Point presentation be shown on the left touch screen, a 3-d model be displayed on the high-resolution front screen, and web pages be displayed on the other two touch screens.
As an analogy, the Event Heap is, for the software accessing it, like a project room with whiteboards on all the walls -- no matter what you're working on in your little corner, you can read whatever anyone else has written on any of the other surfaces. Much of it might not be of much use to you, but its there if you need it.
The gory details are, well, gory -- it uses IBM's TSpaces project, an implementation of Gelertner's tuplespaces idea in Java, and all like that -- but the basic message is fascinating: as we start working with the
blowback of our mediated social interactions moving into real world interaction, the borders between our tools are going to have to be made semi-permeable as well, so they can function as socially as we can.
TrackBack URL:
http://www.corante.com/cgi-bin/mt/teriore.fcgi/1586.
Listed below are links to weblogs that reference Technical document from iRoom: