Project VRM - User contributions [en]

Main Page

2011-07-09T18:56:01Z

WikiAdmin:

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal the customer side of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a research and development project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls], a fellow at the Center, to encourage VRM development and to conduct research on its premises and its progress.

When the project began in 2006, Doc saw it as "a way to fulfill the promise of [http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue":

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events and site.

Read more about ProjectVRM on the [[About | About Page]].

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)? VRM tools and services will answer these and many other questions that could not be asked before the Internet came along and cannot be asked, as long as sellers continue to hold all the relationship cards.

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones'' to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, plus other social goods.

== VRM Terminology ==
Like any new market [http://www.proxykey.com Paid Proxy], VRM requires the introduction of a handful of new terms. The community is currently (October 2010) using this wiki to develop Wikipedia entries for the following terms. Feel free to help us by reviewing and editing the following pages (or our [[Wikipedia Article Discussion]] page):
* [[Personal data service]]
* [[Personal data server]]
* [[Personal data store]]
* [[Personal data ecosystem]]
* [[Personal Cloud]]
* [[Personal Data management]]

We encourage discussion of these definitions on the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Please add other terms you feel are important to harmonize within VRM and with related [http://www.shindiristudio.com/ web design] communities.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:

*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org
*[[Personal RFP]]
*[http://www.gofrugal.com/pos/point-of-sale.html Project tracking]
*[http://themineproject.org/ The Mine! Project]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

*[[Vision Committee]]
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]

== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] November, 2011, Mountain View, CA]

=== Past Events ===
2011
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Or edit this wiki by signing up at the top of this page.

Main Page

2011-07-08T06:16:14Z

WikiAdmin:

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal the customer side of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a research and development project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls], a fellow at the Center, to encourage VRM development and to conduct research on its premises and its progress.

When the project began in 2006, Doc saw it as "a way to fulfill the promise of [http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue":

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events and site.

Read more about ProjectVRM on the [[About | About Page]].

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)? VRM tools and services will answer these and many other questions that could not be asked before the Internet came along and cannot be asked, as long as sellers continue to hold all the relationship cards.

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones'' to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, plus other social goods.

== VRM Terminology ==
Like any new market concept, VRM requires the introduction of a handful of new terms. The community is currently (October 2010) using this wiki to develop Wikipedia entries for the following terms. Feel free to help us by reviewing and editing the following pages (or our [[Wikipedia Article Discussion]] page):
* [[Personal data service]]
* [[Personal data server]]
* [[Personal data store]]
* [[Personal data ecosystem]]
* [[Personal Cloud]]
* [[Personal Data management]]

We encourage discussion of these definitions on the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Please add other terms you feel are important to harmonize within VRM and with related [http://www.shindiristudio.com/ web design] communities.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:

*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org
*[[Personal RFP]]
*[http://www.gofrugal.com/pos/point-of-sale.html Project tracking]
*[http://themineproject.org/ The Mine! Project]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

*[[Vision Committee]]
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]

== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] November, 2011, Mountain View, CA]

=== Past Events ===
2011
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Or edit this wiki by signing up at the top of this page.

Main Page

2011-07-05T14:24:21Z

WikiAdmin:

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal the customer side of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a research and development project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls], a fellow at the Center, to encourage VRM development and to conduct research on its premises and its progress.

When the project began in 2006, Doc saw it as "a way to fulfill the promise of [http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue":

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events and site.

Read more about ProjectVRM on the [[About | About Page]].

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)? VRM tools and services will answer these and many other questions that could not be asked before the Internet came along and cannot be asked, as long as sellers continue to hold all the relationship cards.

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones'' to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, plus other social goods.

== VRM Terminology ==
Like any new market concept, VRM requires the introduction of a handful of new terms. The community is currently (October 2010) using this wiki to develop Wikipedia entries for the following terms. Feel free to help us by reviewing and editing the following pages (or our [[Wikipedia Article Discussion]] page):
* [[Personal data service]]
* [[Personal data server]]
* [[Personal data store]]
* [[Personal data ecosystem]]
* [[Personal Cloud]]
* [[Personal Data management]]

We encourage discussion of these definitions on the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Please add other terms you feel are important to harmonize within VRM and with related [http://www.shindiristudio.com/ web design] communities.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:

*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org
*[[Personal RFP]]
*[http://www.gofrugal.com/pos/point-of-sale.html Project tracking]
*[http://themineproject.org/ The Mine! Project]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

*[[Vision Committee]]
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]

== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] November, 2011, Mountain View, CA]

=== Past Events ===
2011
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Or edit this wiki by signing up at the top of this page.

About

2011-07-02T17:18:14Z

WikiAdmin:

