This folder contains the ontology data related to the paper "Context-aware query derivation for IoT data streams with DIVIDE enabling privacy by design", which is published in the Special Issue on Semantic Web Meets Health Data Management of the Semantic Web Journal.
In the paper, DIVIDE is explained through a running homecare monitoring example. This folder contains all files of the Activity Recognition ontology that is being used for this example.
The Activity Recognition ontology contains two parts:
- A snapshot of the DAHCC ontology. This ontology contains definitions to perform Data Analytics in Health and Connected Care. More information about the DAHCC ontology is available via this website. The files used for this paper are:
- The general ontology files included in the
Ontology
folder of the DAHCC GitHub repo. Note that the current repository contains the RDF/Turtle representation of these ontology files. - The TBox definitions extracted from the
_Homelab.owl
and_HomelabWearable.owl
files in theinstantiated_examples
folder of the DAHCC GitHub repo (in RDF/Turtle format). - All imports of the
imports
folder of the DAHCC GitHub repo that are being (indirectly) imported by any of the other included DAHCC files.
- The general ontology files included in the
- The additional ontology file
KBActivityRecognition.ttl
that represents all extra definitions related to the knowledge-driven activity recognition.
All files in this folder, except for the files in the ontology-no-imports
subfolder, together represent the Activity Recognition ontology.
This ontology is also used for the paper's evaluations.
The ontology-no-imports
subfolder contains an identical copy of the files of the Activity Recognition ontology, with one change: all import statements in the ontology files are removed. This is a small change required to load them in the EYE reasoner. Hence, these files are the ones that are actually used when loading the ontology in DIVIDE.
The main contact person directly involved with this research is Mathias De Brouwer. In case of any remarks or questions, you can email [email protected] or create a GitHub issue.