Jeremiah Owyang Suggests some deliverables for DataPortability
January 12, 2008
Jeremiah Owyang is one of those people with a sharp mind and a clear communication style that makes everyone stand up and listen. His input is always welcome and he has posted some great ideas for DataPortability.org. I thought I would respond to them here.
I will post his requirements and my comments after each.
1. Charter document: This lists the groups purpose, who’s held accountable, and what we expect to see and goals
We have started a Workgroup Roadmap to ensure that the right documents get created and ratified. So far we have an emerging decision making structure and a path for deliverables.
We also have an emerging ‘Agenda‘ which will be expanded into a Manifesto.
2. Needs: Problem definition document, what exactly is broken?
3. Plan: A strategy doc that outlines the next steps the group will take to fix the problem, dependencies, phases, and risks.
Again, we have the Roadmap…
4. Calendar: Of regular meetings, and who’s assigned to each problem. Dates that indicate what will be done when.
The dates will be set by the Roadmap. Meetings, at the moment, are not planned. We are discussing things on the Workgroup Forum.
5. Meeting minutes: A regularly published list of notes after each meeting that indicate the progress done by each member
The discussion forum is actually open to the public. Watch the conversation in real-time. This is 2008 people!
6. Document: Body of standards, the rules, and the final output
The main DataPortability deliverables will be the DataPortability Technical Blueprint and a DataPortability Policy Blueprint. These will map out a way for vendors to implement the world’s open standards for maximum interoperability.
7. Openness: Public announcements of progress of major milestones
Again, the discussion is open and transparent and the public can watch in real time, and can also participate in the public group.
Members will obviously blog, tweet and shout results from the rooftops.
8. Actual results: our identity portable, safe, managed and controlled by the owners.
This will be up to vendors – and to bloggers, media and users who need to choose vendors who respect their DataPortability rights – once the Blueprints are ratified of course.
Can you suggest improvements? Comment here, or join the Public Discussion and start a thread!
Don’t forget to read the rest of his post.