<?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: www.whataloadofrubbish.jobs</title>
	<atom:link href="http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/feed/" rel="self" type="application/rss+xml" />
	<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/</link>
	<description>A Contrarian View of Life in the Recruitosphere</description>
	<lastBuildDate>Tue, 31 Aug 2010 09:03:56 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=abc</generator>
	<item>
		<title>By: careers</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-46</link>
		<dc:creator>careers</dc:creator>
		<pubDate>Wed, 02 Aug 2006 09:39:21 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-46</guid>
		<description>I can perhaps see the logic behind the .jobs TLD, however how is this going to communicated to the typical end user? Currently most surfers seeking a job vacancy will use a &quot;branded&quot; career site (ie Monster) or they will use a search engine and type in a query something like &quot;IT jobs in London&quot;, in other words nobody knows about the .jobs TLD and this idea will completely escape them - unless Google for instance displays a message in serps &quot;did you mean to search for ITlondon.jobs&quot;!</description>
		<content:encoded><![CDATA[<p>I can perhaps see the logic behind the .jobs TLD, however how is this going to communicated to the typical end user? Currently most surfers seeking a job vacancy will use a &#8220;branded&#8221; career site (ie Monster) or they will use a search engine and type in a query something like &#8220;IT jobs in London&#8221;, in other words nobody knows about the .jobs TLD and this idea will completely escape them &#8211; unless Google for instance displays a message in serps &#8220;did you mean to search for ITlondon.jobs&#8221;!</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recruitomatic</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-45</link>
		<dc:creator>Recruitomatic</dc:creator>
		<pubDate>Thu, 13 Jul 2006 09:30:23 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-45</guid>
		<description>Ray:

I am very grateful - and humbled - that you took the time to reply in such detail, and for balancing my post with such a comprehensive answer. For me, your explainations are just what I was looking for. Sincerely, thank you!

Amitai.</description>
		<content:encoded><![CDATA[<p>Ray:</p>
<p>I am very grateful &#8211; and humbled &#8211; that you took the time to reply in such detail, and for balancing my post with such a comprehensive answer. For me, your explainations are just what I was looking for. Sincerely, thank you!</p>
<p>Amitai.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Ray Fassett</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-42</link>
		<dc:creator>Ray Fassett</dc:creator>
		<pubDate>Thu, 13 Jul 2006 04:04:16 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-42</guid>
		<description>If I am a recruiter for ACME Corp and I run newspaper ads, I want to tell my audience to &quot;apply now&quot; by going straight to www.acme.jobs.

If ACME Corp has an employee referral program, I would want all my employees trained to say: &quot;It&#039;s easy to apply, just go to www.acme.jobs.&quot;

.jobs is about a direct navigational route to content that is 1) being actively promoted by the employer and 2) being sought by a target audience. The DNS is the Internet protocol for users to navigate to content on the World Wide Web (www). More simply put, the DNS is a utility. www.acme.jobs is about a destination that contains jobs content at ACME Corp. If I am a job seeker, whether active or passive, www.acme.com tells me, in no uncertain terms, that I am Not going to the jobs content of ACME Corp.

www.acme.com is a URL. www.acme.jobs is a URL. Both are part of the global DNS protocol. Both direct users to a destination that contains content. One destination contains jobs content and the other does not. The difference is very black and white and, quite honestly, doesn&#039;t get any more complicated than this as a utility. If there is to be greater relevancy by search engines to .jobs domain names as some experts are already saying is evolving, then this will be the reason why.

Acme Corp is the party ensuring www.acme.jobs contains jobs content on an ongoing basis. We simply enable ACME Corp to acquire www.acme.jobs and then make sure it functions as a URL on the World Wide Web every time it is called upon to answer from anywhere in the world. Search engines are beginning to show trust in how we are enabling employers to acquire their domain name in .jobs. Our methods take steps to ensure that .jobs domain names contain jobs related content after becoming active and then called upon by users of the Internet. For search engines, it becomes a user trust factor and a core mission of the .jobs utility. Restrictive methods that take steps to ensure content objectives cut against sheer volume objectives. For the .jobs utility, volume should not be equated to adoption. As the licensed operator, it is a decision we have made and believe in more today than ever.

We are pleased with year 1 results, in some ways surpassing initial assumptions and/or business expectations. There&#039;s no question we face challenges, no surprise there. It&#039;s a big world and we have high expectations in what we are doing in cooperation with those that have, on their own, evaluated the .jobs utility and taken an early adopter position going to market in a manner they feel serves their own best interests and recruitment strategies.

Like any licensed utility, .jobs is here to stay. It is part of the core infrastructure of the Internet, no different that .com, .net, .org, and .edu. One URL method informs users to navigate to home page related content (certainly a useful utility for many purposes) and .jobs informs users to navigate to jobs related content. That&#039;s the utility of .jobs, in the most simplest of terms, that has been made equitably available to all employer organizations the world over.

I would like to thank Amitai and the other commentators for having this discussion about .jobs. I hope my comments have contributed in a positive fashion. I also encourage anyone to feel free to contact me directly at rayATgoto.jobs.

Sincerely,

Ray Fassett
.jobs
216-426-1500 ext 129 (United States)</description>
		<content:encoded><![CDATA[<p>If I am a recruiter for ACME Corp and I run newspaper ads, I want to tell my audience to &#8220;apply now&#8221; by going straight to <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a>.</p>
<p>If ACME Corp has an employee referral program, I would want all my employees trained to say: &#8220;It&#8217;s easy to apply, just go to <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a>.&#8221;</p>
<p>.jobs is about a direct navigational route to content that is 1) being actively promoted by the employer and 2) being sought by a target audience. The DNS is the Internet protocol for users to navigate to content on the World Wide Web (www). More simply put, the DNS is a utility. <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a> is about a destination that contains jobs content at ACME Corp. If I am a job seeker, whether active or passive, <a href="http://www.acme.com" rel="nofollow">http://www.acme.com</a> tells me, in no uncertain terms, that I am Not going to the jobs content of ACME Corp.</p>
<p><a href="http://www.acme.com" rel="nofollow">http://www.acme.com</a> is a URL. <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a> is a URL. Both are part of the global DNS protocol. Both direct users to a destination that contains content. One destination contains jobs content and the other does not. The difference is very black and white and, quite honestly, doesn&#8217;t get any more complicated than this as a utility. If there is to be greater relevancy by search engines to .jobs domain names as some experts are already saying is evolving, then this will be the reason why.</p>
<p>Acme Corp is the party ensuring <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a> contains jobs content on an ongoing basis. We simply enable ACME Corp to acquire <a href="http://www.acme.jobs" rel="nofollow">http://www.acme.jobs</a> and then make sure it functions as a URL on the World Wide Web every time it is called upon to answer from anywhere in the world. Search engines are beginning to show trust in how we are enabling employers to acquire their domain name in .jobs. Our methods take steps to ensure that .jobs domain names contain jobs related content after becoming active and then called upon by users of the Internet. For search engines, it becomes a user trust factor and a core mission of the .jobs utility. Restrictive methods that take steps to ensure content objectives cut against sheer volume objectives. For the .jobs utility, volume should not be equated to adoption. As the licensed operator, it is a decision we have made and believe in more today than ever.</p>
<p>We are pleased with year 1 results, in some ways surpassing initial assumptions and/or business expectations. There&#8217;s no question we face challenges, no surprise there. It&#8217;s a big world and we have high expectations in what we are doing in cooperation with those that have, on their own, evaluated the .jobs utility and taken an early adopter position going to market in a manner they feel serves their own best interests and recruitment strategies.</p>
<p>Like any licensed utility, .jobs is here to stay. It is part of the core infrastructure of the Internet, no different that .com, .net, .org, and .edu. One URL method informs users to navigate to home page related content (certainly a useful utility for many purposes) and .jobs informs users to navigate to jobs related content. That&#8217;s the utility of .jobs, in the most simplest of terms, that has been made equitably available to all employer organizations the world over.</p>
<p>I would like to thank Amitai and the other commentators for having this discussion about .jobs. I hope my comments have contributed in a positive fashion. I also encourage anyone to feel free to contact me directly at rayATgoto.jobs.</p>
<p>Sincerely,</p>
<p>Ray Fassett<br />
.jobs<br />
216-426-1500 ext 129 (United States)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recruitomatic</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-44</link>
		<dc:creator>Recruitomatic</dc:creator>
		<pubDate>Wed, 12 Jul 2006 15:35:42 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-44</guid>
		<description>Colin:

On the first point: agreed.

On the second: I don&#039;t if anyone else is getting a better picture as to how this all could work out for the better, but I believe I am now. I just have to come up with a good reason as to why I remain unconvinced.

Thanks again.

Amitai</description>
		<content:encoded><![CDATA[<p>Colin:</p>
<p>On the first point: agreed.</p>
<p>On the second: I don&#8217;t if anyone else is getting a better picture as to how this all could work out for the better, but I believe I am now. I just have to come up with a good reason as to why I remain unconvinced.</p>
<p>Thanks again.</p>
<p>Amitai</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Colin Kingsbury</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-43</link>
		<dc:creator>Colin Kingsbury</dc:creator>
		<pubDate>Wed, 12 Jul 2006 14:55:19 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-43</guid>
		<description>In terms of consumers, .jobs solves a problem that isn&#039;t broken. Most companies in possession of a clue now have a careers link on every page in an easy-to-find location. So whoop-de-doo there.

However, to the extent that search and aggregation are becoming bigger factors, the value of better ranking is not to be dismissed. From that perspective, it doesn&#039;t matter if -people- know about the TLD, it only matters that the Googlebot does.</description>
		<content:encoded><![CDATA[<p>In terms of consumers, .jobs solves a problem that isn&#8217;t broken. Most companies in possession of a clue now have a careers link on every page in an easy-to-find location. So whoop-de-doo there.</p>
<p>However, to the extent that search and aggregation are becoming bigger factors, the value of better ranking is not to be dismissed. From that perspective, it doesn&#8217;t matter if -people- know about the TLD, it only matters that the Googlebot does.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recruitomatic</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-41</link>
		<dc:creator>Recruitomatic</dc:creator>
		<pubDate>Mon, 10 Jul 2006 23:06:16 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-41</guid>
		<description>Like I said in the post, you guys are the experts. I salute you, and Colin too. It seems we are now all in agereement then: without a concerted effort to educate job seekers and change their behaviors, the dot jobs domain could well be a load of....well, no sense in laboring the point.

Thanks for your comments - Amitai.</description>
		<content:encoded><![CDATA[<p>Like I said in the post, you guys are the experts. I salute you, and Colin too. It seems we are now all in agereement then: without a concerted effort to educate job seekers and change their behaviors, the dot jobs domain could well be a load of&#8230;.well, no sense in laboring the point.</p>
<p>Thanks for your comments &#8211; Amitai.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Michael Specht</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-40</link>
		<dc:creator>Michael Specht</dc:creator>
		<pubDate>Mon, 10 Jul 2006 22:52:12 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-40</guid>
		<description>A great follow up post to the different commentary.  Shannon is right on the money with &quot;.jobs needs to be marketed to and adopted by the jobseekers before it will ever become THE way to find job opportunities on a web site. SHRM supported this initiative for employers – I want to know who is going to do the major marketing to change the behavior of job seekers. It won’t all happen through search.&quot;

If this does not happen then dot jobs is just a money making process for SHRM.</description>
		<content:encoded><![CDATA[<p>A great follow up post to the different commentary.  Shannon is right on the money with &#8220;.jobs needs to be marketed to and adopted by the jobseekers before it will ever become THE way to find job opportunities on a web site. SHRM supported this initiative for employers – I want to know who is going to do the major marketing to change the behavior of job seekers. It won’t all happen through search.&#8221;</p>
<p>If this does not happen then dot jobs is just a money making process for SHRM.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recruitomatic</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-39</link>
		<dc:creator>Recruitomatic</dc:creator>
		<pubDate>Mon, 10 Jul 2006 18:42:17 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-39</guid>
		<description>Shannon, I see now. How easy was that? Thanks.</description>
		<content:encoded><![CDATA[<p>Shannon, I see now. How easy was that? Thanks.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Shannon Seery</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-36</link>
		<dc:creator>Shannon Seery</dc:creator>
		<pubDate>Mon, 10 Jul 2006 17:47:22 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-36</guid>
		<description>Hi Ami :-)

I have a couple of thoughts on your additional questions.  I think that there are a lot of &quot;what ifs&quot; - which is exactly why the domain hasn&#039;t reached critical mass yet.

1 &#038; 2 &#038; 3 - Yes - Acme would want to register despite their low number of reqs even though I don&#039;t think that the ACMEs of the world will be the ones to push for general adopotion of the tld.  IF the search engines increasingly recognize .jobs (like Colin explained for .edu) - then anyone with a dotjobs will have a greater chance of ranking higher with search engines and being found by the job seekers that are using them to find jobs.  The registration of the name and the technical tweaks are relatively easy and certainly cheaper than the newspaper ads that ACME is no doubt running.

But the other component here (and the more critical one in my view) is not based on how favorable a tdl may or may not be to search engines.  Search is by NO means the only way that job seekers look for jobs.  .jobs needs to be marketed to and adopted by the jobseekers before it will ever become THE way to find job opportunities on a web site.  SHRM supported this initiative for employers – I want to know who is going to do the major marketing to change the behavior of job seekers.  It won’t all happen through search.

Shannon</description>
		<content:encoded><![CDATA[<p>Hi Ami <img src='http://blogversity.com/recruitomatic/wp-includes/images/smilies/icon_smile.gif' alt=':-)' class='wp-smiley' /> </p>
<p>I have a couple of thoughts on your additional questions.  I think that there are a lot of &#8220;what ifs&#8221; &#8211; which is exactly why the domain hasn&#8217;t reached critical mass yet.</p>
<p>1 &#38;#38; 2 &#38;#38; 3 &#8211; Yes &#8211; Acme would want to register despite their low number of reqs even though I don&#8217;t think that the ACMEs of the world will be the ones to push for general adopotion of the tld.  IF the search engines increasingly recognize .jobs (like Colin explained for .edu) &#8211; then anyone with a dotjobs will have a greater chance of ranking higher with search engines and being found by the job seekers that are using them to find jobs.  The registration of the name and the technical tweaks are relatively easy and certainly cheaper than the newspaper ads that ACME is no doubt running.</p>
<p>But the other component here (and the more critical one in my view) is not based on how favorable a tdl may or may not be to search engines.  Search is by NO means the only way that job seekers look for jobs.  .jobs needs to be marketed to and adopted by the jobseekers before it will ever become THE way to find job opportunities on a web site.  SHRM supported this initiative for employers – I want to know who is going to do the major marketing to change the behavior of job seekers.  It won’t all happen through search.</p>
<p>Shannon</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Recruitomatic</title>
		<link>http://blogversity.com/recruitomatic/2006/07/10/wwwwhataloadofrubbishjobs-2/comment-page-1/#comment-37</link>
		<dc:creator>Recruitomatic</dc:creator>
		<pubDate>Mon, 10 Jul 2006 16:43:29 +0000</pubDate>
		<guid isPermaLink="false">http://recruitomatic.amitaigivertz.com/?p=32#comment-37</guid>
		<description>Colin, thanks for commenting and I appreciate the ah-ha! moment but now you raise more questions:

1. Should your rationale be enough to persuade us - on balance - that this dot jobs domain isn&#039;t still dead on arrival? Will Acme Corporation who may only have 10 or 20 reqs. a year want to go through all the initial hoop-la of getting a dot jobs domain?

2. If they don&#039;t, are you suggesting their access to possible candidates is going to be further restricted because they may not appear as highly placed on the search engines?

3. Are you assuming a) search engines will overtake job boards as the preferred first stop for job seekers, and b) googling &quot;mechanical+engineer+manager+jobs&quot; will favor employers using a dot jobs domain over the most relevant results?

4. You say &quot;in theory&quot;. What will happen in practice?

I like to think if I’m still confused someone else out there is too.

Amitai.</description>
		<content:encoded><![CDATA[<p>Colin, thanks for commenting and I appreciate the ah-ha! moment but now you raise more questions:</p>
<p>1. Should your rationale be enough to persuade us &#8211; on balance &#8211; that this dot jobs domain isn&#8217;t still dead on arrival? Will Acme Corporation who may only have 10 or 20 reqs. a year want to go through all the initial hoop-la of getting a dot jobs domain?</p>
<p>2. If they don&#8217;t, are you suggesting their access to possible candidates is going to be further restricted because they may not appear as highly placed on the search engines?</p>
<p>3. Are you assuming a) search engines will overtake job boards as the preferred first stop for job seekers, and b) googling &#8220;mechanical+engineer+manager+jobs&#8221; will favor employers using a dot jobs domain over the most relevant results?</p>
<p>4. You say &#8220;in theory&#8221;. What will happen in practice?</p>
<p>I like to think if I’m still confused someone else out there is too.</p>
<p>Amitai.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