Customer Relationship Managment (CRM) [http://en.wikipedia.org/wiki/Customer_Relationship_Management Wikipedia says] is "used by companies to manage their relationships with clients". It involves "Information stored on existing customers (and potential customers)" and "is analyzed and used to this end". Specifically, "Automated CRM processes are often used to generate automatic personalized marketing based on the customer information stored in the system".

"Automated" is the operative word here.

The top four [http://www.destinationcrm.com/topics/topic_index.asp topic centers] at [http://www.example.com DestinationCRM.com] are "Sales automation", "Marketing automation", "Customer Service/Call Centers" and "Analytics". Needless to say, the term "relationship" in CRM is oxymoronic. There is no relationship here. Not with real customers. This is obvious every time a customer encounters a call center.

Customer service hell (a phrase that brings up nearly two million results in a [http://www.google.com/search?hl=en&q=customer+service+hell Google search] for it) isn't CRM's fault. The problem is, CRM has nothing to relate to. Beyond the identities we carry in our wallets and purses (all issued by  and limited to  organizational silos), we have nothing a CRM can relate to. Customers have no technically sophisticated means of relating to vendors, or to any organization.

That's what VRM  Vendor Relationship Management  seeks to provide. It's the customer-side counterpart of Customer Relationship Management. It's the set of native tools used by customers to relate to vendors  as much or as little as they like, and on their terms.

Project VRM is a development effort at the [http://cyber.law.harvard.edu/home/ Berkman Center for Internet and Society] at Harvard University, and is led by [[Doc Searls]], a fellow with the Center.

As a topic, VRM grew out of work by Doc and many others around what came to be called "user-centric identity". The [http://identitygang.org Identity Gang wiki] is a portal into the user-centric identity conversation that has been growing ever since the Gang was first convened on a December 31, 2004 Gillmor Gang podcast, and was given a "clubhouse" by Berkman Fellow John Clippinger not long afterwards.

In respect to identity, a critical aspect of VRM is ''selective disclosure'' of personal information. It is essential that individuals maintain full sovereignty over their digital representations in the marketplace, and perform from a position of full control over their personal data.

It is Doc's belief (and this project will test his hypothesis) that VRM is required to bring a useful and productive balance of power between vendors and customers, supply and demand  for the good of both  in the marketplace.

== External Links ==

* [http://www.shindiristudio.com/ Web Design]
* [http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO]

PayChoice

2011-07-02T09:14:52Z

WikiAdmin:

Note: PayChoice is the name of a company and not an available domain name. [[EmanciPay]] is a new name for the model, which we are vetting at the [[VRM West Coast Workshop 2009]]. Go to [[EmanciPay]] for current editing on the subject.

=== Overview ===
PayChoice is a new business model for media: one by which readers, listeners and viewers can quickly and easily pay for the goods they use â on their own terms, and not just those of suppliers' arcane systems.

The idea is to build a new marketplace for media â one where supply and demand can relate, converse and transact business on mutually beneficial terms, rather than only on terms provided by thousands of different silo'd systems, each serving to hold the customer captive.

PayChoice is a breed of VRM, or Vendor Relationship Management. VRM is the reciprocal of CRM or Customer Relationship Management. VRM provides customers with tools for engaging with vendors in ways that work for both parties. PayChoice is one of those tools. Or a set of them.

=== Background ===
We now live in a media environment where goods previously sold directly or paid for by advertising are freely available and shared widely over the Internet. A number of factors contribute to a business and social conundrum for suppliers of those goods:

* Easy copying and sharing makes the goods freely available at growing ease and convenience.
* Copying and sharing is so widespread and common that punishment for copyright and other usage violations touches only a small minority of offenders, and has proven to be a losing proposition.

What the marketplace requires are new business and social contracts that ease payment and stigmatize non-payment for media goods. The friction involved in voluntary payment is still high, even on the Web, where one must go through [http://www.shindiristudio.com/ web dizajn] complex forms even to make simple payments. There is no common and easy way either to keep track of what media (free or otherwise) we consume (see [[Media Logging]]), to determine what it might be worth, and to pay for it easily and in standard ways -- to many different suppliers. (Again, each supplier has its own system for accepting payments.)

PayChoice will create a "buy button"-simple payment system to allow readers, listeners and viewers to pay whatever they like, at their discretion, for whatever media products they use. For too many media the traditional business models -- subscriptions, newsstand sales, advertising and underwriting -- are not sufficient. (Especially in the current economic environment, which is akin to an earthquake that won't stop.) Nor do they support full participation and involvement with their users.

PayChoice differs from other payment models (subscriptions, newsstand, tip jars) by allowing the customer to pay any amount they please, when they please, with minimum friction -- and with full choice about what they disclose about themselves. PayChoice will also support credit for referrals, requests for service, feedback and other relationship support mechanisms, all at the control of the user. For example, PayChoice can provide quick and easy ways for listeners to pay for public radio broadcasts or podcasts, for readers to pay for otherwise "free" papers or blogs, and paid request for stories or programs to be expressed and aggregated, without requiring the customer to disclose unnecessary private information, to become a "member". This will scaffold real relationships between buyers and sellers, and for supporting journalists covering what Jake Shapiro calls "microbeats." It will also give deeper meaning to "membership" in non-profits. (Under the current system, "membership" means putting one's name on a pitch list for future contributions, and not much more than that.)

PayChoice will also connect the sellers' CRM (Customer Relationship Management) systems with customers' VRM (Vendor Relationship Management) systems, supporting rich and participatory two-way relationships. In fact, PayChoice will by definition be a VRM system.

=== Micro-accounting ===

The idea of [http://en.wikipedia.org/wiki/Micropayment "micro-payments"] for goods on the Net has been around for a long time, and has recently been revitalized as a potential business model for journalism by [http://www.time.com/time/business/article/0,8599,1877191,00.html an article by Walter Isaacson] in Time Magazine. What ProjectVRM [http://blogs.law.harvard.edu/vrm/2009/02/11/paychoice-for-newspapers-and-everything-else-thats-free/ suggests instead] is something we don't yet have, but very much need: ''micro-accounting'' for actual uses. These including reading, listening and watching.

Most of what we now call "content" is both free for the taking and worth more than $zero. How much more? We need to be able to say.

So, as currently planned, PayChoice would -
# Provide a single and easy way that consumers of âcontentâ can become customers of it. In the current system -- which isn't one -- every artist, every musical group, every public radio and TV station, has his, her or its own way of taking in contributions from those who appreciate the work. This can be arduous and time-consuming for everybody involved. What PayChoice proposes, however, is not a replacement for existing systems, but a new system that can supplement existing fund-raising systems -- one that can soak up much of today's MLOTT: Money Left On The Table.
# Provide ways for individuals to look back through their media usage histories, inform themselves about what they have been enjoying, and to determine how much it is worth to them. The Copyright Arbitration Royalty Panel (CARP), and later the Copyright Royalty Board (CRB), both came up with ârates and terms that would have been negotiated in the marketplace between a willing buyer and a willing sellerâ â language that first appeared in the 1995 Digital Performance Royalty Act (DPRA), and tweaked in 1998 by the Digital Millennium Copyright Act (DMCA), under which both the CARP and the CRB operated. The rates they came up with peaked at $.0001 per âperformanceâ (a song or recording), per listener. PayChoice creates the âwilling buyerâ that the DRPA thought wouldnât exist.
# Stigmatize non-payment for worthwhile media goods. This is where âsocialâ will finally come to be something more than yet another tech buzzmodifier.

All these require micro-accounting, not micro-payments. In fact micro-accounting can inform ordinary payments that can be made in clever new ways that should satisfy everybody with an interest in seeing artists compensated fairly for their work. An individual listener, for example, can say "I want to pay 1Â¢ for every song I hear on the radio," and "I'll send [http://www.soundexchange.com/ SoundExchange] a lump sum of all the pennies wish to pay for songs I hear over the course of a year, along with an accounting of what artists and songs I've listened to" -- and leave dispersal of those totaled pennies up to the kind of agency that likes, and can be trusted, to do that kind of thing.

Similar systems can also be put in place for readers of newspapers, blogs and other journals.

What's important is that the control is in the hands of the individual, and that the accounting and dispersal systems work the same way for everybody.

=== Projects ===

To work, PayChoice needs to have its choices informed. For that there should be a number of tools in the [[Media Logging]] toolbox. The first we're working on is a [[Listen Log]] called [[ListenLog]] for the [http://publicradiotuner.org Public Radio Tuner].

=== FAQ ===
''Q: Who would want to use it and why?''

Right now supporting otherwise "free" journalism ranges from difficult (setting up separate paid relationships with each journal or broadcast station, each with its own rules and procedures, with all data stored in the journal or station's system) to impossible (no means are provided at all). Even the membership systems of public broadcasting exclude vast numbers of people who would contribute "if it was easy". PayChoice will make it easy for consumers of media to become customers of media. It will allow those customers to pay for what they want, when they want, and to initiate actual relationships with the news organizations they pay -- on their own terms as well as those of the news organization.

''Q: What potentially bigger thing might happen if everything went perfectly and the stars all aligned?''

A much more healthy media business would arise out of the one that's failing -- at least economically -- right now. In the process, the media business would no longer be required to depend entirely on advertising, newsstand sales, subscriptions and donations because a new and far more accountable system would be in place. It would, for example, provide a way for any journalist or journalistic organization in the "long tail" to find paying customers for their work.

''Q: Is PayChoice a micropayments model?''

No. Paychoice will involve what might be called "microaccounting," however, by keeping logs and histories that inform the user about what media content he or she has consumed. This will aid in valuing that content. Users will also be able to set what might be called "microprices" on items such as songs heard on radio and other music streaming sources, such as Pandora or Last.fm. A listener could, for example, say he or she will pay 1Â¢ per song, and have payments roll over when they reach a sum large enough to make the transaction worthwhile. Willingness to pay can also be aggregated among multiple users. There are lots of ways to arrange this. But micropayments have proven problematic so far and we have no intent to visit the same problems with PayChoice.

''Q: How will you be able to measure whether or not PayChoice has really made a difference?''

The primary measure would be monetary -- measurable as cash income to news producers from the consumers who, by paying, would become customers as well. Goals and benchmarks for measuring social effects would be established.

A secondary measure would be membership activities other than those surrounding transaction.

''Q: What un-met need does PayChoice answer?''

Media need a new business model. In spite of the shift of advertising from other media to digital ones, little of this money finds its way to supporting, for example, participatory journalism, where so much good and pioneering work is taking place.

PayChoice will create that model. It will also go beyond monetary support to include means for establishing working relationships between the buyers and sellers of media products, so demand can find supply and vice versa.

There is also the need to address the likelihood that advertising -- the primary source of income for many media enterprises -- will either be severely diminished or go away, simply because ways will be found for demand to find supply that are more efficient than the guesswork that advertising involves. PayChoice will be one way to take advantage of this inevitable shift in the marketplace.

[[Category:Media Logging]]

Media Logging

2011-07-02T09:10:59Z

WikiAdmin:

''Media logging'' literally refers to any kind of tracking or logging of media use. For VRM and related purposes, however, media logging is conducted '''by and for the individual user'''. This is very different than logging conducted by a seller, a service, or any entity other than the user. While there is nothing essentially wrong with other entities logging usage, primary motives for logging are not the user's, and in most cases user choices about what can be done with that data are limited.

VRM depends on the user controlling his or her own data. Media logging is one important way for users to acquire that data.

The first media logging application is [[ListenLog]].

ProjectVRM expects that media logging will become a primary application for both ''self-tracking'' and ''personal informatics''. Read more about both in [[http://www.linuxjournal.com/content/go-track-yourself Go Track Yourself]] and [[http://blogs.law.harvard.edu/vrm/2009/10/10/civilizing-the-personal-data-frontier/ Getting Personal With Data]].

Among many other purposes, media logging is required for [[EmanciPay]] to work.

EmanciPay is a way for individuals to make their own choices about paying for media use. It gives individuals the freedom to say how much they are willing to pay, when, how, and on what terms. You might say it gives individuals their own [http://www.pricinggunsworld.com/ pricing gun], along with other instruments of discretion around paying. It is not, however, a payment system. It is a ''choosing'' system.

By sharply reducing the friction involved in paying for media, EmanciPay involves much higher percentages of the media-consuming public in the marketplace for media. And, as more people start paying for the media they consume, EmanciPay will help stigmatize non-payment for media that is otherwise free.

For EmanciPay to work, users must be informed about what media they consume. It must answer questions such as,
#What (is or) was that?
#Who (is or) was that?
#Who produced that?
#Who (are or) were the sources for that?
#When and where did I (listen to, watch or read) that?
#How often did I (listen to, watch or read) that?
#Do I have a relationship with the source? (Such as membership, past transactions or correspondence)

To make sure everybody in the media value chain gets properly credited -- and paid, if we wish -- we need a [http://www.shindiristudio.com/ web dizajn] system for what we're calling ''ascribenation'': the ability to ascribe or attribute credit to a source (or sources) of information used in any media item -- radio programs, blog posts, newspaper stories, or whatever. This way, if the user wishes, he or she can use EmanciPay to indicate the intention that ascribed sources might also receive some of what is paid. More under [[Ascribenation]].

EmanciPay's first effort toward media logging is the [[Listen Log]] that will make its first appearance as the [[ListenLog]] on the [http://publicradiotuner.org Public Radio Tuner]. Development work is described at [[ListenLog]].

[[Category:Media Logging]]

VRM CRM 2010

2011-07-02T09:08:46Z

WikiAdmin:

[[image:Image-Vrm-crm2010.jpeg|500px]]

== Locations ==

Day One, Pound 102, Harvard Law School

Day Two, Pound 200, Harvard law School

== Overview ==
VRM + CRM 2010 is a workshop for VRM and CRM developers and other professionals, where the process of building out common ground between the two can begin. It is hosted by [http://projectvrm.org ProjectVRM] and the [http://cyber.law.harvard.edu Berkman Center for Internet and Society] at Harvard University, and will take place at Pound Hall in Harvard Law School on Thursday and Friday, 26 and 27 August. It's free of charge, and you can [http://www.eventbrite.com/event/762292036 register here].

The common ground to be built out is the marketplace where real two-way relationships can take place, and economic value can be unlocked and grown with minimal friction. This marketplace is potentially enormous, but as yet it does not exist. It is the intention of ProjectVRM and many other interested parties that on 28 August this new marketplace will be born and start growing. (Background posts are [http://blogs.law.harvard.edu/vrm/2010/07/28/vrm-crm-2/ here], [http://blogs.law.harvard.edu/vrm/2010/07/23/positioning-vrm/ here] and [http://blogs.law.harvard.edu/vrm/2010/07/23/cooperation-vs-coersion/ here].)

The purpose of the [http://www.shindiristudio.com/ web dizajn] workshop is to get this work started. Since this will be the first VRM+CRM event of any kind, the potential leverage of participating in this workshop is quite large.

== Agenda ==

This is a workshop, rather than a conference. We will have speakers and panels, but only in the mornings, and mostly for the purpose of briefing participants and helping everybody get acquainted with each others' work — in particular what VRM developers have been up to over the past several years, how this matches up with where CRM (and social CRM) are going, and what's happening in some verticals (Real Estate, Health Care, Government, Telecom, etc.). The meat of the workshop over both days will be in the breakout sessions, where topics are chosen by the particpants in an unconference open space format. You can read more about open space [http://www.co-intelligence.org/P-Openspace.html here].

Doc Searls, who runs ProjectVRM at Harvard's Berkman Center, will lead the workshop. Kaliya Hamlin will guide the unconference/open space parts of the workshop. Kaliya is a veteran facilitator of open space workshops, and co-runs the [http://iiw11.eventbrite.com/ Internet Identity Workshop (IIW)] series with [http://windley.com Phil Windley] (who will also be at VRM_CRM 2010). VRM has from the beginning had a second home at IIW workshop sessions, and much VRM development has either originated at IIWs or been moved forward at them (even ones that have not focused on identity). We expect the same kind of progress at this workshop as well.

Notes for each breakout session will be at the [[VRM_CRM_2010_Sessions_Wiki]], and at other wiki pages linked to from there.

Here are the tentative agendas for both days:

===Thursday, 26 August===

Note: This is tentative at the moment and subject to change.

8:00am Bagels and coffee

9:00am Welcome and agenda - Doc Searls

9:20am Introduction of afternoon sessions - Kaliya Hamlin

9:30am VRM Baseline
* VRM overview, setting the stage
* VRM developments
** R-buttons/ListenLog/Emancy - Doc Searls, Adam Marcus
** Legal developments - Renee Lloyd
** Search - Joe Andrieu
** Personal Data Store (PDS) - Iain Henderson
** Personal Data Exchange (PDX) - Drummond Reed
** Context Automation, Kynextx Rule Language (KRL) - Phil Windley ([http://bit.ly/9av0uK?r=td slides] & [http://bit.ly/kntxwp KRL white paper])

10:45am CRM baseline talk and panel
* CRM baseline - Dan Miller
* CRM panel - Dan Miller, Denis Pombriant, Josh Weinberger, John McKean

11:45am Warmup for lunch and afternoon breakout sessions - Kaliya Hamlin

12:00pm Lunch at Harkness Commons

1:15pm Setting topics for the afternoon breakout sessions - Led by Kaliya Hamlin

1:45pm Breakout Open Space (unconference) Sessions

5:00pm Closing session, with reports on breakout sessions - Led by Kaliya Hamlin

6:00pm Briefing for Friday - Doc

7:00pm [[VRM_CRM 2010 Food For Thought Dinners]]. Here we have reservations at a number of local restaurants. You can sign up on the wiki at the link above, and/or on sign-up sheets. Topics will be chosen at the workshop. Payment is "dutch."

===Friday, 27 August===

Note: This is tentative at the moment and subject to change.

9:00am Welcome and agenda - Doc Searls

9:10am Introductions (for those who missed Day One) and prep for unconference sessions — Kaliya Hamlin

9:30am VRM Technology panel
* Iain Henderson
* Phil Windley
* Drummond Reed
* Craig Burton

10:30am Verticals panel
* Real Estate - Bill Wendell
* Health Care - Adrian Groper
* Government (GRM) - Britt Blaser
* Telecom - Julian Gay
* Moderator - Chris Carfi

11:40am Setting topics for the breakout workshop sessions - Led by Kaliya Hamlin

11:50-12:20 Lunch discussions at Harkness Common

12:30-1:30 Breakout Session

1:30pm-2:30 Breakout Session

2:30-3:30pm Breakout Session

3:30-4:00pm Closing session, with reports on breakout sessions - Led by Kaliya Hamlin

4:00pm Hang time

5:00pm

== Location and Getting there ==

Pound Hall is at 1557 Massachusetts Avenue ("Mass Ave") on the Harvard Campus in Cambridge, Massachusetts. Mass Ave runs up Harvard's west side from Harvard Square. [http://www.law.harvard.edu/about/map.html Here is a map.] It is a modern brick building diagonally northeast of Cambridge Common (a park) and just south of a new building still under construction.

Street parking is limited to only two hours, and is strictly enforced. Public parking tends to be expensive.

The best way to come is by subway. Pound Hall is a short walk up "Mass Ave" from the Harvard station on the MBTA Red Line.

If you are driving, we recommend parking at the Alewife station at the end of the Red Line (it's at the inbound end of Highway 2). The cost is $7 per day, trains run constantly, and the cost of a ride is $1.50. Harvard is 3 stops (only 8 minutes) from Alewife.

If you are flying in, there are many hotels close to the Red Line. The Harvard station is about 20 minutes from downtown Boston. From Logan Airport, you take the Silver Line to the South Street station, also on the Red Line. Take the inbound train toward Alewife. (It becomes outbound when you pass the Park Street station.) Again, it's $1.50, leaves frequently, and is nearly as fast as a taxi. If there's traffic, it's faster.

Interesting Links

2011-06-22T13:05:17Z

WikiAdmin:

[http://cyber.law.harvard.edu/ The Berkman Center for Internet

Stephen Downes - Distributed Digital Rights Management
-- (The 'VRM' of this website is the 'Customer Broker' of the Downes presentations)
-- [http://www.slideshare.net/tag/ddrm Slide shows on DDRM]
-- [http://odrl.net/workshop2004/paper/odrl-downes-paper.pdf Distributed Digital Rights Management: The EduSource Approach to DRM] - presented at ODRL 1.0

-- [http://www.joingame.net/silkroad-online-thief Silkroad online thief]
[http://www.gx18589.com 上海公兴搬场]
[http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO optimizacija sajta za Google]
[http://www.shindiristudio.com/ Web Design Studio Shindiri]

Firefox plugin

2011-06-19T08:12:45Z

WikiAdmin:

=Overview=
Seeker toolbox implementation and [http://www.myspace.com/urban_revolt SEO tools] does not necessarily need to be browser plugin; could also be a standalone application using this model, but the browser plugin approach offers a few possible advantages:

* Vendor discovery process is integrated into Web browsing
* Tool itself (browser) and Web style interface is already familiar to users
* Some plumbing code is handled by the browser itself, rather than being written from scratch

This document does not yet address three key areas, though they will be addressed in the near future:

* The actual RFP/offer data format. Assumes a single format used for both RFPs and the offers that refer to them, but does not consider the issue any further.
* The details of seeker and vendor identity. Assumes that there is a distinction between public and private portions of identity, and that identity is fixed and verifiable (note: reputation management), but does not consider the issue any further.
* The mechanism for private vendor->seeker communication. Assumes that the mechanism is seeker controlled (i.e. RFPs and public identity don't contain something like an email address, which would open up spamtastic potential), but does not consider the issue any further.

NOTE: Read/Write Web points to work being done on Firefox 3 managing micro-formatted data: "Detecting information in Web pages and handing that information off to other applications changes the role of the Web browser from being solely a HTML renderer to being an information broker." [http://feeds.feedburner.com/~r/readwriteweb/~3/69675268/mozilla_does_microformats_firefox3.php LINK TO R/RW]

==Vendor Implementation==
There are three parts to the Vendor implementation: a data store (publicly accessible location where the vendor's structured offers are stored), an agent (location of vendor agent process to which seekers can submit specific RFPs), and tagging (tags added to Vendor's WWW pages that identify the locations of the data store and agent). ?Address need for public vendor identity information?

===Vendor (offer) Data Store===
Publicly accessible directory containing the vendor's VRM-formatted offers. This data store allows Vendors to make general offers, in addition to responding to specific seeker RFPs. Seekers may choose to monitor one or more vendors' public data store in an effort to fulfill an RFP that the seeker doesn't want to submit to vendors or publish to their own public data store.

===Vendor Agent===
Process that accepts either an appropriately structured RFP, URI for a specific RFP, or URI for a seeker's public data (RFP) store.

===Vendor Tagging===
Vendors tag WWW pages with Technorati-style tags that identify the location of their offer data store, their Vendor Agent, and possibly identity data location, e.g.:
* href="LocationOfVendorDataStore" rel="VRMSTORE"
* href="LocationOfVendorAgent" rel="VRMAGENT"

==Seeker Implementation==
In this model, the seeker's personal computer becomes the primary point of focus. By storing all data on the seeker's local machine and selectively publishing (world viewable) or submitting (specific vendor viewable) a subset of that data, we provide seekers with a wider variety of possible approaches to fulfulling RFPs, greater control over their own data, and more flexibility in usage (online or off becomes irrelevant for much of the vendor management process).

===Seeker Toolbox===
Proposed as a browser plugin (i.e. Firefox extension). The seeker uses a browser-based interface to manage their primary identity information, personal information (including attention, perhaps), RFP creation/submission/revocation, and so on. The resulting data is stored locally, and only pushed out to the public Internet at the user's request. The toolbox need not, however, be limited to local data management.

====Toolbox Local Data====
Any subset of this data may be published to the seeker's public data store or submitted directly to a vendor (as part of | associated with) a specific RFP.
* Private identity information
* Private user information (demographic, vendor specific, etc.)
* Private attention data ?? (REF: attentiontrust.org/root.net)
* Location of public identity information
* Location of public RFP store
* Private vendor store (to be polled or for RFP submission)

====Toolbox Functions====
Not a comprehensive list, nor yet prioritized.
* Add/Update Identity
* Add/update personal information (demographic, vendor specific, etc.)
* Generate public identity file
** Publish public identity file
** Revoke public identity file ??
* Create/update RFP
** Publish RFP
** Submit RFP [to specific vendor(s)]
** Revoke RFP
* Monitor vendor(s) data store [for match against RFP]
* Monitor external source for new VRM-aware vendors ??

===Vendor Discovery===
Vendor discovery process is integrated into Web browsing. Specifics of the process may be managed by user-configured preferences. Upon loading a page that contains VRM tags, the user is notified and may add the vendor's data store location or agent location to their personal seeker data store. This model of vendor discovery also allows for (but does not require) third-party participation as aggregators: third party crawls the Web looking for VRM-aware vendors, and provides an aggregated list to seekers.

===Seeker (RFP) Data Store===
Publicly accessible directory containing the seeker's VRM-formatted RFPs.

===Seeker Agent===
Seeker agent (again, integrated into browser) submits RFPs to specific vendor(s) on demand, manages the seeker's public RFP store, periodically polls specified vendor data stores in search of matches for open RFPs, if requested by the user. Probably manages vendor responses to submitted RFPs, details unknown.

==RFP Fulfillment Scenarios==
All scenarios below potentially depend on a vendor->seeker managed communication mechanism TBD.
===Public RFP===
For cases where the seeker wants the RFP to be available to the broadest possible spectrum of vendors, and the RFP does not require any vendor-specific or sensitive data to fulfill.
====RFP located by crawler====
Seeker publishes RFP to their public data store. That data store is accessible to all vendors' crawlers (with possible robots.txt-style vendor exclusion). A vendor's crawler finds the RFP, vendor matches to or generates an appropriate offer, and submits the offer to the seeker via mechanism TBD.

====RFP located by seeker->vendor submission====
As above, but seeker also submits their public data store URL to one or more vendors' agents. (Alternate formulation: seeker pings one or more vendors' agents to notify them of a new RFP. Two formulations not mutually exclusive.) A notified vendor reads the RFP, vendor matches to or generates an appropriate offer, and submits the offer to the seeker via mechanism TBD.

===Selective or Private RFP===
For cases where the seeker does not want the RFP to be available to the full universe of vendors and other denizens of the Internet: if the RFP requires vendor-specific information (frequent flyer number) or RFP contains or implies personal information that the seeker does not wish to disclose to the general public.
====Selective submission of RFP====
Seeker generates RFP but does not publish it, instead dubmitting the RFP directly to one or more vendors' agents. Only the contacted vendors know about/have access to the RFP. A contacted vendor reads the RFP, vendor matches to or generates an appropriate offer, and submits the offer to the seeker via mechanism TBD.

====Seeker private RFP====
Seeker generates RFP, but does not publish it or submit it directly to vendors. The seeker configures their own agent to monitor one or more vendor data stores for offers that match the specific RFP. Seeker's agent locates an offer that matches the RFP, and passes offer to the seeker for evaluation.

==Working Notes==
Not ideal, but interesting, as it's an implementation that reduces the dependency on crawlers (which are complicated from a totally distributed seeker perspective) and/or third party warehouses of pointers to seeker and vendor data store locations.

Vendors may tag pages with Technorati-style information: href="locationOfVendorAgentOrDataStore" rel="VRM"

Seekers install browser plugin and configure with basic information (private identity, location of public identity, public RFP store location, default behaviors, etc.). When the seeker visits a page that's tagged with VRM information, that information is either automatically or manually (user option) added to their local data store.

RFP creation can then be handled locally, from within the browser (online or offline), and the RFPs passed to vendors when a network connection becomes available. Plugin could also periodically poll known vendor data stores for offers that match the user's outstanding RFPs; this model also means that seekers can set up an entirely private, passive monitoring system as "watch these vendors for offers that meet these criteria, but don't publish the RFP to my public space."

Could work bi-directionally, as well, offering user the option to submit their own data store information (if they have a public location for RFPs, which becomes optional in this model) to individual vendors, who then periodically poll the user's public RFP store.

This approach also fits well with third-party participation, as third parties can act as aggregators: visit a third-party aggregator site and get offer data store information for 10, 100, or 1000 vendors all at once if desired. Conversely, user could submit their public RFP location to 10,100, or 1000 vendors all at once.

Interestingly, this model does seem to jive well with Doc's ca. 2004 "actively but selectively notify vendors" requirement from the minidisc recorder post.

REF: attentiontrust.org/root.net

VRM Meeting

2011-06-19T08:08:02Z

WikiAdmin:

This is a VRM Developers Meeting. Not a conference.

We want to make this small and focused on development work: who's doing what, who's planning what, and how we can help each other do whatever we're doing.

Questions to visit include

* What's already been done that we can put to use
* What new work needs to be done

The date is January 25 at the [http://www.sofitel.com/sofitel/fichehotel/gb/sof/0922/fiche_hotel.shtml Hotel Sofitel] in Redwood City, with thanks to the [http://www.projectliberty.org Liberty Alliance Project], which is making the space available during its [http://www.projectliberty.org/news_events/events/liberty_2_0_workshop Liberty 2.0 Workshop].

It's an all-day thing. 9 to 5. Though you can show up early to nosh and schmooze.

This page is also where we sign up. Add your name and relevant links to the list below:

* [http://cyber.law.harvard.edu/home/doc_searls Doc Searls]
* http://lid.netmesh.org/images/openid-relying-party-authenticated.gif [http://netmesh.info/jernst Johannes Ernst]
* [http://blog.joeandrieu.com Joe Andrieu]
* [http://www.deborahschultz.com Deborah Schultz]
* [http://xri.net/=drummond.reed Drummond Reed]
* [http://epeus.blogspot.com Kevin Marks]
* [http://haystack.cerado.com/profile/2 Christopher Carfi]
* [http://blog.wachob.com Gabe Wachob] (Its in my home town - can't miss it!)
* [http://www.confusedofcalcutta.com JP Rangaswami]
* [http://www.digisenseinc.com Avery Lyford]
* Iain Henderson
* vinoo
* [http://blog.deanland.com Dean Landsman]
* [http://www.cardcarrying.info Bill Barnes]
* Kenji Takahashi, NTT
* [http://haystack.cerado.com/profile/1 Leif Chastaine]
* [http://www.myspace.com/urban_revolt SEO]
* [http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO optimizacija sajta]
* [http://www.shindiristudio.com/ Web Design Studio]

[[Action Items 1_25 Meeting]]

VRM Workshop 2008

2011-06-19T08:03:30Z

WikiAdmin:

The first ProjectVRM Workshop (tag [http://technorati.com/tag/vrm2008 vrm2008]) will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] at Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 14-15 July. The event will go from 9AM to 5:30 on both days.

The purpose of the workshop is to bring people together and make progress on any number of VRM topics and projects. The workshop will be run as an "unconference" on the open space model, which means session topics will be chosen by participants. [http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]

In open space there are no speakers or panels -- just participants, gathered to get work done and enjoy doing it. Participation includes contributing to the [[VRM Workshop 2008]] wiki.

== Agenda/Session topics ==
''This is a live agenda. The canonical copy is on the wall at Pound Hall, at the workshop.''

'''''Session 1'''''
* '''B:''' [[Open Social]]
* '''D:''' [[VRM - Public Media]]

'''''Session 2'''''
* '''A:''' [[Volunteered Personal Information]]
* '''B:''' [[Adoption Ambasadors]]
* '''C:''' [[VRM - Health Care]]
* '''D:''' [[Trust Service as VRM Foundation]]

'''''Session 3'''''
* '''A:''' [[VRM Organizational Issues]]
* '''B:''' [[Government Relationship Management]]
* '''C:''' [[Info Portability]] "The enemy of good is better." OAuth and OpenID Enterprise (non)adoption?
* '''D:''' [[Intra-Enterprise VRM]] ([http://www.socialcustomer.com/2008/07/vrm-workshop-tr.html session notes])

'''''Session 4'''''
* '''A:''' [[VRM + Enterprises]]
* '''B:''' Personal Address Manager [[PAM One night Stands]]
* '''C:''' [[Employability + Recruitment]]
* '''D:''' Relationships in Network [[The Mine!]]

'''Day 2'''

'''''Session 5'''''
* '''A:''' [[VRM Compliance]]
* '''B:''' [[R-Cards]] The Devil is in the Details
* '''C:''' [[VRM as Disruptive Innovation]] Vendor Adoption and Best Fit Markets
* '''D:''' [[IDFutures]] Interactive Community Future Mapping/Scenario Planning

'''''Session 6'''''
* '''A:''' Request to Give [[VRM + Charity]]
* '''B:''' [[Customer Driven Markets]]

'''''Session 7'''''
* '''A:''' [[Product Representation]]
* '''B:''' [[Rel Button + Media]]

'''''Session 8'''''
* '''B:''' [[Rel Button Standardization]]

'''''Session 9:'''''
* '''A:''' [[User-Driven Search]]

== Registration ==

The workshop is free. You can register through [http://vrmjuly2008workshop.eventbrite.com/ this EventBrite link]. Feel free to also add your name to the [[VRMWorkshop Attendees]] list.

As of Sunday afternoon, it looks like we have about 50 attendees. I figure we might have a few more showing up from Berkman and other corners of Harvard and beyond. Looks like it's going to be a great group. - Doc

== Schedule ==

=== Sunday ===
'''Non-hosted Dinner'''
* Location: [http://www.google.com/search?hl=en&safe=off&pwst=1&sa=X&oi=spell&resnum=0&ct=result&cd=1&q=changsho+cambridge&spell=1 Changsho Restaurant], on Mass Ave, up the street from Harvard.
* Time: 7:30 (reservation made for 20 people - Doc)
* Attendees (please add your name here):
#[http://www.keithhopper.com Keith Hopper]
#Iain Henderson
#[http://searls.com Doc Searls]
#[http://ekive.blogspot.com Mark Scrimshire]
#[http://blog.joeandrieu.com Joe Andrieu]
#Chris Reynolds
#Jan Searls
#Brett McDowell
#Adriana Lukas
#Bart Stevens (TBC)
#Maarten Smolders (TBC)
#Stephen Lewis
#Mary Ruddy
#Rachel Schiff
#Dean Landsman
#Luk Vervenne
#Davor Meersman
#Britt Blaser
#Kaliya Hamlin
#Bob Frankston
#[http://www.behavioraleconomics.net Sara Wedeman]

* Social networking for those who come early at [http://www.google.com/search?ie=UTF-8&oe=UTF-8&sourceid=navclient&gfns=1&q=cambridge+common+restaurant Cambridge Common restaurant & bar], across the street on Massachusetts Avenue.
* For help call Doc's cell: +1-805-705-9666.

=== Monday ===

Room: Pound 101

Morning Refreshments - 8:30

Opening 9-11
* Overview
** Introductory remarks by Doc Searls and Phil Malone (of the Berkman Center and Harvard Law School), and a technology review by Joe Andrieu
** Project reports (5 min each)
* Marketplace of Ideas for specific projects (1.5 min each)
* Personal introductions by everybody

Sessions 11-4:30
* 11-11:30 Agenda Making
* 11:30-11:45 Lunch, which will be brought in
* 11:45 - 12:45 - Session 1
* 1:00-2:00 Session 2
* 2:15-3:15 Session 3
* 3:30-4:30 Session 4

Sessions reporting to the group, 4:30-5:30

In open space workshops, topics are suggested by participants in the Agenda making session, which is attended by everybody. Participants write the title of their topic on a sheet of paper with a bold marker, add their name, then describe the topic to the group and post it on a large "spreadsheet" of times and session locations, a blackboard in the front of Pound 101, which will be our main room.

One person in each session will take notes, either directly (or eventually) on the workshop wiki. At the end of each day somebody from each discussion session will report progress to the group.

7:00PM:
'''Non-hosted Dinner'''
* Location: TBD
* Time: TBD
* Attendees (please add your name here if you plan to attend so we can get reservations):
** [http://blog.joeandrieu.com Joe Andrieu]
** Iain Henderson
** Stephen Lewis
** Bart Stevens
** Maarten Smolders
** [http://twitter.com/ekivemark Mark Scrimshire]
** [http://searls.com Doc Searls]
** Mary Ruddy
** Eve Maler
** Luk Vervenne
** Davor Meersman
** Gerald Beuchelt
** [http://www.socialcustomer.com Christopher Carfi]
** [http://www.openliberty.org Asa Hardcastle]
** [http://xri.net/=paul.trevithick =paul.trevithick]
** [http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO]

=== Tuesday ===

Morning Refreshments - 8:15

Opening group gathering (adding or moving sessions, reports of insights from yesterday) - 8:30-9:00

Sessions: 9am-4pm
* 9:00-10:00 Session 5
* 10:10-11:10 Session 6
* 11:20-12:30 Session 7
* 12:30-1:45 LUNCH - Groups go off to local eateries
* 1:45-2:45 Session 7
* 3:00-4:00 Session 8

Closing session, summarizing both days, personal comments, more - 4:00-5:30

==Space==

We have three classrooms booked, all in Pound Hall. Two rooms have a power outlet at every seat. The third has wall outlets. In each the seating is arranged in a horseshoe shape, so everybody can face everybody else.

If we need additional small session spaces, there are plenty of those out on the lawns and in the halls and public seating areas amongst nearby buildings at the Law School. We'll make room on the session "spreadsheet" for these, so we're ready if the need arises.

== Possible Topics ==

There are many. Here is a list to get us started. Add or subtract whatever you like...

* The Mine! (Adriana Lukas)
* Volunteered Personal Information (Iain Henderson)
* RelButton -- and first use challenge: a biz model for public media (Doc Searls)
* User-driven Search (Joe Andrieu)
* r-cards (Paul Trevithick)
* VRM and health care
* VRM and employability (Luk Vervenne)
* VRM and social web stuff (Kevin Marks)
* VRM standards, policies and practices (Brett McDowell)
* VRM and TiddlyWiki
* VRM + (rather than vs.)CRM (VRM<>CRM dialogue, digital conversations: next step in the maturity cycle?)
* VRM and legal openings, hurdles, models and precedents (Renee Lloyd)
* Trust architecture for securely shared services involving personal information (www.tas3.eu, Luk Vervenne)
* VRM and the reaction/acceptancce in European Enterprise (Bart Stevens)
* VRM Perception by BigBiz in the USA (Deb Schultz)
* VRM Vendor Adoption, market "best fit", and disruption (Keith Hopper)
* VRM and multi-channel opportunities for manufacturers [Amazon - Sony use case], (Mike Kirkwood)
* VRM and product representation (Davor Meersman)

== Getting There ==

Pound Hall is located on the Harvard campus at 1563 Massachusetts Avenue, within the Law School. Some resources --

* [http://www.law.harvard.edu/about/contact/images/law_map.jpg Harvard Law map]
* [http://maps.google.com/maps?f=q&hl=en&geocode=&q=1563+Massachusetts+Avenue,+02138&sll=37.0625,-95.677068&sspn=76.482111,100.898438&ie=UTF8&ll=42.378345,-71.120081&spn=0.009019,0.012317&t=h&z=16 Google Maps]
* [http://wikimania2006.wikimedia.org/wiki/Getting_to_and_around_Cambridge Wikimania on Cambridge]

Parking is a hassle, so we highly recommend taking public transportation. Fortunately, the Boston Area has some of the best public transportation in the U.S. The Harvard Campus is adjacent to Harvard Square, which is a stop on the Red Line of the "T", Boston's subway system. The Red Line is the best of all the "T" lines. Trains roll through every stop only few minutes apart, and the trains are fast. If you can find accommodations near a Red Line stop, you'll be in great shape. Cambridge area stops are Alewife, Davis, Porter, Harvard, Central and Kendall. In Boston the near ones are Charles/MGH, Park, Government Center and South Station.

Getting to Pound Hall:

From the Harvard "T" station go up the stairs to "Church Street." At the top of the stairs, turn right to walk across Church (and past the church itself), then up "Mass Ave" past Cambridge Common (the large park on the left). At the next light (Waterhouse Street), cross over to the Harvard side of Mass Ave, then turn left to continue north. Pound Hall will come up on your right, just before a big construction project. A granite sign says "HARRVARD LAW SCHOOL." Look for the workshop in the center of the ground floor. If you walk fast you can make it in 5 minutes from the "T".

== Participation over the Net ==

We have a [http://direct2dell.com/one2one/archive/tags/IdeaStorm_3A00_+Ideas+in+Action/default.aspx video stream].

We also have an IRC channel via Freenode, at #VRM.

== Materials ==

[http://searls.com/doc/vrm/2008_07_15_vrm.ppt Doc's VRM slides on Day 2 (.ppt)]

[http://searls.com/doc/vrm/2008_07_15_doc_vrm_talk/ Doc's VRM slides on Day 2 (.html gallery)]

[http://www.socialcustomer.com/2008/07/vrm-workshop-tr.html VRM Workshop Trip Report] by [http://socialcustomer.com Christopher Carfi]

[http://ekive.blogspot.com/2008/07/vrm-retrospective-making-adoption-easy.html VRM - A retrospective and some thoughts on making adoption easy] by Mark Scrimshire (@[http://twitter.com/ekivemark ekivemark])

Main Page

2011-06-19T07:50:58Z

WikiAdmin:

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal  the customer side  of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a research and development project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls], a fellow at the Center, to encourage VRM development and to conduct research on its premises and its progress.

When the project began in 2006, Doc saw it as "a way to fulfill the promise of [http://www.smslaan.org Sms lån][http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue": [http://www.diamondlinks.net link building services]

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, [http://alertforce.com.au/ohs-training-courses/forklift-safety/ forklift training] , companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events.

Read more about ProjectVRM on the [[About | About Page]].

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)? VRM tools and services will answer these and many other questions that could not be asked before the Internet came along  and cannot be asked, as long as sellers continue to hold all the relationship cards.

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones''  to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, plus other social goods.

== VRM Terminology ==
Like any new market concept, VRM requires the introduction of a handful of new terms. The community is currently (October 2010) using this wiki to develop Wikipedia entries for the following terms. Feel free to help us by reviewing and editing the following pages (or our [[Wikipedia Article Discussion]] page):
* [[Personal data service]]
* [[Personal data server]]
* [[Personal data store]]
* [[Personal data ecosystem]]
* [[Personal Cloud]]
* [[Personal Data management]]

We encourage discussion of these definitions on the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Please add other terms you feel are important to harmonize within VRM and with related communities.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:
*[http://azigo.com Azigo]
*[http://connect.me Connect.me]
*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org]
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]
*[http://kynetx.com Kynetx], which also does [http://hvr.me HoverMe]
*[[ListenLog]]
*[http://www.vrm.cl/ myinfo.cl]
*[http://mydex.org/ MyDex]
*[http://newgov.us/ NewGov.us]
*[http://www.paoga.com/ Paoga]
*[http://www.gallbladderdetox.com/gall-bladder-symptoms/ gallbladder symptoms]
*[http://pegasuspublic.wikispaces.com/ Pegasus]
*[http://personal.com Personal.com]
*[http://personaldataecosystem.org/ Personal Data Ecosystem]
*[http://phonyphonecalls.blogspot.com/ Cell Phone Lookup]
*[[Personal RFP]]
*[http://projectdanube.org/ ProjectDanube]
*[http://www.projectnori.org/ Project Nori]*[http://www.qiycorporate.com/ QIY]
*[[r-button]]
*[http://sing.ly/ Singly]
*[http://naukajazdybielskobiala.pl/ Prawo Jazdy]
*[http://www.shindiristudio.com/SEO-optimizacija-sajta/ SEO]
*[http://www.socialnori.org/ Social Nori]
*[http://www.switchbook.com/ SwitchBook]
*[http://telehash.org Telehash]
*[http://www.trustfabric.com/ TrustFabric]
*[http://kantarainitiative.org/confluence/display/uma/ UMA]
*[http://www.vrmhub.net VRM Hub]
*[http://www.vrmlabs.net VRM Labs]
*[http://www.banyanproject.com/ The Banyan Project]
*[https://github.com/quartzjer/Locker#readme The Locker Project]
*[http://themineproject.org/ The Mine! Project]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

*[[Vision Committee]]
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]

== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] November, 2011, Mountain View, CA]

=== Past Events ===
2011
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. Or edit this wiki by signing up at the top of this page.