<?xml version="1.0" standalone="yes"?>
<Paper uid="X96-1027">
  <Title>TIPSTER-COMPATIBLE PROJECTS AT SHEFFIELD</Title>
  <Section position="3" start_page="0" end_page="121" type="intro">
    <SectionTitle>
GDM
</SectionTitle>
    <Paragraph position="0"> GDM is based on the TIPSTER document manager.</Paragraph>
    <Paragraph position="1"> It provides a central repository or server that stores all the information an LE system generates about the texts it processes. All communication between the system components goes through GDM, thereby insulating parts from each other and providing a uniform API (applications programmer interface) for manipulating the data produced by the system. 1 Benefits of this approach include the ability to exploit the maturity and efficiency of database technology, easy modelling of blackboard-type distributed control regimes (of the type proposed by \[2\]), and reduced interdependence of components.</Paragraph>
    <Paragraph position="2"> GGI GGI is a graphical launchpad for LE subsystems, and provides various facilities for testing and viewing results, and interactively assembling LE components into different system configurations. As we built Sheffield's MUC-6 entry, LaSIE \[6\], it was often the case that we were unsure of the implications for system performance of using tagger X instead of tagger Y, or gazetteer A instead of pattern matcher B. In the GGI interface, substitution of components is a point-and-click operation. This facility supports hybrid systems, ease of upgrading and open systemsstyle module interchangeability. 2 Figure 1 shows the launchpad for a MUC-6 IE system. Colours are used to indicate the status of each component with respect to the current document/collection: dark (red) components have already been run and their results are available for viewing; light (green) components have all their required inputs available and are ready to run, and grey (amber) components require a currently unavailable input before they can become runnable.</Paragraph>
  </Section>
class="xml-element"></Paper>