<!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>Representing Core Themes in a Biology E-Textbook</article-title>
      </title-group>
      <contrib-group>
        <contrib contrib-type="author">
          <string-name>Author</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>Vinay Chaudhri</string-name>
        </contrib>
        <contrib contrib-type="author">
          <string-name>SRI International</string-name>
          <email>dinesh@ai.sri.com</email>
        </contrib>
        <contrib contrib-type="editor">
          <string-name>Research Questions</string-name>
        </contrib>
      </contrib-group>
      <abstract>
        <p>Graduated in 2010, with a PhD in computer science (focus on logic and NLP). Working with ontologies since then. Aims and Objectives of the Research Inquire [1] is a new electronic textbook that integrates the Campbell biology textbook [2] with a reasoning system and a rich biology knowledge base (KB), allowing it to answer a variety of questions. It offers new ways for students to explore and interact with educational materials, and ultimately, improve their understanding of biology. The KB and question answering system are crucial to many of Inquire's interactive features. Subject matter experts (SMEs), who are biology teachers, encode knowledge in the KB, using the process described in [3]. A focus of our research is to provide the SMEs with modelling guidelines or patterns, so that we may systematically acquire knowledge from the textbook. In the following section, we narrow our focus to a particularly challenging class of problems -- modelling the core themes in the textbook.</p>
      </abstract>
      <kwd-group>
        <kwd>To represent a core theme</kwd>
        <kwd>we need to answer the following questions</kwd>
      </kwd-group>
    </article-meta>
  </front>
  <body>
    <sec id="sec-1">
      <title>Supervisors Vinay Chaudhri</title>
    </sec>
    <sec id="sec-2">
      <title>Affiliation SRI International E-Mail dinesh@ai.sri.com Stage</title>
      <p>4. How do we retrieve and present answers given the information in the KB?
We adopted the following steps to handle the core theme relating structure to function:
1. Requirements Specification – SMEs define the core theme in biology terms. We then
conduct a user study, where the definition of the core theme is discussed with
teachers and students. During the study, we gather questions about the core theme.
2. Design – The questions are categorized into a set of templates. We then develop
modelling vocabulary and guidelines, targeted at answering these questions.
3. Implementation -- The SMEs adopt the modelling guidelines during encoding.</p>
      <p>Algorithms to retrieve and present answers are developed. Based on the algorithms,
we can classify the questions into four types – (a) descriptions (b) similarities and
differences, (c) path-based relationships, and (d) slot-value queries.
4. Evaluation – Users (students and teachers) assess the quality of answers.</p>
      <p>Research Results to Date
We have designed and implemented a representation for the core theme relating structure to
function. An evaluation is planned in the near future. Here, we briefly describe the main
relations that used for this core theme:
1. Structure is described using a set of meronymic relations (e.g., has-part, has-region),
spatial relations (e.g., is-inside, is-outside), and properties (e.g., area, diameter).</p>
      <p>
        These relations are provided by the component library [
        <xref ref-type="bibr" rid="ref4">4</xref>
        ], our upper ontology.
2. Functions are described using the relation “has-function”. Our approach is similar in
spirit to the proposal by Burek et al [
        <xref ref-type="bibr" rid="ref5">5</xref>
        ]. However, we do not distinguish between
functions and functionings.
3. The relationship of structure to function is encoded in two ways. First, we have the
relation “facilitates” which is used to state that a sub-structure is important to the
function of a super-structure [
        <xref ref-type="bibr" rid="ref6">6</xref>
        ]. For example, the absorption of light by chlorophyll-A
is facilitated by its poryphrin ring. Second, we have qualitative relations [
        <xref ref-type="bibr" rid="ref7">7</xref>
        ], which
relate structural to functional properties. For example, the length of the loop of Henle
is directly proportional to the rate of water re-absorption.
      </p>
      <p>The SMEs are given guidelines to identify the relations based on sentences in the textbook.
