<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<?xml-stylesheet type="text/xsl" href="../part2stratml.xsl"?><StrategicPlan><id/><Name>Proposed Charter for OASIS Context Server (CXS) Technical Committee</Name><Description>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.The TC shall ... work in a forward looking manner to identify features that are useful but not available in existing systems. It is a goal to use existing systems as a point of reference but not be limited by them.</Description><OtherInformation>Organizations currently struggle to create and deliver consistent personalized experiences across channels, markets, and systems. </OtherInformation><StrategicPlanCore><Organization><Name>Context Server (CXS) Technical Committee</Name><Acronym>CXSTC</Acronym><Identifier>_d8cff7e6-bde3-11e4-98db-1ba257876c4e</Identifier><Description/><Stakeholder><Name>OASIS</Name><Description/></Stakeholder><Stakeholder><Name>Chet Ensign</Name><Description>Director of Standards Development and TC Administration,OASIS: Advancing open standards for the information society</Description></Stakeholder><Stakeholder><Name>End Users</Name><Description>The benefits for end users include more personalized and relevant user experiences as well as more control over aggregated collected data.</Description></Stakeholder><Stakeholder><Name>Organizations</Name><Description>The benefits for organizations include simpler ways to setup, aggregate, and use the collected data associated with their audiences. </Description></Stakeholder><Stakeholder><Name>WCM Architects</Name><Description>Audience -- The primary audience for the final output of this TC includes architects from WCM, CRM, Digital Marketing Solutions, Data Management Platforms, Machine Learning and Big Data System vendors and implementers, as well as system architects from organizations that create Customer/Web/User or Digital Experiences.</Description></Stakeholder><Stakeholder><Name>CRM  Architects</Name><Description/></Stakeholder><Stakeholder><Name>Digital Marketing Solution Architects</Name><Description/></Stakeholder><Stakeholder><Name>Data Management Platform Architects</Name><Description/></Stakeholder><Stakeholder><Name>Machine Learning Architects</Name><Description/></Stakeholder><Stakeholder><Name>Big Data System Vendors</Name><Description/></Stakeholder><Stakeholder><Name>Big Data System Implementers</Name><Description/></Stakeholder><Stakeholder><Name>System Architects</Name><Description>from organizations that create Customer/Web/User or Digital Experiences.</Description></Stakeholder><Stakeholder><Name>CXS TC Proposers</Name><Description/></Stakeholder><Stakeholder><Name>Serge Huber</Name><Description>Jahia Solutions Group</Description></Stakeholder><Stakeholder><Name>Thomas Draier</Name><Description>Jahia Solutions Group</Description></Stakeholder><Stakeholder><Name>Chris Laprun</Name><Description>Jahia Solutions Group</Description></Stakeholder><Stakeholder><Name>Thomas Lund Sigdestad</Name><Description>Enonic</Description></Stakeholder><Stakeholder><Name>Runar Myklebust</Name><Description>Enonic</Description></Stakeholder><Stakeholder><Name>Sten Roger Sandvik</Name><Description>Enonic</Description></Stakeholder><Stakeholder><Name>Julio Camarero</Name><Description>Liferay</Description></Stakeholder><Stakeholder><Name>Arje Cahn</Name><Description>Hippo B.V.</Description></Stakeholder><Stakeholder><Name>Ate Douma</Name><Description>Hippo B.V.</Description></Stakeholder><Stakeholder><Name>Frank van Lankvelt</Name><Description>Hippo B.V.</Description></Stakeholder></Organization><Vision><Description/><Identifier>_d8cff9da-bde3-11e4-98db-1ba257876c4e</Identifier></Vision><Mission><Description>To create specifications for a Context Server as a core technology for enabling the delivery of personalized digital experiences. </Description><Identifier>_d8cffab6-bde3-11e4-98db-1ba257876c4e</Identifier></Mission><Value><Name>Personalization</Name><Description>A clear and defined standard for personalization will ... support growth of the broader  market by making it easier for established and new players to ramp up new products, integrate with existing systems, and grow niche opportunities into new market areas.</Description></Value><Value><Name>Integration</Name><Description/></Value><Value><Name>New Market Niches</Name><Description/></Value><Goal><Name>Use Cases</Name><Description>Target a very focused set of use cases related to delivering personalized user experiences.</Description><Identifier>_d8cffb74-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>For the initial set of deliverables, the TC will target a very focused set of use cases related to delivering personalized user experiences. Through the introduction of a "context server",  personalization can be delivered in a simple and interoperable manner. A standard approach to personalization will speed up vendor innovation and reduce integration costs for customers.[These] use cases, while not planned for completion in the initial set of deliverables, may be considered at a later time:* Entitlement and Access Control* Graphical User Interfaces</OtherInformation><Objective><Name>Behavioral Profiles</Name><Description>Enable collection and aggregation of user behavioral data into profiles</Description><Identifier>_d8cffc3c-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>User Segments</Name><Description>Enable user segment definitions (i.e., based on demographics) to identify sets of profiles</Description><Identifier>_d8cffd54-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Content Targeting</Name><Description>Enable third party systems (WCM etc.)  to tag and serve content based on segments</Description><Identifier>_d8cffe26-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.3</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Profile Access</Name><Description>Allow marketing systems to access profiles and compile lists for campaigns</Description><Identifier>_d8cfff34-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.4</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>User Data</Name><Description>Allow users to access the context server to exercise control over their collected data (user privacy)</Description><Identifier>_d8d00006-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.5</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective><Objective><Name>Product Recommendations</Name><Description>Deliver product recommendations based on user behavior collected by the context server</Description><Identifier>_d8d000ce-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>1.6</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation/></Objective></Goal><Goal><Name>Implementation &amp; Testing</Name><Description>Produce reference implementations and test suites.</Description><Identifier>_d8d00196-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>2</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>The TC shall also support the effort of producing reference implementations and test suites that validate the specifications; all such deliverables will be implemented as community open source projects. </OtherInformation><Objective><Name>Reference Implementation</Name><Description>Deliver an open source reference implementation.</Description><Identifier>_d8d00254-bde3-11e4-98db-1ba257876c4e</Identifier><SequenceIndicator>2.1</SequenceIndicator><Stakeholder><Name/><Description/></Stakeholder><OtherInformation>(2015 projected completion date)The reference implementation will serve as a real world example of how the standard can be used. It will deliver all the basic capabilities defined; it might also include other non-specified features such as security and clustering.</OtherInformation></Objective></Goal></StrategicPlanCore><AdministrativeInformation><StartDate/><EndDate/><PublicationDate>2015-02-26</PublicationDate><Source>https://lists.oasis-open.org/archives/members/201502/msg00004.html</Source><Submitter><FirstName>Owen</FirstName><LastName>Ambur</LastName><PhoneNumber/><EmailAddress>Owen.Ambur@verizon.net</EmailAddress></Submitter></AdministrativeInformation></StrategicPlan>
