Group items matching

in title, tags, annotations or url

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

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.

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

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.

As the web grows exponentially in scale and complexity, an issue that becomes increasingly pressing is data ownership. There has been a lot of noise lately about how Facebook Connect, Google Friend Connect, and even MySpace’s Data Availability.

The Data Portability Project is trying very, very hard to solve these serious issues. They’re seeking to unite the socio-rhetorico-legal precedent with the growing list of open technologies and specifications (OpenID, OAuth, RSS, OPML, MicroFormats, Creative Commons, to name a few) and make sure that these proprietary bits, bytes, friends, enemies, birthdays, activies, pictures, videos, lifestyles, etc. are made open to the content creators (read: YOU, not Mark Zuckerberg).