<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Crowd Sourcing vs. Tribe Sourcing</title>
	<atom:link href="http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/feed/" rel="self" type="application/rss+xml" />
	<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/</link>
	<description>Mok Oh&#039;s Blog about Visual Technologies</description>
	<lastBuildDate>Fri, 20 Apr 2012 01:55:51 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Şi totuşi&#8230; ce e Tribe Sourcing-ul? &#171; dajiculidia</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-581</link>
		<dc:creator><![CDATA[Şi totuşi&#8230; ce e Tribe Sourcing-ul? &#171; dajiculidia]]></dc:creator>
		<pubDate>Sat, 17 Dec 2011 22:01:58 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-581</guid>
		<description><![CDATA[[...] Sursă http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/ Share this:TwitterFacebookLike this:LikeBe the first to like this post. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Sursă http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/ Share this:TwitterFacebookLike this:LikeBe the first to like this post. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Cum se mai practică azi Tribe Sourcing-ul? &#124; LivadaruCostel</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-558</link>
		<dc:creator><![CDATA[Cum se mai practică azi Tribe Sourcing-ul? &#124; LivadaruCostel]]></dc:creator>
		<pubDate>Sat, 12 Nov 2011 12:30:50 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-558</guid>
		<description><![CDATA[[...] a colabora la îndeplinirea unei sarcini cu ambiţia de a crea o ieşire de dorit şi valoroasă. Acest concept se referă la momentul în care nu toţi sunt implicaţi într-o societate sau companie, dar s-a [...]]]></description>
		<content:encoded><![CDATA[<p>[...] a colabora la îndeplinirea unei sarcini cu ambiţia de a crea o ieşire de dorit şi valoroasă. Acest concept se referă la momentul în care nu toţi sunt implicaţi într-o societate sau companie, dar s-a [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google vs Skyhook &#171; andralatcu</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-556</link>
		<dc:creator><![CDATA[Google vs Skyhook &#171; andralatcu]]></dc:creator>
		<pubDate>Sun, 30 Oct 2011 22:23:35 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-556</guid>
		<description><![CDATA[[...] Sursa,Geolocation Wars [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Sursa,Geolocation Wars [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crowd Sourcing vs. Tribe Sourcing &#171; Learning Change</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-554</link>
		<dc:creator><![CDATA[Crowd Sourcing vs. Tribe Sourcing &#171; Learning Change]]></dc:creator>
		<pubDate>Mon, 05 Sep 2011 00:00:34 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-554</guid>
		<description><![CDATA[[...] leave a comment &#187;   Read [...]]]></description>
		<content:encoded><![CDATA[<p>[...] leave a comment &raquo;   Read [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tribe Sourcing, Crowd Sourcing, and Automation &#171; All Things Visual</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-144</link>
		<dc:creator><![CDATA[Tribe Sourcing, Crowd Sourcing, and Automation &#171; All Things Visual]]></dc:creator>
		<pubDate>Mon, 10 Aug 2009 18:37:25 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-144</guid>
		<description><![CDATA[[...] for very specific tasks. But when you can&#8217;t, for one reason or another, going for either crowd sourcing or tribe sourcing makes a heap of sense. This doesn&#8217;t mean that automation has no place &#8212; it means [...]]]></description>
		<content:encoded><![CDATA[<p>[...] for very specific tasks. But when you can&#8217;t, for one reason or another, going for either crowd sourcing or tribe sourcing makes a heap of sense. This doesn&#8217;t mean that automation has no place &#8212; it means [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Crowd-Generated Content (CGC): What Is It? &#171; All Things Visual</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-121</link>
		<dc:creator><![CDATA[Crowd-Generated Content (CGC): What Is It? &#171; All Things Visual]]></dc:creator>
		<pubDate>Fri, 31 Jul 2009 03:46:42 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-121</guid>
		<description><![CDATA[[...] fact, I will argue (in the following blogs) that we first need Tribe-Generated Content first (a la Tribe Sourcing), then Crowd-Generated Content to follow.  A good analogy might be that TGC is the skeleton, and [...]]]></description>
		<content:encoded><![CDATA[<p>[...] fact, I will argue (in the following blogs) that we first need Tribe-Generated Content first (a la Tribe Sourcing), then Crowd-Generated Content to follow.  A good analogy might be that TGC is the skeleton, and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mok Oh</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-71</link>
		<dc:creator><![CDATA[Mok Oh]]></dc:creator>
		<pubDate>Wed, 15 Jul 2009 05:56:28 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-71</guid>
		<description><![CDATA[Many thanks for sharing!]]></description>
		<content:encoded><![CDATA[<p>Many thanks for sharing!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Andrew Velis</title>
		<link>http://allthingsv.com/2009/07/10/crowd-sourcing-vs-tribe-sourcing/#comment-67</link>
		<dc:creator><![CDATA[Andrew Velis]]></dc:creator>
		<pubDate>Mon, 13 Jul 2009 06:28:35 +0000</pubDate>
		<guid isPermaLink="false">http://allthingsv.com/?p=188#comment-67</guid>
		<description><![CDATA[For this example I am first to think about the cost per path taken. Skyhook took a leap in gathering this data by actually sending out trucks across the U.S. to get information about geo location via Wi-Fi sniffing. That costs money. Google&#039;s approach seems much less physical and more over the internet itself. Since iron is cheap (as they say) Google probably decided to implement a infrastructure for data collecting and host it alongside their vast umbrella of growing services. For Google that was the cost effective choice.

To answer which is better, it depends. To me it depends on how much the data is worth to you. Skyhook seems to value its services based on the accuracy of their data. Google seems to be just dipping its toes in the pool to test the waters before taking a dive. Since Google doesn&#039;t rely entirely on this data it can take a more relaxed approach to data collecting.

Razume (www.razume.com) reminds me of a combined approach. They have a community that crowd sources your resume giving tips for improvement. However they also make sure that there are moderators going through resumes providing valuable contributions to someone&#039;s resume. Their approach seems to promote user interaction with the site and provide valuable substance at the same time.]]></description>
		<content:encoded><![CDATA[<p>For this example I am first to think about the cost per path taken. Skyhook took a leap in gathering this data by actually sending out trucks across the U.S. to get information about geo location via Wi-Fi sniffing. That costs money. Google&#8217;s approach seems much less physical and more over the internet itself. Since iron is cheap (as they say) Google probably decided to implement a infrastructure for data collecting and host it alongside their vast umbrella of growing services. For Google that was the cost effective choice.</p>
<p>To answer which is better, it depends. To me it depends on how much the data is worth to you. Skyhook seems to value its services based on the accuracy of their data. Google seems to be just dipping its toes in the pool to test the waters before taking a dive. Since Google doesn&#8217;t rely entirely on this data it can take a more relaxed approach to data collecting.</p>
<p>Razume (www.razume.com) reminds me of a combined approach. They have a community that crowd sources your resume giving tips for improvement. However they also make sure that there are moderators going through resumes providing valuable contributions to someone&#8217;s resume. Their approach seems to promote user interaction with the site and provide valuable substance at the same time.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

