<?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:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Comments on: UIEtips: Social Tagging and the Enterprise &#8211; Does Tagging Work at Work?</title>
	<atom:link href="http://www.uie.com/brainsparks/2010/03/01/uietips-social_tagging/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.uie.com/brainsparks/2010/03/01/uietips-social_tagging/</link>
	<description>UIE\'s latest insights on the world of design</description>
	<lastBuildDate>Sat, 25 May 2013 00:51:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.4.1</generator>
	<item>
		<title>By: Larry Irons</title>
		<link>http://www.uie.com/brainsparks/2010/03/01/uietips-social_tagging/comment-page-1/#comment-150123</link>
		<dc:creator>Larry Irons</dc:creator>
		<pubDate>Mon, 08 Mar 2010 16:50:32 +0000</pubDate>
		<guid isPermaLink="false">http://www.uie.com/brainsparks/?p=1578#comment-150123</guid>
		<description>It really comes down to the difference between tagging for collective understanding and tagging for collaborative understanding in the Long Tail. As I noted in a post a couple of years ago in a post on Thomas Vander Wal&#039;s distinction between collective and collaborative understanding:

&quot;The value of a collective understanding, such as folksonomy, is that it aggregates across what Chris Anderson calls The Long Tail with little to no bias towards the tall end, what Chris refers to as the short head, since people are not second guessing their concept of the object they tag; they aren’t “fitting” their tag to the understandings of others, or how others value the object...

Alternatively, collaborative understanding, where the person doing the tagging does so while keeping the fit of their tags to the tags of others in mind, biases the aggregation process towards the short head of the long tail in relation to the value of the idea or concept of the object...The importance of the distinction, as Thomas clearly sees, is in its overall relationship and use by organizations, especially those attempting to implement Enterprise 2.0.&quot;

http://skilfulminds.com/2008/04/30/collective-tags-collaborative-tags-the-long-tail-and-enterprise-20/</description>
		<content:encoded><![CDATA[<p>It really comes down to the difference between tagging for collective understanding and tagging for collaborative understanding in the Long Tail. As I noted in a post a couple of years ago in a post on Thomas Vander Wal&#8217;s distinction between collective and collaborative understanding:</p>
<p>&#8220;The value of a collective understanding, such as folksonomy, is that it aggregates across what Chris Anderson calls The Long Tail with little to no bias towards the tall end, what Chris refers to as the short head, since people are not second guessing their concept of the object they tag; they aren’t “fitting” their tag to the understandings of others, or how others value the object&#8230;</p>
<p>Alternatively, collaborative understanding, where the person doing the tagging does so while keeping the fit of their tags to the tags of others in mind, biases the aggregation process towards the short head of the long tail in relation to the value of the idea or concept of the object&#8230;The importance of the distinction, as Thomas clearly sees, is in its overall relationship and use by organizations, especially those attempting to implement Enterprise 2.0.&#8221;</p>
<p><a href="http://skilfulminds.com/2008/04/30/collective-tags-collaborative-tags-the-long-tail-and-enterprise-20/" rel="nofollow">http://skilfulminds.com/2008/04/30/collective-tags-collaborative-tags-the-long-tail-and-enterprise-20/</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>
