Group items tagged

I've been following the barrage of news regarding Data Portability with a mix of excitement and trepidation. I've been a proponent of OpenID, and regularly use services like PassPack to keep track of the ridiculous number of log-ins I seem to have accumulated. At the same time, I worry about what data is essentially mine, and what doesn't rightfully belong to me. I'm still not convinced that Robert Scoble owned the contact information for his 5000 "friends" on Facebook, and that is the facet of Data Portability that worries me, at least a little.

I'm finding that the more avenues I have to share my data online, the more I find myself wanting to pull what I already have out there back. I find it hard to imagine that I'm the only person who worries about the over-reaching umbrella of Google linking up to every other site who joins the Data Portability Workgroup and the sheer amount of amassed information any one entity could end up possessing about me.

The social web is booming, signing up new users and generating new pieces of unique content at a steady clip. A recurring theme of the social web is "data portability," the ability to change providers without leaving behind accumulated contacts and content. Most nodes of the social web agree data portability is a good thing, but the exact process of authentication, authorization, and transport of a given user and his or her data is still up in the air. In this post I will take a deeper look at the current best practices of the social Web from the point of view of its major data hubs. We will take a detailed look at the right and wrong ways to request user data from social hubs large and small, and outline some action items for developers and business people interested in data portability and interoperability done right.

The core idea of vendor relationship management (VRM) is simple: the more empowered individuals are when it comes to managing and using personal data – including the ability to manage their relationships with vendors – the greater the benefits to both sides.

Meanwhile, new technologies such as infocards (which create a secure “pipeline” for two parties that want to share information online) make it possible for customers to “co-manage” customer databases. Addresses and contact details can be updated in advance, so that organisations do not discover that the change has taken place too late.

Brett McDowell, executive director of Liberty Alliance, expects a high percentage of member companies to seek certification for the VPI standard. “If these programmes are put in place, there is no way this won’t change the way markets work,” he says.

If you are anything like me (which I hope for your sake you’re not), you’ll be constantly tripping over the names of new data portability initiatives concerned with exchanging social information. Combine any of the following words and create a new name [‘Open’, ‘Social’, ‘Contacts’, ‘Data’, ‘ID’], I checked all the domains and guess what? They’re all taken. (No shit, Sherlock) I thought it would be helpful to list these initiatives and provide a quick comparison of what they do and why they exist. This is my current understanding of the various players. Please comment and correct me where I’m wrong or have omitted important initiatives.

At Mahalo we just rolled out rolled out Microformats for relevant search result pages. So what does this mean, and what are Microformats? Well, they are data classes that help machines and people identify and export information. Data such as contacts and address information is much easier to manage, search engines can also better catalog the info. Yes a little bit of the semantic web of tomorrow….today!

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.

What is needed though is a discussion about this and what the best practices in these cases should be. One option would be the opt-in for such XFN-markup but of course those links would still be available although not that easily extractable. Making it more private would probably harm the site’s usefulness. Removing them might also harm social services such as dopplr which make good use of them to find your contacts on dopplr.

So it’s many questions to be answered and I wonder what a good process might be to answer them. Surely there is the  around but of course they cannot just publish guidelines and the problem is solved. A broader discussion is needed and for a start maybe an exact description of the problem and coming from these some proposals to solve it.