10th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing

Research Article

Automatic Mapping Rules and OWL Ontology Extraction for the OBDA Ontop

Download987 downloads
  • @INPROCEEDINGS{10.4108/icst.collaboratecom.2014.257493,
        author={Fayez Khazalah and Zaki Malik and Abdelmounaam Rezgui},
        title={Automatic Mapping Rules and OWL Ontology Extraction for the OBDA Ontop},
        proceedings={10th IEEE International Conference on Collaborative Computing: Networking, Applications and Worksharing},
        publisher={IEEE},
        proceedings_a={COLLABORATECOM},
        year={2014},
        month={11},
        keywords={obda ontology extraction sparql relational database},
        doi={10.4108/icst.collaboratecom.2014.257493}
    }
    
  • Fayez Khazalah
    Zaki Malik
    Abdelmounaam Rezgui
    Year: 2014
    Automatic Mapping Rules and OWL Ontology Extraction for the OBDA Ontop
    COLLABORATECOM
    IEEE
    DOI: 10.4108/icst.collaboratecom.2014.257493
Fayez Khazalah1,*, Zaki Malik1, Abdelmounaam Rezgui2
  • 1: Wayne State University
  • 2: New Mexico Tech
*Contact email: fayez@wayne.edu

Abstract

Extracting Ontop mapping rules and OWL ontology manually from a relational schema is a tedious task. We present an automatic approach for extracting Ontop mappings and OWL ontology from an existing database schema. The end users can access the underlying data source through SPARQL queries. A SPARQL query is written according to the extracted ontology and the end user does not need to know about the underlying data source and its schema. The proposed approach takes into consideration the different relationships between entities of the database schema. Instead of extracting a flat ontology that is an exact copy of the database schema, it extracts a rich ontology. The extracted ontology can also be used as an intermediate between a domain ontology and the underlying database schema. The experiment results indicate that the extracted mappings and ontology are accurate. i.e., end users can query all data (using SPARQL) from the underlying database source in the same way as if they have written SQL queries.