Ontology-Based Data Access and Integration

An ontology-based data integration (OBDI) system is an information management system consisting of three components: an ontology, a set of data sources, and the mapping between the two. The ontology is a conceptual, formal description of the domain of interest to a given organization (or a community of users), expressed in terms of relevant concepts, attributes of concepts, relationships between concepts, and logical assertions characterizing the domain knowledge. The data sources are the repositories accessible by the organization where data concerning the domain are stored. In the general case, such repositories are numerous, heterogeneous, each one managed and maintained independently from the others. The mapping is a precise specification of the correspondence between the data contained in the data sources and the elements of the ontology. The main purpose of an OBDI system is to allow information consumers to query the data using the elements in the ontology as predicates. In the special case where the organization manages a single data source, the term ontology-based data access (ODBA) system is used

INCMap: A Journey towards ontology-based data integration

Ontology-based data integration (OBDI) allows users to federate over heterogeneous data sources using a semantic rich conceptual data model. An important challenge in ODBI is the curation of mappings between the data sources and the global ontology. In the last years, we have built IncMap, a system to semi-automatically create mappings between relational data sources and a global ontology. IncMap has since been put into practice, both for academic and in industrial applications. Based on the experience of the last years, we have extended the original version of IncMap in several dimensions to enhance the mapping quality: (1) IncMap can detect and leverage semantic-rich patterns in the relational data sources such as inheritance for the mapping creation. (2) IncMap is able to leverage reasoning rules in the ontology to overcome structural differences from the relational data sources. (3) IncMap now includes a fully automatic mode that is often necessary to bootstrap mappings for a new data source. Our experimental evaluation shows that the new version of IncMap outperforms its previous version as well as other state-of-the-art systems

Использование онтологий для построения семантических запросов в реляционных базах данных

На сьогодні всесвітня павутина є найбільшим сховищем інформації. Проте для використання цієї інформації потрібна людина. Мета Семантичного Вебу — представити інформацію у вигляді, придатному для машинної обробки. Він забезпечує можливість спільного доступу до даних, а також їх повторного використання. Велика частина інформації у всесвітній павутині зберігається в реляційних базах даних. Семантичний Веб не може їх використовувати безпосередньо, але реляційні бази даних можуть бути використані для побудови онтологій. Ця ідея привернула увагу багатьох дослідників, які запропонували алгоритми та відповідні програмні рішення для автоматичного або напівавтоматичного вилучення структурованої синтаксичної інформації. У цій роботі досліджено існуючі рішення, показано різні підходи до формалізації логічної моделі реляційної бази даних і перетворення цієї моделі в OWL (мова Семантичного Вебу). Відзначено проблеми розглянутих рішень, а також виділено аспекти, які необхідно враховувати в майбутньому.Nowadays, the Web is the biggest existing information repository. However, to operate with its information human action is required, but the Semantic Web aims to change this. It provides a common framework that allows data to be shared and reused across application, allowing more uses than the traditional Web. Most of the information on the Web is stored in relational databases and the Semantic Web cannot use such databases. Relational databases can be used to construct ontology as the core of the Semantic Web. This task has attracted the interest of many researches, which have made algorithms (wrappers) able to extract structured syntactic information in an automatic or semi-automatic way. At our work we drew experience from those works. We showed different approaches of formalization of a logic model of relational databases, and a transformation of that model into OWL, a Semantic Web language. We closed this paper by mentioning some problems that have only been lightly touched by database to ontology mapping solutions as well as some aspects that need to be considered by future approaches.На сегодняшний день всемирная паутина является крупнейшим хранилищем информации. Тем не менее для использования этой информации необходим человек. Цель Семантического Веба — представить информацию в виде пригодном для машинной обработки. Он обеспечивает возможность совместного доступа к данным, а также их повторного использования. Большая часть информации во всемирной паутине хранится в реляционных базах данных. Семантический Веб не может их использовать непосредственно, но реляционные базы данных могут быть применены для построения онтологий. Эта идея привлекла интерес многих исследователей, которые предложили алгоритмы и соответствующие программные решения для автоматического или полуавтоматического извлечения структурированной синтаксической информации. В этой работе исследованы существующие решения, показаны различные подходы к формализации логической модели реляционной базы данных и преобразования этой модели в OWL (язык Семантического Веба). Отмечены проблемы рассмотренных решений, а также выделены аспекты, которые необходимо учитывать в будущем

