<?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">Exploiting the structure of background knowledge used in ontology matching</title>
			</titleStmt>
			<publicationStmt>
				<publisher/>
				<availability status="unknown"><licence/></availability>
			</publicationStmt>
			<sourceDesc>
				<biblStruct>
					<analytic>
						<author>
							<persName><forename type="first">Zharko</forename><surname>Aleksovski</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Philips Research</orgName>
								<address>
									<settlement>Eindhoven</settlement>
								</address>
							</affiliation>
							<affiliation key="aff1">
								<orgName type="institution">Vrije Universiteit</orgName>
								<address>
									<settlement>Amsterdam</settlement>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Warner</forename><surname>Ten Kate</surname></persName>
							<affiliation key="aff0">
								<orgName type="institution">Philips Research</orgName>
								<address>
									<settlement>Eindhoven</settlement>
								</address>
							</affiliation>
						</author>
						<author>
							<persName><forename type="first">Frank</forename><surname>Van Harmelen</surname></persName>
							<affiliation key="aff1">
								<orgName type="institution">Vrije Universiteit</orgName>
								<address>
									<settlement>Amsterdam</settlement>
								</address>
							</affiliation>
						</author>
						<title level="a" type="main">Exploiting the structure of background knowledge used in ontology matching</title>
					</analytic>
					<monogr>
						<imprint>
							<date/>
						</imprint>
					</monogr>
					<idno type="MD5">94240CE8A3241DAE0AA6BF8594533695</idno>
				</biblStruct>
			</sourceDesc>
		</fileDesc>
		<encodingDesc>
			<appInfo>
				<application version="0.7.2" ident="GROBID" when="2023-03-24T06:49+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>We investigate the use of a background knowledge ontology in ontology matching. We conducted experiments on matching two medical ontologies using a third extensive one as background knowledge, and compare the results with directly matching the two ontologies. Our results indicate that using background knowledge, in particular the exploitation of its structure, has enormous benefits on the matching. The structure of the background ontology needs closer examination to determine how to use it in order to obtain maximal benefit.</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 problem of ontology alignment (also known as ontology integration, semantic integration, ontology mapping, etc.) plays a central role in the development of knowledge based systems. New technologies such as Semantic Web make it easier to use ontologies in the information systems. These trends have driven the development of new ontologies, which in turn has resulted in an increasing amount of ontologies becoming available in the recent years. Essential to an ontology is its reusability, which implies one needs to integrate it into the system using it. Problem arises if the ontology to be integrated uses a different vocabulary from the system using it.</p><p>This problem initiated a lot of research on ontology matching lately, see <ref type="bibr" target="#b0">[1]</ref><ref type="bibr" target="#b1">[2]</ref><ref type="bibr" target="#b2">[3]</ref>. Various approaches have been developed. They mainly focus on two aspects: lexically matching the elements of the ontologies, and using the structure of the ontologies. The first uses string-based and linguistic methods to detect relatedness between elements based on string similarity of their labels, and the second uses the relations within the ontologies to detect similarities. Elements in the ontologies that are related but have neither lexical nor structural similarity remain undetected. Motivated by this issue, we focused on using background knowledge. We followed the intuition that a background ontology which comprehensively describes the domain of the source and target ontologies will provide a way to find matches missed by other approaches.</p><p>In earlier papers, we showed that the use of background ontology can compensate for lack of structure and lexical overlap, and increasing the amount of background knowledge (multiple ontologies) improves the matching result, see <ref type="bibr" target="#b3">[4,</ref><ref type="bibr" target="#b4">5]</ref>. In this work we investigate the benefits and problems of using a comprehensive domain ontology as background knowledge. We conducted experiments of matching one medical ontology to another, while using a much larger and detailed ontology of the same domain as background knowledge. The results of our experiments confirmed that the background knowledge can significantly boost the performance of the matching process. In particular, maximal benefit is achieved when combining different pieces of knowledge within the background knowledge. However, these pieces need careful consideration when combining them.</p><p>The paper is organized as follows: in Section 2 we describe the general scheme of our approach, that is how we use an ontology as background knowledge in ontology integration. In Sections 3 and 4 we describe a case study and a set of experiments to test our expectations. In Section 5 we report on the results of these experiments with evaluation on validity. In Section 6 we discuss representative matches of the different experiments, and Sections 7 and 8 conclude the paper with discussion on related and future work.</p><p>2 Our approach: Using a background knowledge ontology in ontology matching</p><p>In our approach we match two ontologies using a third as background knowledge. We call the ontologies being matched the source and target, see Figure <ref type="figure">1</ref>. We make use of the background knowledge by first relating the concepts from the source and target ontology to the background knowledge, and then checking if these concepts are related. Hence, this process proceeds in two steps: anchoring and deriving relations.</p><p>Anchoring is matching the source and target concepts to the background knowledge. In general, this process can be performed by using an existing ontology matching technique. Besides the concept's labels one can also use the structure of the ontologies. In the anchoring we are not only interested in finding the corresponding equivalent concepts. As we will see in our experiments later, other kind of relatedness with the concepts in the background knowledge can be useful as well.</p><p>Deriving relations is the process of discovering relations between source and target concepts by looking for relations between their anchored concepts in the background knowledge. Both the source and target concept's anchors are part of the background knowledge, and checking if they are related means using the reasoning service in the background knowledge ontology. Combining the anchor relations with the relations between the background knowledge concepts derives the relation between source and target concepts, which is what we are looking for.</p><p>To explain this process in the context of medical ontologies, a realistic example is the following: the source concept SRC:Brain is anchored to background knowledge concept BK:Brain, and the target concept T AR:Head is anchored to a background knowledge concept BK:Head. The background knowledge reveals a relation BK:Brain part-of BK:Head, and we derive a relation that source concept SRC:Brain has a narrower meaning than the target concept T AR:Head. Using background knowledge was crucial in this case; the match was not found by directly matching the source to the target ontology, SRC:Brain is classified under SRC:Central nervous system which is in no way related to the concept T AR:Head.</p><p>As the example suggests, of particular interest in our approach is exploiting the structure of the background knowledge ontology. It is done in the deriving relations step, when checking for relatedness between the anchored concepts in the background</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Source ontology</head><p>Target ontology</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Background knowledge ontology</head><p>Indirect match</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Deriving relations</head></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Anchoring Anchoring</head><p>Fig. <ref type="figure">1</ref>. Matching source to target ontology using background knowledge.</p><p>knowledge ontology. Now we introduce the formal definitions of all the components in this scheme, which we will use in the rest of the paper.</p><p>Concept is a class of things grouped together due to some shared property. It is named with one or more labels which are synonymous to each other. Besides the labels, concept is also determined by its relations to other concepts. We will refer to a concept in two ways: with capital italic letters X, Y ... when referring to an arbitrary concept, X O or X ON T when referring to a concept from a specific ontology, and by using its label, for example Temporal lobe, and ON T :Temporal lobe or O:Temporal lobe when referring to a concept from a specific ontology.</p><p>Relation is a triple (X, relation, Y ), where X and Y are concepts, and relation ∈ T, where T is the set of all types of relations. We will also write it as X ∼ Y with "∼" being the symbol of the relation. Examples of relations used in this paper are: X ≡ Y , -the two concepts have the same meaning, and X Y (with inverse: ), also written as X is-narrower-than Y -the first has narrower meaning than the second. Other relations are used in the existing ontologies as well, see Section 4. Relations can be established between concepts from the same and also from different ontologies.</p><p>Ontology is a pair of sets: ON T (C, R). C is a set of concepts, R is the set of relations among these concepts. We will refer to an ontology using shortened form of its name written in calligraphic letters, like ON T . When referring to C or R of a specific ontology, we will write them as C ON T and R ON T Ontology match is a function of two ontologies that returns a set of relations between their concepts:</p><formula xml:id="formula_0">f : (SRC, T AR) → {(X, relation, Y )|X ∈ C SRC , relation ∈ T, Y ∈ C T AR } (1)</formula><p>Specific types of ontology matches of interest to our approach are the following two: Anchorings are two ontology matches from the source and target ontology to the background knowledge respectively, and Deriving relations is an ontology match between the source and the target ontology which is an indirect matching that uses their anchors to the background knowledge, and the background knowledge itself.</p><p>Hypothesis: Using comprehensive domain ontology as background knowledge can significantly boost the performance of an ontology matching process.</p><p>To test this hypothesis and investigate the problems that occur when our matching scheme is used in practice, we conducted a set of experiments matching existing ontologies available on the Semantic Web. We matched the anatomy parts of CRISP and MeSH using the FMA ontology as a background knowledge. CRISP and MeSH were choosen randomly, and FMA because it extensively covers the anatomy domain. </p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Direct match</head><p>Anchoring:</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Direct match</head><p>Fig. <ref type="figure">2</ref>. Matching CRISP to MeSH ontology using FMA as background knowledge.</p><p>The test data used in the experiments. Source ontology: CRISP<ref type="foot" target="#foot_0">3</ref> (Computer Retrieval of Information on Scientific Projects) is a biomedical document classification system. It contains 738 concepts organized in a hierarchy. The relations in its hierarchy are established based on the classified document sets. The hierarchy contains two relations: broader-than and its inverse narrower-than, meaning superset and subset between the corresponding document sets respectively. In our experiments we used the part of CRISP describing anatomy.</p><p>Target ontology: MeSH<ref type="foot" target="#foot_1">4</ref> is the National Library of Medicine's controlled vocabulary thesaurus intended for classification of documents. The part which we used in the experiments is the anatomy sub hierarchy. It contains is 1475 concepts, and is based on broader-than and its inverse narrower-than relations, the same as CRISP.</p><p>Background knowledge ontology: FMA, as stated in its description <ref type="foot" target="#foot_2">5</ref> : "The Foundational Model of Anatomy is a domain ontology that represents a coherent body of explicit declarative knowledge about human anatomy." The version of FMA used in our experiments dates from the end of 2005. It contains 75000 concepts interconnected with around 160 different relation types. We used the main two hierarchies: isa and part-of.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Testing our hypothesis by conducting experiments.</head><p>We performed five experiments matching CRISP to MeSH. In the first we matched them directly, and in the other four we matched them indirectly using the FMA ontology as background knowledge. The direct matching served as a baseline, against which we compared each of the indirect matchings. With the intention to distile the added value of using background knowledge, we analyzed the additional matches discovered by indirect matching. Furthermore, there were some cases of matches found in the direct and not in the indirect matching. We discuss these in Section 6.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="4">The experiments</head><p>We performed five experiments. In Experiment 1 we matched CRISP to MeSH directly and in the other four we matched them indirectly using FMA as background knowledge. In Experiment 2 we exploited each isa and part-of relation in FMA separately; in Experiment 3 we used isa and part-of relations with their transitive closures; in Experiment 4 we used isa and part-of combined, and in Experiment 5 we restricted to specific combinations of them to induce the matches. The result of each experiment was an ontology match between CRISP and MeSH concepts, using one of the three relations: ≡ (equivalent), (narrower-than), (broader-than). Now, we explain the direct and then the indirect matchings in detail.</p><p>Experiment 1: Direct matching was performed in two steps: lexical and structural. In the lexical phase we matched CRISP to MeSH using the concept's labels. We cleaned the labels of interpunction, general words like the, of, and etc., we accounted for word order and singular/plural forms of the same words. When matching two concepts X and Y , we concluded X ≡ d Y if a pair of their labels matches <ref type="foot" target="#foot_3">6</ref> . Further, we used partial matches as well, if X has a label consisting of a superset of words of a label of Y we concluded X d Y , and analogously X d Y if X has label of subset of the words of a label of Y . In other words, we used the partial lexical matches following the intuition that additional words in a label additionally constrain the meaning of that concept. This way, for example, we concluded that CSP: Mesenteric artery d MSH: Artery.</p><p>In the structural phase of direct matching we used the structure of CRISP and MeSH to further induce matches by combining the relations from CRISP and MeSH and the lexical matches. For example, from the two relations: We extended the set of lexical matches with the matches implied by the structure of CRISP and MeSH. The following rules were used to extend the result set<ref type="foot" target="#foot_4">7</ref> :</p><formula xml:id="formula_1">-if (X C d Y M ) ∧ (Y M Z M ) induce (X C d Z M ) -if (X C Y C ) ∧ (Y C d Z M ) induce (X C d Z M ) -if (X C d Y M ) ∧ (Y M Z M ) induce (X C d Z M ) -if (X C Y C ) ∧ (Y C d Z M ) induce (X C d Z M )</formula><p>These rules also used ≡ relations, where X ≡ Y was considered as X Y and X Y . The rules were exhaustively applied on the result set.</p><p>Indirect matching followed the scheme that we described in Section 2. It was performed in two steps: first anchoring CRISP and MeSH to FMA, and then deriving relations between CRISP and MeSH using FMA as background knowledge, Figure <ref type="figure">2</ref>.</p><p>In the anchoring we used the same direct matching technique described for matching CRISP to MeSH directly. Both CRISP and MeSH were anchored to FMA. The result was set of matches with three different kinds of relations: X ≡ a Y , X a Y , X a Y , where Y is a concept from FMA, and X is in CRISP or MeSH.</p><p>When deriving the relations we used the following rules:</p><formula xml:id="formula_2">-if (X C a Y F ) ∧ (Y F Z F ) ∧ (Z F a Q M ) induce (X C i Q M ) -if (X C a Y F ) ∧ (Y F Z F ) ∧ (Z F a Q M ) induce (X C i Q M )</formula><p>where we used the relations isa and part-of for , and their inverse has-kind and haspart for . However, in FMA there are no broader-than and narrower-than relations, but their specializations: isa and part-of with their inverses has-kind and has-part. We conducted four different experiments of indirect matching while using FMA as a background knowledge. The experiments differ in the way isa and part-of relations from FMA were used and combined when deriving broader-than and narrower-than relations which are then used in the two rules stated above to derive the indirect matches between CRISP and MeSH concepts.</p><p>Experiment 2: Indirect matching by using FMA isa and part-of relations without transitive closure. We induced a relation between the FMA concepts if they were directly related with isa or part-of relation. We used the following rules:</p><formula xml:id="formula_3">-(X F isa Y F ) induce (X F Y F ) -(X F part-of Y F ) induce (X F Y F )</formula><p>When a relation X F Y F was induced, we added its semantic equivalent Y F X F as well. We did this in all the indirect matching experiments.</p><p>Experiment 3: Indirect matching by using FMA isa and part-of relations with their transitive closures. Relation between two FMA concepts was induced when they were related with the transitive closure of isa or part-of relations. We used the following rules:</p><formula xml:id="formula_4">-(X F 1 isa X F 2 isa ... isa X F n ) induce (X F 1 X F n ) -(X F 1 part-of X F 2 part-of ... part-of X F n ) induce (X F 1 X F n )</formula><p>Experiment 4: Indirect matching by using the transitive closure of FMA isa and part-of relations combined. In this experiment we completely merged isa and partof relations and then used the transitive closure of the resulting relation. We used one single inference rule:</p><formula xml:id="formula_5">-(X F 1 rel 1 X F 2 rel 2 ... rel n−1 X F n ) where rel i ∈ {isa, part-of} induce (X F 1 X F n )</formula><p>After analyzing the results of Experiment 4 it appeared that false positive matches were created due to using isa relation before part-of in the process of inducing matches, see Section 6 for clarification. To overcome this negative effect we conducted the next experiment.</p><p>Experiment 5: Indirect matching by using the transitive closure of FMA isa and part-of relations without using isa before part-of . What we did in this experiment was avoiding the use of isa relation before part-of. We used one single inference rule:</p><formula xml:id="formula_6">-(X F 1 part-of X F 2 ... X F k−1 part-of X F k isa X F k+1 ... X F n−1 isa X F n ) induce (X F 1 X F n )</formula><p>5</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head>Results and evaluation</head><p>We present now the results of the experiments. First we explain the numbers presented in the tables, then we interpret and explain their meaning, and finally we provide evaluation on the results. An important issue in presenting the matching results is that in one set of matches many of them may be implied by the others, in combination with the structure of the ontologies. For example, all the concepts in CRISP are found more specific than the root concept in MeSH, whereas having equivalence between the two root concepts already implies all those matches. Similarly, having a match between two concepts contains implicit knowledge about their sub and super-concepts. To make a fair trade-off between the two cases of having all the possible matches and having only the minimal set of matches that implies all the rest, we decided on a result set that is in between.</p><p>In each matching experiment we did the following: We started from the set of all matches, including the implied. For each source concept we took the set of all its matches, and then minimized that set by discarding the matches which are implied by the rest of the set. The minimal set is not sensitive to the order of discarding the implied matches. The union of these minimized sets was the final result. This trade-off matching set extracts the minimal knowledge from the matching result for each of the source concepts separately.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.1">Results of direct and indirect matchings</head><p>In the anchoring phase we matched CRISP and MeSH to FMA directly. The results are shown in Figure <ref type="figure">3</ref>. The equivalence relations were established as 1-1 matches, while narrower-than and broader-than as many to many. Looking for equivalences only already produced successful anchoring: 65.5% of CRISP and 70.6% of MeSH concepts were anchored to their equivalent concepts in FMA. This success comes from the richness of FMA. On the other hand, for many there were no equivalent concepts in FMA because of disagreement on the coverage of anatomy domain. In CRISP there is a concept CSP: Muscle movement which is not an anatomical part of the human body, and as such does not exist in FMA. Still, as shown in the last column on Figure <ref type="figure">3</ref>, nearly 99% of the concepts from both CRISP and MeSH were anchored due to using the structure  <ref type="figure" target="#fig_2">4</ref> summarizes the results of the five experiments. Comparing the indirect to the direct matching, the indirect matchings found many more narrower-than and broaderthan relations than the direct matching. It appeared that the concepts in CRISP and MeSH can be related in many more ways which can not be found by using only the structure of these ontologies alone. In our case FMA contributed the missing knowledge which resulted in such an improvement over the direct matching.  The last column in Figure <ref type="figure" target="#fig_2">4</ref> shows the increase of amount of matches of the indirect matching when compared to the direct matching. The indirect matching of Experiment 2 produced 29% more matches than the direct matching. So, using only the direct isa and part-of relations between the concepts in FMA already outperformed the direct matching. When using the transitive closure of isa and part-of (Experiment 3) we obtained increase of 167%, or nearly 2.7 times more matches than the direct matching. When arbitrarialy mixing isa and part-of with their transitive closure we got increase of 306%, or 4 times more matches than the direct. The fifth experiment, when combining the isa and part-of in a resticted way, there was an increase of 210% which is 3.1 times more matches than the direct. It produced 26% less matches than the fourth, and 19% more than the third experiment.</p><p>These numbers show that using background knowledge produces enormously more matches than direct matching. Without combining the relations within the background knowledge it is already better than the direct matching, then combining the relations in the background knowledge produces much more matches, and combining different relations within background knowledge produces the maximal number. Of course, these numbers do not say anything about the quality of these matches. This will be discussed in the next section. In particular, if the relations are combined arbitrarily then there is big increase in the amount of matches but also false positive matches are created, but when combining them in a specific way we retain the precision of the matches while again considerably increasing the recall.</p><p>When looking at Equivalent (≡), the indirect matching found slightly less relations. All the indirect matchings discovered the same amount of equivalences because the only way to find equivalence indirectly is to have both concepts anchored to the same concept in background knowledge. The equivalences found directly and not indirectly were caused by concepts which existed in CRISP and MeSH but not in FMA. In the next section we take a closer look at such a case. In few cases equivalences were detected indirectly and not directly because their labels were found as synonymous only through the background knowledge.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="5.2">Evaluation of results</head><p>To test for correctness of the matches that we produced with the different experiments, we randomly choose 30 CRISP concepts, and inspected their matches by manually browsing the Wikipedia<ref type="foot" target="#foot_5">8</ref> pages describing these concepts. The evaluation is presented in Figure <ref type="figure">5</ref>. In the last column of Figure <ref type="figure">5</ref> is shown the correctness of the matches produced by the different experiments. Only in Experiment 4 there were wrong matches found where the precision dropped to 93.7%, and in the other experiments it was 100% meaning that all the discovered matches were correct. The evaluation of Experiment 2 and 3 was left out because they produced subsets of Experiment 5 which already produced 100% correct matches.</p><p>Clearly, 30 concepts is not a sufficient number to get to a full evaluation. However, all these cases were closely examined and gave us the impression that this evaluation depicts the correctness of the experiments. The number of matches on these 30 concepts resembles the ratio as found on the whole test set.</p><p>In lack of gold standard, the evaluation phase turned out not to be straight forward. We had to make a choice what to consider correct and what not. Namely, some matches are arguably correct because of the nature of the relation constitutional-part-of. For example, the ulnar artery is constitutional part of the elbow, but it also stretches through the whole arm, and therefore it is not part of the elbow only. We call these matches shared.</p><p>Yet, having the relation between ulnar artery and elbow is a useful one, somebody looking for medical resources about an elbow is interested in the arteries passing through the elbow as well, see Wikipedia for more details on this example. We explored the matches or produced in Experiment 5, and found out that 30 matches are shared, while the other 57 are not. This means that even if inspecting the matches rigidly by discarding shared matches, the background knowledge still produces a large gain in the matching results.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="6">Analysis of discovered matches</head><p>We selected three representative cases of matches from the result sets. We will discuss matches found by the indirect matchings and not by the direct, then take a look at the causes for finding incorrect matches when arbitrary mixing the isa and part-of relations in the background knowledge, and finally we discuss matches found by the direct but not by the indirect matching. Case 1: Matches found by indirect and not by the direct matching. CSP: Temporal lobe i MSH: Head is a representative case of these matches, and is shown on the left hand side in Figure <ref type="figure">6</ref>. Temporal lobes are parts of the brain, and consequently parts of the human's head. In the structure of MeSH and CRISP they are classified under the Brain which is classified under Central Nervous System, and are not connected in any way with the Head. Therefore relation to the Head is impossible to establish using direct matching, and the background knowledge is crucial in discovering the match.</p><p>Case 2: Incorrect match produced by arbitrary mixing of isa and part-of hierarchies. When using isa and then part-of in the inference, some of the matches were incorrect. An example is shown on the right hand side in Figure <ref type="figure">6</ref>  Combining the results of the direct and indirect matching will improve the result of the both. We showed that in an earlier study in <ref type="bibr" target="#b3">[4]</ref>.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="7">Related work</head><p>The research topic of semantic integration is a very active one, yet we encountered two major difficulties when comparing our approach with the others. First is the objective in matching: some target at finding pairs of most corresponding concepts, others aim at 1-1 mappings only, etc.; and second is the different way we use background knowledge.</p><p>Existing approaches mostly use background knowledge in the form of lexicons for discovering synonyms, see <ref type="bibr" target="#b5">[6,</ref><ref type="bibr" target="#b1">2,</ref><ref type="bibr" target="#b6">7]</ref>. S-Match, <ref type="bibr" target="#b7">[8]</ref>, is example where background knowledge is exploited in doing the mapping, which is very similar to the approach we used in this work. In the current state S-Match uses a predefined set of background knowledge sources, such as Wordnet and UMLS. Moreover, it uses the class hierarchy of the background knowledge ontologies.</p><p>Related case-study was performed in <ref type="bibr" target="#b8">[9]</ref>, where the authors investigated enriching user search queries for image retrieval, by using relations from Wordnet. This follows closely our own scheme: the user search query is a source ontology of one single concept with one single label, Wordnet is the background knowledge, and the classification of images is the target ontology. They used isa and part-of relations, and they arrived to conclusion comparable with ours about using and combining these relations.</p><p>The work we present here is a sequel of another case study that followed similar scheme of using background knowledge in ontology integration, see <ref type="bibr" target="#b3">[4]</ref>. In contrast to this work, in the previous studies we used source and target ontologies without structure, the relations we were chasing for were semantic closeness rather than relations with exact semantics such as broader-than and narrower-than. The background knowledge contained only broader-than and narrower-than relations, which prohibited us in investigating the impact of combining different relations.</p></div>
