Hi Serge - good start, but I think we should put more focus on the client here (for a start). And let as much as possible of the interaction between systems go through the client (_javascript_ing). This would by far be the simplest way to integrate the systems. Each system could then however contribute to the context and use the now "rich" context to deliver the best experience.
WCM compiles and returns initial page with a "thin" context.
The returned page has scripts to other systems that are executed and enrich the context, say the Marketing Automation tool for instance.
A section of the page was emty - to be filled in with "recommendations" for the user.
These recommendations come from another system, and are filled out async.
The now "rich" context is passed to this system along with the request - which returns a personalized result finally injected into the page.
From: "Serge Huber" <
shuber@jahia.com>
To: wemi@lists.oasis-open.orgSent: Thursday, August 29, 2013 8:34:50 AM
Subject: [wemi] Use cases definitions, let's get the ball rolling…
First of all thanks to all that could make the meeting, and for the ones who couldn't, I've sent minutes of the meeting and the uploaded the meeting slides to the OASIS WEMI group's document area.
I'd like to get the ball rolling as quickly as possible on the use case definitions, so maybe we could start brainstorming a little here ?
I am imagining the following scenario :
- A user comes into a website using his browser, and all his browser sends along is a cookie ID from a previous visit.
- The front-end delivering the site is a WCM, that actually recognizes the cookie and loads it's own data that it collected for the user (could be anything, but usually something like previous visit time, eventually a username, etc. This could also be a previously saved aggregated context.
- The WCM builds up the context information, and then forwards it different systems such as a web marketing analysis tool, a CRM and an e-commerce to get more information about the current context, for example the web marketing might give information about the number of times the user has visited certain pieces of content, the CRM might give us some information about the users purchase history, and the e-commerce system might tell us if the user has a current cart with non-purchased items.
- The WCM might then forward all this built up context information to a business process tool that could use it to process some business logic and return an updated context
- The WCM could then use the updated context to personalize the content being displayed for the user, for example reminding him that he has a cart that's busy and that since he's a good regular customer he will get a discount if he orders in the next 10 minutes.
The above scenario is of course just an example, but it doesn't require any _javascript_ object to be maintained on the users browser, which, although interesting, might be a little problematic to implement and especially to gain acceptance of the standard.
What do you think about this use case ?
Best regards,
Serge Huber.
- -- --- -----=[ shuber at jahia dot com ]=---- --- -- -
CTO & Co-founder - Jahia Solutions Group, 9 Routes de Jeunes, 1227 Acacias, Switzerland
Jahia’s next-generation, open source CMS stems from a widely acknowledged vision
of enterprise application convergence – web, search, document, social and portal –
unified by the simplicity of web content management.
http://www.jahia.com