Corvallis-based MyStrands, the service that—among other things—lets you share and compare your musical tastes, has announced that they have decided to join the Data Portability Working Group.
A number of folks are putting their hopes in the Data Portability concept. And, to be sure, their recent “skyrocketing into the tech-public consciousness” momentum may have given them the best chance of solving the problems at hand.
As Scott Kveton highlights in the MyStrands post:
We’re really excited about the work that the Data Portability (DP) group is chartered to do. The goal of the group is to build a set of technical and policy blueprints based on existing technologies and concepts that will allow for the free-flow and control of data by users among sites on the web. Taking advantage of the building blocks like OpenID, OAuth and microformats allows the effort to move that much faster….
MyStrands is committed to the Data Portability group because we believe we can really help make things happen and be an integral part of its success.
Coincidentally, another little company you may have heard of—named Microsoft—just announced that they were going to join the Data Portability Working Group, as well. But, I’m not interested in covering that, because a) Last time I checked, they were a bit north of the Silicon Forest, and b) They may have gotten a little bit of press about it already.
In fact, Portland-based blogger Marshall Kirkpatrick has an insightful write-up on the Microsoft news:
Microsoft’s joining the group is an event of sufficiently complex historical meaning that I’m hesitant to try and interpret it here. Microsoft has both been the ultimate example of lock-in and also an important force behind other open standards efforts on the web, including OpenID. Though no fan of Microsoft, I am consistently excited about what the Live team in particular does. I’ll look for analysis of this and future news about implementation at Live from my favorite source on the topic, LiveSide.
Deep breath. Okay, I realize I’ve just thrown around a whole bunch of jibber jabber at you, which probably makes absolutely no sense.
Just what is this “data portability” and why would we want it? Here’s a simple explanation. (Apparently, Vimeo’s embed code doesn’t like WordPress, so I’m linking now instead. Apologies for the extra click.)
For more on MyStrands reasoning behind joining, read Why MyStrands is joining the Data Portability Workgroup. For more on the Data Portability Working Group, visit dataportability.org.