incubator-cvs mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Apache Wiki <wikidi...@apache.org>
Subject [Incubator Wiki] Update of "UnomiProposal" by jbonofre
Date Wed, 09 Sep 2015 13:40:59 GMT
Dear Wiki user,

You have subscribed to a wiki page or wiki category on "Incubator Wiki" for change notification.

The "UnomiProposal" page has been changed by jbonofre:
https://wiki.apache.org/incubator/UnomiProposal?action=diff&rev1=1&rev2=2

  == Abstract ==
  
  Unomi is a reference implementation of the OASIS Context Server specification currently
being worked on by the OASIS Context Server Technical Committee. It provides a high-performance
user profile and event tracking server.
- Proposal
+ 
+ == Proposal ==
+ 
  The server is a data management platform that provides real-time user profile and event
storage as well as a rule engine and fully featured REST+JSON interfaces which make integration
with very different systems easier.
+ 
  One of the main objectives of this implementation is to be modular and flexible enough to
relatively easily build integration into systems such as CMS, WCM, CRM or even ERP. Built
using Apache Karaf and ElasticSearch, it is designed to also be easily clusterable to address
high-traffic scenarios where lots of profile data will need to be updated at a high frequency.
  
  == Background ==
  
  Unomi was built from scratch to serve as a reference implementation for the OASIS Context
Server proposal. It has been developed by Jahia Software.
+ 
  It initially served as a test-bed while working on the specifics of the new proposal, to
make sure that the concepts being discussed and decided would make sense in an actual implementation.
At the same time, Jahia, one of the companies involved in the standardization work, needed
a basis to build their new Marketing Factory product, so it made a lot of sense to start this
way. Thanks to a lot of work done in the standard, the implementation was produced relatively
quickly and this made it possible to build a commercial product on top of this implementation
that will be released in Winter 2015. This implies that the core of the commercial product
being proposed here will undergo a full set of QA tests, including and scalability tests.
+ 
  Another important objective was to provide a platform that deals with user data in an “ethical”
way, in order to make the usage of personal data more transparent and to improve privacy.
Through the work in the standard and this open source implementation, it is the hope of the
original designers that it will be easier for all users of this technology to fully understand
how the data is being used and what type of control is exercised over it. A transparent usage
of customer data could become, in the near future, a key tool to keep customer loyalty. Companies
would then be able to leverage digital marketing frameworks capabilities such as Unomi, but,
as a fair - and quite possibly legally mandatory - counterpart, should allow end users to
understand the data being used, as well as the way it is used, in order to give them more
control over which data to share or to anonymise.
+ 
  The purpose is to bring Jahia Marketing Factory codebase into the Apache Software Foundation
(ASF) in order to build a vibrant, diverse and self-governed open source community around
the technology. Jahia will continue to market and sell Jahia Marketing Factory based on Unomi.
Unomi and Jahia Marketing Factory will be managed separately. This proposal covers the Unomi
source code (mainly written in Java), Unomi documentation and other materials currently available
on GitHub. Unomi is our primary choice for a name of the project.
  
  == Rationale ==
  
  Building highly scalable, performant and flexible personalization architectures requires
major efforts. The complexities of requirements, integrations and use cases is directly related
to the number of users, and Apache projects usually get a lot of visibility and usage. Therefore
it was a goal from the start to share this project with the ASF, as it is believed this is
the best way to achieve the true potential of this codebase, to make it highly visible and
continually improve on its design and implementation to make it the best tool for the job
for a wide variety of use cases.
+ 
  The project, as it sits a bit higher than usual BigData frameworks, could be used a front-end
to a lot of existing Apache project that could be integrated to help deliver more power into
the platform. For example Unomi doesn’t currently include machine learning but it could
very well be expanded to include a module that would use Apache Mahout. In the same way, for
the persistence layer, an already existing Service Provider Interface could be used to provide
other backends such as HDFS, Cassandra, Solr or any other.
  
  == Initial Goals ==
@@ -28, +35 @@

  == Current Status == 
  
  Currently, the project code base is licensed under the Apache License and is available on
Github (https://github.com/Jahia/unomi). 
+ 
  The Jahia Marketing Factory, as soon as it is released, plans on building a robust end user
community of paying and non-paying customers, and hopefully this will trickle down to the
community on the Apache Unomi project once it is established. 
+ 
  Documentation is currently being worked on, but as it is the implementation of a public
standard, most of the conceptual and API documentation will be covered by the specification.
Any specifics of the implementation will of course be documented in the incubator project
  
  == Meritocracy ==
@@ -57, +66 @@

  == Known Risks ==
  
  Development has been sponsored mostly by a single company (or its predecessors) thus far
and coordinated mainly by the core Jahia Unomi team. 
+ 
  For the project to fully transition to the Apache Way governance model, development must
shift towards the meritocracy-centric model of growing a community of contributors balanced
with the needs for extreme stability and core implementation coherency. 
+ 
  The tools and development practices in place for the Jahia Marketing Factory product are
compatible with the ASF infrastructure and thus we do not anticipate any on-boarding pains.
Migration from the current GitHub repository is also expected to be straightforward. 
  
  == Orphaned products ==

---------------------------------------------------------------------
To unsubscribe, e-mail: cvs-unsubscribe@incubator.apache.org
For additional commands, e-mail: cvs-help@incubator.apache.org


Mime
View raw message