Group items tagged

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.

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.

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.

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

This session will provide an overview of the basics behind Data Portability, discussing some of the principles associated with it, how the social networking vendors are addressing it, and what you should be aware of as you consider providing or utilizing some of the newest standards that enable Data Portability.

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.

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.

Would a service like Matchmine fall prey to Strands’ do-it-yourself approach to providing specific ways in which individuals can use their own data portability information? Not likely. Data portability, even with the help of Strands, will still take some time to permeate online social media. And services like Matchmine will continue to evolve, and will likely find peripheral ways in which to further monetize the underlying social behavior that goes into the very use cases towards which data portability will be applied.

Existing participatory systems are designed to separately invite online user contributions in one capacity, and to aggregate collective value in another, but few environments attempt to holistically address the production of useful outcomes by moving participation towards meaningful and intelligent results. This determined focus on how best to design participatory environments to solve problems is particularly relevant given the world’s abundance of complex and urgent problems to be addressed. Methods for solving them collectively online have only begun to be explored.

WordPress got into the social networking game by absorbing BuddyPress this month. BuddyPress is a WordPress plug in set that creates a social network out of a multiple user WordPress installation (WordPress MU). Adding BuddyPress to the WordPress family is a smart move on the part of WordPress to stay fresh and relevant.

In the meantime, people who have other, more valuable projects that have been ignored and fallen by the wayside in the great quest for something only the top ten percent of computer users want. One of the most vocal advocates for Data Portability is Chris Saad, the guy who brought us Particls - a great program. Or, it could be great, if his attention wasn't elsewhere, Twittering and blogging endlessly about Data Portability.

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.

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

The goal of this task is to investigate, and if possible propose, a model that enable re-use of common observation models across the clinical trials and clinical practice contexts. This of course, include how Semantic Web specifications such as RDF/OWL can be leveraged to achieve this.