<?xml version="1.0" standalone="yes"?>
<Paper uid="W00-1002">
  <Title>ADAM: An Architecture for xml-based Dialogue Annotation on Multiple levels</Title>
  <Section position="2" start_page="0" end_page="0" type="intro">
    <SectionTitle>
1 Introduction
</SectionTitle>
    <Paragraph position="0"> In this paper we describe the methodological assumptions and general architectural framework underlying the ADAM Corpus, which is currently being developed as part of the Italian national project SI-TAL (Autori vari, 2000) 1. Annotated dialogue corpora are of crucial importance for the development of vocal applications. Because of their cost, however, it is essential that their acquisition and annotation be designed in order to maximize their reusability as much as possible. The main assumption behind the design of the ADAM corpus is that actual reusability of corpora cruciMly depends on the strategic choices concerning the architectural design of the corpus, i.e. the way in which annotation tThe final version of the ADAM Corpus will be released by the end of 2001. A pilot set, consisting of 30 dialogues, is currently available.</Paragraph>
    <Paragraph position="1"> is organized and structured, and the way in which this is represented in a given physical format 2. Corpus reusability is traditionally seen as mainly a by-product of either corpus representativeness and degree of standardization of annotation schemes. We claim that two other requirements should be taken into account when designing and building an annotated corpus that aims at reusability, namely modularity of annotation, and use of annotation meta-schemes. The meaning of these notions, as well as the way in which they are realized by the ADAM Corpus will be described in detail throughout the paper. Section 2 introduces the corpus; section 3 focuses on ADAM: the motivations underlying its architecture are presented and the adoption of XML as mark-up language is discussed. Finally, the various annotation schemes are illustrated in section 4.</Paragraph>
  </Section>
class="xml-element"></Paper>