@inproceedings{zock-schwab-2016-wordnet,
title = "{W}ord{N}et and beyond: the case of lexical access",
author = "Zock, Michael and
Schwab, Didier",
editor = "Fellbaum, Christiane and
Vossen, Piek and
Mititelu, Verginica Barbu and
Forascu, Corina",
booktitle = "Proceedings of the 8th Global WordNet Conference (GWC)",
month = "27--30 " # jan,
year = "2016",
address = "Bucharest, Romania",
publisher = "Global Wordnet Association",
url = "https://aclanthology.org/2016.gwc-1.61",
pages = "441--449",
abstract = "For humans the main functions of a dictionary is to store information concerning words and to reveal it when needed. While readers are interested in the meaning of words, writers look for answers concerning usage, spelling, grammar or word forms (lemma). We will focus here on this latter task: help authors to find the word they are looking for, word they may know but whose form is eluding them. Put differently, we try to build a resource helping authors to overcome the tip-of-the-tongue problem (ToT). Obviously, in order to access a word, it must be stored somewhere (brain, resource). Yet this is by no means sufficient. We will illustrate this here by comparing WordNet (WN) to an equivalent lexical resource bootstrapped from Wikipedia (WiPi). Both may contain a given word, but ease and success of access may be different depending on other factors like quality of the query, proximity, type of connections, etc. Next we will show under what conditions WN is suitable for word access, and finally we will present a roadmap showing the obstacles to be overcome to build a resource allowing the text producer to find the word s/he is looking for.",
}
<?xml version="1.0" encoding="UTF-8"?>
<modsCollection xmlns="http://www.loc.gov/mods/v3">
<mods ID="zock-schwab-2016-wordnet">
<titleInfo>
<title>WordNet and beyond: the case of lexical access</title>
</titleInfo>
<name type="personal">
<namePart type="given">Michael</namePart>
<namePart type="family">Zock</namePart>
<role>
<roleTerm authority="marcrelator" type="text">author</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Didier</namePart>
<namePart type="family">Schwab</namePart>
<role>
<roleTerm authority="marcrelator" type="text">author</roleTerm>
</role>
</name>
<originInfo>
<dateIssued>2016-27–30 jan</dateIssued>
</originInfo>
<typeOfResource>text</typeOfResource>
<relatedItem type="host">
<titleInfo>
<title>Proceedings of the 8th Global WordNet Conference (GWC)</title>
</titleInfo>
<name type="personal">
<namePart type="given">Christiane</namePart>
<namePart type="family">Fellbaum</namePart>
<role>
<roleTerm authority="marcrelator" type="text">editor</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Piek</namePart>
<namePart type="family">Vossen</namePart>
<role>
<roleTerm authority="marcrelator" type="text">editor</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Verginica</namePart>
<namePart type="given">Barbu</namePart>
<namePart type="family">Mititelu</namePart>
<role>
<roleTerm authority="marcrelator" type="text">editor</roleTerm>
</role>
</name>
<name type="personal">
<namePart type="given">Corina</namePart>
<namePart type="family">Forascu</namePart>
<role>
<roleTerm authority="marcrelator" type="text">editor</roleTerm>
</role>
</name>
<originInfo>
<publisher>Global Wordnet Association</publisher>
<place>
<placeTerm type="text">Bucharest, Romania</placeTerm>
</place>
</originInfo>
<genre authority="marcgt">conference publication</genre>
</relatedItem>
<abstract>For humans the main functions of a dictionary is to store information concerning words and to reveal it when needed. While readers are interested in the meaning of words, writers look for answers concerning usage, spelling, grammar or word forms (lemma). We will focus here on this latter task: help authors to find the word they are looking for, word they may know but whose form is eluding them. Put differently, we try to build a resource helping authors to overcome the tip-of-the-tongue problem (ToT). Obviously, in order to access a word, it must be stored somewhere (brain, resource). Yet this is by no means sufficient. We will illustrate this here by comparing WordNet (WN) to an equivalent lexical resource bootstrapped from Wikipedia (WiPi). Both may contain a given word, but ease and success of access may be different depending on other factors like quality of the query, proximity, type of connections, etc. Next we will show under what conditions WN is suitable for word access, and finally we will present a roadmap showing the obstacles to be overcome to build a resource allowing the text producer to find the word s/he is looking for.</abstract>
<identifier type="citekey">zock-schwab-2016-wordnet</identifier>
<location>
<url>https://aclanthology.org/2016.gwc-1.61</url>
</location>
<part>
<date>2016-27–30 jan</date>
<extent unit="page">
<start>441</start>
<end>449</end>
</extent>
</part>
</mods>
</modsCollection>
%0 Conference Proceedings
%T WordNet and beyond: the case of lexical access
%A Zock, Michael
%A Schwab, Didier
%Y Fellbaum, Christiane
%Y Vossen, Piek
%Y Mititelu, Verginica Barbu
%Y Forascu, Corina
%S Proceedings of the 8th Global WordNet Conference (GWC)
%D 2016
%8 27–30 jan
%I Global Wordnet Association
%C Bucharest, Romania
%F zock-schwab-2016-wordnet
%X For humans the main functions of a dictionary is to store information concerning words and to reveal it when needed. While readers are interested in the meaning of words, writers look for answers concerning usage, spelling, grammar or word forms (lemma). We will focus here on this latter task: help authors to find the word they are looking for, word they may know but whose form is eluding them. Put differently, we try to build a resource helping authors to overcome the tip-of-the-tongue problem (ToT). Obviously, in order to access a word, it must be stored somewhere (brain, resource). Yet this is by no means sufficient. We will illustrate this here by comparing WordNet (WN) to an equivalent lexical resource bootstrapped from Wikipedia (WiPi). Both may contain a given word, but ease and success of access may be different depending on other factors like quality of the query, proximity, type of connections, etc. Next we will show under what conditions WN is suitable for word access, and finally we will present a roadmap showing the obstacles to be overcome to build a resource allowing the text producer to find the word s/he is looking for.
%U https://aclanthology.org/2016.gwc-1.61
%P 441-449
Markdown (Informal)
[WordNet and beyond: the case of lexical access](https://aclanthology.org/2016.gwc-1.61) (Zock & Schwab, GWC 2016)
ACL