Group items tagged

It is a frustrating fact of modern internet life. Users of websites such as Facebook and Google spend hours building up and maintaining friend lists and e-mail address books, but when it comes time to move such social information to another online service, they frequently find it impossible to get their data back out. Instead, they must start re-entering their personal details from scratch.

That may soon change. Over the past year, growing numbers of influential voices have been calling for the creation of common standards for "data portability" — a move that would enable widespread sharing of social information between websites.

Supporters of data portability admit that it is still early days. "There are millions of people involved [but] there are only a relatively small number of social networking sites that are exporting," says Berners-Lee.

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.

What are the elements of a VRM data portability policy? The basic elements of a VRM data portability policy should include: Data retention agreement - How long will my data be retained for? For example - for the life of the relationship plus 30 days. Data reuse agreement - Will my data be used for purposes beyond the original transaction Data ownership agreement - What elements of the data belong to the vendor such as a Frequent Flyer number Data portability agreement - The data that is the subject of the agreement may be stored by the vendor, or it may be held by a data custodian in a Personal Data Store. Data access agreement - The data that is the subject, or a sub-set, of the agreement should be accessible to third parties that have been granted access by the user. For example, granting access to my shipping address information at Amazon by a third party vendor I have performed a transaction with.

What does all this mean? It means we can expect the web to get itself organized, in a hurry. At stake is a significant amount of traffic from Yahoo search, and anyone else that may choose to build applications on top of this data.

Yahoo’s support for semantic web standards like RDF and microformats is exactly the incentive websites need to adopt them. Instead of semantic silos scattered across the Web (think Twine), Yahoo will be pulling all the semantic information together when available, as a search engine should. Until now, there were few applications that demanded properly structured data from third parties. That changes today.

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?