Standardizing personal experience sounds impersonal, doesn't it? Yet, that's what we're talking about here and there are plenty of software folks believing it's the right time for such an effort. When companies manage or utilize a number of systems involved with customer experience management, there is a need for those systems to transfer data from one system to the next. It is a huge challenge for CIOs, trying to streamline heterogeneous technologies and the data and transactions flowing from each solutions from their information system, while at the same time avoiding losing control over the collected data.
Working together, Jahia and Enonic have launched a new project at the OASIS international consortium to develop a standard that will enable the creation, management and delivery of personalized web and digital experiences. This initiative lead to the creation of the OASIS Context Server (CXS) Technical Committee (TC). Think of this effort similar to what brought us Content Management Interoperability Services (CMIS) but instead of a standard for content, we're talking about a standard for personalized data.
This is how Jahia and Enonic realized that the best solution would be to define a standardized and extensible model for collecting and sharing visitor context - in order to deliver personalized and better user experiences across systems, while improving user privacy at the same time. As personalized web solutions are becoming a mandatory part of enterprise digital presence, it is critical to provide open source and standardized solutions. This is why Jahia is also proposing to the TC an existing open source reference implementation, called Unomi (pronounced “You Know Me”), of the future context server standard under an Apache License.
Hence their proposal to OASIS. The effort is already being embraced by the industry, and other market players recently joined: Liferay, Hippo and the currently open Call for Participation invites any interested party to join the new Technical Committee in advance of its first meeting.
In a recent announcement, both Serge Huber, Jahia CTO, and Thomas Sigdestad, CTO of Enonic, commented, “We are thrilled to see how the CXS TC is being welcomed by the community. The OASIS Consortium is the perfect organization to make the standard happen and be embraced by the market. We're looking forward to the first face to face meeting in Paris at the end of April.”
“CXS will affect so many facets of the marketplace. Its success hinges on having the broadest possible range of organizations involved,” said Laurent Liscia, CEO of OASIS. “We're calling on the marketing automation companies, data management platform providers and companies involved in machine learning and Big Data and to work with the traditional WCM and CRM software providers to ensure CXS reflects everyone’s use cases. We applaud Jahia and Enonic for initiating this vital standardization project.”
Purpose of the CXS TC
The purpose of the TC will be to create specifications for a Context Server as a core technology for enabling the delivery of personalized digital experiences. Organizations currently struggle to create and deliver consistent personalized experiences across channels, markets, and systems. The Context Server will simplify management, integration, and interoperability between solutions providing services like Web Content Management, CRM, BigData, Machine Learning, Digital Marketing, and Data Management Platforms.
Proposed initial contributions:
- Context Server proposal” contributed by Jahia and Enonic
- An externally hosted (under an Apache License) open source reference implementation: “Project Unomi : Open Source Context Server prototype implementation” contributed by Jahia
CXS TC key dates and OASIS official information
- TC proposal by Jahia and Enonic : February 20th, 2015
- Discussion opening about the proposed charter by OASIS : February 20th, 2015 (details)
- First face to face meeting April 29th and 30th in Paris
- Call for Participation
Source: Information provided by Jahia and Enonic announcement