<?xml version="1.0" encoding="utf-8"?><!-- generator="wordpress/2.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Tag Team</title>
	<link>http://www.allpeers.com/blog/2005/02/02/tag-team/</link>
	<description>The official AllPeers blog</description>
	<pubDate>Sun, 12 Oct 2008 05:32:39 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.2</generator>

	<item>
		<title>By: Matt</title>
		<link>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1373</link>
		<author>Matt</author>
		<pubDate>Thu, 03 Feb 2005 17:37:07 +0000</pubDate>
		<guid>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1373</guid>
		<description>Thanks, huxing. Interestingly enough, I just read an &lt;a href="http://www.alwayson-network.com/comments.php?id=7480_0_4_0_C"&gt;article&lt;/a&gt; by Google's director of search quality where he confirms exactly that: they generally don't use webpage metadata because of the potential for gaming. However, I don't think this is a problem for the kind of scheme that I am proposing. What I would do is to take advantage of the standard meta element scheme attribute to indicate that the keywords are specifically designed to be used for del.icio.us-style tagging, like so:

&lt;pre&gt;&#60;meta name="keywords" scheme="delicious" content="p2p socialsoftware folksonomy" /&#62;&lt;/pre&gt;

We don't really care whether Google takes this information into account when doing its page ranking, but we do want to be able to query on this data if we ask to do so explicitly. In other words, some unscrupulous person could put a bunch of inaccurate tags into their page, but they wouldn't have much to gain since the order in which pages are displayed when someone searches for these tags would depend on the normal Google page rank, which would be unaffected by this choice of tags.</description>
		<content:encoded><![CDATA[<p>Thanks, huxing. Interestingly enough, I just read an <a href="http://www.alwayson-network.com/comments.php?id=7480_0_4_0_C">article</a> by Google&#8217;s director of search quality where he confirms exactly that: they generally don&#8217;t use webpage metadata because of the potential for gaming. However, I don&#8217;t think this is a problem for the kind of scheme that I am proposing. What I would do is to take advantage of the standard meta element scheme attribute to indicate that the keywords are specifically designed to be used for del.icio.us-style tagging, like so:</p>
<pre>&lt;meta name="keywords" scheme="delicious" content="p2p socialsoftware folksonomy" /&gt;</pre>
<p>We don&#8217;t really care whether Google takes this information into account when doing its page ranking, but we do want to be able to query on this data if we ask to do so explicitly. In other words, some unscrupulous person could put a bunch of inaccurate tags into their page, but they wouldn&#8217;t have much to gain since the order in which pages are displayed when someone searches for these tags would depend on the normal Google page rank, which would be unaffected by this choice of tags.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: huxing</title>
		<link>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1371</link>
		<author>huxing</author>
		<pubDate>Thu, 03 Feb 2005 16:22:24 +0000</pubDate>
		<guid>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1371</guid>
		<description>i hope this happened if it is that good thing. but i gether that searchengine like google are not weighted meta tag at all because seo abuse. so, many people are not bother to think meta tag keywords. i like a combination of liquid (by http://www.liquidinformation.org/index-fr.html) +delicious (demonstlated by http://www.hackdiary.com/misc/firefox-delicious-demo.html) +Wikiproxy (demonstlated by http://www.whitelabel.org/archives/002248.html) wrapper, so that one word are possess more than one tag to refere or link.</description>
		<content:encoded><![CDATA[<p>i hope this happened if it is that good thing. but i gether that searchengine like google are not weighted meta tag at all because seo abuse. so, many people are not bother to think meta tag keywords. i like a combination of liquid (by <a href="http://www.liquidinformation.org/index-fr.html" rel="nofollow">http://www.liquidinformation.org/index-fr.html</a>) +delicious (demonstlated by <a href="http://www.hackdiary.com/misc/firefox-delicious-demo.html" rel="nofollow">http://www.hackdiary.com/misc/firefox-delicious-demo.html</a>) +Wikiproxy (demonstlated by <a href="http://www.whitelabel.org/archives/002248.html" rel="nofollow">http://www.whitelabel.org/archives/002248.html</a>) wrapper, so that one word are possess more than one tag to refere or link.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: scruss</title>
		<link>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1370</link>
		<author>scruss</author>
		<pubDate>Thu, 03 Feb 2005 16:15:05 +0000</pubDate>
		<guid>http://www.allpeers.com/blog/2005/02/02/tag-team/#comment-1370</guid>
		<description>I don't think the BBC has the time or resources to add tagging, especially since it's still at the "internet fad" stage. They've got to justify everything they spend these days, and money is tight.

Anyway, this simplistic tagging scheme has serious bugs. It doesn't deal well with synonyms, f'rinstance &lt;a href="http://www.applejournal.com/gal022.htm"&gt;apple&lt;/a&gt; and &lt;a href="http://home.bawue.de/~wmwerner/essling/english/glas01.html"&gt;windows&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>I don&#8217;t think the BBC has the time or resources to add tagging, especially since it&#8217;s still at the &#8220;internet fad&#8221; stage. They&#8217;ve got to justify everything they spend these days, and money is tight.</p>
<p>Anyway, this simplistic tagging scheme has serious bugs. It doesn&#8217;t deal well with synonyms, f&#8217;rinstance <a href="http://www.applejournal.com/gal022.htm">apple</a> and <a href="http://home.bawue.de/~wmwerner/essling/english/glas01.html">windows</a>.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
