OMA XML Document Management V1.0.1

Note! OMA�XML Document Management�V1.0.1 is Historic and will no longer be maintained by OMA. Newer versions of the Release are available and can be found via the link at the bottom of this page.

The XML Document Management defines a common mechanism that makes user-specific service-related information accessible to the service enablers (e.g., PoC, IM) that need them. Such information is expected to be stored in the network where it can be located, accessed and manipulated (created, changed, deleted). XDM specifies how such information will be defined in well-structured XML documents, as well as the common protocol for access and manipulation of such XML documents, by authorized principals. The XML Configuration Access Protocol (XCAP) [XCAP], as defined by IETF, has been chosen as the common XML Document Management protocol.

The XDM Specification [XDMSPEC] defines two main features:

• The use of the common protocol, XML Configuration Access Protocol (XCAP), by which principals can store and manipulate their service-related data, stored in a network as XML documents.
• The SIP subscription/notification mechanism by which principals can be notified of changes to such documents.

Documents accessed and manipulated via XCAP are stored in (logical) repositories in the network, called generically XML Document Management Servers (XDMS), each repository being associated with a functional entity which uses the data in its associated repository to perform its functions. For example, a POC server accesses a POC XDMS to obtain a particular type of user document, a POC Group document, which provides the member list for a POC group session, and uses this information to invite such members for a POC session.

The Shared XDM Specification [Shared_XDM] specifies a specific type of repository, called a Shared XDMS, which stores documents which can be reused by other enablers. For this release, one such document, the URI List, has been identified.

This is a convenient way for a principal to group together a number of end users (e.g., “Friends' or “Family') or other resources, where such a list is expected to be reused by a number of different enablers. For example, a POC Group member list can include a reference to a URI list as one of its entries.

Due to the reusable nature of the XDM enabler, there will be interactions with other service enablers, and therefore, the architectural design of the XDM enabler (see [XDMAD]) accommodates the needs of those enablers.

Related Links