Phil Wolff proposes starting an interoperability workshop for cloud conversation platforms to discuss standards that would allow for greater connectivity between platforms like Skype, Google Talk, Apple, Facebook, and others. Currently these platforms are diverging in their technical approaches and do not interconnect, limiting their reach and network effects. The workshop would bring together representatives from major platforms to explore topics like models for conversations, contacts, media types, and network behaviors, with the goal of finding areas of convergence to benefit both applications and users by enabling cross-platform functionality and freedom of choice. Wolff suggests now would be a good time to start this conversation among protocol developers and end users.

1. Interop, please Phil Wolff, Skype Journal 10 March 2011

2. “Bruegel's paintings seem to attribute the ultimate failure of the Tower to engineering difficulties rather than to sudden, divinely-caused linguistic differences.” ̶ The Tower of Babel, Wikipedia

3. What if we start a standards/interoperability workshop for cloud conversation?

4. What if we start a standards/interoperability workshop for cloud conversation? Not just the cloud telephony part; the world needs interoperability across a much broader scope.

5. Consider Twilio, Voxeo, Skype, Telefónica/Jajah, Google Talk/Google Voice, Apple, Ribbit/BT, Yahoo!, TokBox, Microsoft/Nokia, Facebook, and Speek. All operate a public cloud communications platform, operate a private one for their own purposes, or are very likely to in the next 18 to 24 months. The list is growing. Together, they serve more than a billion people.

6. Their platforms are diverging on: Models of a conversation Models of contacts, relationship life cycles Models of groups of contacts Media and Modalities (IM, voice, video, 3D immersion/AR, subtitles, SMS) Dial Tone Availability Presence Activity messaging and streaming Intention Presence Peering Agreements Call failure modes Network failure modes Persistence The new call detail record (CDR) reporting User Interface widgets and experience design defaults

7. Early divergence can be good, as an industry explores the possibilities.

8. An industry with many platforms, however, benefits from some types of convergence.

9. The ability for applications to reach more people, working across systems. The opportunity for apps to run in more places. Network effects bigger than any one company. Calls to include parties from more than one network Product innovation within architectural layers, so changes in one technology don’t obsolete all the others. Portability of customer data. Freedom to move between and among accounts. Independence from any one platform provider. Convergence of the new call metadata useful for security, identity, billing, and peering.

10. Interopcan make this space into a more vital ecosystem and industry.

11. Now would be a great time to start a conversation by and for the people building the protocols and the people usingthem.

12. Starting Topics In a world of mashups (that sounds so last decade), the cloud conversation products are new islands of isolation. Are we ready to discuss interoperability? Who should be invited to participate? What will bring the right people together? What will it take to make a safe space for this conversation? How open can we make this conversation? What considerations affect timing? Next steps?

13. Let’s talk Phil Wolff @evanwolf pwolff@SkypeJournal.com Skype:evanwolf +1-510-316-9773 SkypeJournal.com