CATEGORIES
- WEB STARTUPS
- WEB NEWS
- CONFERENCES
- WEB TECH JOBS
- VENTURE CAPITAL
- MICROSOFT
- INTERVIEWS
- ADVERTISING
- VIDEO
- ALL TOPICS
- ALL COMPANIES
CONTRIBUTORS
- ADRIAN CHAN
- ALICIA NAVARRO
- ALLEN STERN-EDITOR
- CORSIN CAMICHEL
- DARREN HERMAN
- HANK WILLIAMS
- MARK DAVIS
- RICK TUROCZY
- SANFORD DICKERT
- SHANNON CLARK
DataPortability - What It Is and What It Isn't
Written by Allen Stern - February 12, 2008
We've written about DataPortability before, most recently we wondered what DataPortability means after watching a video by a Plaxo employee. Today that DataPortability group has posted a list of what it is, and what it isnt:
What DataPortability Is:
- Formalizing the discussion of what a users rights are over their data (?)
- Group is made up of individuals, companies, and organizations
- Output of DP Project is freely available
- Will define "Data Portability" generally and within context of the project
- Will help to normalize terminology used within the Data Portability space
- Will help to syncronize efforts across other Data Portability projects.
- Advocacy for Best Practices in Data Portabililty space.
- Using existing technologies, stitching them together.
- Going to define a vision for the future.
- Going to define capabilities, not technical solutions
- About research and education
What DataPortability Is Not:
- An advocacy for a single technology solution
- Developing new technology solution.
- Going to force data into the public that shouldn't be
- A legal entity providing legal-level precision.
- Currently end-user focused
Not end-user focused? Isnt't that the whole point of Data Portability?
COMMENTS - Add New Comment
seriously, way to clear that up
Interesting list. Sounds similar to what is said here:
http://www.readwriteweb.com/archives/opensocial_social_cloud_for_developers.php
Regarding your last point:
"Not end-user focused? Isnt't that the whole point of Data Portability?"
When posting this list I probably should have done a better job of conveying the tenor of that bullet point when made in the meeting.
Let's see if this helps. The meaning here was that the DP Action Groups should be focused on "what can technology developers be doing" right now rather than "what can end users be doing" as part of the DataPortability Project.
Basically, we got kinda' stuck in the meeting talking at the same time about what how we should communicate with the developers of systems (eg. propose technical solutions they can actually use), and their end user/consumers (eg. what will they expect of portable data).
So, the decision was that we should focus more on talking to developers to help them select existing standards that effectively link together as part of an overall DP methodology. In that light, we're (temporarily?) sidelining the need to speak to multiple audiences.
Whew... I'm not sure if that's any more clear, but I hope it gets us closer. It's possible I've clarified our thinking, but you still disagree (that's kewl, we'd love to hear your thoughts there).
In case I'm still not making myself clear enough, perhaps a real-time chat (via Skype, IM, or phone) would help? You can grab my content data off my link.