Tuesday 27 March 2018

Sacred Domain: How to Keep the .Bible Holy

Critics accuse American Bible Society of being too restrictive with its corner of the internet.

Ongoing net neutrality debates reveal the tensions between the Internet’s open-source, free access ideals and the commercial or private forces behind the web. The debate extended into the internet’s officially biblical realm—the .bible domain—in a recent dispute over its faith-based standards.

Some Bible scholars accused the American Bible Society (ABS) of unfairly restricting use of the top-level domain, which it secured a contract to run as an administrator back in 2013.

The year before, the Internet Corporation for Assigned Names and Numbers (ICANN) opened up thousands of possible new web endings, called top-level domains, and asked interested entities to submit an application—and a $185,000 fee. Beyond the typical .com, .org, and .edu, these branded top-level domains allow for punchier marketing and unique URLs.

Plenty of the top-level domains, even ones with Christian crossover, ended up going to secular corporations. The tech-savvy Oklahoma megachurch then known as LifeChurch.tv applied to run the .church domain, but got beat out by Donuts Inc., a major domain name registry. It still changed its URL and name to Life.Church, but doesn’t serve as the registry operator for fellow .church sites. Donuts also owns .community, .care, and .life, the extension used by the Southern Baptist Convention’s Evangelicals for Life conference (evangelicals.life).

ABS, though, had no competition for .bible and, in partnership with several other Christian organizations, became the entity in charge of registering .bible websites, a task that it said follows its 200-year mission to promote Bible engagement.

Certain companies restrict their top-level domain for their corporate branding—for example, ...

Continue reading...



from
http://feeds.christianitytoday.com/~r/christianitytoday/ctmag/~3/J9I9IkIMQyc/sacred-domain-how-to-keep-dot-bible-holy-abs-icann-websites.html

No comments:

Post a Comment