File Information
File: 05-lr/acl_arc_1_sum/cleansed_text/xml_by_section/concl/85/p85-1029_concl.xml
Size: 1,934 bytes
Last Modified: 2025-10-06 13:56:05
<?xml version="1.0" standalone="yes"?> <Paper uid="P85-1029"> <Title>DESCRIPTION STR.ATEGIE.S FOR NAIVE AND EXPERT USERS</Title> <Section position="9" start_page="243" end_page="243" type="concl"> <SectionTitle> CONCLUSION </SectionTitle> <Paragraph position="0"> It is important to tailor a system's response to the level of expertme of the user. By studying texts aimed at two different levels of readers, we have found that two different strategies were used in describing physical objects, depending on whether the description was for an adult or for a junior. For an adult, an object is described with its sub-parts and their properties; for a junior, the description traces through the mechanical process which renders the object functional.</Paragraph> <Paragraph position="1"> The two strategies presented account for the mare differences found between the adult and jumor entries. This turns out not to consist of merely glving more details for the expert ~ m often thought \[Wallis and Shortliffe 82\]. \[n the adult entries, details given are mainly about the sub-parts and thelr properties and less about the mechanical process involved. When the process mechanism is mentioned at all, it is done very briefly. In the iumor entries, process mechanism m more important than sub-parts and given in more detail. Parts are introduced either alter or at the same time as their function is defined, and, as a consequence, are always defined when presented.</Paragraph> <Paragraph position="2"> Furthermore, since the process mechanism follows every step of the causal chain, descriptions for the novice tend to include more detail about functional reformation than descriptions for the expert. We have shown how formalization of the strategies allows for the development of question-answering systems which can tailor their responses to the user, given his level of expertise about the domaml2</Paragraph> </Section> class="xml-element"></Paper>