<?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">Ontology Refinement Using Implicit User Preferences: A case study in cultural tourism domain</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Krich</forename><surname>Nasingkun</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Japan Advance Institute of Science and Technology</orgName>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="department">Sirinthorn International Institute of Technology</orgName>
								<orgName type="institution">Thammasart University</orgName>
								<address>
									<country key="TH">Thailand</country>
								</address>
							</affiliation>
							<affiliation key="aff2">
								<orgName type="department">Language and Semantic Technology Laboratory National Electronics and Computer Technology Center (NECTEC)</orgName>
								<address>
									<settlement>Pathumthani</settlement>
									<country key="TH">Thailand</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Mitsuru</forename><surname>Ikeda</surname></persName>
							<email>ikeda@jaist.ac.jp</email>
							<affiliation key="aff0">
								<orgName type="institution">Japan Advance Institute of Science and Technology</orgName>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Boontawee</forename><surname>Suntisrivaraporn</surname></persName>
							<affiliation key="aff1">
								<orgName type="department">Sirinthorn International Institute of Technology</orgName>
								<orgName type="institution">Thammasart University</orgName>
								<address>
									<country key="TH">Thailand</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Thepchai</forename><surname>Supnithi</surname></persName>
							<email>thepchai@nectec.or.th</email>
							<affiliation key="aff2">
								<orgName type="department">Language and Semantic Technology Laboratory National Electronics and Computer Technology Center (NECTEC)</orgName>
								<address>
									<settlement>Pathumthani</settlement>
									<country key="TH">Thailand</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Ontology Refinement Using Implicit User Preferences: A case study in cultural tourism domain</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">0A99AE1615B9A0C08E2C47B3E6DF0A74</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-23T23:30+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>Ontology refinement</term>
					<term>implicit knowledge</term>
					<term>cultural tourism</term>
				</keywords>
			</textClass>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>Recommender systems employ static knowledge elicited from experts, causing high cost of maintenance for making the knowledge up-to-date. The contribution of this paper is the proposed method to collect potential concepts from users, in order to assist experts or development of automatic approaches to refining an ontology. Implicit knowledge induced from the users, which is much less expensive to maintain ontology. Ultimately, it offers finergrained, more effective recommendations that match expectation of the users.</p></div>
			</abstract>
		</profileDesc>
	</teiHeader>
	<text xml:lang="en">
		<body>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="1">Introduction</head><p>Cultural tourism (or culture tourism) is a subset of tourism concerned with a country or region's culture, specifically the lifestyle of the people in those geographical areas, the history of those people, their art, architecture, religion(s), and other elements that helped shape their way of life. The web site of Thai Cultural Knowledge Center <ref type="bibr">[1]</ref> is a cultural archive project, implemented through close cooperation between National Electronics and Computer Technology Center and Ministry of Culture under the 2011 Memorandum of Understanding (MOU). The first phase of the project was to develop a technology platform for acquisition, digitization, documentation, preservation, security, and management of complex data in the cultural domain. The second phase focused on integrating data from different sources using different storage technologies, and providing a unified view of the collected data. From November 2010 to June 2013, the database contains more than 100,000 records, linking relevant persons, organizations, places, and artifacts.</p><p>It is quite difficult to find recommendations for tourists based on the cultural aspect, since there is abundant knowledge and data. Fig. <ref type="figure">1</ref> shows an overview of the recommender system framework for cultural tourism. The cultural portal is the central database storing cultural data obtained by data collection module which is done by officer in Ministry of Culture. To utilize the cultural database, an expert may constructs an ontology based on his/her expertise. Relation extraction is a key process for eliciting knowledge in terms of ontology's instances, concepts, and relations from cultural database. Relation templates which are done in the ontology construction process enable us to extract semantic relation among a focused set of entities in cultural archive <ref type="bibr" target="#b2">[2]</ref>, which is constrained by relation types and their arguments. In this paper, we focus on the ontology refinement process, to improve and clarify existing knowledge. The better understanding provide the better alternatives for recommendation. User constrains (from user profile) and selection algorithm are deployed to create the final recommendation output.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 1. Cultural tourism recommendation framework</head><p>The rest of paper is organized as follows. Section 2 explains our related work. Section 3 presents the proposed method and details of our algorithm. Section 4 illustrates usage scenarios of recommendation system that employ the proposed method. Section 5 shows the discussion of this work. Section 6 provides conclusion and some future development directions.</p><p>Ontology refinement can be categorized into two approaches: semi-automatic and automatic approaches. In the semi-automatic approach, the refinement algorithm aims to help the knowledge engineer find relevant information. This can be done by nominating the terms to reduce the effort of looking for new relevant pieces of information. An example of a technique could be the exploration of statistically significant terms. Term co-occurrences are exploited to identify related terms based on statistical means <ref type="bibr" target="#b3">[3]</ref><ref type="bibr" target="#b4">[4]</ref>. The automatic approach, on the other hand, does not require a knowledge engineer during ontology refinement but require some principled way to drive the integration of new knowledge in the ontology. These automatic methods rely either on heuristics (like some quality measure), or on information extraction from unstructured source <ref type="bibr" target="#b5">[5]</ref>; for example, the expansion of WordNet to the tourism domain <ref type="bibr" target="#b6">[6]</ref>. In the biomedical domain, an automated method to refine the Gene Ontology is proposed <ref type="bibr" target="#b7">[7]</ref>. The idea is to extract rules based on term variations for automatic term expansion and validate them with the literature. By using IR techniques, the ontology query model identifies missing knowledge in the ontology relevant to IR tasks. An automatic method to revise the ontology accordingly is proposed for generating better queries <ref type="bibr" target="#b8">[8]</ref>. Many applied NLP techniques to this approach, but, to the best of our knowledge, none of them concentrate on interests from system users. In our work, we focus on semi-automatic technique to collect a potential concepts using evident from user interest, in order to assist ontology engineer in culture domain.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Ontology Refinement Framework</head><p>Based on the definition, ontology refinement is a method to improve existing knowledge to more clarify in specific domain. In our work, we proposed the ontology refinement process based-on user interest, to collect the potential concepts which may use to refine ontology in the future. Cultural tourism domain is used to demonstrate an idea of our approach.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.1">Resource Description Framework</head><p>The Resource Description Framework (RDF) <ref type="bibr" target="#b9">[9]</ref> is a framework for expressing information about resources. Resources can be anything, including documents, people, physical objects, and abstract concepts. RDF is intended for situations in which information on the web needs to be processed by applications, rather than being only displayed to people. RDF provides a common framework for expressing this information so it can be exchange between applications without loss of meaning. Since it is a common framework, application designers can leverage the availability of common RDF parsers and processing tools. The ability to exchange information between different applications means that the information may be made available to applications other than those for which it was originally created. RDF allows us to make state-ments about resources. The format of these statements is simple. A statement always has the following structure:</p><formula xml:id="formula_0">&lt;subject&gt; &lt;predicate&gt; &lt;object&gt;</formula><p>An RDF statement expresses a relationship between two resources. The subject and the object represent the two resources being related; the predicate represents the nature of their relationship. The relationship is phrased in a directional way (from subject to object) and is called in RDF a property. Because RDF statements consist of three elements they are called triples. Fig. <ref type="figure" target="#fig_0">2</ref> show examples of RDF triples (informally expressed in pseudo code). In the example above, Bob is the subject of four triples, and the Mona Lisa is the subject of one and the object of two triples. This ability to have the same resource be in the subject position of one triple and the object position of another makes it possible to find connections between triples, which is an important part of RDF's power</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3.2">Cultural Tourism Ontology</head><p>Cultural tourist has their specific character, their interest not only limit to target destinations/activities itself. But they may gain knowledge in some more aspect around cultural resources. Existing ontology-based recommendation approach has a deep investigate on "is a" and "part of" relations, meanwhile the similarity measurement among instances of the same or similar concepts are well investigated. As shown in Fig. <ref type="figure" target="#fig_1">3</ref>, tourist make interest in "Wat Chong Kham" and "Grand Palace". Using "is a" and "part of" from existing ontology approaches, recommender system may recommend another temple or palaces that related to user favorites. Limitation of existing approached cannot capture interest that may related to resources in other aspect. For example, "King", "Art", "Minority", "Religious" or "Traditional and Ritual" will never been concern.  1 show an example relations that we used to model cultural ontology in our approached. Relations are defined to capture cultural aspects of cultural resources. By this approached, cultural aspect of user interest will be analyses in order to recommend the most related on some aspect. Fig. <ref type="figure">4</ref> show a partial of cultural ontology that we will use to explain algorithm in next section. Relation "founded by" and "is a" are a key relations that we will use to identify potential concepts related to user interested. The output of our approached can collected to assist ontology engineer, to refine ontology according to real interested of users.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Table1. Example Relations in Cultural Ontology</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Relations</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.3</head><p>Ontology Refinement Process</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 5. Ontology Refinement Process</head><p>As showed in Fig. <ref type="figure">5</ref>, Domain ontology and user favorite resources are used as an input of Relation Analysis Process. By using evident from user favorite, the related concepts and instances of user favorites are analyzed. Potential concepts will be nominate by Potential Concept Analysis Process, all relations of related concepts are take into account. Possible concepts that may clarify user interest are formulated. However, only the concepts that share common relation are nominated as a potential new knowledge. In Personalized Ontology Process, new knowledge are collect in order to assist expert to update existing domain ontology in future.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>3.4</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Ontology Refinement Algorithm</head><p>In this section, we explain the pseudo code for ontology refinement. The input of our framework is a set of users favorite's resources that input directly from users. Let O be an ontology that modeling by RDF statements, F = {f1, f2, f3… fn} be a set of users' favorite instances. First, we look at each instance to find identify domain concept of relation DC and the related instances RI. Next, we create a temporary concept that contain only a related instances in each relations, then list of concept that related instances belong to set of relation concept RC. the intersection operation is used to identify the unique relation that share common between the same domain concept and range concept. Finally the set of relation Result which store the list of relation of concepts are return as an output. The output of our approach is a personalized extended ontology. TempC  {G | G is a temporary concept that has only RI as a member} 7:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Algorithm 1: Refinement Algorithm</head><p>RC  {G | r (f, g) for some role r that g is an instance of concept G} 8:</p><p>Relation  {r (DC, RC) and r (DC, TempC) | r (f, g) for some role r} 9:</p><p>if The output from our technique capture the real interest concepts based-on existing ontology structure in the user point of view. Ontology engineer can use this technique to collect the realistic concepts to assist the ontology refinement process.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">Recommendation Scenarios</head><p>This section shows the usage scenarios recommendation system in Cultural recommendation framework. Existing ontology has the structure as shown in Fig. <ref type="figure">4</ref>, tourist identify "Wat Arun" as his favorite place. By our approach, all related instances and concepts will be investigate. The unique character of user interest will be identify. Finally, the potential knowledge are nominate as an extended of personalized ontology.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Fig. 6. Example Ontology Extension Generated by the Proposed Technique</head><p>Fig. <ref type="figure">6</ref> show an example user favorite instances and existing ontology structure. The output of our approached is an extended knowledge, Concept "Temple founded by King", "Temple founded by Rama II" and "Rama II" are nominated to be the part of the personalized ontology.</p><p>In the recommendation, instead of interpret the interest to temple according to initial ontology. The emerging of new concept 'Temple founded by King' lead the interpretation of user interest into a specific group of temple. Instead of 40,717 temples in Thailand, we may scope the number of recommendation using our approach into 217 items. When we collect the list of concepts from many users, ontology engineer will use it to analyze and refine existing domain ontology in the future work.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Discussion</head><p>In our approach, induced related concepts require instances as supporting evidence. For example, if we have instance of temples as a member of user favorites, it is possible to discover sub concepts of the temples. The shared commons among different types of concepts (ex. Festival, Palace, Temple) without instances, cannot infer the new knowledge. Although we can identify the links among items, the support evidence (instant of concept) still required to prove the intention from users. For example, our technique cannot infer concept 'King founded Temple' from favorite instance of Palace or Buddhism_Related_Festival concept (even we have some relation between this two concepts).</p><p>Without this approached, existing taxonomy of ontology can produce the similar outputs (for example Temple founded by King). However, that concept may not be interested (never be used) by real users. In addition, it will make the over size of ontology problem. In contrast, expert will decide to approve/ignore the inferred knowledge in our approached.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusion and Future work</head><p>We have presented an ontology refinement approach in cultural tourism domain using implicit knowledge induction from users' favorite resources. New potential concepts based-on user interest are discover to improving and clarifying the existing knowledge.</p><p>Some future work includes an implementation of a recommendation framework for cultural tourism and evaluation of the recommendation result. In addition, the ontology refining approaches can be applied to other specific user-oriented domains.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Fig. 2 .</head><label>2</label><figDesc>Fig. 2. Example RDF statement (Source: RDF 1.1 Primer N.d.)</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>Fig. 3 .</head><label>3</label><figDesc>Fig. 3. Conceptual Idea of Cultural Tourist Recommendation</figDesc><graphic coords="5,147.35,147.35,300.50,225.75" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>Input: O = {rdf triples}; F set of n user's favorite individuals from O Output: {extended rdf triples} w.r.t O and F (to be added to the personalized ontology) 1: ADC  ; Result  ; 2: for each f  F do 3: DC  ; RI  ;TempC  ;RC  ;Relation  ; 4: DC  {c | f is an instance of concept c} 5: RI  {g | r (f, g) for some role r} 6:</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="2,136.10,303.35,345.45,265.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="6,136.10,313.70,318.70,246.95" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0"><head></head><label></label><figDesc></figDesc><graphic coords="8,136.10,183.35,345.35,206.90" type="bitmap" /></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>&lt;Bob&gt; &lt;is a&gt; &lt;person&gt;. &lt;Bob&gt; &lt;is a friend of&gt; &lt;Alice&gt;. &lt;Bob&gt; &lt;is born on&gt; &lt;the 4th of July 1990&gt;. &lt;Bob&gt; &lt;is interested in&gt; &lt;the Mona Lisa&gt;. &lt;the Mona Lisa&gt; &lt;was created by&gt; &lt;Leonardo da Vinci&gt;. &lt;the video 'La Joconde à Washington'&gt; &lt;is about&gt; &lt;the Mona Lisa&gt;</figDesc><table /></figure>
		</body>
		<back>

			<div type="acknowledgement">
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Acknowledgment</head><p>This research was conducted under a grant in the SIIT-JAIST-NECTEC Dual Doctoral Degree Program.</p></div>
			</div>

			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title/>
	</analytic>
	<monogr>
		<title level="j">&lt;Attraction&gt;</title>
		<editor>&lt;Wat Arun&gt;</editor>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">3</biblScope>
		</imprint>
	</monogr>
	<note>&lt;Wat Arun&gt;</note>
