<?xml version="1.0" standalone="yes"?>
<Paper uid="W06-1910">
  <Title>Experiments Adapting an Open-Domain Question Answering System to the Geographical Domain Using Scope-Based Resources</Title>
  <Section position="3" start_page="69" end_page="69" type="intro">
    <SectionTitle>
2 Restricted Domain QA Systems
</SectionTitle>
    <Paragraph position="0"> RDQAs present some characteristics that prevent us from a direct use of ODQA systems. The most important differences are: * Usually, for RDQA, the answers are searched in relatively small domain specific collections, so methods based on exploiting the redundancy of answers in several documents are not useful. Furthermore, a highly accurate Passage Retrieval module is required because frequently the answer occurs in a very small set of passages.</Paragraph>
    <Paragraph position="1"> * RDQAs are frequently task-based. So, the repertory of question patterns is limited allowing a good accuracy in Question Processing with limited effort.</Paragraph>
    <Paragraph position="2"> * User requirements regarding the quality of the answer tend to be higher in RDQA. As (Chung et al., 2004) pointed out, no answer is preferred to a wrong answer.</Paragraph>
    <Paragraph position="3"> * In RDQA not only NEs but also domain specific terminology plays a central role. This fact usually implies that domain specific lexicons and gazetteers have to be used.</Paragraph>
    <Paragraph position="4"> * In some cases, as in GD, many documents included in the collections are far to be standard NL texts but contain tables, lists, ill-formed sentences, etc. sometimes following a more or less defined structure. Thus, extraction systems based, as our, on the linguistic structure of the sentences have to be relaxed in some way to deal with this kind of texts.</Paragraph>
    <Paragraph position="5"> More information about RDQA systems can be found in the ACL 2004 Workshop on QA in Restricted Domains1 and the AAAI 2005 Worshop on Question Answering in Restricted Domains (Molla and Vicedo, 2005) .</Paragraph>
  </Section>
class="xml-element"></Paper>