<div xmlns="http://www.tei-c.org/ns/1.0"><head n="8">Conclusions</head><p>Based on the results produced in the experiments, we draw the following conclusions from our study:</p><p>(i) Using comprehensive background knowledge in form of ontology can boost the ontology matching process as compared to a direct matching of the two ontologies.</p><p>(ii) Most of the value in using background knowledge comes from combining different pieces of knowledge within the background knowledge.</p><p>(iii) Different pieces of knowledge within the background knowledge need careful combination in order to gain maximal benefit.</p><p>A crucial requirement in using background knowledge is the existence of extensive reference ontologies in different domains at hand. Therefore, the development of such ontologies and subsequent publication on the Semantic Web will make the problem of integration easier.</p><p>Currently we are expanding the reported experiments further, we are looking for approximation schemes when deriving the relations within FMA, and we are investigating the usefulness of other relations in FMA like: X is-attached-to Y , X sends-output-to Y , etc. These relations will produce more matches different from those we present here.</p><p>Our findings were concluded from experiments conducted on medical test data. Therefore, we are conducting similar experiments in music domain on matching styles and genres from different music providers. In contrast to the medical domain, the knowledge in music is much weakly structured as different music content providers largely disagree on the meaning of music terms. In this direction, we took the effort to extract relatively extensive music ontology from Wikipedia which will serve as background knowledge in our experiments.</p></div><figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_1"><head>-</head><label></label><figDesc>CSP: Brain ≡ d MSH: Brain -MSH: Brain MSH: Temporal lobes we can induce the relation -CSP: Brain d MSH: Temporal lobes</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_2"><head>Fig. 4 .</head><label>4</label><figDesc>Fig. 4. Matching CRISP to MeSH directly and indirectly</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_3"><head>4 :Fig. 5 .</head><label>45</label><figDesc>Fig. 5. Evaluation of the matchings CRISP to MeSH directly and indirectly on 30 random CRISP concepts</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_4"><head>4 Fig. 6 .</head><label>46</label><figDesc>Fig.6. Two indirect matches: on the left the correct match Temporal lobe i Head, and on the right incorrect match Dental pulp i Bronchus.</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" xml:id="fig_5"><head></head><label></label><figDesc>finding CSP:Dental pulp i MSH:Bronchus. Each of the two relations Dental pulp isa Loose connective tissue part-of Right main bronchus remain correct when generalizing to Dental pulp Loose connective tissue, and Loose connective tissue Right main bronchus, but their transitive closure does not hold any more: Dental pulp Right main bronchus is incor-rect, which then implies the incorrect match CSP:Dental pulp i MSH:Bronchus is found. Case 3: Matches found by direct but not by indirect matching. An example of such a match is CSP:Mesenteric artery ≡ d MSH:Mesenteric Arteries. The relation was not found indirectly because a concept Mesenteric artery does not exist in FMA, instead there are two more specific FMA:Inferior Mesenteric Artery and FMA:Superior Mesenteric Artery and one broader concept FMA:Artery. Using FMA the following indirect relations were discovered for CSP:Mesenteric artery: -CSP:Mesenteric artery i MSH:Arteries -CSP:Mesenteric artery i MSH:Mesenteric Artery, Inferior -CSP:Mesenteric artery i MSH:Mesenteric Artery, Superior</figDesc></figure>
<figure xmlns="http://www.tei-c.org/ns/1.0" type="table" xml:id="tab_0"><head></head><label></label><figDesc>Anchoring CRISP and MeSH to FMA of CRISP and MeSH. For example, CSP: Muscle movement was anchored as narrowerthan FMA: Muscle because within CRISP it is narrower-than CSP: Muscle. Figure</figDesc><table><row><cell></cell><cell>Anchoring</cell><cell>≡</cell><cell>Anchored</cell></row><row><cell></cell><cell>concepts</cell><cell></cell><cell>concepts</cell></row><row><cell>Anchoring CRISP to FMA</cell><cell>738</cell><cell cols="2">483 (65.5%) 607 1,474 730 (98.9%)</cell></row><row><cell>Anchoring MeSH to FMA</cell><cell cols="3">1,475 1,042 (70.6%) 1,545 2,227 1,462 (99.1%)</cell></row><row><cell>Fig. 3.</cell><cell></cell><cell></cell></row></table></figure>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="3" xml:id="foot_0">http://crisp.cit.nih.gov/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="4" xml:id="foot_1">http://www.nlm.nih.gov/mesh/</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="5" xml:id="foot_2">http://sig.biostr.washington.edu/projects/fm/AboutFM.html</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="6" xml:id="foot_3">The small d letter in the right upper corner means that the relation is a direct match, letter a means it is an anchor relation, and letter i means that it is an indirect match.</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="7" xml:id="foot_4">X C , X M , X F stand for an arbitrary concept from CRISP, MeSH and FMA respectively</note>
			<note xmlns="http://www.tei-c.org/ns/1.0" place="foot" n="8" xml:id="foot_5">http://wikipedia.org/</note>
		</body>
		<back>
			<div type="references">

				<listBibl>

