<?xml version="1.0" standalone="yes"?>
<Paper uid="P03-2030">
  <Title>The FrameNet Data and Software</Title>
  <Section position="3" start_page="0" end_page="0" type="metho">
    <SectionTitle>
2 Frame Semantics and FrameNet II
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
2.1 Frame Semantics in Theory and Practice
</SectionTitle>
      <Paragraph position="0"> The development of the theory of Frame Semantics began more than 25 years ago (Fillmore, 1976; Fillmore, 1977), but since 1997, thanks to two NSF grants4, we have been able to apply it in a serious way to building a lexicon which we intend to be both usable by human beings and machine-tractable, so that it can serve as a lexical database for NLP, computational lexical semantics, etc. In FrameNet II, all the data, including the definitions of frames, FEs, and LUs and all of the sentences and the annotation associated with them is stored in one relational database implemented in MySQL (Baker et al., 2003; Fillmore et al., 2001).</Paragraph>
      <Paragraph position="1"> The FrameNet public website contains an index by frame and an index by LU which links to both the lexical entry and the full annotation for each LU.</Paragraph>
      <Paragraph position="2"> The frame-to-frame relations which are now being entered in the database will be visible on the website soon.</Paragraph>
    </Section>
    <Section position="2" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
2.2 FrameNet II Data Release 1.0
</SectionTitle>
      <Paragraph position="0"> The HTML version of the data consists of all the files on the web site, so that users can set up a local copy and browse it with any web browser. It is fairly compact, less than 100 Mb in all.</Paragraph>
      <Paragraph position="1"> The plain XML version of the data consists of the following files: frames.xml This file contains the descriptions of all the 450 frames and their FEs, totaling more than 3,000. Each frame also includes information as to frame-to-frame relations.</Paragraph>
      <Paragraph position="2"> luNNN.xml There is one such file per LU (roughly 7500) which contain the example sentences and annotation (if any) for each LU.</Paragraph>
      <Paragraph position="3"> 4We are grateful to the National Science Foundation for funding the project through two grants, IRI #9618838 and ITR/HCI #0086132. We refer to these two three-year stages in the life of the project as FrameNet I and FrameNet II. relations.xml A file containing information about frame-to-frame and FE-to-FE relations and meta-relations between them.</Paragraph>
      <Paragraph position="4"> We intend to have a version of the XML that includes RDF of the DAML+OIL flavor, so that the FN frames and FEs can be related to existing ontologies and Semantic Web-aware applications can access FN data using a standard methodology.</Paragraph>
      <Paragraph position="5"> Narayanan has created such a version for the FN I data, and a new version reflecting the more complex FN II data is under construction (Narayanan et al., 2002).</Paragraph>
    </Section>
  </Section>
  <Section position="4" start_page="0" end_page="0" type="metho">
    <SectionTitle>
3 The FrameNet Software Suite
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
3.1 The FrameNet Desktop tools
</SectionTitle>
      <Paragraph position="0"> The FN software used for frame definition and annotation has been fundamentally rewritten since the demo at the LREC conference last summer (Fillmore et al., 2002a). The two major changes are (1) combining the frame editing tools and the annotation tools into a single GUI, making the interface more intuitive and (2) moving to a client-server model.</Paragraph>
      <Paragraph position="1"> In the previous version, each client accessed the database directly, which made it very difficult to avoid collisions between users, and meant that each client was large, containing a lot of the logic of the application, MySQL-specific queries, etc. In the new version, the basic modules are now the MySQL database, an application server, and one or more client processes. This has a number of advantages: (1) All the database calls are made by the server, making it much easier to avoid conflicts between users. (2) The application server contains nearly all the logic, meaning that the clients are &amp;quot;thin&amp;quot; processes, concerned mainly with the GUI. (3) The separation into client and server makes it easier to set up remote access to the FN database. (4) The increased overhead caused by the more complex architecture is at least offset by the ability to cache frequentlyrequested data on the server, making access much faster.</Paragraph>
      <Paragraph position="2"> The public FrameNet web pages contain static versions of several reports drawn from the database, notably, the lexical entry report, displaying all the valences of each LU. The working environment for the staff includes dynamic versions of these reports and several others, all written as java applets. Partially shared code makes these reports accessible within the desktop package as well.</Paragraph>
    </Section>
    <Section position="2" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
