<?xml version="1.0" standalone="yes"?>
<Paper uid="P06-4003">
  <Title>LeXFlow: a System for Cross-fertilization of Computational Lexicons</Title>
  <Section position="7" start_page="10" end_page="11" type="concl">
    <SectionTitle>
5 Implementation Overview
</SectionTitle>
    <Paragraph position="0"> Our system is currently implemented as a web-based application where the human external agents interact with system through a web browser. All the human external agents attending the different document workflows are the users of system. Once authenticated through username and password the user accesses his workload area where the system lists all his pending documents (i.e. entries) sorted by type of flow.</Paragraph>
    <Paragraph position="1"> The system shows only the flows to which the user has access. From the workload area the user  We hypothesize a human agent, but the same role could be performed by a software agent. To this end, we are investigating the possibility of automatically exploiting the procedure described in (Ruimy and Roventini, 2005).</Paragraph>
    <Paragraph position="2">  such as: selecting and processing pending document; creating a new document; displaying a graph representing a DW of a previously created document; highlighting the current position of the document. This information is rendered as an SVG (Scalable Vector Graphics) image. Figure 5 illustrates the overall implementation of the system. null</Paragraph>
    <Section position="1" start_page="11" end_page="11" type="sub_section">
      <SectionTitle>
5.1 The Client Side: External Agent Inter-
</SectionTitle>
      <Paragraph position="0"> action The form used to process the documents is rendered with XForms. Using XForms, a browser can communicate with the server through XML documents and is capable of displaying the document with a user interface that can be defined for each type of document. A browser with XForms capabilities will receive an XML document that will be displayed according to the specified template, then it will let the user edit the document and finally it will send the modified document to the server.</Paragraph>
    </Section>
    <Section position="2" start_page="11" end_page="11" type="sub_section">
      <SectionTitle>
5.2 The Server Side
</SectionTitle>
      <Paragraph position="0"> The server-side is implemented with Apache Tomcat, Apache Cocoon and MySQL. Tomcat is used as the web server, authentication module (when the communication between the server and the client needs to be encrypted) and servlet container. Cocoon is a publishing framework that uses the power of XML. The entire functioning of Cocoon is based on one key concept: component pipelines. The pipeline connotes a series of events, which consists of taking a request as input, processing and transforming it, and then giving the desired response. MySQL is used for storing and retrieving the documents and the status of the documents.</Paragraph>
      <Paragraph position="1"> Each software agent is implemented as a webservice and the WSDL language is used to define its interface.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>