<?xml version="1.0" standalone="yes"?>
<Paper uid="W96-0505">
  <Title>Debug EdltsCructure Newnem L.mngclmge Style Prefenmeu Tools Trust I ~ ...... t d.~.~i, oF ,.,d., I E~e~ m</Title>
  <Section position="4" start_page="17" end_page="18" type="ackno">
    <SectionTitle>
4 Demonstration
</SectionTitle>
    <Paragraph position="0"> Figure I shows part of the GIST main window during the definition of a simple pension form. Apart from the menu bar the window has three areas: the button panel on the left, followed by the outline area and the content area. By clicking on the buttons, the author can create various types of form part, including sections, text fields, and multiple choice questions; the whole form is also considered to be a form part.</Paragraph>
    <Paragraph position="1"> Each form part is presented on a single line of the model: its type is shown by a label in the outline area (e.g. Section); its content is shown by a sentence in the content area (e.g. personal details of reader). Hierarchical relationships among form parts are shown by indenting: thus the form is composed of two sections; the first section is composed of four text fields and a documentation request; and the second section is composed of a multiple choice question with five options.</Paragraph>
    <Paragraph position="2"> Each form part is characterized by a set of attributes. The most important attribute, the Content, is shown in the main window; the other attributes can be viewed by double-clicking the relevant line of the model, and include the following: * Applicability condition: A condition which determines whether a question or section applies to the form-filler - e.g. the question about the  reader's previous surname only applies to married women.</Paragraph>
    <Paragraph position="3"> * Information status: An indication of whether the requested information is obfigatory or optional. An applicable question may be optional if the requested information is inaccessible or sensitive.</Paragraph>
    <Paragraph position="4"> * Information source: An indication of where to find the requested information.</Paragraph>
    <Paragraph position="5"> All attributes are presented in a controlled natural language resembling English note form; Italian and German versions of this language are also supported. Although sometimes clumsy, sentences in this language are easily understood. To specify an attribute value, the user must create a sentence in the controlled language. Most systems using controlled languages allow users to enter sentences in free text (e.g. \[5\]); for our purposes, however, free text input is unsatisfactory because users would need training in the controlled language and might still make errors. We have therefore preferred an input mechanism in which sentences are built through a series of menu-guided choices.</Paragraph>
    <Paragraph position="6"> As an illustration, we will consider the Content attribute for the form, reader requesting retirement pension of reader. Initially, this attribute is set to the pattern \[form title\], the square brackets indicating an element to be expanded; in the interface, such elements are implemented as buttons. By clicking on the button, the user obtains a list of more specific patterns, including \[person\] requesting \[benefit\]. If selected, this becomes the current pattern in place of \[form title\]. Next; the user can click either on \[person\] or on \[benefit\] to expand the pattern further; this process continues until all expandable elements have been eliminated.</Paragraph>
    <Paragraph position="7"> When the model is complete, the panel of style settings can be edited through the Style menu, and the output languages chosen through the Language menu; after these preliminaries, another option in the Language menu can be selected in order to generate draft texts. The drafts are displayed in text editing windows, one for each language, from which they can be saved as text files. From the model in figure 1 the system will generate the text shown in figure 2 along with equivalent versions in Italian and German.</Paragraph>
  </Section>
class="xml-element"></Paper>