DataPortability

Anyone who has been involved in Open Source software development knows that you have to have a steering group, and there has to be some hierarchy. You can't get a ship moving in any direction with 50 oars in the water each rowing in their own direction. I understand that in order to have buy-in from so many different groups, no one wants to alienate anyone, but the reference made at the meeting (and I'm sorry I forgot who made it) to OpenID was a valid one. They developed the technology, then took it out to various companies and asked for buy-in. In order to "strike while the iron is hot," the luxury of having 100 people all defining things differently and addressing different concerns before there is even a rudimentary roadmap makes the scope of the project much larger than it has to be, and slows down progress.

In the last couple of weeks there have been a number of very positive steps forward for Data Portability in general and the DataPortability Project specifically. These include wins by the OpenID Foundation, the IC report, the DataPortability Report and others.

A couple of trends, though, are causing me a little concern and may require a slight course correction before they spin out of control and fragment, rather than standardize, the ecosystem.

1. Tightly coupled OpenID Implementations

Time to continue the conversation about DataPortability... this time using video.We want to hear your thoughts about DataPortability recorded as a short video. We hope to share these videos individually as well as compile them into a single video to help the community understand expectations, goals and themes that are emerging in the discussion.

On Sunday, we had a significant discussion on data portability and about the activities, responsibilities and opportunities of and for the eponymous group which has recently generated much hype and buzz but little, (as far as I’ve see) clarity and/or cogent strategy for advancing its expansive charter:

So anyway, I do believe that there is an opportunity here and Chris Saad is correct that getting a number of the prominent players in this arena to come to the table on this topic is a feat; however, simply bringing them together without engaging with the gnarly problems and policies that have kept data portability from becoming a reality could bring more confusion and angst than benefit.

The frustration over the minimal barrier to “becoming a member” of the group (you simply have to sign up for a mailing list) and the focus on large vendors without advancing an agenda with teeth and clearly defined metrics for success was palpable. But so was the desire to make some progress, and if not come to complete agreement, to at least identify concerns shared by the majority of us and perhaps develop a strategy to deflate the hype to date and get the group moving in a productive direction.

Despite the valid concerns that some have with Google’s Social Graph API, I thought I would talk about the technical possibilities. My social graph may be of particular interest becuase I had used my Wordpress blog’s XFN feature to mark up the blogs I read as “muse” and my profile on at least 10 social networks as “me.” Using the Google’s Social Graph API demo you can see my extensive list of FOAF and XFN URLs. There is also a machine readable format that could be fed into a new social network to find friends on that network. (click for a larger version)

The world has changed. At least the marketing world. The era of mass marketing and advertisment as we knew it for many years has passed. Of course TV is not dead but it’s more and more superceded by the internet with all it’s channels for niche entertainment and self expression. Banner blindness and shrinking advertisement effectiveness have added their part. And so companies look out for other ways to reach potential and existing customers.

Add to that the success of the DataPortability Working Group which set policies and technical guidelines in how to create a World Wide Web in which data is more freely flowing around than ever before bringing us closer and closer to seamless networking experience and a semantic web.

This of course is only a glimpse of what might be necessary tomorrow. And the question is of course how far this tomorrow is away. Several things are of course available already or being worked on. The Google Social Graph API is there, blogging and commenting in Plone is worked on, Multimedia support is available, OpenID is as well (but maybe could be enhanced).Creating a social networking layer using e.g. plone.relations and membrane is not too complicated to implement and marking things up with microformats is also no magic.

Caring is sharing, people, especially when it comes to your personal data. Leading developers from important social-network sites joining a "data-portability" advocacy group doesn't represent history in the making. It's a marketing campaign to make everyone feel sickly sweet, knowing that these websites are so concerned about our information. Like the Care Bears, by signing on to the DataPortability Working Group, top coders like Brad Fitzpatrick, Dave Recordon, and Ben Ling have joined forces to form a group which we can only call by one name. Presenting: The Share Bears!

