<?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/"
		>
<channel>
	<title>Comments on: Yummy and yummier</title>
	<atom:link href="http://tagsonomy.com/index.php/yummy-and-yummier/feed/" rel="self" type="application/rss+xml" />
	<link>http://tagsonomy.com/index.php/yummy-and-yummier/</link>
	<description>a blog on tagging</description>
	<lastBuildDate>Wed, 01 Sep 2010 01:32:45 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.8.4</generator>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Emily</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-6118</link>
		<dc:creator>Emily</dc:creator>
		<pubDate>Wed, 01 Nov 2006 13:13:06 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-6118</guid>
		<description>&lt;strong&gt;Yep&lt;/strong&gt;

                       There&#039;s no place like ~
</description>
		<content:encoded><![CDATA[<p><strong>Yep</strong></p>
<p>                       There&#8217;s no place like ~</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechCrunch &#187; Profile: DinnerBuzz</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-536</link>
		<dc:creator>TechCrunch &#187; Profile: DinnerBuzz</dc:creator>
		<pubDate>Sun, 22 Jan 2006 04:56:17 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-536</guid>
		<description>[...] king services it could become a very useful service over time. Links: Site About Tag Cloud Youâ€™re It  (â€œIt may not seem like it matters SO much now but once we start buildin [...]</description>
		<content:encoded><![CDATA[<p>[...] king services it could become a very useful service over time. Links: Site About Tag Cloud Youâ€™re It  (â€œIt may not seem like it matters SO much now but once we start buildin [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: BuzzMachine  &#187; Blog Archive   &#187; Made for the distributed world</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-147</link>
		<dc:creator>BuzzMachine  &#187; Blog Archive   &#187; Made for the distributed world</dc:creator>
		<pubDate>Mon, 18 Jul 2005 02:55:04 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-147</guid>
		<description>[...] 	 			 					I just came across Dinnerbuzz (catching up on my RSS after vacation; saw it via You&#8217;re It). Though the execution is iffy at best, the concept is close to what I&#8217;m  [...]</description>
		<content:encoded><![CDATA[<p>[...] 	 			 					I just came across Dinnerbuzz (catching up on my RSS after vacation; saw it via You&#8217;re It). Though the execution is iffy at best, the concept is close to what I&#8217;m  [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: TechCrunch</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-111</link>
		<dc:creator>TechCrunch</dc:creator>
		<pubDate>Mon, 04 Jul 2005 04:39:05 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-111</guid>
		<description>&lt;strong&gt;Profile: DinnerBuzz&lt;/strong&gt;

	Company: Dinnerbuzz
	
	Launched: June 2005
	What is it?
	Dinnerbuzz is a new service that allows users to provide feedback on restaurants, bars and coffee shops. It leverages user-provided metadata (including tagging) to allow others to easily find an...</description>
		<content:encoded><![CDATA[<p><strong>Profile: DinnerBuzz</strong></p>
<p>	Company: Dinnerbuzz</p>
<p>	Launched: June 2005<br />
	What is it?<br />
	Dinnerbuzz is a new service that allows users to provide feedback on restaurants, bars and coffee shops. It leverages user-provided metadata (including tagging) to allow others to easily find an&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: justinsmith</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-110</link>
		<dc:creator>justinsmith</dc:creator>
		<pubDate>Sat, 02 Jul 2005 07:28:52 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-110</guid>
		<description>Hi Alex,

Thanks for your thoughtful and thorough comments.  I really appreciate them.

I just wanted to let you know that the &quot;search by rating&quot; feature has now been added to all global and local tag views.  More is on the way!

Thanks again,
Justin</description>
		<content:encoded><![CDATA[<p>Hi Alex,</p>
<p>Thanks for your thoughtful and thorough comments.  I really appreciate them.</p>
<p>I just wanted to let you know that the &#8220;search by rating&#8221; feature has now been added to all global and local tag views.  More is on the way!</p>
<p>Thanks again,<br />
Justin</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Anthony Eden</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-104</link>
		<dc:creator>Anthony Eden</dc:creator>
		<pubDate>Wed, 29 Jun 2005 19:15:19 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-104</guid>
		<description>The problem with complex tag combinations is determining grouping. For example, what if I want curry and either indian or thai? It might be curry+indian&#124;thai, but do I mean (curry+indian)&#124;thai or do I mean curry+(indian&#124;thai). Does the parser need to know about grouping and if so have we exceeded the complexity levels that an average user is willing or able to support? This is my stopping point for adding complex functionality to Tagsurf.

FWIW Tagsurf has been using the /tag/foo format from day 1 along with a lot of other nice friendly URLs.</description>
		<content:encoded><![CDATA[<p>The problem with complex tag combinations is determining grouping. For example, what if I want curry and either indian or thai? It might be curry+indian|thai, but do I mean (curry+indian)|thai or do I mean curry+(indian|thai). Does the parser need to know about grouping and if so have we exceeded the complexity levels that an average user is willing or able to support? This is my stopping point for adding complex functionality to Tagsurf.</p>
<p>FWIW Tagsurf has been using the /tag/foo format from day 1 along with a lot of other nice friendly URLs.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: unquiet</title>
		<link>http://tagsonomy.com/index.php/yummy-and-yummier/comment-page-1/#comment-103</link>
		<dc:creator>unquiet</dc:creator>
		<pubDate>Wed, 29 Jun 2005 18:44:37 +0000</pubDate>
		<guid isPermaLink="false">http://tagsonomy.com/index.php/yummy-and-yummier/#comment-103</guid>
		<description>As far as apache or lighttpd-powered sites go, it&#039;s a simple matter of rewrite rules to get the tag syntax like delicious, regardless of the original setup. It looks like the DinnerBuzz people just haven&#039;t put any rewrite rules in...

The real question is... how do we support more complex tag combinations? What if I want to search for results containing &#039;curry&#039; and &#039;indian&#039; but not &#039;bangalore&#039;?

Should it be /tag/curry/indian/-bangalore ? /tag/curry+indian-bangalore ? 

Or how about searching for Thai OR Indian curry? /tag/curry/indian&#124;thai ?

Standardisation is nice, but it has to go further than just the basics, or the REAL difficulty with tag subscriptions will begin to rear its ugly head.</description>
		<content:encoded><![CDATA[<p>As far as apache or lighttpd-powered sites go, it&#8217;s a simple matter of rewrite rules to get the tag syntax like delicious, regardless of the original setup. It looks like the DinnerBuzz people just haven&#8217;t put any rewrite rules in&#8230;</p>
<p>The real question is&#8230; how do we support more complex tag combinations? What if I want to search for results containing &#8216;curry&#8217; and &#8216;indian&#8217; but not &#8216;bangalore&#8217;?</p>
<p>Should it be /tag/curry/indian/-bangalore ? /tag/curry+indian-bangalore ? </p>
<p>Or how about searching for Thai OR Indian curry? /tag/curry/indian|thai ?</p>
<p>Standardisation is nice, but it has to go further than just the basics, or the REAL difficulty with tag subscriptions will begin to rear its ugly head.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
