Wednesday, August 12, 2009

Commenting on an SEM Clubhouse post

There's a good discussion about .tel and hCard on the SEM Clubhouse blog. I am responding here because its comments section doesn't allow basic formatting for clarity.

Silver in comment #4 says:
it’s not at all clear to me why a “single universal personal identifier for multiple communication services” could not be their existing website.

Why not an existing website? Well assuming you're using standardized formats so the info can be correctly parsed, why not? Except of course that using http + parsing hCard or other formats is incredibly slower than doing a .tel DNS lookup. Plus, you need the skills so you don't make a mistake in publishing your data. And finally, you need to have a website already. Believe it or not, there are as many companies without websites as companies with. If I'm a window cleaner, plumber, dentist or doctor, why do I need a website? I need a Presence Online, I need to Market Myself, I need to Be Found and Contacted, but I don't need to waste money and time building a website.
Furthermore, even if I do have a website, updating my contact info when it changes can be a chore. If I also have a .tel, I can dynamically pull the .tel info and display it on my website, and use the .tel as an easily updated dynamic data store for contact info.

A simpler way of looking at this is to state that .tel is a business tool.

Regarding:
you need a site, you need to pay for it, and you need a means of updating it

Those are not dependencies for the .tel beyond paying the yearly domain fee (which you also have to pay with your own domain). You do not pay site hosting and other hidden fees, you do not build a site, and you have all sorts of means of updating it, from a standard web interface to complete APIs or even uploading excel spreadsheets.

Also I think you're missing the core point that .tel is (once again) not a website. You're saying:
I’m pleased to hear that .TEL may incorporate microformatting in the future! It definitely makes sense if you want to facilitate machine-readable contact info.

.tel is absolutely the easiest machine-readable contact info system there is! All .tel contact info is stored as structured DNS records. Simply make a DNS query to a .tel domain, asking for the contact records, and you've got them right there. They need minimal parsing, and probably about 100 times less resources than grabbing the data from an hCard. Navigation at the speed of DNS is something to be appreciated. :)

To go back to Yellow Pages directories: they're not competitors to .tel. They'll gladly grab your .tel info to populate their directories, it'll save them quite a few headaches and will make their offering more valuable. It's only that currently SIP and other communication channels are short-changed because of the difficulty of modifying the underlying infrastructures of the major YP providers.

Finally, let me answer your last question:
The privacy feature is the least clear selling point about .TEL. I’m by no means ignorant about privacy issues, but it’s unclear to me how .TEL helps those, and why that those of us who want to make our contact info more readily findable should simultaneously want to keep it private?

To start with, there's a comprehensive .tel Privacy document. You certainly want your contact information readily findable, but are you sure you want all your info findable by everyone? Probably not. You may want to keep that cell phone number of yours private and only give it to a couple of close friends. In order to do that, Telnic has developed a privacy model comprised of encryption specifications and an optional centralized friending system implementation. I've described the implementation in another blog post of mine, Privacy in .tel.

Here's a final thought for you:
Imagine you want to dial a number, but instead dial a name. This is .tel. The name resolves to a number (or many) and the call is made. It's just like typing and name in the browser address bar and it resolving to an IP address. We're in the 21st century. 15 years ago we stopped remembering IP addresses. Why do we still need to remember phone numbers?

Henri.

PS: The .tel-to-vCard mapping info is here.

2 comments:

Silver said...

Just a couple of more rebuttals to your rebuttals, Henri -

Re: parsing of hCard is slower - Yet, this is done by machinery with processes individual to the consumer of that info, and is still so fast that it's virtually unnoticeable by people.

Re: you need skills to create - True, but there are so many template-driven websites and turnkey hosting solutions out there, this is hardly a barrier to entry. (Google Sites are just one example.)

And, as for being able to use .TEL as a data store, that's going to require a considerably higher skill level than setting up a turnkey website. I can use a DNS information service such as Hexillion's Domain Dossier at http://centralops.net/co/ to read the additional DNS info stored for henri.tel, but how many unsophisticated small businessmen will know how to do this?

Finally, on the privacy issue - the way it usually works is that I provide private contact information directly to friends and family. .TEL sounds a bit more difficult for this purpose, because I'd have to expect my friends to remember the URL, remember a special password, go to the URL and type in the password to get my number updated. This is pretty convoluted. Just this past week, a friend of mine changed cell phone numbers, and she simply emailed us all the updated info. Frankly, if she didn't tell us and updated it in some site where we'd be expected to go, login and retrieve it, she'd simply stop getting calls from some friends for whom that'd be too much.

Rik said...

You're missing the point about speed. It's not about being fast enough that it's "virtually unnoticeable by people", it's about being fast enough that it enables applications to do things that they couldn't do until .tel, like auto-lookups upon dialing, at the exact time when you need the latest contact info.

.tel enables a whole new set of applications and features that web-based systems just can't provide.

For privacy, you have a single TelFriends login, which works for all .tel domains. In general you'll enter it once in your app (or on the web) and forget about it.

Finally, when your friend changed her phone number and had to email everyone, why don't you ask her how easy that was, how many bounces she got, and whether she wouldn't be better off with a .tel and never again have to worry about disseminating her latest contact info to people? :)

Remember, you don't have to go and retrieve contact info for someone until you actually contact that someone. .tel makes it very easy to get the correct contact info every time you need it, and only then.