research:context
Differences
This shows you the differences between two versions of the page.
Both sides previous revisionPrevious revisionNext revision | Previous revision | ||
research:context [2006/07/01 21:51] – jorge | research:context [2009/11/30 16:55] (current) – *prog->soft dharnie | ||
---|---|---|---|
Line 1: | Line 1: | ||
===== Context-Dependent Behaviour Adaptations ===== | ===== Context-Dependent Behaviour Adaptations ===== | ||
+ | [[http:// | ||
==== Motivation ==== | ==== Motivation ==== | ||
Line 17: | Line 18: | ||
==== Design ==== | ==== Design ==== | ||
- | At our lab, we are currently exploring different language constructs for the development of context-aware applications. Here we present one of thes constructs called Split Objects (Bardou et al, ECOOP 1996). In such a model, application entities are composed of roles (known as viewpoints) which represent the different behaviours the entity can adopt. A role is a particular point of view on an entity that has an identification and a partial definition of that entity. The model' | + | At our [[http:// |
{{ rolemodel02.jpg? | {{ rolemodel02.jpg? | ||
- | The problem with the split objects model is that the message sender must know before hand which are the roles a receiver could take. In dynamic environments like mobile open networks, this acknowledgment is practically impossible and undesirable (due to the heterogeneity and autonomicity of the participants). Hence we have extended this model in such a way that the sender only have to include its own context information in the messages (and not a role). At the receiver side there will be a reasoning engine that will take as input the context of both sender and receiver, and will map this information to a role. We have called this entity the context-dependent role selector. For further information about this solution, we refer the interested reader to [ [[http://prog.vub.ac.be/ | + | The problem with the split objects model is that the message sender must know before hand which are the roles a receiver could take. In dynamic environments like mobile open networks, this acknowledgment is practically impossible and undesirable (due to the heterogeneity and autonomicity of the participants). Hence we have extended this model in such a way that the sender only have to include its own context information in the messages (and not a role). At the receiver side there will be a reasoning engine that will take as input the context of both sender and receiver, and will map this information to a role. We have called this entity the context-dependent role selector. For further information about this solution, we refer the interested reader to [ [[http://soft.vub.ac.be/ |
==== Ongoing and Future Work ==== | ==== Ongoing and Future Work ==== | ||
Line 43: | Line 44: | ||
==== Further Reading ==== | ==== Further Reading ==== | ||
- | **A Role-Based Implementation of Context-Dependent Communications Using Split Objects**. Jorge Vallejos, Peter Ebraert, Brecht Desmet. In " | + | **A Role-Based Implementation of Context-Dependent Communications Using Split Objects**. Jorge Vallejos, Peter Ebraert, Brecht Desmet. In " |
research/context.1151783485.txt.gz · Last modified: 2006/07/01 21:52 (external edit)