<biblStruct xml:id="b0">
	<analytic>
		<title level="a" type="main">Falcon-ao: Aligning ontologies with falcon</title>
		<author>
			<persName><forename type="first">N</forename><surname>Jian</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Hu</surname></persName>
		</author>
		<author>
			<persName><forename type="first">G</forename><surname>Cheng</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Qu</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">K-Cap 2005 Workshop on Integrating Ontologies</title>
				<imprint>
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b1">
	<analytic>
		<title level="a" type="main">A Survey of Approaches to Automatic Schema Matching</title>
		<author>
			<persName><forename type="first">E</forename><surname>Rahm</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><forename type="middle">A</forename><surname>Bernstein</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">VLDB Journal</title>
		<imprint>
			<biblScope unit="volume">10</biblScope>
			<biblScope unit="issue">4</biblScope>
			<date type="published" when="2001">2001</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b2">
	<analytic>
		<title level="a" type="main">Foam -framework for ontology alignment and mapping; results of the ontology alignment initiative</title>
		<author>
			<persName><forename type="first">M</forename><surname>Ehrig</surname></persName>
		</author>
		<author>
			<persName><forename type="first">Y</forename><surname>Sure</surname></persName>
		</author>
		<ptr target=".org" />
	</analytic>
	<monogr>
		<title level="m">Proceedings of the Workshop on Integrating Ontologies</title>
				<editor>
			<persName><forename type="first">B</forename><surname>Ashpole</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">M</forename><surname>Ehrig</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</editor>
		<editor>
			<persName><forename type="first">H</forename><surname>Stuckenschmidt</surname></persName>
		</editor>
		<meeting>the Workshop on Integrating Ontologies</meeting>
		<imprint>
			<date type="published" when="2005">2005</date>
			<biblScope unit="volume">156</biblScope>
			<biblScope unit="page" from="72" to="76" />
		</imprint>
	</monogr>
	<note type="report_type">CEUR-WS</note>
