<?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: Category Mistake</title>
	<atom:link href="http://www.plannedobsolescence.net/category-mistake/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.plannedobsolescence.net/category-mistake/</link>
	<description>falling indelibly into the past</description>
	<pubDate>Sun, 20 Jul 2008 01:30:34 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.6</generator>
		<item>
		<title>By: Francois Lachance</title>
		<link>http://www.plannedobsolescence.net/category-mistake/#comment-635</link>
		<dc:creator>Francois Lachance</dc:creator>
		<pubDate>Mon, 07 Nov 2005 21:17:42 +0000</pubDate>
		<guid isPermaLink="false">http://www.new.plannedobsolescence.net/?p=327#comment-635</guid>
		<description>&lt;p&gt;Kathleen, 
&lt;/p&gt;
&lt;p&gt;
Batch processing would have to be based on the categories currently present in combination with some sort of natural language processing to pick up keywords. That could lead to some interesting metadata creation. 
&lt;/p&gt;
&lt;p&gt;
Perhaps another tack may help you find greater satisfaction. Q. Do all 680 some messages need category makeovers? If so breaking the task into stages might make it manageable for a human being. Given your tree of categories, is there one category in particular that in your opinion requires work? Start there. Do one entry a day. Or limit yourself to a one hour session per week. Report back on the blog in a highly pomo self reflexive fashion on the results. Move on to the next category. 680 is a finite number. 
&lt;/p&gt;
&lt;p&gt;
I suspect you are also considering the backlog that might accumulate if you don&#8217;t use your category tree on entries you create henceforth. This entry, for example, &#8220;Category Mistake&#8221; mihgt fit under &#8220;to do&#8221; which is nicely empty at the moment or may it belongs under &#8220;uncategorizable&#8221; which provides a lovely set of paradoxes: labeled, it is categorized. 
&lt;/p&gt;
&lt;p&gt;
Of course some of your readers could volunteer to read through your entries, with an eye on the category tree you have developed, and make suggestions. Your blog could be adopted by an information sciences class.
&lt;/p&gt;
</description>
		<content:encoded><![CDATA[<p>Kathleen,
</p>
<p>
Batch processing would have to be based on the categories currently present in combination with some sort of natural language processing to pick up keywords. That could lead to some interesting metadata creation.
</p>
<p>
Perhaps another tack may help you find greater satisfaction. Q. Do all 680 some messages need category makeovers? If so breaking the task into stages might make it manageable for a human being. Given your tree of categories, is there one category in particular that in your opinion requires work? Start there. Do one entry a day. Or limit yourself to a one hour session per week. Report back on the blog in a highly pomo self reflexive fashion on the results. Move on to the next category. 680 is a finite number.
</p>
<p>
I suspect you are also considering the backlog that might accumulate if you don&#8217;t use your category tree on entries you create henceforth. This entry, for example, &#8220;Category Mistake&#8221; mihgt fit under &#8220;to do&#8221; which is nicely empty at the moment or may it belongs under &#8220;uncategorizable&#8221; which provides a lovely set of paradoxes: labeled, it is categorized.
</p>
<p>
Of course some of your readers could volunteer to read through your entries, with an eye on the category tree you have developed, and make suggestions. Your blog could be adopted by an information sciences class.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
