The smashHitCore ontology for GDPR-compliant sensor data sharing in smart cities

A.K. Kurteva, Tek Raj Chhetri, Amar Tauqeer, Rainer Hilscher, Anna Fensel*, Kevin Nagorny, Ana Correia, Albert Zilverberg, Stefan Schstakov, More Authors

*Corresponding author for this work

Research output: Contribution to journalArticleScientificpeer-review

40 Downloads (Pure)

Abstract

The adoption of the General Data Protection Regulation (GDPR) has resulted in a significant shift in how the data of European Union citizens is handled. A variety of data sharing challenges in scenarios such as smart cities have arisen, especially when attempting to semantically represent GDPR legal bases, such as consent, contracts and the data types and specific sources related to them. Most of the existing ontologies that model GDPR focus mainly on consent. In order to represent other GDPR bases, such as contracts, multiple ontologies need to be simultaneously reused and combined, which can result in inconsistent and conflicting knowledge representation. To address this challenge, we present the smashHitCore ontology. smashHitCore provides a unified and coherent model for both consent and contracts, as well as the sensor data and data processing associated with them. The ontology was developed in response to real-world sensor data sharing use cases in the insurance and smart city domains. The ontology has been successfully utilised to enable GDPR-complaint data sharing in a connected car for insurance use cases and in a city feedback system as part of a smart city use case.

Original languageEnglish
Article number6188
JournalSensors (Basel, Switzerland)
Volume23
Issue number13
DOIs
Publication statusPublished - 2023

Keywords

  • ontology
  • knowledge graph
  • consent
  • contract
  • sensor data
  • smart city
  • mobility
  • insurance
  • compliance
  • data sharing

Fingerprint

Dive into the research topics of 'The smashHitCore ontology for GDPR-compliant sensor data sharing in smart cities'. Together they form a unique fingerprint.

Cite this