Committees: Difference between revisions

From Project VRM
Jump to navigation Jump to search
m (Reverted edits by Kelebek (Talk) to last version by Dsearls)
 
(14 intermediate revisions by 7 users not shown)
Line 8: Line 8:




== VRM Requirements and Specs Committee == (and Standards?)
== [[Standards_Committee | VRM Standards Committee]] ==  
 
Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson
Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson


Line 18: Line 19:
* Data transfer/portability is always under user control
* Data transfer/portability is always under user control
* Vendors can discover the appropriate service for each user
* Vendors can discover the appropriate service for each user


== VRM Organisation Committee ==
== VRM Organisation Committee ==
Line 28: Line 28:
== VRM Usage Committee ==
== VRM Usage Committee ==


Adriana Lukas & Chris Carfi & Deb Schultz & Alan Mitchell & Dean Landsman( & Sean Bohan) & Kaliya & Bart Stevens
Adriana Lukas & Chris Carfi & Deb Schultz & Alan Mitchell & Dean Landsman & Sean Bohan & Kaliya & Bart Stevens
(guys and girls, pls have a look at my thoughts below, Cheers Bart)
 
VRM ActionPacks are designed to help various influencers and decision makers understand and implement VRM principals and technologies into their next project or product. Please feel free to contribute to and share these packs freely.
 
They need to be written:
 
For Bloggers and Media
 
For Designers
 
For Developers
 
For Executives
 
Topics which need to be included are:
 
- Problem Overview
 
- Problem Specifics
 
Actions you can take
 
- Community Evangelism
 
 
- Open Initiatives
 
List open source projects that could benefit from input from this audience
 
- Implement VRM
 
A list of resources that make it possible for this [audience] to implement VRM into your next product or consultancy programme.
 
- Business Justification Guides
 
 
- Design/Decision Guides
 
- Reference Implementations
 
 
- Case Studies  - Industry specific
 
- List of places you can promote your outcomes/register your compatibility
 
- Host a VRM talk
 
- Sample Slides


- List of people to invite in your area (nominate yourself!)
[[What is to be done?]]


== VRM Compliance Committee == (and Standards? see VRM Requirements and specs)
== VRM Compliance Committee ==  
(and Standards? see VRM Requirements and specs)
Iain Henderson & Brett
Iain Henderson & Brett

Latest revision as of 13:50, 9 December 2009

Committees are based on goals that have been articulated and agree at the VRM meeting that took place at Google offices in Mountain View, CA on 2nd December 2007.


VRM Vision Committee

Dean Landsman & Doc Searls & Jerry Michalski & Charles Andres & Keith Hopper & Adriana Lukas & Iain Henderson & Deb Schultz & Alan Mitchell


VRM Standards Committee

Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson

Requirements that came out of a Change of Address Use Case analysis:

  • Address stored independently of any particular vendor
  • Owner of address can choose who stores canonical source
  • Data should be in an open format and portable without data or service loss
  • Data transfer/portability is always under user control
  • Vendors can discover the appropriate service for each user

VRM Organisation Committee

Doc Searls & Brett & Charles Andres & Joe Andrieu Charter process for subgroups see [[1]]


VRM Usage Committee

Adriana Lukas & Chris Carfi & Deb Schultz & Alan Mitchell & Dean Landsman & Sean Bohan & Kaliya & Bart Stevens

What is to be done?

VRM Compliance Committee

(and Standards? see VRM Requirements and specs) Iain Henderson & Brett

Retrieved from "http://cyber.harvard.edu/projectvrm/?title=Committees&oldid=4167"