<!DOCTYPE article PUBLIC "-//NLM//DTD JATS (Z39.96) Journal Archiving and Interchange DTD v1.0 20120330//EN" "JATS-archivearticle1.dtd">
<article xmlns:xlink="http://www.w3.org/1999/xlink">
  <front>
    <journal-meta />
    <article-meta>
      <title-group>
        <article-title>Ontology Refinement System for Improving Consistency of Classification among Brother Concepts</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Takeshi Masuda</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kouji Kozaki</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Kazunori Komatani</string-name>
          <xref ref-type="aff" rid="aff0">0</xref>
          <xref ref-type="aff" rid="aff1">1</xref>
        </contrib>
        <aff id="aff0">
          <label>0</label>
          <institution>Similarity among Is-a Hierarchies</institution>
        </aff>
        <aff id="aff1">
          <label>1</label>
          <institution>The Institute of Scientific and Industrial Research, Osaka University</institution>
        </aff>
      </contrib-group>
      <abstract>
        <p>The consistency of classification is an indicator of ontologies' quality. In this paper, we focus on the consistency among brother concepts and develop a refinement system that finds inconsistent parts from a target ontology and propose methods to make such parts consistent. To find inconsistent parts and make proposals, the system compares a slot hierarchy and other two hierarchies that have reference relationship to the slot hierarchy.</p>
      </abstract>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Introduction</title>
      <p>2.1</p>
      <p>In order to develop a refinement method, we focus on an ontology development
guideline that “Each subclass of a super class is distinguished by the values of exactly
one attribute of the super class. [4]”, and found the interesting characteristic of among
is-a hierarchies under the guideline. We found that conceptual structures are similar to
other is-a hierarchies in ontologies which follow the guideline. For example, in Fig.1,
these 3 hierarchies, “Basic Concept Hierarchy”, “Slot Hierarchy” and “Referred
Concept Hierarchy”, are following guideline and then their structure are similar. In this
paper, our refinement system compare these 3 hierarchies and detect un-similar parts
as a refinement candidates and make proposals to add new concepts for each candidates.
Basic Concept Hierarchy
Carriage</p>
      <p>Movement
Space</p>
      <p>Natural Area
Natural Area</p>
      <p>Vehicle</p>
      <p>Movement </p>
      <p>Space
Airplane</p>
      <p>Movement 
Space</p>
      <p>Ground</p>
      <p>Air
Ground</p>
      <p>Air
Slot Hierarchy</p>
      <p>Reference
Referred Concept Hierarchy</p>
      <p>In our previous method [5], we compared 3 hierarchies but it is only use super-sub
relations whereas in this paper, we also consider comparing among brother concepts’
hierarchies. To compare these 3 hierarchies with brother concepts, we focus on “Slot
Hierarchy” as a basis. “Slot Hierarchy” consists of a certain slot “S” and its lower slots
“SLm” (m = 1 ~ M, M is a number of lower slots). These lower slots are specialized
only once from “S”. In this case, “Basic Concept Hierarchy” consists of concepts that
has slots in slot hierarchy (“B”, “BLm”), these brother concepts (“B_BRx”, x = 1~ X, X
is a number of brother concepts.) and middle concepts (“BMa”, a = 1~ A, A is a number
of middle concepts.) (Fig.2.). “Referred Concept Hierarchy” consists likewise.
2.3</p>
      <sec id="sec-1-1">
        <title>Patterns of Refinement Candidates</title>
        <p>Comparing 3 hierarchies like Fig.2, if there are no brother concepts (B_BRx, R_BRy)
that did not have (or be referred from) “Sm”, these 3 hierarchies are not similar. So we
can classify patterns of refinement candidate by existence of B_BRx or R_BRy. To sum
up, patterns of refinement candidate are the following four. (i) X &gt; 0 and Y &gt; 0, (ii) X
= 0 and Y &gt; 0, (iii) X &gt; 0 and Y = 0, (iv) X = 0 and Y = 0. (X is a number of bother
concepts in “Basic Concept Hierarchy, Y is a number of bother concepts in “Referred
Concept Hierarchy”. We do not make any proposals for (iv) because it is already
similar.)
2.4</p>
      </sec>
      <sec id="sec-1-2">
        <title>Limitations on Refinement Proposals</title>
        <p>In our refinement method, refinement proposals are 3 types as follows. A
correspondence between refinement candidates and proposals are shown at Table.1.
(a).
(b).
(c).</p>
        <p>add new Slot
add new concept to Basic Concept Hierarchy and new Slot
add new concept to Referred Concept Hierarchy and new Slot</p>
        <p>At this comparison with brother concept hierarchies, a number of refinement
proposal become enormous. Because there are much more comparison concepts in brother
concepts hierarchies than comparison among upper and lower concepts. For example,
I assume that some numbers M = 2 (lower slot of “S”), X = 40 (brother concept in basic
concept hierarchy “B_BRx”) and number of leaf concepts is 18, Y = 3 (brother concept
in referred concept hierarchy R_BRy) and number of leaf concepts is 2. This example
is X &gt; 0 and Y &gt; 0, then candidate type is (i). From table.1, all proposals, a1 ~ c1, are
suggested. Therefore total number of proposals for this example is 328. This number is
quite large to consider as refinement proposal, even this example has a few brother
concept in referred concept hierarchy. If there are same number of brother concepts in
referred concept hierarchy, a number of proposals can be over a thousand per a
candidates. For the above reasons, we consider 2 limitations on refinement proposals.
limitation1: Compare brother concepts that have same parents
limitation2: Compare brother concepts that are specialized same level.</p>
      </sec>
    </sec>
    <sec id="sec-2">
      <title>Evaluation</title>
      <sec id="sec-2-1">
        <title>Evaluation Methods</title>
        <p>
          We conducted a pre-experience to evaluate this refinement proposal method. We use
