https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&user=DrummondReed&feedformat=atomProject VRM - User contributions [en]2024-03-28T20:19:12ZUser contributionsMediaWiki 1.39.5https://cyber.harvard.edu/projectvrm/?title=VRM_Development_Work&diff=5934VRM Development Work2013-07-29T16:49:10Z<p>DrummondReed: +Twitter handles for Connect.Me, Kynetx, Respect Network</p>
<hr />
<div>Here is a partial list of VRM development efforts. (See [[Main_Page#About_VRM | About VRM]]). Some are organizations, some are commercial entities, some are standing open source code development efforts.<br />
<br />
{| style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #ccc; padding: 2px" align="left" style="text-align:left;"<br />
|- style="color: white; background-color:#588F27; text-align: left;" <br />
| '''SOFTWARE and SERVICES'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Intentcasting'''<br />
|-<br />
| [http://askforit.com AskForIt] † - individual demand aggregation and advocacy<br />
|-<br />
| [https://bodyshopbids.com/ Body Shop Bids] † - intentcasting for auto body work bids based on uploaded photos<br />
|-<br />
| [http://havetohave.com Have to Have] † - "A single destination to store and share everything you want online"<br />
|-<br />
| [http://intently.co Intently] † - Intentcasting "shouts" for services<br />
|-<br />
| [http://www.nifti.com Nifti] † - Intentcasting "puts" in the market at customer (or community-) -chosen prices<br />
|-<br />
| [http://offersbyme.com/ OffersByMe] † - intentcasting for local offers<br />
|-<br />
| [http://prizzm.com/ Prizzm] †- social CRM platform rewarding customers for telling businesses what they want, what they like, and what they have problems with<br />
|-<br />
| [http://redbeacon.com/ RedBeacon] † - intentcasting locally for home services<br />
|-<br />
| [http://www.thumbtack.com/ Thumbtack] † - service for finding trustworthy local service providers<br />
|-<br />
| [http://trovi.co/ Trovi] intentcasting; matching searchers and vendors in Portland, OR and Chandler, AZ†<br />
|-<br />
| [http://ubokia.com/ Übokia] intentcasting†<br />
|-<br />
| [http://www.zaarly.com/ Zaarly] † intentcasting to community - local so far in SF and NYC<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Privacy protection'''<br />
|-<br />
| [http://abine.com Abine] † [http://abine.com/donottrackme Do Not Track Me], [http://abine.com/deleteme DeleteMe], [http://abine.com/maskme MaskMe] [http://www.abine.com/privacywatchdetail.php PrivacyWatch]: privacy-protecting browser extensions and services<br />
|-<br />
| [http://www.mozilla.org/en-US/collusion/ Collusion] Firefox add-on for viewing third parties tracking your movements<br />
|-<br />
| [http://disconnect.me/ Disconnect.me] † browser extentions to stop unwanted tracking, control data sharing<br />
|-<br />
| [http://ghostery.com/ Ghostery] † browser extension for tracking the trackers<br />
|-<br />
| [http://privacyscore.com/ PrivacyScore] † browser extensions and services to users and site builders for keeping track of trackers<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Databases'''<br />
|-<br />
| [http://infogrid.org/ InfoGrid] - graph database for personal networking applications<br />
|-<br />
| [http://projectdanube.org/ ProjectDanube] - open source software for identity and personal data services<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Messaging Services and Brokers'''<br />
|-<br />
| [https://gli.ph/ Gliph] †- private, secure identity management and messaging for smartphones<br />
|-<br />
| [http://www.directly.com/ Directly] † - customer service Q&A site connecting to people who have worked in big companies and are willing to help when the company can’t or won't<br />
|-<br />
| [http://www.getabl.com/ PingUp] (was Getabl) †- chat utility for customers to engage with merchants the instant customers are looking for something<br />
|-<br />
| [http://www.trustfabric.com/ TrustFabric] † - service for managing relationships with sellers<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Personal Data and Relationship Management'''<br />
|-<br />
| [http://www.azigo.com/ Azigo.com] † - personal data, personal agent<br />
|-<br />
| [http://www.complainapp.com/ ComplainApp] † - An iOS/Android app to "submit complaints to businesses instantly - and find people with similar complaints" <br />
|-<br />
| [http://connect.me/ Connect.Me] † - peer-to-peer reputation, personal agent [http://twitter.com/respectconnect @respectconnect] <br />
|-<br />
| [https://www.cozycloud.cc CozyCloud] † - personal cloud storage, service<br />
|-<br />
| [http://databanker.com/ DataBanker] - lets individual consumers aggregate and understand their personal behavioral data, and sell that data to product designers, marketers, and social researchers<br />
|-<br />
| [http://geddup.com/blog/about/ Geddup.com] † - personal data and relationship management<br />
|-<br />
| [http://higgins-project.org/ Higgins] - open source, personal data<br />
|-<br />
| [http://lockerproject.org/ The Locker Project] - open source, personal data<br />
|-<br />
| [http://mydex.org/ Mydex] †- personal data stores and other services<br />
|-<br />
| [https://mysocialcloud.com MySocialCloud] † - personal password management [http://www.reputation.com/reputationwatch/press-releases/reputationcom-acquires-online-platform-mysocialcloud Acquired by Reputation.com on 23 July 2013]<br />
|-<br />
| [http://www.onecub.com/ OneCub] †- Le compte unique pour vos inscriptions en ligne (single account for online registration)<br />
|-<br />
| [http://www.paoga.com/ Paoga] † - personal data, personal agent<br />
|-<br />
| [http://personal.com/ Personal.com] † - personal data storage, personal agent<br />
|-<br />
| [http://personal-clouds.org/ Personal Clouds] - personal cloud wiki<br />
|-<br />
| [http://www.privowny.com/ Privowny] † - privacy company for protecting personal identities and for tracking use and abuse of those identities, building relationships<br />
|-<br />
| [http://www.qiycorporate.com/ QIY] † - independent infrastructure for managing personal data and relationships<br />
|-<br />
| [http://singly.com/ Singly] † - personal data storage and platform for development, with an API<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Transaction Management'''<br />
|-<br />
| [https://www.dashlane.com/ Dashlane] † - simplified login and checkout<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Trust-Based or -Providing Systems and Services'''<br />
|-<br />
| [http://idcubed.org/ id3] - trust frameworks<br />
|-<br />
| [http://respectnetwork.com/ Respect Network] † - VRM personal cloud network based on OAuth, XDI, KRL, unhosted, and other open standards, open source, and open data initiatives. Respect Network is the parent of [http://connect.me/ Connect.Me]. [http://twitter.com/respectnet @respectnet] [http://twitter.com/respectconnect @respectconnect] [http://twitter.com/drummondreed @drummondreed] <br />
|-<br />
| [http://trust.cc Trust.cc] Personal social graph based fraud prevention, affiliated with Social Islands<br />
|-<br />
| [https://trustcloud.com/ TrustCloud]<br />
|-<br />
| <br />
|- style="background-color:#F7E967; text-align: left;" <br />
| '''SERVICE PROVIDERS OR PROJECTS BUILT ON VRM PRINCIPLES'''<br />
|-<br />
| [http://belmewel-register.nl/ belmewel-register.nl — the "Dutch YouMayCallMe registry"] † "reverses the customer paradigm"<br />
|-<br />
| [https://cldstr.com/ Cloudstore] † personal clouds<br />
|-<br />
| [http://datacoup.com Datacoup] † a marketplace that translates personal data into a form of currency used for exchange on goods, offers or both<br />
|-<br />
| [http://dot.UI/ dotui.com] † intelligent media solutions for retail and hospitality customers<br />
|-<br />
| [https://web.easydns.com/ easyDNS] † Customer driven managed DNS hosting, domain tools and registration with no lock-in<br />
|-<br />
| [http://edentiti.com/ Edentiti] Customer driven verification of idenity<br />
|-<br />
| [http://firstretail.com First Retail Inc.] † commodity infrastructure for bi-directional marketplaces to enable the Personal RFP<br />
|-<br />
| [http://realestatecafe.com Real Estate Cafe] † money-saving services for DIY homebuyers & FSBOs <br />
|-<br />
| [http://hover.com/ Hover.com] Customer-driven domain management†<br />
|-<br />
| [http://hypothes.is/ Hypothes.is] - open source, peer review<br />
|-<br />
| [http://myinfo.cl/ MyInfo.cl] (Transitioning from VRM.cl) †<br />
|-<br />
| [http://neustar.biz/ Neustar] "Cooperation through trusted connections" †<br />
|-<br />
| [http://newgov.us/ NewGov.us] - GRM<br />
|-<br />
| [https://ownyourinfo.com OwnYourInfo] Personal information storing and sharing application †<br />
|-<br />
| [http://reputation.com Reputation.com] † - Service for controlling one's reputation online<br />
|-<br />
| [http://www.spotflux.com/ Spotflux] † malware, tracking, unwanted ad filtration through an encrypted tunnel<br />
|-<br />
| [http://www.switchbook.com/ SwitchBook] † - personal search<br />
|-<br />
| [http://www.tangledp2p.com/ Tangled Web] † - mobile, P2P & PDS<br />
|-<br />
| [http://www.banyanproject.com/ The Banyan Project]- community news co-ops owned by reader/members<br />
|-<br />
| [http://www.tiddlywiki.com/ TiddlyWiki] - a reusable non-linear personal Web notebook<br />
|-<br />
| [http://ting.com/ Ting] † - customer-driven mobile virtual network operator (MVNO - a cell phone company)<br />
|-<br />
| [http://tucows.com/ Tucows] † Parent of Ting and Hover<br />
|-<br />
| [http://www.virtualzero.it/ VirtualZero] - Open food platform, supply chain transparency<br />
|-<br />
| [http://myvu.com/ Vū] † User-driven personalized content delivery<br />
| <br />
|- style="background-color:#CAFCD8; text-align: left;" <br />
| '''INFRASTRUCTURE'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Concepts'''<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/EmanciPay EmanciPay] - dev project for customer-driven payment choices<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/GRM:_Government_Relationship_Management GRM: Government Relationship Management] - subcategory of VRM<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog] - personal data logging<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/Personal_RFP Personal RFP] - crowdsourcing, standards<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/R-button R-button] - UI elements for relationship members<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Hardware'''<br />
|-<br />
| [http://freedomboxfoundation.org/ Freedom Box] - personal server on free software and hardware<br />
|-<br />
| [http://precipit.at/ Precipitat, WebBox] - new architecture for decentralizing the Web, little server<br />
|-<br />
| [http://www.scanadu.com Scanadu] † - A scanner packed with sensors designed to read your vital signs and send them wirelessly to your smartphone<br />
|-<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Standards, Frameworks, Code bases and Protocols'''<br />
|-<br />
| [http://cliquespace.net CliqueSpace] A system that models user and device interactions. See [http://ssrn.com/abstract=1714848 this SSRN paper].<br />
|-<br />
| [http://datownia.com/ Datownia] † - builds APIs from Excel spreadsheets held in Dropbox<br />
|-<br />
| [http://innotribe.com/2012/10/31/discover-digital-asset-grid-2/ Digital Asset Grid] S prototype for secure and accountable Intentcasting infrastructure, funded by SWIFT [http://innotribe.com Innotribe].<br />
|-<br />
| [http://www.eventedapi.org/ Evented APIs] - new standard for live web interactivity<br />
|-<br />
| [https://github.com/kynetx/krl KRL (Kinetic Rules Language)] - personal event networks, personal rulesets, programming Live Web interactions [http://twitter.com/windley @windley] <br />
|-<br />
| [http://kynetx.com/ Kynetx] † - personal event networks, personal rulesets [http://twitter.com/windley @windley] <br />
|-<br />
| [https://github.com/CSEMike/OneSwarm Oneswarm] - privacy protecting peer-to-peer data sharing<br />
|-<br />
|- [http://infogrid.org/ InfoGrid] RESTful Web Graph database<br />
|-<br />
| http://www.mozilla.org/en-US/persona/ Mozila Persona] - a privacy-protecting one-click email-based way to do single sign on at websites<br />
|-<br />
| [http://tas3.eu/ TAS3.eu — Trusted Architecture for Securely Shared Services] - R&D toward a trusted architecture and set of adaptive security services for individuals<br />
|-<br />
| [http://telehash.org/ Telehash] - standards, personal data protocols<br />
|-<br />
| [http://tent.io/ Tent] - open decentralized protocol for personal autonomy and social networking<br />
|-<br />
| [http://themineproject.org/ The Mine! Project] - personal data, personal agent<br />
|-<br />
| [http://kantarainitiative.org/confluence/display/uma/ UMA] - standards<br />
|-<br />
| [http://code.google.com/p/webfinger/ webfinger] - personal Web discovery, finger over HTTP<br />
|-<br />
| [http://www.oasis-open.org/committees/xdi/ XDI] - OASIS semantic data interchange standard<br />
|-<br />
| <br />
|- style="background-color:#A9CF54; text-align: left;" <br />
| '''PEOPLE'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Analysts and Consultants'''<br />
|-<br />
| [http://ctrl-shift.co.uk/ Ctrl-SHIFT] † - analysts<br />
|-<br />
| [http://synergetics.be/ Synergetics] † - VRM for job markets<br />
|-<br />
| [http://www.vrmlabs.net/ VRM Labs] - Research<br />
|-<br />
| [http://healthurl.com/ HealthURL] - Medical<br />
| <br />
|- style="background-color:#D8BFD8; text-align: left;" <br />
| '''CONSORTIA, WORKGROUPS'''<br />
|- style="background-color:#f0f0f0 text-align: left;" <br />
|-<br />
| [http://fing.org/ Fing.org] - VRM fostering organization<br />
|-<br />
| [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara] - legal agreements, trust frameworks<br />
|-<br />
| [http://pegasuspublic.wikispaces.com/ Pegasus] - eID smart cards<br />
|-<br />
| [http://personaldataecosystem.org/ Personal Data Ecosystem Consortium] (PDEC) - industry collaborative<br />
|<br />
|- style="background-color:#8FBC8F; text-align: left;" <br />
| '''MEETUPS, CONFERENCES AND EVENTS'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
|-<br />
| [http://www.internetidentityworkshop.com/ IIW: Internet Identity Workshop] - yearly unconference in Mountain View<br />
|-<br />
| [http://www.vrmhub.net/ VRM Hub] - meeting in London<br />
<br />
NOTES:<br /><br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with companies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.) <br /><br />
A - creating standard<br /><br />
B - Using other standards<br /><br />
1 - EventedAPI<br /></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_Development_Work&diff=5891VRM Development Work2013-02-05T00:13:32Z<p>DrummondReed: updated listing for Respect Network</p>
<hr />
<div>Here is a partial list of VRM development efforts. (See [[Main_Page#About_VRM | About VRM]]). Some are organizations, some are commercial entities, some are standing open source code development efforts.<br />
<br />
{| style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #ccc; padding: 2px" align="left" style="text-align:left;"<br />
|- style="color: white; background-color:#588F27; text-align: left;" <br />
| '''SOFTWARE and SERVICES'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Intentcasting'''<br />
|-<br />
| [http://askforit.com AskForIt] † - individual demand aggregation and advocacy<br />
|-<br />
| [https://bodyshopbids.com/ Body Shop Bids] † - intentcasting for auto body work bids based on uploaded photos<br />
|-<br />
| [http://havetohave.com Have to Have] † - "A single destination to store and share everything you want online"<br />
|-<br />
| [http://intently.co Intently] † - Intentcasting "shouts" for services, in the U.K.<br />
|-<br />
| [http://innotribe.com Innotribe] Funding the [http://innotribe.com/2012/10/31/discover-digital-asset-grid-2/ Digital Asset Grid] prototype, for secure and accountable Intentcasting infrastructure<br />
|-<br />
| [http://offersbyme.com/ OffersByMe] † - intentcasting for local offers<br />
|-<br />
| [http://prizzm.com/ Prizzm] †- social CRM platform rewarding customers for telling businesses what they want, what they like, and what they have problems with<br />
|-<br />
| [http://redbeacon.com/ RedBeacon] † - intentcasting locally for home services<br />
|-<br />
| [http://www.thumbtack.com/ Thumbtack] † - service for finding trustworthy local service providers<br />
|-<br />
| [http://trovi.co/ Trovi] intentcasting; matching searchers and vendors in Portland, OR and Chandler, AZ†<br />
|-<br />
| [http://ubokia.com/ Übokia] intentcasting†<br />
|-<br />
| [http://www.zaarly.com/ Zaarly] † intentcasting to community - local so far in SF and NYC<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Browser Extensions'''<br />
|-<br />
| [http://abine.com Abine] † DNT+, deleteme, PrivacyWatch: privacy-protecting browser extentions<br />
|-<br />
| [http://www.mozilla.org/en-US/collusion/ Collusion] Firefox add-on for viewing third parties tracking your movements<br />
|-<br />
| [http://disconnect.me/ Disconnect.me] † browser extentions to stop unwanted tracking, control data sharing<br />
|-<br />
| [http://ghostery.com/ Ghostery] † browser extension for tracking the trackers<br />
|-<br />
| [http://privacyscore.com/ PrivacyScore] † browser extensions and services to users and site builders for keeping track of trackers<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Databases'''<br />
|-<br />
| [http://infogrid.org/ InfoGrid] - graph database for personal networking applications<br />
|-<br />
| [http://projectdanube.org/ ProjectDanube] - open source software for identity and personal data services<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Messaging Services and Brokers'''<br />
|-<br />
| [https://gli.ph/ Gliph] †- private, secure identity management and messaging for smartphones<br />
|-<br />
| [http://www.insidr.com/ Insidr] † - customer service Q&A site connecting to people who have worked in big companies and are willing to help when the company can’t or won't<br />
|-<br />
| [http://www.getabl.com/ PingUp] (was Getabl) †- chat utility for customers to engage with merchants the instant customers are looking for something<br />
|-<br />
| [http://www.trustfabric.com/ TrustFabric] † - service for managing relationships with sellers<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Personal Data and Relationship Management'''<br />
|-<br />
| [http://www.azigo.com/ Azigo.com] † - personal data, personal agent<br />
|-<br />
| [http://www.complainapp.com/ ComplainApp] † - An iOS/Android app to "submit complaints to businesses instantly - and find people with similar complaints" <br />
|-<br />
| [http://connect.me/ Connect.Me] † - peer-to-peer reputation, personal agent<br />
|-<br />
| [http://geddup.com/blog/about/ Geddup.com] † - personal data and relationship management<br />
|-<br />
| [http://higgins-project.org/ Higgins] - open source, personal data<br />
|-<br />
| [http://lockerproject.org/ The Locker Project] - open source, personal data<br />
|-<br />
| [http://mydex.org/ Mydex] †- personal data stores and other services<br />
|-<br />
| [http://www.onecub.com/ OneCub] †- Le compte unique pour vos inscriptions en ligne (single account for online registration)<br />
|-<br />
| [http://www.paoga.com/ Paoga] † - personal data, personal agent<br />
|-<br />
| [http://personal.com/ Personal.com] † - personal data storage, personal agent<br />
|-<br />
| [http://personal-clouds.org/ Personal Clouds] - personal cloud wiki<br />
|-<br />
| [http://www.privowny.com/ Privowny] † - privacy company for protecting personal identities and for tracking use and abuse of those identities, building relationships<br />
|-<br />
| [http://www.qiycorporate.com/ QIY] † - independent infrastructure for managing personal data and relationships<br />
|-<br />
| [http://singly.com/ Singly] † - personal data storage and platform for development, with an API<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Transaction Management'''<br />
|-<br />
| [https://www.dashlane.com/ Dashlane] † - simplified login and checkout<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Trust-Based or -Providing Systems and Services'''<br />
|-<br />
| [http://idcubed.org/ id3] - trust frameworks<br />
|-<br />
| [http://respectnetwork.com/ Respect Network] † - VRM personal cloud network based on OAuth, XDI, KRL, unhosted, and other open standards, open source, and open data initiatives. Respect Network is the parent of [http://connect.me/ Connect.Me].<br />
|-<br />
| [http://trust.cc Trust.cc] Personal social graph based fraud prevention, affiliated with Social Islands<br />
|-<br />
| <br />
|- style="background-color:#F7E967; text-align: left;" <br />
| '''SERVICE PROVIDERS OR PROJECTS BUILT ON VRM PRINCIPLES'''<br />
|-<br />
| [http://firstretail.com First Retail Inc.] † commodity infrastructure for bi-directional marketplaces to enable the Personal RFP<br />
|-<br />
| [http://dot.UI/ dotui.com] † intelligent media solutions for retail and hospitality customers<br />
|-<br />
| [http://edentiti.com/ Edentiti] Customer driven verification of idenity<br />
|-<br />
| [http://realestatecafe.com Real Estate Cafe] † money-saving services for DIY homebuyers & FSBOs <br />
|-<br />
| [http://hover.com/ Hover.com] Customer-driven domain management†<br />
|-<br />
| [http://hypothes.is/ Hypothes.is] - open source, peer review<br />
|-<br />
| [http://myinfo.cl/ MyInfo.cl] (Transitioning from VRM.cl) †<br />
|-<br />
| [http://neustar.biz/ Neustar] "Cooperation through trusted connections" †<br />
|-<br />
| [http://newgov.us/ NewGov.us] - GRM<br />
|-<br />
| [http://reputation.com] † - Service for controlling one's reputation online<br />
|-<br />
| [http://www.spotflux.com/ Spotflux] † malware, tracking, unwanted ad filtration through an encrypted tunnel<br />
|-<br />
| [http://www.switchbook.com/ SwitchBook] † - personal search<br />
|-<br />
| [http://www.tangledp2p.com/ Tangled Web] † - mobile, P2P & PDS<br />
|-<br />
| [http://www.banyanproject.com/ The Banyan Project]- community news co-ops owned by reader/members<br />
|-<br />
| [http://www.tiddlywiki.com/ TiddlyWiki] - a reusable non-linear personal Web notebook<br />
|-<br />
| [http://ting.com/ Ting] † - customer-driven mobile virtual network operator (MVNO - a cell phone company)<br />
|-<br />
| [http://tucows.com/ Tucows] †<br />
|-<br />
| [http://www.virtualzero.it/ VirtualZero] - Open food platform, supply chain transparency<br />
|-<br />
| <br />
|- style="background-color:#CAFCD8; text-align: left;" <br />
| '''INFRASTRUCTURE'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Concepts'''<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/EmanciPay EmanciPay] - dev project for customer-driven payment choices<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/GRM:_Government_Relationship_Management GRM: Government Relationship Management] - subcategory of VRM<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog] - personal data logging<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/Personal_RFP Personal RFP] - crowdsourcing, standards<br />
|-<br />
| [http://cyber.law.harvard.edu/projectvrm/R-button R-button] - UI elements for relationship members<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Hardware'''<br />
|-<br />
| [http://freedomboxfoundation.org/ Freedom Box] - personal server on free software and hardware<br />
|-<br />
| [http://precipit.at/ Precipitat, WebBox] - new architecture for decentralizing the Web, little server<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Standards, Frameworks, Code bases and Protocols'''<br />
|-<br />
| [http://datownia.com/ Datownia] † - builds APIs from Excel spreadsheets held in Dropbox<br />
|-<br />
| [http://www.eventedapi.org/ Evented APIs] - new standard for live web interactivity<br />
|-<br />
| [https://github.com/kynetx/krl KRL (Kinetic Rules Language)] - personal event networks, personal rulesets, programming Live Web interactions<br />
|-<br />
| [http://kynetx.com/ Kynetx] † - personal event networks, personal rulesets<br />
|-<br />
| https://github.com/CSEMike/OneSwarm Oneswarm] - privacy protecting peer-to-peer data sharing<br />
|-<br />
| http://www.mozilla.org/en-US/persona/ Mozila Persona] - a privacy-protecting one-click email-based way to do single sign on at websites<br />
|-<br />
| [http://tas3.eu/ TAS3.eu — Trusted Architecture for Securely Shared Services] - R&D toward a trusted architecture and set of adaptive security services for individuals<br />
|-<br />
| [http://telehash.org/ Telehash] - standards, personal data protocols<br />
|-<br />
| [http://tent.io/ Tent] - open decentralized protocol for personal autonomy and social networking<br />
|-<br />
| [http://themineproject.org/ The Mine! Project] - personal data, personal agent<br />
|-<br />
| [http://kantarainitiative.org/confluence/display/uma/ UMA] - standards<br />
|-<br />
| [http://code.google.com/p/webfinger/ webfinger] - personal Web discovery, finger over HTTP<br />
|-<br />
| [http://www.oasis-open.org/committees/xdi/ XDI] - OASIS semantic data interchange standard<br />
|-<br />
| <br />
|- style="background-color:#A9CF54; text-align: left;" <br />
| '''PEOPLE'''<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Analysts and Consultants'''<br />
|-<br />
| [http://ctrl-shift.co.uk/ Ctrl-SHIFT] † - analysts<br />
|-<br />
| [http://synergetics.be/ Synergetics] † - VRM for job markets<br />
|-<br />
| [http://www.vrmlabs.net/ VRM Labs] - Research<br />
|-<br />
| [http://healthurl.com/ HealthURL] - Medical<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Consortia, Workgroups'''<br />
|-<br />
| [http://fing.org/ Fing.org] - VRM fostering organization<br />
|-<br />
| [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara] - legal agreements, trust frameworks<br />
|-<br />
| [http://pegasuspublic.wikispaces.com/ Pegasus] - eID smart cards<br />
|-<br />
| [http://personaldataecosystem.org/ Personal Data Ecosystem Consortium] (PDEC) - industry collaborative<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Meetups, Conferences, and Events'''<br />
|-<br />
| [http://www.internetidentityworkshop.com/ IIW: Internet Identity Workshop] - yearly unconference in Mountain View<br />
|-<br />
| [http://www.vrmhub.net/ VRM Hub] - meeting in London<br />
<br />
NOTES:<br /><br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with companies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.) <br /><br />
A - creating standard<br /><br />
B - Using other standards<br /><br />
1 - EventedAPI<br /></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_Development_Work&diff=5839VRM Development Work2012-05-26T21:22:37Z<p>DrummondReed: Added XDI and Respect Network</p>
<hr />
<div>Here is a partial list of VRM development efforts, most or all of which move in the direction of Life Management Platforms (see [[Main_Page#About_VRM | About VRM]]). Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
<br />
{| style="border-collapse: separate; border-spacing: 0; border-width: 1px; border-style: solid; border-color: #ccc; padding: 2px" align="center" style="text-align:center;"<br />
| align="left" style="background:#f0f0f0; padding: 4px;"|'''Project Description'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Dev project'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''FOSS'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''PDS'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Standard(s)'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Fourth Party'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Communications'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Service'''<br />
| align="center" style="background:#f0f0f0; padding: 4px;"|'''Open API'''<br />
|- style="background-color:#FEAE4F; text-align: left;" <br />
| '''INFRASTRUCTURE'''||||||||||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Concepts'''||||||||||||||||<br />
|-<br />
|align="left"| [http://cyber.law.harvard.edu/projectvrm/EmanciPay EmanciPay] - dev project for customer-driven payment choices<br />
|<!-- DEV Project -->&#10003;<br />
|<!-- FOSS -->&#10003;<br />
|<!-- PDS --><br />
|<!-- Standard(s) -->&#10003;<br />
|<!-- Fourth Party --><br />
|<!-- Communications --><br />
|<!-- Service --><br />
|<!-- Open API -->&#10003;<br />
|-<br />
|align="left"| [http://cyber.law.harvard.edu/projectvrm/GRM:_Government_Relationship_Management GRM: Government Relationship Management] - subcategory of VRM||✓||||||||||||✓||<br />
|-<br />
|align="left"| [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog] - personal data logging||✓||✓||✓||||||||||<br />
|-<br />
|align="left"| [http://cyber.law.harvard.edu/projectvrm/Personal_RFP Personal RFP] - crowdsourcing, standards||✓||||||✓||||||✓||<br />
|-<br />
|align="left"| [http://cyber.law.harvard.edu/projectvrm/R-button R-button] - UI elements for relationship members||✓||||||✓||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Hardware'''||||||||||||||||<br />
|-<br />
|align="left"| [http://freedomboxfoundation.org/ Freedom Box] personal server on free software and hardware||✓||✓||||||||✓||||<br />
|-<br />
|align="left"| [http://precipit.at/ Precipitat, WebBox] - new architecture for decentralizing the Web, little server||✓||||||||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Standards, Frameworks, and Protocols'''||||||||||||||||<br />
|-<br />
|align="left"| [http://www.eventedapi.org/ Evented APIs] - new standard for live web interactivity||✓||✓||||✓ AB||||||||✓<br />
|-<br />
|align="left"| [https://github.com/kynetx/krl KRL (Kinetic Rules Language)] - personal event networks, personal rulesets, programming Live Web interactions||✓||✓||||||||||||<br />
|-<br />
|align="left"| [http://kynetx.com/ Kynetx] † - personal event networks, personal rulesets||✓||✓||||✓||||✓||✓||✓<br />
|-<br />
|align="left"| [http://tas3.eu/ TAS3.eu — Trusted Architecture for Securely Shared Services] - R&D toward a trusted architecture and set of adaptive security services for individuals||✓||✓||||✓||||||||<br />
|-<br />
|align="left"| [http://telehash.org/ Telehash] - standards, personal data protocols||✓||||||✓||||||||<br />
|-<br />
|align="left"| [http://themineproject.org/ The Mine! Project] - personal data, personal agent||✓||||✓||||||||||<br />
|-<br />
|align="left"| [http://kantarainitiative.org/confluence/display/uma/ UMA] - standards||✓||✓||||✓||||✓||||<br />
|-<br />
|align="left"| [http://code.google.com/p/webfinger/ webfinger] - personal Web discovery, finger over HTTP||✓||✓||||✓||||✓||||<br />
|-<br />
|align="left"| [http://www.oasis-open.org/committees/xdi/ XDI] - OASIS semantic data interchange standard||✓||✓||||✓||||✓||✓||✓<br />
|-<br />
| ||||||||||||||||<br />
|- style="background-color:#4FC3FE; text-align: left;" <br />
| '''PEOPLE'''||||||||||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Analysts and Consultants'''||||||||||||||||<br />
|-<br />
|align="left"| [http://ctrl-shift.co.uk/ Ctrl-SHIFT] † - analysts||||||||||||||✓||<br />
|-<br />
|align="left"| [http://synergetics.be/ Synergetics] † - VRM for job markets||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.vrmlabs.net/ VRM Labs] Research||✓||||||||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Consortia, Workgroups'''||||||||||||||||<br />
|-<br />
|align="left"| [http://fing.org/ Fing.org] - VRM fostering organization||✓||||||||||||||<br />
|-<br />
|align="left"| [http://idcubed.org/ id3] - trust frameworks||✓||✓||✓|| B||||||✓||✓<br />
|-<br />
|align="left"| [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara] - legal agreements, trust frameworks||✓||||||||||||||<br />
|-<br />
|align="left"| [http://pegasuspublic.wikispaces.com/ Pegasus] eID smart cards||✓||||||||||||||<br />
|-<br />
|align="left"| [http://personaldataecosystem.org/ Personal Data Ecosystem Consortium] (PDEC) - industry collaborative||✓||✓||✓||✓||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Meetups, Conferences, and Events'''||||||||||||||||<br />
|-<br />
|align="left"| [http://www.vrmhub.net/ VRM Hub] Group meeting in London||✓||||||||||||||<br />
|-<br />
| ||||||||||||||||<br />
|- style="background-color:#FEFB4F; text-align: left;" <br />
| '''SERVICE PROVIDERS OR PROJECTS BUILT ON VRM PRINCIPLES'''||||||||||||||||<br />
|-<br />
|align="left"| [http://dot.UI/ dotui.com] † intelligent media solutions for retail and hospitality customers||✓||||||||||||✓||<br />
|-<br />
|align="left"| [http://hover.com/ Hover.com] Customer-driven domain management†||||||||||||||✓||<br />
|-<br />
|align="left"| [http://hypothes.is/ Hypothes.is] - open source, peer review||✓||✓||||||||||||<br />
|-<br />
|align="left"| [http://myinfo.cl/ MyInfo.cl] (Transitioning from VRM.cl †||✓||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://newgov.us/ NewGov.us] - GRM||✓||||||||||||✓||✓<br />
|-<br />
|align="left"| [http://www.spotflux.com/ Spotflux] † malware, tracking, unwanted ad filtration through an encrypted tunnel||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.switchbook.com/ SwitchBook] † - personal search||✓||||||||||||||<br />
|-<br />
|align="left"| [http://www.tangledp2p.com/ Tangled Web] † - mobile, P2P & PDS||||||✓||||||✓||✓||<br />
|-<br />
|align="left"| [http://www.banyanproject.com/ The Banyan Project]- community news co-ops owned by reader/members||✓||✓||||||||||✓||<br />
|-<br />
|align="left"| [http://www.thimbl.net/ Thimbl] †||||||||||||||✓||<br />
|-<br />
|align="left"| [http://www.tiddlywiki.com/ TiddlyWiki] - a reusable non-linear personal Web notebook||✓||✓||✓||||||||||<br />
|-<br />
|align="left"| [http://ting.com/ Ting] † - customer-driven mobile virtual network operator (MVNO - a cell phone company)||||||||||||✓||✓||<br />
|-<br />
|align="left"| [http://tucows.com/ Tucows] †||||||||||||✓||✓||<br />
|-<br />
|align="left"| [http://www.virtualzero.it/ VirtualZero] - Open food platform, supply chain transparency||✓||||||||||✓||✓||<br />
|-<br />
| ||||||||||||||||<br />
|- style="color: white; background-color:#944FFE; text-align: left;" <br />
| '''SOFTWARE and SERVICES'''||||||||||||||||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Browser Extensions'''||||||||||||||||<br />
|-<br />
|align="left"| [http://disconnect.me/ Disconnect.me] † browser extentions to stop unwanted tracking, control data sharing||||||||||✓||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Databases'''||||||||||||||||<br />
|-<br />
|align="left"| [http://infogrid.org/ InfoGrid] - graph database for personal networking applications||✓||✓||✓|| B||||✓||✓||✓<br />
|-<br />
|align="left"| [http://projectdanube.org/ ProjectDanube] - open source software for identity and personal data services||✓||✓||✓||||||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Messaging Services and Brokers'''||||||||||||||||<br />
|-<br />
|align="left"| [https://gli.ph/ Gliph] †- private, secure identity management and messaging for smartphones||✓||||||||✓||✓||✓||<br />
|-<br />
|align="left"| [http://www.insidr.com/ Insidr] † - customer service Q&A site connecting to people who have worked in big companies and are willing to help when the company can’t or won\'t||✓||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.getabl.com/ PingUp] (was Getabl) †- chat utility for customers to engage with merchants the instant customers are looking for something||✓||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.trustfabric.com/ TrustFabric] † - service for managing relationships with sellers||✓||✓||||||✓||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Personal Data Management'''||||||||||||||||<br />
|-<br />
|align="left"| [http://www.azigo.com/ Azigo.com] † - personal data, personal agent||✓||||✓|| B||✓||||✓||<br />
|-<br />
|align="left"| [http://connect.me/ Connect.Me] † - peer-to-peer reputation, personal agent||✓||||||||✓||||✓||✓<br />
|-<br />
|align="left"| [http://higgins-project.org/ Higgins] - open source, personal data||✓||✓||✓|| B||||✓||||<br />
|-<br />
|align="left"| [https://github.com/quartzjer/Locker#readme The Locker Project] - open source, personal data||✓||✓||✓||||||||||✓<br />
|-<br />
|align="left"| [http://mydex.org/ MyDex] †- personal data stores and other services||✓||✓||✓||||✓||||✓||✓<br />
|-<br />
|align="left"| [http://www.paoga.com/ Paoga] † - personal data, personal agent||✓||||✓||||||||✓||<br />
|-<br />
|align="left"| [http://personal.com/ Personal.com] † - personal data storage, personal agent||✓||||✓||||✓||||✓||<br />
|-<br />
|align="left"| [http://personal-clouds.org/ Personal Clouds] - personal cloud wiki||✓||||✓||||||||||<br />
|-<br />
|align="left"| [http://www.privowny.com/ Privowny] † - privacy company for protecting personal identities and for tracking use and abuse of those identities, building relationships||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.qiycorporate.com/ QIY] † - independent infrastructure for managing personal data and relationships||||||✓||||||||✓||<br />
|-<br />
|align="left"| [http://sing.ly/ Singly] † - personal data storage and platform for development, with an API||✓||||✓||||✓||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Recommendations and Personal RFPs (Intentcasting)'''||||||||||||||||<br />
|-<br />
|align="left"| [http://offersbyme.com/ OffersByMe] † - personal rfp service||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://prizzm.com/ Prizzm] †- social CRM platform rewarding customers for telling businesses what they want, what they like, and what they have problems with||✓||||||||✓||||||<br />
|-<br />
|align="left"| [http://redbeacon.com/ RedBeacon] † - personal rfp service||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.thumbtack.com/ Thumbtack] † - service for finding trustworthy local service providers||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://ubokia.com/ Übokia] personal RFP†||||||||||✓||||✓||<br />
|-<br />
|align="left"| [http://www.zaarly.com/ Zaarly] † personal RFP||||||||||||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Transaction Management'''||||||||||||||||<br />
|-<br />
|align="left"| [https://www.dashlane.com/ Dashlane] † - simplified login and checkout||||||||||✓||||✓||<br />
|- style="background-color:#f0f0f0; text-align: left;" <br />
| '''Trust Frameworks & Networks'''||||||||||||||||<br />
|-<br />
|align="left"| [http://respectnetwork.com/ Respect Network] - VRM network based on KRL & XDI ||✓||✓||✓||✓||✓||✓||✓||✓<br />
|}<br />
<br />
NOTES:<br /><br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with companies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.) <br /><br />
A - creating standard<br /><br />
B - Using other standards<br /><br />
1 - EventedAPI<br /></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=5749Main Page2011-11-04T22:39:09Z<p>DrummondReed: /* VRM Development Work */</p>
<hr />
<div>== About VRM ==<br />
<br />
VRM stands for [http://en.wikipedia.org/wiki/Vendor_Relationship_Management '''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.<br />
<br />
To vendors, VRM is the customer-side counterpart 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," [http://en.wikipedia.org/wiki/Vendor_lock-in "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.<br />
<br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Customers must enter relationships with vendors as '''independent actors'''.<br />
#Customers must be the '''points of integration for their own data'''.<br />
#Customers must have '''control of data they generate and gather'''. This means they must be able to share data selectively and voluntarily.<br />
#Customers must be able to '''assert their own terms of engagement'''. <br />
#Customers must be '''free to express their demands and intentions outside of any one company's control'''.<br />
<br />
<br />
== VRM Goals ==<br />
<br />
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 goals of VRM efforts:<br />
<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals the ability to share data selectively''', without disclosing more personal information than the individual allows.<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals means for expressing demand in the open market''', outside any organizational silo, without disclosing any unnecessary personal information.<br />
#'''Make individuals platforms for business''' by opening the market to many kinds of third party services that serve buyers as well as sellers <br />
#'''Base relationship-managing tools on open standards and open APIs (application program interfaces)'''. This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.<br />
<br />
<br />
== VRM Tools ==<br />
<br />
These are ideal characteristics of VRM tools:<br />
<br />
#'''VRM tools are personal'''. As with hammers, wallets and mobile phones, people use them as individuals,. They are social only in secondary ways.<br />
#'''VRM tools help customers express intent'''. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.<br />
#'''VRM tools help customers engage'''. This can be with each other, or with any organization, including (and especially) its CRM system.<br />
#'''VRM tools help customers manage'''. This includes both their own data and systems and their relationships with other entities, and their systems.<br />
#'''VRM tools are substitutable'''. This means no source of VRM tools can lock users in.<br />
<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://www.azigo.com/ Azigo.com] † - personal data, personal agent<br />
*[http://connect.me/ Connect.Me] † - peer-to-peer reputation, personal agent<br />
*[http://ctrl-shift.co.uk/ Ctrl-SHIFT] † - analysts<br />
*[http://dot.UI dot.UI] †<br />
*[[EmanciPay]] - person-driven payments<br />
*[http://www.eventedapi.org/ Evented APIs] - standards<br />
*[[GRM: Government Relationship Management]] - subcategory of VRM<br />
*[http://higgins-project.org Higgins] - open source, personal data<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara] - legal agreements, trust frameworks<br />
*[https://github.com/kynetx/krl KRL (Kynetx Rules Language)] - personal event networks, personal rulesets<br />
*[http://kynetx.com Kynetx] † - personal event networks, personal rulesets<br />
*[[ListenLog]] - personal data logging<br />
*[https://github.com/quartzjer/Locker#readme The Locker Project] - open source, personal data<br />
*[http://hover.com Hover.com] †<br />
*[http://hypothes.is Hypothes.is] - open source, peer review<br />
*[http://myinfo.cl MyInfo.cl] (Transitioning from [http://vrm.cl VRM.cl] †<br />
*[http://newgov.us/ NewGov.us] - GRM<br />
*[http://www.paoga.com/ Paoga] † - personal data, personal agent<br />
*[http://pegasuspublic.wikispaces.com/ Pegasus]<br />
*[http://personal.com Personal.com] † - personal data storage, personal agent<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem Consortium (PDEC)] - consortia<br />
*[[Personal RFP]] - crowdsourcing, standards<br />
*[http://www.privowny.com/ Privowny] †<br />
*[http://prizzm.com Prizzm] †<br />
*[http://projectdanube.org/ ProjectDanube] - open source, personal data<br />
*[http://www.projectnori.org/ Project Nori] - open source, personal data<br />
*[http://www.qiycorporate.com/ QIY] † - personal data, personal agent<br />
*[[R-button]] - standards<br />
*[http://redbeacon.com RedBeacon] † - personal shopping<br />
*[http://sing.ly/ Singly] † - personal agent<br />
*[http://www.socialnori.org/ Social Nori] - personal data, personal agent<br />
*[http://www.getabl.com/ Getabl] †<br />
*[http://www.switchbook.com/ SwitchBook] † - personal search<br />
*[http://telehash.org Telehash] - standards, personal data protocols<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] - personal data, personal agent<br />
*[http://www.thimbl.net/ Thimbl] †<br />
*[http://www.thumbtack.com/ Thumbtack] † - personal markets<br />
*[http://ting.com/ Ting] †<br />
*[http://www.trustfabric.com/ TrustFabric] † - personal networks<br />
*[http://tucows.com Tucows] †<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA] - standards<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://code.google.com/p/webfinger/ webfinger] - standards<br />
*[http://www.zaarly.com/ Zaarly] †<br />
<br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with compnaies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.)<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
<br />
== VRM Events ==<br />
<br />
Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]<br />
<br />
=== Past Events ===<br />
2011<br />
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12][http://www.chenkrahman.com/ ,] May 3-5, Mountain View, CA<br />
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco<br />
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT<br />
* VRM Gathering at [[SXSW Interactive 2011]]<br />
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA<br />
<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA.<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA.<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
<br />
== ProjectVRM Participation ==<br />
<br />
We have two mailing lists:<br />
<br />
* Our main [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]<br />
* Our geeks-only [https://cyber.law.harvard.edu/lists/info/opensourcevrm Open Source VRM developers list]<br />
<br />
You can also edit this wiki by signing up at the top of this page.<br />
<br />
And we encourage you to use the hashtag #VRM when blogging about the topic.<br />
<br />
== Internal Links ==<br />
<br />
* [[Comittees]]<br />
* [[VRM History]]<br />
* [[VRM Research Opportunities]]<br />
* [[Implications]]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=5746Main Page2011-10-18T22:35:24Z<p>DrummondReed: /* VRM Development Work */ first draft of tagging all the entries</p>
<hr />
<div>== About VRM ==<br />
<br />
VRM stands for [http://en.wikipedia.org/wiki/Vendor_Relationship_Management '''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.<br />
<br />
To vendors, VRM is the customer-side counterpart 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," [http://en.wikipedia.org/wiki/Vendor_lock-in "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.<br />
<br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Customers must enter relationships with vendors as '''independent actors'''.<br />
#Customers must be the '''points of integration for their own data'''.<br />
#Customers must have '''control of data they generate and gather'''. This means they must be able to share data selectively and voluntarily.<br />
#Customers must be able to '''assert their own terms of engagement'''. <br />
#Customers must be '''free to express their demands and intentions outside of any one company's control'''.<br />
<br />
<br />
== VRM Goals ==<br />
<br />
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 goals of VRM efforts:<br />
<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals the ability to share data selectively''', without disclosing more personal information than the individual allows.<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals means for expressing demand in the open market''', outside any organizational silo, without disclosing any unnecessary personal information.<br />
#'''Make individuals platforms for business''' by opening the market to many kinds of third party services that serve buyers as well as sellers <br />
#'''Base relationship-managing tools on open standards and open APIs (application program interfaces)'''. This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.<br />
<br />
<br />
== VRM Tools ==<br />
<br />
These are ideal characteristics of VRM tools:<br />
<br />
#'''VRM tools are personal'''. As with hammers, wallets and mobile phones, people use them as individuals,. They are social only in secondary ways.<br />
#'''VRM tools help customers express intent'''. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.<br />
#'''VRM tools help customers engage'''. This can be with each other, or with any organization, including (and especially) its CRM system.<br />
#'''VRM tools help customers manage'''. This includes both their own data and systems and their relationships with other entities, and their systems.<br />
#'''VRM tools are substitutable'''. This means no source of VRM tools can lock users in.<br />
<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://www.azigo.com/ Azigo.com] † - personal data, personal agent<br />
*[http://connect.me/ Connect.Me] † - peer-to-peer reputation, personal agent<br />
*[http://ctrl-shift.co.uk/ Ctrl-SHIFT] † - analysts<br />
*[http://dot.UI dot.UI] †<br />
*[[EmanciPay]] - person-driven payments<br />
*[http://www.eventedapi.org/ Evented APIs] - standards<br />
*[[GRM: Government Relationship Management]] - subcategory of VRM<br />
*[http://higgins-project.org Higgins] - open source, personal data<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara] - legal agreements, trust frameworks<br />
*[https://github.com/kynetx/krl KRL (Kynetx Rules Language)] - personal event networks, personal rulesets<br />
*[http://kynetx.com Kynetx] † - personal event networks, personal rulesets<br />
*[[ListenLog]] - personal data logging<br />
*[https://github.com/quartzjer/Locker#readme The Locker Project] - personal data<br />
*[http://hover.com Hover.com] †<br />
*[http://hypothes.is Hypothes.is] - peer review<br />
*[http://myinfo.cl MyInfo.cl] (Transitioning from [http://vrm.cl VRM.cl] †<br />
*[http://newgov.us/ NewGov.us] - GRM<br />
*[http://www.paoga.com/ Paoga] † - personal data, personal agent<br />
*[http://pegasuspublic.wikispaces.com/ Pegasus]<br />
*[http://personal.com Personal.com] † - personal data storage, personal agent<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem Consortium (PDEC)] - consortia<br />
*[[Personal RFP]] - crowdsourcing, standards<br />
*[http://www.privowny.com/ Privowny] †<br />
*[http://projectdanube.org/ ProjectDanube] - open source, personal data<br />
*[http://www.projectnori.org/ Project Nori] - open source, personal data<br />
*[http://www.qiycorporate.com/ QIY] † - personal data, personal agent<br />
*[[r-button]] - standards<br />
*[http://redbeacon.com RedBeacon] † - personal shopping<br />
*[http://sing.ly/ Singly] † - personal agent<br />
*[http://www.socialnori.org/ Social Nori] - personal data, personal agent<br />
*[http://www.getabl.com/ Getabl] †<br />
*[http://www.switchbook.com/ SwitchBook] † - personal search<br />
*[http://telehash.org Telehash] - standards, personal data protocols<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] - personal data, personal agent<br />
*[http://www.thimbl.net/ Thimbl] †<br />
*[http://www.thumbtack.com/ Thumbtack] † - personal markets<br />
*[http://ting.com/ Ting] †<br />
*[http://www.trustfabric.com/ TrustFabric] † - personal networks<br />
*[http://tucows.com Tucows] †<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA] - standards<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://code.google.com/p/webfinger/ webfinger] - standards<br />
*[http://www.zaarly.com/ Zaarly] †<br />
<br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with compnaies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.)<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
<br />
== VRM Events ==<br />
<br />
Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]<br />
<br />
=== Past Events ===<br />
2011<br />
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12][http://www.chenkrahman.com/ ,] May 3-5, Mountain View, CA<br />
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco<br />
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT<br />
* VRM Gathering at [[SXSW Interactive 2011]]<br />
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA<br />
<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA.<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA.<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
<br />
== ProjectVRM Participation ==<br />
<br />
We have two mailing lists:<br />
<br />
* Our main [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]<br />
* Our geeks-only [https://cyber.law.harvard.edu/lists/info/opensourcevrm Open Source VRM developers list]<br />
<br />
You can also edit this wiki by signing up at the top of this page.<br />
<br />
And we encourage you to use the hashtag #VRM when blogging about the topic.<br />
<br />
== Internal Links ==<br />
<br />
* [[Comittees]]<br />
* [[VRM History]]<br />
* [[VRM Research Opportunities]]<br />
* [[Implications]]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=5745Main Page2011-10-18T21:33:19Z<p>DrummondReed: </p>
<hr />
<div>== About VRM ==<br />
<br />
VRM stands for [http://en.wikipedia.org/wiki/Vendor_Relationship_Management '''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.<br />
<br />
To vendors, VRM is the customer-side counterpart 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," [http://en.wikipedia.org/wiki/Vendor_lock-in "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.<br />
<br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Customers must enter relationships with vendors as '''independent actors'''.<br />
#Customers must be the '''points of integration for their own data'''.<br />
#Customers must have '''control of data they generate and gather'''. This means they must be able to share data selectively and voluntarily.<br />
#Customers must be able to '''assert their own terms of engagement'''. <br />
#Customers must be '''free to express their demands and intentions outside of any one company's control'''.<br />
<br />
<br />
== VRM Goals ==<br />
<br />
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 goals of VRM efforts:<br />
<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals the ability to share data selectively''', without disclosing more personal information than the individual allows.<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals means for expressing demand in the open market''', outside any organizational silo, without disclosing any unnecessary personal information.<br />
#'''Make individuals platforms for business''' by opening the market to many kinds of third party services that serve buyers as well as sellers <br />
#'''Base relationship-managing tools on open standards and open APIs (application program interfaces)'''. This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.<br />
<br />
<br />
== VRM Tools ==<br />
<br />
These are ideal characteristics of VRM tools:<br />
<br />
#'''VRM tools are personal'''. As with hammers, wallets and mobile phones, people use them as individuals,. They are social only in secondary ways.<br />
#'''VRM tools help customers express intent'''. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.<br />
#'''VRM tools help customers engage'''. This can be with each other, or with any organization, including (and especially) its CRM system.<br />
#'''VRM tools help customers manage'''. This includes both their own data and systems and their relationships with other entities, and their systems.<br />
#'''VRM tools are substitutable'''. This means no source of VRM tools can lock users in.<br />
<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://www.azigo.com/ Azigo.com] †<br />
*[http://connect.me/ Connect.Me] †<br />
*[http://ctrl-shift.co.uk/ Ctrl-SHIFT] †<br />
*[http://dot.UI dot.UI] †<br />
*[[EmanciPay]]<br />
*[http://www.eventedapi.org/ Evented APIs]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://higgins-project.org Higgins]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]<br />
*[https://github.com/kynetx/krl KRL]<br />
*[http://kynetx.com Kynetx] †<br />
*[[ListenLog]]<br />
*[https://github.com/quartzjer/Locker#readme The Locker Project]<br />
*[http://www.eclipse.org/higgins/ Higgins]<br />
*[http://hover.com Hover.com] †<br />
*[http://hypothes.is Hypothes.is]<br />
*[http://myinfo.cl MyInfo.cl] (Transitioning from [http://vrm.cl VRM.cl] †<br />
*[http://newgov.us/ NewGov.us]<br />
*[http://www.paoga.com/ Paoga] †<br />
*[http://pegasuspublic.wikispaces.com/ Pegasus]<br />
*[http://personal.com Personal.com] †<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem]<br />
*[[Personal RFP]]<br />
*[http://www.privowny.com/ Privowny] †<br />
*[http://projectdanube.org/ ProjectDanube]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[http://www.qiycorporate.com/ QIY] †<br />
*[[r-button]]<br />
*[http://redbeacon.com RedBeacon] †<br />
*[http://sing.ly/ Singly] †<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.getabl.com/ Getabl] †<br />
*[http://www.switchbook.com/ SwitchBook] †<br />
*[http://telehash.org Telehash]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project]<br />
*[http://www.thimbl.net/ Thimbl] †<br />
*[http://www.thumbtack.com/ Thumbtack] †<br />
*[http://ting.com/ Ting] †<br />
*[http://www.trustfabric.com/ TrustFabric] †<br />
*[http://tucows.com Tucows] †<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
*[http://www.zaarly.com/ Zaarly] †<br />
<br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with compnaies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.)<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
<br />
== VRM Events ==<br />
<br />
Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]<br />
<br />
=== Past Events ===<br />
2011<br />
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12][http://www.chenkrahman.com/ ,] May 3-5, Mountain View, CA<br />
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco<br />
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT<br />
* VRM Gathering at [[SXSW Interactive 2011]]<br />
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA<br />
<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA.<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA.<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
<br />
== ProjectVRM Participation ==<br />
<br />
We have two mailing lists:<br />
<br />
* Our main [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]<br />
* Our geeks-only [https://cyber.law.harvard.edu/lists/info/opensourcevrm Open Source VRM developers list]<br />
<br />
You can also edit this wiki by signing up at the top of this page.<br />
<br />
And we encourage you to use the hashtag #VRM when blogging about the topic.<br />
<br />
== Internal Links ==<br />
<br />
* [[Comittees]]<br />
* [[VRM History]]<br />
* [[VRM Research Opportunities]]<br />
* [[Implications]]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=5744Main Page2011-10-18T21:32:49Z<p>DrummondReed: +Connect.Me (company)</p>
<hr />
<div>== About VRM ==<br />
<br />
VRM stands for [http://en.wikipedia.org/wiki/Vendor_Relationship_Management '''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.<br />
<br />
To vendors, VRM is the customer-side counterpart 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," [http://en.wikipedia.org/wiki/Vendor_lock-in "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.<br />
<br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Customers must enter relationships with vendors as '''independent actors'''.<br />
#Customers must be the '''points of integration for their own data'''.<br />
#Customers must have '''control of data they generate and gather'''. This means they must be able to share data selectively and voluntarily.<br />
#Customers must be able to '''assert their own terms of engagement'''. <br />
#Customers must be '''free to express their demands and intentions outside of any one company's control'''.<br />
<br />
<br />
== VRM Goals ==<br />
<br />
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 goals of VRM efforts:<br />
<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals the ability to share data selectively''', without disclosing more personal information than the individual allows.<br />
#'''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.<br />
#'''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.<br />
#'''Give individuals means for expressing demand in the open market''', outside any organizational silo, without disclosing any unnecessary personal information.<br />
#'''Make individuals platforms for business''' by opening the market to many kinds of third party services that serve buyers as well as sellers <br />
#'''Base relationship-managing tools on open standards and open APIs (application program interfaces)'''. This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.<br />
<br />
<br />
== VRM Tools ==<br />
<br />
These are ideal characteristics of VRM tools:<br />
<br />
#'''VRM tools are personal'''. As with hammers, wallets and mobile phones, people use them as individuals,. They are social only in secondary ways.<br />
#'''VRM tools help customers express intent'''. These include preferences, policies, terms and means of engagement, authorizations, requests and anything else that’s possible in a free market, outside any one vendor’s silo or ranch.<br />
#'''VRM tools help customers engage'''. This can be with each other, or with any organization, including (and especially) its CRM system.<br />
#'''VRM tools help customers manage'''. This includes both their own data and systems and their relationships with other entities, and their systems.<br />
#'''VRM tools are substitutable'''. This means no source of VRM tools can lock users in.<br />
<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://www.azigo.com/ Azigo.com] †<br />
*[http://connect.me/ Connect.Me †<br />
*[http://ctrl-shift.co.uk/ Ctrl-SHIFT] †<br />
*[http://dot.UI dot.UI] †<br />
*[[EmanciPay]]<br />
*[http://www.eventedapi.org/ Evented APIs]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://higgins-project.org Higgins]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]<br />
*[https://github.com/kynetx/krl KRL]<br />
*[http://kynetx.com Kynetx] †<br />
*[[ListenLog]]<br />
*[https://github.com/quartzjer/Locker#readme The Locker Project]<br />
*[http://www.eclipse.org/higgins/ Higgins]<br />
*[http://hover.com Hover.com] †<br />
*[http://hypothes.is Hypothes.is]<br />
*[http://myinfo.cl MyInfo.cl] (Transitioning from [http://vrm.cl VRM.cl] †<br />
*[http://newgov.us/ NewGov.us]<br />
*[http://www.paoga.com/ Paoga] †<br />
*[http://pegasuspublic.wikispaces.com/ Pegasus]<br />
*[http://personal.com Personal.com] †<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem]<br />
*[[Personal RFP]]<br />
*[http://www.privowny.com/ Privowny] †<br />
*[http://projectdanube.org/ ProjectDanube]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[http://www.qiycorporate.com/ QIY] †<br />
*[[r-button]]<br />
*[http://redbeacon.com RedBeacon] †<br />
*[http://sing.ly/ Singly] †<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.getabl.com/ Getabl] †<br />
*[http://www.switchbook.com/ SwitchBook] †<br />
*[http://telehash.org Telehash]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project]<br />
*[http://www.thimbl.net/ Thimbl] †<br />
*[http://www.thumbtack.com/ Thumbtack] †<br />
*[http://ting.com/ Ting] †<br />
*[http://www.trustfabric.com/ TrustFabric] †<br />
*[http://tucows.com Tucows] †<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
*[http://www.zaarly.com/ Zaarly] †<br />
<br />
† Indicates companies. Others are organizations, development projects or both. Some development projects are affiliated with compnaies. (e.g. Telehash and The Locker Project with Singly, and KRL with Kynetx.)<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
<br />
== VRM Events ==<br />
<br />
Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]<br />
<br />
=== Past Events ===<br />
2011<br />
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12][http://www.chenkrahman.com/ ,] May 3-5, Mountain View, CA<br />
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco<br />
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT<br />
* VRM Gathering at [[SXSW Interactive 2011]]<br />
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA<br />
<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA.<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA.<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
<br />
== ProjectVRM Participation ==<br />
<br />
We have two mailing lists:<br />
<br />
* Our main [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]<br />
* Our geeks-only [https://cyber.law.harvard.edu/lists/info/opensourcevrm Open Source VRM developers list]<br />
<br />
You can also edit this wiki by signing up at the top of this page.<br />
<br />
And we encourage you to use the hashtag #VRM when blogging about the topic.<br />
<br />
== Internal Links ==<br />
<br />
* [[Comittees]]<br />
* [[VRM History]]<br />
* [[VRM Research Opportunities]]<br />
* [[Implications]]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Wikipedia_Article_Discussion&diff=4491Wikipedia Article Discussion2010-10-08T05:19:19Z<p>DrummondReed: + Joe Andireu feedback</p>
<hr />
<div>This page is for suggestions about which VRM terms should be added as Wikipedia articles and how they should be linked. Please edit as needed to share your views.<br />
<br />
== New Articles ==<br />
Drummond suggests adding the following Wikipedia articles. See [http://www.equalsdrummond.name/?p=337 his blog entry] about these terms for rationale.<br />
# [[Personal data service]]<br />
# [[Personal data server]]<br />
# [[Personal data store]]<br />
# [[Personal data ecosystem]]<br />
<br />
== Disambiguation Links ==<br />
Drummond suggests editing the [http://en.wikipedia.org/wiki/PDS PDS] page to add disambiguation entries with links to the first three articles above.<br />
<br />
== Cross-Links ==<br />
Drummond suggests all three of the above include links to each other and to the [http://en.wikipedia.org/wiki/Vendor_Relationship_Management] page (plus other page-specific links as needed, such as to the [http://mydex.org/2010/09/27/the-case-for-personal-information-empowerment-mydex-publishes-groundbreaking-white-paper/ Mydex white paper].<br />
<br />
== Next Steps ==<br />
# Complete preliminary discussion of the above on the [http://cyber.law.harvard.edu/lists/info/projectvrm ProjectVRM mailing list].<br />
# Compose first drafts of the three articles above.<br />
# When there is consensus, post everything to Wikipedia.<br />
<br />
== Change Log (Reverse Chronological Order) ==<br />
* --[[User:DrummondReed|DrummondReed]] 05:19, 8 October 2010 (UTC): Added Joe Andrieu's feedback below.<br />
* --[[User:DrummondReed|DrummondReed]] 22:06, 7 October 2010 (UTC): Broke out personal data server so it will be its own article per feedback from Katherine Warman Kern.<br />
<br />
== Feedback ==<br />
<br />
=== Joe Andrieu 2010-10-07 Email to ProjectVRM List ===<br />
<br />
''Drummond,<br />
<br />
I'm a bit surprised you didn't include references to the work already done by folks in this community. An oversight, I'm sure, because I know the point of the exercise is, in fact, to unify these disparate views. And I'm guessing I may have missed some of the references in what I list here, like Paul's work. I'd suggest linking to all of those as part of the VRM wiki to provide background & context.<br />
<br />
My single biggest complaint would a personal data service sounds like it would also include those services which use my personal data to provide value to me, as opposed to just those services that mediate access & permissions.<br />
<br />
In UMA, this role is an Authorization Manager:<br />
http://kantarainitiative.org/confluence/display/uma/Lexicon<br />
<br />
Using the information sharing terminology developed last year:<br />
http://kantarainitiative.org/confluence/display/infosharing/Lexicon<br />
This role is an intermediary.<br />
<br />
Or using the glossary from the pRFP Engagement Model:<br />
http://kantarainitiative.org/confluence/display/infosharing/Personal+RFP+Engagement+Model<br />
This role is a facilitator.<br />
<br />
Finally, if you use the lexicon that Doc, Iain, Kaliya, Craig, and I developed after the last VRM Workshop:<br />
http://blog.joeandrieu.com/2010/09/17/personal-data-stores-exchanges-and-applications/ <br />
This role is a personal data exchange.<br />
<br />
My hope is that at the end of this process, we have a set of terms that will be essentially understood by the unitiated at first sight. The first three times I read through your blog post, Drummond, I thought you were combining exchanges and applications in your definition of personal data services. So, I think personal data service fails to be easily understood, even with a sophisticated reader.<br />
<br />
I think this is backed up by Katherine's comments where she imagines a personal data store as an aggregator of information. It's more likely that it's the exchange that acts as the aggregator, while the underlying data continues to live at its "native" store.<br />
<br />
One key element here I don't think any of us have adequately addressed is the distinction between on-demand data used in mash-ups, and collated, cached data aggregated and stored. A premise I've been operating on is highly preferential to the first, but many people's mental model of a datastore is of the latter. Given the zero-distance network, I believe the future is in mashups, not in stored aggregation. Yes, we'll cache when it speeds things up, but that's fundamentally different than aggregating all your data into one place so you can use it. Instead, use an exchange to let the data be served from wherever it is and consuming applications can pull it together at run-time to provide value. Not only does this eliminate a whole raft of data quality & maintenance issues, it removes the aggregated data store as a honey pot for hacking one place to get all your lovely information. Unfortunately, I'm not sure how to make this distinction in our lexicon.<br />
<br />
My second biggest complaint is similar to the first, but regarding the connotative confusion between a personal data server and a personal data store. If I hear (or read) "personal data server", my first interpretation is to think that is a machine that serves up personal data. But it isn't. It's software that operates a personal data service. Unfortunately, "server" is used to mean the software, the hardware, and the running instance of that software, depending on context. This innate ambiguity doesn't bode well for "server" as a term.<br />
<br />
I think the root of the problem is that "service" and "server" are incredibly general terms that are used throughout our industry for several different meanings. Even combined with an adjective and declared as part of a curated lexicon, I have a hard time believing that a majority of people would hold on to the distinctions in common usage. On the other hand, stores, apps, and exchanges seem to have fairly distinct niches in our mental model of how the world works.<br />
<br />
Finally, I'll put in a vote against Ecosystem. I know a lot of work has gone into using that name, especially with the formation of the new IC3's Personal Data Ecosystem group. However, an ecosystem includes predators and parasites and digestive, destructive niches. I've never been a fan of its use for engineered systems because unless you're doing some sort of genetic evolution, you rarely design in willful subjugation, exploitation, and destruction of elements in the system.<br />
<br />
Doc, Craig and I played around with "grove" as a metaphor for this system of stores, exchanges, and apps, but that has it's own problems. What it /does/ have, however, is a unique space in our mental architecture. If "grove" were established in our lexicon, it'd be absolutely clear what we mean when we tell companies to integrate the Grove into their business or be a part of the Grove or get in the Grove, just as we said the same things about the Web. Telling a company they need to get into the Ecosystem just doesn't have the same clarity. You still have to answer which ecosystem you're talking about.<br />
<br />
Since I have so many comments on the basic breakdown, I didn't want to directly edit the wiki. We should get the framework in general consensus, then flesh it out. Also, it'll probably be easier to understand the lexicon as a whole if all the terms had definitions on the same page, instead of having each definition separate.<br />
<br />
-j''</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Wikipedia_Article_Discussion&diff=4490Wikipedia Article Discussion2010-10-07T22:06:25Z<p>DrummondReed: Broke out personal data server so it will be its own article per feedback from Katherine Warman Kern</p>
<hr />
<div>This page is for suggestions about which VRM terms should be added as Wikipedia articles and how they should be linked. Please edit as needed to share your views.<br />
<br />
== New Articles ==<br />
Drummond suggests adding the following Wikipedia articles. See [http://www.equalsdrummond.name/?p=337 his blog entry] about these terms for rationale.<br />
# [[Personal data service]]<br />
# [[Personal data server]]<br />
# [[Personal data store]]<br />
# [[Personal data ecosystem]]<br />
<br />
== Disambiguation Links ==<br />
Drummond suggests editing the [http://en.wikipedia.org/wiki/PDS PDS] page to add disambiguation entries with links to the first three articles above.<br />
<br />
== Cross-Links ==<br />
Drummond suggests all three of the above include links to each other and to the [http://en.wikipedia.org/wiki/Vendor_Relationship_Management] page (plus other page-specific links as needed, such as to the [http://mydex.org/2010/09/27/the-case-for-personal-information-empowerment-mydex-publishes-groundbreaking-white-paper/ Mydex white paper].<br />
<br />
== Next Steps ==<br />
# Complete preliminary discussion of the above on the [http://cyber.law.harvard.edu/lists/info/projectvrm ProjectVRM mailing list].<br />
# Compose first drafts of the three articles above.<br />
# When there is consensus, post everything to Wikipedia.<br />
<br />
== Change Log (Reverse Chronological Order) ==<br />
* --[[User:DrummondReed|DrummondReed]] 22:06, 7 October 2010 (UTC): Broke out personal data server so it will be its own article per feedback from Katherine Warman Kern.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Wikipedia_Article_Discussion&diff=4489Wikipedia Article Discussion2010-10-07T05:22:45Z<p>DrummondReed: New page: This page is for suggestions about which VRM terms should be added as Wikipedia articles and how they should be linked. Please edit as needed to share your views. == New Articles == Drumm...</p>
<hr />
<div>This page is for suggestions about which VRM terms should be added as Wikipedia articles and how they should be linked. Please edit as needed to share your views.<br />
<br />
== New Articles ==<br />
Drummond suggests adding the following Wikipedia articles. See [http://www.equalsdrummond.name/?p=337 his blog entry] about these terms for rationale.<br />
# [[Personal data service]] (which would include a redirect from '''Personal data server''')<br />
# [[Personal data store]]<br />
# [[Personal data ecosystem]]<br />
<br />
== Redirects ==<br />
Drummond suggests that [[Personal data server]] be a redirect to [[Personal data service]], and that the latter page include a subsection about [[Personal data server]]. This is because much of the content would be redundant if theY were two separate articles. On the other hand, the concept of a [[Personal data store]] is distinct enough that it deserves its own article.<br />
<br />
== Disambiguation Links ==<br />
Drummond suggests editing the [http://en.wikipedia.org/wiki/PDS PDS] page to add disambiguation entries with links to the first three articles above.<br />
<br />
== Cross-Links ==<br />
Drummond suggests all three of the above include links to each other and to the [http://en.wikipedia.org/wiki/Vendor_Relationship_Management] page (plus other page-specific links as needed, such as to the [http://mydex.org/2010/09/27/the-case-for-personal-information-empowerment-mydex-publishes-groundbreaking-white-paper/ Mydex white paper].<br />
<br />
== Next Steps ==<br />
# Complete preliminary discussion of the above on the [http://cyber.law.harvard.edu/lists/info/projectvrm ProjectVRM mailing list].<br />
# Compose first drafts of the three articles above.<br />
# When there is consensus, post everything to Wikipedia.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4488Main Page2010-10-07T05:14:15Z<p>DrummondReed: /* VRM Terminology */</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Terminology ==<br />
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):<br />
* [[Personal data service]]<br />
* [[Personal data server]]<br />
* [[Personal data store]]<br />
* [[Personal data ecosystem]]<br />
<br />
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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM Participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4487Main Page2010-10-07T04:59:02Z<p>DrummondReed: /* VRM Terminology */</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Terminology ==<br />
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):<br />
* [[Personal Data Service]]<br />
* [[Personal Data Server]]<br />
* [[Personal Data Store]]<br />
* [[Personal Data Ecosystem]]<br />
<br />
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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM Participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4486Main Page2010-10-07T04:55:52Z<p>DrummondReed: /* VRM Development Work */</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Terminology ==<br />
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:<br />
* [[Personal Data Service]]<br />
* [[Personal Data Server]]<br />
* [[Personal Data Store]]<br />
* [[Personal Data Ecosystem]]<br />
<br />
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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[http://personaldataecosystem.org/ Personal Data Ecosystem]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM Participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4485Main Page2010-10-07T01:10:59Z<p>DrummondReed: +VRM Terminology section</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Terminology ==<br />
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:<br />
* [[Personal Data Service]]<br />
* [[Personal Data Server]]<br />
* [[Personal Data Store]]<br />
* [[Personal Data Ecosystem]]<br />
<br />
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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM Participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4484Main Page2010-10-07T01:02:29Z<p>DrummondReed: /* ProjectVRM participation */</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM Participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4483Main Page2010-10-07T00:59:01Z<p>DrummondReed: /* VRM Development Work */</p>
<hr />
<div>== About VRM ==<br />
<br />
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.<br />
<br />
In a narrow sense, VRM is the reciprocal &#151; the customer side &#151; 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.<br />
<br />
These tools are currently in development.<br />
<br />
== Project VRM ==<br />
<br />
[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. <br />
<br />
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":<br />
<br />
[[Image:Not-1.gif]]<br />
<br />
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. <br />
<br />
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.<br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM and the Economy ==<br />
<br />
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. <br />
<br />
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 &#151; and cannot be asked, as long as sellers continue to hold all the relationship cards. <br />
<br />
== VRM Principles ==<br />
<br />
VRM development work is based on the belief that ''free customers are more valuable than captive ones'' &#151; to themselves, to vendors, and to the larger economy. To be free &#151;<br />
<br />
#Relationships must be voluntary.<br />
#Customers must enter relationships with vendors as independent actors.<br />
#Customers must be the points of integration for their own data.<br />
#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.<br />
#Customers must be able to assert their own terms of engagement and service. <br />
#Customers must be free to express their demands and intentions outside of any one company's control.<br />
<br />
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.<br />
<br />
== VRM Goals ==<br />
<br />
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:<br />
<br />
#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.<br />
#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.<br />
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.<br />
#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.<br />
#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.<br />
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.<br />
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers.<br />
#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.<br />
<br />
== VRM Development Work ==<br />
<br />
Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:<br />
*[http://azigo.com Azigo]<br />
*[[EmanciPay]]<br />
*[[FCRA: Access to credit data]]<br />
*[[GRM: Government Relationship Management]]<br />
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup]<br />
*[http://kynetx.com Kynetx]<br />
*[[ListenLog]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.paoga.com/ Paoga]<br />
*[[Personal RFP]]<br />
*[http://www.projectnori.org/ Project Nori]<br />
*[[r-button]]<br />
*[http://www.socialnori.org/ Social Nori]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
*[http://www.trustfabric.org/ TrustFabric.org]<br />
*[http://kantarainitiative.org/confluence/display/uma/ UMA]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://www.banyanproject.com/ The Banyan Project]<br />
*[http://themineproject.org/ The Mine! Project] <br />
*[http://code.google.com/p/webfinger/ webfinger]<br />
<br />
== ProjectVRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
*[[Steering Committee]]<br />
<br />
== ProjectVRM Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
* [[VRM FAQ]]<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
ProjectVRM events take place once or twice per year:<br />
=== Upcoming Events ===<br />
2011<br />
* VRM Gathering at [[SXSW Interactive 2011]] (date TBD)<br />
<br />
=== Past Events ===<br />
2010<br />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
2009<br />
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University<br />
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX<br />
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA<br />
<br />
2008<br />
* [[VRM2008]] took place in Munich on 21/22 April 2008<br />
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
<br />
[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.<br />
<br />
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.<br />
<br />
== ProjectVRM participation ==<br />
<br />
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.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=ListenLog_XDI&diff=3340ListenLog XDI2009-02-27T18:53:20Z<p>DrummondReed: </p>
<hr />
<div>== About ==<br />
This page provides an overview of a proposed [http://en.wikipedia.org/wiki/XDI XDI] format for ListenLog files.<br />
<br />
== Example ListenLog XDI Document ==<br />
This example is shown in XDI [http://wiki.oasis-open.org/xdi/X3Format X3 Simple] format.<br />
<pre><br />
$ <-- XDI context self-descriptor --><br />
$is$a<br />
$$(+listenlog) <-- declares XDI context type --><br />
$is$$(+listenlog)<br />
=!f83.62b1.44f.2813 <-- User ID (XRI i-number) --><br />
$d$first<br />
"2008-01-01T12:13:14Z" <-- starting file datetime --><br />
$d$last<br />
"2008-01-14T03:04:05Z" <-- ending file datetime --><br />
+listenlog$d!2008-01-01T12:13:14Z<br />
$d$first<br />
"2008-01-01T12:13:14Z" <-- starting log entry datetime --><br />
$d$last<br />
"2008-01-01T12:18:22Z" <-- ending log entry datetime --><br />
+station<br />
@!3f45.2219.8de9.549b <-- station ID --><br />
+program<br />
@!5ce2.e907.12c9.3a55!23 <-- program ID --><br />
+location<br />
{geolocation-identifier} <-- location ID --><br />
+listenlog$d!2008-01-01T12:18:22Z<br />
$d$first<br />
"2008-01-01T12:18:22Z"<br />
$d$last<br />
"2008-01-01T12:27:56Z"<br />
+station<br />
@(http://somestation.com/)<br />
+program<br />
@(http://coolprogram.com/program)<br />
+location<br />
{geolocation-identifier}<br />
</pre><br />
<br />
== Example ListenLog XDI Dictionary ==<br />
This is the dictionary for validating a ListenLog XDI file:<br />
<pre><br />
+listenlog<br />
$has<br />
$d$$<br />
$has$a$max$1<br />
$d$first<br />
$d$last<br />
+station<br />
+program<br />
+location<br />
$d$first<br />
$is$a<br />
$d <-- XML datetime, defined in XDI $ Dictionary --><br />
$d$last<br />
$is$a<br />
$d<br />
+station<br />
$is$a<br />
@<br />
+program<br />
$is$a<br />
@<br />
+location<br />
$is$a<br />
$a$xsd$string$regex+geolocation<br />
$a$xsd$string$regex+geolocation<br />
$regex<br />
"{regex-for-geolocation-code}"<br />
</pre><br />
<br />
== Synonyms ==<br />
This is an example of how synonym maps can be stored alongside the data being described.<br />
<pre><br />
@!5ce2.e907.12c9.3a55!23<br />
$is<br />
@(http://kxxx.com/bluesforall)<br />
@1234.5678.abcd.9876!345<br />
</pre></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=ListenLog_XDI&diff=3339ListenLog XDI2009-02-27T10:21:11Z<p>DrummondReed: New page: == About == This page provides an overview of a proposed [http://en.wikipedia.org/wiki/XDI XDI] format for ListenLog files. == Example ListenLog XDI Document == This example is shown in X...</p>
<hr />
<div>== About ==<br />
This page provides an overview of a proposed [http://en.wikipedia.org/wiki/XDI XDI] format for ListenLog files.<br />
<br />
== Example ListenLog XDI Document ==<br />
This example is shown in XDI [http://wiki.oasis-open.org/xdi/X3Format X3 Simple] format.<br />
<pre><br />
$ <-- XDI context self-descriptor --><br />
$is$a<br />
$$(+listenlog) <-- declares XDI context type --><br />
$is$$(+listenlog)<br />
=!f83.62b1.44f.2813 <-- User ID (XRI i-number) --><br />
$d$first<br />
"2008-01-01T12:13:14Z" <-- starting file datetime --><br />
$d$last<br />
"2008-01-14T03:04:05Z" <-- ending file datetime --><br />
+listenlog$d!2008-01-01T12:13:14Z<br />
$d$first<br />
"2008-01-01T12:13:14Z" <-- starting log entry datetime --><br />
$d$last<br />
"2008-01-01T12:18:22Z" <-- ending log entry datetime --><br />
+station<br />
@!3f45.2219.8de9.549b <-- station ID --><br />
+program<br />
@!5ce2.e907.12c9.3a55!23 <-- program ID --><br />
+location<br />
{geolocation-identifier} <-- location ID --><br />
+listenlog$d!2008-01-01T12:18:22Z<br />
$d$first<br />
"2008-01-01T12:18:22Z"<br />
$d$last<br />
"2008-01-01T12:27:56Z"<br />
+station<br />
@(http://somestation.com/)<br />
+program<br />
@(http://coolprogram.com/program)<br />
+location<br />
{geolocation-identifier}<br />
</pre><br />
<br />
== Example ListenLog XDI Dictionary ==<br />
This is the dictionary for validating a ListenLog XDI file:<br />
<pre><br />
+listenlog<br />
$has<br />
$d$$<br />
$has$a$max$1<br />
$d$first<br />
$d$last<br />
+station<br />
+program<br />
+location<br />
$d$first<br />
$is$a<br />
$d <-- XML datetime, defined in XDI $ Dictionary --><br />
$d$last<br />
$is$a<br />
$d<br />
+station<br />
$is$a<br />
@<br />
+program<br />
$is$a<br />
@<br />
+location<br />
$is$a<br />
$a$xsd$string$regex+geolocation<br />
$a$xsd$string$regex+geolocation<br />
$regex<br />
"{regex-for-geolocation-code}"<br />
</pre></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=ListenLog&diff=3338ListenLog2009-02-27T09:27:05Z<p>DrummondReed: /* ListenLog Specifics */ + link to ListenLog XDI page</p>
<hr />
<div>=== Background ===<br />
[[Category:Media Logging]]<br />
<br />
ListenLog, or [[Listen Log]] is a form of [[Media Logging]]. It is required for [[PayChoice]] to work. PayChoice is a new business model for otherwise free media goods -- one that sharply reduces the frictions involved in paying for media. By increasing the number of people who pay for free media, PayChoice also helps stigmatize non-payment for those goods.<br />
<br />
Logging of listening is required to answer all these common questions:<br />
#What was that (program, segment, piece of music)?<br />
#Who was that (host, guest)?<br />
#Who produced that (program, segment, piece of music)?<br />
#When and where did I listen to that?<br />
#How often did I (listen to, watch or read) that in the past?<br />
#Do I have a relationship with the source? (Such as membership, or past transactions.)<br />
<br />
ListenLog is a simple utility that does nothing more than record listening data for the user. It will store it in a form that can be crunched in many ways and for many purposes -- all by the user's choice and at the user's discretion. It will be data that can go in any database or spreadsheet. It can also be shared in a selectively disclosed way. (See [[VRM Principles]].) This will make possible a marketplace for third-party services that help both listeners and the institutions with which they relate. (Starting with stations, but also including program producers, artists and others.)<br />
<br />
With ListenLog data, listeners can make fully informed choices about how they support streams, podcasts and on-demand sources of programming.<br />
<br />
Listeners can also form better relationships with stations and program sources. Membership can come to mean far more than serving as a future target for pitches and billing.<br />
<br />
Both Media Logging and PayChoice are brand new and still unproven. The former, and hopefully also the latter, are being pioneered with the Public Radio Tuner, which is currently being developed by [[http://prx.org PRX]] and other partners, including NPR and ProjectVRM at the [[http://cyber.law.harvard.edu Berkman Center]].<br />
<br />
There are challenges posed both by the pioneering nature of the work and the limitations of the iPhone.<br />
<br />
For example, the iPhone has a tiny memory for data and no persistent and user- (or program-) accessible data store on the host computer with which it syncs through iTunes. But iPhone does provide means for that data to be stored remotely, in a trusted "cloud." For this purpose, PRX has created ListenLog.org as a site/service for storing each user's data and making it available through standard web service interfaces.<br />
<br />
Because this distances the user's data from the user's devices, and requires trust in PRX (or any host), questions of trust are naturally raised. These are the same issues raised by any cloud service, including Gmail and Amazon S3. Establishing trust mechanisms -- both technical and contractual -- are non-trivial. But they are also essential for laying the groundwork required for this new business model to work.<br />
<br />
=== Overview ===<br />
<br />
The VRM ListenLog is a proposed method for integrating simple user-driven functionality into an online audio player device or application. The ListenLog concept was devised in part for the [http://publicradiotuner.com Public Radio Tuner iPhone project], where it will likely be first introduced. The ListenLog is a consolidated and documented history of an individual's online listening activity. It is simply a recorded activity log, in a standard and open format, documenting an individual's listening actions through one (or more) online devices. The ListenLog is unique in that its aim is to give the user complete control over what to do with their listener activity data, including where the data lives, who to share it with, and how it can be used.<br />
<br />
While tracking listener behavior data is not a new concept, the ListenLog is a novel approach to deploying early VRM functionality. While a simple activity log might not appear as the killer app, it succeeds by putting in place a small piece of user-driven infrastructure into a larger application - one with a promise of relatively wide distribution. Since this infrastructure component will write, store, and share listener activity in an open and standard format, we hope that such a log will become significantly more useful as other devices and tools leverage the standard to increase what an individual can do with their ListenLog data. This type of sideways approach holds the promise of planting the seeds of VRM onto lots of devices without requiring the primary application functionality (i.e. audio listening) be purely user-driven.<br />
<br />
A user-driven activity log works well for an application that pulls together audio streams and files from a number of different sources. Of course, online audio providers (vendors in the VRM model) can already track and aggregate listening behavior data, but only for the audio they control. When the user acts as the sole point of integration, pulling together audio from multiple sources, their own consolidated log becomes uniquely powerful. Only when the listener is the point of integration does such an approach yield a new type of value.<br />
<br />
=== ListenLog Specifics ===<br />
<br />
Initially, the ListenLog will capture online audio stream and file listening behavior occurring through a specific application and device in a standard format (see the [[ListenLog XDI]] page for an example). At minimum, the log will capture audio stream/file identification, user agent, listen start time, listen duration and device location information. Extending this data to incorporate unique device IDs, audio meta data, rating (e.g. thumbs-up/down), referral, or other application behavior data is a natural for consideration.<br />
<br />
The application supporting ListenLog recording capability will host the minimum of user-facing functionality. Specifically, the individual user will be able to choose a digital identity(s) with which to associate their listening data, and can also choose where the data is stored, as it will be dynamically written by the device application to any ListenLog standards compliant service provider (host).<br />
<br />
A separate ListenLog Service interface, perhaps integrated with the ListenLog storage provider, will enable the user to choose if and how to share their ListenLog data, either anonymously or as associated with digital identities. For example, an individual may choose to share all data publicly and anonymously. All users selecting this option would, in aggregate, create a single, public "firehose" feed of all listening activity. It is our hope that third-party developers will offer user-driven functionality based on your ListenLog functionality, helping you share selected data conditionally with vendors for example, or providing agnostic recommendations based on your listening habits.</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRMWorkshop_Attendees&diff=2764VRMWorkshop Attendees2008-06-18T06:23:38Z<p>DrummondReed: </p>
<hr />
<div>Attendee List:<br />
<br />
[http://doc.searls.com Doc Searls]<br><br />
[http://www.mediainfluencer.com Adriana Lukas]<br><br />
[http://www.ichoosr.com Bart Stevens]<br><br />
[http://xri.net/=charles-andres Charles Andres]<br><br />
[http://land-com.net Dean Landsman]<br><br />
Iain Henderson<br><br />
[http://blog.joeandrieu.com Joe Andrieu]<br><br />
[http://xri.net/=jtrentadams/(+about) J. Trent Adams]<br><br />
[http://adrian.medcommons.net/ Adrian Gropper]<br><br />
[http://www.identitywoman.net Kaliya Hamlin, Identity Woman]<br><br />
[http://www.red-sweater.com/blog/ Daniel Jalkut]<br><br />
[http://www.socialcustomer.com Christopher Carfi]<br><br />
[http://2idi.com/contact/=mary.ruddy Mary Ruddy]<br><br />
[http://keithhopper.com Keith Hopper]<br><br />
[http://www.brucemacvarish.com Bruce MacVarish]<br><br />
[http://identity4all.blogspot.com/ Peter Davis] (tentative)<br/><br />
[http://equalsdrummond.name/ Drummond Reed] ([http://xri.net/=drummond contact page])<br/><br />
[http://www.xmlgrrl.com Eve Maler] (tentative)<br/><br />
[http://www.parity.com/team.html#tom Tom Carroll] (tentative)<br/><br />
[http://www.deborahschultz.com Deb Schultz] (tentative)<br/></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_Workshop_2008&diff=2755VRM Workshop 20082008-06-09T18:31:56Z<p>DrummondReed: + Drummond Reed</p>
<hr />
<div>The first ProjectVRM Workshop (tag [http://technorati.com/tag/pvrmw2008a pvrmw2008a]) will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center], here at [http://harvard.edu Harvard University], on Monday-Tuesday 14-15 July.<br />
<br />
We're thinking of calling it "Relacon", in the model of Bloggercon, the first of which was conducted by Dave Winer here at Harvard, in 2003. It was a good model for many unconferences that followed, incluidng the [http://iiw.idcommons.net/index.php/Main_Page IIW -- Internet Identity Workshop], an outstanding and highly productive workshop that has been happening twice a year since Fall 2005. VRM was a big topic at the last one, and perhaps the next one too. This VRM workshop is posed as the first at which the VRM conversation finally breaks off on its own from incubation at the IIWs.<br />
<br />
The main purpose of the workshop is to work on development: moving code forward, and bringing existing code together. Also for the various committees to get together in physical space to move their work forward as well. <br />
<br />
There won't be a cost to the event, but our budget is minimal, so basically what we'll be doing is making use of a small block Harvard classrooms at a time when school is out of session. <br />
<br />
If you can come, please add your name to the attendee list. If working with a wiki is daunting for you (as it is for most people), please send me your name and I'll add it to the list. My email: dsearls AT cyber.law.harvard.edu<br />
<br />
- Doc Searls <br />
<br />
Attendee List:<br />
<br />
[http://doc.searls.com Doc Searls]<br><br />
[http://www.mediainfluencer.com Adriana Lukas]<br><br />
[http://www.ichoosr.com Bart Stevens]<br><br />
[http://xri.net/=charles-andres Charles Andres]<br><br />
[http://land-com.net Dean Landsman]<br><br />
Iain Henderson<br><br />
[http://blog.joeandrieu.com Joe Andrieu]<br><br />
[http://xri.net/=jtrentadams/(+about) J. Trent Adams]<br><br />
[http://adrian.medcommons.net/ Adrian Gropper]<br><br />
[http://www.identitywoman.net Kaliya Hamlin, Identity Woman]<br><br />
[http://www.red-sweater.com/blog/ Daniel Jalkut]<br><br />
[http://www.socialcustomer.com Christopher Carfi]<br><br />
[http://2idi.com/contact/=mary.ruddy Mary Ruddy]<br><br />
[http://keithhopper.com Keith Hopper]<br><br />
[http://www.brucemacvarish.com Bruce MacVarish]<br><br />
[http://identity4all.blogspot.com/ Peter Davis] (tentative)<br/><br />
[http://equalsdrummond.name/ Drummond Reed] ([http://xri.net/=drummond contact page]) (tentative)<br/></div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_FAQ&diff=2641VRM FAQ2008-04-21T23:41:54Z<p>DrummondReed: added a bunch of questions (missing answers)</p>
<hr />
<div>== What is VRM? ==<br />
'''V'''endor '''R'''elationship '''M'''anagement. The one-liner is that, "VRM is the inverse of CRM - [http://en.wikipedia.org/wiki/Customer_relationship_management Customer Relationship Management]".<br />
<br />
== How is VRM the inverse of CRM? ==<br />
<br />
== What are some typical examples of how an individual would use VRM? ==<br />
<br />
''<br />
* Change-of-address<br />
* Digital receipts<br />
* Personal RFPs<br />
''<br />
<br />
== Why would companies support VRM? ==<br />
<br />
== How did VRM get started? ==<br />
<br />
== Is there a VRM industry association? How does it represent individuals? ==<br />
<br />
== How is VRM related to Internet identity? ==<br />
<br />
== How is VRM related to data portability? ==<br />
<br />
== What's a relationship button (relbutton or r-button)? ==<br />
<br />
== What's a relationship card? ==<br />
<br />
== Is VRM about technical standards or business principles? ==<br />
[My question was not about technical standards versus business principles. It relates to what VRM looks like. Is VRM defined solely in terms of technical standards, or does it also include new services and business models that stand on the side of the individual when dealing with vendors and change the nature of commercial relationships? I think that clearly it has to. VRM is not just a technology.<br />
<br />
I may have been my mis-reading the 5 levels of maturity, but the 'flavour' of what came across was that in the end, it's really all about clever new bits of technology. Alan]<br />
<br />
Yes. It is both clever bits of code and new best practices for businesses. Doc Searls has made it clear from the beginning that Project VRM is a development project: that the end goal is working code that makes a difference in the real world. At the same time, Doc has also made it clear that the ultimate goal is fixing the marketplace, which means that new best practices '''will''' emerge. <br />
<br />
Joe Andrieu advocates a drive towards interoperable relationship services--using both standards and running code--which will transform the marketplace by giving companies a new way to increase their profits. By giving companies a winning proposition, we can get them to adopt new methodologies and new business principles. This is similar to the way that the web was adopted because it made business sense, and as it was adopted, radically changed how companies and customers relate. Without http and HTML the transformation that enabled the Cluetrain Manifesto never would've happened, and in fact, it was the openness of those standards that enabled the world wide web to displace Lotus Notes as intranetware and AOL/Compuserve as online services. Joe sees a similar technology-led VRM revolution, where Project VRM catalyzes change by assuring standards and applications that enable individuals to play in the marketplace on their own terms in a way that also improves businesses' bottom lines.<br />
<br />
== How can companies "implement" VRM when it is the individual who is managing the relationships? Doesn't it create a conceptual mess that risks smuggling the corporation as relationship manager back in by the back door? ==<br />
To Sean Bohan, while the user is in charge (driving the relationship) there still needs to be some corresponding structures on the Vendor side to accept/interact/transact with that VRM'd user. There needs to be a nut for the bolt. Vendors must have some form of acceptance, some framework that can work with customers who are in charge. Compliant and Aligned both work for me, but I was trying to get across the idea that there is commitment, acceptance and more importantly, '''work''' on the Vendor's side to be VRM compliant. Doc said in the past this needs to be Win-Win for the vendors too, and "Implement" is something a BigCo guy would understand (I get something out of implementation). "Implement" may be the wrong word (it was workin form me in the wee hours of the morning) - and we can change it. I think the idea of "smuggling the corporation as relationship manager back in" is also something that needs to be discussed in the context of compliance and standards (which Brett was crystal clear on in the last call). Not sure which committee would handle that or if it is a grenade the whole group should jump on at once. <br />
<br />
Joe Andrieu agrees: there must be a nut for the bolt '''and''' users are not going to build their own bolt. There is a need for Vendors to implement the "receiving" side of the VRM equation. This isn't about tools that are one-sided on behalf of the user. Full participation means both Vendors and individuals participate and benefit. Also, someone needs to build those tools for the individuals. In this latter sense, companies "implementing" VRM are those tool providers enabling individuals to participate in VRM relationship services.<br />
<br />
[VRM is not SAP and the slightest hint that it is is extremely dangerous. We are talking at two different levels here. Operationally speaking, companies have to 'implement' changes to become a bolt that fits the nut. That goes without saying. <br />
<br />
But at another psyschological/presentational level the word 'implement' fits and reinforces corporations' customer control agenda. We have to work effectively at both levels: the message to the corporation has to be 'you will only realise the win-wins by handing over control - i.e. letting the customer manage the relationship'. So it is as much about all the baggage corporate types simply assume when they hear a word, as it is about technically correct English. Alan]<br />
<br />
Alan, respectfully, I have to disagree with the statement "the message to the corporation has to be 'you will only realise the win-wins by handing over control - i.e. letting the customer manage the relationship'." That's putting things into an extreme that is neither palatable nor necessary. I would suggest instead that what we are saying to corporations is "here is an opportunity to create more value for your customers and your bottom line. It requires rethinking what is important to you in terms of control, but at the end of the day it gives you greater predictability, better product insights, and deeper, more meaningful relationships with more loyal customers." The '''political''' argument that companies need to give up control is no more appealing to me than any of the other political consumer movements out there, from Carbon-neutral to not-tested on animals to Fair Trade. These movements (which I actually support politically) are at their core ideological and therefore subject to extreme limitations, namely a lack of common ground with those who don't agree with '''your''' agenda. VRM on the other hand, like the World Wide Web, is enabling a radically new type of marketplace that will be adopted by individuals and companies alike because it is, unequivocally, '''economically''' superior, no agenda required. No need to debate the ideology--just point to the bottom line. IMO, any other debate is unnecessarily controversial. --[[User:Joe.andrieu|Joe.andrieu]] 17:13, 18 April 2008 (EDT)</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_vision&diff=2640VRM vision2008-04-21T23:19:23Z<p>DrummondReed: extensive edits to shorten and format</p>
<hr />
<div>VRM, or Vendor Relationship Management, is the reciprocal of CRM or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]. VRM describes a set of tools, technologies and services that help individuals go to market and manage relationships with vendors. In turn, vendors who align themselves to these tools, technologies and services will have the opportunity to build better relationships with their customers.<br />
<br />
The goal of VRM is to improve the relationship between Demand and Supply by providing new and better ways for the former to relate to the latter. In a larger sense, VRM immodestly intends to improve markets and their mechanisms by equipping customers to be independent leaders and not just captive followers in their relationships with vendors and other parties on the supply side of the marketplace.<br />
<br />
== History ==<br />
CRM systems for the duration have borne the full burden of relating with customers. VRM will provide customers with the means to bear some of that weight, and to help make markets work for ''both'' vendors and customers in ways that don't require the former to "lock in" the latter.<br />
<br />
''TODO â details for this section:<br />
* Where name came from<br />
* Where idea came from (relationship with the Cluetrain Manifesto)<br />
** Core concepts & shifting landscape: Internet increasing alienation between consumer and vendor, etc.<br />
* How VRM has helped leverage (and tries to see ahead of) ideas being worked on in the identity space, etc.<br />
''<br />
<br />
== Problems With CRM ==<br />
CRM, as originally envisaged, was a reasonably attractive proposition to the end customer. The idea was that an organisation would build a more complete view of the customer across their many touchpoints (retail, phone, email, events, etc.), and then, via investing in software, changing culture, and integrating marketing, sales and service, the organization would be able to be more responsive to the customers needs and provide more satisfying sales and service.<br />
<br />
However, more often than not, organisations underestimated the cost of the cultural change â or decided (wrongly) they could do without it. Many also tended to focus more on the cost saving potential of the new technologies than the relationship improvement potential. But one structural problem emerged to surpass all the tactical issues with the vision or how it was deployed: ''it is impossible for any one organisation to build a comprehensive view of their customer''. Some, with great effort, can build a complete view of THEIR OWN relationship with a customer; but they will still be largely unaware of the many other supply relationships that the customer typically maintains (over 100 would not be unusual).<br />
<br />
Only the individual, when given access to the necessary tools and processes, can create anything approaching a complete view of their supply requirements.<br />
<br />
== Project VRM ==<br />
<br />
''TODO â details for this section:<br />
* Berkman Center - Steering Committee<br />
* Doc Searls, Champion<br />
* Objectives<br />
''<br />
<br />
== Challenges for VRM ==<br />
For VRM to work, vendors must have a reason to value it, and customers must have reasons to invest the necessary time, effort and attention to making it work. Solving this "chicken-and-egg" problem for both sides is the primary challenge for VRM.<br />
<br />
''TODO â details for this section:<br />
* Iconoclastic anti-vendor perception<br />
* Need killer apps<br />
''<br />
<br />
== VRM Capabilities & Standards ==<br />
<br />
Following are some of the generic capabilities listed at the [http://projectvrm.org Project VRM website] that are anticipated to emerge as part of VRM adoption.<br />
<br />
=== Personal Data Stores ===<br />
<br />
This is a generic term for one or more services that help individuals gather, store, protect, analyze, share and use information describing themselves, their relationships, their transactions, and their intentions.<br />
<br />
VRM envisions that personal data stores will become the means by which individuals plan, administer and organize many aspects of their daily lives as well as conduct interactions and transactions with vendors. With personal data stores, individuals will be able to pull together their own: <br />
<br />
* Administrative records and details <br />
* Contact databases: friends, family, colleagues etc.<br />
* Transaction histories: products and services purchases, etc.<br />
* Interaction histories: records of correspondence <br />
* Supplier data ('my doctor', 'my plumber', etc.)<br />
* Personal preferences e.g. 'favored' brands and organizations vs 'blacklisted' brands and organizations <br />
* Plans for life projects (trips, moving home etc) <br />
* Information gathered and collected to help inform decisions and actions about all the above. <br />
<br />
=== Personal Data Analytics ===<br />
<br />
Just as vendors mine and analyse the data in their CRM systems to better understand their customers, individuals will be able to mine and analyse the VRM data in their own personal data stores to better understand their needs and make better buying decisions. Personal data analytics can help users: <br />
<br />
* Track trends such as personal spending, calorie intake, household energy usage, car mileage, etc.<br />
* Use 'people like you' comparisons to highlight areas where their resources could be better managed.<br />
* Anticipate and understand spending changes after major life events, such as marriage, having children, getting divorced, etc.<br />
<br />
=== Request for Proposal (RFP) ===<br />
<br />
A Request for Proposal (RFP) is a message sent from an individual to a company, set of companies, or marketplace declaring the individual's need for a product or service. RFPs are a "reverse market" where customers publish their needs/requirements/specifications and vendors can respond with their offer/price/terms. This creates an environment where the consumer has a direct the product or solution, as opposed to accepting a solution that by it's very nature is advantageous to the vendor. <br />
<br />
RFPs can range from simple commodity requests (e.g. insurance renewal, new lawnmower, laptop computer) to specifications for products or services that do not even exist yet. They can take many forms: <br />
<br />
* ''One-to-one'', where a named individual sends his request directly to one or more named companies <br />
* ''Aggregated'', where multiple individuals' requests are collated and passed on to companies by an intermediary. Companies then respond to these RFPs either on an individual or collective basis. <br />
* ''Anonymized'', where an intermediary informs a company or set of companies that a specific number of customers are seeking out a particular product or service, but access is only provided through the intermediary until a transaction is closed. <br />
<br />
=== Permissions Management and Reverse Messaging ===<br />
<br />
Though "permission marketing" has become a buzzword, in practice it has not lived up to its hype. True permission management must put the individual fully in control, allowing them to specify the "rules of engagement" for marketing relationships and to maintain that control over time. <br />
<br />
Permissions management covers both receiving information and releasing information on a timely and relevant basis. In the former case, for example, an individual may be planning to buy a new car in June. He could specify his willingness to receive messages about new cars, in a specific price bracket, from specific brands/dealers, in the months of April and May, but be assured that all such communications will cease June 1. This is also called "reverse messaging", and its success hinges completely on the individual's confidence that they have 100% control over the reverse messaging channel, i.e., they can fine tune it or shut it off just as they can with their TV. This can be accomplished using specially-generated addresses (such as a custom email or instant messaging address) whose lifespan is controlled by the user.<br />
<br />
Individuals can also choose what data to release to what vendors, for what purposes, on what terms and conditions. For example, a person may want to release information about: <br />
<br />
* Medical history and lifestyle, to health researchers, on an anonymous basis, for free, for the purposes of cancer research.<br />
* Their current inventory of hardware and software, to a specialist retailer/reseller, on a named but once-only use basis, for the purposes of advice on solving a computing problem or buying a new peripheral.<br />
* Clothing and cosmetic brand preferences, on an anonymous basis, to marketing companies, in return for a fee.<br />
<br />
=== Power of Attorney Services ===<br />
<br />
Many aspects of managing a supply relationship are tedious and time-consuming, such as renewing insurance or performing scheduled maintainance on a vehicle. As a result many buyers settle for something far from the best value just to avoid the hassle.<br />
<br />
With power of attorney services, individuals can give buying agents permission to act on their behalf, within certain parameters, without the need for specific detailed negotiation. For example, the individual may give power of attorney to the agent to sweep the market for best prices for insurance contracts with equivalent terms, one month before their current contract is due to come to an end. <br />
<br />
=== Problem Solving Communities (PSCs) === <br />
<br />
Before purchasing a product or service, individuals often need to answer a long series of questions, such as: <br />
<br />
* What are the available options? <br />
* What things do I need to do achieve my desired outcome? <br />
* How do I do x or y? <br />
* What are the hidden pitfalls that I ought to be aware of? <br />
* Who can I trust? <br />
* Which is better for somebody in my circumstances, option A or option B?<br />
<br />
Although online and offline services exist to help individuals in some cases, often the best source of information is other individuals facing the same decision. Problem solving communities tap this potential by collecting answers other people have discovered and making them available, avoiding the need for each new individual to reinvent the wheel. <br />
<br />
VRM has the potential to bring real economies of scale to this process. <br />
If it costs $100 to research and formulate a good answer to a certain question, then it adds $100 to the cost of the product or service in question. But if the same answer is used 1000 times over, the unit cost falls from $100 to $0.1: a productivity boost of 99.9%. <br />
<br />
=== Personal Scenario Planning ===<br />
<br />
Lastly, there are some events in our lives which few of us encounter often enough to become expert at handling them: getting married or divorced, moving, organizing a trip round the world, coping with a life threatening illness or accident, surviving the death of partner, etc. <br />
<br />
Scenario Planning is like a specialized type of problem solving community. It identifies best practices, pitfalls to watch out for, and other essential knowledge about a key life event. For example, if you are getting married, a scenario planning service can help you organize details such as venue, ceremony, invites, attire, presents, catering, travel, honeymoon, etc.<br />
<br />
Since many of these decisions involve vendor relationships, scenario planning can integrates many of the other components of VRM systems, bringing them all to bear to simplify what can otherwise be an overwhelming set of choices in a short period of time. <br />
<br />
<br />
== Related Initiatives ==<br />
<br />
=== Internet Identity ===<br />
VRM is closely related to Internet identity for the simple reason that in order to control their own data and relationships across vendors, users must be able to assert their identity independent from any particular vendor relationship. <br />
<br />
Widely known as "user-centric identity", this field includes technologies such as [http://en.wikipedia.org/wiki/OpenID OpenID], [http://en.wikipedia.org/wiki/I-cards information cards (i-cards)], the [http://en.wikipedia.org/wiki/Higgins_project Higgins Project], and [http://en.wikipedia.org/wiki/XDI XDI]. All of these technologies seek to provide users with a way to control their identity, data, and relationships without dependence on any one vendor or service provider.<br />
<br />
=== Data Portability (DP) ===<br />
<br />
[http://en.wikipedia.org/wiki/DataPortability Data portability] seeks to do for all forms of data what [http://en.wikipedia.org/wiki/Telephone_number_portability telephone number portability] has done for phone numbers. DP promotes the ability for users to move and share their identity, contacts, photos, videos, or any other form of personal data from one website or web service to another. Like Internet identity, data portability is essential to VRM because without it, users can be "locked in" to vendor relatioships and restricted from full freedom-of-choice.<br />
<br />
=== Relationship Cards (R-Cards) ===<br />
<br />
Relationship cards, commonly called r-cards, are a new type of [http://en.wikipedia.org/wiki/I-cards information card (i-card)] developed by the [http://en.wikipedia.org/wiki/Higgins_project Higgins Project] that enable automated data sharing relationships. R-cards can instantiate any type of relationship â person-to-person, person-to-vendor, or vendor-to-vendor â and can be used to share and automatically synchronize changes to any type of data, from an email address to an loyalty points balance to a wedding gift registry.<br />
<br />
See the details under the Wikipedia [[http://en.wikipedia.org/wiki/I-cards i-card] entry.<br />
<br />
== VRM Example Uses ==<br />
<br />
''TODO â details of this section.''<br />
List practical, leading examples of best proposed uses for VRM. Link to Use Cases (if any)<br />
* Personal Address Manager<br />
''<br />
<br />
== VRM Companies ==<br />
<br />
''TODO â details of this section.''<br />
Companies, sellers, vendors all may have existing examples of VRM. Please post them here.<br />
''<br />
<br />
== Additional Links ==<br />
* [[VRM FAQ]]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Personal_Address_Manager_Service&diff=2407Personal Address Manager Service2008-03-05T04:15:48Z<p>DrummondReed: /* Technologies */ updated link for XDI to Wikipedia</p>
<hr />
<div>This Standard is being developed according to the VRM [[Use Cases|Use Case]] guidelines.<br />
<br />
When possible, elements of the Requirements Model are incorporated directly herein. Otherwise, a link is provided for downloading supporting documents.<br />
<br />
==Status==<br />
[[:Category:Working Draft|Working Draft]]<br />
[[Category:Working Draft]]<br />
<br />
==Schedule==<br />
{| border="1"<br />
|+ '''Proposed Schedule for First Draft'''<br />
! Item !! Who? !! Comment !! 2/20 !! 3/5 !! 3/19 !! 4/2 !! 4/16 !! 4/30 !! 5/14 !! 5/28<br />
|-<br />
! Use Case Description<br />
| J. Andrieu || ||XXX|| || || || || || ||<br />
|-<br />
! Actors<br />
| J. Andrieu || ||XXX|| || || || || || ||<br />
|-<br />
! Roles<br />
| J. Andrieu || ||XXX|| || || || || || ||<br />
|-<br />
! Role Map<br />
| J. Andrieu || || ||XXX|| || || || || ||<br />
|-<br />
! Role Profiles<br />
| J. Andrieu || || ||XXX|| || || || || ||<br />
|-<br />
! High Level Use Cases<br />
| TBD || || || ||XXX|| || || || ||<br />
|-<br />
! Scenarios<br />
| TBD || || || ||XXX|| || || || ||<br />
|-<br />
! Abstract Use Case Narratives<br />
| TBD || || || || ||XXX|| || || ||<br />
|-<br />
! Specific Use Case Narratives<br />
| TBD || || || || ||XXX|| || || ||<br />
|-<br />
! Use Case Diagrams<br />
| TBD || || || || || ||XXX|| || ||<br />
|-<br />
! Use Case Maps<br />
| TBD || || || || || ||XXX|| || ||<br />
|-<br />
! Constraints and Requirements<br />
| TBD || || || || || || ||XXX|| ||<br />
|-<br />
! Technology Review<br />
| TBD || || || || || |||| ||XXX||<br />
|-<br />
! Formats and Protocols<br />
| TBD || || || || || || || || ||XXX<br />
|}<br />
<br />
Target date for announcing first complete draft: VRM Workshop June 2008<br />
<br />
==Description==<br />
The Personal Address Manager Service (PAM Service or PAM) allows anyone to manage their postal address in one place and have it automatically be propagated and used by others, as authorized.<br />
<br />
==Actors==<br />
A list of all Actors supported by the system.<br />
;Individuals: people who use a postal address as a point of contact for receiving correspondence. Also individuals who wish to contact others through a postal address.<br />
;Organizations: entities who rely on a postal address as a way to reach individuals with whom they have existing relationships. Could be a for-profit corporation, sole proprietorship, non-profit, or government agency. Also entities who wish to contact others through a postal address.<br />
<br />
Note that this service is specifically NOT designed to support organizations who rely on postal addresses as a way to reach individuals with whom the want to create a relationship, who we will refer to as "Direct Marketers" for lack of a better term. For this Service, Use Cases which support Direct Marketers are explicitly out of scope.<br />
<br />
==Roles==<br />
;Addressee:Anyone who use a postal address as a point of contact.<br />
;Addressor:Anyone who wants to reach an Addressee at their postal address.<br />
;AddresseeDelegate:Anyone authorized by an Addressee to act on their behalf. ''Specializes Addressee''.<br />
;AddressorDelegate:Anyone authorized by an Addressor to act on their behalf. ''Specializes Addressor''.<br />
;AddressRequester:Individuals or organizations who request a postal address on demand for either immediate or perpetual use. ''Specializes Addressor''.<br />
;AddressSubscriber:Individuals or organizations who subscribe for updates to an individual's address. ''Specializes Addressor''.<br />
;OnlineAddressSubscriber:AddressSubscribers who will receive updates electronically. ''Specializes AddressSubscriber''<br />
;OfflineAddressSubscriber:AddressSubscribers who will receive updates via postal service. ''SpecializesAddressSubscriber''<br />
<br />
==Role Map==<br />
A visual representation of the supported Roles and their relationships to one another.<br />
<br />
[[image:PAM_Role_Map.png]]<br />
<br />
==Profiles==<br />
A detailed description of each Role's expectations, capability, and requirements for the system. Developed to enough detail to distinguish what this particular user needs from the system design.<br />
<br />
===Addressee===<br />
* Average Internet user. Understands websites, email, etc., but doesn't necessarily understand any of the underlying technology (HTML, http, SMTP, etc.). Web friendly but not especially tech savvy.<br />
* Updates address on average once/year, although many users will spend years in between usage.<br />
* Authorizations occur more frequently, so that interface is more familiar.<br />
* Has list of authorized Requestors/Subscribers for address updates in various formats and for various services (DMV, utilities, magazine subscriptions, websites, etc.)<br />
* Could have addresses anywhere on the planet.<br />
<br />
===Addressee Delegate===<br />
* Specializes Addressee<br />
* Authorized by the Addressee to manage authorizations and edit addresses.<br />
* May serve as delegate for multiple addressees<br />
* Can be expected to be moderately more tech-savvy than the average Addressee, but they could have the role just because they are the person in the household with the most geek skills.<br />
<br />
===Addressor===<br />
* Anyone who wants to reach the addressee via their current postal address as managed in the Personal Address manager.<br />
* May be offline or online.<br />
* Selected by virtue of the Addressee's desire to use the Personal Address Manager for this Addressor.<br />
* Could be anywhere on the planet.<br />
<br />
===Addressor Delegate===<br />
* Anyone authorized by an Addressor to act on their behalf.<br />
* Typically this is a shipping or mailing service<br />
* High technical sophistication<br />
* Likely to have automated systems for managing large numbers of Addressees and Addressors.<br />
<br />
===AddressRequester===<br />
* Specializes Addressor<br />
* Internet-savvy entity who wants to make sure they always have the latest postal address for contacting users. Capable of implementing (or using) fairly sophisticated web services<br />
* Manages tens to millions of users... small or large organization or individual.<br />
* Will use the Personal Address Manager for on-demand queries.<br />
* Sometimes handles mailings in-house, sometimes through third-party mailing house.<br />
<br />
===AddressSubscriber===<br />
* Specializes Addressor<br />
* Maintains own database and will not be relying on the Personal Address Manager for on-demand usage.<br />
<br />
===OfflineAddressSubscriber===<br />
* Specialized AddressSubscriber<br />
* No Internet access expected or required.<br />
* Will be reached via postal mail.<br />
<br />
===OnlineAddressSubscriber===<br />
* Specialized AddressSubscriber<br />
* Average Internet User<br />
* Has email address<br />
* May have contact manager software capable of more sophisticated processing<br />
** Or may manually process incoming email updates<br />
<br />
==High Level Use Cases==<br />
A list of all supported use cases in the system, identifying all required use cases by title.<br />
# Addressee Manages Address<br />
## Addressee Creates Address <br />
## Addressee Reviews Address<br />
## Addressee Changes Address<br />
## Addressee Deletes Address<br />
# Addressee Manages Addressors<br />
## Addressee Uploads Addressors<br />
## Addressee Authorizes Addressor<br />
## Addressee Manages Addressor Permissions <br />
## Addressee Deletes Addressor<br />
# Addressee Manages Delegates<br />
## Addressee Authorizes Delegate<br />
## Addressee Unauthorizes Delegate<br />
## Addressee Removes Delegate<br />
# Addressor Manages Delegates<br />
## Addressor Authorizes Delegate<br />
## Addressor Unauthorizes Delegate<br />
## Addressor Removes Delegate<br />
# Addressor discovers Personal Address Manager service for Addressee<br />
# Addressor Requests Authorization<br />
# Delegate requests authorization<br />
# AddressRequester Requests Current Address<br />
# AddressSubscriber Activates Subscription<br />
# AddressSubscriber Deactivates Subscription<br />
# Addressee Accesses Activity Log<br />
# Addressor reports address change<br />
# Addressee acknowledges address change<br />
<br />
==Scenarios==<br />
Prose descriptions of a user's interaction with the system as one example of the Use Case that explains the context, the interaction, and the benefit. Each Use Case requires at least one Scenario.<br />
===Addressee Changes Address===<br />
====Scenario 1====<br />
Bob just got a new job and is moving from Los Angeles to San Francisco and recently selected his new home. He has an address to send to existing vendors. He visits the Change of Address Service and inputs his new address and all of the vendors he wants outgoing notices for (with appropriate account #s and other identifying information). The service confirms the new address, date of the move, and the subscribers it will contact. A few vendors require contact information (they aren't in the system) so Bob provides it. The system sends out the notices and keeps track of delivery so Bob can later verify receipt of the update.<br />
=====Possible Variations=====<br />
Address changes initiated by a visit to a vendor rather than the CoA service? <br />
=====Discussion=====<br />
What is the most efficient and appropriate way for users to manage their account information for each vendor? Telling the DMV (department of Motor Vehicles, the service that provides driver's licenses in California) that John Doe is moving is useless if they don't know the driver's license number as well. Seems like this should be jointly specified by the vendor, when possible. That's easier if the vendor initiates the authorization process (catalyzing the creation of the record in the COA service). However, for real-world, off-line vendors, we probably need a simpler upload or manual entry. What about exports/uploads from bill pay services such as are common at banks or financial management services like Mint or Wesabe? - Joe Andrieu<br />
<br />
==Abstract Use Case Narratives==<br />
An implementation and technology-free chronological ordering of user intention and system responsibilities for a particular use case. Based on one or more specific Scenarios, define the specific, yet technology-free, interactions that are required for the use case. These narratives will be normative, that is, they will ultimately define the requirements of the functioning system.<br />
<br />
===Addressee Changes Address===<br />
{| border="1" cellspacing="0" cellpadding="5" align="center"<br />
! width="50%"|User Intention<br />
! width="50%"|System Responsibility<br />
|- <br />
| 1. Addressee decides to move.<br />
| <br />
|-<br />
| 2. Addressee expresses new address to system (optionally including scheduling information).<br />
| <br />
|-<br />
|<br />
| 3. System assures Addressors get the new address when they need it.<br />
|}<br />
<br />
<br />
WikiQuestion/suggestion: let's set this up as a template.<br />
<br />
==Specific Use Case Narratives==<br />
Implementation-specific sequences of user action and system response for a use case. These narratives will be illustrative, that is, they will show how a particular set of technologies can implement a particular use care--or how a specific set of technologies might require or suggest changes to the use case.<br />
<br />
==Use Case Diagrams==<br />
Both abstract and specific use cases may be diagramed visually to represent the transaction flow between various system components. For abstract use cases, the diagrams will be normative. For specific use cases, they will be illustrative.<br />
==Use Case Maps==<br />
A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.<br />
==Constraints & Requirements==<br />
In addition to responding to specific use cases appropriately, every VRM Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity. <br />
<br />
When mapping out the first set of use cases, it became clear that the a few of the core Use Cases were already substantially met by such online services as Plaxo and LinkedIn, raising the question of what would actually make a Personal Address Manager service VRM-compliant. That led directly to a handful of simple requirements that assure the user and vendors have appropriate access and controls.<br />
<br />
#Address stored independently of any particular service provider<br />
#Addressee can choose who stores canonical source (self-storage ok)<br />
#Data should be in an open format and portable without data or service loss<br />
#Data transfer and use is always under user control<br />
#Addressors can discover the appropriate CoA service for each user<br />
==Technology Review==<br />
Review relevant technology and existing services, highlighting how they inform our development, either by highlighting successful ideas or as examples of what we should avoid.<br />
===Services===<br />
*LinkedIn http://www.linkedin.com<br />
*Plaxo http://www.plaxo.com<br />
*Ryze http://www.ryze.com<br />
===Technologies===<br />
*FOAF http://www.foaf-project.org<br />
*hCard http://microformats.org/wiki/hcard<br />
*OAuth http://www.oauth.net<br />
*OpenID http://openid.net<br />
*XDI http://en.wikipedia.org/wiki/XDI<br />
*CardSpace http://www.microsoft.com/net/cardspace.aspx<br />
<br />
===Organizations/Movements===<br />
*DataPortability.org http://www.dataportability.org<br />
*Microformats http://microformats.org<br />
<br />
==Formats & Protocols==<br />
We will need formats for<br />
#Representing an address (machine readable)<br />
#Presenting an address (human/postal service readable)<br />
#Personal Address Manager metadata<br />
##Address Metadata<br />
##*Address Name<br />
##Authorizations<br />
##Log data<br />
<br />
We will need protocols for<br />
#Authenticating Addressees, Addressors, and delegates<br />
#Authorizing Addressors & Delegates<br />
#Service discovery<br />
#Inbound human services<br />
#*most likely web pages<br />
#Inbound automated services<br />
#Outbound automated services<br />
#*email</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=Blogs&diff=1586Blogs2007-01-22T08:45:39Z<p>DrummondReed: /* Blog posts on VRM */ Drummond Reed</p>
<hr />
<div>== Blog posts on VRM ==<br />
<br />
* Technorati [http://technorati.com/search/VRM VRM search]<br />
* Technorati [http://technorati.com/tag/vrm VRM tag search]<br />
* Gooogle Blogsearch [http://blogsearch.google.com/blogsearch?hl=en&q=vrm&btnG=Search+Blogs VRM search]<br />
* Pierre-Philippe Cormeraie: [http://pierre-philippe.blogspot.com/2007/01/nownow-une-approche-vrm-du-service-svp.html NowNow : une approche VRM du service SVP?]<br />
* Johannes Ernst: [http://netmesh.info/jernst/Digital_Identity/doc-searls-vendor-relationship-management.html Doc Searls: Vendor Relationship Management]<br />
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/07/doc-appears-to-have-an-epiphany/ Doc does appear to have an epiphany]<br />
* Dennis Kennedy: [http://www.denniskennedy.com/blog/2006/10/meme_to_watch_identity_and_vrm.html Meme to Watch: VRM and CRM]<br />
* J.P. Rangaswami: [http://blogs.telegraph.co.uk/technology/shanerichmond/nov06/customereconomics.htm Economics of the Customer]<br />
* Denise Howell: [http://betweenlawyers.corante.com/archives/2006/09/06/vlfs_should_embrace_vrm.php VLFs should embrace VRM]<br />
* Denise Howell: [http://blogs.zdnet.com/Howell/?p=67 Monetizing the urge to recommend]<br />
* Alceste: [http://barking.alceste.ch/?p=44 CRM is dead, long live VRM]<br />
* Phil Windley: [http://www.windley.com/archives/2006/12/vendor_relationship_matters.shtml Vendor Relationship Matters]<br />
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/08/time-to-rethink-the-basis-of-marketing-data/ Time to rethink the basis of marketing data]<br />
* Dave Winer: [http://www.scripting.com/2006/12/05.html#When:9:22:36PM Note to Terry Semel: Get on board with VRM.]<br />
* Bernie Goldbach: [http://irish.typepad.com/irisheyes/2006/12/podleaders_shou.html Podleaders should talk VRM]<br />
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/07/doc-appears-to-have-an-epiphany/ Vendor Relations Management]<br />
* Dennis Kennedy: [http://www.denniskennedy.com/blog/2006/10/meme_to_watch_identity_and_vrm.html Meme to watch: Identity and VRM]<br />
* Harold Gilchrist: [http://www.podcastbrowser.com/blog/?p=284 The Gang says the user is in charge]<br />
* Shane Williamson: [http://shanewilliamson.spaces.live.com/Blog/cns!200D676A335D69C6!1113.entry WARNING: Vendor Relationship Management may make your company successful]<br />
* Rob Kleine: [http://www.gentleye.com/digito-society/?p=662 Doc on VRM or Your CRM Just Exploded!]<br />
* Heinz Wittenbrinks: [http://heinz.typepad.com/lostandfound/2006/12/vrm.html VRM]<br />
* Whitney McNamara: [http://www.blackmailr.com/smr/2006/10/09/lunchtime-musings-what-doc-searls-still-wants/ What Doc Searls (still) Wants...]<br />
* Jeremie Miller: [http://jeremie.com/blog/index.php?entry=entry061211-160116 What does the R mean in VRM?]<br />
* Britt Blaser: [http://www.blaserco.com/blogs/?p=42 VRM Entry Point]<br />
* Gave Wachob: [http://blog.wachob.com/2006/12/doc_searls_has_.html Candidate/Campaign Relationship Management]<br />
* Sean Coon: [http://www.seancoon.org/2006/12/doc_and_vrm.html Doc on VRM]<br />
* Ethan Zuckerman: [http://www.ethanzuckerman.com/blog/?p=1145 Doc Searls, live, not in the ceiling]<br />
* Joe Andrieu : [http://blog.joeandrieu.com/2006/12/13/incredible-inevitable-identity/ Incredible Inevitable Identity]<br />
* Joe Andrieu : [http://blog.joeandrieu.com/2006/12/03/internet-identity-reputation-networks-and-more/ Internet Identity -&gt; Reputation Networks and more]<br />
* Joe Andrieu : [http://blog.joeandrieu.com/2006/11/21/vrm-make-a-gesture-create-a-market/ VRM: Make a gesture, create a market]<br />
* SteveX: [http://blog.stevex.net/index.php/2006/12/13/vendor-relationship-management/ Vendor Relationship Management]<br />
* ChrisKelly.org: [http://www.chriskelley.org/?p=401 Data Exchange]<br />
* Christopher Carfi: [http://www.socialcustomer.com/2006/12/vrm_vendor_rela.html VRM - Vendor Relationship Management]<br />
* Paul Trevithick: [http://sp.typepad.com/blog/2006/12/docs_vrm_projec.html Doc's VRM Project]<br />
* Denise Howell: [http://blogs.zdnet.com/Howell/?p=69 Vendor Relationship Management and the Support Economy]<br />
* RussDev Blog: [http://www.russdev.com/wp-blog/2006/12/16/suppliers-vendors-vrm-is-future/ Suppliers (Vendors) - VRM Is Future.]<br />
* Joe Andrieu: [http://blog.joeandrieu.com/2006/12/18/the-r-in-vrm/ The 'R' in VRM]<br />
* Deb Schultz: [http://www.deborahschultz.com/deblog/advertising_promotion/index.html Banner ads and PV - I wish they would just die already ]<br />
* Colin Henderson: [http://bankwatch.wordpress.com/2007/01/02/microformats-as-information-brokers-the-intelligent-agents-to-support-vrm/ Microformats as information brokers - the intelligent agents to support VRM ]<br />
* Christopher Carfi: [http://www.socialcustomer.com/2007/01/more_on_vendor_.html That Nagging Voice of the Human Customer]<br />
* Drummond Reed: [http://www.equalsdrummond.name/?p=91 VRM: VROOOM!]<br />
* Pierre-Philippe Cormeraie: [http://pierre-philippe.blogspot.com/2007/01/vrm-crm-20.html VRM = CRM 2.0?]<br />
* Colin Henderson: [http://bankwatch.wordpress.com/2007/01/05/microformats-as-information-brokers-revisited/ Microformats as information brokers - revisited]<br />
* USVO: [http://blog.usvo.com/?p=35 The Customer Revolt]<br />
* Joe Andrieu: [http://blog.joeandrieu.com/2007/01/19/shopatron-redefines-vendor-relationships/ Shopatron redefines Vendor Relationships]<br />
<br />
== Doc Searls' posts on VRM (includes [http://www.linuxjournal.com/blog/800285 Linux Journal essays)] ==<br />
<br />
* [http://doc.weblogs.com/2006/11/20#vrmInquiry VRM Inquiry]<br />
* [http://doc.weblogs.com/2006/11/16#thisIsWhyIWantVrm This is why I want VRM]<br />
* [http://doc.weblogs.com/2006/11/19#turningFunnelsIntoMegaphones Turning funnels into megaphones]<br />
* [http://doc.weblogs.com/2006/10/08#howVrmHelpsCrm How VRM helps CRM]<br />
* [http://www.linuxjournal.com/node/1000137 Let's go bust some silos]<br />
* [http://www.linuxjournal.com/node/1000089 Turning the world i-side out]<br />
* [http://www.linuxjournal.com/node/1000035 The Intention Economy]<br />
* [http://doc.weblogs.com/2006/11/27#abuseCaseForVrm Abuse case for VRM]<br />
* [http://doc.weblogs.com/2006/12/07#relations Relations]<br />
* [http://www.linuxjournal.com/node/1000153 Can we relate?]</div>DrummondReedhttps://cyber.harvard.edu/projectvrm/?title=VRM_Meeting&diff=1514VRM Meeting2006-12-30T23:48:56Z<p>DrummondReed: added Drummond</p>
<hr />
<div>This is a VRM Developers Meeting. Not a conference. <br />
<br />
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.<br />
<br />
The date is January 25 in Redwood City. Details will be up here shortly.<br />
<br />
<br />
Meanwhile this page is also where we sign up. Add your name and relevant links to the list.<br />
<br />
List of attendees:<br />
<br />
* [http://cyber.law.harvard.edu/home/doc_searls Doc Searls]<br />
* http://lid.netmesh.org/images/openid-relying-party-authenticated.gif [http://netmesh.info/jernst Johannes Ernst]<br />
* [http://blog.joeandrieu.com Joe Andrieu]<br />
* [http://www.deborahschultz.com Deborah Schultz]<br />
* [http://xri.net/=drummond.reed Drummond Reed]</div>DrummondReed