Alec Saunders (CEO of iotum) posted out a wonderful visionary piece on presence called “New Presence” and the Voice 2.0 Manifesto. It does a good job of pointing out the potential of presence, the set of data and sensors it needs to have to function, and the need to somehow break up what he calls the “walled gardens” that independent presence systems have today.
I’d like elaborate on some of the comments I posted to his blog entry and to relate his vision of presence to the Rich Presence model I introduced in my telebriefing “Stop Interrupting Me! Effects of Communication on Info-stress and Attention Fatigue” (conceptual model posted up here). Incidentally, I still like my term “rich presence” better as it implied more functional rather than just ‘new and different”.
When the Voice 2.0 Manifesto was written, it identified presence as the enabler of conversation, allowing parties to easily determine each others willingness to engage, and by which technology.
Lord knows I have way too many conversations and would have way more if my spam filter wasn’t working and I didn’t have caller ID.It’s the quality of the conversations that is the issue. I want presence to enable higher quality conversations that are more relevant and important to me. In essence, presence is one of the key enablers of attention management.
Alec posts up a good diagram of all the profile, context, and relationship data involved in his future vision of presence, similar to the “data” and “sensors” on my conceptual architecture but his has some great additional detail.But from his description I am wondering where the brains are in his model.Where does the information get crunched for a particular message coming in? In my conceptual model of an attention management system I define an “attention response engine” with Rich Presence, Rules & Scoring, and Channel Switching & Routing components. Deciding where presence stops and the decision making kicks in has been a matter of debate between myself and Mike Gotta.
Alec has a good listing of new applications that rich presence would enable, but I believe presence must be valuable to end users, not the vendors. If the end users don’t get enough out of it, the vendors will be left high and dry. Per my pushing/pulling definition of “attentional technologies and capabilities”, the issue for end users is: does this quiet my life, pushing back noise and pulling the messages most important to me in my current state forward?
…the simple confusion around protocol standards. Ironically, this ought to be the simplest piece to solve. Standards are simply codified ways to describe information. The tussle between SIP / SIMPLE, and XMPP must be resolved before New Presence can effectively move forward.
I think there are a lot more standards needed than simply resolving SIP/SIMPLE and XMPP. Standards on how roles and relationships are defined, interests, rules and scoring, preferences must all be defined. XMPP is extensible, but that doesn’t mean it defines these extensions.
These are not criticisms, just adjustments to a visionary piece. I think we are both thinking in the same direction. My hope is that a solid enough vision of presence can be created to encourage vendors to actually move forward with something easy to use and, while not perfect, a lot better than we have today.