Skip to main navigation Skip to search Skip to main content

On using conceptual data modeling for ontology engineering

  • Mustafa Jarrar*
  • , Jan Demey
  • , Robert Meersman
  • *Corresponding author for this work
  • Vrije Universiteit Brussel

Research output: Contribution to journalArticlepeer-review

Abstract

This paper tackles two main disparities between conceptual data schemes and ontologies, which should be taken into account when (re)using conceptual data modeling techniques for building ontologies. Firstly, conceptual schemes are intended to be used during design phases and not at the run-time of applications, while ontologies are typically used and accessed at run-time. To handle this first difference, we define a conceptual markup language (ORM-ML) that allows to represent ORM conceptual diagrams in an open, textual syntax, so that ORM schemes can be shared, exchanged, and processed at the run-time of autonomous applications. Secondly, unlike ontologies that are supposed to hold application-independent domain knowledge, conceptual schemes were developed only for the use of an enterprise application(s), i.e. "in-house" usage. Hence, we present an ontology engineering-framework that enables reusing conceptual modeling approaches in modeling and representing ontologies. In this approach we prevent application-specific knowledge to enter or to be mixed with domain knowledge. To end, we present DogmaModeler: an ontology-engineering tool that implements the ideas presented in the paper.

Original languageEnglish
Pages (from-to)185-207
Number of pages23
JournalLecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics)
Volume2800
DOIs
Publication statusPublished - 2003
Externally publishedYes

Keywords

  • Conceptual data modeling
  • Context
  • DOGMA
  • DogmaModeler
  • Ontology
  • Ontology tools
  • ORM
  • ORM-ML
  • Reusability

Fingerprint

Dive into the research topics of 'On using conceptual data modeling for ontology engineering'. Together they form a unique fingerprint.

Cite this