RODI: Benchmarking Relational-to-Ontology Mapping Generation Quality

Accessing and utilizing enterprise or Web data that is scattered across multiple data sources is an important task for both applications and users. Ontology-based data integration, where an ontology mediates between the raw data and its consumers, is a promising approach to facilitate such scenarios. This approach crucially relies on useful mappings to relate the ontology and the data, the latter being typically stored in relational databases. A number of systems to support the construction of such mappings have recently been developed. A generic and effective benchmark for reliable and comparable evaluation of the practical utility of such systems would make an important contribution to the development of ontology-based data integration systems and their application in practice. We have proposed such a benchmark, called RODI. In this paper, we present a new version of RODI, which significantly extends our previous benchmark, and we evaluate various systems with it. RODI includes test scenarios from the domains of scientific conferences, geographical data, and oil and gas exploration. Scenarios are constituted of databases, ontologies, and queries to test expected results. Systems that compute relational-to-ontology mappings can be evaluated using RODI by checking how well they can handle various features of relational schemas and ontologies, and how well the computed mappings work for query answering. Using RODI, we conducted a comprehensive evaluation of seven systems

SNOMED CT standard ontology based on the ontology for general medical science

Background: Systematized Nomenclature of Medicine—Clinical Terms (SNOMED CT, hereafter abbreviated SCT) is acomprehensive medical terminology used for standardizing the storage, retrieval, and exchange of electronic healthdata. Some efforts have been made to capture the contents of SCT as Web Ontology Language (OWL), but theseefforts have been hampered by the size and complexity of SCT. Method: Our proposal here is to develop an upper-level ontology and to use it as the basis for defining the termsin SCT in a way that will support quality assurance of SCT, for example, by allowing consistency checks ofdefinitions and the identification and elimination of redundancies in the SCT vocabulary. Our proposed upper-levelSCT ontology (SCTO) is based on the Ontology for General Medical Science (OGMS). Results: The SCTO is implemented in OWL 2, to support automatic inference and consistency checking. Theapproach will allow integration of SCT data with data annotated using Open Biomedical Ontologies (OBO) Foundryontologies, since the use of OGMS will ensure consistency with the Basic Formal Ontology, which is the top-levelontology of the OBO Foundry. Currently, the SCTO contains 304 classes, 28 properties, 2400 axioms, and 1555annotations. It is publicly available through the bioportal athttp://bioportal.bioontology.org/ontologies/SCTO/. Conclusion: The resulting ontology can enhance the semantics of clinical decision support systems and semanticinteroperability among distributed electronic health records. In addition, the populated ontology can be used forthe automation of mobile health applications

ANSWERING GEOSPARQL QUERIES OVER RELATIONAL DATA

In this paper we present the system Ontop-spatial that is able to answer GeoSPARQL queries on top of geospatial relational databases, performing on-the-fly GeoSPARQL-to-SQL translation using ontologies and mappings. GeoSPARQL is a geospatial extension of the query language SPARQL standardized by OGC for querying geospatial RDF data. Our approach goes beyond relational databases and covers all data that can have a relational structure even at the logical level. Our purpose is to enable GeoSPARQL querying on-the-fly integrating multiple geospatial sources, without converting and materializing original data as RDF and then storing them in a triple store. This approach is more suitable in the cases where original datasets are stored in large relational databases (or generally in files with relational structure) and/or get frequently updated

Ontology-Based Resolution of Cloud Data Lock-in Problem

Cloud computing is nowadays becoming a popular paradigm for the provision of computing infrastructure that enables organizations to achieve financial savings. On the other hand, there are some known obstacles, among which vendor lock-in stands out. Furthermore, due to missing standards and heterogeneities of cloud storage systems, the migration of data to alternative cloud providers is expensive and time-consuming. We propose an approach based on Semantic Web services and AI planning to tackle cloud vendor data lock-in problem. To complete the mentioned task, data structures and data type mapping rules between different types of cloud storage systems are defined. The migration of data among different providers of platform as a service is presented in order to prove the practical applicability of the proposed approach. Additionally, this concept was also applied to software as a service model of cloud computing to perform one-shot data migration from Zoho CRM to Salesforce CRM