<?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: The Tagging Plan for AMO</title>
	<atom:link href="http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/feed/" rel="self" type="application/rss+xml" />
	<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/</link>
	<description>because at 3am anything sounds good</description>
	<lastBuildDate>Thu, 10 May 2012 20:52:06 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Mozilla Project Weekly Status: July 13, 2009 &#171; The Firefox Extension Guru&#8217;s Blog</title>
		<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/comment-page-1/#comment-40279</link>
		<dc:creator>Mozilla Project Weekly Status: July 13, 2009 &#171; The Firefox Extension Guru&#8217;s Blog</dc:creator>
		<pubDate>Sun, 19 Jul 2009 17:40:39 +0000</pubDate>
		<guid isPermaLink="false">http://micropipes.com/blog/?p=76#comment-40279</guid>
		<description>[...] Tagging [...]</description>
		<content:encoded><![CDATA[<p>[...] Tagging [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: l.m.orchard</title>
		<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/comment-page-1/#comment-30916</link>
		<dc:creator>l.m.orchard</dc:creator>
		<pubDate>Tue, 10 Mar 2009 15:16:45 +0000</pubDate>
		<guid isPermaLink="false">http://micropipes.com/blog/?p=76#comment-30916</guid>
		<description>@Dave: The limits are generous, and most people should never hit them.  But, they also give room for things like Machine Tags, if such a thing ever proved useful on AMO.  For example:

upcoming:event=1424682
iso:isbn=0713998393</description>
		<content:encoded><![CDATA[<p>@Dave: The limits are generous, and most people should never hit them.  But, they also give room for things like Machine Tags, if such a thing ever proved useful on AMO.  For example:</p>
<p>upcoming:event=1424682<br />
iso:isbn=0713998393</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Wil Clouser</title>
		<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/comment-page-1/#comment-30744</link>
		<dc:creator>Wil Clouser</dc:creator>
		<pubDate>Sat, 07 Mar 2009 01:28:34 +0000</pubDate>
		<guid isPermaLink="false">http://micropipes.com/blog/?p=76#comment-30744</guid>
		<description>@Dave: The numbers are arbitrary.  Delicious uses 128 and 128, Flickr has a limit of 75 tags per photo.  We just picked similar numbers.</description>
		<content:encoded><![CDATA[<p>@Dave: The numbers are arbitrary.  Delicious uses 128 and 128, Flickr has a limit of 75 tags per photo.  We just picked similar numbers.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave</title>
		<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/comment-page-1/#comment-30742</link>
		<dc:creator>Dave</dc:creator>
		<pubDate>Sat, 07 Mar 2009 01:16:47 +0000</pubDate>
		<guid isPermaLink="false">http://micropipes.com/blog/?p=76#comment-30742</guid>
		<description>Why such high limits on characters and tag count?  The whole point of tagging is to give short concise labels to help find things.  80 tags per add-on feels excessive, and a 128 char tag feels really excessive.  Tags should be words or phrases, not entire sentences.  Taken to the extreme, this means I can theoretically tag my add-on with 10kB of tagging text... which is insane.  With high limits you&#039;ll have more redundancy instead of forcing people to be concise so we can actually sort things here.

I&#039;d suggest something more on the line with 32 char/tag and 20-40 tags/add-on.</description>
		<content:encoded><![CDATA[<p>Why such high limits on characters and tag count?  The whole point of tagging is to give short concise labels to help find things.  80 tags per add-on feels excessive, and a 128 char tag feels really excessive.  Tags should be words or phrases, not entire sentences.  Taken to the extreme, this means I can theoretically tag my add-on with 10kB of tagging text&#8230; which is insane.  With high limits you&#8217;ll have more redundancy instead of forcing people to be concise so we can actually sort things here.</p>
<p>I&#8217;d suggest something more on the line with 32 char/tag and 20-40 tags/add-on.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Mozilla Add-ons Blog &#187; Blog Archive &#187; AMO Tagging plan update</title>
		<link>http://micropipes.com/blog/2009/03/06/the-tagging-plan-for-amo/comment-page-1/#comment-30732</link>
		<dc:creator>Mozilla Add-ons Blog &#187; Blog Archive &#187; AMO Tagging plan update</dc:creator>
		<pubDate>Fri, 06 Mar 2009 20:28:25 +0000</pubDate>
		<guid isPermaLink="false">http://micropipes.com/blog/?p=76#comment-30732</guid>
		<description>[...] Thanks for all your feedback. I&#8217;ve posted again with an updated AMO Tagging Plan. [...]</description>
		<content:encoded><![CDATA[<p>[...] Thanks for all your feedback. I&#8217;ve posted again with an updated AMO Tagging Plan. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

