Directory Info The search keywords contain company name, address, areas of business etc. Along with the phone number and email, this is what a basic listing in any on-line Yellow Pages etc directory contains. You'd assume this is why the DI keyword exists in the first place: to have a single SOURCE of real-time, accurate data in the DNS for directories to tap into. So why isn't Telnic using the DNS data SOURCE aspect as a major selling point to on-line directories to embrace .tel technology? (Not the single contact aspect. Haven't seen any public docs on that aspect.) Basically, it's not just about having a single point of contact, it's about having a single SOURCE of contact data. If customers had control over their own single source of listings such .tel, one change would affect all on-line directories. If a YP organization had a Telpages interface that they could query for changes, then they could periodically update their databases with the latest information. Or better yet, just read the DNS, although that would be much slower than their own database. And a question for those directories that are experimenting with tels: what happens when your customer changes their .tel information - do they also have to inform you to change your database? Ideally the answer should be NO. Mark |
TelPages as the Source for On-Line Directories So this presents another idea. Could TelPages ever become the standard source for all on-line directories? Subscribe to it and get all sorts of information and changes. Since TP is actually a database of some of what's in the DNS, a Telnic application could ping all subscribers through dedicated sockets (?) that changes in a specific area have occurred. Kind of like a Twitter for directory owners. Mark |
I'm looking at using www.TelephoneDirectory.tel to promote on-line directories. Anybody want to trade 3-way links to developed directories? Mark |
Quote:
What is the diference between TELview and TELscope?[/size] |
Quote:
Telview is for mapping tels. TelScope might be for coupon management, not sure yet. But couldn't resist getting those names. Mark[/size] |