From Databases to Ontologies

2009 ◽  
pp. 2360-2383
Author(s):  
Guntis Barzdins ◽  
Janis Barzdins ◽  
Karlis Cerans

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.

Author(s):  
Guntis Barzdins

This chapter introduces the UML profile for OWL as an essential instrument for bridging the gap between the legacy relational databases and OWL ontologies. We address one of the long-standing relational database design problems where initial conceptual model (a semantically clear domain conceptualization ontology) gets “lost” during conversion into the normalized database schema. The problem is that such “loss” makes database inaccessible for direct query by domain experts familiar with the conceptual model only. This problem can be avoided by exporting the database into RDF according to the original conceptual model (OWL ontology) and formulating semantically clear queries in SPARQL over the RDF database. Through a detailed example we show how UML/OWL profile is facilitating this new and promising approach.


Author(s):  
Guntis Bārzdiņš ◽  
Sergejs Rikačovs ◽  
Marta Veilande ◽  
Mārtiņš Zviedris

Ontological Re-engineering of Medical Databases This paper describes data export from multiple medical databases (relational databases) into a single shared Medical Data Warehouse (RDF database structured according to an integrated OWL ontology). The exported data is conveniently accessible via SPARQL or via graphical query language ViziQuer based on UML profile for OWL. The approach is illustrated on one of Latvian Medical databases - Injury Register.


Author(s):  
Morad Hajji ◽  
Mohammed Qbadou ◽  
Khalifa Mansouri

Ontologies are spreading more and more in the field of information technologies as a privileged solution allowing the formalization of knowledge. The theoretical model of ontologies is most promising. They are increasingly ubiquitous given the benefits they present. Despite the proliferation of research proposing approaches dedicated to the design of a database from an ontology, the tools to design a database from an ontology are rare or inaccessible. Thus, in this contribution, we present our approach for the development of an Eclipse Plug-in, in order to automatically generate a conceptual model of a relational database from an ontology. To evaluate the usefulness of our approach, we used our resulting Eclipse Plug-in to automatically generate a conceptual model of a relational database from an ontology, customize it, and automatically generate the corresponding SQL script for Data Definition. The results of this experiment showed that our Plug-in constitutes a concretization of our approach and a means of automatic translation from the ontological model to the relational model.


2018 ◽  
Vol 4 (1) ◽  
pp. 57-63
Author(s):  
Anatoliy Yuferov

The article considers the issues of converting the ENDF format systems of constants to relational databases. This conversion can become one of the tools facilitating the development and operation of factual information, techniques and algorithms in the field of nuclear data and, therefore, increasing the efficiency of the corresponding computational codes. The work briefly examines an infological model of ENDF libraries. The possible structure of tables of the corresponding relational database is described. The proposed database schema and the form of tables take into account the presence of both single and multiple properties of the isotopes under consideration. Consideration is given to the difference in organizational requirements for transferring constants from relational tables to programs and performing a visual analysis of data in tables by a physicist-evaluator. The conversion algorithms and results are described for the ROSFOND-A and ENDF/B-VII.1 libraries. It is shown that performing calculations directly in the DBMS environment has its advantages in terms of simplifying programming and eliminating the need to solve a number of problems on data verification and validation. Possible approaches are indicated to ensure operation of inherited software together with nuclear data libraries in the relational format. Some terminological refinements are proposed to facilitate constructing an infological model for ENDF format. The conversion programs and the ENDF/B-VII.1 library in the relational format are available on a public site.


10.28945/3199 ◽  
2008 ◽  
Author(s):  
Milos Bogdanovic ◽  
Aleksandar Stanimirovic ◽  
Nikola Davidovic ◽  
Leonid Stoimenov

Most universities where students study informational technologies and computer science have an introductory course dealing with the development and design of databases. These courses often include usage of database design tools. In this paper, the #EER tool is presented, the task of which is to make the process of relational databases design easier for the students and partially automatize it. The tool evolved due to the experience in using similar tools for educational purposes. It enables fast and efficient development of the relational database conceptual model and its automatized compilation into a relational model and further to data definition language (DDL) commands. #EER tool is based on the extended entity-relationship (EER) model for conceptual modeling of relational databases. Modular architecture of the tool, the development of which is based on the usage of the design patterns, along with the benefits that its usage brings, is also presented.


Author(s):  
Mirella M. Moro ◽  
Lipyeow Lim ◽  
Yuan-Chi Chang

It is well known that XML has been widely adopted for its flexible and self-describing nature. However, relational data will continue to co-exist with XML for several different reasons one of which is the high cost of transferring everything to XML. In this context, data designers face the problem of modeling both relational and XML data within an integrated environment. This chapter highlights important questions on hybrid XML-relational database design and discusses use cases, requirements, and deficiencies in existing design methodologies especially in the light of data and schema evolution. The authors’ analysis results in several design guidelines and a series of challenges to be addressed by future research.


2021 ◽  
Vol 9 (7) ◽  
pp. 71-78
Author(s):  
Ian Adamson

With the extensive use of relational databases in the business environment there is a need to reduce database complexity in order to avoid data inconsistency and redundancy, which can provide a company with unreliable and/or meaningless data and information. The use of the REA Data Model in database design can significantly help with this problem.  The model can eliminate the need for unnecessary data artifacts which should only be generated by the system when needed. This paper also addresses the need for a Relational Database Complexity Metric. A simple and easy to understand metric is presented.


2021 ◽  
Vol 12 (4) ◽  
pp. 1-11
Author(s):  
Halima E. Samra ◽  
Alice S. Li ◽  
Ben Soh ◽  
Mohammed A. AlZain

In general, databases provide a single comprehensive view suitable for analysis and relevant information for a variety of organizational purposes. The intent of this paper is to review the contemporary database design in terms of data modelling, process modelling, relational databases, and data storage. The review indicates the contemporary relational database architecture provides numerous advantages such as high consistency and availability. However, it is not suitable for big data because its performance decreases as the data grows and faces scalability constraints as it is impossible to scale horizontally, and its vertical growth is limited. An implication here is that big data requires more than a relational database and the traditional SQL.


Sign in / Sign up

Export Citation Format

Share Document