OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.


Help: OASIS Mailing Lists Help | MarkMail Help

oasis-charter-discuss message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]

Subject: Call for Comment: proposed Charter for OASIS Context Server (CXS) Technical Committee

To OASIS Members:

A draft TC charter has been submitted to establish the OASIS Context Server (CXS) Technical Committee. In accordance with the OASIS TC Process Policy section 2.2: (https://www.oasis-open.org/policies-guidelines/tc-process#formation) the proposed charter is hereby submitted for comment. The comment period shall remain open until 23:59 UTC on 06 March 2015.

OASIS maintains a mailing list for the purpose of submitting comments on proposed charters. Any OASIS member may post to this list by sending email to: oasis-charter-discuss@lists.oasis-open.org. All messages will be publicly archived at: http://lists.oasis-open.org/archives/oasis-charter-discuss/. Members who wish to receive emails must join the group by selecting "join group" on the group home page: http://www.oasis-open.org/apps/org/workgroup/oasis-charter-discuss/. Employees of organizational members do not require primary representative approval to subscribe to the oasis-charter-discuss e-mail.

A telephone conference will be held among the Convener, the OASIS TC Administrator, and those proposers who wish to attend within four days of the close of the comment period. The announcement and call-in information will be noted on the OASIS Charter Discuss Group Calendar.

We encourage member comment and ask that you note the name of the proposed TC (CXS) in the subject line of your email message.

—- TC Charter 

TC Formation Proposal - OASIS Context Server (CXS)
Section 1: Charter

(1)(a) TC Name
OASIS Context Server (CXS) Technical Committee 

(1)(b) Statement of Purpose

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.

The benefits for end users include more personalized and relevant user experiences as well as more control over aggregated collected data. 

The benefits for organizations include simpler ways to setup, aggregate, and use the collected data associated with their audiences. 

A clear and defined standard for personalization will also 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.

The TC shall also 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.

(1)(c) Scope

The TC will accept as input the following initial contributions:

1. “Context Server proposal” contributed by Jahia and Enonic, https://docs.google.com/document/d/1YKwDyJaouKzzN3SqSa4DYZiEvgJmGkZVN-yyUG0uDVI/edit?usp=sharing

2. An externally hosted (under an Apache License) open source reference implementation: “Project Unomi : Open Source Context Server prototype implementation” contributed by Jahia, https://github.com/Jahia/unomi

The TC will further accept input from various vendors' existing interfaces and domain models, and other contributions for consideration without any prejudice or restrictions. These inputs will be evaluated based on technical merit insofar as they conform to the TC charter.

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.

Example use cases:

* Enable collection and aggregation of user behavioral data into profiles
* Enable user segment definitions (i.e., based on demographics) to identify sets of profiles
* Enable third party systems (WCM etc.)  to tag and serve content based on segments
* Allow marketing systems to access profiles and compile lists for campaigns
* Allow users to access the context server to exercise control over their collected data (user privacy)
* Deliver product recommendations based on user behavior collected by the context server

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. 

The TC will focus on producing the required deliverables such as a detailed list of use cases, a domain model, a REST API, as well as a reference implementation.

The following 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

(1)(d) Deliverables

The initial set of deliverables will include:

1. Context Server specification (2015 projected completion date) that includes:

   1. Use cases
   2. Domain Model
   3. Rest API

2. Open Source Reference Implementation (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.

(1)(e) IPR Mode

The IPR mode for the TC will be Non-Assertion Mode ( https://www.oasis-open.org/policies-guidelines/ipr#s10.3 ).

(1)(f) 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.

(1)(g) Language

The language in which the TC will conduct business: English
Section 2: Additional Information

(2)(a) Identification of Similar Work

* W3C “Customer Experience Digital Data Acquisition proposal” : http://www.w3.org/community/custexpdata/ . As of 2014-10, the specification draft is still quite young (v 0.5); it specifies mostly a _javascript_ Data model for storing (mostly e-commerce) context data inside browser objects. Clearly there is some overlap with what we are trying to achieve, so we would plan to approach them to see how we may help each other so as not to duplicate efforts.

* Data Management Platforms (DMP ,http://searchcio.techtarget.com/definition/data-management-platform-DMP) as a class are technically close to the concept of the context server. Many products define themselves as DMPs but (to our knowledge) no official standard has been established. The work produced in this TC could be beneficial to DMP product designs.

(2)(b) First TC Meeting

We propose a face to face kickoff meeting , to be held April  29-30th 2015 , possibly in Paris. Face to face sponsoring will be provided jointly by Enonic, Jahia, Liferay

(2)(c) Ongoing Meeting Schedule

Split into Workgroups with designated tasks

* Frequent meetings for workgroups (weekly)
* Regular formal TC meetings (3-4 weeks)

(2)(d) TC Proposers

Serge Huber, shuber@jahia.com, Jahia Solutions Group

Thomas Draier, tdraier@jahia.com, Jahia Solutions Group

Chris Laprun, claprun@jahia.com, Jahia Solutions Group

Thomas Lund Sigdestad, tsi@enonic.com, Enonic

Runar Myklebust, rmy@enonic.com, Enonic

Sten Roger Sandvik - srs@enonic.com, Enonic

Julio Camarero, julio.camarero@liferay.com, Liferay

Arje Cahn, Hippo, a.cahn@onehippo.com, Hippo B.V.

Ate Douma, Hippo, a.douma@onehippo.com, Hippo B.V.

Frank van Lankvelt, Hippo, f.vanlankvelt@onehippo.com, Hippo B.V.

(2)(e) Primary Representatives' Support

Thomas Sigdestad, tsi@enonic.com, Enonic: "Enonic supports the OASIS CXS TC charter. We see CXS standard as a major step in commoditizing real-time personalized digital experiences - Leading the CXS TC proposal and major contributor to the work - we see CXS is a pillar in the future of our company"

Serge Huber, shuber@jahia.com, Jahia Solutions Group: "Jahia supports the OASIS CXS TC charter. We strongly believe that as User Experience is becoming a key success factor in the industry and a critical infrastructure for Enterprises. This is the reason why standardization and open source commoditization are needed and we are focused on making this a reality through this new Context Server proposal. Leading the CXS TC proposal, we are submitting the initial specification document as well as the open source implementation and we will support CXS in our product line. "

James Falkner, james.falkner@liferay.com, Liferay: "Liferay supports the OASIS CXS TC charter. We believe that being able to provide a unique experience to users based on their context will be a key part in our vision as a platform. As a convener, we see the context server as a very promising solution to achieve interconnection of different services and providers between different platforms."

Arje Cahn, Hippo, a.cahn@onehippo.com, Hippo B.V., the company behind Hippo CMS, supports the OASIS CXS TC charter. The ability to bring together different streams of visitor data from disparate systems using a standardized API is part of our vision for a more contextualized web experience. We intend to support CXS in our Hippo CMS product line.

(2)(f) TC Convener

Serge Huber, Jahia Solutions, http://www.jahia.com, shuber@jahia.com

Thomas Sigdestad, Enonic, https://enonic.com, tsi@enonic.com 

Julio Camarero, Liferay, http://www.liferay.com , julio.camarero@liferay.com

(2)(g) OASIS Member Section

The CXS TC does not intend to seek affiliation with any OASIS Member Section.

(2)(h) Anticipated Contributions

1. “Context Server proposal” contributed by Jahia and Enonic: https://docs.google.com/document/d/1YKwDyJaouKzzN3SqSa4DYZiEvgJmGkZVN-yyUG0uDVI/edit?usp=sharing

2. An externally hosted (under an Apache License) open source reference implementation : “Project Unomi : Open Source Context Server prototype implementation” contributed by Jahia: https://github.com/Jahia/unomi

(2)(i) FAQ Document

None at this time

(2)(j) Work Product Titles and Acronyms

We propose “Context Server” as the Work Product title and CXS as the acronym for “ConteXt Server”.


/chet   [§] 
Chet Ensign
Director of Standards Development and TC Administration 
OASIS: Advancing open standards for the information society

Primary: +1 973-996-2298
Mobile: +1 201-341-1393 

Check your work using the Support Request Submission Checklist at http://www.oasis-open.org/committees/download.php/47248/tc-admin-submission-checklist.html 

TC Administration information and support is available at http://www.oasis-open.org/resources/tcadmin

Follow OASIS on:
LinkedIn:    http://linkd.in/OASISopen
Twitter:        http://twitter.com/OASISopen
Facebook:  http://facebook.com/oasis.open

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]