<?xml version="1.0" standalone="yes"?>
<Paper uid="C94-1080">
  <Title>CONCURRENT LEXICALIZED DEPENDENCY PARSING: A BEHAVIORAL VIEW ON ParseTalk EVENTS</Title>
  <Section position="2" start_page="0" end_page="0" type="intro">
    <SectionTitle>
1 INTRODUCTION
</SectionTitle>
    <Paragraph position="0"> In this paper, we propose a grammar model that combines lexical organization of grammatical knowledge with lexicalized control of the corresponding parser in a coherent object-oriented specification framework. We build upon recent developments in the lield of linguistic grammar theory which have already yiekled a rigid lexical mod,larization, but extend thcm by assigning full procedural autonomy to lexical units. In particular, we treat lexic,'ll items as active lexieal processes commtnticating with each other by message passing. Titus, they dynamically establish heterogeneous communication lines in order to dctcnninc each lexical item's fimctional role. While the issue of lexiealize(I control has early becn invcstigatcd in the l)aradigm of conceptual parsers (e.g., Riesbcck &amp; Schank 1978), and word expell parsing in particular (Small &amp; Ricger, 1982), we here elaborate on improving ils lcxical commtmication facilities by formalizing the parscr's message passing protocol according to actor computation principles. As this protocol allows for asynchronous message passing, concurrency enters as a theoretical notion at the level of grantmar specification, not only as an implcmentational fcatttrc.</Paragraph>
    <Paragraph position="1"> Correspondingly, we introduce a behavioral description in terms of event type networks which rcpresent grammatical interrelations at the level of actor definitions, while event networks represent the I)arsing process in terms of actual messages exchanged between instantiated actors. The ParseTalk model outlined in this paper can thereft)re be considcred as an attempt to rcmedy the lack of theoretical integration of parallelism at the level of grammar design.</Paragraph>
  </Section>
class="xml-element"></Paper>