<?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"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
	xmlns:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Hierarchy Versus Tagging: Organizing Information And How Online Marketers Can Make Millions</title>
	<atom:link href="http://onlinemarketerblog.com/2007/10/hierarchy-versus-tagging-organizing-information-and-how-online-marketers-can-make-millions/feed/" rel="self" type="application/rss+xml" />
	<link>http://onlinemarketerblog.com/2007/10/hierarchy-versus-tagging-organizing-information-and-how-online-marketers-can-make-millions/</link>
	<description>If Copyblogger and JaffeJuice had a bad-ass baby</description>
	<lastBuildDate>Thu, 18 Mar 2010 21:30:28 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Jason Hamrick</title>
		<link>http://onlinemarketerblog.com/2007/10/hierarchy-versus-tagging-organizing-information-and-how-online-marketers-can-make-millions/comment-page-1/#comment-21</link>
		<dc:creator>Jason Hamrick</dc:creator>
		<pubDate>Tue, 06 Nov 2007 15:46:13 +0000</pubDate>
		<guid isPermaLink="false">http://onlinemarketer.wordpress.com/2007/10/27/hierarchy-versus-tagging-organizing-information-and-how-online-marketers-can-make-millions/#comment-21</guid>
		<description>Nice work, DJ.

IF I read you correctly, your chief complaint with hierarchies is that they are not responsive to changes over time, but I think that here you&#039;re conflating two aspects of taxonomy systems -- the &lt;em&gt;relationship&lt;/em&gt; among terms in a lexicon, and the &lt;em&gt;origin&lt;/em&gt; of those terms.

Tagging systems aren&#039;t required to be flat and hierarchies aren&#039;t required to be closed.  Imagine the construction of hierarchies whose included terms are based on tags created by users.

In this scenario, a content producer (publisher) constructs an initial hierarchy of editorially-chosen tags based on the content of their site and make some decisions about the hierarchy (Is Egypt inside Africa or the Middle East or both?). These publishers can then open the site up to tagging by visitors, and through cloud tags and analytics can track which words are repeatedly being used by site visitors to categorize a particular piece of content. This data can inform the structure of the hierarchy -- do most people categorize an item as &quot;Egypt and Africa&quot; or &quot;Egypt and the Middle East&quot;?

Once a tag&#039;s usage has reached a certain threshold, it can be promoted from the folksonomy into the site&#039;s official lexicon and slotted into the hierarchy. Publishers can then use those recently promoted tags to categorize newly created content.

This scheme blends the best of both worlds -- it allows content owners to control how their content is being &quot;officially&quot; categorized while still allowing for users to interact and have input.

As for homophones, Google has shown us the power of disambiguation (&quot;Did you mean Britney Spears?&quot;) and through synomyn rings content producers can manage mis-spellings, homophones, and other aspects of language.</description>
		<content:encoded><![CDATA[<p>Nice work, DJ.</p>
<p>IF I read you correctly, your chief complaint with hierarchies is that they are not responsive to changes over time, but I think that here you&#8217;re conflating two aspects of taxonomy systems &#8212; the <em>relationship</em> among terms in a lexicon, and the <em>origin</em> of those terms.</p>
<p>Tagging systems aren&#8217;t required to be flat and hierarchies aren&#8217;t required to be closed.  Imagine the construction of hierarchies whose included terms are based on tags created by users.</p>
<p>In this scenario, a content producer (publisher) constructs an initial hierarchy of editorially-chosen tags based on the content of their site and make some decisions about the hierarchy (Is Egypt inside Africa or the Middle East or both?). These publishers can then open the site up to tagging by visitors, and through cloud tags and analytics can track which words are repeatedly being used by site visitors to categorize a particular piece of content. This data can inform the structure of the hierarchy &#8212; do most people categorize an item as &#8220;Egypt and Africa&#8221; or &#8220;Egypt and the Middle East&#8221;?</p>
<p>Once a tag&#8217;s usage has reached a certain threshold, it can be promoted from the folksonomy into the site&#8217;s official lexicon and slotted into the hierarchy. Publishers can then use those recently promoted tags to categorize newly created content.</p>
<p>This scheme blends the best of both worlds &#8212; it allows content owners to control how their content is being &#8220;officially&#8221; categorized while still allowing for users to interact and have input.</p>
<p>As for homophones, Google has shown us the power of disambiguation (&#8220;Did you mean Britney Spears?&#8221;) and through synomyn rings content producers can manage mis-spellings, homophones, and other aspects of language.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
