<?xml version="1.0" encoding="utf-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	>
<channel>
	<title>Comments on: Tags and Term extraction</title>
	<atom:link href="http://www.theryanking.com/entries/2005/04/10/tags-and-term-extraction/feed/" rel="self" type="application/rss+xml" />
	<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/</link>
	<description>Music and Technology, but NO TECHNO!</description>
	<pubDate>Fri, 10 Feb 2012 17:42:30 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: the ryan king    &#187; Taking the Folk out of Folksonomy</title>
		<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/#comment-1547</link>
		<dc:creator>the ryan king    &#187; Taking the Folk out of Folksonomy</dc:creator>
		<pubDate>Mon, 02 Jan 2006 05:53:15 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/#comment-1547</guid>
		<description>[...] eir algorithms. 	Auto-tagging is not folkonomy. Jonas and I have been over this, remember? This post pretty much sums up my arguments against auto-tagging, though [...]</description>
		<content:encoded><![CDATA[<p>[...] eir algorithms. 	Auto-tagging is not folkonomy. Jonas and I have been over this, remember? This post pretty much sums up my arguments against auto-tagging, though [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anton&#8217;s Stuff  &#187; Blog Archive   &#187; Yahoo Terms Extraction</title>
		<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/#comment-201</link>
		<dc:creator>Anton&#8217;s Stuff  &#187; Blog Archive   &#187; Yahoo Terms Extraction</dc:creator>
		<pubDate>Tue, 12 Apr 2005 03:40:01 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/#comment-201</guid>
		<description>[...] hed plugin and see about using it on my domains. 	Another article about the Y! service at: http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/ [...]</description>
		<content:encoded><![CDATA[<p>[...] hed plugin and see about using it on my domains. 	Another article about the Y! service at: <a href="http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/" rel="nofollow">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/</a> [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: the laboratory  &#187; Blog Archive   &#187; Tags vs. Yahoo Term Extraction</title>
		<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/#comment-198</link>
		<dc:creator>the laboratory  &#187; Blog Archive   &#187; Tags vs. Yahoo Term Extraction</dc:creator>
		<pubDate>Mon, 11 Apr 2005 05:07:32 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/#comment-198</guid>
		<description>[...] plugin lets you tag your posts with terms extracted via the new service.  I found this via Ryan King who has some pretty good points to make why this isn&#8217;t  [...]</description>
		<content:encoded><![CDATA[<p>[...] plugin lets you tag your posts with terms extracted via the new service.  I found this via Ryan King who has some pretty good points to make why this isn&#8217;t  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ryan</title>
		<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/#comment-197</link>
		<dc:creator>ryan</dc:creator>
		<pubDate>Mon, 11 Apr 2005 04:31:33 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/#comment-197</guid>
		<description>Denis-
Thanks for stopping by...

I agree that the plugin is useful and interesting. The point I was trying to make is that the data that term extraction gives us is different from tags and therefore should not be mixed.

Note, Jonas has &lt;a href="http://www.jluster.org/2005/04/maybe-a-solution/" rel="nofollow"&gt;updated his solution based on my criticisms&lt;/a&gt; and I would call it progress.</description>
		<content:encoded><![CDATA[<p>Denis-<br />
Thanks for stopping by&#8230;</p>
<p>I agree that the plugin is useful and interesting. The point I was trying to make is that the data that term extraction gives us is different from tags and therefore should not be mixed.</p>
<p>Note, Jonas has <a href="http://www.jluster.org/2005/04/maybe-a-solution/" rel="nofollow">updated his solution based on my criticisms</a> and I would call it progress.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Denis de Bernardy</title>
		<link>http://theryanking.com/entries/2005/04/10/tags-and-term-extraction/#comment-196</link>
		<dc:creator>Denis de Bernardy</dc:creator>
		<pubDate>Mon, 11 Apr 2005 01:50:57 +0000</pubDate>
		<guid isPermaLink="false">http://theryanking.com/blog/archives/2005/04/10/tags-and-term-extraction/#comment-196</guid>
		<description>I think there definitly is something to do with the plugin. But I would reprocess the results some bit before using the raw results.

I see one use, too: Given a properly extracted keyword set, that I hope I'll get from my &lt;a href="http://www.semiologic.com/projects/keyword-autoextract/" rel="nofollow"&gt;keyword autoextract&lt;/a&gt; project, there would be room to create an &lt;a href="http://www.semiologic.com/projects/keyword-autoextract/" rel="nofollow"&gt;amazon autoextract&lt;/a&gt; plugin, for instance.</description>
		<content:encoded><![CDATA[<p>I think there definitly is something to do with the plugin. But I would reprocess the results some bit before using the raw results.</p>
<p>I see one use, too: Given a properly extracted keyword set, that I hope I&#8217;ll get from my <a href="http://www.semiologic.com/projects/keyword-autoextract/" rel="nofollow">keyword autoextract</a> project, there would be room to create an <a href="http://www.semiologic.com/projects/keyword-autoextract/" rel="nofollow">amazon autoextract</a> plugin, for instance.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

