Difference between revisions of "Committees"

From Project VRM
Jump to navigation Jump to search
m (Reverted edits by Kelebek (Talk) to last version by Dsearls)
 
(32 intermediate revisions by 7 users not shown)
Line 1: Line 1:
 
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.  
 
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 Goals ==
 
  
  
#Define and advocate a clear vision for a VRM world
+
== VRM Vision Committee ==
#Ensure the Development and publishing of open standards and specifications for VRM services
 
#Create a lightweight and effective organisational structure
 
#Drive VRM usage
 
#Create and oversee VRM compliance program
 
  
 +
Dean Landsman & Doc Searls & Jerry Michalski & Charles Andres & Keith Hopper & Adriana Lukas & Iain Henderson & Deb Schultz & Alan Mitchell
  
  
== VRM Committees ==
+
== [[Standards_Committee | VRM Standards Committee]] ==  
  
 +
Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson
  
==== VRM Vision ====
+
''Requirements that came out of a '''Change of Address Use Case''' analysis:''
  
Dean Landsman & Doc Searls & Jerry Michalski & Charles Andres & Keith Hopper & Adriana Lukas & Iain Henderson & Deb Schultz & Alan Mitchell
+
* 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 ==
==== VRM Requirements and Specs ==== (and Standards?)
 
Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson
 
 
 
==== VRM Organisation ====
 
  
 
Doc Searls & Brett & Charles Andres & Joe Andrieu
 
Doc Searls & Brett & Charles Andres & Joe Andrieu
 
Charter process for subgroups see [[http://wiki.idcommons.net/index.php/Working_Groups]]
 
Charter process for subgroups see [[http://wiki.idcommons.net/index.php/Working_Groups]]
  
==== VRM Usage ====
 
  
Adriana Lukas & Chris Carfi & Deb Schultz & Alan Mitchel & Dean Landsman( & Sean Bohan) & Kaliya
+
== 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 ==== (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 18: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