a race ontology that is made by author and this ontology contains 213 concepts. This
experience was designed to asses 2 points: (
          <xref ref-type="bibr" rid="ref1">1</xref>
          ) how many appropriate candidates are
detected and (
          <xref ref-type="bibr" rid="ref2">2</xref>
          ) how the 2 limitations work.
3.2
        </p>
      </sec>
      <sec id="sec-2-2">
        <title>Results and Discussions</title>
        <p>
          (
          <xref ref-type="bibr" rid="ref1">1</xref>
          ) How many appropriate candidates are detected.
        </p>
        <p>Table.2 shows the result. By previous method, 149 candidates are detected and 18%
are proposed correctly. While by new method, 11 candidates are detected and 63% are
proposed appropriately. Both new and previous method’s candidates are not repeated.
However average number of proposals are 1154, which is too much to consider.</p>
        <p>No limitation
Limitation 1</p>
        <p>Limitation 2
4</p>
      </sec>
    </sec>
    <sec id="sec-3">
      <title>Conclusion</title>
      <p>
        (
        <xref ref-type="bibr" rid="ref2">2</xref>
        ) How the 2 limitations work
      </p>
      <p>Table.3 shows the result. By “limitation1”, average number of proposals decreased
to 13, it is 100 times fewer than no limitation. In this case, 4 candidates still have correct
proposal under “limitation 1”, but 3 candidates cannot be proposed any suggestions..
While by “limitation 2”, average proposals also decreased to 377 but it is still enormous
to see. But it has 5 correct candidates, it is better than “limitation1”.</p>
      <p>Previous method</p>
      <p>In this paper, we focus on similarity among brother concepts’ hierarchies. However
a number of refinement proposals are drastically increased by the explosion of
combination. Then we provide 2 types of limitations to prevent this explosion. As a result, we
could improve an accuracy of proposals and suppress the number of proposals. In future
work, we consider some refinement candidates that we cannot make any proposal and
integrate the previous refinement method and the new refinement method.</p>
    </sec>
    <sec id="sec-4">
      <title>Acknowledgements</title>
      <p>This work was supported by JSPS KAKENHI Grant Numbers JP25280081,
26240033, JP24120002.</p>
      <p>JP</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1. [Sirin 07]
          <string-name>
            <surname>Sirin</surname>
            ,
            <given-names>E.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Parsia</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Grau</surname>
            ,
            <given-names>B. C.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kalyanpur</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          , and
          <string-name>
            <surname>Katz</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          :
          <article-title>Pellet: A practical owl-dl reasoner</article-title>
          ,
          <source>Web Semantics: science, services and agents on the World Wide Web</source>
          , Vol.
          <volume>5</volume>
          , No.
          <issue>2</issue>
          , pp.
          <fpage>51</fpage>
          -
          <lpage>53</lpage>
          (
          <year>2007</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2. [Horridge 11]
          <string-name>
            <surname>Horridge</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          :
          <article-title>Justification based explanation in ontologies</article-title>
          ,
          <source>PhD thesis</source>
          , University of Manchester (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3. [Noy 01]
          <string-name>
            <surname>Noy</surname>
            ,
            <given-names>N. F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sintek</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Decker</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          , Crub´ezy,
          <string-name>
            <given-names>M.</given-names>
            ,
            <surname>Fergerson</surname>
          </string-name>
          ,
          <string-name>
            <given-names>R. W.</given-names>
            , and
            <surname>Musen</surname>
          </string-name>
          ,
          <string-name>
            <surname>M. A.</surname>
          </string-name>
          :
          <article-title>Creating Semantic Web Contents with Prot´eG´e-2000, IEEE Intelligent Systems</article-title>
          , Vol.
          <volume>16</volume>
          , No.
          <issue>2</issue>
          , pp.
          <fpage>60</fpage>
          -
          <lpage>71</lpage>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4. [Mizoguchi 06]
          <article-title>Tutorial on ontological engineering - Part 2: Ontology development, tools and languages New Generation Computing</article-title>
          ,
          <string-name>
            <surname>OhmSha</surname>
          </string-name>
          &amp; Springer,
          <volume>22</volume>
          (
          <issue>1</issue>
          ), pp.
          <fpage>61</fpage>
          -
          <lpage>96</lpage>
          (
          <year>2004</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5. [Masuda 15]
          <string-name>
            <surname>Masuda</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Kozaki</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Komatani</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <article-title>Evaluation of Method to Improve Ontology Consistency based on Similarities among is-a Hierarchies in Referring Relation</article-title>
          ,
          <year>JSAI2015</year>
          ,
          <fpage>2M1</fpage>
          -
          <lpage>3</lpage>
          ,
          <year>2015</year>
          .
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>