The DataPortability initiative just released their report for the month of January. I love the open approach the group has embraced to share the issues, highlights, and progress with the community.

The Good: The work is being broken down into a bunch of action groups to help get the teams organized and break the work into manageable chunks.

The Bad: Like many similar efforts, the big vendors agree to participate and make a lot of noise about it, but they haven’t all been doing the real work necessary to make it succeed. With any luck, this open approach will convince some of the vendors that they need to participate and contribute if they want to be part of the initiative.

When Facebook joined the DataPortability.org Workgroup a few weeks ago, the press described the move both as a “bombshell” as well as “brilliant PR”. In order to understand what Facebook’s decision to join actually means a little bit better, I spoke with Chris Saad, Co-Founder and Chairperson of DataPortability.org.

IF: What does it mean for companies like Facebook to “join” DataPortability.org? CS: It means they agree to engage in the conversation and work towards a blueprint for maximum interoperability between applications.

IF: Has Facebook promised to implement any particular functionality by any particular time? CS: Not yet - but once the blueprint is done we can then start asking vendors to implement things. Many other vendors have already moved quickly - in the last few weeks and months lots of vendors have been implementing OpenID, etc - these things are not unrelated.

“Connect. Control. Share. Remix” is the new slogan used by DataPortability Group.but it reminds me the Coriander release from Netvibes: (Re)mix the web.

A few months ago, we announced that we were opening the social graph and invited others to join us. An effort like that encompasses many different technology projects and all kinds of different companies; in just a few months the idea of opening up social networks has received a lot of attention. Today we're excited to share an amazing new plugin for Movable Type that allows you to aggregate, control, and share your actions around the web and we're the first to bring this sort of functionality to free and open source blogging tools.

It's worth revisiting some of the successes the openness movement has accomplished in just the past few months: Google's OpenSocial released new versions of its APIs and we hosted a wildly successful hackathon to help support the creation of new widgets for the standard. OpenID 2.0 shipped and both Google and Yahoo! are now supporting OpenID, bringing hundreds of millions of new IDs to the community. The group DataPortability.org was formed and released a video reinforcing these themes around openness. And finally, we've made good on our promise to let you show off all the services you belong to, with TypePad and Vox automatically letting you list your accounts around the web on your blogs using Microformats to link to your profiles. And as of today, the same ability is available for Movable Type.

As we explained half a year ago, we're on a mission. Like we said then, blogs change the way we communicate. Just like with TrackBack, OpenID, opening the social graph, and so much else in blogging, we're hoping that we can influence everyone else to follow our lead and move blogging forward with us. Bringing your actions around the web under your control is a fundamental next step to making all of our blogs even more powerful and expressive.

Data portability is an idea long championed, and becoming more important all the time.  As we continue to load our online lives on to various social networking sites, the concept of making it easy to get that information back off again, and re-using the information on the next big site without having to start over from scratch are compelling, reasonable, and just plain logical.  Why would you want it any other way?.

It's a good sign that DataPortability.Org is gaining traction.  It's also a good sign that Microsoft has joined.  While Microsoft certainly can't be thought of as a leader in the move to open up our data, it has been making serious strides to open up a number of its platforms, and a common vision shared by the members of DataPortability.Org could make control of our own data something closer to a reality.

I’m sure some folks are wondering exactly what this means. Even though I was close to the decision making around this, I believe it is still too early to tell. Personally, I share Marc Canter’s skepticism about Dataportability.org given that so far there’s been a lot of hype but no real meat.

As far as I can tell, Dataportability.org seems like a good forum for various social software vendors to start talking about how we can get to a world where there is actual interoperability between social software applications. I’d like to see real meat fall out of this effort not fluff. One of the representatives Microsoft has chosen is the dev lead from the product team I am on (Inder Sethi) which implies we want technical discussion of protocols and technologies not just feel good jive. We’ll also be sending a product planning/marketing type as well (John Richards) to make sure the end user perspective is also being covered. You can assume that even though I am not on the working group in person, I will be there in spirit since I communicate with both John and Inder on a regular basis.