Group items tagged

First things first. DataPortability is a brand… its a kind of un-organisation (a bit like BarCamps are un-conferences); a group of people and organisations who have the same philosophy, a philosophy of the portability of data. Every member of DataPortability should push for (advocate/evangelise) portability of data to web-users, developers and organisations.

The DataPortability Project will support other projects/groups working towards data portability (at the moment this explicitly includes communities involved in OpenID, OAuth, Microformats and the Semantic Web). Some members of DataPortability are also involved with legal issues and privacy which are just as important as the portability of data. The DataPortability Project is there to support people into a Web of Data.

Portability of data, or data portability is portable data. In other words, data can be copy/pasted and/or moved from one location to another. This is dependent on accessibility.

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: Who controls the direction of DataPortability.org? CS: DataPortability is managed like a wiki - participants step up to the plate and just get things done. Some of the most active participants join the Steering group to help set the direction.

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.

Whenever Microsoft Corp. eschews an open standard (think the OpenDocument Format, aka ODF), it gets pilloried. Whenever it embraces one, as it will soon do with DataPortability.org, fears rise that Redmond will twist it to its own advantage, (think Java) or, failing that, sabotage it. (ActiveX) So is the nascent DataPortability.org group at such risk from Redmond? Not according to a source inside the group. "The DataPortability group is made up of many voices - individuals who are passionate about solving the problem," the source said. "Microsoft's voice is a welcome addition but it is not the only voice in the conversation and it does not have any special consideration."

With the announcement of Microsoft joining the DataPortability workgroup, the attention is on the blossom workgroup more than it has ever been before. Naturally with all the added attention (as if Facebook and Google joining wasn’t bad enough) there is a fresh new round of people questioning the validity of DP and its associated stack.

Let me make this perfectly clear: Dataportability does not give any more or less users access to your personal information than before. Now keep that single point in mind while I give a simple example.

How do you explain to an end-user what DataPortability is, why they might want it, and where they might get it?

How do you explain to a developer what DataPortability is, why they might want it, and how they might achieve it?

Developers learn most effectively by developing something. Users learn most effectively by using something.

“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.

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.

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.

The news today is that Microsoft intends to join the DataPortability Project. So where’s the beef? Why are long-time influentials from all these large vendors joining the cause? What are we offering? What are we trying to do? What’s in it for them? What do they bring to the table?

First, I’d like to clarify that DataPortability is not mine. It is an initiative that was co-founded by many people who all believed that something was missing from the existing Identity/Data/Standards landscape. Something very small, but very important.

As you might know I attended the London DataPortability Lunch last week and met cool people like Chris Saad, Julian Bond, John Breslin, Tom Morris and others. Among other things we have been discussing the maybe first use case to tackle for Data Portability which is Discovery. As you also might know there was some discussion about how to approach the DataPortability problem space and one of the ideas which came out of that was my idea of dividing it into fields and levels. Now this general discovery use case nevertheless makes much sense because it seems to be a general starting point for every field we might address. So how does it work?

The DataPortability workgroup’s strongest voice, Chris Saad, noted among the DataPortability Design Principles that the mission ought to be less “fight the man” and more practical and useful goals. It will be interesting to see if the group’s finalized vision is limited to the import/export use cases, because these surely have the least potential. Otherwise, portability may not really matter to an average user, but the benefits to the user experience surely do, and I think selling DataPortability means selling the huge benefits of an efficient, distributed Web experience.

Forward-thinkers are creating innovative interfaces to your distributed data, and products are going to evolve quickly. Figuring out what portability means, what the best technologies are, and how this all looks from the user’s perspective are all pieces of a large puzzle that will strongly affect the future of the Web.

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

It was kind of heartening today - after reading yet another press release about some BigCo joining the DataPortability effort - to stumble upon this roadmap timeline of activities leading to a DataPortabilioty enabled web.  Kind of heartening in a cute naive way.

So lets please lighten it up on the press releases and claims of support - when its just not clear what the hell these companies are supporting or what they’re doing - at all.

Digg has joined the DataPortability Project, a group of websites cooperating to help you securely use your data however you want. Why? Because you own your data. It’s that simple. From the start, Digg has supported the idea that you own your own data.

Digg already supports many of the open standards that let you use your data on sites other than Digg, including RSS, OPML, and hCard. We use RDF to embed the Creative Commons public domain dedication into each page. Just this week, we added MicroID, a Microformat that lets you prove to other services that you own your Digg user profile. We’ll be adding more open standards, such as OpenID, APML, OAuth, and XFN, in the coming months.

One. DataPortability.org is a volunteer, community project.

Two. DataPortability.org takes nothing for granted and does not adhere to any one gospel of portability.

Three. Warning — this is a PSA. Let’s stop demonizing PR and using “PR” in place of moron, lightweight or unproductive.

Early adopters of the Web rolled up their sleeves to demonstrate what was possible on their own sites (even before animated gifs came along), so perhaps advocates of things like the Web of Data, opening the social graph and DataPortability should begin at home too…

I always say that you have to manage you online indentity and that you have to put effort in gaining online authority. This because the online world is getting more and more integrated with the real world and as a person you have to have an online authority to become popular in networks. But there are so many social networks and it takes so much time. Well possible dataportability may help to manage all your profiles online! Just watch the video.

My last column discussed the brand utility supported entertainment model in which content providers and marketers work upstream to create customized complimentary experiences. One option would be to align this model with the open standard objectives of DataPortability.org. Their mission: to gather "existing open standards into a blueprint for a social, open, remixable Web where your online identity, media, contacts and content can follow you wherever you go."

For brands and content creators, that means conversation would truly have to be initiated by the user. The user would own the data, and the brand content offering would have to be valuable enough to warrant an exchange. In essence, brand content would be bought with "data currency."

There are brand enthusiasts who participate in campaigns on an ongoing basis. Yet each time they return, these fans must register and sign-up for the full experience. If the brand were to embrace technologies such as OpenID, not only would it provide their fans access to cross-promotional properties around that campaign, it would also provide easy access to all future campaigns. And with future potential of data portability, people could take those experiences with them, introducing content to friends and hopefully igniting passionate new fans.

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.