<?xml version="1.0" encoding="UTF-8"?>
<TEI xml:space="preserve" xmlns="http://www.tei-c.org/ns/1.0" 
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" 
xsi:schemaLocation="http://www.tei-c.org/ns/1.0 https://raw.githubusercontent.com/kermitt2/grobid/master/grobid-home/schemas/xsd/Grobid.xsd"
 xmlns:xlink="http://www.w3.org/1999/xlink">
	<teiHeader xml:lang="en">
		<fileDesc>
			<titleStmt>
				<title level="a" type="main">An Ontology-based solution for XML query response enrichment</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Larbi</forename><surname>Abdelmadjid</surname></persName>
							<affiliation key="aff0">
								<orgName type="department">Computer Science Department UDL</orgName>
								<orgName type="laboratory">SBA EEDIS Laboratory ENERGARID Laboratory UTM Bechar</orgName>
								<address>
									<country key="DZ">Algeria</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Seddiki</forename><surname>Bachir</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Computer Science Department ENERGARID</orgName>
								<orgName type="laboratory">Laboratory UTM Bechar</orgName>
								<address>
									<country key="DZ">Algeria</country>
								</address>
							</affiliation>
						</author>
						<author role="corresp">
							<persName><forename type="first">Larbi</forename><surname>Ismail</surname></persName>
							<email>larbismail@gmail.com</email>
							<affiliation key="aff1">
								<orgName type="department">Computer Science Department ENERGARID</orgName>
								<orgName type="laboratory">Laboratory UTM Bechar</orgName>
								<address>
									<country key="DZ">Algeria</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">An Ontology-based solution for XML query response enrichment</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">D07AC57A8F6DF26680C8242AED7BBDF9</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-25T07:15+0000">
					<desc>GROBID - A machine learning software for extracting information from scholarly documents</desc>
					<ref target="https://github.com/kermitt2/grobid"/>
				</application>
			</appInfo>
		</encodingDesc>
		<profileDesc>
			<textClass>
				<keywords>
					<term>XML query</term>
					<term>response</term>
					<term>enrichment</term>
					<term>ontology</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>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</head></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>INTRODUCTION</head><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 <ref type="bibr" target="#b0">[1]</ref>.</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 II.</p><p>THE ONTOLOGY CONCEPT Gruber <ref type="bibr" target="#b1">[2]</ref> 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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>III. STATE OF ART</head><p>There are many works including the ontology for treating the problem of including the semantic to the query [3],</p><p>Figure <ref type="figure">1</ref>. Semenatic Query Transformation Using ontologies or for using semantic query over heterogeneous databases <ref type="bibr" target="#b3">[4]</ref>, or for answering queries using views <ref type="bibr" target="#b4">[5]</ref> Figure <ref type="figure">2</ref>. An ontology-based system for semantic query Over heterogeneous databases</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>IV. DESIGN OF THE PROPOSED SOLUTION</head><p>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 <ref type="figure">1</ref>) shows the steps of the solution:</p><p>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.   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></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>VI. CONCLUSION</head><p>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></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 3 .</head><label>3</label><figDesc>Figure 3. Proposed solution</figDesc><graphic coords="3,134.65,154.55,326.15,244.45" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Figure 4 .</head><label>4</label><figDesc>Figure 4. Ontology Structure</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Figure 5 .</head><label>5</label><figDesc>Figure 5. Proposed solution</figDesc><graphic coords="4,182.80,106.25,227.45,222.65" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 7 .</head><label>7</label><figDesc>Figure 7. Proposed solution</figDesc><graphic coords="5,183.60,54.00,228.10,134.30" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="2,94.25,278.65,406.95,207.75" type="bitmap" /></figure>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<monogr>
		<author>
			<persName><forename type="first">Elisa</forename><surname>Mirjana Mazuran</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Letizia</forename><surname>Quintarelli</surname></persName>
		</author>
		<author>
			<persName><surname>Tanca</surname></persName>
		</author>
		<title level="m">Data mining for xml query-answering support, ieee transactions on knowledge and data engineering</title>
				<imprint>
			<date type="published" when="2011">2011</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A translation approach to portable ontology specifications</title>
		<author>
			<persName><forename type="first">T</forename><forename type="middle">R</forename><surname>Gruber</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Knowledge acquisition</title>
		<imprint>
			<biblScope unit="volume">5</biblScope>
			<biblScope unit="issue">2</biblScope>
			<biblScope unit="page" from="199" to="220" />
			<date type="published" when="1993">1993</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<monogr>
		<title level="m" type="main">Semenatic Query Transformation Using ontologies</title>
		<author>
			<persName><forename type="first">Freytag</forename><forename type="middle">C Jc</forename><surname>Necib</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<monogr>
		<title level="m" type="main">An ontology-based system for semantic query over heterogeneous databases</title>
		<author>
			<persName><forename type="first">Donglin</forename><surname>Chen</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2009">2009</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<monogr>
		<title level="m" type="main">Answering Queries Using Views</title>
		<author>
			<persName><forename type="first">Y</forename><surname>Alon</surname></persName>
		</author>
		<author>
			<persName><surname>Levy</surname></persName>
		</author>
		<imprint>
			<date type="published" when="2000">2000</date>
		</imprint>
	</monogr>
</biblStruct>

				</listBibl>
			</div>
		</back>
	</text>
</TEI>
