EXPERIENTIAL VALUE: A HIERARCHICAL MODEL, THE IMPACT ON E-LOYALTY AND A CUSTOMER TYPOLOGY

The main objective of this study is to empirically test a fourth-order hierarchical model of experiential value in an online book and CD setting. In addition, we provide empirical evidence for the role of hedonic and utilitarian value components in creating attitudinal and behavioral loyalty. Finally, we develop an online customer typology, based on the underlying value sources. Based on a sample of 190 visitors of online book and CD retailers, we used PLS to test a third and fourth order hierarchical model of experiential value, emphasizing a hedonic (intrinsic) and utilitarian (extrinsic) value component and the existence of the holistic concept of experiential value. Our results demonstrate that experiential value consists of the third order components hedonic (intrinsic) and utilitarian (extrinsic) value. Both value aspects impact attitudinal loyalty ultimately leading to behavioral loyalty which is also directly affected by utilitarian value. Finally, a nonhierarchical (k-means) cluster analysis identified four segments of online visitors: hedonists, utilitarians, active negativists, and reactive positivists.marketing ;

Modeling, Simulation and Emulation of Intelligent Domotic Environments

Intelligent Domotic Environments are a promising approach, based on semantic models and commercially off-the-shelf domotic technologies, to realize new intelligent buildings, but such complexity requires innovative design methodologies and tools for ensuring correctness. Suitable simulation and emulation approaches and tools must be adopted to allow designers to experiment with their ideas and to incrementally verify designed policies in a scenario where the environment is partly emulated and partly composed of real devices. This paper describes a framework, which exploits UML2.0 state diagrams for automatic generation of device simulators from ontology-based descriptions of domotic environments. The DogSim simulator may simulate a complete building automation system in software, or may be integrated in the Dog Gateway, allowing partial simulation of virtual devices alongside with real devices. Experiments on a real home show that the approach is feasible and can easily address both simulation and emulation requirement

Identification of Design Principles

This report identifies those design principles for a (possibly new) query and transformation language for the Web supporting inference that are considered essential. Based upon these design principles an initial strawman is selected. Scenarios for querying the Semantic Web illustrate the design principles and their reflection in the initial strawman, i.e., a first draft of the query language to be designed and implemented by the REWERSE working group I4

AtomsMasher: Personal Reactive Automation for the Web

The rise of "Web 2.0" has seen an explosion of web sites for the social sharing of personal information. To enable users to make valuable use of the rich yet fragmented sea of public, social, and personal information, data mashups emerged to provide a means for combining and filtering such information into coherent feeds and visualizations. In this paper we present AtomsMasher (AM), a new framework which extends data mashups into the realm of context-aware reactive behaviors. Reactive scripts in AM can be made to trigger automatically in response to changes in its world model derived from multiple web-based data feeds. By exposing a simple state-model abstraction and query language abstractions of data derived from heterogeneous web feeds through a simulation-based interactive script debugging environment, AM greatly simplifies the process of creating such automation in a way that is flexible, predictable, scalable and within the reach of everyday Web programmers

Towards a Rule Interchange Language for the Web

This articles discusses rule languages that are needed for a a full deployment of the SemanticWeb. First, it motivates the need for such languages. Then, it presents ten theses addressing (1) the rule and/or logic languages needed on the Web, (2) data and data processing, (3) semantics, and (4) engineering and rendering issues. Finally, it discusses two options that might be chosen in designing a Rule Interchange Format for the Web