<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Victus Spiritus &#187; crowd sourced</title>
	<atom:link href="http://www.victusspiritus.com/tag/crowd-sourced/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.victusspiritus.com</link>
	<description>a blog by Mark Essel on web technology, startups and design philosophy</description>
	<lastBuildDate>Mon, 30 Jan 2012 19:33:20 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<atom:link rel="hub" href="http://pubsubhubbub.appspot.com"/><atom:link rel="hub" href="http://superfeedr.com/hubbub"/><cloud domain='www.victusspiritus.com' port='80' path='/?rsscloud=notify' registerProcedure='' protocol='http-post' />
		<item>
		<title>Social Tagging for a Social Browser</title>
		<link>http://www.victusspiritus.com/2010/03/23/social-tagging-for-a-social-browser/</link>
		<comments>http://www.victusspiritus.com/2010/03/23/social-tagging-for-a-social-browser/#comments</comments>
		<pubDate>Tue, 23 Mar 2010 11:11:55 +0000</pubDate>
		<dc:creator>Mark Essel</dc:creator>
				<category><![CDATA[Uncategorized]]></category>
		<category><![CDATA[crowd sourced]]></category>
		<category><![CDATA[opengardin]]></category>
		<category><![CDATA[social web]]></category>
		<category><![CDATA[victus media]]></category>

		<guid isPermaLink="false">http://www.victusspiritus.com/2010/03/23/social-tagging-for-a-social-browser/</guid>
		<description><![CDATA[<p>In the quest to design a social reader thats fun and useful, Tyler and I have previously leaned heavily on semantic entity extraction from web feeds. While useful, entity matching APIs are lossy, noisy, and can become expensive very quickly &#8230;</p>]]></description>
			<content:encoded><![CDATA[<p>In the quest to design a social reader thats fun and useful, Tyler and I have previously leaned heavily on semantic entity extraction from web feeds. While useful, entity matching APIs are lossy, noisy, and can become expensive very quickly (many thousands of dollars per month). It is our belief that between the creators and curators of content there is more than enough &#8220;human intelligence&#8221; out there to categorize media. In nearly all instances a knowledgable reader is capable of more precisely tagging content. </p>
<p><span id="more-3363"></span></p>
<p>Here are the benefits of setting up opengard.in this way:</p>
<ul>
<li>creators and curators will get virtual rewards for contributing
</li>
<li>we get over the heavy cost in automation of semantic tagging for a great number of feeds by using what&#8217;s there already and creating a framework for additional human knowledge.
</li>
<li>we can build statistical algorithms to suggest tags by learning from human decisions given content/data. I think this could be a fun project where we can leverage open source &#038; algorithms. I was thinking of starting with titles, first paragraphs, and song/video beginnings and converting them to binary arrays of &#8220;word&#8221; data. There may even be correlations between compression and content topics that are worth exploring</li>
</ul>
<div style="float:right;margin:0px 0px 0px 0px;"><a title="Post on Google Buzz" class="google-buzz-button" href="http://www.google.com/buzz/post" data-button-style="small-count" data-url="http://www.victusspiritus.com/2010/03/23/social-tagging-for-a-social-browser/"></a><script type="text/javascript" src="http://www.google.com/buzz/api/button.js"></script></div>]]></content:encoded>
			<wfw:commentRss>http://www.victusspiritus.com/2010/03/23/social-tagging-for-a-social-browser/feed/</wfw:commentRss>
		<slash:comments>4</slash:comments>
		</item>
	</channel>
</rss>

