<?xml version="1.0" standalone="yes"?>
<Paper uid="W03-1403">
  <Title>Is there a way to represent metaphors in WordNets? Insights from the Hamburg Metaphor Database</Title>
  <Section position="8" start_page="7" end_page="7" type="concl">
    <SectionTitle>
4 Conclusion
</SectionTitle>
    <Paragraph position="0"> The answer to the question whether metaphors can be represented in WordNets depends on the interpretation of metaphor.</Paragraph>
    <Paragraph position="1"> With respect to EuroWordNet, if individual lexemes with metaphorical meaning are considered, it can be stated that a lot of them are already represented by synsets that can or must be used figuratively. What is missing are relations between literal and figurative individual synsets.</Paragraph>
    <Paragraph position="2"> If a metaphor is considered as a structured mapping of one conceptual domain to another, the productivity of the envisaged index, as well as its potential to account for new metaphorical word senses, increases drastically. Unfortunately, so does also the complexity of the implementation task, for example by means of a composite metaphorical index. The analyses of two different target domains, POLITICS and SPORTS, show that at first a much more encompassing representation of the source domains, mainly events and their characteristics like parts, participants, actions and characteristics of the participants, is necessary in order to represent the domain structure. This can be achieved by encoding more instances of EWN relations like Meronymy and ROLE/INVOLVED, as well as possibly additional relations.</Paragraph>
    <Paragraph position="3"> For the time being, continuing the domain centered perspective adopted by the Hamburg Metaphor Database, the following research lines seem the most promising: 1. More clearly identify literal and figurative synsets in the mapped domains, and their linking relation.</Paragraph>
    <Paragraph position="4"> 2. Individuate elements in source domains and the conceptual-semantic relations between them.</Paragraph>
  </Section>
class="xml-element"></Paper>