Application Ontology Manager for Hydra

IST-2005-034891

Ján HreňoMartin SarnovskýPeter Kostelník

TU Košice

Content

• Project Overview

• Application Ontology Manager

• Device Ontology

• Use of Ontologies in HYDRA

HYDRA Project

• HYDRA IST-2005-034891 project (Net- worked Embedded System Middleware for Heterogeneous Physical Devices in a Distributed Architecture)

• Project vision:To create the most widely deployed middleware for intelligent networked embedded systems that will allow producers to develop cost-effective and innovative embedded applications for new and already existing devices.

• Project goal:To develop a middleware for Ambient-Intelligent devices based on a Service-oriented Architecture using Model Driven Architecture

HYDRA Outputs

• Output of the project

- Middleware

- SDK

- DDK

• Set of Managers

- Application Elements

- Device Elements

Application Ontology Manager

• Interface for using the Device Ontology and all the related models

• AOM maintains the run-time instances of the Hydra devices

• Semantic model based on Sesame framework

• Java, OSGi

Application Ontology Manager IDE

Device Ontology

• Device ontology presents basic high-level concepts describing the device related information

• Bottom up design• Based on most frequent functionality requirements it was extended with models

of:- Hardware/Software- Events provided by device- Energy profiles- QoS profiles- Security properties

• Static structures (HW, SW, Energy profiles)• Support of multiple annotations (QoS, Security)• Owl, Designed in TopBraid

(a part of) HYDRA Device Ontology

Use of ontologies in HYDRA

• Ontologies for

- Device developer

- Application developer

- Application

• The role of semantics

- Model-driven device editor

- Querying with expectations and requirements

- Semantic devices

- Application context awareness

Model Driven Device Editor

• Ontology administration tools included in the IDE

• Serves as ontology editor

• Role of semantics: model-driven editor

• 2 ontologies supporting annotation process were created:- Static taxonomy model- Annotation property model

• Form properties• Annotation properties

Querying with expectations and requirements

• Scenario: application needs to select most suitable device for playing the video files located in the living room

• Role of semantics: - Query and requirements clauses created using AOM IDE- Translated to SPARQL, evaluated by reasoner- Result retrieved in XML

• IDE supports 2 types of queries:- Retrieve requirements for devices matching query- Retrieve devices having services matching the query

Semantic Devices I

• Programming concept representing a logical aggregate of devices and services

• Implemented using:-Static mapping-Dynamic mapping

• Creation of semantic devices in DDK, IDE

• Application developer can focus on selection of devices – proxies and code generated automatically in DDK according to the configuration information attached

Application context awareness

• Used in creation of application domain model

• Used to specify some attributes - Locations (rooms, etc.)- Persons who use application- Devices belongs to specific locations owned by

concrete users

• Role of semantics:- Application domain models to be used are

integrated into ontologies- Enables to create queries containing application

context information

Application model example

Thank you for your attention