{"id":930,"date":"2011-08-01T17:06:24","date_gmt":"2011-08-01T15:06:24","guid":{"rendered":"http:\/\/www.tld.sc\/en\/?p=930"},"modified":"2020-01-13T11:01:20","modified_gmt":"2020-01-13T09:01:20","slug":"930","status":"publish","type":"post","link":"https:\/\/www.bnamed.blog\/en\/2011\/08\/930\/","title":{"rendered":"Will ICANN terminate .jobs?"},"content":{"rendered":"

\"\"A while ago we already posted an article that ICANN had seriously warned the .jobs registry<\/a>. The registry got this warning because, according to ICANN, they had set up a partnership via which the registry violated the rules of their own policy.<\/p>\n

Via the partnership, it became possible to register domain names under the .jobs extension which didn’t comply to the rules which are mentioned in the general policy of the .jobs registry. ICANN didn’t agree on this and they gave the registry until the end of March to solve those problems. However the registry didn’t react because according to them they hadn’t done anything wrong.<\/p>\n

To register a name under the .jobs extension you need to meet one of the following conditions. You are:<\/p>\n

    \n
  1. a member of the SHRM (Society of Human Resource Management)
    \n<\/span><\/span><\/li>\n
  2. an HR company which only places positions within your own organisation on the .jobs website you’ve registered<\/span><\/span><\/li>\n<\/ol>\n

    If you follow this rules, it’s impossible for selection and recruiting offices to register a .jobs domain name. They are HR companies but they offer positions of third parties.<\/p>\n

    However it turns out it isn’t so hard to become a member of the SHRM. For the .josb registry, being a member was sufficient. Once you had registered your .jobs name, it was up to you what you did with your domain name and website. ICANN however means that, if you’re a member of the SHRM, you also need to practice SHRM related activities.<\/p>\n

    ICANN had enough of it once the registry itself registered the domain name universe.jobs. They linked a huge job database. For ICANN this was absolutely not tolerable. That’s why ICANN demanded the ICC (International Chamber of Commerce) the right to terminate their partnership with the .jobs registry.<\/p>\n

    Whether ICANN, once they received this right, also will terminate their contract with the .jobs registry isn’t clear. We’ll keep you posted about this.<\/p>\n","protected":false},"excerpt":{"rendered":"

    A while ago we already posted an article that ICANN had seriously warned the .jobs registry. The registry got this warning because, according to ICANN, they had set up a partnership via which the registry violated the rules of their own policy.<\/p>\n","protected":false},"author":2,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":[],"categories":[1],"tags":[],"_links":{"self":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/930"}],"collection":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/comments?post=930"}],"version-history":[{"count":3,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/930\/revisions"}],"predecessor-version":[{"id":2149,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/posts\/930\/revisions\/2149"}],"wp:attachment":[{"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/media?parent=930"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/categories?post=930"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.bnamed.blog\/en\/wp-json\/wp\/v2\/tags?post=930"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}