<?xml version="1.0" standalone="yes"?>
<Paper uid="P05-3008">
  <Title>ID Rec Features Classifier Error rates Classification Task In domain Out Av</Title>
  <Section position="3" start_page="0" end_page="29" type="intro">
    <SectionTitle>
2 Voice-navigable procedures
</SectionTitle>
    <Paragraph position="0"> ISS procedures are formal documents that typically represent many hundreds of person hours of preparation, and undergo a strict approval process. One requirement in the Clarissa project was that the procedures should be displayed visually exactly as they  steps appear in the original PDF form. However, reading these procedures verbatim would not be very useful. The challenge is thus to let the spoken version diverge significantly from the written one, yet still be similar enough in meaning that the people who control the procedures can be convinced that the two versions are in practice equivalent.</Paragraph>
    <Paragraph position="1"> Figure 1 illustrates several types of divergences between the written and spoken versions, with &amp;quot;speech bubbles&amp;quot; showing how procedure text is actually read out. In this procedure for space suit maintenance, one to three suits can be processed. The group of steps shown cover filling of a &amp;quot;dry LCVG&amp;quot;. The system first inserts a question to ask which suits require this operation, and then reads the passage once for each suit, specifying each time which suit is being referred to; if no suits need to be processed, it jumps directly to the next section. Step 51 points the user to a subprocedure. The spoken version asks if the user wants to execute the steps of the subprocedure; if so, it opens the LCVG Water Fill procedure and goes directly to step 6. If the user subsequently goes past step 17 of the subprocedure, the system warns that the user has gone past the required steps, and suggests that they close the procedure.</Paragraph>
    <Paragraph position="2"> Other important types of divergences concern entry of data in tables, where the system reads out an appropriate question for each table cell, confirms the value supplied by the user, and if necessary warns about out-of-range values.</Paragraph>
    <Section position="1" start_page="29" end_page="29" type="sub_section">
      <SectionTitle>
Rec Patterns Errors
Reject Bad Total
</SectionTitle>
      <Paragraph position="0"> different configurations of the system.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>