|
The MIDAS discovery model identifies three key entities involved in the discovery process:
Users are the principals that can provide and request services and interact by accessing services via heterogeneous devices.
Services are “black boxes” encapsulating physical/logical resources and providing the functions to operate on them.
All MIDAS entities have profiles that describe their characteristics.
To support user-centric discovery, MIDAS associates each user with a personal context space during each discovery session.
|
| |
|
MIDAS Profiles
|
|
A profile has a modular structure and it is composed of different parts:
- identification
- capabilities
- requirements
- binding
Each profile part can be split into two categories:
- static metadata, e.g., entity names, user interests, and service functions
- dynamic metadata, e.g., entity location and device battery status
Profiles are represented in OWL.
See the Profile Ontology [HyperOWL]
[HyperONT]
In the Case Studies section you can find an example of OWL service profiles.
|
| |
| |
|
MIDAS Context Model
|
|
MIDAS user contexts are logically structured into three different categories.
- The informative context characterizes the user in terms of personal characteristics, offered functionalities,
requirements, and device exploited to access services during a discovery session.
It includes:
- the user profile
- the device profile of the current access terminal
- the profiles of all services offered by the user
- The environmental context includes any useful information about the environment in which the user operates, e.g., date, time, temperature and humidity,
that may be measured by sensors in the surrounding environment.
- The interaction context describes past and current interactions with services.
|
| |
|
We are currently revising our context ontology. The latest context ontology will be online soon.
|
|
