<?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: shrm, youtube&#8217;d</title>
	<atom:link href="http://www.cheezhead.com/2007/06/22/shrm2007-youtube/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.cheezhead.com/2007/06/22/shrm2007-youtube/</link>
	<description>Insight and opinion from the world of employment.</description>
	<pubDate>Sat, 19 Jul 2008 15:22:40 +0000</pubDate>
	<generator>http://wordpress.org/?v=2.5.1</generator>
		<item>
		<title>By: Sean Rehder</title>
		<link>http://www.cheezhead.com/2007/06/22/shrm2007-youtube/#comment-34808</link>
		<dc:creator>Sean Rehder</dc:creator>
		<pubDate>Sat, 23 Jun 2007 13:34:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.cheezhead.com/2007/06/22/shrm2007-youtube/#comment-34808</guid>
		<description>Joel,

I won't be at SHRM, but I think the "promoted community tag," or what ever you call it, is a great idea.  Goes along with your Wiki...I think.

The world knows that HR/Recruiting needs a standard set of terminology/definitions, perhaps you could contribute a top 10 heirarchy of "tags."  I'd suggest no more than 10...maybe even 7...then plan for subsets of those tags (TBD)....but always have those "bread crumbs" up to the top heirarchy.

Is this a stupd idea?</description>
		<content:encoded><![CDATA[<p>Joel,</p>
<p>I won&#8217;t be at SHRM, but I think the &#8220;promoted community tag,&#8221; or what ever you call it, is a great idea.  Goes along with your Wiki&#8230;I think.</p>
<p>The world knows that HR/Recruiting needs a standard set of terminology/definitions, perhaps you could contribute a top 10 heirarchy of &#8220;tags.&#8221;  I&#8217;d suggest no more than 10&#8230;maybe even 7&#8230;then plan for subsets of those tags (TBD)&#8230;.but always have those &#8220;bread crumbs&#8221; up to the top heirarchy.</p>
<p>Is this a stupd idea?</p>
]]></content:encoded>
	</item>
</channel>
</rss>
