This is an archived page from a previous event. Click here to go to the latest event.

A Glimpse Into the Future if XMPP and Wave are Successful

Jason Kolb, Technical Leader, Voice Techn., Cisco

Date: Tuesday, April 20

Time: 5:00 - 5:15 PM

Location: Salon E

While email was built on an open, federated standard, today's social networks sit on top of the Web as a series of (mostly) closed Web sites. Interoperability isn't even on the table and the best you can hope for is an API that exposes what you'd like to use. Even more disconcerting, a user's online presence is firmly embedded in a closed system--you can't take it with you if you outgrow the network. 

The XMPP protocol is now more than a decade old and provides rich presence and multimedia communication functions, along with personal event subscription and presence, all built on a Web-friendly platform that integrates beautifully with HTTP, email, and SPARQL. It's become the engine for many modern instant messaging platforms but hasn't seen much use outside of that sphere--yet. In mid-2009 Google released Wave to a limited audience. Wave is part Web client and part extension to the XMPP protocol. It could very well be the catalyst that is needed to push XMPP over the edge into mainstream use. The Wave protocol fills functional holes in XMPP, providing extensions that offer federation, real-time content updates and synchronization, and define a conversation's structure. 

In short, everything that's needed to build a powerful, distributed social communication network. It also has Google to market it. 

If successful, XMPP and Wave will have profound and lasting effects on our daily lives online. They will enable people to have a single point of contact, single sign-on, online presence, and a truly unified communication endpoint hosted at a personal virtual server. This will drastically undercut the role of today's social networks, relegating them to the role of unneeded middle-men and proprietary interfaces on top of a global and open social network. This opens up exciting new possibilities. Managing multiple devices will be easy as your online presence itself will be aware of which endpoint you'd prefer to use at any given time and be capable of text, audio, and video communication, responding differently depending on who is contacting you. Personal bots that live on your personal virtual sever will help you communicate and function even when offline, obeying your rules no matter what time it is. Conversation content and context stored in Waves can be marked up and exposed for search, allowing for richer context as the client tools mature. You will be able to publish your data to your virtual server for discovery and exploration using Linked Data (Semantic Web) technology, which will finally allow you to use your social graph as a true data source. All sorts of fascinating new uses will emerge as the true potential of this technology is absorbed and exploited by the market. 2010 promises to be an exciting year as Wave is rolled out and we begin to see new clients emerge--both for Wave and XMPP--and we catch a glimpse of what the next generation of communication looks like.

Deprecated: mysql_connect(): The mysql extension is deprecated and will be removed in the future: use mysqli or PDO instead in /home/ecommec/public_html/cgi-bin/mt/php/extlib/adodb5/drivers/adodb-mysql.inc.php on line 443
  • Isn't this a bit stale as a topic, most of us were writing about it a year ago, I'm afraid Wave's missed the point when it comes to XMPP.

    http://www.cleartext.com/do...
    http://www.cleartext.com/do...

  • Couldn't possibly agree more.
    My only worry's are that uptake of Wave has been pretty slow. Partly (imho) due to a lot of people just seeing it as Googles (currently rather crashy) GUI.
    Theres;
    GooglesWave/Fed1, Pygowave, and Ruby on Sails.
    Am I missing any?
    None of these are yet fully federated together, although some are close.

    For Wave to truly take of we need a few more servers running...preferably completely independent from Google. This would help client markers (like myself) demo Wave for purpose's far outside of the "email/wiki" text based functionality, and help promote it as a platform for just about any sort of social data exchange.

    It would also help if Google got their act together a bit and published a client/server spec for their servers.
    At the moment its a little like email before POP3/IMAP!

    But still, I have faith, and the potential is huge.

blog comments powered by Disqus