<?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: Why SHRM Must Reject the .jobs Amendment</title>
	<atom:link href="http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/</link>
	<description>Recruiting News, Recruiting Events, Recruiting Community, Social Recruiting</description>
	<lastBuildDate>Tue, 14 Feb 2012 01:03:49 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Open Letter to ICANN: Reject the .jobs Amendment! - ERE.net</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-28901</link>
		<dc:creator>Open Letter to ICANN: Reject the .jobs Amendment! - ERE.net</dc:creator>
		<pubDate>Thu, 15 Jul 2010 15:46:45 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-28901</guid>
		<description>[...] sanction such an arrangement or to turn it down. Regular ERE readers will remember that I wrote a post in April urging SHRM to reject the amendment, but they ultimately approved [...]</description>
		<content:encoded><![CDATA[<p>[...] sanction such an arrangement or to turn it down. Regular ERE readers will remember that I wrote a post in April urging SHRM to reject the amendment, but they ultimately approved [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Can We Learn Anything From The .JOBS TLD? &#124; Trademark Blog from IP Lab</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-25601</link>
		<dc:creator>Can We Learn Anything From The .JOBS TLD? &#124; Trademark Blog from IP Lab</dc:creator>
		<pubDate>Tue, 15 Jun 2010 21:26:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-25601</guid>
		<description>[...] Emply Media has now requested permission from ICANN to loosen up its registration practice for .JOBS, a move already criticized by some industry observers and others. [...]</description>
		<content:encoded><![CDATA[<p>[...] Emply Media has now requested permission from ICANN to loosen up its registration practice for .JOBS, a move already criticized by some industry observers and others. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric shannon</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-22069</link>
		<dc:creator>eric shannon</dc:creator>
		<pubDate>Wed, 28 Apr 2010 14:52:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-22069</guid>
		<description>After thinking .jobs over a lot more, I want to say that as a consequence of lending its name to Employ Media for the promotion of .jobs, SHRM has an obligation to prevent .jobs domain auctions or the sale of those domains through the sale of Employ Media itself. It cannot avoid damaging its constituents if it fails to do this. More background on my blog at http://www.internetinc.com/the-dot-jobs-domain-tax

-eric</description>
		<content:encoded><![CDATA[<p>After thinking .jobs over a lot more, I want to say that as a consequence of lending its name to Employ Media for the promotion of .jobs, SHRM has an obligation to prevent .jobs domain auctions or the sale of those domains through the sale of Employ Media itself. It cannot avoid damaging its constituents if it fails to do this. More background on my blog at <a href="http://www.internetinc.com/the-dot-jobs-domain-tax" rel="nofollow">http://www.internetinc.com/the-dot-jobs-domain-tax</a></p>
<p>-eric</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Phil Haynes</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21440</link>
		<dc:creator>Phil Haynes</dc:creator>
		<pubDate>Wed, 14 Apr 2010 14:32:16 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21440</guid>
		<description>Let me toss a comment in here from a job seekers perspective.  Job seekers don&#039;t need MORE job sites.  45,000 already.  Seems to me this is yet another instance of a vendors (Employ Media and Direct Employers) putting profits in the way of actually helping people get jobs.  In the example of www.siliconvalley.jobs, does anyone actually think there will ONLY be silicon valley jobs posted?  Of course not, companies around the world will post jobs here for tech talent once again confusing the market and confounding the job seekers.  Further fragmentation of the job board world guarantees more frustration for job seekers and employers but also profits.
What a shame.  I agree, SHRM needs to do something right and refuse the amendment.</description>
		<content:encoded><![CDATA[<p>Let me toss a comment in here from a job seekers perspective.  Job seekers don&#8217;t need MORE job sites.  45,000 already.  Seems to me this is yet another instance of a vendors (Employ Media and Direct Employers) putting profits in the way of actually helping people get jobs.  In the example of <a href="http://www.siliconvalley.jobs" rel="nofollow">http://www.siliconvalley.jobs</a>, does anyone actually think there will ONLY be silicon valley jobs posted?  Of course not, companies around the world will post jobs here for tech talent once again confusing the market and confounding the job seekers.  Further fragmentation of the job board world guarantees more frustration for job seekers and employers but also profits.<br />
What a shame.  I agree, SHRM needs to do something right and refuse the amendment.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric shannon</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21352</link>
		<dc:creator>eric shannon</dc:creator>
		<pubDate>Sun, 11 Apr 2010 00:20:15 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21352</guid>
		<description>@sara I think you are seeing stayawake.tv in first page results because you have not turned off &#039;Web history&#039;. Google knows you like to visit that webpage...</description>
		<content:encoded><![CDATA[<p>@sara I think you are seeing stayawake.tv in first page results because you have not turned off &#8216;Web history&#8217;. Google knows you like to visit that webpage&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Welstead</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21348</link>
		<dc:creator>Sarah Welstead</dc:creator>
		<pubDate>Sat, 10 Apr 2010 20:58:02 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21348</guid>
		<description>@eric I just went to Google, typed in &#039;stayawake&#039; (without quotes) and I see StayAwake.tv (mine) comes up #3.  And it should - I&#039;ve had that domain since 2001, so it&#039;s had plenty of time to get there.  (Though apparently I need to talk to my web genius, because the redirect from StayAwake.ca - which I didn&#039;t get my hands on til 2005 or so - doesn&#039;t seem to be working.)  

But my personal business isn&#039;t really a good example, since (a) I mostly work under my own name (Sarah Welstead), and that DOES deliver great Google results and (b) all of my clients are referrals. I don&#039;t actually accept &#039;random&#039; clients, so I don&#039;t care how findable StayAwake is from a keyword perspective (and I knew, even 10 years ago, that the chances of being found from a search for &#039;stay awake&#039; as 2 words were virtually nil).  

As a general rule, I agree with you on the desire for &#039;short, relevant, memorable&#039; keyword domains - which is why I think .jobs and other domains should be more widely available.  The more of a monopoly .com has on credibility, the worse it is for anyone who doesn&#039;t have $100k to secure (i.e. buy from a cybersquatter) a good .com domain that isn&#039;t some huge long bastardization of their company name/function.  


@David  Thanks for the clarification, and I can appreciate the concern around allowing a single 3rd party, for-profit organization to have too much control.  

However, I still think that relaxing some of the regulations would deliver a long-term benefit for everyone, because as I said, NONE of the recruiting and HR professionals I&#039;ve spoken to in the past 12 months (including some very senior, successful ones who tend to know their industry VERY well) had any clue .jobs even existed.

Maybe one of the benefits of the current hue and cry will be improved awareness...</description>
		<content:encoded><![CDATA[<p>@eric I just went to Google, typed in &#8216;stayawake&#8217; (without quotes) and I see StayAwake.tv (mine) comes up #3.  And it should &#8211; I&#8217;ve had that domain since 2001, so it&#8217;s had plenty of time to get there.  (Though apparently I need to talk to my web genius, because the redirect from StayAwake.ca &#8211; which I didn&#8217;t get my hands on til 2005 or so &#8211; doesn&#8217;t seem to be working.)  </p>
<p>But my personal business isn&#8217;t really a good example, since (a) I mostly work under my own name (Sarah Welstead), and that DOES deliver great Google results and (b) all of my clients are referrals. I don&#8217;t actually accept &#8216;random&#8217; clients, so I don&#8217;t care how findable StayAwake is from a keyword perspective (and I knew, even 10 years ago, that the chances of being found from a search for &#8216;stay awake&#8217; as 2 words were virtually nil).  </p>
<p>As a general rule, I agree with you on the desire for &#8216;short, relevant, memorable&#8217; keyword domains &#8211; which is why I think .jobs and other domains should be more widely available.  The more of a monopoly .com has on credibility, the worse it is for anyone who doesn&#8217;t have $100k to secure (i.e. buy from a cybersquatter) a good .com domain that isn&#8217;t some huge long bastardization of their company name/function.  </p>
<p>@David  Thanks for the clarification, and I can appreciate the concern around allowing a single 3rd party, for-profit organization to have too much control.  </p>
<p>However, I still think that relaxing some of the regulations would deliver a long-term benefit for everyone, because as I said, NONE of the recruiting and HR professionals I&#8217;ve spoken to in the past 12 months (including some very senior, successful ones who tend to know their industry VERY well) had any clue .jobs even existed.</p>
<p>Maybe one of the benefits of the current hue and cry will be improved awareness&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric shannon</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21340</link>
		<dc:creator>eric shannon</dc:creator>
		<pubDate>Sat, 10 Apr 2010 14:29:31 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21340</guid>
		<description>Sara, you make some good points but try searching Google for &#039;stay awake&#039;, I didn&#039;t see your site on the first three pages. Even worse, it doesn&#039;t show for &#039;stayawake&#039;. this should give you an appreciation for the common desire for short, relevant, memorable keyword domains likely to appear in search results with reasonable effort.</description>
		<content:encoded><![CDATA[<p>Sara, you make some good points but try searching Google for &#8216;stay awake&#8217;, I didn&#8217;t see your site on the first three pages. Even worse, it doesn&#8217;t show for &#8216;stayawake&#8217;. this should give you an appreciation for the common desire for short, relevant, memorable keyword domains likely to appear in search results with reasonable effort.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: David Manaster</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21334</link>
		<dc:creator>David Manaster</dc:creator>
		<pubDate>Fri, 09 Apr 2010 23:53:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21334</guid>
		<description>@Steven - I&#039;m proud of the work that John has done here as well. He&#039;s been working hard reporting on the new plans for the .jobs domain for months.

@eric - The rights that Employ Media is requesting seem so different from the rights that I see the other managers of domains exercising that I am amazed that this has not raised more eyebrows in tech and domain policy circles.

@Master - I&#039;m hoping that there was a serious discusion of exactly that in today&#039;s PDP Council meeting.

@Sarah With only about 15,000 sold, most don&#039;t consider the .jobs domain to be a commercial success. Indeed, that lack of commercial success is probably the only reason that this proposed change did not generate more outrage. If the exact same proposal would have been attempted with the .com domain, it would have been front page news in every newspaper in North America.

To be clear, the amendment considered by the SHRM PDP Council today was not ever going to open up more domains to be purchased by the general public, as you describe in the case of the .ca TLD.  In this case, Employ Media was asking SHRM to amend the charter to give them the broad ability to either sell the new domains or maintain ownership of them while still allowing other other parties to use them. Theoretically, they could use this power to allow anyone to buy them, but their announced plans were to develop all of said domains with a single partner, DirectEmployers, which sounds about as far from the opening up of the .ca domain that you describe as I can imagine.</description>
		<content:encoded><![CDATA[<p>@Steven &#8211; I&#8217;m proud of the work that John has done here as well. He&#8217;s been working hard reporting on the new plans for the .jobs domain for months.</p>
<p>@eric &#8211; The rights that Employ Media is requesting seem so different from the rights that I see the other managers of domains exercising that I am amazed that this has not raised more eyebrows in tech and domain policy circles.</p>
<p>@Master &#8211; I&#8217;m hoping that there was a serious discusion of exactly that in today&#8217;s PDP Council meeting.</p>
<p>@Sarah With only about 15,000 sold, most don&#8217;t consider the .jobs domain to be a commercial success. Indeed, that lack of commercial success is probably the only reason that this proposed change did not generate more outrage. If the exact same proposal would have been attempted with the .com domain, it would have been front page news in every newspaper in North America.</p>
<p>To be clear, the amendment considered by the SHRM PDP Council today was not ever going to open up more domains to be purchased by the general public, as you describe in the case of the .ca TLD.  In this case, Employ Media was asking SHRM to amend the charter to give them the broad ability to either sell the new domains or maintain ownership of them while still allowing other other parties to use them. Theoretically, they could use this power to allow anyone to buy them, but their announced plans were to develop all of said domains with a single partner, DirectEmployers, which sounds about as far from the opening up of the .ca domain that you describe as I can imagine.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Sarah Welstead</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21333</link>
		<dc:creator>Sarah Welstead</dc:creator>
		<pubDate>Fri, 09 Apr 2010 22:42:41 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21333</guid>
		<description>No one responded to my comment on John Zappe&#039;s original article (about why the sky would fall in because of this) so I came over here to read your piece, David, thinking that perhaps it would answer my question.  I also read Laurie Ruettiman&#039;s post and Lance Haun&#039;s posts, on their blogs, on the subject.

And while I think I now have a better sense of the outrage this whole thing is causing (the lack of transparency and disclosure, the &#039;change without due process and input&#039;, etc.), I still can&#039;t quite understand.

Yes, I understand SHRM wants to prevent fraud and cybersquatters and protect &#039;the HR community&#039;.

But the whole thing reminds me of what happened with the .ca domain (that&#039;s the official domain for Canada) circa 2000:  The .ca domain was initially over-protected; you couldn&#039;t get one without submitting a big application proving you had offices in more than one province; they cost a lot more than regular domains; and they had far less credibility than .com or even .co.uk.  

The result?  People like me, who started small businesses at the time, were forced into getting URLs like www.StayAwake.tv because I didn&#039;t qualify for a .ca domain and the .com one was already taken.  Even larger companies sometimes didn&#039;t qualify, and the process was (for the time) such a pain in the neck that they just didn&#039;t bother, and kept using .com.

The result of THAT?  .ca domains never really took off, they didn&#039;t confer credibility, and didn&#039;t take any of the pressure off .com domains - all that happened was that your customers outside Canada (and even sometimes IN Canada) were like &quot;What the heck is your URL about?  What&#039;s .ca?  Where ARE you?&quot;

Finally - I think in 2003 - the .ca domain was opened up more widely.  There was some of the same hand-wringing about CIRA (Canadian Internet Registration Authority) along the same lines I&#039;m seeing here with SHRM, but in the end, more Canadian companies got more .ca URLs for less money - which gave the .ca domain more credibility and more Canadian companies an easier way to make a name for themselves online.  The .ca domain was not suddenly held hostage to zillions of evil cybersquatters, most .ca buyers were legit, and most companies were able to get the URL(s) they needed.

If the SHRM was so invested in the .jobs domain, and it&#039;s so important for companies and HR practitioners, how come 98% of the recruiting and HR professionals I&#039;ve spoken to in the past 12 months don&#039;t even know it EXISTS?</description>
		<content:encoded><![CDATA[<p>No one responded to my comment on John Zappe&#8217;s original article (about why the sky would fall in because of this) so I came over here to read your piece, David, thinking that perhaps it would answer my question.  I also read Laurie Ruettiman&#8217;s post and Lance Haun&#8217;s posts, on their blogs, on the subject.</p>
<p>And while I think I now have a better sense of the outrage this whole thing is causing (the lack of transparency and disclosure, the &#8216;change without due process and input&#8217;, etc.), I still can&#8217;t quite understand.</p>
<p>Yes, I understand SHRM wants to prevent fraud and cybersquatters and protect &#8216;the HR community&#8217;.</p>
<p>But the whole thing reminds me of what happened with the .ca domain (that&#8217;s the official domain for Canada) circa 2000:  The .ca domain was initially over-protected; you couldn&#8217;t get one without submitting a big application proving you had offices in more than one province; they cost a lot more than regular domains; and they had far less credibility than .com or even .co.uk.  </p>
<p>The result?  People like me, who started small businesses at the time, were forced into getting URLs like <a href="http://www.StayAwake.tv" rel="nofollow">http://www.StayAwake.tv</a> because I didn&#8217;t qualify for a .ca domain and the .com one was already taken.  Even larger companies sometimes didn&#8217;t qualify, and the process was (for the time) such a pain in the neck that they just didn&#8217;t bother, and kept using .com.</p>
<p>The result of THAT?  .ca domains never really took off, they didn&#8217;t confer credibility, and didn&#8217;t take any of the pressure off .com domains &#8211; all that happened was that your customers outside Canada (and even sometimes IN Canada) were like &#8220;What the heck is your URL about?  What&#8217;s .ca?  Where ARE you?&#8221;</p>
<p>Finally &#8211; I think in 2003 &#8211; the .ca domain was opened up more widely.  There was some of the same hand-wringing about CIRA (Canadian Internet Registration Authority) along the same lines I&#8217;m seeing here with SHRM, but in the end, more Canadian companies got more .ca URLs for less money &#8211; which gave the .ca domain more credibility and more Canadian companies an easier way to make a name for themselves online.  The .ca domain was not suddenly held hostage to zillions of evil cybersquatters, most .ca buyers were legit, and most companies were able to get the URL(s) they needed.</p>
<p>If the SHRM was so invested in the .jobs domain, and it&#8217;s so important for companies and HR practitioners, how come 98% of the recruiting and HR professionals I&#8217;ve spoken to in the past 12 months don&#8217;t even know it EXISTS?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Master Burnett</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21330</link>
		<dc:creator>Master Burnett</dc:creator>
		<pubDate>Fri, 09 Apr 2010 20:19:38 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21330</guid>
		<description>David, you did a great job at articulating why the amendment should be rejected, I echo your points. While the ownership issue disturbs me, the lack of visibility around the proposed changes disturbs me more.</description>
		<content:encoded><![CDATA[<p>David, you did a great job at articulating why the amendment should be rejected, I echo your points. While the ownership issue disturbs me, the lack of visibility around the proposed changes disturbs me more.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: .jobs aiming to become a gTLD by the back door? &#124; DomainIncite.com - Domain Name News &#38; Opinion</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21323</link>
		<dc:creator>.jobs aiming to become a gTLD by the back door? &#124; DomainIncite.com - Domain Name News &#38; Opinion</dc:creator>
		<pubDate>Fri, 09 Apr 2010 16:36:53 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21323</guid>
		<description>[...] as ERE.net points out, the “proposed amendment” to its charter reads more like a claim that no amendment is [...]</description>
		<content:encoded><![CDATA[<p>[...] as ERE.net points out, the “proposed amendment” to its charter reads more like a claim that no amendment is [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: eric shannon</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21320</link>
		<dc:creator>eric shannon</dc:creator>
		<pubDate>Fri, 09 Apr 2010 15:05:46 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21320</guid>
		<description>What puzzles me to no end, is why any stakeholder would want to give EmployMedia the right to sell or auction the domains in question... that would pull the rug out from under any particular beneficial use the domains might be put to in a partnership. 

If you are an EmployMedia partner, that puts a gun to your head... that doesn&#039;t seem good for DirectEmployers or SHRM or its members.

Putting the domains to some good use is one thing, and creating an exit strategy for EmployMedia is another.</description>
		<content:encoded><![CDATA[<p>What puzzles me to no end, is why any stakeholder would want to give EmployMedia the right to sell or auction the domains in question&#8230; that would pull the rug out from under any particular beneficial use the domains might be put to in a partnership. </p>
<p>If you are an EmployMedia partner, that puts a gun to your head&#8230; that doesn&#8217;t seem good for DirectEmployers or SHRM or its members.</p>
<p>Putting the domains to some good use is one thing, and creating an exit strategy for EmployMedia is another.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Steven Rothberg</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21317</link>
		<dc:creator>Steven Rothberg</dc:creator>
		<pubDate>Fri, 09 Apr 2010 14:25:29 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21317</guid>
		<description>You should be proud, David, of the work that John Zappe and the rest of the team at ERE has done in bringing this important issue some sunlight. 

Perhaps the proposals put forward by Employ Media and Direct Employers will prove to be in the best interests of the HR community and even the general public, but that can&#039;t be known until all of the stakeholders have had an opportunity to understand the issue and weigh in on it. 

With an almost complete lack of transparency over the entire process -- even that the issue exists -- the process reaks. The work of ERE here has been exemplary.</description>
		<content:encoded><![CDATA[<p>You should be proud, David, of the work that John Zappe and the rest of the team at ERE has done in bringing this important issue some sunlight. </p>
<p>Perhaps the proposals put forward by Employ Media and Direct Employers will prove to be in the best interests of the HR community and even the general public, but that can&#8217;t be known until all of the stakeholders have had an opportunity to understand the issue and weigh in on it. </p>
<p>With an almost complete lack of transparency over the entire process &#8212; even that the issue exists &#8212; the process reaks. The work of ERE here has been exemplary.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SHRM Council To Consider .Jobs Friday : ERE.net</title>
		<link>http://www.ere.net/2010/04/08/why-shrm-must-reject-the-jobs-amendment/comment-page-1/#comment-21290</link>
		<dc:creator>SHRM Council To Consider .Jobs Friday : ERE.net</dc:creator>
		<pubDate>Fri, 09 Apr 2010 02:19:20 +0000</pubDate>
		<guid isPermaLink="false">http://www.ere.net/?p=12373#comment-21290</guid>
		<description>[...] If you are wondering what this all about, there&#8217;s plenty of background in the article I posted Wednesday evening. You can find it here. ERE CEO David Manaster also provides a synopses of the events and offers his take on the issue. [...]</description>
		<content:encoded><![CDATA[<p>[...] If you are wondering what this all about, there&#8217;s plenty of background in the article I posted Wednesday evening. You can find it here. ERE CEO David Manaster also provides a synopses of the events and offers his take on the issue. [...]</p>
]]></content:encoded>
	</item>
</channel>
</rss>

