CircleID

I've always thought that a company-specific jobs site ought to be done as a logical subdomain of the main company domain; thus, if the main domain is foo.com, the jobs site would be at jobs.foo.com.  Just what is gained by putting it instead at foo.jobs, other than revenue for a registry and registrar?

So, here is a puzzle…

If I were to abuse the policies to find some exploitable loophole.....

Here is an edge case… in the process of recruitment, hiring people who are good with their hands, who specialize in meticulous handmade crafts, could I get the domain hand.jobs?

Lets say that this request came in under a legitimate premise, and got approved and delegated.

Roll the calendar forward to a time 6 months later, and the registrant realizes that there might be another use for the domain name and redirects it to an adult site or synthetic latex glove manufacturer… who polices or enforces this?

I realize this is probably a bad example of an edge case, or it sounds like a joke, but I am sincerely curious.

Is there some form of community policing that needs to occur to maintain the integrity of the STLD charter?

Jothan around .jobs both EmployMedia and SHRM have stated that they will "police" any requests around this.  However with the recent example of domain hijacking you raise a very good point.

Joel Cheesman says in his blog: "The data is going to have to stay pure. If engineering.jobs, marketing.jobs, etc. ever get sold in conjunction with statefarm.jobs, .jobs will have no greater benefit than a .net"

Today's registrar marketplace rewards low margins and high volume; it's hard to see how generic names can legitimately be kept out ... particularly if a qualified company's name has these words in their formal registered name.

The stld .jobs sounds like a great idea. The role out needs more definition, but the end result can be helpful to the HR professional as well as the job seeker. As with any new venture there are always obsticals to overcome, but the value far exceeds the obsticals.