Response to posting on Elastictime Blog
The following was posted in reply to comments on the Elastictime Blog regarding presence technology. The original article is available at:
http://elastictime.wordpress.com/2006/12/12/9/#comments
This post is right on target as regards a variety of problems facing systems that attempt to accurately represent presence to users. Given a casual glance, presence does not appear to be a complex concept. Examined in real-world circumstances, however, the standard “online” vs “away” (OvA) model is surprisingly insufficient. In order to develop an effective means of providing robust representations of presence, it is important to develop definitions we can use to describe the various components.
As you describe in your discussion of unified communications, presence systems often relate our presence relative to a device used to communicate (telephone, pc, etc.). We can infer then, that “Physical” presence, is the physical presence of a user at a known device. Physical presence often implies a locational linkage. For example, if a user is physically present at their PC and that PC is labeled as “work” or “home”, a valid assumption regarding the users location can be made. As you mention, technologies such as GPS may lead to more refined representations of physical presence, into what I call “Geographical” presence. There are many shortcomings to the current state of geopositioning technology in the office environment, but it is a proven concept for mobile computing.
Unfortunately, presence systems have not been designed to assure accurate representations of physical presence. While it is great that, according to AOL, 1/4 of users change their away message daily, the vast majority of users never change their presence status. In fact, most presence applications default to the “online” condition after a user logs in. This has the detrimental effect of changing physical presence into “Device” presence, representing that the client application is ready to communicate, regardless of actual user status.
Inappropriate handling of device presence can lead to mistrust of the system and “Are you there?” type messages regardless of the user’s representation.
Another concept you discuss is the availability of the user. I would contend that availability is a representation of a user’s physical presence combined with their willingness to be interrupted. So if we look at the communication process, the user has to be present to communicate and also willing to communicate. Interruption management is a topic for an entirely separate post, but most users recognize the importance of interruptions to their daily work tasks. Any presence system needs to allow both the interruptor and the interrupted to make value judgements about the importance of interruptions to ensure essential communications are permitted while those of less importance are not initiated.
Finally, you mention the Windows Presence Platform. Standardized protocols to provide presence are alredy in existence. One example is the Extensible Messaging and Presence Protocol (commonly known as Jabber), which has been evaluated and approved by the IETF. XMPP, although originally designed to support non-proprietary instant messaging, has grown to be a leading presence technology.
Many of the concepts here require their own greater discussions at some later time. This discussion, however, is a great place to bring these problems out of the darkness and into the light where they can begin to be solved. I look forward to participating further!

