An Integration-Oriented Ontology to Govern Evolution in Big Data Ecosystems

Big Data architectures allow to flexibly store and process heterogeneous data, from multiple sources, in their original format. The structure of those data, commonly supplied by means of REST APIs, is continuously evolving. Thus data analysts need to adapt their analytical processes after each API release. This gets more challenging when performing an integrated or historical analysis. To cope with such complexity, in this paper, we present the Big Data Integration ontology, the core construct to govern the data integration process under schema evolution by systematically annotating it with information regarding the schema of the sources. We present a query rewriting algorithm that, using the annotated ontology, converts queries posed over the ontology to queries over the sources. To cope with syntactic evolution in the sources, we present an algorithm that semi-automatically adapts the ontology upon new releases. This guarantees ontology-mediated queries to correctly retrieve data from the most recent schema version as well as correctness in historical queries. A functional and performance evaluation on real-world APIs is performed to validate our approach.Comment: Preprint submitted to Information Systems. 35 page

Experience feedback committee in emergency medicine: a tool for security management

International audienc

Electronic Medication Regimen Complexity Index at admission and complications during hospitalization in medical wards: a tool to improve quality of care?

International audienc

Assessment of the contribution of morbidity and mortality conferences to quality and safety improvement: a survey of participants’ perceptions

International audienc

Information included in the meeting minutes of the 20 EFCs (<i>n</i> = 160 reports).

<p>Information included in the meeting minutes of the 20 EFCs (<i>n</i> = 160 reports).</p

Characteristics of the actions adopted by the committee (<i>n</i> = 206).

<p>Characteristics of the actions adopted by the committee (<i>n</i> = 206).</p

Characteristics of event reports reviewed by EFCs (<i>n</i> = 1707).

<p>Characteristics of event reports reviewed by EFCs (<i>n</i> = 1707).</p

Characteristics of analysis reports reported to committee (<i>n</i> = 91).

<p>Characteristics of analysis reports reported to committee (<i>n</i> = 91).</p

Comparison of characteristics of EFCs according to the number of actions decided in the year (< 5 versus ≥ 5).

<p>Comparison of characteristics of EFCs according to the number of actions decided in the year (< 5 versus ≥ 5).</p