XML Configuration Access Protocol

Abstract: In multimedia communications, presence, and instant messaging systems, there is a need to define Uniform Resource Identifiers (URIs) that represent services that are associated with a group of users. One example is a resource list service. If a user sends a Session Initiation Protocol (SIP) SUBSCRIBE message to the URI representing the resource list service, the server will obtain the state of the users in the associated group, and provide it to the sender. To facilitate definition of these services, this specification defines two Extensible Markup Language (XML) documents. One document contains service URIs, along with their service definition and a reference to the associated group of users. The second document contains the user lists that are referenced from the first. This list of users can be utilized by other applications and services. Both documents can be created and managed with the XML Configuration Access Protocol (XCAP). [STANDARDS-TRACK]

Abstract: This document describes a usage of the Extensible Markup Language (XML) Configuration Access Protocol (XCAP) for manipulating the contents of Presence Information Data Format (PIDF) based presence documents. It is intended to be used in Session Initiation Protocol (SIP) based presence systems, where the Event State Compositor can use the XCAP-manipulated presence document as one of the inputs on which it builds the overall presence state for the presentity. [STANDARDS- TRACK]

Abstract: A method and nodes are introduced to allow pushing from a network towards an IP television (IPTV) terminal an Electronic Program Guide (EPG) in an optimized manner. An IPTV server stores a personalized EPG based on a generic EPG and on a subscriber profile. Upon changes to the personalized EPG, its content is pushed towards the IPTV terminal. According to one aspect of the invention, only changes from what the IPTV terminal has previously stored are being pushed down, thereby saving signalling bandwidth. For that purpose, the EPG as well as a user profile are presented and stored in eXtendable Markup Language (XML) format, allowing the use of XML Configuration Access Protocol for performing changes to the user profile from a Home Subscriber Server. Changes are then pushed towards the IPTV terminal.

Abstract: This specification defines a document format that can be used to indicate that a change has occurred in a document managed by the Extensible Markup Language (XML) Configuration Access Protocol (XCAP). This format indicates the document that has changed and its former and new entity tags. It also can indicate the specific change that was made in the document, using an XML patch format. This format allows also indications of element and attribute content of an XML document. XCAP diff documents can be delivered to clients using a number of means, including a Session Initiation Protocol (SIP) event package.