The basic principles of ExperiaSpere are:
- Experiences can be represented by Java structures that in turn represent portals through resources can be managed.
- In a purchase/delivery sense, Experiences are defined by a series of events that mark the progress from consideration through order to delivery and finally to tear-down.
- Service Factories are where Experience structures live, and these Factories accept orders for the experiences they represent.
- Templates (XML) or metadata define the experiences, and this structure is produced by the Factory when it is initialized and offered for completion to order processes in the form of an XML template. The completed order template is then processed by the Factory to secure the resource commitments.
If you add in our SocioPATH social framework, you add the notion of both a user as a technical identity, and the ability to manage experiences from their ordering through their delivery and settlement in a personalized way, including the ability to exercise policies (through SocioPOLICY) to automate most aspects of communication.