To answer questions, we need to account for various subtleties in terms of the transitivity of
parts and in transferring functions from substructures to superstructures. Due to space
restrictions, we omit a discussion of these issues.</p>
    </sec>
  </body>
  <back>
    <ref-list>
      <ref id="ref1">
        <mixed-citation>
          1.
          <string-name>
            <surname>Spaulding</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Overholtzer</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pacheco</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tien</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Chaudhri</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Gunning</surname>
            ,
            <given-names>D.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>Inquire for iPad: Bringing Question-Answering AI into the Classroom</article-title>
          . In : Conference on AI in
          <string-name>
            <surname>Education</surname>
          </string-name>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref2">
        <mixed-citation>
          2.
          <string-name>
            <surname>Reece</surname>
            ,
            <given-names>J.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Urry</surname>
            ,
            <given-names>L.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Cain</surname>
            ,
            <given-names>M.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Wasserman</surname>
            ,
            <given-names>S.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Minorsky</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Jackson</surname>
            ,
            <given-names>R</given-names>
          </string-name>
          .:
          <article-title>Campbell Biology 9th edn</article-title>
          .
          <source>Pearson</source>
          (
          <year>2010</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref3">
        <mixed-citation>
          3.
          <string-name>
            <surname>Chaudhri</surname>
            ,
            <given-names>V.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Dinesh</surname>
            ,
            <given-names>N.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Pacheco</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Ng</surname>
            ,
            <given-names>G.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Goldenkranz</surname>
            ,
            <given-names>A.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Seyed</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Sharma</surname>
          </string-name>
          , N.:
          <article-title>Preliminary Steps towards a Knowledge Factory Process</article-title>
          .
          <source>In : Conference on Knowledge Capture</source>
          (
          <year>2011</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref4">
        <mixed-citation>
          4.
          <string-name>
            <surname>Barker</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Porter</surname>
            ,
            <given-names>B.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Clark</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          :
          <article-title>A Library of Generic Concepts for Composing Knowledge Bases</article-title>
          .
          <source>In : Conference on Knowledge Capture</source>
          (
          <year>2001</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref5">
        <mixed-citation>
          5.
          <string-name>
            <surname>Burek</surname>
            ,
            <given-names>P.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Hoehndorf</surname>
            ,
            <given-names>R.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Loebe</surname>
            ,
            <given-names>F.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Visagie</surname>
            ,
            <given-names>J.:</given-names>
          </string-name>
          <article-title>A top-level ontology of functions and its application in the Open Biomedical Ontologies</article-title>
          .
          <source>Bioinformatics</source>
          <volume>22</volume>
          (
          <issue>14</issue>
          ),
          <fpage>e66</fpage>
          -
          <lpage>e73</lpage>
          (
          <year>2006</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref6">
        <mixed-citation>
          6.
          <string-name>
            <surname>Umeda</surname>
            ,
            <given-names>Y.</given-names>
          </string-name>
          ,
          <string-name>
            <surname>Tomiyama</surname>
            ,
            <given-names>T.</given-names>
          </string-name>
          :
          <article-title>Functional Reasoning in Design</article-title>
          .
          <source>IEEE Expert</source>
          <volume>12</volume>
          (
          <issue>2</issue>
          ),
          <fpage>42</fpage>
          -
          <lpage>48</lpage>
          (
          <year>1997</year>
          )
        </mixed-citation>
      </ref>
      <ref id="ref7">
        <mixed-citation>
          7.
          <string-name>
            <surname>Forbus</surname>
            ,
            <given-names>K.</given-names>
          </string-name>
          :
          <source>Qualitative Process Theory. Artificial Intelligence</source>
          <volume>24</volume>
          ,
          <fpage>85</fpage>
          -
          <lpage>168</lpage>
          (
          <year>1984</year>
          )
        </mixed-citation>
      </ref>
    </ref-list>
  </back>
</article>