{'fraction_non_alphanumeric': 0.024906600249066, 'fraction_numerical': 0.0, 'mean_word_length': 5.586065573770492, 'pattern_counts': {'":': 0, '<': 0, '<?xml version=': 0, '>': 0, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 1, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
A design methodology of ontology based database applications

Recently, ontologies emerge in various domains and different communities. For instance, in the database area, they are used to facilitate data exchange and integration, in the Semantic Web field, to describe terms, retrieve information and interconnect Web services. Several ontology languages and formalisms are given (OWL, PLIB, etc.). Due to the ontology evolution, various applications manipulate a huge amount of ontological data (data referencing ontologies). Consequently, they cannot fit in the main memory. To offer efficient storage and querying mechanisms of these data, academicians and industrials proposed database solutions storing in the same repository data and the ontology describing their senses. Such database is called ontology-based databases (OBDB). Despite this trend, no design methodology adapted to OBDB exists contrary to traditional databases, where two main methodologies inspired from: Codd-Armstrong and Chen research efforts are proposed. Developing a design methodology for OBDB constitutes a crucial challenge for the success of OBDB applications. Similarities between conceptual models and ontologies recently identified motivate us to propose an OBDB design methodology inspired from the existing ones. To do so, we first describe in details these similarities and differences. Secondly, we propose an ontology-driven methodology to derive a normalized logical schema of a database from domain ontology whose each class contains a set of FDs. Finally, a prototype implementing our methodology is presented.