27.03.2014 Views

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SEKE 2012 Proceedings - Knowledge Systems Institute

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

specialist intervention. The work at [10] classifies the conflicts<br />

during the integration of XML schemas and proposes<br />

a resolution mechanism using XQuery.<br />

The approach in [9] performs a division of mappings.<br />

This technique decomposes the document into sub-trees.<br />

Joint operations are represented by an undirected graph with<br />

acyclic handling algorithms to solve conflicts. An XML<br />

framework proposed in [13] defines data integration based<br />

on the overall schema, a set of XML data and a set of mappings.<br />

They define an identification function that aims at<br />

globally identifying nodes coming from different sources.<br />

To solve the problem of heterogeneity, this paper<br />

presents a ontology-based approach, which can be used to<br />

improve traditional techniques of XML mapping and storage<br />

into RDB. The purpose of using ontologies is to explicit<br />

the resource content regardless of how the information is<br />

structurally stored. This approach adds semantics to the<br />

XML files while reduces unneeded structural information<br />

to map the XML data to the relational format.<br />

3 Background<br />

To avoid submitting different XQuery queries, we propose<br />

to store XML data in a RDB. By mapping the XML<br />

structure to the relational model, only one SQL query is<br />

posed into the DB. To provide this solution, we need to define<br />

a set of transformation rules that map the XML structure<br />

to a collection of tables and columns.<br />

However, XML documents related to the same application<br />

domain may present different structures, making the<br />

mapping process more difficult. To overcome this issue, the<br />

X2Rel framework provides the following functionalities, as<br />

described in Figure 1:<br />

Figure 1. X2Rel framework architecture [6].<br />

The OntoGen and OntoRel components are finished and<br />

published works. The QMap module is an ongoing project.<br />

The focus of this paper is to present the XMap component,<br />

as described in the next section.<br />

4 The XMap Component<br />

The XMap component uses as input the original XML<br />

files, the global ontology generated by OntoGen and the relational<br />

schema created by OntoRel. In order to specify the<br />

concept equivalences between the XML documents, the ontology<br />

and the relational schema, our approch is based on<br />

a mapping document, as later detailed in Section 4.2. The<br />

insertion of XML data into the RDB is structured in five<br />

ascending levels, as described in Figure 2.<br />

• Integrate the XML files into a global schema, described<br />

by a OWL ontology. Provided by the OntoGen<br />

component, this module receives a set of XML files<br />

and produces the ontology (integrated schema) [7];<br />

• Translate the OWL ontology to a relational schema.<br />

Provided by the OntoRel component, this module receives<br />

the ontology and produces the relational schema<br />

(a SQL script with the create table statements) [6];<br />

• Map and insert the original XML files into the RDB.<br />

Provided by the XMap component, this module receives<br />

the XML files, the ontology and the relational<br />

schema and produces the SQL script with a set of insert<br />

statements;<br />

• And finally map the original XML queries into equivalent<br />

SQL statements. Provided by the QMap component,<br />

this module receives a XQuery statement and<br />

produces a corresponding SQL statement.<br />

Figure 2. The XMap Architecture<br />

The first level associates the input data. The integrated<br />

representation of such documents is responsible for speci-<br />

439

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!