</biblStruct>

<biblStruct xml:id="b1">
	<monogr>
		<ptr target="http://www.m-culture" />
		<title level="m">Cultural Knowledge Center, Ministry of Culture</title>
				<meeting><address><addrLine>Thailand</addrLine></address></meeting>
		<imprint>
			<date type="published" when="2014-09-15">September 15, 2014</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Semantic Relation Extraction for Extensive Service of a Cultural Database</title>
		<author>
			<persName><forename type="first">W</forename><surname>Buranasing</surname></persName>
		</author>
		<author>
			<persName><forename type="first">V</forename><surname>Sornlertlamvanich</surname></persName>
		</author>
		<author>
			<persName><forename type="first">T</forename><surname>Charoenporn</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the SNLP2013</title>
				<meeting>the SNLP2013</meeting>
		<imprint>
			<date type="published" when="2013">2013</date>
			<biblScope unit="page" from="241" to="247" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Ontology enrichment with texts from the WWW</title>
		<author>
			<persName><forename type="first">A</forename><surname>Faatz</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Steinmetz</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Semantic Web Mining</title>
		<imprint>
			<biblScope unit="volume">20</biblScope>
			<date type="published" when="2002">2002</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Towards the self-annotating web</title>
		<author>
			<persName><forename type="first">P</forename><surname>Cimiano</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Handschuh</surname></persName>
		</author>
		<author>
			<persName><forename type="first">S</forename><surname>Staab</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the 13th international conference on World Wide Web</title>
				<meeting>the 13th international conference on World Wide Web</meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="462" to="509" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">Towards text knowledge engineering</title>
		<author>
			<persName><forename type="first">U</forename><surname>Hahn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">K</forename><surname>Schnattinger</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Hypothesis</title>
		<imprint>
			<biblScope unit="volume">1</biblScope>
			<date type="published" when="1998">1998</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">Automatic Adaptation of WordNet to Domains</title>
		<author>
			<persName><forename type="first">R</forename><surname>Navigli</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Velardi</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceeding of the LREC2002</title>
				<meeting>eeding of the LREC2002</meeting>
		<imprint>
			<date type="published" when="2002">2002</date>
			<biblScope unit="page" from="1023" to="1027" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">Automatic extension of Gene Ontology with flexible identification of candidate terms</title>
		<author>
			<persName><forename type="first">J.-B</forename><surname>Lee</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J. -J</forename><surname>Kim</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><forename type="middle">C</forename><surname>Park</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Bioinformatics</title>
		<imprint>
			<biblScope unit="volume">22</biblScope>
			<biblScope unit="page" from="665" to="670" />
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Ontology refinement for improved information retrieval</title>
		<author>
			<persName><forename type="first">A</forename><surname>Jimeno-Yepes</surname></persName>
		</author>
		<author>
			<persName><forename type="first">R</forename><surname>Berlanga-Llavori</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Rebholz-Schuhmann</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Information Processing &amp; Management</title>
		<imprint>
			<biblScope unit="volume">46</biblScope>
			<biblScope unit="page" from="426" to="435" />
			<date type="published" when="2010">2010</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b9">
	<monogr>
		<title level="m" type="main">1 Primer N</title>
		<ptr target="http://www.w3.org/TR/2014/NOTE-rdf11-primer-20140624/" />
		<imprint>
			<date type="published" when="2014-10-05">October 5, 2014</date>
		</imprint>
	</monogr>
</biblStruct>

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