https://cyber.harvard.edu/projectvrm/api.php?action=feedcontributions&user=Joe.andrieu&feedformat=atomProject VRM - User contributions [en]2024-03-29T12:49:46ZUser contributionsMediaWiki 1.39.5https://cyber.harvard.edu/projectvrm/?title=VRM_CRM_2010_Food_For_Thought_Dinners&diff=4459VRM CRM 2010 Food For Thought Dinners2010-08-26T20:16:04Z<p>Joe.andrieu: /* Grafton Street */</p>
<hr />
<div>==Dinners==<br />
Each dinner has a topic and a topic leader. Ideally, a brief report will come out of the dinner, and get written down below.<br />
<br />
Food for thought dinners: Thursday, August 26th at 7pm<br />
<br />
All dinners at 7PM, reservations held under "Berkman"<br />
<br />
<br />
<br />
===Spice===<br />
24 Holyoke Street, Cambridge, MA 02138<br />
Tel: (617) 868-9560 <br />
http://www.spicethaicuisine.com/restaurant/start.asp<br />
http://maps.google.com/maps?client=safari&rls=en&oe=UTF-8&um=1&ie=UTF-8&q=24+Holyoke+Street,+Cambridge,+MA+02138&fb=1&gl=us&hnear=Cambridge,+MA&cid=0,0,13983633003503058163&ei=QaF2TNHYIML6lwf1gLnwCg&sa=X&oi=local_result&ct=image&resnum=1&ved=0CBMQnwIwAA<br />
<br />
Topic: Government Relationship Management/GRM<br />
<br />
Participants:<br />
#_Topic/leader: Britt Blaser; http://NewGov.us<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Casablanca===<br />
40 Brattle Street, Cambridge, MA 02138<br />
Tel: (617) 868-9560<br />
http://www.casablanca-restaurant.com/<br />
<br />
Topic: Legal and Business- the VRM view<br />
<br />
Participants:<br />
#_Topic leader:Renee Lloyd<br />
#_Joyce Searls<br />
#_Tim Christin<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Daedalus===<br />
45 1/2 Mount Auburn St.<br />
Cambridge, Ma 02138<br />
617-349-0071<br />
http://www.daedalusharvardsquare.com/<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Grafton Street===<br />
1230 Massachusetts Avenue, Cambridge, MA 02138<br />
617.497.0400<br />
http://www.graftonstreetcambridge.com/<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader: Shopping Data & Personal RFP's / Tara Hunt (Shwowp)<br />
#_Uwe Hook (www.bateshook.com)<br />
#_Cassandra Girard<br />
#_Joe Andrieu<br />
#_Iain Henderson<br />
#_Terry Taciuk<br />
#_Charles Andres<br />
#_Adrian Gropper<br />
<br />
<br />
Wait list:<br />
#_Pete Baldwin<br />
#_John McKean<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Legal Seafoods===<br />
20 University Road<br />
Cambridge, MA 02138<br />
617-491-9400<br />
http://www.legalseafoods.com/restaurants/cambridge-charles-square<br />
<br />
<br />
<br />
Topic/Participants: Automating VRM/Phil Windley<br />
#_Craig Burton<br />
#_Sean Bohan<br />
#_Jonathan Yarmis<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Russell House Tavern===<br />
14 JFK Street, Cambridge, MA 02138<br />
617 500 3055<br />
http://www.russellhousecambridge.com/<br />
Confirmation #: 1484807496 (Berkman)<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Chang Sho Restaurant===<br />
Chang Sho Restaurant<br />
1712 Massachusetts Avenue, Cambridge, MA 02138-1804<br />
(617) 547-6565<br />
(straight up Mass Ave on the left)<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/Leader: Doc Searls /My vacation photos, (not really) Open topic- group decides<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Dolphin Seafood===<br />
1105 Massachusetts Ave. Cambridge, MA 02138<br />
617.661.2937<br />
http://www.dolphinseafood.com/<br />
<br />
<br />
Participants:<br />
<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM_CRM_2010_Food_For_Thought_Dinners&diff=4437VRM CRM 2010 Food For Thought Dinners2010-08-26T15:55:03Z<p>Joe.andrieu: /* Grafton Street */</p>
<hr />
<div>==Dinners==<br />
Each dinner has a topic and a topic leader. Ideally, a brief report will come out of the dinner, and get written down below.<br />
<br />
Food for thought dinners: Thursday, August 26th at 7pm<br />
<br />
All dinners at 7PM, reservations held under "Berkman"<br />
<br />
<br />
<br />
===Spice===<br />
24 Holyoke Street, Cambridge, MA 02138<br />
Tel: (617) 868-9560 <br />
http://www.spicethaicuisine.com/restaurant/start.asp<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Casablanca===<br />
40 Brattle Street, Cambridge, MA 02138<br />
Tel: (617) 868-9560<br />
http://www.casablanca-restaurant.com/<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Daedalus===<br />
45 1/2 Mount Auburn St.<br />
Cambridge, Ma 02138<br />
617-349-0071<br />
http://www.daedalusharvardsquare.com/<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Grafton Street===<br />
1230 Massachusetts Avenue, Cambridge, MA 02138<br />
617.497.0400<br />
http://www.graftonstreetcambridge.com/<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader: Shopping Data & Personal RFP's / Tara Hunt (Shwowp)<br />
#_Uwe Hook (www.bateshook.com)<br />
#_Cassandra Girard<br />
#_Joe Andrieu<br />
#_Iain Henderson<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Legal Seafoods===<br />
20 University Road<br />
Cambridge, MA 02138<br />
617-491-9400<br />
http://www.legalseafoods.com/restaurants/cambridge-charles-square<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Russell House Tavern===<br />
14 JFK Street, Cambridge, MA 02138<br />
617 500 3055<br />
http://www.russellhousecambridge.com/<br />
Confirmation #: 1484807496 (Berkman)<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
Wait list:<br />
#_<br />
#_<br />
<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Chang Sho Restaurant===<br />
Chang Sho Restaurant<br />
1712 Massachusetts Avenue, Cambridge, MA 02138-1804<br />
(617) 547-6565<br />
(straight up Mass Ave on the left)<br />
<br />
<br />
<br />
Participants:<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:<br />
<br />
----<br />
<br />
===Dolphin Seafood===<br />
1105 Massachusetts Ave. Cambridge, MA 02138<br />
617.661.2937<br />
http://www.dolphinseafood.com/<br />
<br />
<br />
Participants:<br />
<br />
#_Topic/leader:<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
<br />
Wait list:<br />
<br />
#_<br />
#_<br />
#_<br />
<br />
<br />
Report:</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4392Main Page2010-08-10T09:39:33Z<p>Joe.andrieu: Reverted edits by Hill9 (Talk) to last version by Joe.andrieu</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 />
*[[r-button]]<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 />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
=== Past Events ===<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>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4390Main Page2010-08-09T05:43:39Z<p>Joe.andrieu: Reverted edits by Moore (Talk) to last version by Dsearls</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 />
*[[r-button]]<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 />
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge MA<br />
<br />
=== Past Events ===<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>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Compliance_Committee&diff=4388Compliance Committee2010-08-07T03:08:19Z<p>Joe.andrieu: Undo revision 4386 by Jessica (Talk)</p>
<hr />
<div>The objective of the Compliance Committee is to <br />
'''Create and oversee VRM compliance program'''<br />
<br />
The background to this proposal is that we suspect that, over time, applications or organisations may claim to be 'VRM' practitioners, but not in fact be so (i.e. they do not comply with one or more of the core principles). As such, we wish to have ways and means of limiting the impact of these false claims.<br />
<br />
Our proposal is that:<br />
<br />
1) We develop a series of statements of good/ best practice in the areas that define VRM (see below *), build those into a process through which organisations can be assessed on a five point scale. Each statement would have to be 'owned' by a VRM expert and would include:<br />
<br />
- the statement of good practice itself (e.g. data within a VRM application will be portable).<br />
<br />
- 5 answer options (ranging from 'never heard of this practice = 0 to 'yes we do this and can prove it' = 100%)<br />
<br />
- detailed compliance text explaining the practice and issues around it<br />
<br />
* VRM practices could be clustered, for example, into:<br />
<br />
<br />
- Individual (user)-centrism<br />
<br />
<br />
- ability to generate a 'win-win' for buyer and seller<br />
<br />
<br />
- approach to personal information (portability etc)<br />
<br />
<br />
- use of open standards<br />
<br />
<br />
- overall transparency of service offering<br />
<br />
<br />
This would allow a 'VRM index' score to be generated at overall level, for each subject area, and for each individual practice. These scores then drive compliance (e.g. scores below 35% are non-compliant, scores below 65% are 'pending and scores 65 and above are compliant). They also drive benchmarking, i.e. to what extent is my application VRM compliant, which in turn drives improvement activity and the consulting/ services activities that go along with that. <br />
<br />
The score also becomes a published reputation with a reputation/ compliance mark provided. We'd run a white list (VRM compliant) and a black list (were compliant but are no longer so) with the bit in between being 'pending assessment'.<br />
<br />
<br />
2) We establish an entity that owns the VRM Compliance and Benchmarking Program, which could be Berkman, could be hosted by the Liberty Alliance or could be a new entity. This is a key step and obviously feeds into the VRM Organisation work stream.<br />
<br />
<br />
3) We make the VRM Compliance/ Benchmarking assessment available in two forms. <br />
<br />
<br />
a) a face to face assessment of large organisations which we'd outsource to organisations which specialise in assessing and from which the entity above would earn revenues (a % of the assessment charge).<br />
<br />
<br />
b) a 'lite touch' self-assessment variant typically for smaller businesses/ non-profits.<br />
<br />
<br />
4) Over time, and as VRM applications and standards emerge, we develop a complementary technical compliance program in which applications are physically tested to ensure compliance to a specific, pre-agreed technical standard.<br />
<br />
<br />
Hope that helps give a flavour of what we have in mind.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4252Main Page2010-01-16T10:11:24Z<p>Joe.andrieu: cleared out gunk left from much older spam from Crypto18</p>
<hr />
<div>== About VRM ==<br />
<br />
VRM, or Vendor Relationship Management, is the reciprocal of CRM or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]. It provides customers with tools for engaging with vendors in ways that work for both parties.<br />
<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 &#151; in ways that don't require the former to "lock in" the latter.<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 />
For VRM to work, vendors must have reason to value it, and customers must have reasons to invest the necessary time, effort and attention to making it work. Providing those reasons to both sides is the primary challenge for VRM.<br />
<br />
== Project VRM ==<br />
<br />
[http://projectvrm.org Project VRM] is a community-driven effort, led by [http://cyber.law.harvard.edu The Berkman Center for Internet and Society] at Harvard University, to support the creation and building of VRM tools. ProjectVRM carries forward thinking by various parties around the world. These include ideas brought up by Doc Searls and his fellow [http://cluetrain.com Cluetrain Manifesto] authors, work of the [http://www.rightsideup.net/ Buyer Centric Commerce Forum] and other allied efforts in the U.K., and many sessions at Internet Identity Workshops.<br />
<br />
ProjectVRM is headed by [http://cyber.law.harvard.edu/people/dsearls Doc Searls], a fellow with the Berkman Center.<br />
<br />
In addition to this wiki, ProjectVRM has [http://blogs.law.harvard.edu/vrm a blog] and a [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list]. <br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM Principles ==<br />
<br />
#Relationships are voluntary.<br />
#Customers are born free and independent of vendors.<br />
#Customers control their own data. They can share data selectively and control the terms of its use.<br />
#Customers are points of integration and origination for their own data.<br />
#Customers can assert their own terms of engagement and service. <br />
#Customers are free to express their demands and intentions outside any companyâs control.<br />
<br />
These can all be summed up in the statement ''Free customers are more valuable than captive ones''.<br />
<br />
In a broader way, the same should be true of individuals relating to organizations. With VRM, however, our primary focus is on customer relationships with vendors, or sellers. <br />
<br />
== VRM Goals ==<br />
<br />
#Define and advocate a clear vision for a VRM world<br />
#Ensure the development and publishing of open standards and specifications for VRM services<br />
#Create a lightweight and effective organisational structure<br />
#Drive VRM usage<br />
#Create and oversee VRM compliance program<br />
<br />
== VRM Current Topics ==<br />
<br />
This is a catch-all where we can point both to ongoing conversations and current development work. These include (but are hardly limited to)...<br />
<br />
*[[Media Logging]]<br />
*[[Listen Log]] (the general topic) and [[ListenLog]] (the development project0<br />
*[[PayChoice]]<br />
*[[Personal RFP]]<br />
*[[FCRA: Access to credit data]]<br />
<br />
== VRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
<br />
== Allied Efforts ==<br />
<br />
*[[The Mine! Project]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://publicradiotuner.org Public Radio Tuner]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
<br />
== Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
<br />
* [[VRM FAQ]]<br />
<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
* Project VRM [[committees]]<br />
<br />
* VRM and -related [[events]]<br />
<br />
* VRM [[Initiatives]]<br />
<br />
* VRM [[Principles]]<br />
<br />
* VRM [[Process]]<br />
<br />
* VRM [[scenarios]]<br />
<br />
* VRM [[technology]]<br />
<br />
* VRM coverage in [[blogs]]<br />
<br />
* VRM discussion in [[VRM discussion in podcasts | podcasts]]<br />
<br />
* [[Questions raised]] by VRM<br />
<br />
* [[VRMcompanies]] &#151; A list of VRM or VRMlike comnpanies <br />
<br />
* [[Expressions of Relationships]] (notes from VRM meeting)<br />
<br />
* [[Random Notes from Jan 25th VRM Developers Meeting]] (stream of consciousness / ears and brain to fingertips and keyboard)<br />
<br />
* [[Website planning]]<br />
<br />
* Other [[related efforts]]<br />
<br />
Conference Call archive and audio links have been moved to the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
[[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
<br />
[[VRooM Boston 2009]] took place on 12-13 October 2009<br />
<br />
[http://vrmhub.pbwiki.com/ VRM Hub] Monthly Meetings in London<br />
<br />
[[VRM2008]] took place in Munich on 21/22 April 2008<br />
<br />
[[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[[VRM at SXSW 2009]] March 2009, Austin, TX<br />
<br />
[[VRM West Coast Workshop 2009]] May 15-16, Palo Alto, CA<br />
<br />
[[VRM East Coast Workshop 2009]] 12-13 October at Harvard University<br />
<br />
== Join Us! ==<br />
<br />
Looking to contribute to the Project VRM Wiki? Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list], send an email to the owners, and we'll get you up and running!</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Main_Page&diff=4251Main Page2010-01-16T10:05:16Z<p>Joe.andrieu: Reverted edits by Antakyanet (Talk) to last version by Andromeda</p>
<hr />
<div>== About VRM ==<br />
<br />
VRM, or Vendor Relationship Management, is the reciprocal of CRM or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]. It provides customers with tools for engaging with vendors in ways that work for both parties.<br />
<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 &#151; in ways that don't require the former to "lock in" the latter.<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 />
For VRM to work, vendors must have reason to value it, and customers must have reasons to invest the necessary time, effort and attention to making it work. Providing those reasons to both sides is the primary challenge for VRM.<br />
<br />
== Project VRM ==<br />
<br />
[http://projectvrm.org Project VRM] is a community-driven effort, led by [http://cyber.law.harvard.edu The Berkman Center for Internet and Society] at Harvard University, to support the creation and building of VRM tools. ProjectVRM carries forward thinking by various parties around the world. These include ideas brought up by Doc Searls and his fellow [http://cluetrain.com Cluetrain Manifesto] authors, work of the [http://www.rightsideup.net/ Buyer Centric Commerce Forum] and other allied efforts in the U.K., and many sessions at Internet Identity Workshops.<br />
<br />
ProjectVRM is headed by [http://cyber.law.harvard.edu/people/dsearls Doc Searls], a fellow with the Berkman Center.<br />
<br />
In addition to this wiki, ProjectVRM has [http://blogs.law.harvard.edu/vrm a blog] and a [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list]. <br />
<br />
Read more about ProjectVRM on the [[About | About Page]].<br />
<br />
== VRM Principles ==<br />
<br />
#Relationships are voluntary.<br />
#Customers are born free and independent of vendors.<br />
#Customers control their own data. They can share data selectively and control the terms of its use.<br />
#Customers are points of integration and origination for their own data.<br />
#Customers can assert their own terms of engagement and service. <br />
#Customers are free to express their demands and intentions outside any companyâs control.<br />
<br />
These can all be summed up in the statement ''Free customers are more valuable than captive ones''.<br />
<br />
In a broader way, the same should be true of individuals relating to organizations. With VRM, however, our primary focus is on customer relationships with vendors, or sellers. <br />
<br />
== VRM Goals ==<br />
<br />
#Define and advocate a clear vision for a VRM world<br />
#Ensure the development and publishing of open standards and specifications for VRM services<br />
#Create a lightweight and effective organisational structure<br />
#Drive VRM usage<br />
#Create and oversee VRM compliance program<br />
<br />
== VRM Current Topics ==<br />
<br />
This is a catch-all where we can point both to ongoing conversations and current development work. These include (but are hardly limited to)...<br />
<br />
*[[Media Logging]]<br />
*[[Listen Log]] (the general topic) and [[ListenLog]] (the development project0<br />
*[[PayChoice]]<br />
*[[Personal RFP]]<br />
*[[FCRA: Access to credit data]]<br />
<br />
== VRM Committees ==<br />
<br />
*[[Vision Committee]]<br />
*[[Marketing Committee]]<br />
*[[Standards Committee]]<br />
*[[Organization Committee]]<br />
*[[Usage Committee]]<br />
*[[Compliance Committee]]<br />
<br />
== Allied Efforts ==<br />
<br />
*[[The Mine! Project]]<br />
*[http://mydex.org/ MyDex]<br />
*[http://www.vrmhub.net VRM Hub]<br />
*[http://www.vrmlabs.net VRM Labs]<br />
*[http://publicradiotuner.org Public Radio Tuner]<br />
*[http://www.switchbook.com/ SwitchBook]<br />
<br />
== Resources ==<br />
<br />
* ProjectVRM [[mailing list]]<br />
<br />
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]<br />
<br />
* [[VRM FAQ]]<br />
<br />
* VRM [Twitter stream http://twitter.com/vrm]<br />
<br />
* Project VRM [[committees]]<br />
<br />
* VRM and -related [[events]]<br />
<br />
* VRM [[Initiatives]]<br />
<br />
* VRM [[Principles]]<br />
<br />
* VRM [[Process]]<br />
<br />
* VRM [[scenarios]]<br />
<br />
* VRM [[technology]]<br />
<br />
* VRM coverage in [[blogs]]<br />
<br />
* VRM discussion in [[VRM discussion in podcasts | podcasts]]<br />
<br />
* [[Questions raised]] by VRM<br />
<br />
* [[VRMcompanies]] &#151; A list of VRM or VRMlike comnpanies <br />
<br />
* [[Expressions of Relationships]] (notes from VRM meeting)<br />
<br />
* [[Random Notes from Jan 25th VRM Developers Meeting]] (stream of consciousness / ears and brain to fingertips and keyboard)<br />
<br />
* [[Website planning]]<br />
<br />
* Other [[related efforts]]<br />
<br />
Conference Call archive and audio links have been moved to the [[Project_VRM:Community_Portal | Community Portal]] page.<br />
<br />
== VRM Events ==<br />
<br />
[[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA<br />
<br />
[[VRooM Boston 2009]] took place on 12-13 October 2009<br />
<br />
[http://vrmhub.pbwiki.com/ VRM Hub] Monthly Meetings in London<br />
<br />
[[VRM2008]] took place in Munich on 21/22 April 2008<br />
<br />
[[VRM Workshop 2008]] took place in July 2008 at Harvard University<br />
<br />
[[VRM at SXSW 2009]] March 2009, Austin, TX<br />
<br />
[[VRM West Coast Workshop 2009]] May 15-16, Palo Alto, CA<br />
<br />
[[VRM East Coast Workshop 2009]] 12-13 October at Harvard University<br />
<br />
== Join Us! ==<br />
<br />
Looking to contribute to the Project VRM Wiki? Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list], send an email to the owners, and we'll get you up and running!...........[http://www.colonialutah.com .][http://www.diacetate.com .][http://www.resortquestmortgage.com .][http://www.dandaria.info .][http://www.qualitytopsite.com .][http://www.cg286.com .][http://www.wallpapers-nintendo.net .][http://www.wahyupromo.com .][http://www.idahoagbell.org .][http://www.farnsworthonbroadway.net .][http://www.qzepc.com .][http://www.888flik.com .][http://www.woodburycinema.com .][http://www.forexfee.com .][http://www.legithosting.com .][http://www.weightlossdietinformation.com .][http://wwct.net .][http://www.comparingfashion.com .][http://www.dontclickit.net .][http://www.funnycolour.com .][http://www.wellshs.org .][http://www.bestclickbankebook.com .][http://www.profitfromclickbank.com .][http://www.hotmailmember.com .][http://www.xmlinsider.com .][http://www.olimpiaclub.info .][http://www.vanguardtaxes.com .][http://www.thedailydowner.com .][http://www.dreamcreature.com .][http://www.people-finder.dandaria.info .][http://www.affiliate-people-search.ws .].........</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Project_VRM_talk:Community_Portal&diff=4250Project VRM talk:Community Portal2010-01-16T10:05:14Z<p>Joe.andrieu: Reverted edits by Antakyanet (Talk) to last version by Joe.andrieu</p>
<hr />
<div>hi, my company is http://www.dataforcecrm.com. We are an on demand VRM that does what this site describes in the real world with customers like Intel. <br />
<br />
Jim</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Project_VRM:Community_Portal&diff=4249Project VRM:Community Portal2010-01-16T10:05:14Z<p>Joe.andrieu: Reverted edits by Antakyanet (Talk) to last version by Killspam</p>
<hr />
<div>[[November 11 2009 Conference Call]]<br />
<br />
[[September 30 2009 Conference Call]]<br />
<br />
[[September 02 2009 Conference Call]]<br />
<br />
==Prior Conference Calls==<br />
[[conference call archive]]<br />
<br />
[[:Category:conference call]]<br />
[http://www.sexalemi.org sikis izle]<br />
[http://www.pornositeleri.net porno izle]<br />
[http://www.sexalemi.org sex izle]<br />
[http://www.sexalemi.org sikis]<br />
[http://www.cinsel.name sikis izle]<br />
[http://www.cinsel.name.tr sikis]<br />
[http://www.hiphopalemi.net hiphop]<br />
[http://www.kelebekchat.net kelebek chat]<br />
[http://www.kelebeksohbet.org kelebek sohbet]<br />
[http://www.chatsohbet.org chat sohbet]<br />
[http://www.siberchat.net chat]<br />
[http://www.pornositeleri.net porno]<br />
[http://www.pornositeleri.org porno izle]<br />
[http://www.pornositeleri.org porno siteleri]<br />
[http://www.sexpormok.net sex]<br />
[http://www.mynetsohbet.net mynet sohbet]<br />
[http://www.hiphopalemi.net chat]<br />
[http://www.hiphopalemi.net rap]<br />
[http://www.kelebekchat.net kelebek]<br />
[http://www.gaychat.gen.tr gay chat]<br />
[http://www.cinsel-sohbet.com cinsel sohbet]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM2008_Higgens/OpenIDSAML_InfoCards_as_VRM_enabler&diff=4183VRM2008 Higgens/OpenIDSAML InfoCards as VRM enabler2009-12-09T18:52:33Z<p>Joe.andrieu: Reverted edits by Sivas400 (Talk) to last version by KruGer</p>
<hr />
<div>[http://www.sexalemi.org sikis izle]<br />
[http://www.pornositeleri.net porno izle]<br />
[http://www.sexalemi.org sex izle]<br />
[http://www.sexalemi.org sikis]<br />
[http://www.cinsel.name sikis izle]<br />
[http://www.cinsel.name.tr sikis]<br />
[http://www.hiphopalemi.net hiphop]<br />
[http://www.kelebekchat.net kelebek chat]<br />
[http://www.kelebeksohbet.org kelebek sohbet]<br />
[http://www.chatsohbet.org chat sohbet]<br />
[http://www.siberchat.net chat]<br />
[http://www.pornositeleri.net porno]<br />
[http://www.pornositeleri.org porno izle]<br />
[http://www.pornositeleri.org porno siteleri]<br />
[http://www.sexpormok.net sex]<br />
[http://www.mynetsohbet.net mynet sohbet]<br />
[http://www.hiphopalemi.net chat]<br />
[http://www.hiphopalemi.net rap]<br />
[http://www.kelebekchat.net kelebek]<br />
[http://www.gaychat.gen.tr gay chat]<br />
[http://www.sempatim.net seviÅme]<br />
[http://www.cinsel-sohbet.com cinsel sohbet]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=The_Matrix_(Blue_Pill)&diff=4182The Matrix (Blue Pill)2009-12-09T18:52:32Z<p>Joe.andrieu: Reverted edits by Sivas400 (Talk) to last version by Kelebek</p>
<hr />
<div>'''VRM Scenarios - "The Matrix (Blue Pill)"'''<br />
<br />
http://www.socialcustomer.com/images/bluepill.jpg<br />
<br />
Vendors control production, allocation and distribution, and at the same time understand that a connected customer is a lifetime customer. Supply chain models such as [http://www.inventoryops.com/ConsignmentInventory.htm vendor managed inventory and consignments] are used. The vendor controls what purchase options are given to the customer, and realizes that he must be equitable, or the customer will terminate the relationship. The vendor has perfect information on the behavior of his customers, including purchase history. Vendors use this information to continually refine and model the selection and quantity of goods and services made available to each customer to not only maximize profits, but also to ensure continued access to that customer. Customers select their vendors based on the belief that they will have an ongoing relationship with the vendors they choose, and give them feedback as to what they'd like to see.<br />
[http://www.sexalemi.org sikis izle]<br />
[http://www.pornositeleri.net porno izle]<br />
[http://www.sexalemi.org sex izle]<br />
[http://www.sexalemi.org sikis]<br />
[http://www.cinsel.name sikis izle]<br />
[http://www.cinsel.name.tr sikis]<br />
[http://www.hiphopalemi.net hiphop]<br />
[http://www.kelebekchat.net kelebek chat]<br />
[http://www.kelebeksohbet.org kelebek sohbet]<br />
[http://www.chatsohbet.org chat sohbet]<br />
[http://www.siberchat.net chat]<br />
[http://www.pornositeleri.net porno]<br />
[http://www.pornositeleri.org porno izle]<br />
[http://www.pornositeleri.org porno siteleri]<br />
[http://www.sexpormok.net sex]<br />
[http://www.mynetsohbet.net mynet sohbet]<br />
[http://www.hiphopalemi.net chat]<br />
[http://www.hiphopalemi.net rap]<br />
[http://www.kelebekchat.net kelebek]<br />
[http://www.gaychat.gen.tr gay chat]<br />
[http://www.cinsel-sohbet.com cinsel sohbet]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Project_VRM:Community_Portal&diff=4181Project VRM:Community Portal2009-12-09T18:52:31Z<p>Joe.andrieu: Reverted edits by Sivas400 (Talk) to last version by Kelebek</p>
<hr />
<div>[[November 11 2009 Conference Call]]<br />
<br />
[[September 30 2009 Conference Call]]<br />
<br />
[[September 02 2009 Conference Call]]<br />
<br />
==Prior Conference Calls==<br />
[[conference call archive]]<br />
<br />
[[:Category:conference call]]<br />
[http://www.sexalemi.org sikis izle]<br />
[http://www.pornositeleri.net porno izle]<br />
[http://www.sexalemi.org sex izle]<br />
[http://www.sexalemi.org sikis]<br />
[http://www.cinsel.name sikis izle]<br />
[http://www.cinsel.name.tr sikis]<br />
[http://www.hiphopalemi.net hiphop]<br />
[http://www.kelebekchat.net kelebek chat]<br />
[http://www.kelebeksohbet.org kelebek sohbet]<br />
[http://www.chatsohbet.org chat sohbet]<br />
[http://www.siberchat.net chat]<br />
[http://www.pornositeleri.net porno]<br />
[http://www.pornositeleri.org porno izle]<br />
[http://www.pornositeleri.org porno siteleri]<br />
[http://www.sexpormok.net sex]<br />
[http://www.mynetsohbet.net mynet sohbet]<br />
[http://www.hiphopalemi.net chat]<br />
[http://www.hiphopalemi.net rap]<br />
[http://www.kelebekchat.net kelebek]<br />
[http://www.gaychat.gen.tr gay chat]<br />
[http://www.cinsel-sohbet.com cinsel sohbet]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=EmanciPay&diff=4180EmanciPay2009-12-09T18:52:31Z<p>Joe.andrieu: Reverted edits by Sivas400 (Talk) to last version by Joe.andrieu</p>
<hr />
<div>EmanciPay is a new way for media to make money. It's a choosing system -- one by which readers, listeners and viewers can easily choose to pay whatever they like, whenever they like, for the media goods they use -- and to do that on their own terms, and not just those of media suppliers' arcane systems.<br />
<br />
The idea is to build a new marketplace for media â one where supply and demand can relate, converse and transact business on mutually beneficial terms, rather than only on terms provided by thousands of different silo'd systems, each serving to hold the customer captive, and causing much inconvenience and friction in the process.<br />
<br />
EmanciPay is a breed of VRM, or Vendor Relationship Management. VRM is the reciprocal of CRM or Customer Relationship Management. VRM provides customers with tools for engaging with vendors in ways that work for both parties. EmanciPay is one of those tools. Or a set of them.<br />
<br />
=== Background ===<br />
We now live in a media environment where goods previously sold directly or paid for by advertising are freely available and shared widely over the Internet. A number of factors contribute to a business and social conundrum for suppliers of those goods:<br />
* Easy copying and sharing makes the goods freely available at growing ease and convenience.<br />
* Copying and sharing is so widespread and common that punishment for copyright and other usage violations touches only a small minority of offenders, and has proven to be a losing proposition.<br />
What the marketplace requires are new business and social contracts that ease payment and stigmatize non-payment for media goods. The friction involved in voluntary payment is still high, even on the Web, where one must go through complex forms even to make simple payments. There is no common and easy way either to keep track of what media (free or otherwise) we consume (see [[Media Logging]]), to determine what it might be worth, and to pay for it easily and in standard ways -- to many different suppliers. (Again, each supplier has its own system for accepting payments.)<br />
<br />
EmanciPay will create a &quot;buy button&quot;-simple payment system to allow readers, listeners and viewers to pay whatever they like, at their discretion, for whatever media products they use. For too many media the traditional business models -- subscriptions, newsstand sales, advertising and underwriting -- are not sufficient. (Especially in the current economic environment, which is akin to an earthquake that won't stop.) Nor do they support full participation and involvement with their users.<br />
EmanciPay differs from other payment models (subscriptions, newsstand, tip jars) by allowing the customer to pay any amount they please, when they please, with minimum friction -- and with full choice about what they disclose about themselves. <br />
<br />
EmanciPay will also support credit for referrals, requests for service, feedback and other relationship support mechanisms, all at the control of the user. For example, EmanciPay can provide quick and easy ways for listeners to pay for public radio broadcasts or podcasts, for readers to pay for otherwise &quot;free&quot; papers or blogs, and paid request for stories or programs to be expressed and aggregated, without requiring the customer to disclose unnecessary private information, to become a &quot;member&quot;. This will scaffold real relationships between buyers and sellers, and for supporting journalists covering what Jake Shapiro calls &quot;microbeats.&quot; It will also give deeper meaning to "membership" in non-profits. (Under the current system, "membership" means putting one's name on a pitch list for future contributions, and not much more than that.)<br />
<br />
EmanciPay will also connect the sellers' CRM (Customer Relationship Management) systems with customers' VRM (Vendor Relationship Management) systems, supporting rich and participatory two-way relationships. In fact, EmanciPay will by definition be a VRM system.<br />
<br />
=== Micro-accounting ===<br />
The idea of [http://en.wikipedia.org/wiki/Micropayment "micro-payments"] for goods on the Net has been around for a long time, and has recently been revitalized as a potential business model for journalism by [http://www.time.com/time/business/article/0,8599,1877191,00.html an article by Walter Isaacson] in Time Magazine. What ProjectVRM [http://blogs.law.harvard.edu/vrm/2009/02/11/EmanciPay-for-newspapers-and-everything-else-thats-free/ suggests instead] is something we don't yet have, but very much need: ''micro-accounting'' for actual uses. These including reading, listening and watching.<br />
Most of what we now call "content" is both free for the taking and worth more than $zero. How much more? We need to be able to say.<br />
So, as currently planned, EmanciPay would -<br />
# Provide a single and easy way that consumers of âcontentâ can become customers of it. In the current system -- which isn't one -- every artist, every musical group, every public radio and TV station, has his, her or its own way of taking in contributions from those who appreciate the work. This can be arduous and time-consuming for everybody involved. What EmanciPay proposes, however, is not a replacement for existing systems, but a new system that can supplement existing fund-raising systems -- one that can soak up much of today's MLOTT: Money Left On The Table.<br />
# Provide ways for individuals to look back through their media usage histories, inform themselves about what they have been enjoying, and to determine how much it is worth to them. The Copyright Arbitration Royalty Panel (CARP), and later the Copyright Royalty Board (CRB), both came up with ârates and terms that would have been negotiated in the marketplace between a willing buyer and a willing sellerâ â language that first appeared in the 1995 Digital Performance Royalty Act (DPRA), and tweaked in 1998 by the Digital Millennium Copyright Act (DMCA), under which both the CARP and the CRB operated. The rates they came up with peaked at $.0001 per âperformanceâ (a song or recording), per listener. EmanciPay creates the âwilling buyerâ that the DPRA thought wouldnât exist.<br />
# Stigmatize non-payment for worthwhile media goods. This is where âsocialâ will finally come to be something more than yet another tech buzzmodifier.<br />
All these require micro-accounting, not micro-payments. In fact micro-accounting can inform ordinary payments that can be made in clever new ways that should satisfy everybody with an interest in seeing artists compensated fairly for their work. An individual listener, for example, can say "I want to pay 1¢ for every song I hear on the radio," and "I'll send [http://www.soundexchange.com/ SoundExchange] a lump sum of all the pennies wish to pay for songs I hear over the course of a year, along with an accounting of what artists and songs I've listened to" -- and leave dispersal of those totaled pennies up to the kind of agency that likes, and can be trusted, to do that kind of thing.<br />
Similar systems can also be put in place for readers of newspapers, blogs and other journals.<br />
What's important is that the control is in the hands of the individual, and that the accounting and dispersal systems work the same way for everybody.<br />
=== Projects ===<br />
To work, EmanciPay needs to have its choices informed. For that there should be a number of tools in the [[Media Logging]] toolbox. The first we're working on is a [[Listen Log]] called [[ListenLog]] for the [http://publicradiotuner.org Public Radio Tuner].<br />
=== FAQ ===<br />
''Q: Who would want to use it and why?''<br />
<br />
Right now supporting otherwise &quot;free&quot; journalism ranges from difficult (setting up separate paid relationships with each journal or broadcast station, each with its own rules and procedures, with all data stored in the journal or station's system) to impossible (no means are provided at all). Even the membership systems of public broadcasting exclude vast numbers of people who would contribute &quot;if it was easy&quot;. EmanciPay will make it easy for consumers of media to become customers of media. It will allow those customers to pay for what they want, when they want, and to initiate actual relationships with the news organizations they pay -- on their own terms as well as those of the news organization.<br />
<br />
''Q: What potentially bigger thing might happen if everything went perfectly and the stars all aligned?''<br />
<br />
A much more healthy media business would arise out of the one that's failing -- at least economically -- right now. In the process, the media business would no longer be required to depend entirely on advertising, newsstand sales, subscriptions and donations because a new and far more accountable system would be in place. It would, for example, provide a way for any journalist or journalistic organization in the &quot;long tail&quot; to find paying customers for their work.<br />
<br />
''Q: Is EmanciPay a micropayments model?''<br />
<br />
No. EmanciPay will involve what might be called "microaccounting," however, by keeping logs and histories that inform the user about what media content he or she has consumed. This will aid in valuing that content. Users will also be able to set what might be called "microprices" on items such as songs heard on radio and other music streaming sources, such as Pandora or Last.fm. A listener could, for example, say he or she will pay 1¢ per song, and have payments roll over when they reach a sum large enough to make the transaction worthwhile. Willingness to pay can also be aggregated among multiple users. There are lots of ways to arrange this. But micropayments have proven problematic so far and we have no intent to visit the same problems with EmanciPay.<br />
<br />
''Q: How will you be able to measure whether or not EmanciPay has really made a difference?''<br />
<br />
The primary measure would be monetary -- measurable as cash income to news producers from the consumers who, by paying, would become customers as well. Goals and benchmarks for measuring social effects would be established.<br />
<br />
A secondary measure would be membership activities other than those surrounding transaction.<br />
<br />
''Q: What un-met need does EmanciPay answer?''<br />
<br />
Media need a new business model. In spite of the shift of advertising from other media to digital ones, little of this money finds its way to supporting, for example, participatory journalism, where so much good and pioneering work is taking place.<br />
<br />
EmanciPay will create that model. It will also go beyond monetary support to include means for establishing working relationships between the buyers and sellers of media products, so demand can find supply and vice versa.<br />
<br />
There is also the need to address the likelihood that advertising -- the primary source of income for many media enterprises -- will either be severely diminished or go away, simply because ways will be found for demand to find supply that are more efficient than the guesswork that advertising involves. EmanciPay will be one way to take advantage of this inevitable shift in the marketplace.<br />
<br />
[[Category:Media Logging]]<br />
[http://www.sexalemi.org sikis izle]<br />
[http://www.pornositeleri.net porno izle]<br />
[http://www.sexalemi.org sex izle]<br />
[http://www.sexalemi.org sikis]<br />
[http://www.cinsel.name sikis izle]<br />
[http://www.cinsel.name.tr sikis]<br />
[http://www.hiphopalemi.net hiphop]<br />
[http://www.kelebekchat.net kelebek chat]<br />
[http://www.kelebeksohbet.org kelebek sohbet]<br />
[http://www.chatsohbet.org chat sohbet]<br />
[http://www.siberchat.net chat]<br />
[http://www.pornositeleri.net porno]<br />
[http://www.pornositeleri.org porno izle]<br />
[http://www.sexpormok.net sex]<br />
[http://www.mynetsohbet.net mynet sohbet]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Events&diff=4179Events2009-12-09T18:50:39Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>==Future Events==<br />
<br />
* [http://cyber.law.harvard.edu/projectvrm/VRM_East_Coast_Workshop_2009 VRM East Coast Workshop 2009], 12-13 October 2009 at Harvard Law School, Cambridge, MA.<br />
* [http://cyber.law.harvard.edu/projectvrm/VRooM_Leadership_Workshop November 2009 Leadership Workshop], Location TBA<br />
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop 2009 (IIWIX, IIW)], 3-5 November 2009 at the Computer History Museum in Mountain View, CA.<br />
<br />
==Past Events==<br />
<br />
[[VRM West Coast Workshop 2009]]<br />
<br />
[[VRMworkshop]] at Harvard Law School, July 2008<br />
<br />
[[VRM Hacker Session]] November 9th 2007 London<br />
<br />
[http://www.supernova2006.com/ Supernova] 20-22 June, 2007 San Francisco<br />
<br />
[http://conferences.oreillynet.com/os2007/ OSCon] 23-27 July, Portland<br />
<br />
[http://conference.digitalidworld.com/2007/ Digital ID World (DIDW)] 24-26 September 2007, San Francisco<br />
<br />
[http://www.windley.com/events/iiw2007a/announcement Internet Identity Workshop (IIW)] May 14-15, 2007, Mountain View, CA<br />
<br />
[https://events.projectliberty.org/details.php?id=11 Identity Open Space (IOS)], 26-27 April, 2007 Brussels<br />
<br />
[[Notes from VRM & Public Media Workshop]] at the Berkman Center, April 4, 2007<br />
* Includes follow-up brainstorming ideas from April 6, 2007<br />
<br />
[http://cyber.law.harvard.edu/identity/Mobile_Identity_Workshop Mobile Identity Workshop], January 26, 2007<br />
<br />
[[Notes from VRM Meeting]], January 25, 2007<br />
<br />
[[Notes from Internet Identity Workshop 2006b]], December 4-6, 2006</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Interesting_Links&diff=4178Interesting Links2009-12-09T18:50:38Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>[http://cyber.law.harvard.edu/ The Berkman Center for Internet<br />
<br />
Stephen Downes - Distributed Digital Rights Management<br />
-- (The 'VRM' of this website is the 'Customer Broker' of the Downes presentations)<br />
-- [http://www.slideshare.net/tag/ddrm Slide shows on DDRM]<br />
-- [http://odrl.net/workshop2004/paper/odrl-downes-paper.pdf Distributed Digital Rights Management: The EduSource Approach to DRM] - presented at ODRL 1.0</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Help:Contents&diff=4177Help:Contents2009-12-09T18:50:37Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Khopper</p>
<hr />
<div>It's easy to start editing pages on this wiki! It is the job of every registered user to try and improve these pages. Wikis work best when everyone is involved and adding, editing, reworking, and checking the contents.<br />
<br />
==== How Do I Start? ====<br />
Log in (you must have a login to edit). Click on the "edit" tab at the top of any page. You will then begin editing the page you are on. There is a helpful [[Help:Cheatsheet|Cheatsheet]] to learn the basics of formatting your changes.<br />
<br />
==== Can I Practice? ====<br />
You bet. Try out editing on the [[Project_VRM:Sandbox|Sandbox]] Page. Anything goes there.<br />
<br />
==== When Should I Jump In? ==== <br />
A Wiki benefits from the "[http://en.wikipedia.org/wiki/Wikipedia:Be_bold_in_updating_pages Be bold]" philosophy. If you see something that can be improved, do not hesitate to do it yourself. Improvements come from the iterative additions and edits of all of us. Pages keep a revision history, so nothing can't be undone (click on the "history" tab at the top of the page). <br />
<br />
==== What Happens When There is Disagreement? ==== <br />
If someone disagrees with you, or you with them, then good! We've inspired involvement, and through edits and discussion on the [[Help_Talk:Contents|Talk Page]], consensus can be reached (each wiki page has its own respective talk page). Wikis work great for emerging concepts and themes like VRM that will benefit from exploration and the evolution of mutual agreement. Paradoxically, edits that introduce diversions from commonly-held understanding is what helps best build and spread editorial consensus.<br />
<br />
==== When Should We Use the Talk Page? ==== <br />
Every wiki page has a talk page. Click on the "discussion" tab at the top of the page to get there. Whenever you have a question that's holding you back from an edit or when conversation seems more appropriate than document-building. Please sign your comments on the talk page with four tildes ("<nowiki>~~~~</nowiki>") which will automatically drop in your username and time stamp.<br />
<br />
==== How Do I Keep Track of What's Going On? ==== <br />
There is a special page called "[[Special:Recentchanges|Recent Changes]]" that keeps a running list of all recent changes to the wiki. Think of this like a news feed of what's going on. Check out what other people are doing. Piggyback on their changes.<br />
<br />
You can also watch pages by clicking on the "watch" tab at the top of a page. This adds the page to your personal [[Special:Watchlist|Watchlist]]. You can visit this page any time to see what changes have been made, by whom, and when. For example, you can add the [[VRM vision]] page to your watchlist by clicking [http://cyber.law.harvard.edu/projectvrm/watch/VRM_vision here]. There are all sorts of additional [[Special:Specialpages|Special Pages]] that are worth checking out.<br />
<br />
==== Can I be Automatically Alerted Through Email? ==== <br />
You can receive email alerts when changes happen to watched pages by adjusting your [[Special:Preferences|Preferences]] page.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Taxonomy_issues&diff=4176Taxonomy issues2009-12-09T18:50:36Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Khopper</p>
<hr />
<div>Very much a stub...sorry for the current "stream of consciousness" character of this -- will be cleaning it all up as soon as possible.<br />
<br />
There's <strong>a lot</strong> of work here. RFPs should allow for widely varying degrees of specificity. Ideally, a seeker should be able to create an RFP for:<br />
<ul><li>a blackberry 7130c</li><br />
<li>a cell phone with bluetooth and EDGE support</li><br />
<li>a cell phone costing less than $250</li><br />
<li>a cell phone</li></ul><br />
Even before considering the different attributes required by different types of requests (travel planning vs. product purchase, for example) it's clear that creating a workable microformat for RFPs will be a fascinating (and frustrating) process. It's worth noting, though, that work in this area pays off in many ways.<br />
<br />
Desirable: RFP attribute "package," optional, linking multiple RFPs. Indicator to vendors that the seeker is interested in the entire package (implicitly asserting that offers that cover the entire package are preferable/required? Or explicit flag?) -- plane ticket RFP, car rental RFP, hotel RFP, linked by package ID. Five different books, linked by package ID. Possibly worthwhile on both ends: seeker only wants A if they can also get B, vendor can tailor offer/discounts based on total package.<br />
<br />
Note to self: Marti's "fulfillment" RFP attribute is an elegant addition. Does seem to suggest that authoritative, verifiable identity for vendors goes from "extremely useful" to "non-negotiable," though. Note also that it makes authoritative seeker identity even more significant: if seekers provide feedback that (is | may be) used to establish vendor reputation as an evaluation factor, there's significant incentive to astroturf. <br />
<br />
Suggests the desirability of a parallel reputation system that covers both vendors and seekers. Consider how long an entity has had a public presence, RFP/feedback patterns. Unfortunately seems to also suggest that there could be an actual need for some third-part(y|ies), handling the seeker/vendor DB stuff outlined in the VRM diagram: in addition to pointers to requests/offers, the archive retains history. In this case I guess one would want as many competing versions as possible, so that clients can poll multiple and use their own systems to resolve differing data.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Questions_raised&diff=4175Questions raised2009-12-09T18:50:35Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div><br />
<br />
* VRM [[policy objectives]]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Process&diff=4174Process2009-12-09T18:50:34Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>This page is a draft proposal. Please send any comments to [mailto:joe@andrieu.net] or to the Project VRM [[mailing list]].<br />
<br />
(On 19 May 2008, [http://www.mediainfluencer.net/2008/05/from-misapprehensions-to-alternatives/ Adriana Lukas suggested] that the process described here is "identity-based VRM", and should be distinguisted from "[http://docs.google.com/View?docid=df9dfsgj_1ghhqgjfq feeds-based VRM]". So, a note to selves: these should be distinguised in this wiki as well. - Doc)<br />
<br />
==VRM Process==<br />
One thing that Iâve been noodling lately is how we, as a community, can organize our efforts around VRM. <br />
<br />
===Microformats Inspiration===<br />
In a recent [http://bankwatch.wordpress.com/2007/01/05/microformats-as-information-brokers-revisited/ exchange] with [http://bankwatch.wordpress.com/about/ Colin Henderson] at [http://bankwatch.wordpress.com/ BankWatch], he asked about [http://microformats.org microformats] and VRM. I [http://blog.joeandrieu.com/2007/01/19/vrm-microformats/ replied] that I think there is a lot to learn from their efforts. In particular, microformats has a great ironclad process, established in the early days, that continues to serve as a corral and assembly line for new microformats proposal. It is the foundation for how they forge community consensus. Along with the principle of paving the cowpaths, the process severely cuts down on distracting hypothetical conversations and assures a wiki-documented evolution towards a community consensus. Many newbie questions have been productively answered by a link to the process page and a polite invitation to read it and start working their ideas through it.<br />
<br />
===A Standard Process===<br />
Establishing such a standard process could have a great positive influence on VRM, especially as Project VRM has the potential to become a clearinghouse for different approaches in different domains, each requiring independent investment, development, and consensus. For example, VRM solutions for vendor selection are likely different from those for Personal Health Records and those for Banking.<br />
<br />
Early community norms about how we go from âA great ideaâ to something people can start implementing, would, I believe, help more ideas reach critical success more quickly, as people spend more time doing the work rather than debating hypothetical design points and process issues. A good process would also let people know how to contribute and assure that good ideas are fully fleshed out as they develop. Of course, concrete design issues, grounded in context, goals, and constraints, are good topics for conversation.<br />
<br />
This actually dovetails, nicely I think, with Chrisâs [http://www.socialcustomer.com/2007/01/more_on_vendor_.html comments] earlier on putting the cart before the horse in VRM development. As he said so concisely:<br />
<blockquote><br />
Before diving into creating a new technical spec, step outside and look around a bit.<br />
</blockquote><br />
<br />
So, here is a strawman proposal for how we might, as a community, organize a process for developing VRM systems. The idea is that each of these steps helps elucidate the details of a problem that could be solved by VRM. Each step is itself straightforward, building upon the steps before hand, and once complete, moving to interoperable implementations should be fairly simple. *grin*<br />
<br />
===Scenarios===<br />
It turns out that Usage Scenarios could be an important part of this process, meaning Scenarios in the context of Use Cases and user-driven development. Chris Carfi has started an excellent thread about future [[VRM Scenarios]], using a subtly different meaning of the word. Iâll generally stick with Usage Scenarios to clarify my use.<br />
<br />
Usage Scenarios are, for me, a simple, short, narrative description of one or more specific and detailed interactions with the current or proposed system. The idea is to keep it real, to keep it colloquial, and to capture the essence of the situation rather than a detailed list of all possible variants. In my projects, Usage Scenarios have proven to be a great bridge between the problem domain and a technical specification. And when kept to just a paragraph or so, they are easy to write, too.<br />
<br />
==='''''Protocol''''' as VRM Output===<br />
In writing this, it became clear that we might benefit from having a specific noun for describing the output of our work. Microformats produces microformats. Pretty straight forward. What does VRM produce? Perhaps '''''Protocol''''' would be appropriate:<br />
<br />
* To develop a new VRM Protocol, one would shephard it through the VRM process on the Project VRM wiki.<br />
* To implement a component of, or software that connects with, a VRM Protocol, one would implement the interfaces and protocols of that Interchange.<br />
* The VRM Loan Protocol currently supports mortgage applications.<br />
* The VRM pRFP Protocol allows for the secure, identity-controlled digital requests-for-proposals in an open marketspace.<br />
<br />
Protocal seems to work. However, I would definitely appreciate feedback and alternative suggestions for such a term.<br />
<br />
==Draft VRM Process==<br />
The proposed process follows. The idea is that each section would have its own wiki page, preceeded by the name of the Interchange. Eg. http://projectvrm.org/Interchanges/pRFP/Domain and http://projectvrm.org/Interchanges/pRFP/Current_usage_scenarios<br />
<br />
#'''Problem Domain'''<br>A discussion of the problem domain, in the nature of a real-world problem that is containable, i.e., a specific solvable problem. This becomes the charter for this particular Interchange.<br />
#'''Current Scenarios'''<br>Brief prose descriptions of actual instances of the problem.<br />
#'''Desired Scenarios'''<br>Brief prose descriptions about how it might all be made better.<br />
#'''Existing Efforts'''<br>A review of what has already been done in this area and who (organizationally) is still working on this problem. This will serve both to incorporate existing efforts and to learn from past mistakes.<br />
##'''Software'''<br />
##'''Protocols'''<br />
##'''Formats'''<br />
##'''Initiatives'''<br />
##'''Organizations'''<br />
#'''Users'''<br>A quick run down of who the system must support at various different levels. This should list both categories of users and some specific examples in each category. There may be many subcategories under each of the following major categories.<br>The idea here is not to build the system to be perfect for each of these users, but to make sure we have all the stakeholders in context as we flesh out the design. Ultimately just a handful of target users will be the focus.<br />
##'''End users'''<br />
##'''Vendor users'''<br />
##'''Supporting Users'''(retailers? regulators?)<br />
##'''Implementors'''<br />
#'''Use Cases'''<br>These are specific, complete transactions between users and the system. All critical use cases should be listed, along with various incidental or support cases that could influence overall design. Ultimately, a handful of defining use cases will drive system design.<br />
##'''Abstract, High-Level Use Cases'''<br>Single sentences describing a use case. When done well, they become the name of the use case. For an ATM, you might have âWithdraw Cashâ or âTransfer Fundsâ as abstract high-level use cases.<br />
##'''Concrete Detailed Use Cases'''<br>Detailed use cases describe the chronological back & forth (action/reaction) between users and the system to realize a particular transaction. Concrete use cases are free to use specific design and implementation choices. This is useful either at the very beginning when transcribing scenarios (when the specifics help you understand what is actually happening) and at the very end (when the specifics represent design decisions).<br />
##'''Abstract, Detailed Use Cases'''<br>Abstract use cases are stripped of the design decisions to more completely and accurately describe the critical steps while also freeing up the design process to innovate. For example, a concrete use case for the ATM might include the concrete steps of inserting a bankcard, prompting for a PIN, entering pin on keypad, and verifying PIN. And abstract version of that same use case could be âidentify user, authenticate user.â Itâs easy to see how the abstract version allows for alternative implementations where the first one presumed a bankcard, keypad and PIN.<br />
#'''Brainstorming'''<br>Free-form inspirations and ideas about how to realize one or more of those use cases.<br />
#'''Draft'''<br>After some brainstorming, a basic system design will emerge, either meeting all the use cases or accepting the loss of some use cases as part of the design choices in the draft.<br />
##'''Entities'''<br />
##'''Communications'''<br />
###'''Protocols'''<br />
###'''Formats'''<br />
###'''Transactions'''<br />
#'''Proposal'''<br>Once the draft is bandied about and improved on by the community, the group who has taken stewardship of the domain can propose it to the entire VRM community as a standard VRM Interchange. This would expose it to more feedback and improvements and engage the entire VRM universe in the final stages of development.<br />
#'''Published Standard'''<br>After the community as a whole has had a chance to contribute, the Interchange would eventually either be approved and published as a standard or disbanded. I donât see any reason for a specific timeframe for any of these steps in the process, but there may be efforts that get proposed that ultimately are better served by other means or by breaking them into smaller Interchanges. It is at the publication stage that a standard becomes âofficialâ and earns a version number. Amendments or revisions to the standard would go through some related process and be published with a later version.<br />
#'''Reference Implementation'''<br>Create a reference implementation of the standard, to provide a sandbox against which implementers can test their implementations, and to provide a baseline for interoperability.<br />
#'''Implementation Directory'''<br>The standard is added to a directory of the different people and/or services who claim support for the standard. (This could also include external points-of-view/reviews of how well that person/service supported the standard.)<br />
<br />
Feedback is definitely welcome.<br />
[[User:Joe.andrieu|Joe.andrieu]] 09:28, 23 January 2007 (EST)</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Personal_Data_Stores&diff=4172Personal Data Stores2009-12-09T18:50:30Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>Drummond Reedâs â Personal Data Store<br />
With Iain Henderson to address as well<br />
<br />
On Board:<br />
<br />
PDS:<br />
<br />
What should be in it? (at a minimum) and (ideally)<br />
Whatâs it for?<br />
<br />
What is its essential characteristics/components<br />
<br />
Where does it reside?<br />
<br />
Where does it fit in the overall OSI Model and the VRM architecture <br />
<br />
Why is it important?<br />
<br />
When is it deployed?<br />
<br />
How is it managed â what policies apply?<br />
<br />
Does it have to be standard? Cabn there be many types?<br />
<br />
What are the points of failure?<br />
<br />
Drummond â the concept of PDS has been central to VRM<br />
<br />
This is to talk about why? And to look specifically at the PDS<br />
<br />
One starting point is âWhy is it importantâ/<br />
<br />
Another is âwhat is essential?â<br />
<br />
When we wrap up, we ask â On what points are we not in agreement?<br />
<br />
Iain describes myDex though Slide show<br />
<br />
Observation â Enterprise CRM architecture have multiple attributes but only store data for a year. If well designed, âimportant dataâ will be stored in Analytical System and data warehouse. Which holds the atomic level of data and stores it for the duration of a decisionmaking cycle.<br />
<br />
Analytical systems tracks who bought what, where and why?==> to anticipate what to do next<br />
<br />
First order concern is quality â meaning completeness, accuracy and several other attributesâ¦<br />
<br />
Evidence is that âCRM Needs to be fixedâ â spending 200 bps is not enough to fulfill requirements. Okay at collecting info on customer. Not so good on tracking customer/product/outlet info in a usable fashion<br />
<br />
Definition of âPersonal Data Store â (admittedly not a helpful term) A generic term to âsource, store, enhance and selectively disclose my personal informationâ<br />
<br />
Needs to run on the same principles as the CRM⦠Systems will do the doingâ¦.<br />
<br />
The personal data warehouse is the missing element.<br />
<br />
In CRM the identity layer is at the top end<br />
PDS resides on top. With the sources <br />
<br />
Sees 3,500 attributes over 70 years (is what each individual has)<br />
<br />
''(Thematic) Individuals have less tools, more attributes to control, fewer resources to monitor and track.''<br />
<br />
Craig Burton â it is important and extensible as well. <br />
A: So you need to identify the important attributes versos <br />
<br />
To determine whatâs important, just identify what info you might need to get your life started again.<br />
<br />
Next slide depicts Interactions and transactions with all sorts of businesses and govât entities. With the Identity Layer at the core.<br />
<br />
*No CRM database can handle persona so you go about creating multiple ones to transact and interactx in the world.<br />
<br />
Important â This is a logical design, not a physical designâ¦<br />
<br />
It has been posited that Interactions are whatâs being monitored and that Transactions are a type of interaction.<br />
<br />
Joe Andreiu â says we can get to the Model T version that does okay <br />
<br />
Next slide â Current state of Who has what data⦠<br />
<br />
Was My Data, Your data, Everybodyâs Data, âTheir Dataâ<br />
<br />
Everybodyâs data = public domain â all sorts of data thatâs avaialbe.<br />
âTheir Data (or parasitic tailings) â what Experian, Acxiom etc, collect about you<br />
<br />
Your dat â include a vendors products /services, policies, pricesâ¦<br />
And guesses regarding view of a customers preferences, requirementsâ¦<br />
<br />
Our Data â identifiers, clams,/Assertions and transactionsâ¦<br />
<br />
MY DATA â is stuff known only to me⦠Circumstances, Assets, Liabilities, preferencesâ¦<br />
<br />
There are also back channels which are interactions between the parasites, vendors, and the publicly available stores.<br />
<br />
At Liberty Alliance they have been discussing âVolunteered Informationâ<br />
<br />
Finally, Thereâs the Target State<br />
<br />
In 10 years time 80 percent of customer management prcesses will startywith âMYDATAâ (me) <br />
<br />
So the customer will be in more control and overt interactions will be between the vendor <br />
<br />
Toxic will be bad for both vendors and customers â they destroy trust.<br />
<br />
''Drummond â 3 times Iâve heard that âThe customer is the point of integrationâ (which originated from Joe Andrieu)''<br />
<br />
âCustomer as Point of Integrationâ<br />
<br />
Joe says âAnalysis and Insightâ revolved around the vendor data⦠It is the source of Googleâs competitive advantage ⦠<br />
<br />
Craig Burton â but Googleâs source of distrust was doing personal data storage for Google to tag and index<br />
<br />
PDS has âroots in two placesâ<br />
<br />
1) Doc Searls â personal experience with the medical treatment across several care givers and each introduced errors in their systems so that they could not reconcile or synchronize⦠The conclusion is that it would have been more efficient and less dangerous if Doc had been the single repository providing to access to the data on an as needed basis.<br />
<br />
2) The other side is âStymergyâ which is the general term for how ants find the shortest path to food. It is also the answer to a distribution problem for multiple trucks between warehouses. They send out ants randomly, the one that comes back first, his trail is doubled.<br />
<br />
Balance between exploration and exploitation. They mark their environment. Joe articulates that the data should be stored centrally and when multiple companies or individuals want access, they should not seek out things from one another. They should get it from the individualâs data store<br />
<br />
Stuart- Why wouldnât you just ask Amazon.com or Google to do a better job of making your information accessible to other apps. So I can assemble it at my command from the multiple sources.<br />
<br />
Joeâs answer â youâre asking about data portability. <br />
Iain says (itâs because youâd be operating under their terms and conditions)<br />
<br />
Joe says it is because personal data store is not just âthe dataâ it is about setting up mechanisms for permissioning information in, out based behind your own front end (called identity)<br />
<br />
And youâre going to have all sorts of front ends or âService Specificationsâ (Liberty calls them Service Interface Specification)<br />
<br />
Status updates<br />
Addresses<br />
Music ratings<br />
Search Activities<br />
Personal RFPs<br />
Personal Healthcare records<br />
SMTP/POP<br />
<br />
And itâs all under your control<br />
<br />
Sop the question is whether the hub is about authentication (identity layer)<br />
And permissioning<br />
<br />
*** so there is a multi-billion battle raging over control of permissioning for status updates.<br />
<br />
Iain â youâre still missing the link between doing data and planning data.<br />
<br />
Doc sees the user as the point of integration and also origination.<br />
<br />
Else â a problem solving thing which gets brought up.<br />
<br />
That is the ossified way that existing systems work<br />
In medical system, fârinstance⦠there is a kiretsu of equipment providers, suppliers etc where it is hard to get data from individuals or companies. Incompatibility between media, age of PC, etc.<br />
<br />
You are going to have this architecture work better in some cases rather than others.<br />
<br />
Iain, where thereâs failure in ERP or CRM itâs because the system is trying to do too much and gets clogged up.<br />
<br />
So you need to make the distinction between getting stuff done and when you have to do long-term planning.<br />
<br />
Per Drummond â donât you end up answering the question by establishing the framework for these the service interfaces service provier (Facebook, Myspace, Plaxo)â¦. And those service providers would manage one or more of the service specification intervfaces.<br />
<br />
Joe is saying that it is easier to solve and optimize the âshortest pathâ solution for specific tasks then to define the personal data store that does it all.<br />
<br />
Iain is saying that it will have to do the analytics earlier and constantly.<br />
<br />
Architecturally you sidestep it by providing a service thatâs operational and do it in a way that is consistent with doing the analytical and do it in a way thatâs consistent with identity based permissions.<br />
<br />
So you donât have to do them all if you can solve one of them seamlessly.<br />
<br />
Drummond will explain what XDI is all about as a protocol:<br />
<br />
The idea of getting all sorts of schemas to talk to one another is a real probalem. HtML canât. XML cannot.<br />
<br />
About trusted Data sharing. And itâs about permission <br />
<br />
Craig says that XDI is not a protocol. It is a language structure <br />
<br />
He wants to know âwhat does it resolve toâ if I write a command and it gets abstracted to something that then resolves to the data and its location. So if you want to share some of your data that resides elsewhere, like in multiple banks⦠<br />
<br />
''The Data doesnât have to live at the hub⦠But control does''<br />
<br />
Craig â it resolves around a URL and then I can react to it based on a structured card<br />
<br />
Card<br />
Rule Set<br />
Data set<br />
<br />
Resolved to a URL and it gives permission to access to where that data can be found. And enable data set mashup.<br />
<br />
E.g. iphone with a GPS Google Map moment. âTell me where the lone palms hotel is in relationship to meâ tell me where I am and where I go.<br />
<br />
Itâs mashup that needs to include all that data.<br />
<br />
CyberCrack!<br />
<br />
Ad active rules to operate on your data store, and the mashup of all the services <br />
<br />
I just want to get this group to define the architecture to put it into the hands of the developer community./<br />
<br />
E.g. Amazon.comâs EC2 setting up all sort of things (like 30 years of census data) <br />
<br />
Q: When you say ârule setsâ do you just mean permissions?<br />
<br />
A: (using the MyDex example - ) as a proof of concept, no browser is required. Any program and any entity can subscribe to the other info an dlocation and all or part be âin the cloudâ<br />
<br />
Switchbook has all the info distilled on the hard drive, there is a copy in the cloud for back up purposes. It doesnât have to be in the cloud. And thereâs code in the client to handle I/O<br />
<br />
When you get to rules⦠You put functionality in the cloud that handles services and can find them in the cloud.<br />
<br />
Customer write the rules.<br />
<br />
Stuart⦠Example is embedding a twitpics or a URL in a twit⦠Iâm publishing something that can then be seen by anyone or everyone. Or how do I add a âsmart URLâ to a tweet so that I can publish to everyone, but the URL has a set of criteria behind it or around it that is controlled by the higher order infrastructure.<br />
<br />
Can use a medium like Twitter to infect the world with XDI and XRI<br />
<br />
If all or portions of your data are addressable, it can be made accessible to the rest of the world. If you make it abstract. If itâs inside the âIdentity Layerâ it can be under the control of the user. One of the key purposes of the next step, which is XDI⦠The same format says that I can store the âpermissionsâ (sometimes called ârulesâ) so that I can access the Link contract. So that the read/write instructions can attached to another set of rules to do something like letting the gas company <br />
<br />
Go To Wiki.kynetics.com (it explains the rules that Phil Wendly has developed)<br />
<br />
Joe says that Grease Monkey does it as well. But Craig Burton says that kinetics⦠is what we should be interested in.<br />
<br />
Joe says HTML 5 is being deployed now in browsers. <br />
<br />
Craig: I would strongly recommend that we do this in a way that is somewhere between Wiki-based and Selecter-based that is Strong foundation for VRM. <br />
<br />
Joe, part of this is about deployment⦠âI hate JaSon because it is inherently insecureâ but they have ways to do secure parsing of Jason⦠But it was adopted because it provided trivially easy way to do it insecurely and native to JAVAscript.<br />
<br />
We want to play friendly with them.<br />
<br />
Question, gas company needs employment data about me. 1 to 1 federation on their own terms. VRM way. Passport agency acts as a node and permissions allows Gas company to get info from passport agency. <br />
<br />
Data liquidity is what itâs all about.<br />
<br />
Read it as âpermissionedâ or âunpermissionedâ and the reason that there is so much unpermissioned is because âthereâs no technology in useâ to support permissioned. Which is an argument for Portable Permissioning.<br />
<br />
Joe-looking at Switchbook in this context is that your identity is stringly around what you give permission for.<br />
<br />
Switchbook defines you by your âsearch mapâ itâs a file that is orthogonal to all your other identifiers. Itâs Switchbox has a âSearchMapâ document at its core. It is the context where your current browsing shows where youâve been and what youâve done and all that.<br />
<br />
Idea is that we shouldnât get hung up on the protocol right now. Just define how entities interact and figure out the mesh points.<br />
<br />
In the IDWSF model, how you talk to the gas company is permissions based. They may send you an email or something and you set it up with your IDWSF model.<br />
<br />
Drummond: Now we talk about our questions.<br />
<br />
1) Why is it important?<br />
<br />
Initial â The thing that will put the individual back in control of personal information. Meaning the information that is important to the person.<br />
<br />
Itâs the store that you personally have control of, it could be anything.<br />
<br />
Will allow us to be more promiscuous with our data because we know it will be stored in a trusted way.<br />
<br />
It is a context for control.<br />
<br />
Because if you abuse it, I know your pheromone trail? <br />
<br />
Benefit is that it will improve my quality life, based on my decisions.<br />
<br />
Itâs important because it is valuable? It can be bartered><br />
<br />
It is economically transformational><br />
<br />
Jim â Like credit cards, this lowered the friction and reduces guesswork and waste from the vendor side. Which increases value. <br />
<br />
Best case you provide the best possible outcome for both parties.<br />
<br />
It is more efficiently economically. (the economy will operate more efficiently)<br />
<br />
It enables what weâre calling the fourth party services (what VRM is promising).<br />
<br />
Markâs point â Itâs a way to organize VRM.<br />
<br />
What weâre talking about as the personal data store is to create a better marketplace by providing the way the individuals are regarded by buyers/sellers/governments.<br />
<br />
It helps people organize their lives. It enhances efficiency and productivity.<br />
<br />
Framework for new use conventions that we donât foresee right now (think of browsing⦠or logging onto the bank)<br />
<br />
Itâs implementable <br />
<br />
Now letâs look to points of failure:<br />
<br />
Adriana would say that there are point-to-point identity free interactions that donât require this.<br />
<br />
Aside â Kim Cameron says that âIdentityâ is not an identifier. It is just a set of claims that require context. You can have a claimless set of claims in a container.<br />
<br />
It is about 4 different identifiers:<br />
<br />
Authentication<br />
Presentation<br />
Reference ID (how to be reached email address)<br />
Internal ID <br />
<br />
This is your identity online<br />
<br />
Are there VRM-y things that donât have a personal data store as part of it⦠The answer is noâ¦<br />
<br />
You need a place for your stuffâ¦<br />
<br />
<br />
Q: Where does it have to reside⦠It could be anywhere as long as itâs accessible by the applications<br />
<br />
Q: Isnât really a permission and control hub? Answer is ânoâ it is still about the data with rules established as to the permission and conditions under which<br />
<br />
Weâve gone in circles around what is a relationship manager as opposed to a relation service.<br />
<br />
Iain says, itâs all about how you operate around the data⦠Need to clarify how to source, store, enhance and selectively disclose data.<br />
<br />
Drummond â the other place the Identity comes in is that the idea of the role of the user in terms of control is akin to the control they have over their bank account. But the bank has authority.<br />
<br />
The relationship someone has with Equifax, for instance, is Massively Passively<br />
<br />
Another parallel is like the spam filter, where we have passive benefit but virtually no control.<br />
<br />
Jim Morris asked what this would be like if it were Communist China and there was an argument for centralized ⦠Drummond, from the point of view of market (as opposed to moral), this is the mechanism for giving user control.<br />
<br />
This is about distributed planning. <br />
<br />
Has anyone looked at giving control of the personal ID store to a centralized trusted entityâ¦<br />
<br />
Bullets for tomorrow:<br />
<br />
Privacy:<br />
*IP addresses are they tracked⦠<br />
*Iâm worried about Google tracking activity<br />
<br />
User Experience <br />
*complex<br />
*could create opportunity for errors<br />
*Mashing on toes<br />
<br />
Conformance and compliance<br />
(if I share data, how will I know if people abide)<br />
a<br />
Reputational authority (how do I know you are who you say you are)<br />
<br />
Service dependability<br />
Business dependability<br />
<br />
Portability?<br />
Inadequate choice of SPs<br />
<br />
Data Breach and fear of data breach (Honey Pot)</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=PAM_One_night_Stands&diff=4171PAM One night Stands2009-12-09T18:50:29Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>This VRM Workshop session covered the concept of the Personal Address Manager.<br />
<br />
The scene setting points covered:<br />
<br />
First Assumption - Privacy<br />
Differences from long running relationships<br />
- Mutual policy negotiation - pain-free<br />
- Default policy bucket<br />
- No identifier<br />
Easy to produce end of relationship artifacts<br />
Win-Win for customers and vendors<br />
- Removing barriers to exit is attractive.<br />
A use case was examined: Single Stop Online Shopping <br />
<br />
With Address<br />
With Personal Delivery Service (eg. relationship wth UPS, Fedex etc.)<br />
With Vendor Delivery Service (eg. Vendors own delivery service that respects PAM token)<br />
With Address from Personal Address Manager<br />
<br />
Is the "With Address" scenario a Personal Address Manager (PAM) case? However the PAM might be the place where user relationship policies are stored. "With Address" was eliminated as a policy statement by vendors.<br />
<br />
The "with Delivery Service" was selected to analyze.<br />
<br />
'''Roles: '''<br />
Shopper (S:)<br />
Merchant (M:)<br />
<br />
'''Assumption:''''''Bold text'''<br />
Policy Assurance and Warranty<br />
<br />
'''Scenario:'''<br />
Step 1. <br />
<br />
S: Shop at a compliant store <br />
<br />
M: Offer VRM ("use VRM" button on the web page)<br />
<br />
Step 2.<br />
<br />
S: Click "Use VRM"<br />
<br />
M: Endpoint Request<br />
<br />
Step 3.<br />
<br />
S: VRM Discovery End point - ie. PAM Address pointer<br />
<br />
M: Push to provision<br />
<br />
Step 4.<br />
<br />
S: Provision vendor<br />
<br />
S: Give Vendor token (with policy)<br />
<br />
M: Policy agreement <br />
<br />
M: Use token to get address<br />
<br />
M: Use Address<br />
<br />
M: Delete<br />
<br />
M: Confirmation of End of use <br />
<br />
<br />
Side notes:<br />
<br />
Initiatives are underway to build a policy framework. (SAML and WS-Policy?)<br />
<br />
<br />
<br />
This was a complex discussion to develop the scenario. Edits to refine this discussion can be made on the VRM Workshop Wiki in the Personal Address Manager page.<br />
<br />
Also posted to [http://ekive.blogspot.com/2008/07/vrm-and-personal-address-manager.html EKIVE Blog]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=ListenLog_Meeting_Notes&diff=4170ListenLog Meeting Notes2009-12-09T18:50:29Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>[[Category:Media Logging]]<br />
[[Category:Conference call]]<br />
<br />
Below are meeting notes and ongoing issues and action item lists. For a detailed description of ListenLog, visit the main [[ListenLog]] page.<br />
<br />
==1/12==<br />
===Parking Lot===<br />
* Where is data stored (by default)? Does it sync to a local store or just stream out?<br />
* Is there any concern from collaboration stations and partners that there's no exclusive access to data / analytics?<br />
* What data do we capture? Application behavior data in addition to basic listen data? What about rating data? Location data?<br />
** Should the standard by minimal for extensibility vs. maximal for enhanced value/functionality<br />
** Privacy concerns (EFF Chair Brad Templeton)<br />
* Security / encryption on the stored data? Which bits?<br />
* How best to communicate and promote the ListenLog concept and where the key benefits and differentiators are? How do we address naysayers and differentiate from alternative approaches, e.g. APML?<br />
* How do we do identity? How do we make it swappable? Do we use icards, openID, Oauth? <br />
* How do we start the service without identity? (e.g. access to device ID?)<br />
* Do users have control over what's stored?<br />
* What's the absolute minimum of device-side functionality?<br />
** Opt-out(?)<br />
** Change repository<br />
** Assign identity<br />
* Where does legal and TOS come in? (see rights and contracts below)<br />
* Does anyone enforce standards compliance?<br />
* Who does the work / coding?<br />
** PRX + who?<br />
* Do we think about revenue / sustainability? PRX has two roles here - one to build codebase and standards for storage, the other to think about services and how we'd use the data.<br />
* Do we do opt out for data capture? (probably yes)<br />
* Do we provide "public by default," e.g. ubiquitious, anonymous access to the data out of the box (probably no)<br />
* Can we open source iphone bit? Publicly available libraries?<br />
* What's in the first release?<br />
** Should we provide ability for users to release data? How and to whom? What capacity for sharing? What terms? Anon vs. nonanon?<br />
* Does there need to be database legal protection underlying data rights access to drive user terms?<br />
<br />
==1/13==<br />
* How do we make the data inherently more anonymous?<br />
** Match account data between logs<br />
** Make timestamp and LAT-LONG fuzzy?<br />
* What data rights can a user authorize for third parties?<br />
** propagation rights (the grantee can't extend to someone else)<br />
** public rights vs. directed/granted rights (e.g. for anyone to use vs. for specific entity to use)<br />
*** anon/non-anonymous<br />
*** Most rights issues/rats nests are associated with granted rights<br />
** How long you can use the data for? Keep the data?<br />
** Rights to cease use, remove data(?) + confirmation(?)<br />
** Can't use this to try and find/identify someone - reverse-engineering rights<br />
** commercial/non-commercial?<br />
** Contact me (e.g. DNC)<br />
** Compare to IRB<br />
* Contract rights<br />
** Investigate proactively - what is it that pandora might want to do? What is reasonable?<br />
*** give me audio recommendations<br />
*** use for product development<br />
** Don't cross-correlate/aggregate (e.g. social network correlation, Ben Laurie) - piercing identity/privacy data<br />
** Endorsement / assignment to my identity<br />
<br />
===Core Requirements===<br />
* what data is going to be captured<br />
* where is it stored and in what format<br />
* how does one identify oneself / assign identity<br />
* what's the minimum functionality that needs to live on the device<br />
* what's the minimum functionality that needs to live remotely<br />
* additional / core functionality to prove value necessary?<br />
* Determine protections for communication and storage between client app and repository authenticated, encrypted, etc.<br />
<br />
===Action Items===<br />
* Draft functional requirements<br />
* Doc talk to Berkman legal re: user rights / terms<br />
<br />
==1/20==<br />
* There is a core set of things to figure out to proceed with this project. We'll focus on those:<br />
** What data will we capture?<br />
** What format will we send and store the data in?<br />
** How is this data being transmitted and stored?<br />
** How do we maintain integrity, privacy, and provide the required minimum of user control (e.g. "delete my data")?<br />
** How do we assign or associate identity?<br />
<br />
* In discussing data capture, Keith argued for being minimal and conservative and providing a mechanism for extending<br />
* Agreement that our proposed data, format, and services will deal with listening attention data only; both for on-demand (file) audio as well as streaming audio<br />
* Open question about whether Sound Exchange / RIAA requires specific formats, if so, might be nice to comply<br />
* XRI be resolved / discoverability<br />
<br />
* XDI can be used to transmit and/or store; X3 looks promising<br />
* XRI = identifier - resolvable to an XDI endpoint<br />
* XDI dictionary - like an XML schema<br />
* XRI authority resolution server (open XRI)<br />
* community iname registry<br />
* inumber (this is how you handle reassignment)<br />
* At what level will we register?<br />
* How will we maintain this registry?<br />
* How will other applications that write to LL handle XRI? Will they resolve to their own server? <br />
*What about dupes?<br />
**xri synonyms is the answer?<br />
* Use iname registration for digital identity?<br />
** might not need an icard selector on the iphone<br />
** Simpler way?<br />
<br />
===Action Items===<br />
* Diagram high-level architecture<br />
* Prep for discussing identity options next week<br />
* Look into Sound Exchange reporting formats and PBcore formats<br />
<br />
==2/26==<br />
===Action Items===<br />
* Make some design decisions to get us started with POC development<br />
* Create a boxes and arrows diagram to help represent the data sets and functional entities and where they live<br />
* Have a convo with berkman RE: servers and hosting the user data<br />
* Identity + claimant - how best to handle user identity (focus on near-term)?<br />
* XDI dictionary - designing what info is sent to log, registrants, etc.<br />
* Revisit user functionality on wiki - what do we really need to do? What role should XRI/XDI (and existing OpenXRI code) do for us here?<br />
<br />
==3/3==<br />
===Notes on Identity Requirements===<br />
<br />
When does identity happen? There are at least three contexts where we handle identity<br />
<br />
#Capture data implicitly<br />
##No registration<br />
##Linked to phone<br />
#Access to data provisioned through phone<br />
#Sending listen activity to other data store providers instead of the default store<br />
<br />
Perhaps there are others, but these three seem clear so far.<br />
<br />
By way of thinking about identity, it is worth noting that there are four distinct functional aspects of identity. Something I call the Identity Quartet (blog post imminent!)<br />
<br />
# For authentication, logging into services (username:jandrieu)<br />
# For presentation, e.g., as handle on MySpace or Facebook or WOrld of Warcraft (name: Thor the Destroyer)<br />
# Internally for database level handling of the attributes & privileges associated with a user (users.primaryKey=1023304)<br />
# As a service endpoint, e.g., joe@andrieu.net<br />
<br />
Flexible identity systems separate these four elements. Lazy ones combine, such as using my email address as my username. Or displaying my email address when I comment on a bulletin board system. A good system has distinct identifiers for each of these roles, and in fact, sophisticated ones could/should allow multiple different identifiers of the same functional class, for the same user, such as allowing an individual to have multiple characters on WoW, Iain Henderson calls this aspect of identity "personnas".<br />
<br />
So, between the first set of contexts and the four functional types, we should be able to map out what we need for ListenLog.<br />
<br />
-j<br />
<br />
===Identity Workflow===<br />
How identity in the LL app(s) might work. This is a proposed workflow based on my limited understanding of how identity systems work:<br />
<br />
[[User:Khopper|Khopper]] 15:19, 10 March 2009 (UTC)<br />
<br />
# ID the data: iPhone app by default will create a unique ID for each install (likely created by combining application ID + device ID) in order to appropriately key the log data to a unique instance (individual)<br />
# Claim the data: In order to get access to this data beyond the phone, the individual must associate the existing unique ID in #1 with a more friendly and portable identity (i.e. user ID). This could be through a unique external or internal identification process. External might be something like OpenID, internal might be created and assigned through an integrated user registration process. This would have to happen on the phone.<br />
# To complete the association, the user must authenticate (internally or externally)<br />
# The LL datastore must associate the UniqueID in #1 with the userID in #2. Ideally, this will be obfuscated in some way to protect the identity of the user (is this possible?).<br />
# To retrieve the data remotely (e.g. on a website that lets you browse your LL data), you must provide identity credentials and authenticate. This will locate the data and validate your access to it.<br />
# To write to the data remotely through another application or device (e.g. Pandora), you must follow steps 1-4 above. This should be standardized as part of the LL specification. It is conceivable that there are use cases where data needs to be merged or split by application ID, by user ID, or by Unique ID.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Health_VRM&diff=4169Health VRM2009-12-09T18:50:27Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>Mike Kirkwood. â Healthcare discussion<br />
Mike@polka.com<br />
<br />
Focusing on the space of a âMe serviceâ for the healthcare industry<br />
<br />
Includes âHealth Journalingâ app for itunes<br />
<br />
Thereâs personal health records<br />
<br />
Took engine that was user focused, and offered it to the providers.<br />
<br />
Kaiser<br />
Healthnet<br />
<br />
Weâre training them to figure out how, rather them having to open up a personâs file, putting it into a record repository that the patient controls.<br />
<br />
Finding that the record doesnât change that often<br />
<br />
CFP2 â Robert Wood Johnson released as a way to share observations âacross the wallâ in a clinical setting and have them integrated into other test results and validated<br />
<br />
Itâs a big deal<br />
<br />
Sean Bohan â says that the big things are conformance (using your meds right)<br />
<br />
40% of the problems is adherence<br />
<br />
and 10% is fatal combination.<br />
<br />
Sean â the other side is disease management⦠Healthcare providers will offload patient management to small companies that would outcall <br />
<br />
Payer is struggling with bad disease management because too many people are ending up in the ER which is the most expensive way to do disease management.<br />
<br />
So the providers and payers want to incent people to take care of themselves so they donât end up in the critical phase.<br />
<br />
Project Health Design â has a call to papers. Told clinical teams that if they can get a system to log daily livings, they will a system that will work.<br />
<br />
This system would be part of the service delivery solution.<br />
<br />
Can put HealthVault or Google Health in the middle.<br />
<br />
So there are other players in the mix.. like the hospital or the doctor.<br />
<br />
They would solicit the patient maintained data <br />
<br />
HIPAA and HL7 data privacy issues had prevented this stuff from happening before.<br />
<br />
Can add glucose monitor, heartbeat monitor (an Observation Engine) will then publish to the provider<br />
<br />
Mike asserts that this sort of system should adhere to the 10 points that Joe brought up in the User Controled User session.<br />
<br />
How is it secured. How is the data disposed of.<br />
<br />
E.g. What does Blue Cross want?<br />
(not necessarily the clinician)<br />
<br />
Once you collect it, you can assign filters (provider view, Payer view, my view) Realistically, the way data is exchanged betweenthe participants is hopeless. They just donât sync.<br />
<br />
So the payer might foot the bill for the solution just to know whether someone is adhering to the drug administration requirements.<br />
<br />
Adherence might be a little dicier⦠âCan it answer âdid he take his medsââ<br />
<br />
Sean talks about the Persistence Curve⦠in terms of the revenue to the Pharma company⦠People who take their meds all the time have fewer incidence of medical treatment<br />
<br />
Sean â you still need the education.<br />
<br />
Observation â 70% of the pills advertised directly on TV are prescribed.<br />
<br />
What weâve learned in the past few months is that the Apple App Store has broken the back of the monitoring business. There are lots of apps for people to monitor their activity<br />
<br />
Jim Morris says â the medical profession feels like they are controlling us with the ânon-complianceâ issues.<br />
<br />
If there was ever a case where user empowerment this is it<br />
<br />
Joe asks â have you looked at the data rights issues especially when it gets to âin aggregateâ reporting.<br />
<br />
A: in the Polka view, you should be in control of both your data and âin aggregateâ.<br />
<br />
If you can get 50 people to go into the T-test and get 10 of these. Then we will have 30-50 people to prove out. They think they can get statistically valid results with this population.<br />
<br />
The control should be imposed for both individual and aggregated data<br />
<br />
Clinical team can say what they want from the person.<br />
<br />
Give them an iPhone and the app for monitoring their activity.<br />
<br />
De-identivcation needs to take place right behind the Observation Engine.<br />
<br />
Q: who would this be targeted at. Everybody out there to monitor both healthy and unhealthy activity so you can judge what to sell them and what to charge. Also figure out whether the rest of the family is involved.<br />
<br />
Then there are people in the Disease management group who wouldnât want the data to be made available.<br />
<br />
Then thereâs the idea of monitoring peopleâs behavior or whatever on Twitter or Facebook in order to determine what they would want to market to them.<br />
<br />
The Use case is to validate the heart teamâs protocol. To prove that the tools that are out there and fun to use. âObservations or daily livingâ Also have them call on the phone in order to measure str<br />
<br />
Asa- You can set up the stream to determine that âyou pay this side and charge that sideâ. <br />
<br />
The incentive is you might get an iPhone and a Watch to get people to participate.<br />
<br />
The real dividing line is between the collection of the info and then having control over how it is disseminated and who âknows itâs me.â<br />
<br />
Insurance companies already say that they give you a better rate.<br />
<br />
The weakness is that âpeople donât input data consistentlyâ<br />
<br />
A: Beckton Dickinson has added Bluetooth to the devices that collect blood samples and all that <br />
<br />
Joe â you would set this up so people would do it because they are doing something else â a point of sale dynamic<br />
<br />
Mike â we had tracking on an iPhone (if people put in the data)⦠So we added a public/private Twitter like microblog (140 characters)<br />
<br />
Added a Type and in-depth object<br />
Added location<br />
<br />
The Tweet describes the situtation<br />
<br />
Then can add tags with Diet info and it gets mapped to the diet tool or whatever.<br />
<br />
Sean â need a perpetual carrot.<br />
<br />
Can also package it as a game.<br />
<br />
Itâs not the game device. Itâs the game dynamics and the participatory nature<br />
<br />
Thereâs a tweet-what-you-eat service <br />
<br />
Q: does this scale. Or what percentage of the population will be tweeting or not.<br />
<br />
Mike: You get monetized by the providers who will share the savings and they will publish a list of what apps are covered by a pyement provider.<br />
<br />
Info will go through the observation engine where it will become part of the aggregate.<br />
<br />
Then they will start to incentivize users in ways that make it âcompulsoryâ<br />
<br />
Joe â thereâs an insane need to understand the 5% of the people who bother to tag. But youâre going to want to reach people when they are fully engaged. And when youâre fully engaged youâre not tweeting.<br />
<br />
Sean â this idea of journaling (tracking) you do when youâre training for a marathon.<br />
<br />
Thereâs a book called âFlowâ where they gave people pagers, and you have to write down what youâre doing. The pager prompted them to âtweet nowâ at specific intervals.<br />
<br />
The system must be hardened against going down. E.g. when you put the healthcare in the middle (like when someone has a needle in a vein)â¦<br />
<br />
One of the things we started implementing, included location (named, address or lat/long) <br />
<br />
We learned that âhealth is untouchableâ because of HIPAA and that sort of thing.<br />
<br />
Location is the same thing. People want to protect it. âI donât want people to know my health status (until I do) or my location (til I do). Health emergencies break that mold.<br />
<br />
Joe recommends watching âSubsidized Fateâ â¦<br />
<br />
Because people that want to use our data will use game design to add the dynamics and participation that we require.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Expressions_of_Relationships&diff=4168Expressions of Relationships2009-12-09T18:50:26Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>These are my rough notes of what is being written on the flip chart during the VRM meeting breakout on 2006-01-25.<br />
<br />
==Relationships vs. Expressions==<br />
* [http://socialcustomer.typepad.com/vrm_expression_matrix.pdf Relationships v. Expressions (PDF)]<br />
<br />
==Types of Relationships==<br />
* marriage<br />
* business partnership<br />
* counselor<br />
* subscription<br />
* friendship<br />
* family<br />
* membership<br />
* fanboy<br />
* contract<br />
* employment<br />
* confucian<br />
* mentor / advisor<br />
* citizenship<br />
* blacklist<br />
* champion<br />
* familiar stranger<br />
* colleague<br />
* teacher<br />
* stalker<br />
* neighbor<br />
* patron<br />
* customer<br />
* vendor<br />
* circle of trust<br />
* sponsor<br />
* priest / shaman / rabbi / ...<br />
* advocate<br />
* alumni<br />
* nemesis<br />
* cohorts<br />
* shared experience<br />
* enemy<br />
<br />
==Expressions of Relationships==<br />
You know it is a relationship when ...<br />
* there are implications for the future<br />
* expectations<br />
* recognition<br />
* subscription<br />
* payment<br />
* tipping<br />
* genealogy<br />
* hate sites<br />
* strong feelings<br />
* recommend<br />
* contract<br />
* employment<br />
* ask advice<br />
* expose yourself to vulnerability ("trust")<br />
* blacklist<br />
* conversation<br />
* stalking<br />
* repeat patronage<br />
* badmouth<br />
* reliance<br />
* federation<br />
* referral/introduction<br />
* sponsor<br />
* invite<br />
* rebuff<br />
* evaluate<br />
* hug / PDA<br />
* advocate<br />
* commenting (e.g. blogs)<br />
* give gifts<br />
* find<br />
* respond<br />
* keep apprised<br />
* request<br />
* extend credit<br />
* support<br />
* vouch<br />
* shared experience<br />
* having coffee<br />
* conferences<br />
<br />
==Dimensions==<br />
* Time<br />
* Transparency<br />
* Intensity<br />
* Frequency<br />
* Commitment<br />
* Control<br />
* Potential to real<br />
* Latent to explicit<br />
* Reciprocity<br />
* Symmetry<br />
* Frequency of interaction<br />
* Cardinality<br />
<br />
== Some interesting questions / thoughts ==<br />
* Are we presuming that relationships are bidirectional? (e.g. crush) No ...<br />
* Relationships are not boolean -- there is a degree, e.g. very close vs. "have heard of some guy.."<br />
* Law/lawyers as a source of a relationship taxonomy<br />
* Confucianism as a source of relationship taxonomy<br />
* A social network that doesn't allow you to include your enemies isn't worth having.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Committees&diff=4167Committees2009-12-09T18:50:26Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>Committees are based on goals that have been articulated and agree at the VRM meeting that took place at Google offices in Mountain View, CA on 2nd December 2007. <br />
<br />
<br />
<br />
== VRM Vision Committee ==<br />
<br />
Dean Landsman & Doc Searls & Jerry Michalski & Charles Andres & Keith Hopper & Adriana Lukas & Iain Henderson & Deb Schultz & Alan Mitchell<br />
<br />
<br />
== [[Standards_Committee | VRM Standards Committee]] == <br />
<br />
Brett & Drummond Reed & Alan & Joe Andrieu & Paul & Iain Henderson<br />
<br />
''Requirements that came out of a '''Change of Address Use Case''' analysis:''<br />
<br />
* Address stored independently of any particular vendor<br />
* Owner of address can choose who stores canonical source<br />
* Data should be in an open format and portable without data or service loss<br />
* Data transfer/portability is always under user control<br />
* Vendors can discover the appropriate service for each user<br />
<br />
== VRM Organisation Committee ==<br />
<br />
Doc Searls & Brett & Charles Andres & Joe Andrieu<br />
Charter process for subgroups see [[http://wiki.idcommons.net/index.php/Working_Groups]]<br />
<br />
<br />
== VRM Usage Committee ==<br />
<br />
Adriana Lukas & Chris Carfi & Deb Schultz & Alan Mitchell & Dean Landsman & Sean Bohan & Kaliya & Bart Stevens<br />
<br />
[[What is to be done?]]<br />
<br />
== VRM Compliance Committee == <br />
(and Standards? see VRM Requirements and specs)<br />
Iain Henderson & Brett</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Information_flow&diff=4166Information flow2009-12-09T18:50:25Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Khopper</p>
<hr />
<div>As it emerged at the white board during a VRM session at [http://iiw.windley.com/wiki/Workshop2006b Internet Identity Workshop].<br />
<br />
http://cyber.law.harvard.edu/projectvrm/images/c/ca/Vendor-relationship-management-flow.jpg<br />
<br />
Some prose describing this diagram on [http://netmesh.info/jernst/Digital_Identity/doc-searls-vendor-relationship-management.html Johannes Ernst's Blog].<br />
<br />
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Upside-down buyers' guide]: a simple flow for, for example, ordering servers, using an RFQ microformat and the existing Technorati tag system.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Mailing_list&diff=4165Mailing list2009-12-09T18:50:24Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>[http://cyber.law.harvard.edu/lists/info/projectvrm The list.]<br />
<br />
[http://cyber.law.harvard.edu/lists/subscribe/projectvrm Subscribing.]<br />
<br />
Post by mailing to projectvrm AT eon.law.harvard.edu.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=PayChoice&diff=4164PayChoice2009-12-09T18:50:24Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>Note: PayChoice is the name of a company and not an available domain name. [[EmanciPay]] is a new name for the model, which we are vetting at the [[VRM West Coast Workshop 2009]]. Go to [[EmanciPay]] for current editing on the subject.<br />
<br />
=== Overview ===<br />
PayChoice is a new business model for media: one by which readers, listeners and viewers can quickly and easily pay for the goods they use â on their own terms, and not just those of suppliers' arcane systems.<br />
<br />
The idea is to build a new marketplace for media â one where supply and demand can relate, converse and transact business on mutually beneficial terms, rather than only on terms provided by thousands of different silo'd systems, each serving to hold the customer captive.<br />
<br />
PayChoice is a breed of VRM, or Vendor Relationship Management. VRM is the reciprocal of CRM or Customer Relationship Management. VRM provides customers with tools for engaging with vendors in ways that work for both parties. PayChoice is one of those tools. Or a set of them.<br />
<br />
=== Background ===<br />
We now live in a media environment where goods previously sold directly or paid for by advertising are freely available and shared widely over the Internet. A number of factors contribute to a business and social conundrum for suppliers of those goods:<br />
<br />
* Easy copying and sharing makes the goods freely available at growing ease and convenience.<br />
* Copying and sharing is so widespread and common that punishment for copyright and other usage violations touches only a small minority of offenders, and has proven to be a losing proposition.<br />
<br />
What the marketplace requires are new business and social contracts that ease payment and stigmatize non-payment for media goods. The friction involved in voluntary payment is still high, even on the Web, where one must go through complex forms even to make simple payments. There is no common and easy way either to keep track of what media (free or otherwise) we consume (see [[Media Logging]]), to determine what it might be worth, and to pay for it easily and in standard ways -- to many different suppliers. (Again, each supplier has its own system for accepting payments.)<br />
<br />
PayChoice will create a &quot;buy button&quot;-simple payment system to allow readers, listeners and viewers to pay whatever they like, at their discretion, for whatever media products they use. For too many media the traditional business models -- subscriptions, newsstand sales, advertising and underwriting -- are not sufficient. (Especially in the current economic environment, which is akin to an earthquake that won't stop.) Nor do they support full participation and involvement with their users.<br />
<br />
PayChoice differs from other payment models (subscriptions, newsstand, tip jars) by allowing the customer to pay any amount they please, when they please, with minimum friction -- and with full choice about what they disclose about themselves. PayChoice will also support credit for referrals, requests for service, feedback and other relationship support mechanisms, all at the control of the user. For example, PayChoice can provide quick and easy ways for listeners to pay for public radio broadcasts or podcasts, for readers to pay for otherwise &quot;free&quot; papers or blogs, and paid request for stories or programs to be expressed and aggregated, without requiring the customer to disclose unnecessary private information, to become a &quot;member&quot;. This will scaffold real relationships between buyers and sellers, and for supporting journalists covering what Jake Shapiro calls &quot;microbeats.&quot; It will also give deeper meaning to "membership" in non-profits. (Under the current system, "membership" means putting one's name on a pitch list for future contributions, and not much more than that.)<br />
<br />
PayChoice will also connect the sellers' CRM (Customer Relationship Management) systems with customers' VRM (Vendor Relationship Management) systems, supporting rich and participatory two-way relationships. In fact, PayChoice will by definition be a VRM system.<br />
<br />
=== Micro-accounting ===<br />
<br />
The idea of [http://en.wikipedia.org/wiki/Micropayment "micro-payments"] for goods on the Net has been around for a long time, and has recently been revitalized as a potential business model for journalism by [http://www.time.com/time/business/article/0,8599,1877191,00.html an article by Walter Isaacson] in Time Magazine. What ProjectVRM [http://blogs.law.harvard.edu/vrm/2009/02/11/paychoice-for-newspapers-and-everything-else-thats-free/ suggests instead] is something we don't yet have, but very much need: ''micro-accounting'' for actual uses. These including reading, listening and watching.<br />
<br />
Most of what we now call "content" is both free for the taking and worth more than $zero. How much more? We need to be able to say.<br />
<br />
So, as currently planned, PayChoice would -<br />
# Provide a single and easy way that consumers of âcontentâ can become customers of it. In the current system -- which isn't one -- every artist, every musical group, every public radio and TV station, has his, her or its own way of taking in contributions from those who appreciate the work. This can be arduous and time-consuming for everybody involved. What PayChoice proposes, however, is not a replacement for existing systems, but a new system that can supplement existing fund-raising systems -- one that can soak up much of today's MLOTT: Money Left On The Table.<br />
# Provide ways for individuals to look back through their media usage histories, inform themselves about what they have been enjoying, and to determine how much it is worth to them. The Copyright Arbitration Royalty Panel (CARP), and later the Copyright Royalty Board (CRB), both came up with ârates and terms that would have been negotiated in the marketplace between a willing buyer and a willing sellerâ â language that first appeared in the 1995 Digital Performance Royalty Act (DPRA), and tweaked in 1998 by the Digital Millennium Copyright Act (DMCA), under which both the CARP and the CRB operated. The rates they came up with peaked at $.0001 per âperformanceâ (a song or recording), per listener. PayChoice creates the âwilling buyerâ that the DRPA thought wouldnât exist.<br />
# Stigmatize non-payment for worthwhile media goods. This is where âsocialâ will finally come to be something more than yet another tech buzzmodifier.<br />
<br />
All these require micro-accounting, not micro-payments. In fact micro-accounting can inform ordinary payments that can be made in clever new ways that should satisfy everybody with an interest in seeing artists compensated fairly for their work. An individual listener, for example, can say "I want to pay 1¢ for every song I hear on the radio," and "I'll send [http://www.soundexchange.com/ SoundExchange] a lump sum of all the pennies wish to pay for songs I hear over the course of a year, along with an accounting of what artists and songs I've listened to" -- and leave dispersal of those totaled pennies up to the kind of agency that likes, and can be trusted, to do that kind of thing.<br />
<br />
Similar systems can also be put in place for readers of newspapers, blogs and other journals.<br />
<br />
What's important is that the control is in the hands of the individual, and that the accounting and dispersal systems work the same way for everybody.<br />
<br />
=== Projects ===<br />
<br />
To work, PayChoice needs to have its choices informed. For that there should be a number of tools in the [[Media Logging]] toolbox. The first we're working on is a [[Listen Log]] called [[ListenLog]] for the [http://publicradiotuner.org Public Radio Tuner].<br />
<br />
=== FAQ ===<br />
''Q: Who would want to use it and why?''<br />
<br />
Right now supporting otherwise &quot;free&quot; journalism ranges from difficult (setting up separate paid relationships with each journal or broadcast station, each with its own rules and procedures, with all data stored in the journal or station's system) to impossible (no means are provided at all). Even the membership systems of public broadcasting exclude vast numbers of people who would contribute &quot;if it was easy&quot;. PayChoice will make it easy for consumers of media to become customers of media. It will allow those customers to pay for what they want, when they want, and to initiate actual relationships with the news organizations they pay -- on their own terms as well as those of the news organization.<br />
<br />
''Q: What potentially bigger thing might happen if everything went perfectly and the stars all aligned?''<br />
<br />
A much more healthy media business would arise out of the one that's failing -- at least economically -- right now. In the process, the media business would no longer be required to depend entirely on advertising, newsstand sales, subscriptions and donations because a new and far more accountable system would be in place. It would, for example, provide a way for any journalist or journalistic organization in the &quot;long tail&quot; to find paying customers for their work.<br />
<br />
''Q: Is PayChoice a micropayments model?''<br />
<br />
No. Paychoice will involve what might be called "microaccounting," however, by keeping logs and histories that inform the user about what media content he or she has consumed. This will aid in valuing that content. Users will also be able to set what might be called "microprices" on items such as songs heard on radio and other music streaming sources, such as Pandora or Last.fm. A listener could, for example, say he or she will pay 1¢ per song, and have payments roll over when they reach a sum large enough to make the transaction worthwhile. Willingness to pay can also be aggregated among multiple users. There are lots of ways to arrange this. But micropayments have proven problematic so far and we have no intent to visit the same problems with PayChoice.<br />
<br />
''Q: How will you be able to measure whether or not PayChoice has really made a difference?''<br />
<br />
The primary measure would be monetary -- measurable as cash income to news producers from the consumers who, by paying, would become customers as well. Goals and benchmarks for measuring social effects would be established.<br />
<br />
A secondary measure would be membership activities other than those surrounding transaction.<br />
<br />
''Q: What un-met need does PayChoice answer?''<br />
<br />
Media need a new business model. In spite of the shift of advertising from other media to digital ones, little of this money finds its way to supporting, for example, participatory journalism, where so much good and pioneering work is taking place.<br />
<br />
PayChoice will create that model. It will also go beyond monetary support to include means for establishing working relationships between the buyers and sellers of media products, so demand can find supply and vice versa.<br />
<br />
There is also the need to address the likelihood that advertising -- the primary source of income for many media enterprises -- will either be severely diminished or go away, simply because ways will be found for demand to find supply that are more efficient than the guesswork that advertising involves. PayChoice will be one way to take advantage of this inevitable shift in the marketplace.<br />
<br />
[[Category:Media Logging]]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Scenarios&diff=4163Scenarios2009-12-09T18:50:22Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>'''VRM Scenarios''' ([http://www.socialcustomer.com/2007/01/vrm_scenarios.html source])<br />
<br />
There are many different implementations of scenario planning; the one here is a modified version of the one described [http://web.archive.org/web/19961127115652/www.wired.com/wired/scenarios/build.html here] and originally pioneered by [http://www.gbn.com/ColumnListDisplayServlet.srv?col=10 Peter Schwartz at GBN].<br />
<br />
So, the two big questions: <br />
<br />
'''Q1:''' Who controls the interactions between vendor and customer?<br><br />
'''Q2:''' Are the interactions focused on transactions or relationships?<br />
<br />
This gives us a universe as follows:<br />
<br />
http://www.socialcustomer.com/images/vrmscenarios.png<br />
<br />
It's important to note that the object of this exercise is most emphatically NOT to "predict" which of these four areas will "win." Instead, it's to draw a vivid caricature of each world, and determine its key traits. Doing this allows us to better plan for, and recognize, instances of that particular scenario when we run across it in the future.<br />
<br />
'''Discussions for the four quadrants'''<br />
<br />
[[Minority Report]]<br><br />
[[Me-Ville]]<br><br />
[[The Global Village]]<br><br />
[[The Matrix (Blue Pill)]]<br><br />
<br />
'''Hybrid scenario(s)?'''<br />
<br />
The above scenarios are designed to characterize "a market". But even today there are many markets, segmented by industry (e.g. real estate vs. groceries), scale (wholesale vs. consumer), locality, price/quality bracket, and (sometimes) subcommunity. What kind of scenarios can be developed for the interplay and coevolution of disparate markets, and shifting utilization of different market types?</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM_Workshop&diff=4162VRM Workshop2009-12-09T18:50:21Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>#REDIRECT [[VRM Workshop 2008]]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Standards_Committee&diff=4161Standards Committee2009-12-09T18:50:20Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>The objective of the Standards Committee is to<br />
'''Ensure the Development and publishing of open standards and specifications for VRM services'''.<br />
<br />
This page will be the central point of organization for the committee.<br />
<br />
The near term strategies of the standards committee are three-fold:<br />
#Work on VRM [[Services]], starting with the [[Personal Address Manager Service]], which started life as the Change of Address Use Case at IIW2007b.<br />
#Develop an organizational capability in creating and working with use cases<br />
#Regular bi-weekly teleconferences.<br />
##[[Standards Committee Teleconference 2009 01 21]]<br />
##[[:Category:Standards Committee Teleconferences]]<br />
<br />
#Regular quarterly face-to-face meetings<br />
<br />
If you would like to contribute to these efforts, please email [[mailto:joe@switchbook.com Joe Andrieu]], the chair of this committee and we can arrange for you to join the Standards Committee mailing list. (This is a working list for the committee, not the discussion list of item 1 above.) Please specifically mention the Standards Committee so I can distinguish your interest from general VRM inquiries.<br />
<br />
You might also want to review the [[Initiatives]] page, which was an early draft of a proposed process for developing VRM standards. Our language has changed a bit and we will not be focusing on Use Cases rather than initiatives, but we will be doing much of the same work.<br />
<br />
[[Standards Committee Face to Face 2008 October]]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Category:Standards_Committee_Teleconferences&diff=4160Category:Standards Committee Teleconferences2009-12-09T18:50:19Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Joe.andrieu</p>
<hr />
<div>This pages links to all of the Standards Committees Teleconference notes</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Media_Logging&diff=4159Media Logging2009-12-09T18:50:17Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Dsearls</p>
<hr />
<div>Media Logging is required for [[EmanciPay]] to work.<br />
<br />
EmanciPay is a new business model for media in which the users of media pay what they please for what they consume. By sharply reducing the friction involved in paying for media, EmanciPay involves much higher percentages of the media-consuming public in the marketplace for media. And, as more people start paying for the media they consume, EmanciPay will help stigmatize non-payment for media that is otherwise free.<br />
<br />
For EmanciPay to work, users must be informed about what media they consume. It must answer questions such as,<br />
#What (is or) was that?<br />
#Who (is or) was that?<br />
#Who produced that?<br />
#Who (are or) were the sources for that?<br />
#When and where did I (listen to, watch or read) that?<br />
#How often did I (listen to, watch or read) that?<br />
#Do I have a relationship with the source? (Such as membership, past transactions or correspondence)<br />
<br />
To make sure everybody in the media value chain gets properly credited -- and paid, if we wish -- we need a system for what we're calling ''ascribenation'': the ability to ascribe or attribute credit to a source (or sources) of information used in any media item -- radio programs, blog posts, newspaper stories, or whatever. This way, if the user wishes, he or she can use EmanciPay to indicate the intention that ascribed sources might also receive some of what is paid. More under [[Ascribenation]].<br />
<br />
EmanciPay's first effort toward media logging is the [[Listen Log]] that will make its first appearance as the [[ListenLog]] on the [http://publicradiotuner.org Public Radio Tuner]. Development work is described at [[ListenLog]].<br />
<br />
[[Category:Media Logging]]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Project_VRM_talk:Community_Portal&diff=4158Project VRM talk:Community Portal2009-12-09T18:50:11Z<p>Joe.andrieu: Reverted edits by Kelebek (Talk) to last version by Jromano</p>
<hr />
<div>hi, my company is http://www.dataforcecrm.com. We are an on demand VRM that does what this site describes in the real world with customers like Intel. <br />
<br />
Jim</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM2008&diff=4005VRM20082009-12-01T08:37:54Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by PhilWhitehouse</p>
<hr />
<div>This is the base page for VRM2008 at the European Identity Conference in Munich April 21-22, 2008.<br />
<br />
If you are at the unconference, please feel free to contribute here. Just click the edit button. If there is no edit button, first create an account or log in. Once you are logged in, you can also click on the "edit" links for each section.<br />
<br />
==Sessions==<br />
This will become a session list. Enclose Session names in double brackets and it will become a link to a separate page for that session. This is the easiest way to create a new wiki page for your session. Even better, if you prepend the session name with VRM2008, we can guarantee it will be unique for the unconference. Then you can use a "pipe" | character to have a more user friendly name. See the Personal Address Manager session for an example:<br />
* [[VRM2008 Personal Address Manager|Personal Address Manager]]<br />
* [[VRM2008 User-centric Search|User-centric Search]]<br />
* [[VRM2008 Higgens/OpenIDSAML InfoCards as VRM enabler]]<br />
* [[VRM2008 VRM and Advertising]]<br />
* [[VRM2008 Phil and Paul get married (BT)]]<br />
* [[VRM2008 Rel Button]]<br />
* [[VRM2008 Business Value/Aspects of VRM]]<br />
<br />
==Attendees==<br />
Please feel free to add yourself as an attendee, with any contact information you might want to offer to others interested in VRM.<br />
*Doc Searls<br />
*Joe Andrieu (facilitator) mailto:joe@switchbook.com<br />
*Bart Stevens (facilitator) mailto:bart.stevens@ichoosr.com<br />
*Charles Andres mailto:candres@parityinc.net<br />
*Phil Whitehouse mailto:phil.whitehouse@gmail.com<br />
*Paul Downey<br />
<br />
==Thanks==<br />
Joe Andrieu and Bart Stevens would like to extend a special thanks to Kuppinger Cole and Joerg Resch for their gracious support and sponsorship. This meeting wouldn't have been possible without them.<br />
<br />
We'd also like to thank all the participants who took the time to join us for the conversation. You are the folks who create the potential for meetings like this to create real value for all of us.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=R-button_Functional_Specification&diff=4004R-button Functional Specification2009-12-01T08:37:43Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Christophercarfi</p>
<hr />
<div>(Some suggested spec categories if you're looking for a place to get started [[User:Khopper|Khopper]] 17:45, 2 September 2008 (EDT))<br />
<br />
== Universal Characteristics / Attributes ==<br />
<br />
== Core Capabilities ==<br />
<br />
<br />
== R-button States ==<br />
<br />
[[Image:pic1.jpg]]<br />
<br />
[[Link to Drummond Reed explanation of each R-button state]]<br />
<br />
== Expected Behavior ==<br />
<br />
<br />
== Design Affordances ==<br />
<br />
<br />
== Use Cases ==</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Services&diff=4003Services2009-12-01T08:37:40Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Joe.andrieu</p>
<hr />
<div>'''''Working Draft'''''<br />
<br />
An introduction to VRM Services and how Use Cases inform our work on VRM. (Formerly called Use Cases.)<br />
<br />
==Existing Work==<br />
*Service/[[Use Case Brainstorming]]<br />
*[[Services Under Development]]<br />
**[[:Category:Working Draft|Working Drafts]]<br />
***[[Personal Address Manager Service]]<br />
<br />
==Definitions==<br />
First, a Service is a bundle of functionality that provides a complete set of value for users.<br />
<br />
Second, A Use Case is a distinct, complete transaction between an actor and the system. A service is a collection of supported Use Cases. <br />
<br />
; Transaction: an actor initiated interaction with the system to produce a specific benefit.<br />
<br />
; Actor: any entity, human or automated, that initiates and drives a transaction in order to create value for itself or its beneficiary. Users include end-users, administrators, vendors, vendor's CRM systems, and customers. Every VRM Service will be developed with specific focal actors in mind while incorporating the needs of all supported users.<br />
<br />
; System: An implemented service that provides a bundled set of functionality for actors. VRM Services implement a few focal use cases and multiple supporting use cases in order to provide value to actors. Think of Services as a convenient way to organize VRM functionality into implementable systems.<br />
<br />
==The Requirements Model==<br />
Third, in developing a complete VRM Standard, we will create several documents, which will define exactly what value the system will product for which actors. These documents together comprise the Requirements Model for the Standard.<br />
<br />
; Actors: A list of all Actors supported by the system.<br />
; Roles: A list of all Roles support by the system, specifying one or two focal Roles. Roles specify an Actor in terms of their relationship with the system so that we know why they are interacting, what they need to do, and what they expect from the system. More formally, a Role is an abstract collection of needs, interest, expectations, behaviors, and responsibilities characterizing a relationship between a class or kind of actors and a system. <br />
; Role Map: A visual representation of the supported Roles and their relationships to one another.<br />
; Profiles: A detailed description of each Role's expectations, capability, and requirements for the system, forming an operational context for that particular role. Developed to enough detail to distinguish what this particular Actor needs from the system design.<br />
; High Level Use Cases: A list of all supported use cases in the system, identifying all focal and required use cases by title, ordered by priority.<br />
; Scenarios: Prose descriptions of a Role'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 />
; Abstract Use Case Narratives: An implementation and technology-free chronological ordering of Actor intention and System responsibilities for a particular use case. Based on one or more specific Scenarios. The abstract narrative defines 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 />
; Specific Use Case Narratives: Implementation-specific sequences of Actor 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 />
; Use Case Diagrams: 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: A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.<br />
; Constraints & Requirements: In addition to responding to specific use cases appropriately, every 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. When mapping out the first use case, it became clear that 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 Change of Address service VRM-compliant. That led directly to a handful of simple requirements that assure the user and vendors have appropriate access and controls.<br />
; Technology Review: A review of existing technologies that can be leveraged to implement a complete service, either directly--by incorporating the technology into a deliverable solution, or indirectly--by learning from the technology to assure a more complete solution.<br />
; Formats & Protocols: The data formats and protocols that are required for implementing the service. This includes interoperable data formats as well as open standard transport protocols for moving data around.<br />
<br />
==Standards and Compliance==<br />
Third, we propose that any implementation that fully implements all of the normative requirements of the Requirements Model for a VRM Service, including all constraints and interoperability requirements, meets the VRM Standard for that Service.<br />
<br />
Toward that end, the normative documents for the Requirements Model will be drafted, revised, and vetted via an open process, accessible to anyone. Our expectation is that the governing committee of the VRM effort, and the VRM Standards Committee in particular, will oversee the development of new services from brainstorming through to publication. The VRM Standards Committee will Propose complete standards to the governing committee once sufficient development and public review demonstrates to the committee that such a standard is ready for publication. Ultimate authority for publication will remain with the governing committee itself; we anticipate VRM Standards being published as "Recommendations" in similar spirit to long standing Internet Engineering Task Force (IETF) practices.<br />
<br />
The VRM [[Compliance Committee]] will oversee compliance to published standards, authenticating vendors right to claim their technology or services are "VRM Compliant."<br />
<br />
==Process==<br />
As a Service is defined by its working group, it will proceed through different levels of maturity.<br />
<br />
;Working Draft: any work at a stage before the working group considers it to be a complete spec. Straight numeric progression of versions, e.g., WD 1, WD 2, etc. <br />
;Working Specification: approved by the working group as a specification, but not yet at the stage where it has been approved by the VRM powers-that-be. At this stage the key goal is to âproveâ the spec via implementations and interop testing. A Working Specification can go back into more Working Drafts if the Working Group decides further revisions are needed. Another straight numeric progression of versions, i.e., WS 1, WS 2, etc. This level is achieved by a majority vote of the members of the Working Group.<br />
;Recommended Specification: A Working Spec that has been approved by the VRM powers-that-be. A âfinalâ VRM standard, fixed by version # and suitable for widespread adoption. To become a Recommended Specification, a Working Specification must go through a minimum public review period and have some number of interoperable implementations (OASIS is three; donât know about IETF). Also another numeric progression of versions, i.e., RS 1, RS 2, etc. This level is achieved by a majority vote of the VRM Steering Committee.<br />
<br />
==Work in Progress==<br />
The VRM initiative is early in its development. The proposed processes are likely to evolve over time. Given the fluid yet inherently dated nature of wikis and web pages, any particular document may or may not reflect the current--or ultimate--disposition of the VRM community. However, we have to start somewhere. We look forward to your input.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Events&diff=4002Events2009-12-01T08:37:21Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Judi</p>
<hr />
<div>==Future Events==<br />
<br />
* [http://cyber.law.harvard.edu/projectvrm/VRM_East_Coast_Workshop_2009 VRM East Coast Workshop 2009], 12-13 October 2009 at Harvard Law School, Cambridge, MA.<br />
* [http://cyber.law.harvard.edu/projectvrm/VRooM_Leadership_Workshop November 2009 Leadership Workshop], Location TBA<br />
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop 2009 (IIWIX, IIW)], 3-5 November 2009 at the Computer History Museum in Mountain View, CA.<br />
<br />
==Past Events==<br />
<br />
[[VRM West Coast Workshop 2009]]<br />
<br />
[[VRMworkshop]] at Harvard Law School, July 2008<br />
<br />
[[VRM Hacker Session]] November 9th 2007 London<br />
<br />
[http://www.supernova2006.com/ Supernova] 20-22 June, 2007 San Francisco<br />
<br />
[http://conferences.oreillynet.com/os2007/ OSCon] 23-27 July, Portland<br />
<br />
[http://conference.digitalidworld.com/2007/ Digital ID World (DIDW)] 24-26 September 2007, San Francisco<br />
<br />
[http://www.windley.com/events/iiw2007a/announcement Internet Identity Workshop (IIW)] May 14-15, 2007, Mountain View, CA<br />
<br />
[https://events.projectliberty.org/details.php?id=11 Identity Open Space (IOS)], 26-27 April, 2007 Brussels<br />
<br />
[[Notes from VRM & Public Media Workshop]] at the Berkman Center, April 4, 2007<br />
* Includes follow-up brainstorming ideas from April 6, 2007<br />
<br />
[http://cyber.law.harvard.edu/identity/Mobile_Identity_Workshop Mobile Identity Workshop], January 26, 2007<br />
<br />
[[Notes from VRM Meeting]], January 25, 2007<br />
<br />
[[Notes from Internet Identity Workshop 2006b]], December 4-6, 2006</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Interesting_Links&diff=4001Interesting Links2009-12-01T08:37:02Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Downes</p>
<hr />
<div>[http://cyber.law.harvard.edu/ The Berkman Center for Internet<br />
<br />
Stephen Downes - Distributed Digital Rights Management<br />
-- (The 'VRM' of this website is the 'Customer Broker' of the Downes presentations)<br />
-- [http://www.slideshare.net/tag/ddrm Slide shows on DDRM]<br />
-- [http://odrl.net/workshop2004/paper/odrl-downes-paper.pdf Distributed Digital Rights Management: The EduSource Approach to DRM] - presented at ODRL 1.0</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Notes_from_VRM&diff=4000Notes from VRM2009-12-01T08:36:59Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Khopper</p>
<hr />
<div>''Notes from the notetaker: There was so much covered and so much discussed on this day - I did not attempt to scribe the event. Alas, below are merely my own self-directed thoughts that emerged. Please add your own if you were present.'' -[http://cyber.law.harvard.edu/projectvrm/?title=User:Khopper Keith Hopper]<br />
<br />
<br />
'''Objective:'''<br />
<br />
How can the public broadcasting audience member take greater control of their relationship with public media? (â¦and as the audience becomes the former audience, how does this relationship change?)<br />
<br />
<br />
'''Background Thoughts:'''<br />
<br />
* Relationship does not equal transaction â in envisioning a vendor relationship tool, we need to think beyond just financial transactions (e.g. donation software)<br />
* Incremental, internal change is not what weâre looking for here. Instead, letâs identify new ideas for experimentation on the fringes of the industry. These ideas should allow individuals to flex their creative consumer muscles in this new participatory landscape. Existing public media, broadcasters, shows, and distributors will serve as the relationships, platform, and ethos to leverage<br />
* Letâs not attempt to address or work inside the existing public broadcasting infrastructure â a better strategy might be to 'end-run' a solution that imagines new ideas from a variety of committed individuals and asks for permission from the stations, shows, and distributors to explore these ideas. If the ideas get traction, the existing players can get involved to their level of comfort and in the ways they see valuable<br />
* There seems to be an overlap between what's going on in participatory culture and what exists in public broadcasting. The potential exists to tap a whole new generation of creative consumers who will 'discover' public broadcasting and want to adopt it for its potential as a non-commercial, open network designed explicitly to serve the public. Can we stimulate this adoption?<br />
[[Image:public-radio-participation.jpg]]<br />
<br />
* Can we reduce the friction of listener giving? Perhaps provide a capacity to donate directly to shows/programs?<br />
* Project VRM shouldnât code software, but rather lay out ideas, standards, and support for others who can<br />
* What's the device that will eventually replace the radio? How will this impact public radio and the relationship with the (former) listeners?<br />
* What does the long tail of public media look like? <br />
** Leverages democratized tools of production and redistributable media<br />
** Leverages the cheap, fast, and widespread distribution of end-to-end environments and the benefits of aggregation<br />
** Uses filter technology to drive demand down the tail<br />
* If we were to reinvent public radio in an end-to-end environment like the internet, what would it look like? How would it compare to what exists, and what important differences might emerge? Can we fill those gaps?<br />
<br />
<br />
'''Ideas for action:'''<br />
<br />
* Make public radio the 'test project' for a vendor relationship management tool<br />
* Provide a capacity for end-users to publish their iTunes playlists of public radio podcasts â provide a tool or environment that aggregates and features listener playlists<br />
* Is there stuff we can do with RDS (or HD, PAD, etc.), such as publish texting codes for listeners to use in providing feedback or funding linked to specific stations, programs, and times?<br />
* Use the existing NPR podcast directory as a platform for additional capability â specifically, experimentation with an online donation linked to podcasts<br />
* Get a conversation or survey going with the end-users, mashup folks, or those formally known as the audience to get a better idea of needs/desires and to brainstorm ideas for creative production/control over public media<br />
** As a creative consumer, what is it that I want to do with public media? What are my 'lego blocks'?<br />
* Investigate a new model for a public radio station ''not'' centered on broadcast<br />
** Embrace end-user control over programming, funding, content creation, and overall relationship<br />
** Incorporate participatory programming direction (e.g. guest programmers, vote programs into timeslots, etc.)<br />
** Incorporate online-only shows; act as test market for new shows<br />
** Re-invent the traditional show model (ala Radio Open Source) to be truly conversational and participatory (What might this look like?)<br />
** Use financial models like fundable.org to collect threshold capital to fund desired programming<br />
** Use a small terrestrial station to carry stream and get CPB certification and permit audio use in podcasts (whatâs the secret, here?)<br />
* Build a configurable and redistributable âuser-as-public-radio-stationâ model, integrating various streams and podcasts from around the web into a cohesive and personalized internet public radio station (e.g. KPR = Keith Public Radio)</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Privacy_issues&diff=3999Privacy issues2009-12-01T08:36:54Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Bbenz</p>
<hr />
<div>Hereâs a possible VRM privacy model for discussion, based on [http://www-306.ibm.com/software/data/db2/eas/anonymous/ existing tools that I work with at IBM]<br />
<br />
As a real-world example, Iâm planning on switching cell-phone carriers in February this year, and I also need a new cell phone. In this case, I could enter my needs into a VRM system, which would anonymously store them (in a centralized database via a Web site/Web service, or locally to some kind of P2P client.). <br />
<br />
As for how to store the info and identify needsâ¦. Somehow we have to be able to identify the cell phone needed. I suppose that UPC codes could be used or some other identifier, translated from a master list of products offered. The cell phone plan entry is a little more nebulous. Not sure how that one would be identified, other than needs based on a customer formâ¦.minutes needed, family plan, coverage, etcâ¦.(Iâll just skip over this little part for nowâ¦..:)<br />
<br />
After the needs are recorded, they would be anonymized via a one-way hash (we currently use the [http://en.wikipedia.org/wiki/SHA-1 SHA-1] algorithm). The original data is still in its original state, but only accessible to the person who created it. Other customers can not see any data but their own.<br />
<br />
Hashed entries are stored separately and available for querying by Vendors. Vendors would have to register to receive a shared hash key. That key would allow Vendors to query customer needs, but only for products that they provide, via unique, shared codes. <br />
<br />
Vendors can not see customer data. They can only query data with products that they have on offer, via a unique shared ID. The VRM system notifies the customer when a match is found, not the Vendor.<br />
<br />
The VRM system could optionally notify the vendor when a match is found, for statistical purposes (comparing hits to products sold, for example), but this binary hit/no hit value is all the vendor would have. The customer remains anonymous until they choose to purchase a product or service. <br />
<br />
Customers that are notified when a match is found would be anonymously directed to a Web page or Web Service with an offer for the specific product that they are looking for. It is then up to the customer to decide if they want to pursue the product with that vendor (take the relationship to the next level).<br />
<br />
If the offers are all Web Service based, tools could be built to aggregate and compare offers that are returned when needs are recorded. Going even further, the tools could be built to link to product and service reviews, and complete the transaction once a decision is made. <br />
<br />
In my real-world example, I would shop for a cell phone and service options online, anonymously, and decide on one or more products that Iâm interested in, pretty much the same way I do now. I would then record my cell phone preferences and service needs in the VRM system. My needs would be hashed and added to the hash values that are accessible to Vendors (via a centralized or P2P-style decentralized system). Registered cell phone vendor A can query the hashed data using the same unique IDs (UPCs or other value) that I entered when I recorded my need. If thereâs a match, I would be notified of an offer from that Vendor by the VRM system. At the same time, Cell phone service provider B could query my plan needs via shared plan IDs or via plan parameters, and offer me a cell phone and cell phone service bundle in conjunction with a cell phone provider. <br />
<br />
I would review these offers anonymously and decide which is best for me. Once I have made a decision, I would contact the vendor (via the VRM system, or directly) and proceed with the purchase. The purchase would be my first direct, non-anonymous contact with the vendor.<br />
<br />
Once a decision is reached and a purchase has been made, I would remove the record of my needs from the VRM system, and no longer receive offers for that specific product or service.<br />
<br />
Things that need more thought, more discussion:<br />
This model only works assuming multiple vendors are trying to sell you the same, somewhat easily identified product or service. For vague items that donât easily fit into this model (video service providers, holiday travel, catering, many other services), more thought is neededâ¦</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Project_ideas&diff=3998Project ideas2009-12-01T08:36:51Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Avery</p>
<hr />
<div>== Upside-down buyer's guide ==<br />
<br />
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],<br />
<br />
''Doc has been contemplating business, identity and vendor lock-in, and makes me think about an interesting experiment -- use links, tags, and a microformat to help people buy a "commodity" IT product, the 1U or 2U rack-mount Linux server.''<br />
<br />
''First step would be to come up with a microformat for a "server RFQ". At the beginning of the experiment, these could be relatively loose -- just a bunch of "ol"s with "id"s such as "required-parts" "preferred-parts", "disliked-parts", "forbidden-parts", "required-features" and so on.''<br />
<br />
''There would also be a section for "status", which would be time until buying decision, "deferred" "cancelled" or "ordered". If and when the idea got more popular, the RFQ could be more detailed, and sites and apps could offer server RFQ construction wizards. The nice thing about using a microformat is that (1) it's human-readable in a browser and (2) you can add free-form commentary on what you like or don't like in a server.''<br />
<br />
''So you want to buy a server? Write your server RFQ, put it up with a rel="tag" link to a Technorati tags page for "server RFQs". and another tag link to a new, unique tags page just for that one, such as "joe@example.com-2005-07-09".''<br />
<br />
''Along come the vendors who want to sell you a box, and are naturally watching the "server RFQs" tag like hawks, I mean like some animal that doesn't want to eat you. Like Easter Bunnies? Vendor sales person checks your RFQ, makes a page for you with links to matching products and a rel=tag link to "joe@example.com-2005-07-09". This is highly automatable, but careful, vendors -- don't spam. A future web-based product configurator should be able to crawl a server RFQ page and come up with a good quotation in response.''<br />
<br />
''Now, you, the buyer, just watch the RSS feed for joe@example.com-2005-07-09 -- hey presto, it turns into your own personalized Server Buyers' Guide! When you buy the server, you change the "status" field on the RFP to "ordered", and add a link to the vendor you bought from. This is to (1) give the good vendors Google Juice and (2) let vendors know you're serious in the future so they'll pay attention to your RFQs. ''<br />
<br />
Read the whole thing.<br />
<br />
== Categories of VRM data ==<br />
What you've done, like, and want<br />
<br />
Done: Transaction history. Your copy of your transaction/interaction record categorized <br />
<br />
Like: Preferences. Where do you like to sit on a plane, car, color, and size<br />
<br />
Want: Personal RFP. What things do you want to buy and how do you describe your need<br />
<br />
Perhaps there is a service to intelligently inform one category from another. For instance, by looking at a transaction history you can deduce preferences and suggest wants. You always want to sit in the aisle seat and buy milk every week.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=September_09_2008_Conference_Call&diff=3997September 09 2008 Conference Call2009-12-01T08:36:48Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Khopper</p>
<hr />
<div>Topic: Relbutton working meeting<br />
<br />
== Attendees ==<br />
<br />
* Keith Hopper<br />
* Dean Landsman<br />
* Iain Henderson<br />
* Britt Blaser<br />
* Matt Cooperider<br />
* Joe Andrieu<br />
* Drummond Reed<br />
* Chris Carfi<br />
* Doc Searls<br />
<br />
== Action Items ==<br />
* Drummond send out link to IDTBD google doc notes<br />
* Use [http://cyber.law.harvard.edu/projectvrm/edit/Talk:R-button discussion page] on r-button for discussion, thoughts, ideas, questions<br />
* Update format and content for [[R-button Functional Specification]] page<br />
* Dean to ask Sean and crew about "r-button"<br />
* Pick date for convening at Berkman re: VRM + Public Media<br />
** Keith check with Barbara Applebee<br />
** Who could do prototyping? Asa? Leonard Lynn? Phil Jacob? Britt Blaser? Should all coalesce in a single meeting?<br />
* Update r-button image (ccarfi)<br />
* What are those toolbar icons called in firefox?? (dsearls)<br />
<br />
== Agenda notes, questions, comments ==<br />
* Functional spec & Digital ID world<br />
** Meeting held on 9/9 on volunteered personal information button. Agreed that it should it be the same as the r-button - to be deployed by pariity<br />
* [[R-button]] page and requirements that Doc has created<br />
** Idea from Andre - browser plug-in icon (toolbar / add-on items) that represents r-button functionality<br />
* [http://barcamp.org/PublicMediaCamp Public Media Barcamp]<br />
* Use convening power of Berkman to bring together VRM incorporating a Public Media audience: show off and follow-up<br />
* Sean / marketing update<br />
** Trying to schedule a call for this week<br />
* iPhone update - budgets submitted, waiting for CPB confirmation, 'direct giving' scheduled for<br />
* Update from Digital ID World - check google doc notes on IDTBD google groups</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Taxonomy_issues&diff=3996Taxonomy issues2009-12-01T08:36:44Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Whitneymcn</p>
<hr />
<div>Very much a stub...sorry for the current "stream of consciousness" character of this -- will be cleaning it all up as soon as possible.<br />
<br />
There's <strong>a lot</strong> of work here. RFPs should allow for widely varying degrees of specificity. Ideally, a seeker should be able to create an RFP for:<br />
<ul><li>a blackberry 7130c</li><br />
<li>a cell phone with bluetooth and EDGE support</li><br />
<li>a cell phone costing less than $250</li><br />
<li>a cell phone</li></ul><br />
Even before considering the different attributes required by different types of requests (travel planning vs. product purchase, for example) it's clear that creating a workable microformat for RFPs will be a fascinating (and frustrating) process. It's worth noting, though, that work in this area pays off in many ways.<br />
<br />
Desirable: RFP attribute "package," optional, linking multiple RFPs. Indicator to vendors that the seeker is interested in the entire package (implicitly asserting that offers that cover the entire package are preferable/required? Or explicit flag?) -- plane ticket RFP, car rental RFP, hotel RFP, linked by package ID. Five different books, linked by package ID. Possibly worthwhile on both ends: seeker only wants A if they can also get B, vendor can tailor offer/discounts based on total package.<br />
<br />
Note to self: Marti's "fulfillment" RFP attribute is an elegant addition. Does seem to suggest that authoritative, verifiable identity for vendors goes from "extremely useful" to "non-negotiable," though. Note also that it makes authoritative seeker identity even more significant: if seekers provide feedback that (is | may be) used to establish vendor reputation as an evaluation factor, there's significant incentive to astroturf. <br />
<br />
Suggests the desirability of a parallel reputation system that covers both vendors and seekers. Consider how long an entity has had a public presence, RFP/feedback patterns. Unfortunately seems to also suggest that there could be an actual need for some third-part(y|ies), handling the seeker/vendor DB stuff outlined in the VRM diagram: in addition to pointers to requests/offers, the archive retains history. In this case I guess one would want as many competing versions as possible, so that clients can poll multiple and use their own systems to resolve differing data.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=The_role_of_social_enterprises_in_VRM&diff=3995The role of social enterprises in VRM2009-12-01T08:36:39Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Alan.Mitchell</p>
<hr />
<div>VRM and social enterprise<br />
<br />
Led by William Heath, Mydex.<br />
<br />
If we had an institution which got our interest in VRM going what would it look like?<br />
<br />
In the UK, we created a Community Interest Company called Mydex. I'll explain what it is in more detail in a minute, but basically it is a new form of legal entity in the UK which allows for the establishment of profit-making companies, whose core purpose is a community benefit, where most of the profits it generates are reinvested into the community 'cause'.<br />
<br />
One of our tasks is educating people around the core issues of personal information empowerment. We have to say it over and over again. <br />
<br />
Under the current status quo of organisations centralised gathering and management of customer data, they are ending up with bad â inaccurate, partial, out of date data - while losing customer trust.<br />
Customers meanwhile are having to dealing with many different silos, which they find frustrating and difficult.<br />
The VRM Mydex process puts you in control, you can choose who you do business with. It can invoke independent assertions. Work with added value services.<br />
When individuals are empowered to manage their own data in this way, companies benefit too because they are fed with accurate, timely quality data.<br />
So Mydex is creating an interface which individuals feel they can trust and which is under their control.<br />
<br />
Mydex's formal statement of social purpose is that it âlets individuals realise the value of their personal dataâ. Key characteristics of a CIC are:<br />
it works in benefit of community<br />
has the advantages of commercial company â it can take risks, make a profiit <br />
but these profits have to reinvested into its purpose<br />
transparency of operation<br />
directors can be reasonably paid<br />
regulated dividend<br />
No tax advantages but relatively light touch regulation-<br />
<br />
There are different types e.g. not for profit cooperative, vs limited by shares.<br />
<br />
If a dedicated institution -<br />
what is its scope: what's in it and what's not?<br />
what characteristics âwhat does it need to do to earn its users' trust and love?<br />
global v local; what is its global dimension, what is its local dimension. If it is global, what organisational structure should it adopt. Amex or Visa?<br />
<br />
Points from ensuing discussion<br />
<br />
It needs to be sustainable.<br />
<br />
Reliable<br />
<br />
What Governance would people actually trust? It needs to be open.<br />
<br />
Immutability so that it can't metamorphose in front of your eyes, to become something other. By regulation; charter.<br />
<br />
Alignment to purpose<br />
<br />
Leavability â right to delete me. Exit.<br />
<br />
Transparency of governance, process, finance.<br />
<br />
No cabals (or do cabals sometimes exist only in the mind of the critic?).<br />
<br />
Community should be able to kick out directors/accountability. <br />
<br />
Open standards.- in a 'global' or local context?<br />
.<br />
All contracts should be public; all specifications for data etc should be public<br />
<br />
Portable data.<br />
<br />
More on Global vs local: <br />
is it one single corporation; federated â a group of the willing. A coalition.<br />
Clearly some aspects have to be local. Probably some aspects that have to be global.<br />
e.g. language, local law. <br />
Use global to avoid reinventing the wheel â good ideas can be globally accessed. Use the crowd sourcing to your advantage.<br />
<br />
It should be the people's Google, (whatever that means<br />
<br />
instead of creating global entity, create an entity that defines the community, and let them define their own extensions, and define their own versions. <br />
That model should be chaoridc.<br />
<br />
If global, what is our 'community'? Idea of a global definition/guidelines to make this work, is interesting. Technologies, resources, knowledge, influence, relationships.<br />
<br />
Degree of proactivity. e.g can raise a war chest to tackle issues the community don't like. e.g to sue evil doers. Talking about compliance â need to protect interests.<br />
Different means of of proactivity â campaigning, dealing with issues once, for all.<br />
<br />
Want to be able to innovate â leadership, structure, incentives, On the other hand, don't want politbureau style.<br />
<br />
Design things so that everybody can do it: a mental model <br />
<br />
scalable, extensible, interoperable;<br />
<br />
agnostic about technology<br />
<br />
What are the metrics for Mydex to measure its service to the community?.<br />
<br />
Money flows:<br />
corporate fees<br />
value added services<br />
VPI fees<br />
member/supporter contributions<br />
membership subscription<br />
<br />
The money flows must be aligned to the community interest. <br />
Is Mydex sharing its revenues with me, or is the individual sharing some of its revenues with Mydex.?<br />
<br />
Auditability/track how my data is being used. Very like banking: storing personal information so that it earns interest, being loaned to vendors.<br />
<br />
Non-discriminatory pricing and access models.<br />
<br />
A personal data union.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM2008_Phil_and_Paul_get_married_(BT)&diff=3994VRM2008 Phil and Paul get married (BT)2009-12-01T08:36:14Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by PhilWhitehouse</p>
<hr />
<div>Phil Whitehouse and Paul Downey presented their early thoughts on VRM.<br />
<br />
Paul presented a slide deck which can be seen here: http://www.slideshare.net/psd/vrm-wedding/<br />
<br />
Phil then presented a TiddlyWiki file showcasing Getting Married as a case study. This file can be seen here: http://www.osmosoft.com/wedding<br />
<br />
This led towards a discussion on the potential role of brokers in a VRM engagement. A blog post and video exploring this idea can be seen here: http://philwhitehouse.blogspot.com/2008/04/vrm-tiddlywiki.html</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=VRM_Marketing&diff=3993VRM Marketing2009-12-01T08:36:05Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Judi</p>
<hr />
<div>Scumbag Marketers-<br />
<br />
Dean lays down the law :<br />
<br />
We need enterprise buy in for this to work. (meaning large companies, brick n mortar and online and have CRM)<br />
<br />
Don has brought up there there are a lot of companies that might want to sell what looks like CRM and it might not be with the best intent.<br />
<br />
Itâs all about money and they may say âwhatâs in it for me?â<br />
<br />
We have a few candidates in mind ⦠we know the right person there. Itâs the highest of C persons because it has to come from the top or else weâre fighting our way through all the little fiefdoms⦠Because they have to be told<br />
<br />
Pushback â Chris: look at Frank Eliason at ComcastCares who did grassroots, Twitterbased end-run. <br />
<br />
Deb-Based on experience with P&G going to the top and pushing down even with smart big companies could be hard. So higher ups and infulentials<br />
<br />
* Weâve agreed on Influentials and horizontal<br />
<br />
Phil Wolff â another challenge, might be to understand the systems they are using and pull through with an existing vendors. <br />
<br />
Sean, VRM isnât going to replace CRM⦠Itâs not a replacement⦠Think about Oracle/Sun for example, they may be incorporating VRM into part of their solution.<br />
<br />
* So we have to take a multi-pronged approach <br />
* We have to target each and speak in their language.<br />
<br />
Gam â At sephora, they started at the top and were pushed progressively down to the group that was doing Facebook and they were only interested in their âthe Fan siteâ so then it got totally diffused and sent out.<br />
<br />
Sean says weâre tight but we still donât talk in a way that has appeal horizontally among non-geeks<br />
<br />
Doc says that there are a few people who get it the first time out. And now we (this group) needs to get out their with a set of stories that highlights the curb appeal<br />
<br />
Weâve played down the marketing VRM until some code has been written and there are some examples out there.<br />
<br />
Weâve been watching the best people rising and the people who really get it doing some cool stuff.<br />
<br />
Now within 6mo to a year. Weâll have PublicRadio. Weâll have Gamâs thing andtcetera. And Debâs gonna have the one pager.<br />
<br />
Debâs observation â there are all sorts of consultants saying âyou donât bet itâ and evangelizing around Searchi optimization and blogging.<br />
<br />
Deb has community managers at CPG, that means they get that. The future of e-commerce is the next step and âthis is it.â<br />
<br />
Dean is channeling Allan â he says that weâre making a statement and getting internal buy in. The mission now should be to get buy in from them and get them to pay something like $10K. <br />
<br />
Deb says, they need a real story.<br />
<br />
Chris says â We have two products now⦠One was VRM⦠The next one is a very distinct product which is âa seat at the table to influence creation of VRMâ<br />
<br />
It is Access, privilege and Influence and it should have a price attached to it.<br />
<br />
Don â there is definitely value to them. We just have to bring it to their attention.<br />
<br />
Chris is saying once again that it has value to them<br />
<br />
There will be more of a story when the ClueTrain Manifesto update comes out it will clarify the connection. <br />
<br />
Conceptual DNA exists.<br />
<br />
Doc says also â by bureaucratizing what we do, some good things happened, but thereâs some organization issues. <br />
<br />
* Joyce, Judi, Dean and Renee are going to blend things back together. Renee Lloyd has the best way to articulate this and get the organization.<br />
<br />
Dean: Big Company buy in will get companies getting big and small companies interested. <br />
<br />
Doc has confidence that the major CRM companies are going to buy into this. Doc is planning to have a combined CRM/VRM session and CRM will sponsor, attend and bring customers.<br />
<br />
Q: is there going to be a certification process. And The 4th party concept will be baked in. And certification will protect the concept and clarify. There will be a VRM seal of approval.<br />
<br />
Per Dean: VRM as a brand is not sexy⦠And itâs not our consumer brand.<br />
Doc says that like the word ATM, people use them but necessarily use the term<br />
<br />
Seanâs observation â the name isnât as important as the fact that we have more clay on the piece and, besides, the naming folks at McCann or whatever will âmake a hashâ of any name we might come from<br />
<br />
Philâs idea â there are two sides that will make this work. Weâve been focusing on the plumbing side⦠And not the moms and pops or the people that are using it.<br />
<br />
Sean is saying that there are stories to be told <br />
Deb says that we need the idiot CNN reporter can say the narrative<br />
<br />
Jeff Schwartz⦠Agreed that itâs not ready, <br />
<br />
Chris Anderson and Tim OâReilley are not sold on it. But some others might be.<br />
<br />
Sean: need the manifesto, need the North Star, <br />
<br />
Paul: thereâs not one user story, There are many orthogonal ones.<br />
<br />
Deb: What we should do is have Sean, Doc or Dean give their elevator pitch.<br />
<br />
And Whatâs your story to Mom.<br />
<br />
Dean â Big go hears: These days we know that people have more communications platforms where you hear them speak. They are telling you what you had used as predictive, you can now get directly from them.<br />
<br />
We enable this data to come in and we make it so you can use info from both sides.<br />
<br />
Deb: weâve heard that this is social media stuff is happening. Does it help me sell more stuff.<br />
<br />
Paul â said that thereâs a fourth party story for the shopper.<br />
<br />
Doc: starts with a question:<br />
<br />
Which do you hate more, loyalty cards or bad customer service? And dependeing on which one you go down that path. <br />
<br />
Then the story is that the companies are already outsourcing their customer service to you. This is your chance to take better control of that.<br />
<br />
Jeff asks: why would a vendor want you to give control to the customers?<br />
<br />
Doc: Ask what do you hate most about your business<br />
A: Guesswork⦠You can get rid of the waste that occurs because of guess work<br />
<br />
* Weâre equipping pull as VRM turns push into pull.<br />
<br />
Thereâs so much buzz about listening to your customer and enterprise âgets thatâ but theyâre using market research data, customer research, and market effectiveness studies.<br />
<br />
We need to use âthe equippingâ word⦠Ergo not the monitoring stuff<br />
<br />
Don â the difference between marketing sales⦠Tell the marketing guy that VRM shortens the sales cycles, increases loyalty, costs lessâ¦<br />
<br />
Sales guy ⦠you tell them that they gotta have it.<br />
<br />
Jeff Schwartz â says the good thing is to say things<br />
<br />
Cover Fear of loss and Desire for gain<br />
<br />
Sean says â this levels the playing field between big companies and you. You can interact with them eye-to-eye, peer-to-peer. No more loyalty cards. Iâm doing it to GM⦠<br />
<br />
Leveling the playing field is the big deal.<br />
<br />
Philâs asking whether we have a shopping list regarding the talent we need <br />
<br />
Sean says that we need a grassroots movement sort of structure.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=User_Driven_Services&diff=3992User Driven Services2009-12-01T08:35:59Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Judi</p>
<hr />
<div>User Driven Services â Joe Andrieu<br />
<br />
Introduced a series of blog posts for user driven services<br />
See blog: [http://blog.joeandrieu.com/]<br />
<br />
Issues that arose that led to the idea of user driven services to tackle the general issues of interactions between individuals and a system<br />
<br />
See blog for definitions<br />
<br />
But in general â a System is something built for a particular goal<br />
<br />
User is an individual â not a computer an actual individual<br />
<br />
Services is an interaction that creates value<br />
<br />
User driven service definition<br />
<br />
âServices that maximize value creation by maximizing user control and authority.â<br />
<br />
There are a spectrum of possibilities<br />
<br />
And there is a continuum of âuser driven servicesâ<br />
<br />
You could argue that Google, for instance, is very user driven⦠on a first order level<br />
<br />
But they donât conform to many of the characteristics<br />
<br />
# impulse form the User<br />
# Control<br />
# Transparcncy<br />
# Data portability<br />
# Service endpoint portability<br />
# Self hosting<br />
# User generativity<br />
# Improvability<br />
# Self-managed identity<br />
# Duty of Care<br />
<br />
Question - what do you see as the value of adding all these criteria over the relatively random stuff thatâs going on<br />
<br />
Answer from Joe â this is the basis for many conversations. And the conversation regarding VRM was always future. User-driven gives a way to ground it in specific instances⦠like whether a mobile app to tie into a company internet, he wanted to make it more user-driven.<br />
<br />
Weâre part of a huge transformation of our society, started with The Enlightenment⦠just figuring out what it means on the internet<br />
<br />
Doc: the problem comes up even since Ben Franklin⦠<br />
<br />
Added it includes time travel⦠The pace of correspondence is so much faster<br />
<br />
Added 4th party discussion makes it more easy to define crisply and clearly <br />
<br />
Now we need to define what âfouth party isâ because âvrm is not about user-driven, itâs about how the end-statement changes everything.â Itâs transformational if you can address the end-state<br />
<br />
User-driven has instances. Whereas Fourth-party is a category of participant or service provider (not always acting on behalf of the user)<br />
<br />
Google figures that they would win in the âopenâ game with their semantic labeling and they expose their APIs to let them <br />
<br />
Joe â for Switchbook, we think our algorithms are better.<br />
<br />
Issue raised â âUser driven works for some ?? and not othersâ¦<br />
<br />
Doc says â the characteristics define a number of bullets that dictate how you let people in without locking them in and locking them down.<br />
<br />
Joe â like Umar Haque (phonetic)â¦<br />
<br />
He has some this and shares the core tenet that, weâre not doing a moral argument. Weâre coming from the idea that thereâs money left on the table because of faster response time and less waste. <br />
<br />
Itâs economically stupid to do it the old way.<br />
<br />
Service enpoint portability â you can change service provider without anyting falling apart<br />
<br />
Self-hosting = you control the dagt<br />
<br />
User-generative = means that the user should be able to add value<br />
<br />
Improvability is the âAâ in NEA⦠<br />
<br />
Self managed ID â to be dealt with<br />
<br />
Duty of care <br />
<br />
Docâs question â who does this apply to? Different users may attach more or less importance to each one<br />
<br />
But the service provider has to do them all and be responsive to all requirements and maintain sustainable advantage⦠But not locking people in.<br />
<br />
1) reprise: Impulse of user - this is not about data mining⦠it is about the system responding to a gesture of intent.<br />
<br />
The internet is really good at this.<br />
<br />
Q: is this really targeting individuals⦠The service needs to be at the architectural level and this is about an individual interacting with a service (that could be a 4th party interacting with a 2nd party on behalf of the first party)<br />
<br />
E.g. that will come up is a personal RFP⦠but it might benefit from group interaction because it could be group buying <br />
<br />
e.g. might be eBay because it aggregates a whole lot of sellers.<br />
<br />
Alan Mitchell â says that your describing a cell that interacts with a larger organismâ¦<br />
<br />
A: This is the pattern of behaviors that make the cell survivable for the organism to live. Itâs that system level that Iâm trying to describe<br />
<br />
Doc: a distinction is that we start with the individual (cell) how do we give it the right nutrients to support VRM, not just consumer â like Consumer Reports. Thatâs not are starting point. <br />
<br />
Joe: itâs part of our Jui Jitsu⦠where we shift the weight.<br />
<br />
Don Marti talks about the upside down buyers guide â putting the buyers in control<br />
<br />
2) control â Users control the services⦠E.g. can<br />
<br />
Control is not a great word â but the gang put that down. Users should have control<br />
<br />
Also comment that service provider should respect the directives of the user.<br />
<br />
Issue is whether this expects too much of the user. You could also grant it to tohers.<br />
<br />
Doc â we are pouring all sort of responsibility on the users⦠BUT SO ARE VENDORS â with self-service and all. But then again, we can make control as simple as possible.<br />
<br />
The issue is whether there is a âstandard default arrangementâ (policies) which is how the things are all the time.<br />
<br />
The fact is that if people donât vote⦠Theyâre happy.<br />
<br />
Itâs something you tackle at the policy level⦠it is distributable, but fluid. Bo said âepisodicâ you care to control what you care about it.<br />
<br />
Next up (not discussed ) is âterms of serviceâ that VRM assertsâ¦<br />
<br />
â¨Transparency is straightforward â people let you know what they want you to know⦠Alain asked does it apply to all the discounts and incentives etc⦠<br />
<br />
A: this is about increasing value by maximizing control and authority<br />
<br />
Q2: this is a principle of design â so it has to do with how the service is designed.<br />
<br />
A: well the system does require design..<br />
<br />
Q3- therefore the user is not in control and itâs not transparent.<br />
<br />
A: the people who design the system define reality. Because weâre using Web technology and thatâs already defvined. But the term âtransparencyâ has a waterâs edge.<br />
<br />
But the question is, âWhere do you draw the line?â like motives, margins and incentives are a big part of transparency.<br />
<br />
Allainâs answer is that âfor a fourth party serviceâ transpareny has to include motives and incentives.<br />
<br />
Is transparency âfull disclosureâ <br />
<br />
A: there are five categories of transparency⦠<br />
<br />
This is a new dimension of the Caveat Emptor akin to the FDA having all the <br />
<br />
Transparency is not a âdictateâ it is something that user driven services will need to be survivable⦠and it means clear understanding of policy.<br />
<br />
Alain â weâre getting to the heart of the organizational world where the vendor needs to assert what it does not intend to be transparent.<br />
<br />
Darius â in the real world, the service provider will publish service agreements and people will operate under it and it will either work or it wonât.<br />
<br />
It is not the primary place where people make a decision.<br />
<br />
Q: is there a registry where people could log on and check <br />
<br />
Bill Washburn â there should be a dialogue around a quantitative approach to transparency to a qualitative view regarding âwhat should be the major areas of concern.â <br />
<br />
So this will be rescheduled to tomorrow.<br />
<br />
Suggestion is to talk about âdefining 4th party services in a way that would have a ârulebookâ with criteria that should be conformed toâ<br />
<br />
Joe was wondering whether you could apply these criteria to Web based activity⦠like SMTP or Web Hosting.</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=PAM_One_night_Stands&diff=3991PAM One night Stands2009-12-01T08:35:56Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Ekivemark</p>
<hr />
<div>This VRM Workshop session covered the concept of the Personal Address Manager.<br />
<br />
The scene setting points covered:<br />
<br />
First Assumption - Privacy<br />
Differences from long running relationships<br />
- Mutual policy negotiation - pain-free<br />
- Default policy bucket<br />
- No identifier<br />
Easy to produce end of relationship artifacts<br />
Win-Win for customers and vendors<br />
- Removing barriers to exit is attractive.<br />
A use case was examined: Single Stop Online Shopping <br />
<br />
With Address<br />
With Personal Delivery Service (eg. relationship wth UPS, Fedex etc.)<br />
With Vendor Delivery Service (eg. Vendors own delivery service that respects PAM token)<br />
With Address from Personal Address Manager<br />
<br />
Is the "With Address" scenario a Personal Address Manager (PAM) case? However the PAM might be the place where user relationship policies are stored. "With Address" was eliminated as a policy statement by vendors.<br />
<br />
The "with Delivery Service" was selected to analyze.<br />
<br />
'''Roles: '''<br />
Shopper (S:)<br />
Merchant (M:)<br />
<br />
'''Assumption:''''''Bold text'''<br />
Policy Assurance and Warranty<br />
<br />
'''Scenario:'''<br />
Step 1. <br />
<br />
S: Shop at a compliant store <br />
<br />
M: Offer VRM ("use VRM" button on the web page)<br />
<br />
Step 2.<br />
<br />
S: Click "Use VRM"<br />
<br />
M: Endpoint Request<br />
<br />
Step 3.<br />
<br />
S: VRM Discovery End point - ie. PAM Address pointer<br />
<br />
M: Push to provision<br />
<br />
Step 4.<br />
<br />
S: Provision vendor<br />
<br />
S: Give Vendor token (with policy)<br />
<br />
M: Policy agreement <br />
<br />
M: Use token to get address<br />
<br />
M: Use Address<br />
<br />
M: Delete<br />
<br />
M: Confirmation of End of use <br />
<br />
<br />
Side notes:<br />
<br />
Initiatives are underway to build a policy framework. (SAML and WS-Policy?)<br />
<br />
<br />
<br />
This was a complex discussion to develop the scenario. Edits to refine this discussion can be made on the VRM Workshop Wiki in the Personal Address Manager page.<br />
<br />
Also posted to [http://ekive.blogspot.com/2008/07/vrm-and-personal-address-manager.html EKIVE Blog]</div>Joe.andrieuhttps://cyber.harvard.edu/projectvrm/?title=Personal_Data_Stores&diff=3990Personal Data Stores2009-12-01T08:35:51Z<p>Joe.andrieu: Reverted edits by KruGer (Talk) to last version by Judi</p>
<hr />
<div>Drummond Reedâs â Personal Data Store<br />
With Iain Henderson to address as well<br />
<br />
On Board:<br />
<br />
PDS:<br />
<br />
What should be in it? (at a minimum) and (ideally)<br />
Whatâs it for?<br />
<br />
What is its essential characteristics/components<br />
<br />
Where does it reside?<br />
<br />
Where does it fit in the overall OSI Model and the VRM architecture <br />
<br />
Why is it important?<br />
<br />
When is it deployed?<br />
<br />
How is it managed â what policies apply?<br />
<br />
Does it have to be standard? Cabn there be many types?<br />
<br />
What are the points of failure?<br />
<br />
Drummond â the concept of PDS has been central to VRM<br />
<br />
This is to talk about why? And to look specifically at the PDS<br />
<br />
One starting point is âWhy is it importantâ/<br />
<br />
Another is âwhat is essential?â<br />
<br />
When we wrap up, we ask â On what points are we not in agreement?<br />
<br />
Iain describes myDex though Slide show<br />
<br />
Observation â Enterprise CRM architecture have multiple attributes but only store data for a year. If well designed, âimportant dataâ will be stored in Analytical System and data warehouse. Which holds the atomic level of data and stores it for the duration of a decisionmaking cycle.<br />
<br />
Analytical systems tracks who bought what, where and why?==> to anticipate what to do next<br />
<br />
First order concern is quality â meaning completeness, accuracy and several other attributesâ¦<br />
<br />
Evidence is that âCRM Needs to be fixedâ â spending 200 bps is not enough to fulfill requirements. Okay at collecting info on customer. Not so good on tracking customer/product/outlet info in a usable fashion<br />
<br />
Definition of âPersonal Data Store â (admittedly not a helpful term) A generic term to âsource, store, enhance and selectively disclose my personal informationâ<br />
<br />
Needs to run on the same principles as the CRM⦠Systems will do the doingâ¦.<br />
<br />
The personal data warehouse is the missing element.<br />
<br />
In CRM the identity layer is at the top end<br />
PDS resides on top. With the sources <br />
<br />
Sees 3,500 attributes over 70 years (is what each individual has)<br />
<br />
''(Thematic) Individuals have less tools, more attributes to control, fewer resources to monitor and track.''<br />
<br />
Craig Burton â it is important and extensible as well. <br />
A: So you need to identify the important attributes versos <br />
<br />
To determine whatâs important, just identify what info you might need to get your life started again.<br />
<br />
Next slide depicts Interactions and transactions with all sorts of businesses and govât entities. With the Identity Layer at the core.<br />
<br />
*No CRM database can handle persona so you go about creating multiple ones to transact and interactx in the world.<br />
<br />
Important â This is a logical design, not a physical designâ¦<br />
<br />
It has been posited that Interactions are whatâs being monitored and that Transactions are a type of interaction.<br />
<br />
Joe Andreiu â says we can get to the Model T version that does okay <br />
<br />
Next slide â Current state of Who has what data⦠<br />
<br />
Was My Data, Your data, Everybodyâs Data, âTheir Dataâ<br />
<br />
Everybodyâs data = public domain â all sorts of data thatâs avaialbe.<br />
âTheir Data (or parasitic tailings) â what Experian, Acxiom etc, collect about you<br />
<br />
Your dat â include a vendors products /services, policies, pricesâ¦<br />
And guesses regarding view of a customers preferences, requirementsâ¦<br />
<br />
Our Data â identifiers, clams,/Assertions and transactionsâ¦<br />
<br />
MY DATA â is stuff known only to me⦠Circumstances, Assets, Liabilities, preferencesâ¦<br />
<br />
There are also back channels which are interactions between the parasites, vendors, and the publicly available stores.<br />
<br />
At Liberty Alliance they have been discussing âVolunteered Informationâ<br />
<br />
Finally, Thereâs the Target State<br />
<br />
In 10 years time 80 percent of customer management prcesses will startywith âMYDATAâ (me) <br />
<br />
So the customer will be in more control and overt interactions will be between the vendor <br />
<br />
Toxic will be bad for both vendors and customers â they destroy trust.<br />
<br />
''Drummond â 3 times Iâve heard that âThe customer is the point of integrationâ (which originated from Joe Andrieu)''<br />
<br />
âCustomer as Point of Integrationâ<br />
<br />
Joe says âAnalysis and Insightâ revolved around the vendor data⦠It is the source of Googleâs competitive advantage ⦠<br />
<br />
Craig Burton â but Googleâs source of distrust was doing personal data storage for Google to tag and index<br />
<br />
PDS has âroots in two placesâ<br />
<br />
1) Doc Searls â personal experience with the medical treatment across several care givers and each introduced errors in their systems so that they could not reconcile or synchronize⦠The conclusion is that it would have been more efficient and less dangerous if Doc had been the single repository providing to access to the data on an as needed basis.<br />
<br />
2) The other side is âStymergyâ which is the general term for how ants find the shortest path to food. It is also the answer to a distribution problem for multiple trucks between warehouses. They send out ants randomly, the one that comes back first, his trail is doubled.<br />
<br />
Balance between exploration and exploitation. They mark their environment. Joe articulates that the data should be stored centrally and when multiple companies or individuals want access, they should not seek out things from one another. They should get it from the individualâs data store<br />
<br />
Stuart- Why wouldnât you just ask Amazon.com or Google to do a better job of making your information accessible to other apps. So I can assemble it at my command from the multiple sources.<br />
<br />
Joeâs answer â youâre asking about data portability. <br />
Iain says (itâs because youâd be operating under their terms and conditions)<br />
<br />
Joe says it is because personal data store is not just âthe dataâ it is about setting up mechanisms for permissioning information in, out based behind your own front end (called identity)<br />
<br />
And youâre going to have all sorts of front ends or âService Specificationsâ (Liberty calls them Service Interface Specification)<br />
<br />
Status updates<br />
Addresses<br />
Music ratings<br />
Search Activities<br />
Personal RFPs<br />
Personal Healthcare records<br />
SMTP/POP<br />
<br />
And itâs all under your control<br />
<br />
Sop the question is whether the hub is about authentication (identity layer)<br />
And permissioning<br />
<br />
*** so there is a multi-billion battle raging over control of permissioning for status updates.<br />
<br />
Iain â youâre still missing the link between doing data and planning data.<br />
<br />
Doc sees the user as the point of integration and also origination.<br />
<br />
Else â a problem solving thing which gets brought up.<br />
<br />
That is the ossified way that existing systems work<br />
In medical system, fârinstance⦠there is a kiretsu of equipment providers, suppliers etc where it is hard to get data from individuals or companies. Incompatibility between media, age of PC, etc.<br />
<br />
You are going to have this architecture work better in some cases rather than others.<br />
<br />
Iain, where thereâs failure in ERP or CRM itâs because the system is trying to do too much and gets clogged up.<br />
<br />
So you need to make the distinction between getting stuff done and when you have to do long-term planning.<br />
<br />
Per Drummond â donât you end up answering the question by establishing the framework for these the service interfaces service provier (Facebook, Myspace, Plaxo)â¦. And those service providers would manage one or more of the service specification intervfaces.<br />
<br />
Joe is saying that it is easier to solve and optimize the âshortest pathâ solution for specific tasks then to define the personal data store that does it all.<br />
<br />
Iain is saying that it will have to do the analytics earlier and constantly.<br />
<br />
Architecturally you sidestep it by providing a service thatâs operational and do it in a way that is consistent with doing the analytical and do it in a way thatâs consistent with identity based permissions.<br />
<br />
So you donât have to do them all if you can solve one of them seamlessly.<br />
<br />
Drummond will explain what XDI is all about as a protocol:<br />
<br />
The idea of getting all sorts of schemas to talk to one another is a real probalem. HtML canât. XML cannot.<br />
<br />
About trusted Data sharing. And itâs about permission <br />
<br />
Craig says that XDI is not a protocol. It is a language structure <br />
<br />
He wants to know âwhat does it resolve toâ if I write a command and it gets abstracted to something that then resolves to the data and its location. So if you want to share some of your data that resides elsewhere, like in multiple banks⦠<br />
<br />
''The Data doesnât have to live at the hub⦠But control does''<br />
<br />
Craig â it resolves around a URL and then I can react to it based on a structured card<br />
<br />
Card<br />
Rule Set<br />
Data set<br />
<br />
Resolved to a URL and it gives permission to access to where that data can be found. And enable data set mashup.<br />
<br />
E.g. iphone with a GPS Google Map moment. âTell me where the lone palms hotel is in relationship to meâ tell me where I am and where I go.<br />
<br />
Itâs mashup that needs to include all that data.<br />
<br />
CyberCrack!<br />
<br />
Ad active rules to operate on your data store, and the mashup of all the services <br />
<br />
I just want to get this group to define the architecture to put it into the hands of the developer community./<br />
<br />
E.g. Amazon.comâs EC2 setting up all sort of things (like 30 years of census data) <br />
<br />
Q: When you say ârule setsâ do you just mean permissions?<br />
<br />
A: (using the MyDex example - ) as a proof of concept, no browser is required. Any program and any entity can subscribe to the other info an dlocation and all or part be âin the cloudâ<br />
<br />
Switchbook has all the info distilled on the hard drive, there is a copy in the cloud for back up purposes. It doesnât have to be in the cloud. And thereâs code in the client to handle I/O<br />
<br />
When you get to rules⦠You put functionality in the cloud that handles services and can find them in the cloud.<br />
<br />
Customer write the rules.<br />
<br />
Stuart⦠Example is embedding a twitpics or a URL in a twit⦠Iâm publishing something that can then be seen by anyone or everyone. Or how do I add a âsmart URLâ to a tweet so that I can publish to everyone, but the URL has a set of criteria behind it or around it that is controlled by the higher order infrastructure.<br />
<br />
Can use a medium like Twitter to infect the world with XDI and XRI<br />
<br />
If all or portions of your data are addressable, it can be made accessible to the rest of the world. If you make it abstract. If itâs inside the âIdentity Layerâ it can be under the control of the user. One of the key purposes of the next step, which is XDI⦠The same format says that I can store the âpermissionsâ (sometimes called ârulesâ) so that I can access the Link contract. So that the read/write instructions can attached to another set of rules to do something like letting the gas company <br />
<br />
Go To Wiki.kynetics.com (it explains the rules that Phil Wendly has developed)<br />
<br />
Joe says that Grease Monkey does it as well. But Craig Burton says that kinetics⦠is what we should be interested in.<br />
<br />
Joe says HTML 5 is being deployed now in browsers. <br />
<br />
Craig: I would strongly recommend that we do this in a way that is somewhere between Wiki-based and Selecter-based that is Strong foundation for VRM. <br />
<br />
Joe, part of this is about deployment⦠âI hate JaSon because it is inherently insecureâ but they have ways to do secure parsing of Jason⦠But it was adopted because it provided trivially easy way to do it insecurely and native to JAVAscript.<br />
<br />
We want to play friendly with them.<br />
<br />
Question, gas company needs employment data about me. 1 to 1 federation on their own terms. VRM way. Passport agency acts as a node and permissions allows Gas company to get info from passport agency. <br />
<br />
Data liquidity is what itâs all about.<br />
<br />
Read it as âpermissionedâ or âunpermissionedâ and the reason that there is so much unpermissioned is because âthereâs no technology in useâ to support permissioned. Which is an argument for Portable Permissioning.<br />
<br />
Joe-looking at Switchbook in this context is that your identity is stringly around what you give permission for.<br />
<br />
Switchbook defines you by your âsearch mapâ itâs a file that is orthogonal to all your other identifiers. Itâs Switchbox has a âSearchMapâ document at its core. It is the context where your current browsing shows where youâve been and what youâve done and all that.<br />
<br />
Idea is that we shouldnât get hung up on the protocol right now. Just define how entities interact and figure out the mesh points.<br />
<br />
In the IDWSF model, how you talk to the gas company is permissions based. They may send you an email or something and you set it up with your IDWSF model.<br />
<br />
Drummond: Now we talk about our questions.<br />
<br />
1) Why is it important?<br />
<br />
Initial â The thing that will put the individual back in control of personal information. Meaning the information that is important to the person.<br />
<br />
Itâs the store that you personally have control of, it could be anything.<br />
<br />
Will allow us to be more promiscuous with our data because we know it will be stored in a trusted way.<br />
<br />
It is a context for control.<br />
<br />
Because if you abuse it, I know your pheromone trail? <br />
<br />
Benefit is that it will improve my quality life, based on my decisions.<br />
<br />
Itâs important because it is valuable? It can be bartered><br />
<br />
It is economically transformational><br />
<br />
Jim â Like credit cards, this lowered the friction and reduces guesswork and waste from the vendor side. Which increases value. <br />
<br />
Best case you provide the best possible outcome for both parties.<br />
<br />
It is more efficiently economically. (the economy will operate more efficiently)<br />
<br />
It enables what weâre calling the fourth party services (what VRM is promising).<br />
<br />
Markâs point â Itâs a way to organize VRM.<br />
<br />
What weâre talking about as the personal data store is to create a better marketplace by providing the way the individuals are regarded by buyers/sellers/governments.<br />
<br />
It helps people organize their lives. It enhances efficiency and productivity.<br />
<br />
Framework for new use conventions that we donât foresee right now (think of browsing⦠or logging onto the bank)<br />
<br />
Itâs implementable <br />
<br />
Now letâs look to points of failure:<br />
<br />
Adriana would say that there are point-to-point identity free interactions that donât require this.<br />
<br />
Aside â Kim Cameron says that âIdentityâ is not an identifier. It is just a set of claims that require context. You can have a claimless set of claims in a container.<br />
<br />
It is about 4 different identifiers:<br />
<br />
Authentication<br />
Presentation<br />
Reference ID (how to be reached email address)<br />
Internal ID <br />
<br />
This is your identity online<br />
<br />
Are there VRM-y things that donât have a personal data store as part of it⦠The answer is noâ¦<br />
<br />
You need a place for your stuffâ¦<br />
<br />
<br />
Q: Where does it have to reside⦠It could be anywhere as long as itâs accessible by the applications<br />
<br />
Q: Isnât really a permission and control hub? Answer is ânoâ it is still about the data with rules established as to the permission and conditions under which<br />
<br />
Weâve gone in circles around what is a relationship manager as opposed to a relation service.<br />
<br />
Iain says, itâs all about how you operate around the data⦠Need to clarify how to source, store, enhance and selectively disclose data.<br />
<br />
Drummond â the other place the Identity comes in is that the idea of the role of the user in terms of control is akin to the control they have over their bank account. But the bank has authority.<br />
<br />
The relationship someone has with Equifax, for instance, is Massively Passively<br />
<br />
Another parallel is like the spam filter, where we have passive benefit but virtually no control.<br />
<br />
Jim Morris asked what this would be like if it were Communist China and there was an argument for centralized ⦠Drummond, from the point of view of market (as opposed to moral), this is the mechanism for giving user control.<br />
<br />
This is about distributed planning. <br />
<br />
Has anyone looked at giving control of the personal ID store to a centralized trusted entityâ¦<br />
<br />
Bullets for tomorrow:<br />
<br />
Privacy:<br />
*IP addresses are they tracked⦠<br />
*Iâm worried about Google tracking activity<br />
<br />
User Experience <br />
*complex<br />
*could create opportunity for errors<br />
*Mashing on toes<br />
<br />
Conformance and compliance<br />
(if I share data, how will I know if people abide)<br />
a<br />
Reputational authority (how do I know you are who you say you are)<br />
<br />
Service dependability<br />
Business dependability<br />
<br />
Portability?<br />
Inadequate choice of SPs<br />
<br />
Data Breach and fear of data breach (Honey Pot)</div>Joe.andrieu