As presence becomes integrated into many application categories, it becomes problematic to have separate presence models for each application or service. By sharing a common presence platform, applications and services can draw from a consistent, synchronized store of presence information. This common “presence pool” can be tapped to integrate applications, route communications, data and to monitor conditions in real-time. The vision of common presence platform that can be used to add presence to existing or next-generation applications is catching on. There is commentary on the topic and there are commercial presence platforms, including Jabber, Inc.’s, in the market.

The application categories where presence is valuable or essential include: Unified communications, social networks, consumer services, collaboration tools, workflow and monitoring applications. Today, most of these applications have their own, built-from-scratch presence platforms and typically can not exchange presence information with other applications.

What do you think?

• Have you, or are you considering presence-enabling existing or new applications or services?
• Do you like the concept of a common presence platform?
• Do you plan to write your own presence platform from scratch, or use one that works off-the-shelf?

Of course, here at Jabber, Inc., we’re biased towards the off-the-shelf model, but would be interested to learn why you have, or are considering writing your own presence engine from scratch.

This entry was posted on Sunday, November 11, 2007 at November 11, 2007 and is filed under Presence. You can follow any responses to this entry through the RSS 2.0 feed. You can leave a response, or trackback from your own site.