Feeds

Dot, squiggle, plop

Unencoding the web

Top three mobile application threats

Column My first response to the idea of a dot-sex web domain was: "Well, that's a rip-off". And when I heard about dot-tv and dot-euro I wasn't the only one to say: "Here we go again..." And I bet most of us were equally cynical about dot-asia.

I mean, most people in Asia don't actually use the Roman alphabet and so (I sort of assumed) they would see this as just another way of lining the pockets of domain registrars. So I checked with Kieren McCarthy.

Kieren, as you may remember, was a reporter on the Register for some time and then, in a fit of insanity, put himself up for election to the council of ICANN. When that didn't work out, he accepted an actual paying job with them. Turncoat, I said. Not a bit of it, he said. "Well, can you justify this latest scam for taking money out of people with websites? I asked."

The problem, apparently, isn't with the desire of domain registrars wanting to make money. It's the fact that the internet is, inherently, unfair to the people of the East. Come to that, it's also unfair to those who use Cyrillic or other non-Roman alphabets. So ICANN can justify dot-asia, and it's going further with a project (unofficially) named dot-squiggle.

Squiggles are the characters which most English-speaking people simply can't decipher, and which make a walk down the main streets of Tokyo and Bangkok such a mystifying experience.

In the same way that I can't read Japanese street signs, the average Korean struggles to understand the URLs of the World Wide Web. ICANN is tackling this.

ICANN has organised a conference, to be held in Taipei next month, to try to find out where the world ought to go with dot-squiggle. It is an upgrade to the encoding of domain names and DNS to allow Chinese characters, Korean characters, Singaporean characters, and all non-Roman alphabets to be uniquely decoded so that ordinary citizens of the various Asian countries can search the internet without needing to know how to write in English.

It doesn't take much imagination to see how useful that could be. But does it explain dot-asia?

"Public demand," said the official spokesman I was referred to by ICANN. "It was the same with dot-euro," she said. "We were approached by domain registrars who suggested there was a need for it, and they demonstrated their technical ability to handle the job. Some did say it was uncalled for, and would just force the big domain holdes and trade-mark owners to register names like www.sony.euro to cough up. But it turns out that no; there really are lots and lots - millions - of people who want to be "me@justme.euro" or run www.justme.euro as websites; and that in fact, Sony didn't feel even slightly bothered by the idea."

And, apparently, there is an equally enthusiastic requirement for dot-asia domains, and ICANN expects ordinary people to go for it on an even greater scale. The main pressure to provide it, it says, actually came from Asia - specifically, from Korea.

The move towards non-Roman domains and characters, however, is just the second step. From ICANN's point of view, the real goal is a domain name system which allows almost anybody to create and administer a top-level domain which is entirely original. If you didn't get a dot-com name, suddenly, who cares? Create dot-anything.

For sailors, perhaps, there would be a value in a dot-boat domain. For bee-keepers, a dot-honey domain; for gardeners, a dot-seed domain. If someone wants to have a domain and has the skills to administer it, the plan is to make it possible. Why not?

But of course, this opens several cans, many of which have worms.

Developing a system of character encoding which enables all these domains to exist in any number of languages, was a challenge. But now it's been done (and is in beta) the next step is going to be, surely, to decide whether we can open up the rest of programming technology? Was that a worm I saw?

Today, HTML is not only written in Roman characters, but uses English (and American-spelled English, at that). That means if your education doesn't include English, you can't be a website manager (worm).

What about Pascal? C#? C++? Javascript? Why should it not be possible for people who use different alphabets to write software in them? Ooh, look, another worm...

It'll be interesting to see how this one plays out. ®

Combat fraud and increase customer satisfaction

More from The Register

next story
Virgin Media so, so SORRY for turning spam fire-hose on its punters
Hundreds of emails flood inboxes thanks to gaffe
A black box for your SUITCASE: Now your lost luggage can phone home – quite literally
Breakfast in London, lunch in NYC, and your clothes in Peru
AT&T threatens to pull out of FCC wireless auctions over purchase limits
Company wants ability to buy more spectrum space in auction
Turnbull leaves Australia's broadband blackspots in the dark
New Statement of Expectations to NBN Co offers get-out clauses for blackspot builds
Facebook claims 100 MEEELLION active users in India
Who needs China when you've got the next billion in your sights?
Facebook splats in-app chat, whacks brats into crack yakety-yak app
Jibber-jabbering addicts turfed out just as Zuck warned
Google looks to LTE and Wi-Fi to help it lube YouTube tubes
Bandwidth hogger needs tube embiggenment if it's to succeed
prev story

Whitepapers

Top three mobile application threats
Learn about three of the top mobile application security threats facing businesses today and recommendations on how to mitigate the risk.
Combat fraud and increase customer satisfaction
Based on their experience using HP ArcSight Enterprise Security Manager for IT security operations, Finansbank moved to HP ArcSight ESM for fraud management.
The benefits of software based PBX
Why you should break free from your proprietary PBX and how to leverage your existing server hardware.
Five 3D headsets to be won!
We were so impressed by the Durovis Dive headset we’ve asked the company to give some away to Reg readers.
SANS - Survey on application security programs
In this whitepaper learn about the state of application security programs and practices of 488 surveyed respondents, and discover how mature and effective these programs are.