<?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"
	>
<channel>
	<title>Comments on: How to keep tracks with all your comments accross the blogosphere?</title>
	<atom:link href="http://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/feed/" rel="self" type="application/rss+xml" />
	<link>http://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/</link>
	<description>He does his work in mysterious ways, some people like it, some people don't.</description>
	<pubDate>Sat, 26 Jul 2008 02:06:46 +0000</pubDate>
	<generator>http://wordpress.org/?v=MU</generator>
		<item>
		<title>By: Bill</title>
		<link>http://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-40</link>
		<dc:creator>Bill</dc:creator>
		<pubDate>Sat, 12 May 2007 14:49:06 +0000</pubDate>
		<guid isPermaLink="false">https://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-40</guid>
		<description>MSN I NIIPET
&lt;a href="http://msn.com" rel="nofollow"&gt;MSN&lt;/a&gt;</description>
		<content:encoded><![CDATA[<p>MSN I NIIPET<br />
<a href="http://msn.com" rel="nofollow">MSN</a></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tony</title>
		<link>http://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-6</link>
		<dc:creator>Tony</dc:creator>
		<pubDate>Sun, 12 Feb 2006 16:44:00 +0000</pubDate>
		<guid isPermaLink="false">https://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-6</guid>
		<description>Hi botanik,
You made a good point about limitations of tag usage. However, i think the limitation you metioned is what is happening to every web application right now, not only for coComment. Lack of tag definition makes information lost, multiple definitions may lead to redundancy. Obviously, a suggestion would be: make sure you tag definiton just match.
As for the difference between search engine and tag navigation, from my point of view, the first one can be considered as full user-oriented. Suppliers of information don't particate in the information retrieval activity; Defining search terms, constructing search clause, filtrating and choosing results, all of these activities are usually done alone by searchers. As for the latter one, information suppliers initialize the first step of search acitivity (or to certain degree, browse activity). Pre-defined tags are given to navigate at the very beginning. And generally speaking, because of suppliers' more accurate cognition for the information, tags always consistent with contents.
The difference result in a point, search engine works well based on huge amount of information source, for example, if use Tag navigation for huge amount of information, the same thing is usually defined by many different tags by different suppliers; Tag navigation works more efficient when information amount is relatively limit.
In coComment context, conversations of a single user usually are not of huge amount. So I think tag navigation would work better in this context; otherwise, definition of search terms for search engine is going to be a problem for searchers; some conversation can be lost if the search terms are not defined properly. For example, if a coComment users conversation include contents of "Nano", however, there is never "iPod" show up in the conservations, what if a searcher defines a search term "iPod"? He/she will never know the record of "Nano" conservation. On the other hand, if tags are supplied, no matter "iPod" or "Nano", readers can easily get the idea.
So, in my opionion, if there is such facility added to coComment, Tag navigation should take priority, search engine can work as assistant function.
What do you think ?</description>
		<content:encoded><![CDATA[<p>Hi botanik,<br />
You made a good point about limitations of tag usage. However, i think the limitation you metioned is what is happening to every web application right now, not only for coComment. Lack of tag definition makes information lost, multiple definitions may lead to redundancy. Obviously, a suggestion would be: make sure you tag definiton just match.<br />
As for the difference between search engine and tag navigation, from my point of view, the first one can be considered as full user-oriented. Suppliers of information don&#8217;t particate in the information retrieval activity; Defining search terms, constructing search clause, filtrating and choosing results, all of these activities are usually done alone by searchers. As for the latter one, information suppliers initialize the first step of search acitivity (or to certain degree, browse activity). Pre-defined tags are given to navigate at the very beginning. And generally speaking, because of suppliers&#8217; more accurate cognition for the information, tags always consistent with contents.<br />
The difference result in a point, search engine works well based on huge amount of information source, for example, if use Tag navigation for huge amount of information, the same thing is usually defined by many different tags by different suppliers; Tag navigation works more efficient when information amount is relatively limit.<br />
In coComment context, conversations of a single user usually are not of huge amount. So I think tag navigation would work better in this context; otherwise, definition of search terms for search engine is going to be a problem for searchers; some conversation can be lost if the search terms are not defined properly. For example, if a coComment users conversation include contents of &#8220;Nano&#8221;, however, there is never &#8220;iPod&#8221; show up in the conservations, what if a searcher defines a search term &#8220;iPod&#8221;? He/she will never know the record of &#8220;Nano&#8221; conservation. On the other hand, if tags are supplied, no matter &#8220;iPod&#8221; or &#8220;Nano&#8221;, readers can easily get the idea.<br />
So, in my opionion, if there is such facility added to coComment, Tag navigation should take priority, search engine can work as assistant function.<br />
What do you think ?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: botanik</title>
		<link>http://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-5</link>
		<dc:creator>botanik</dc:creator>
		<pubDate>Sat, 11 Feb 2006 16:21:00 +0000</pubDate>
		<guid isPermaLink="false">https://theinfor.wordpress.com/2006/02/06/how-to-keep-tracks-with-all-your-comments-accross-the-blogosphere/#comment-5</guid>
		<description>hi tony, 
I agree that tagging your posts could be a nice feature for coComment, but im not sure how much that will improve searches cause sometimes a topic you think is technology might be fitting much more and better say under culture for example..etc. I'm sure this are facts that a good search engine is able to solve but i just wanted to double check this idea. What do you think?
/bk</description>
		<content:encoded><![CDATA[<p>hi tony,<br />
I agree that tagging your posts could be a nice feature for coComment, but im not sure how much that will improve searches cause sometimes a topic you think is technology might be fitting much more and better say under culture for example..etc. I&#8217;m sure this are facts that a good search engine is able to solve but i just wanted to double check this idea. What do you think?<br />
/bk</p>
]]></content:encoded>
	</item>
</channel>
</rss>
