<?xml version="1.0" standalone="yes"?>
<Paper uid="W00-1013">
  <Title>Document Transformations and Information States</Title>
  <Section position="3" start_page="0" end_page="0" type="intro">
    <SectionTitle>
1 Introduction
</SectionTitle>
    <Paragraph position="0"> Document transformations is becoming a hot topic in industrial research on document creation. The reason is practical: with the new presentation possibilities, the advantages of being able to adapt the 'same' document content to different uses - where the difference can lie in the support devices, audiences, languages or modes of interaction - becomes very attractive. It not only becomes attractive, it also becomes necessary: one needs to present material in various contexts (oral presentatious, internet portals, etc.) and it is very costly to develop presentations from scratch for these various contexts.</Paragraph>
    <Paragraph position="1"> This situation raises an old question and opens a new area of research: can one separate content from presentation? The philosophical answer might be 'no', but in practice one doesn't need an absolute answer. As this area of research arises more out of practical necessity than pure intellectual curiosity, the</Paragraph>
    <Paragraph position="3"> www. ling. gu. se/research/proj ec~s/trindi/ engineering is preceding the science and it will take some time before it rest on explicit solid foundations.</Paragraph>
    <Paragraph position="4"> Here we look only at one small aspect of the problem: how can we model small changes in presentation that are due to various degrees of interactivity between participants in instructional exchanges. We start from a traditional manual and make some assumptions about minimal interactivity which are modeled through dialogue moves. We conclude that in this way we can make the presentation of the material more flexible. An important limit on the flexibility is, however, the detail with which the discourse structure of the manual encodes the task plan underlying the activity.</Paragraph>
  </Section>
class="xml-element"></Paper>