<?xml version="1.0" encoding="UTF-8"?><!-- generator="wordpress/1.5.2" -->
<rss version="2.0" 
	xmlns:content="http://purl.org/rss/1.0/modules/content/">
<channel>
	<title>Comments on: Some good criticisms</title>
	<link>http://www.memeticweb.org/?p=4</link>
	<description>Using MemeIDs to make a lightweight Semantic Web</description>
	<pubDate>Sat, 02 May 2026 20:11:57 +0000</pubDate>
	<generator>http://wordpress.org/?v=1.5.2</generator>

	<item>
 		<title>Comment on Some good criticisms by: matthew smillie</title>
		<link>http://www.memeticweb.org/?p=4#comment-8</link>
		<pubDate>Mon, 14 Nov 2005 04:57:09 +0000</pubDate>
		<guid>http://www.memeticweb.org/?p=4#comment-8</guid>
					<description>Bob,

I'll state it as clearly as I can: that definition of relevance is completely useless for anyone using the system, for anyone evaluating it, and for anyone maintaining it.  It leaves a gaping and obvious hole in the results: what about documents clearly relevant to a given *meme* (e.g. Harvard for the zip code example) but which don't incorporate the *meme id*, and are hence not in the results of a search?

Any sort of &quot;meme id adoption rate&quot; would reduce to the same sort of relevance judgements (which applications of the id are spam, and which aren't?), and would simply define a ceiling on an appropriately-defined recall measure - you can't get away from human-level relevance in a search system.

By relying so heavily on the meme id, you're cutting out what could be potentially the most beneficial aspect of the system, and the one that has the most resonance: the meme itself as a locus of meaning for the meme id.  What does it do in the search? What effect does it have on results? As far as I can tell, the answer to both of those questions is &quot;nothing&quot;.</description>
		<content:encoded><![CDATA[	<p>Bob,</p>
	<p>I&#8217;ll state it as clearly as I can: that definition of relevance is completely useless for anyone using the system, for anyone evaluating it, and for anyone maintaining it.  It leaves a gaping and obvious hole in the results: what about documents clearly relevant to a given *meme* (e.g. Harvard for the zip code example) but which don&#8217;t incorporate the *meme id*, and are hence not in the results of a search?</p>
	<p>Any sort of &#8220;meme id adoption rate&#8221; would reduce to the same sort of relevance judgements (which applications of the id are spam, and which aren&#8217;t?), and would simply define a ceiling on an appropriately-defined recall measure - you can&#8217;t get away from human-level relevance in a search system.</p>
	<p>By relying so heavily on the meme id, you&#8217;re cutting out what could be potentially the most beneficial aspect of the system, and the one that has the most resonance: the meme itself as a locus of meaning for the meme id.  What does it do in the search? What effect does it have on results? As far as I can tell, the answer to both of those questions is &#8220;nothing&#8221;.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Some good criticisms by: Administrator</title>
		<link>http://www.memeticweb.org/?p=4#comment-6</link>
		<pubDate>Thu, 10 Nov 2005 21:54:24 +0000</pubDate>
		<guid>http://www.memeticweb.org/?p=4#comment-6</guid>
					<description>Matthew,

Thanks for your comments and your long thoughtful post on shiftless.

Relevance has always been subjective and in the eye of the beholder. As you say, it should be in relation to a human need. We are twisting it, I know, but for memography, relevance is &quot;some human tagged this page with the meme I am looking for.&quot;

Note that we will still only have high precision and recall, since some taggers may make mistakes, there will be spammers, etc.

Perhaps we should call it &quot;relevence&quot; to distinguish it (with deference to Jacques Derrida and his &quot;differance&quot; that made such a difference, and to the &quot;Relevence of Misspelling,&quot; a topic I will address shortly). 

Bob Doyle</description>
		<content:encoded><![CDATA[	<p>Matthew,</p>
	<p>Thanks for your comments and your long thoughtful post on shiftless.</p>
	<p>Relevance has always been subjective and in the eye of the beholder. As you say, it should be in relation to a human need. We are twisting it, I know, but for memography, relevance is &#8220;some human tagged this page with the meme I am looking for.&#8221;</p>
	<p>Note that we will still only have high precision and recall, since some taggers may make mistakes, there will be spammers, etc.</p>
	<p>Perhaps we should call it &#8220;relevence&#8221; to distinguish it (with deference to Jacques Derrida and his &#8220;differance&#8221; that made such a difference, and to the &#8220;Relevence of Misspelling,&#8221; a topic I will address shortly). </p>
	<p>Bob Doyle
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Some good criticisms by: matthew smillie</title>
		<link>http://www.memeticweb.org/?p=4#comment-5</link>
		<pubDate>Tue, 08 Nov 2005 07:16:48 +0000</pubDate>
		<guid>http://www.memeticweb.org/?p=4#comment-5</guid>
					<description>I got wind of this via the SIG-IRList.

Long and rambling response: http://www.shiftless.org/archives/2005/11/memetic_web_ann.html

Summary: I think you're misapplying the recall measure (ratio of relevant documents retrieved to total relevant documents).  A good definition of &quot;relevant documents&quot; should be in relation to a particular human-level information need, not simply &quot;contains the query string&quot;.  In the terms you've defined, documents should be relevant in relation to the *meme*, not simply the meme id.  Defining relevance in terms of the meme id only shows that Google crawls regularly and indexes very rare strings.</description>
		<content:encoded><![CDATA[	<p>I got wind of this via the SIG-IRList.</p>
	<p>Long and rambling response: <a href='http://www.shiftless.org/archives/2005/11/memetic_web_ann.html' rel='nofollow'>http://www.shiftless.org/archives/2005/11/memetic_web_ann.html</a></p>
	<p>Summary: I think you&#8217;re misapplying the recall measure (ratio of relevant documents retrieved to total relevant documents).  A good definition of &#8220;relevant documents&#8221; should be in relation to a particular human-level information need, not simply &#8220;contains the query string&#8221;.  In the terms you&#8217;ve defined, documents should be relevant in relation to the *meme*, not simply the meme id.  Defining relevance in terms of the meme id only shows that Google crawls regularly and indexes very rare strings.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Some good criticisms by: shiftless</title>
		<link>http://www.memeticweb.org/?p=4#comment-4</link>
		<pubDate>Tue, 08 Nov 2005 02:44:17 +0000</pubDate>
		<guid>http://www.memeticweb.org/?p=4#comment-4</guid>
					<description>&lt;strong&gt;The Memetic Web Announcement&lt;/strong&gt;

There was an announcement for the Memetic Web broadcast today on the SIG-IRList, a moderated search and information-retrieval mailing list I subscribe to. The basic idea seems to be a compromise on the semantic web and tagging (Flickr, technorati, del....</description>
		<content:encoded><![CDATA[	<p><strong>The Memetic Web Announcement</strong></p>
	<p>There was an announcement for the Memetic Web broadcast today on the SIG-IRList, a moderated search and information-retrieval mailing list I subscribe to. The basic idea seems to be a compromise on the semantic web and tagging (Flickr, technorati, del&#8230;.
</p>
]]></content:encoded>
				</item>
	<item>
 		<title>Comment on Some good criticisms by: Kevin Marks</title>
		<link>http://www.memeticweb.org/?p=4#comment-3</link>
		<pubDate>Thu, 03 Nov 2005 07:09:03 +0000</pubDate>
		<guid>http://www.memeticweb.org/?p=4#comment-3</guid>
					<description>The point is that as the rel=&quot;tag&quot; uses a URL, you don't need to burden the tag itself with namespace paranoia.
Linking to http://www.memography.org/index.php/Memelink says that you are defining the tag via that link.
Technorati currently chooses to fold tags in different tagspaces together, but you are free to keep them distinct with your own parser.</description>
		<content:encoded><![CDATA[	<p>The point is that as the rel=&#8221;tag&#8221; uses a URL, you don&#8217;t need to burden the tag itself with namespace paranoia.<br />
Linking to <a href='http://www.memography.org/index.php/Memelink' rel='nofollow'>http://www.memography.org/index.php/Memelink</a> says that you are defining the tag via that link.<br />
Technorati currently chooses to fold tags in different tagspaces together, but you are free to keep them distinct with your own parser.
</p>
]]></content:encoded>
				</item>
</channel>
</rss>
