Abstract: Techniques to manage presence information based on routing rules are described. An apparatus may comprise a presence management component operative to manage presence information for a presentity. The presence management component comprises a presence interface module operative to receive a routing rule for a communication event for a presentity node used by a presentity. The presence management component also comprises a presence control module communicatively coupled to the presence interface module, the presence control module operative to determine presence state information based on the routing rule. The presence management component further comprises a presence publish module communicatively coupled to the presence control module, the presence publish module operative to publish the presence state information to multiple watcher nodes. Other embodiments are described and claimed.

Abstract: Techniques to manage presence information based on routing rules are described. An apparatus may comprise a presence management component operative to manage presence information for a presentity. The presence management component comprises a presence interface module operative to receive a routing rule for a communication event for a presentity node used by a presentity. The presence management component also comprises a presence control module communicatively coupled to the presence interface module, the presence control module operative to determine presence state information based on the routing rule. The presence management component further comprises a presence publish module communicatively coupled to the presence control module, the presence publish module operative to publish the presence state information to multiple watcher nodes. Other embodiments are described and claimed.

Abstract: Techniques to manage presence information based on routing rules are described. An apparatus may comprise a presence management component operative to manage presence information for a presentity. The presence management component comprises a presence interface module operative to receive a routing rule for a communication event for a presentity node used by a presentity. The presence management component also comprises a presence control module communicatively coupled to the presence interface module, the presence control module operative to determine presence state information based on the routing rule. The presence management component further comprises a presence publish module communicatively coupled to the presence control module, the presence publish module operative to publish the presence state information to multiple watcher nodes. Other embodiments are described and claimed.

Abstract: Architecture for gathering and presentation to a remote user (watcher) of presence, preferences, and capabilities information of a local user (publisher). An extensible presence document is employed, as transmitted by the publisher, that contains specific information about the capabilities of the publisher endpoint and preferences that are for the publisher overall. The document is aggregated, and the aggregated capabilities are transmitted to watchers. The watchers render this information in a user experience.

Abstract: Architecture for gathering and presentation to a remote user (watcher) of presence, preferences, and capabilities information of a local user (publisher). An extensible presence document is employed, as transmitted by the publisher, that contains specific information about the capabilities of the publisher endpoint and preferences that are for the publisher overall. The document is aggregated, and the aggregated capabilities are transmitted to watchers. The watchers render this information in a user experience.

Abstract: Architecture for gathering and presentation to a remote user (watcher) of presence, preferences, and capabilities information of a local user (publisher). An extensible presence document is employed, as transmitted by the publisher, that contains specific information about the capabilities of the publisher endpoint and preferences that are for the publisher overall. The document is aggregated, and the aggregated capabilities are transmitted to watchers. The watchers render this information in a user experience.

Abstract: Architecture for extending a presence document into additional formats and protocols. An aggregator federates the presence document into a standardized schema that can be consumed at a standardized endpoint. The standardized schema can be a web feed that is interoperably consumed by a web feed consumer, for example, an RSS/Atom schema. Access of the presence document content is controlled based on a relationship between the user and a subscriber. Categories are specified for the presence document content, and access is controlled according to the categories. The specified categories can correspond to user authentication levels. The categories can include multiple syndicated channels corresponding to multiple subscriber access levels. In this way, levels of access are defined for various categories of availability information and activity information, based on the relationship of the user to the subscriber.

Abstract: Architecture that synchronizes meeting information (e.g., documents, agenda, action items, notes, attendees, join information, etc.) across the different stages of a meeting lifecycle. The architecture provides client-side synchronization across meeting lifecycle services that can include a scheduling server, content management server, and meeting server, as well as other lifecycle servers that may be employed. Information from the scheduling server can be written asynchronously to the other lifecycle servers, updates made to the content management server are synchronized to the other servers, and updates made to the meeting server are synchronized to the other servers.

Abstract: Architecture for gathering and presentation to a remote user (watcher) of presence, preferences, and capabilities information of a local user (publisher). An extensible presence document is employed, as transmitted by the publisher, that contains specific information about the capabilities of the publisher endpoint and preferences that are for the publisher overall. The document is aggregated, and the aggregated capabilities are transmitted to watchers. The watchers render this information in a user experience.

Abstract: Alternate contacts information for a subscriber is dynamically generated and managed by schematizing representation of alternate contacts. Initial alternate contacts are computed based on organization hierarchy, delegate information set by a user in system directory, contacts information set by the user in personal directories, and/or by other user defined settings. The information is customized by the user and associated with user presence such that a dynamic alternate contacts list is published to other users based on a presence status of the user.

Abstract: Callers are enabled to choose among available communication modes based on information about a called party's mobile status. Mobile status information including whether or not the called party is in motion, their speed if they are in motion, a direction of their movement, as well as their location, can be received from sources such as a presence server, a GPS service, and other information sources. Inferences are made based on the received information and available and/or recommended communication modes suggested to the caller.

Abstract: Techniques to manage presence information based on routing rules are described. An apparatus may comprise a presence management component operative to manage presence information for a presentity. The presence management component comprises a presence interface module operative to receive a routing rule for a communication event for a presentity node used by a presentity. The presence management component also comprises a presence control module communicatively coupled to the presence interface module, the presence control module operative to determine presence state information based on the routing rule. The presence management component further comprises a presence publish module communicatively coupled to the presence control module, the presence publish module operative to publish the presence state information to multiple watcher nodes. Other embodiments are described and claimed.

Abstract: A system, method, and computer program product for administering a distribution channel for the promotion and sale of products and services. Content from vendors is maintained in a central repository and administered by the distribution channel manager. Tools are provided for members of the distribution channel to build their own customized web sites for providing consumers access to the content in the central repository as well as their own proprietary information. Sales leads are generated and tracked and routed to the consortium member agencies.