<rdf:RDF xmlns:burst="http://xmlns.com/burst/0.1/" xmlns:admin="http://webns.net/mvcb/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:syn="http://purl.org/rss/1.0/modules/syndication/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" xmlns:owl="http://www.w3.org/2002/07/owl#" xmlns:cc="http://web.resource.org/cc/" xmlns:xsd="http://www.w3.org/2001/XMLSchema#" xmlns:swrc="http://swrc.ontoware.org/ontology#" xmlns:rdfs="http://www.w3.org/2000/01/rdf-schema#" xmlns="http://purl.org/rss/1.0/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#"><channel rdf:about="http://www.bibsonomy.org/burst/user/renew/nlp"><title>BibSonomy publications for /user/renew/nlp</title><link>http://www.bibsonomy.org/burst/user/renew/nlp</link><description>BibSonomy BuRST Feed for /user/renew/nlp</description><dc:date>2008-07-21T01:31:08+02:00</dc:date><items><rdf:Seq><rdf:li rdf:resource="http://www.bibsonomy.org/bibtex/2d55ef372846dae639344c4932e252ff2/renew"/><rdf:li rdf:resource="http://www.bibsonomy.org/bibtex/22d8f740fe023824a89405eaaddc4bfce/renew"/><rdf:li rdf:resource="http://www.bibsonomy.org/bibtex/297d07bfe67a320c6f764ca4b361985b3/renew"/></rdf:Seq></items></channel><item rdf:about="http://www.bibsonomy.org/bibtex/2d55ef372846dae639344c4932e252ff2/renew"><title>Special Section on Natural Language in Software Engineering</title><description>Welcome to IEEE Xplore 2.0: Special Section on Natural Language in Software Engineering</description><link>http://www.bibsonomy.org/bibtex/2d55ef372846dae639344c4932e252ff2/renew</link><dc:creator>renew</dc:creator><dc:date>2008-03-22T18:45:00+01:00</dc:date><dc:subject>nlp engineering software </dc:subject><content:encoded>&lt;span style=&#034;color:#555555;&#034;&gt;P. &lt;a href=&#034;http://www.bibsonomy.org/author/Sawyer&#034;&gt;Sawyer&lt;/a&gt;  and V. &lt;a href=&#034;http://www.bibsonomy.org/author/Gervasi&#034;&gt;Gervasi&lt;/a&gt;  &lt;/span&gt;(&lt;em&gt;2008&lt;/em&gt;)</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="http://www.bibsonomy.org/tag/nlp"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/engineering"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/software"/></rdf:Bag></taxo:topics><burst:publication><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/2d55ef372846dae639344c4932e252ff2/renew"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/2d55ef372846dae639344c4932e252ff2/renew"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#Article"/><owl:sameAs rdf:resource="http://ieeexplore.ieee.org/xpl/freeabs_all.jsp?tp=&amp;arnumber=4460889&amp;isnumber=4460888"/><swrc:date>Sat Mar 22 18:45:00 CET 2008</swrc:date><swrc:booktitle>Software, IET</swrc:booktitle><swrc:pages>1-2</swrc:pages><swrc:title>Special Section on Natural Language in Software Engineering</swrc:title><swrc:volume>2</swrc:volume><swrc:year>2008</swrc:year><swrc:keywords>nlp engineering software </swrc:keywords><swrc:abstract>Not Available</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="1751-8814" swrc:key="issn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="10.1049/iet-sen:20089034" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="P. Sawyer"/></rdf:_1><rdf:_2><swrc:Person swrc:name="V. Gervasi"/></rdf:_2></rdf:Seq></swrc:author></rdf:Description></burst:publication></item><item rdf:about="http://www.bibsonomy.org/bibtex/22d8f740fe023824a89405eaaddc4bfce/renew"><title>Analyzing and Accessing Wikipedia as a Lexical Semantic Resource</title><description>stuff from citeyoulike</description><link>http://www.bibsonomy.org/bibtex/22d8f740fe023824a89405eaaddc4bfce/renew</link><dc:creator>renew</dc:creator><dc:date>2008-02-27T00:48:49+01:00</dc:date><dc:subject>wikipedia lexical semantics nlp </dc:subject><content:encoded>&lt;span style=&#034;color:#555555;&#034;&gt;Torsten &lt;a href=&#034;http://www.bibsonomy.org/author/Zesch&#034;&gt;Zesch&lt;/a&gt;  and Iryna &lt;a href=&#034;http://www.bibsonomy.org/author/Gurevych&#034;&gt;Gurevych&lt;/a&gt;  and Max &lt;a href=&#034;http://www.bibsonomy.org/author/Mühlhäuser&#034;&gt;M&amp;#252;hlh&amp;#228;user&lt;/a&gt;  &lt;/span&gt;&lt;em&gt;Biannual Conference of the Society for Computational Linguistics and Language Technology, &lt;/em&gt;(&lt;em&gt;2007&lt;/em&gt;)</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="http://www.bibsonomy.org/tag/wikipedia"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/lexical"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/semantics"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/nlp"/></rdf:Bag></taxo:topics><burst:publication><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/22d8f740fe023824a89405eaaddc4bfce/renew"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/22d8f740fe023824a89405eaaddc4bfce/renew"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><swrc:date>Wed Feb 27 00:48:49 CET 2008</swrc:date><swrc:booktitle>Biannual Conference of the Society for Computational Linguistics and Language Technology</swrc:booktitle><swrc:school><swrc:University swrc:name="Darmstadt University of Technology"/></swrc:school><swrc:title>Analyzing and Accessing Wikipedia as a Lexical Semantic Resource</swrc:title><swrc:year>2007</swrc:year><swrc:keywords>wikipedia lexical semantics nlp </swrc:keywords><swrc:abstract>We analyze Wikipedia as a lexical semantic resource and compare it with conventional resources, such as dictionaries, thesauri, semantic wordnets, etc. Different parts of Wikipedia reflect different aspects of these resources. We show that Wikipedia contains a vast amount of knowledge about, e.g., named entities, domain specific terms, and rare word senses. If Wikipedia is to be used as a lexical semantic resource in large-scale NLP tasks, efficient programmatic access to the knowledge therein is required. We review existing access mechanisms and show that they are limited with respect to performance and the provided access functions. Therefore, we introduce a general purpose, high performance Java-based Wikipedia API that overcomes these limitations. It is available for research purposes at http://www.ukp.tu-darmstadt.de/software/WikipediaAPI.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="2348620" swrc:key="id"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="4" swrc:key="priority"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Torsten Zesch"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Iryna Gurevych"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Max Mühlhäuser"/></rdf:_3></rdf:Seq></swrc:author></rdf:Description></burst:publication></item><item rdf:about="http://www.bibsonomy.org/bibtex/297d07bfe67a320c6f764ca4b361985b3/renew"><title>You are what you say: privacy risks of public mentions</title><description>You are what you say</description><link>http://www.bibsonomy.org/bibtex/297d07bfe67a320c6f764ca4b361985b3/renew</link><dc:creator>renew</dc:creator><dc:date>2008-02-22T21:03:38+01:00</dc:date><dc:subject>nlp privacy </dc:subject><content:encoded>&lt;span style=&#034;color:#555555;&#034;&gt;Dan &lt;a href=&#034;http://www.bibsonomy.org/author/Frankowski&#034;&gt;Frankowski&lt;/a&gt;  and Dan &lt;a href=&#034;http://www.bibsonomy.org/author/Cosley&#034;&gt;Cosley&lt;/a&gt;  and Shilad &lt;a href=&#034;http://www.bibsonomy.org/author/Sen&#034;&gt;Sen&lt;/a&gt;  and Loren &lt;a href=&#034;http://www.bibsonomy.org/author/Terveen&#034;&gt;Terveen&lt;/a&gt;  and John &lt;a href=&#034;http://www.bibsonomy.org/author/Riedl&#034;&gt;Riedl&lt;/a&gt;  &lt;/span&gt;&lt;em&gt;SIGIR &#039;06: Proceedings of the 29th annual international ACM SIGIR conference on Research and development in information retrieval, &lt;/em&gt;&lt;em&gt;page565--572. &lt;/em&gt;&lt;em&gt;New York, NY, USA, &lt;/em&gt;&lt;em&gt;ACM, &lt;/em&gt;(&lt;em&gt;2006&lt;/em&gt;)</content:encoded><taxo:topics><rdf:Bag><rdf:li rdf:resource="http://www.bibsonomy.org/tag/nlp"/><rdf:li rdf:resource="http://www.bibsonomy.org/tag/privacy"/></rdf:Bag></taxo:topics><burst:publication><rdf:Description rdf:about="http://www.bibsonomy.org/bibtex/297d07bfe67a320c6f764ca4b361985b3/renew"><owl:sameAs rdf:resource="http://www.bibsonomy.org/uri/bibtex/297d07bfe67a320c6f764ca4b361985b3/renew"/><rdf:type rdf:resource="http://swrc.ontoware.org/ontology#InProceedings"/><owl:sameAs rdf:resource="http://portal.acm.org/citation.cfm?doid=1148170.1148267"/><swrc:date>Fri Feb 22 21:03:38 CET 2008</swrc:date><swrc:address>New York, NY, USA</swrc:address><swrc:booktitle>SIGIR &#039;06: Proceedings of the 29th annual international ACM SIGIR conference on Research and development in information retrieval</swrc:booktitle><swrc:pages>565--572</swrc:pages><swrc:publisher><swrc:Organization swrc:name="ACM"/></swrc:publisher><swrc:title>You are what you say: privacy risks of public mentions</swrc:title><swrc:year>2006</swrc:year><swrc:keywords>nlp privacy </swrc:keywords><swrc:abstract>In today&#039;s data-rich networked world, people express many aspects of their lives online. It is common to segregate different aspects in different places: you might write opinionated rants about movies in your blog under a pseudonym while participating in a forum or web site for scholarly discussion of medical ethics under your real name. However, it may be possible to link these separate identities, because the movies, journal articles, or authors you mention are from a sparse relation space whose properties (e.g., many items related to by only a few users) allow re-identification. This re-identification violates people&#039;s intentions to separate aspects of their life and can have negative consequences; it also may allow other privacy violations, such as obtaining a stronger identifier like name and address.This paper examines this general problem in a specific setting: re-identification of users from a public web movie forum in a private movie ratings dataset. We present three major results. First, we develop algorithms that can re-identify a large proportion of public users in a sparse relation space. Second, we evaluate whether private dataset owners can protect user privacy by hiding data; we show that this requires extensive and undesirable changes to the dataset, making it impractical. Third, we evaluate two methods for users in a public forum to protect their own privacy, suppression and misdirection. Suppression doesn&#039;t work here either. However, we show that a simple misdirection strategy works well: mention a few popular items that you haven&#039;t rated.</swrc:abstract><swrc:hasExtraField><swrc:Field swrc:value="Seattle, Washington, USA" swrc:key="location"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="1-59593-369-7" swrc:key="isbn"/></swrc:hasExtraField><swrc:hasExtraField><swrc:Field swrc:value="http://doi.acm.org/10.1145/1148170.1148267" swrc:key="doi"/></swrc:hasExtraField><swrc:author><rdf:Seq><rdf:_1><swrc:Person swrc:name="Dan Frankowski"/></rdf:_1><rdf:_2><swrc:Person swrc:name="Dan Cosley"/></rdf:_2><rdf:_3><swrc:Person swrc:name="Shilad Sen"/></rdf:_3><rdf:_4><swrc:Person swrc:name="Loren Terveen"/></rdf:_4><rdf:_5><swrc:Person swrc:name="John Riedl"/></rdf:_5></rdf:Seq></swrc:author></rdf:Description></burst:publication></item></rdf:RDF>