<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>An Ontology-based solution for XML query response enrichment</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Larbi Abdelmadjid</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Seddiki Bachir</string-name>
          <email>Html_bachir@yahoo.fr</email>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Larbi Ismail</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Merzoug A.</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Computer Science Department ENERGARID Laboratory UTM Bechar Algeria</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>Computer Science Department UDL SBA EEDIS Laboratory ENERGARID Laboratory UTM Bechar Algeria</institution>
        </aff>
      </contrib-group>
      <pub-date>
        <year>2017</year>
      </pub-date>
      <fpage>27</fpage>
      <lpage>31</lpage>
      <abstract>
        <p>- The use of ontologies for the enrichment (expansion) of the user query can be a solution to solve the problem of semantic variations, also for our case in the case where the object sought (drugà is not found, Of similar products by taking into account the contours related to the sick profile and the orientations of the physician and the semantics given by the pharmaceutical ontology. The ontologies offer resources in the form of semantic relations, they allow to extend the field To search for a query, which results in improved search results</p>
      </abstract>
      <kwd-group>
        <kwd>XML query</kwd>
        <kwd>response</kwd>
        <kwd>enrichment</kwd>
        <kwd>ontology</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>INTRODUCTION</title>
      <p>
        In recent years the database research domain has concentrated on XML (eXtensible Markup Language) as a flexible
hierarchical model suitable to represent huge amounts of data with no absolute and fixed schema, and a possibly irregular and
incomplete structure[
        <xref ref-type="bibr" rid="ref1">1</xref>
        ].
      </p>
      <p>Ultimately, it is expected that applications deployed on the Internet may lead reasoning using the knowledge stored on the web .
So, we aim to exploit the richness of relationships semantics provided by ontologies to adapt the user query and improve its
response</p>
      <p>II.</p>
    </sec>
    <sec id="sec-2">
      <title>THE ONTOLOGY CONCEPT</title>
      <p>
        Gruber [
        <xref ref-type="bibr" rid="ref2">2</xref>
        ] introduced the ontology notion as "an explicit specification of a onceptualization“, Borst. A. has slightly modify the
definition as follows: "an explicit and formal specification of a shared conceptualization“. Ontologies are used in many fields.
Areas identified in 1998 by Guarino are engineering knowledge, qualitative modeling, language engineering, databases design,
information retrieval, information extraction, management and the organization of knowledge. One of the biggest projects based
on the use of ontologies is add to a real web layer enabling knowledge research information at the semantic level and at the
simplest lexical and / or syntactical level.
      </p>
      <p>III.</p>
    </sec>
    <sec id="sec-3">
      <title>STATE OF ART There are many works including the ontology for treating the problem of including the semantic to the query [3], 27 Journées portes ouvertes sur la Faculté des Sciences Exactes JFSE 2017</title>
      <p>
        or for using semantic query over heterogeneous databases [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], or for answering queries using views[
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]
The entry of the proposed solution is a written query in SQL. A first processing consists in segmenting the
query and searching for the predicate value indicating the name of the drug. The following figure (see figure
1) shows the steps of the solution:
1. The system receives the patient's profile
2. Calculating the similarity of the concepts close to the drug derived from the ontology
3. Rewriting the patient's request
4. Searching for the rewritten query response by viewing the XML database
5. Display the response of the request.
&lt;owl:Class rdf:ID="Winery"/&gt;
&lt;owl:Class rdf:ID="Region"/&gt;
&lt;owl:Class rdf:ID="ConsumableThing"/&gt;
&lt;owl:Class rdf:ID="TexasThings"&gt;
&lt;owl:equivalentClass&gt;
&lt;owl:Restriction&gt;
      </p>
      <p>&lt;owl:onProperty
rdf:resource="#locatedIn" /&gt;</p>
      <p>&lt;owl:allValuesFrom
rdf:resource="#TexasRegion" /&gt;</p>
      <p>&lt;/owl:Restriction&gt;
&lt;/owl:equivalentClass&gt;
&lt;/owl:Class&gt;</p>
    </sec>
    <sec id="sec-4">
      <title>ILLUSTARTIVE EXAMPLE With the help of the editor Protege2000 we can create our ontology following the information given by the expert.</title>
      <p>The application supports multiple paths to get results in this example there are two voices:
1. Direct Request. In this case the application directly accesses the database.
2. Semantics Query: Accesses the ontology query, regenerate other queries against the XML database. In this case the resulting
query will closer to the original query domain and in the user selection.
It can be seen from the example that there is a correct result ie represents the execution of the main query directly on the basis of
XML data, and other results represent the query execution generated by the use of ontology.</p>
      <p>CONCLUSION
Our query expansion mechanism exploits the richness of relationships semantics provided by ontologies. Its adaptation to the user
by the through prototypicality (represented by the terminology, by weights on the terms) allows you to customize both the
extension query input the amount of results provided. Our solution allows us to customize the user query by patient requirements
and directed by the doctor on one hand and according to the concepts provided by the terminological ontology in the other
(validated by pharmaceutical expert) in order to have a comprehensive response. The first results are encouraging and it is
estimated the continuity of this project in the future.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          [1]
          <string-name>
            <surname>Mirjana</surname>
            <given-names>mazuran</given-names>
          </string-name>
          , Elisa quintarelli, and
          <article-title>Letizia tanca, “Data mining for xml query-answering support, ieee transactions on knowledge and data engineering”, 2011</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          [2]
          <string-name>
            <surname>Gruber</surname>
            ,
            <given-names>T. R. “</given-names>
          </string-name>
          <article-title>A translation approach to portable ontology specifications</article-title>
          .
          <source>Knowledge acquisition”</source>
          ,
          <volume>5</volume>
          , (
          <issue>2</issue>
          ):
          <fpage>199</fpage>
          -
          <lpage>220</lpage>
          ,
          <year>1993</year>
          .
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          [3]
          <string-name>
            <surname>Necib</surname>
          </string-name>
          .C.
          <article-title>B and Freytag</article-title>
          .JC. ,
          <source>“Semenatic Query Transformation Using ontologies”</source>
          .
          <source>2005</source>
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          [4]
          <string-name>
            <surname>Chen</surname>
          </string-name>
          , Donglin, “
          <article-title>An ontology-based system for semantic query over heterogeneous databases”, 2009</article-title>
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          [5]
          <string-name>
            <surname>Alon</surname>
            <given-names>Y. Levy</given-names>
          </string-name>
          ,”Answering Queries Using Views”,
          <year>2000</year>
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>