[enum-wg] Could Web 2.0 be the killer application for ENUM?
Rui Ribeiro racribeiro at gmail.com
Thu Oct 29 00:24:36 CET 2009
Hi All, Today I was thinking on diferente applications for ENUM. While VoIP is a nice (killer app), it "seems" to confict with established businesse models and services. What about if there is other applications that could use ENUM that are based on a completly different model? Some of the biggest rising applications on the WEB are Facebook, Twitter, ... and so on. They provide some kind of communication, in fact, it's a mix of: instant messaging, picture sharing, presence, ... and all together. In fact, there are some subset web applications that, together, can provide to the used most of their digital needs. If you have visited and used them you may know that there are some features that are better on one site, and others better on others. Not because they are technicaly better, but because you, as a user, like them better. Then I was thinking about ID's on this diferent web 2.0 services. If you have a bizard name, you are lucky, but if your name that conflicts with another user on the Internet, you are in trouble. You have to come up with lots of diferent ID's for diferent services. Then there is another issue... what if I don't like "facebook" anymore and now the hipe is on "bookface" (another web 2.0 application, similar to facebook)? My social network will just paralise on facebook, and I would have to republish on "bookface". What if my microblogging site starts to be other than twitter, what would happen to all my followers? What if ENUM could provide references to microblogging site, to presence site, picture sharing, ...? Yes, I now that Web URL's are already enabled on ENUM, but I'm thinking a little further... what if we could publish the URL with the application type reference, not just the WEB site. It happens already with VoIP, where the register states the type of protocol that should be used: SIP, h323, tel, ... Technically everything is possible on ENUM, as it is a swissknife where each blade is made out of RFC's. ;-) The benifit for the user could be the ability to point all the applications to the ENUM number, and the applications would then go and get the information on the right place. Why publish the microblogging link, the presence/status link and so on if you could just publish your ENUM number? All the followers would just following you any way, even if you change the application. For ENUM, it could be an application outside of the "voip box" that could push to the forefront of the innovation wave. Think of ENUM register as a personal ID, and not as a phone number... is this a bad assumption? I know that the number is given by the teleco industry/regulator and not by the state it self, but what is you phone number other than you personal ID? With portability services (hopefully) we could maintain the same number for ever, right? Thanks, Rui Ribeiro racribeiro at gmail.com
[ enum-wg Archives ]