OASIS Context Server (CXS) TC

TC Page     Send a comment to this TC

Supporting delivery of personalized user experiences, establish a Customer Data Platform standard


The Technical Committee was closed by OASIS TC Administration on 09 December 2022 and is no longer active. Archives of its work remain publicly accessible and are linked from this page. OASIS appreciates the efforts of all those who participated in this TC.

Table of Contents


See the announcement: Customer Data Platform v1.0 from CXS TC approved as a Committee Specification.

See press announcement: OASIS Starts Context Server (CXS) Initiative to Advance Standards for Personalized User Experiences Online: Jahia, LifeRay, Progress Software, and Others Collaborate on Standards for Big Data, Web Content Management (WCM), and Digital Marketing

See CMSWire article: "CMS Vendors Partner on Open Customer Data Sharing Standard" featuring interviews with CXS TC members, Serge Huber of Jahia and Thomas Sigdestad of Enonic.

The first meeting of the OASIS Context Server (CXS) Technical Committee was held as a face-to-face meeting on April 29-30, 2015, in Paris, France. Serge Huber and Thomas Sigdestad were elected co-chairs. Participation in the OASIS Context Server (CXS) TC is open to all interested parties. Contact join@oasis-open.org for more information.


The OASIS Context Server (CXS) TC was chartered to create specifications for a Context Server (also known as Customer Data Platforms, CDP see below) as a core technology for enabling the delivery of personalized user experiences. The goal is to assist organizations that currently struggle to create and deliver consistent personalized experiences across channels, markets, and systems. The Context Server (aka CDP) will simplify management, integration, and interoperability between solutions providing services like Web Content Management, CRM, BigData, Machine Learning, Digital Marketing, and Data Management Platforms. TC members are producing a detailed list of use cases, a domain model, a REST API, as well as a reference implementation to serve as a real world example of how the Context Server standard can be used.

Relation to Customer Data Platforms: since the OASIS Context Server TC has been established, the term Customer Data Platform (CDP) has emerged and can be interchangeably be used for the Context Server. To reflect this, the specification produced by this TC has changed its name to : the Customer Data Platform specification.

Relation to Apache Unomi : the reference implementation of the Customer Data Platform specification is produced as part of the Apache Unomi project.

For more information on the Context Server (CXS) TC, see the TC Charter.


No subcommittees have been formed for this TC.

TC Liaisons

No TC Liaisons have been announced for this TC.

TC Tools and Approved Publications

Links for tools/publications have not yet been activated.

Technical Work Produced by the Committee

Customer Data Platform Version 1.0. Edited by Thomas Lund Sigdestad and Serge Huber. 04 October 2019. OASIS Committee Specification 01. https://docs.oasis-open.org/cxs/cdp/v1.0/cs01/cdp-v1.0-cs01.html. Latest version: https://docs.oasis-open.org/cxs/cdp/v1.0/cdp-v1.0.html.

Expository Work Produced by the Committee

There are no approved expository work products for this TC yet.

External Resources

Although not produced by the OASIS Context Server (CXS) TC, the following information offers useful insights into its work.

Apache Unomi, the reference implementation of the CDP standard specification currently being defined by this TC.

Mailing Lists and Comments

cxs: the discussion list used by TC members to conduct Committee work. TC membership is required to post, and TC members are automatically subscribed. The public may view the list archives.

cxs-comment: a public mailing list for providing feedback on the technical work of the OASIS Context Server (CXS) TC. Send a comment or view the comment list archives.

Press Coverage and Commentary

Additional Information

Providing Feedback: OASIS welcomes feedback on its technical activities from potential users, developers, and others to better assure the interoperability and quality of OASIS work.