Using the Unified Communications Enhanced Presence Schema
This content is no longer actively maintained. It is provided as is, for anyone who may still be using these technologies, with no warranties or claims of accuracy with regard to the most recent product version or service release.
The Unified Communications Enhanced Presence Schema defines the syntax and basic semantics of the data types that are used to represent the presence and other data as values of category instances on the unified communications platform based on Microsoft Office Communications Server.
However, the server does not validate the XML data provided that the names of the XML elements are registered with it. Invalid XML elements are ignored by the server. The main utility of the schemas is to provide applications other than Office Communicator with the knowledge of the data types. This approach is useful when the applications must interoperate with Communicator and when the data of interest is not already encapsulated by the API. In such cases, you can use the schemas to generate valid enhanced presence data before publication and then parse the enhanced presence data originating from Communicator. This process is necessary for all enhanced presence data when using the Unified Communications Managed API. This process is only necessary for some presence data when using Unified Communications Client API. Examples of such data include the legacy presence data as well as custom presence data—this data is not encapsulated by the API. With Office Communicator Automation API, all the presence data is encapsulated and you do not work directly with the schemas.