DataPortability: In-Motion Podcast - Episode 3
April 11, 2008 by Trent Adams
Thanks to everyone spreading the word, we’re really starting to pick up some speed. In the third espisode of the DataPortability: In-Motion Podcast show, hosts Trent and Steve are joined by Christian Scholz (aka MrTopf) in a chat with Kevin Marks, Developer Advocate at Google’s OpenSocial project.
After the news, the conversation starts with presentations that Christian’s been giving on DataPortability at various meetups in Germany, London, and virtually as part of the Second Life OpenGrid Project.
From there we dive into the discussion with Kevin and what’s up in OpenSocial, and how developers can get on board. He also mentioned participating in small coding projects proposed by DataPortability Project members Phil Wolf and David Recordon (who we hope to have on soon to talk more about it). There’s also a brief discussion about Google’s OpenID support and how to test out the Social Graph API.
Leading the episode, a brief news update on:
- RSA Conference 2008
- TotSpot Embraces DataPortability
- DataPortability Project Members and MyBlogLog FOAF
BTW - If you like this podcast, check out Christian’s TopfCast, too. He includes kewl tunes, for that full-bodied listening experience.
Episode 3: Listen | Comment
Subscribe: iTunes | Feedburner | Via Email
Episode Length: 0:48:08
Related Posts:
- 7/18/2008 - DataPortability: In-Motion Podcast - Episode 13
- 6/27/2008 - DataPortability: In-Motion Podcast - Episode 12
- 6/13/2008 - DataPortability: In-Motion Podcast - Episode 11
- 6/6/2008 - I'm In-Motion, what about you?
- 5/30/2008 - DataPortability: In-Motion Podcast - Episode 10















[…] Episode 3 is out now and among a little interview with me I was also invited to interview Kevin Marks, developer advocate (esp. for OpenSocial) at Google. We talked of course lots about OpenSocial and how it might fit into the DataPortability area (to me it’s still not so clear but Kevin said something thinks along the ways that you don’t move the data to the app but the app to the data. Of course this is one possibility but IMHO it does not solve the whole problem yet, like linking different networks together). […]