DataPortability

First and foremost, in the development of DP-related business models I’m seeking win-win solutions for consumers and businesses. As DP goes mainstream there will be proponents and opponents of a slew of different, important, and highly controversial aspects of DP. At the front of the line and at the top of my mind are privacy concerns. I actually think we have a chance to change privacy for the better, gain the (nearly) complete trust of consumers, and at the same time, provide businesses with better opportunities to engage in opt-in, targeted, 1-to-1 marketing. This is the holy-grail of DP IMO and the future of advertising.

This post represents a rough sketch-up of the future of DP and DP business models. It’s not quite the “sharing data between facebook and Myspace” that seems to be all the rage today. But I believe this is a realistic direction in which to head, and I think it makes a lot of sense to develop models that maintain customer privacy while sharing data in every aspect of their lives, not just on and over the Web. Furthermore, these models will help businesses employ next generation advertising that allow them to serve customers to the highest potential of the business.

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

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 Echo Nest is a music technology company founded by two MIT Media Lab PhDs. The Echo Nest’s proprietary music analyzer API automatically analyzes audio (e.g., aif, wav, mp3, m4a), and generates an XML file describing the musical and structural content of the music. Computation takes about 1/50th of the duration of the track and the text output is about 1/20th of the size of its corresponding mp3.

Unlike other automatic methods of acoustic feature extraction, which progress strictly on raw audio signal, our technology was inspired by how people perceive music.  As a result, developers are able to automatically extract and use a wide array of time-based musical attributes for any song, including: timbre, pitch, rhythm, loudness, onsets, beats, tempo, sections, time signature, key, etc.

The iPhone platform elegantly solves the design problem of small screens by greatly intensifying the information resolution of each displayed page. Small screens, as on traditional cell phones, show very little information per screen, which in turn leads to deep hierarchies of stacked-up thin information--too often leaving users with "Where am I?" puzzles. Better to have users looking over material adjacent in space rather than stacked in time.

It had to happen sooner or later. We’ve had Technorati. We’ve had TechMeme. Now we have Tweetmeme, which will track what’s hot on micro-blogging platform Twitter. The business of tracking the online conversation just a got shot in the arm with the tech equivalent of crack cocaine.

Robert Scobles ban from Facebook early this month brought up the discussion again about ownership of user data in social networks such as MySpace, Facebook and others, as well as about data portability. Robert Scoble did violate the terms of service agreement with Facebook; so much seems to be clear. What his actual motivations were for his actions are not so clear though. You can check out his version of the story at Computerworld and also 1938 Media's Loren Feldman's takes one and two on this incident as well.

It does not matter what the actual reasons were and what exactly happened, but one thing is clear, it brought attention to an issue that everybody who uses social networking sites is just all very familiar with. I for myself consider it a pain to rebuild profiles and connections from scratch at every social media site again and again. It takes time and as most others, is time the only commodity I have always a shortage of. Then I look at my profiles at the different sites and how they developed over time to realize that they are all looking pretty much the same, I even hooked up with the same people at all those different sites again.

Hello DataPortability.org It is actually looking very promising that this initiative will result into a standard that will be adopted by many social media sites. They are not going to reinvent the wheel and start creating something from scratch, but use and "mash-up" existing standards and initiative to create something new specifically aimed to solve the data portability problem.

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.

DataPortability.org is heading up a workgroup that will hopefully do just that. While many groups and companies are taking part in this effort, the recent addition of a few big name players has attracted a lot of attention.

WebProNews spoke with Chris Saad, the Co-Founder and Chairman of Data Portability.

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.

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.

MySpace has just announced that they will be launching their developer platform on February 5th. You can pre-register now by going to http://developer.myspace.com (requires login).

rom a technology perspective, Kapur says most of the specific details will be released on the 5th, but he did emphasize that the company has maintained an open relationship with widget developers, and wants them to be able to use data from MySpace in their applications, potentially including your friend’s list. With Facebook moving to allow developers to host applications on third-party sites and DataPortability continuing to gain traction, this seems like the only way to go.

Finally, Kapur told me that the MySpace Developer Program will support Google OpenSocial from day one. This may provide a much needed boost for OpenSocial, which has received criticism for offering very little in the way of tangible products since being announced.

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.

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.

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.

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

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.

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.

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!