</biblStruct>

<biblStruct xml:id="b3">
	<analytic>
		<title level="a" type="main">Matching unstructured vocabularies using a background ontology</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Aleksovski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Klein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Ten Kate</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Van Harmelen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of Knowledge Engineering and Knowledge Management (EKAW)</title>
				<meeting>Knowledge Engineering and Knowledge Management (EKAW)</meeting>
		<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b4">
	<analytic>
		<title level="a" type="main">Improving ontology mapping by using web ontologies as background knowledge</title>
		<author>
			<persName><forename type="first">Z</forename><surname>Aleksovski</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Klein</surname></persName>
		</author>
		<author>
			<persName><forename type="first">W</forename><surname>Ten Kate</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Van Harmelen</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Submitted for acceptance at International Semantic Web Conference (ISWC)</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b5">
	<analytic>
		<title level="a" type="main">D4.2.1 state-of-the-art-survey on ontology merging and aligning v1</title>
		<author>
			<persName><forename type="first">J</forename><surname>De Bruijn</surname></persName>
		</author>
		<author>
			<persName><forename type="first">F</forename><surname>Martin-Recuerda</surname></persName>
		</author>
		<author>
			<persName><forename type="first">D</forename><surname>Manov</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Ehrig</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">SEKT Project deliverable D4</title>
		<imprint>
			<biblScope unit="volume">2</biblScope>
			<biblScope unit="issue">1</biblScope>
			<date type="published" when="2004">2004</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b6">
	<analytic>
		<title level="a" type="main">A survey of schema-based matching approaches</title>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">J</forename><surname>Euzenat</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="j">Journal on Data Semantics IV</title>
		<imprint>
			<biblScope unit="page" from="146" to="171" />
			<date type="published" when="2005">2005</date>
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b7">
	<analytic>
		<title level="a" type="main">S-match: an algorithm and an implementation of semantic matching</title>
		<author>
			<persName><forename type="first">F</forename><surname>Giunchiglia</surname></persName>
		</author>
		<author>
			<persName><forename type="first">P</forename><surname>Shvaiko</surname></persName>
		</author>
		<author>
			<persName><forename type="first">M</forename><surname>Yatskevich</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Proceedings of the European Semantic Web Symposium (ESWC)</title>
				<meeting>the European Semantic Web Symposium (ESWC)</meeting>
		<imprint>
			<date type="published" when="2004">2004</date>
			<biblScope unit="page" from="61" to="75" />
		</imprint>
	</monogr>
</biblStruct>

<biblStruct xml:id="b8">
	<analytic>
		<title level="a" type="main">Enriching search queries for image retreival using wordnet</title>
		<author>
			<persName><forename type="first">L</forename><surname>Hollink</surname></persName>
		</author>
	</analytic>
	<monogr>
		<title level="m">Submitted for acceptance at ISWC&apos;06</title>
				<imprint>
			<date type="published" when="2006">2006</date>
		</imprint>
	</monogr>
</biblStruct>

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