3.2 API, Library, and Utilities
</SectionTitle>
      <Paragraph position="0"> We are currently working on defining a FN API and writing libraries for accessing the database from other programs. We plan to distribute a command-line utility as a demonstration of this API.</Paragraph>
    </Section>
  </Section>
  <Section position="5" start_page="0" end_page="0" type="metho">
    <SectionTitle>
4 FrameSQL and Kernel Dependency
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
Graphs
4.1 Searching with FrameSQL
</SectionTitle>
      <Paragraph position="0"> Prof. Hiroaki Sato of Senshu University has written a web-based tool which allows users to search existing FN annotations in a variety of ways. The tool also makes conveniently available several other electronic resources such as WordNet, and other on-line dictionaries. It is especially useful for doing conventional lexicography.</Paragraph>
    </Section>
    <Section position="2" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
4.2 Kernel Dependency Graphs
</SectionTitle>
      <Paragraph position="0"> The major product of the project is the lexical database of frame descriptions and annotated sentences; although these clearly are potentially very useful in many sorts of NLP task, FrameNet (at least in its present phase) remains primarily lexicographic. Nevertheless, as a an intermediate step toward applications such as automatic text summarization, we have recently begun studying kernel dependency graphs (KDGs), which provide a sort of automatic summarization of annotated sentences.</Paragraph>
      <Paragraph position="1"> KDGs consist of a0 the predicator (verb, noun, or adjective), a0 the lexical heads of its dependents a0 the &amp;quot;marking&amp;quot; on the dependents (prepositions, complementizers, etc. if any), and a0 the FEs of the dependents.</Paragraph>
      <Paragraph position="2"> To take a simple example, (1-a), which is annotated for the target chained in the Attaching frame, could be represented as the KDG in (1-b).</Paragraph>
      <Paragraph position="3">  (1) a. [Agent Four activists] chained [Item themselves] [Goal to an oil drilling rig being towed to the Barents Sea] [Time in early August].</Paragraph>
      <Paragraph position="4">  The situation can be complicated by the presence of higher control verbs and &amp;quot;transparent&amp;quot; nouns which bring about a mismatch between the semantic head and the syntactic head of an FE (Fillmore et al., 2002b), as in (2), which should have the same KDG as (1-a).</Paragraph>
      <Paragraph position="5"> (2) [Agent Four activists] planned to chain [Item themselves] [Goal to the bottom of an oil drilling rig being towed to the Barents Sea] [Time in early August].</Paragraph>
    </Section>
  </Section>
  <Section position="6" start_page="0" end_page="0" type="metho">
    <SectionTitle>
5 Layered Annotation and Frame
</SectionTitle>
    <Paragraph position="0"/>
    <Section position="1" start_page="0" end_page="0" type="sub_section">
      <SectionTitle>
Semantic Parsing
</SectionTitle>
      <Paragraph position="0"> A large majority of FEs are annotated with a triplet of labels, one for the FE name, one for the phrase type and one for the grammatical function of the constituent with regard to the target. But the FN software allows more than three layers of annotation for a single target, for situations such as when one FE contains another (e.g. in [Agent You] 're hurting [Body part [Victim my] arms]).</Paragraph>
      <Paragraph position="1"> In addition, the FN software allows us to annotate more than one target in a sentence. A full representation of the meaning of a sentence can be built up by composing the semantics of the frames evoked by the major predicators.</Paragraph>
    </Section>
  </Section>
class="xml-element"></Paper>