<?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">Rule Induction for Concept Hierarchy Alignment</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Ichise</forename><surname>Ryutaro</surname></persName>
							<email>ichise@nii.ac.jp</email>
							<affiliation key="aff0">
								<orgName type="department">Intelligent Systems Research Division</orgName>
								<orgName type="institution">National Institute of Informatics</orgName>
								<address>
									<addrLine>2-1-2 Hitotsubashi, Chiyoda-ku</addrLine>
									<postCode>101-8430</postCode>
									<settlement>Tokyo</settlement>
									<country key="JP">Japan</country>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Honiden</forename><surname>Shinichi</surname></persName>
							<email>honiden@nii.ac.jp</email>
							<affiliation key="aff0">
								<orgName type="department">Intelligent Systems Research Division</orgName>
								<orgName type="institution">National Institute of Informatics</orgName>
								<address>
									<addrLine>2-1-2 Hitotsubashi, Chiyoda-ku</addrLine>
									<postCode>101-8430</postCode>
									<settlement>Tokyo</settlement>
									<country key="JP">Japan</country>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Rule Induction for Concept Hierarchy Alignment</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">0F5DDA18AB799F988FF36437E024F7DB</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T17:34+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>
			<abstract>
<div xmlns="http://www.tei-c.org/ns/1.0"><p>To manage information like ontology, we usually use categorization with concept hierarchy. Such concept hierarchies are managed individual for each system due to the many differences in concept hierarchies. Consequently, it is difficult to reuse information in computer-based systems. Here, we propose a new concept alignment method for concept hierarchies as a solution to this problem, and construct a system to evaluate the performance of our method. The results of this experiment reveal that the proposed method can be used to induce appropriate align rules for concept hierarchies and classify information into appropriate categories within another concept hierarchy.</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>The rapid advances in computer technology have allowed us to archive much more information than ever before. To maintain such archives, hierarchical categorization is often used, by which information is categorized based on a concept hierarchy. Ontologies and class libraries are examples of such systems. The hierarchical categorization is usually maintained by a single organization or individual for consistency. In practice, a concept hierarchy is not suitable for multiple purposes, requiring that concept hierarchies be constructed for individual application domains. In other words, concept hierarchies are maintained in each domain separately. This means that it is not convenient to reuse information because the concept categorization differs between concept hierarchies. To solve this problem, we propose a new method that allows a concept in one concept hierarchy to be aligned with another concept in another concept hierarchy. In this paper, we describe a machine-learning method for aligning multiple concept hierarchies.</p><p>This paper is organized as follows: A concept hierarchy model is defined, followed by the proposal for the new machine learning method used to align concepts. In the experiment section, the performance of our system, HICAL (HIerarchical Concept ALignment system), which is based on the proposed method, is compared in a variety of settings, followed by a discussion of the results. We then discuss related work in regard to HICAL and present the conclusions of this study.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="2">Concept Hierarchy Model</head><p>In this section, we describe a model of the nature of concept hierarchies. Many information management systems for use with conceptual information like ontologies and class libraries are managed via a system of hierarchical categorization. A concept hierarchy contains only one conceptual categorization criterion. We can consider the diagram on the left side of Figure <ref type="figure" target="#fig_0">1</ref> to be a representation of a single concept hierarchy. In the figure there are two different concept hierarchies ( ½ and ¾ ) and three different information instances (Á ½ , Á ¾ and Á ¿ ). Some instances are shared between the two concept hi- erarchies and some are not. It is important to keep in mind that these concept hierarchies are not the same. The next step is to consider an appropriate way to transfer an instance from ½ into ¾ . In the example shown in Figure <ref type="figure" target="#fig_0">1</ref>, ¾ does not contain Á ¾ . If Á ¾ can be placed in the concept hierarchy of ¾ , the user can then use Á ¾ with concept hierarchy ¾ . In the next section, we propose a method of defining a rule for conversion from the concept hierarchy of ½ to that of ¾ , so that an instance that has already been categorized in ½ can subsequently be categorized in ¾ . The most important point of this approach is that the concept hierarchy of ¾ does not need to be adjusted to fit the concept hierarchy of ½ . </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="3">Concept Alignment</head><p>In our proposed method of constructing an alignment rule, we must first find categories that are similar to each other ("similar categories"); the instance will then be aligned based on the similarity between categories. To find similar categories, our algorithm starts by comparing the most general categories of the two concept hierarchies. For each pair of categories, we can determine similarity based on the instances categorized in the two categories. For each category, we can decide whether a particular instance belongs to that category. If the categorization methods of two categories are similar, then the system can generate an aligning rule for them. For example, if one category contains 100 instances and a category in another concept hierarchy contains the same 100 instances, then the algorithm can generate an aligning rule for these categories, because they can be considered to have the same categorization criteria. It should be noted that, because concept hierarchies are structured as trees, we can easily categorize according to a nodal structure, such that lower (more specific) categories are included in higher (more general) categories.</p><p>To find similar categories, we used a statistical method for determining the degree of similarity between two categorization criteria. The " statistic" method <ref type="bibr" target="#b0">[Fleiss, 1973]</ref> is an established method of evaluating similarity between two criteria. We explain this method briefly. Let us suppose that there are two categorization criteria, Ë ½ and Ë ¾ . As men- tioned earlier, we can decide whether a particular information instance belongs to a particular category or not. Consequently, instances are divided into four classes shown in Table <ref type="table">1</ref>. Symbols AE ½½ AE ½¾ AE ¾½ AE ¾¾ denote numbers of in- stances for each class. For example, AE ½½ denotes the number of instances which belong to both the category Ë ½ and the cat- egory Ë ¾ . We may logically suppose that if category Ë ½ and Ë ¾ have the same criterion of categorization, then AE ½¾ and AE ¾½ become close to zero and if the two categories have a dif- ferent criterion of categorization, then AE ½½ and AE ¾¾ become close to zero. The " statistic" method utilizes this principle to determine the similarity of categorization criteria.</p><p>The relationship between the two categorization criteria is examined from "top" to "bottom". The alignment algorithm is shown in Figure <ref type="figure">2</ref>. First, the most general categories in the two concept hierarchies are compared using the " statistic". If the comparison confirms that the two categories are similar, then the algorithm outputs an alignment rule for them. At the same time, the algorithm pairs one of these two similar categories with a "child" category in the other similar category. This new pair is then evaluated recursively using the " statistic" method. When a similar pair is not generated, the algorithm outputs the alignment rule between the two concept hierarchies. We can then apply this rule to deciding whether a particular instance in ½ fits the concept hierarchy in ¾ .</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Input:</head><p>AE ½¼ , // Top category in ½ AE ¾¼ , // </p><formula xml:id="formula_0">Á Ð Ñ ÒØ Ò Ø ; AE ½ AE ¾ Ø Û Ó Ò Ó Ò Á ; /* calculate ×Ø Ø ×Ø */ if ´AE½ AE ¾ µ È Ø•½ Ñ ÓÑ Ò Ø ÓÒ´AE ½ AE ¾ µ; Ê Ê • Á; fi; Ø Ø Á; end; Ø Ø • ½ ; end;</formula><p>return Ê; </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.1">Data and Settings</head><p>In order to evaluate this algorithm, we conducted three experiments using the Yahoo! Japan [Yahoo! Japan, 2000] and LYCOS Japan [LYCOS Japan, 2000] directories as concept hierarchies, and the links (URLs) in each directory as information instances. The Yahoo! directory contains approximately 41,000 categories and 224,000 URLs. LYCOS contains approximately 5,700 categories and 48,000 URLs. Approximately 25,000 URLs are common to both Yahoo! and LYCOS. Generally speaking, as a concept hierarchy, Yahoo! contains more knowledge than LYCOS, however half of the URLs in LYCOS are not contained in Yahoo!. This demonstrates that even a concept hierarchy that contains an enormous amount of information does not cover all information.</p><p>In this study, we used the three category pairs (and subcategories) as our two concept hierarchies. The location in Yahoo! and LYCOS are as follows: We conducted 10-fold cross validation for shared instances. Shared instances were divided into 10 data sets; 9 of these sets were used for training and the remaining set was used for testing. Ten experiments were conducted for each data set. The parameter of significance level for the " statistic" was set at 5%.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.2">Results</head><p>The results of the experiments are shown in Figure <ref type="figure" target="#fig_3">3</ref>, 4 and 5. The vertical axis is the average accuracy of the test data. "Exact rules" represent values of accuracy for a system that only uses the alignment rules for the category to which the instance belongs. "Parent rules" indicates that if the system does not generate an alignment rule for a category to which the instance belongs, it will use the rule generated for the parent category instead. "Criterion 1" indicates that the instance is categorized in the same category as the test data and "Criterion 2" indicates that the instance is categorized in the same category or parent category as the test data. "Criterion 1" is very strict criterion because the target concept hierarchy should have enough intermediate categories in comparison with the source concept hierarchy, while "Criterion 2" is more general and more realistic because it does not matter which concept hierarchies are rich in categorization. Two directions of alignment are presented; from Yahoo! to Lycos, and from Lycos to Yahoo!. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4.3">Discussion</head><p>More than 80% of the instances used in our experiments, with the exception of the company domain, were categorized correctly by HICAL. In the company domain, more than 60% of the instances were categorize appropriately. The data in Figure <ref type="figure" target="#fig_3">3</ref> 5 imply that Yahoo-to-Lycos alignment was more accurate than the inverse operation. As can be seen from the total number of categories, the categorical hierarchy in Yahoo! is more complex than that of LYCOS. Therefore, for Yahoo-to-Lycos alignment, the learned rules are likely to involve transferring instances from relatively complex categories to relatively general categories. Such a trend is likely to result in relatively accurate rules. For example, suppose concept hierarchy contains category Ë within concept , however concept hierarchy does not divide into categories. In such a case, it would be much easier to learn a rule for "A:/X/S -B:/X" than to learn a rule for "B:/X -A:/X/S", because "B:/X" contains instances that belong in Ë and instances that do not. The results shown in figures reflect this. Nevertheless, in this situation our method works properly. When regarding parent categories as correct answers ("Criterion 2"), both alignment directions exhibited almost the same results, i.e., "B:/X -A:/X" is learned instead of "B:/X -A:/X/S".</p><p>The limitation of this method is that it does not work in cases in which the more general and more specific categories within a concept hierarchy are independent. For example, let's consider two concept hierarchies; one that classifies a food-related instance under foodstuff as the more general category and then by country of origin as the more specific category, and another that classifies a food-related instance by country of origin as the more general category and by foodstuff as the more specific category. Both types of concept hierarchy can be found on the concept hierarchy. In such a case, our current system HICAL would not work, because comparison between the two categories proceeds from gen-eral to specific (top to bottom). To solve this problem, we are planning to combine our current system with a bottom-up method.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5">Related Work</head><p>One of the systems related to HICAL is the ontology merging/alignment system. In the merging process for ontology, a process such as our system is necessary due the requirements of concept hierarchy management. Chimaera <ref type="bibr" target="#b0">[McGuinness et al., 2000]</ref> and <ref type="bibr">PROMPT [Noy and Musen, 2000]</ref> are examples of such systems, assisting in the combination of different ontologies. However, such systems require human interaction for merging or alignment. In addition to this requirement, they are based on similarity between words, which introduces instability. Word similarity is often biased by the dictionaries used. In contrast, our system does not use word similarity, instead using syntactics alone. Hence, our system has the ability to find identical concepts regardless of the category name or word. For example in the experiment conducted in this study, in the literature domain, HICAL found the relationship between the "Genji-monogatari" (a famous Japanese story written by "Murasakishikibu") category in LY-COS and the "Murasakishikibu" category in Yahoo!<ref type="foot" target="#foot_0">1</ref> . In LY-COS, classical literature is classified by title (concept category), whereas in Yahoo!, poetry masters are categorized by author. As the dictionaries commonly used do not contain such information, word-based systems would not be capable of finding title/author relationships.</p><p>The bookmark-sharing systems of Siteseer <ref type="bibr" target="#b1">[Rucker, 1997]</ref> and Blink <ref type="bibr" target="#b0">[Blink, 2000]</ref> are also similar to HICAL. The main difference is the use of hierarchies for categorization. The Siteseer and Blink system only considers the number of URLs (instances) in a given category, whereas our method uses hierarchical One of the merits of our approach is that if there is no exact category into which a given URL (instance) fits, then the URL (instance) is mapped into the parent category. kMedia <ref type="bibr">[Takeda et al.2000</ref>] is another bookmarksharing system that uses hierarchical structures explicitly but is dependent on similarity of words in pages. <ref type="bibr">Bookmark-Agent [Mori and Yamada, 1999]</ref> uses another approach, utilizing bookmarks based on keywords. As mentioned above, HICAL only uses syntactical information, not words as are used by a bookmark agent. HICAL is therefore capable of correctly categorizing different words under the same concept.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Conclusion</head><p>In this paper, we propose a new method for aligning concept hierarchies as a new approach to utilizing information in multiple concept hierarchies, based on statistical methods. To test our ideas, we conducted experiments using the Yahoo! and LYCOS categories. Our experimental results show that the alignment rules learned by HICAL yield reliable alignments, allowing information in one concept hierarchy to be aligned to an appropriate position in another concept hierarchy. The advantage of using our method is that it allows users to use their own concept hierarchy for categorizing all information, and may serve as a powerful tool for aligning concept hierarchies.</p><p>With these encouraging results, several research possibilities present themselves for future development of alignment strategies. Our alignment method is based on a top-down approach. We should combine a bottom-up approach to increase accuracy. In addition, there may exist other possibilities for alignment. Extending the proposal to applying to more than three concept hierarchies needs to be investigated. In such a case, despite confliction between several concept hierarchies, more hints can be obtained from other concept hierarchies.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_0"><head>Figure 1 :</head><label>1</label><figDesc>Figure 1: Concept Hierarchy Model</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head></head><label></label><figDesc>Figure 2: Alignment Algorithm</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head></head><label></label><figDesc>¯Yahoo! : Arts / Humanities / Literature LYCOS : Arts / Literature ¯Yahoo! : Business and Economy / Companies LYCOS : Business Industry / Company ¯Yahoo! : Recreation LYCOS : Hobby Sports</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>Figure 3 :</head><label>3</label><figDesc>Figure 3: Result for Literature Domain</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>Figure 5 :</head><label>5</label><figDesc>Figure 4: Result for Company Domain</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_1"><head></head><label></label><figDesc>Top category in ¾</figDesc><table><row><cell>Output:</cell><cell>È ; Ê;</cell><cell>// threshold for statistic // Rule Set</cell></row><row><cell>begin</cell><cell></cell><cell></cell></row><row><cell cols="3">/* make pair for candidate */</cell></row><row><cell cols="3">/* using child node or parent node */</cell></row><row><cell cols="2">½ Ñ Ø ½; Ê ;</cell><cell>ÓÑ Ò Ø ÓÒ´AE ½¼ AE ¾¼ µ;</cell></row><row><cell cols="2">while Ø</cell><cell></cell></row><row><cell cols="2">while Ø</cell><cell></cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="1" xml:id="foot_0">similar to the relationship between "Sherlock Holmes" and "Conan Doyle"</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">PROMPT: Algorithm and Tool for Automated Ontology Merging and Alignment</title>
		<author>
			<persName><forename type="first">;</forename><surname>Blink</surname></persName>
		</author>
		<author>
			<persName><forename type="first">;</forename><surname>Fleiss</surname></persName>
		</author>
		<author>
			<persName><forename type="first">L</forename><surname>Joseph</surname></persName>
		</author>
		<author>
			<persName><surname>Fleiss</surname></persName>
		</author>
		<author>
			<persName><surname>Mcguinness</surname></persName>
		</author>
		<ptr target="http://www.lycos.co.jp/" />
	</analytic>
	<monogr>
		<title level="m">An Environment for Merging and Testing Large Ontologies In Proceedings of the seventh International Conference on Principles of Knowledge Representation and Reasoning</title>
				<editor>
			<persName><forename type="first">Musen</forename><surname>Noy</surname></persName>
		</editor>
		<meeting><address><addrLine>LYCOS Japan; LYCOS Japan; Austin, Texas</addrLine></address></meeting>
		<imprint>
			<publisher>American Association for Artificial Intelligence</publisher>
			<date type="published" when="1973">2000. 2000. 1973. 1973. 2000. 2000. 2000. KR2000. 2000. 1999. 1999. 2000. July-August 2000</date>
			<biblScope unit="page" from="450" to="455" />
		</imprint>
	</monogr>
	<note>Proceedings of the 17th National Conference on Artificial Intelligence</note>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">Siteseer: Personalized Navigation for the Web Communications of the ACM</title>
		<author>
			<persName><forename type="first">James</forename><surname>Rucker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Marcos</forename><forename type="middle">J</forename><surname>Rucker</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Takeshi</forename><surname>Polanco ; Hideaki Takeda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Yuichiro</forename><surname>Matsuzuka</surname></persName>
		</author>
		<author>
			<persName><surname>Taniguchi</surname></persName>
		</author>
		<ptr target="http://www.yahoo.co.jp/" />
	</analytic>
	<monogr>
		<title level="m">Discovery of Shared Topics Networks among People -A Simple Approach to Find Community Knowledge from WWW Bookmarks</title>
				<meeting><address><addrLine>Melbourne, Australia</addrLine></address></meeting>
		<imprint>
			<publisher>Springer</publisher>
			<date type="published" when="1997">1997. 1997. 2000. August 28 -September 1. 2000. 2000. 2000</date>
			<biblScope unit="volume">40</biblScope>
			<biblScope unit="page" from="668" to="678" />
		</imprint>
	</monogr>
	<note>Proceedings of the 6th Pacific Rim International Conference on Artificial Intelligence(PRICAI-2000). Yahoo! Japan. Yahoo! Japan</note>
</biblStruct>

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