« Efficiency vs. Exploration | Main | Microblogging In The Enterprise »

September 05, 2008


Feed You can follow this conversation by subscribing to the comment feed for this post.

Dave Uhlir

Excellent points!

Perhaps you were a tad too hard on UC vendors for doin' a what comes natural in using UC-centric presence models. Application-specific presence isn't the cardinal sin - lack of (presence and other) federation is the real problem.

Presence information is valuable and adding custom presence states that are appropriate for specific applications can add great value to a solution.

For example, for UC applications, it might be useful to have presence states that differentiate between speaking on the phone handset versus the speaker. This distinction is useful because more care must be taken speaking on a call that is being broadcast over a speaker. But if this custom presence state doesn't follow open standards and can't be published to other systems, its utility becomes vanishingly small.

It is gauche to design closed-system communications offerings (and social networking services, collaboration applications, etc.) which can only work for people within the walled garden system.

Once enough of the market understands how useful presence is, systems with non-standard, unfederated presence models will have to get with the program, or be left behind.


Disclosure: I'm employed by Jabber, Inc., a company that has so much belief in the Power of Presence(R) that the phrase is our company tagline and a registered trademark.

Colm Smyth

This is an excellent post, drawing together some of the voices who are emphasising the unifying role of presence awareness in UC.

I'd like to elaborate but right now I'm heads down working on R2 of Avaya's Intelligent Presence Server (due mid next year), so all I can say is, watch this space ;)

The comments to this entry are closed.

Become a Fan

Twitter Updates

    follow me on Twitter