Natural Search Blog


W3C Issues Mobile App Guidelines

The World Wide Web Consortium (“W3C”) announced today a mobile web best practices document, providing standards intended to improve the user experience of the web on mobile devices.

This is good, because it will help promote better standards across mobile application development. Until now, developers have been all over the map in terms of how such apps or mobile-enabled sites are created.

So, the big question in my mind — what sort of domain name do they recommend for mobile apps?!? Do they recommend using the .mobi top level domain (“TLD”)? (more…)

.MOBI Top Level Domain Names Have Misguided Rules

Well the “Sunrise Registration” period for the new .MOBI top level domain names just started up about a week ago, and I have to say that the rules that have been imposed with .MOBI are irritating. The company that serves as the registry for it, “mobile Top Level Domain Ltd” (“mTLD”), has required that anyone who is delivering up content on a .MOBI TLD must deliver up at least the root level page in XHTML-MP format.

According to their mandatory registrant rules, you could just own the .MOBI domain for your site and not publish a site on it — just sit on it, to keep others from hosting stuff on your trademarked name. Once you publish content on the .MOBI domain, at least the root response must be in XHTML-MP flavor, and they will police these domains to insure compliance. Sites not in compliance will be warned, and if they aren’t fixed, their zone file entries will be deleted until the sites are corrected!

Now, I understand that they idealistically want to make the internet world a better place, and they’re seeking to insure consistency by imposing this standard. However, I think they’re misguided and this is a pretty bad business decision. I don’t see anything wrong in having generally thematic rules associated with TLDs, like using .EDU only for educational institutions and .MIL only for military sites. My beef is with having a registry now take on additional powers of setting a required protocol for the content on the site, policing it and checking for validity, and unplugging sites that don’t comply. (more…)


Fatal error: Uncaught Error: Call to undefined function UTW_ShowCurrentTagSet() in /home2/sspencer/public_html/naturalsearchblog.com/wp-content/themes/naturalsearch/footer.php:5 Stack trace: #0 /home2/sspencer/public_html/naturalsearchblog.com/wp-includes/template.php(688): require_once() #1 /home2/sspencer/public_html/naturalsearchblog.com/wp-includes/template.php(647): load_template('/home2/sspencer...', true) #2 /home2/sspencer/public_html/naturalsearchblog.com/wp-includes/general-template.php(76): locate_template(Array, true) #3 /home2/sspencer/public_html/naturalsearchblog.com/wp-content/themes/naturalsearch/index.php(49): get_footer() #4 /home2/sspencer/public_html/naturalsearchblog.com/wp-includes/template-loader.php(74): include('/home2/sspencer...') #5 /home2/sspencer/public_html/naturalsearchblog.com/wp-blog-header.php(19): require_once('/home2/sspencer...') #6 /home2/sspencer/public_html/naturalsearchblog.com/index.php(17): require('/home2/sspencer...') #7 {main} thrown in /home2/sspencer/public_html/naturalsearchblog.com/wp-content/themes/naturalsearch/footer.php on line 5