Project VRM - User contributions [en]

Initiatives

2009-11-27T07:03:23Z

Maniac: /* Initiatives */

This page is a draft proposal and will soon be replaced by a Use Case based approach. Please send any comments to [mailto:joe@switchbook.com] or to the Project VRM [[mailing list]].

==Initiatives==
Our work is organized into Initiatives. Each Initiative is a community effort to resolve one or more related problems in vendor-customer relationships.

Initiatives begin in [[Initiative Brainstorming]], where anyone can add or expand on current ideas for ProjectVRM. Once an idea is concrete enough to receive the blessing of the community and has gathered one or more champions, it begins the VRM [[Process]]. During that process, the champions see that each step in the process is completed thoroughly enough to advance to the next step and that the Initiative advances at an acceptable pace. Some initiatives will take longer than others. Many will spawn multiple protocols. It is the champions job to facilitate the advancement of an Initiative from a good idea to a working Protocol.

Our fist initiative, still nameless (feel free to suggest one) addresses the challenge of making it easy for listeners and viewers of public broadcasting to pay for the goods they get on the radio or over the Net. Right now only 10% of those listeners contribute to their public stations  a number that would be much higher, by all accounts, if the labor and costs (e.g. getting junk-mailed by stations) were lower.

Visit the [[Initiative Brainstorming]] page for more on ProjectVRM initiatives. If you have an idea, please post it there, or vet it with the ProjectVRM community on our [[mailing list]]. We may already be working on it.

See also:
*VRM [[Process]]
*[[Initiative Brainstorming]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Scenarios

2009-11-27T07:02:06Z

Maniac:

'''VRM Scenarios''' ([http://www.socialcustomer.com/2007/01/vrm_scenarios.html source])

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].

So, the two big questions:

'''Q1:''' Who controls the interactions between vendor and customer? 
'''Q2:''' Are the interactions focused on transactions or relationships?

This gives us a universe as follows:

http://www.socialcustomer.com/images/vrmscenarios.png

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.

'''Discussions for the four quadrants'''

[[Minority Report]] 
[[Me-Ville]] 
[[The Global Village]] 
[[The Matrix (Blue Pill)]] 

'''Hybrid scenario(s)?'''

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?
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Minority Report

2009-11-27T07:01:32Z

Maniac:

'''VRM Scenarios - "Minority Report"'''

http://www.socialcustomer.com/images/minrpt.png

Vendors bring every resource to bear to extract the last bit of margin out of every customer. Targeted ads, served relentlessly and based on our past purchasing behavior, attempt to entice us to consume the next new thing. Friedman's "Flat World" observation plays out to its logical conclusion, with manufacturing and marketing, sales and service taking place at whatever patch on the globe can deliver the product most cost-effectively. Since vendors use data mining of petabytes of customer data in order to predict the next hot trend, post-sale service becomes increasingly unimportant, since product lifecycles are measured in weeks. Customer data becomes a pure commodity, created, owned and traded by vendors in the way that carbon credits and pork bellies are traded today. Vendors with economies of scale rule the day. Customers get low prices, and limited choice.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

The Matrix (Blue Pill)

2009-11-27T07:00:56Z

Maniac:

'''VRM Scenarios - "The Matrix (Blue Pill)"'''

http://www.socialcustomer.com/images/bluepill.jpg

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.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

VRM discussion in podcasts

2009-11-27T06:57:58Z

Maniac:

* Trent Adams and Steve Greenberg interview Kaliya Hamlin and Joe Andrieu: [http://feeds.feedburner.com/~r/DataPortabilityPodcasts/~5/264038613/dp_in-motion_20080404.mp3 Dataportability podcast]
* Dave Winer: [http://static2.podcatch.com/blogs/gems/snedit/cn06Dec06.mp3 MCN Tutorial on Vendor Relationship Management]
* Phil Windley: [http://weblog.infoworld.com/udell/2006/09/08.html Udell-Windley podcast]
* Gillmor Gang: [http://www.podshow.com/shows/?mode=detail&episode_id=24321 VRM Gang Part I]
* Gillmor Gang: [http://www.podshow.com/shows/?mode=detail&episode_id=24351 VRM Gang Part II]
* Gillmor Gang: [http://www.podshow.com/shows/?mode=detail&episode_id=24354 VRM Gang Part III]
* IT Conversations: [http://www.itconversations.com/shows/detail1676.html Managing Vendors Before They Manage You]
* The Story of Digital Identity [http://thestoryofdigitalidentity.libsyn.com/index.php?post_id=178699 Chris Carfi and VRM Scenarios]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Questions raised

2009-11-27T06:57:20Z

Maniac:

* VRM [[policy objectives]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Project VRM:Community Portal

2009-11-27T06:56:49Z

Maniac: /* Prior Conference Calls */

[[November 11 2009 Conference Call]]

[[September 30 2009 Conference Call]]

[[September 02 2009 Conference Call]]

==Prior Conference Calls==
[[conference call archive]]

[[:Category:conference call]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Main Page

2009-11-27T06:56:16Z

Maniac: /* Join Us! */

== About VRM ==

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.

CRM systems for the duration have borne the full burden of relating with customers. VRM will provide customers with the means to bear some of that weight, and to help make markets work for ''both'' vendors and customers  in ways that don't require the former to "lock in" the latter.

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.

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.

== Project VRM ==

[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.

ProjectVRM is headed by [http://cyber.law.harvard.edu/people/dsearls Doc Searls], a fellow with the Berkman Center.

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].

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

== VRM Principles ==

#Relationships are voluntary.
#Customers are born free and independent of vendors.
#Customers control their own data. They can share data selectively and control the terms of its use.
#Customers are points of integration and origination for their own data.
#Customers can assert their own terms of engagement and service.
#Customers are free to express their demands and intentions outside any companyâs control.

These can all be summed up in the statement ''Free customers are more valuable than captive ones''.

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.

== VRM Goals ==

#Define and advocate a clear vision for a VRM world
#Ensure the development and publishing of open standards and specifications for VRM services
#Create a lightweight and effective organisational structure
#Drive VRM usage
#Create and oversee VRM compliance program

== VRM Current Topics ==

This is a catch-all where we can point both to ongoing conversations and current development work. These include (but are hardly limited to)...

*[[Media Logging]]
*[[Listen Log]] (the general topic) and [[ListenLog]] (the development project0
*[[PayChoice]]
*[[Personal RFP]]
*[[FCRA: Access to credit data]]

== VRM Committees ==

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

== Allied Efforts ==

*[[The Mine! Project]]
*[http://mydex.org/ MyDex]
*[http://www.vrmhub.net VRM Hub]
*[http://www.vrmlabs.net VRM Labs]
*[http://publicradiotuner.org Public Radio Tuner]
*[http://www.switchbook.com/ SwitchBook]

== Resources ==

* ProjectVRM [[mailing list]]

* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]

* [[VRM FAQ]]

* VRM [Twitter stream http://twitter.com/vrm]

* Project VRM [[committees]]

* VRM and -related [[events]]

* VRM [[Initiatives]]

* VRM [[Principles]]

* VRM [[Process]]

* VRM [[scenarios]]

* VRM [[technology]]

* VRM coverage in [[blogs]]

* VRM discussion in [[VRM discussion in podcasts | podcasts]]

* [[Questions raised]] by VRM

* [[VRMcompanies]]  A list of VRM or VRMlike comnpanies

* [[Expressions of Relationships]] (notes from VRM meeting)

* [[Random Notes from Jan 25th VRM Developers Meeting]] (stream of consciousness / ears and brain to fingertips and keyboard)

* [[Website planning]]

* Other [[related efforts]]

Conference Call archive and audio links have been moved to the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Lexicon ==

* [[VRM lexicon]]

* [http://wiki.auds.org/index.php//wiki/agreement AUDS] (user driven services... name still in the works) agreement -- contains a lexicon

== VRM Events ==

[[VRooM Leadership Workshop]] will take place on 31 Oct * 1 Nov in Mountain View, CA (just before IIW9) Location to be determined.

[[VRooM Boston 2009]] took place on 12-13 October 2009

[http://vrmhub.pbwiki.com/ VRM Hub] Monthly Meetings in London

[[VRM2008]] took place in Munich on 21/22 April 2008

[[VRM Workshop 2008]] took place in July 2008 at Harvard University

[[VRM at SXSW 2009]] March 2009, Austin, TX

[[VRM West Coast Workshop 2009]] May 15-16, Palo Alto, CA

[[VRM East Coast Workshop 2009]] 12-13 October at Harvard University

== Join Us! ==

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.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

VRooM Boston 2009

2009-11-27T06:54:07Z

Maniac: /* Name */

[[Image:vroomboston2009_small.png|200px|thumb|left]]VRooM Boston 2009 will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center] in the John Chipman Gray Room in Pound Hall at [http://law.harvard.edu Harvard Law School], on Monday-Tuesday 12-13 October, 2009. The event will go from 9AM to 5:30 on both days. There will be a no-host dinner on Monday evening.

As with earlier workshops, the purpose is to bring people together and make progress on any number of VRM topics and projects. Most of the workshop will be an "unconference" on the open space model, which means session topics will be chosen by participants. ([http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]) The one exception will be [http://cyber.law.harvard.edu/projectvrm/VRooM_Boston_2009#Panel:_Getting_Personal_With_Data:_How_Users_Get_Control_and_What_They_Do_With_It ''Getting Personal With Data: How Users Get Control and What They Do With It''], described below.

== Registration ==

The workshop is free. You can register through [http://vrmeastcoast2009.eventbrite.com/ this EventBrite link].

== Possible Topics for sessions / discussion ==

(These are just suggestions. The topics can be anything.)

* VRM and Health Care
* VRM hacks, so far
* User-initiated terms of service
* Where Personal informatics / self-tracking aligns with VRM (User control of data.)
* Existing technologies and protocols VRM can use
* [http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup] (Kantara initiative) (Previously Volunteered Personal Information Workgroup)
* The Mine! Project
* MINT
* VRM and search
* Personal Data Stores
* VRM and open source
* Scanaroo (and turning loyalty cards inside-out)
* ListenLog
* Emancipay
* VRM and Identity (Information Cards, OpenID...)
* VRM and Mobile
* Personal RFPs
* VRM evangelism
* VRM and search
* VRM and Real Estate

== Open Space format ==

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

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

== Schedule ==

=== Monday ===

==== Setup and Sessions ====

''''Greetings and VRM overview by Doc Searls''''

''''Suggesting and choosing the day's session topics''''

(Wiki note takers will fill in the sessions below.)

'''''Session 1'''''
* Issues in P2P Data Storage and Exchange
* 20,000 foot view of where VRM will thrive - What areas are ripe for VRM applications?

'''''Session 2'''''
* Privacy Policy, Terms of Use, and anonymity (is it important?)
* Real estate - the need for buyer and seller-sided VRM apps

'''''Wrap-up'''''
''''' Reports from group sessions '''''

==== Dinner on Monday Night ====
Monday's dinner at at 6:30 at Daedalus in Harvard Sq. (http://www.daedalusharvardsquare.com/)

# Doc Searls
# Keith Hopper
# Dean Landsman
# Renee Lloyd
# John Eckman
# Mary Ruddy
# Andy Oram
# Alexander Torrenegra
# Charles Andres
# Sean Bohan
# Bill Wendell

=== Tuesday ===

==== Panel: Getting Personal With Data: How Users Get Control and What They Do With It ====
[http://www.google.com/search?hl=en&q=self-tracking '''Self-tracking'''] and [http://www.google.com/search?hl=en&q=personal+informatics '''personal informatics'''] are hot [http://www.selftracking.net/ new] new development categories, driven by the growing sense that primary responsibility for gathering personal data, integrating it, and putting it to use, belongs to individuals -- not to companies, governments or other organizations. Together these tools help individuals become both the [http://blog.joeandrieu.com/2007/06/14/vrm-the-user-as-point-of-integration/ ''point of integration''] for their own data, and the ''primary authority'' for what gets done with that data.

''Self-tracking'' is how individuals collect data about themselves, while ''personal informatics'' is how individuals organize that data and put it to use. Together these tools inform individuals' relationships with themselves, with their social networks, with the organizations to which they belong -- and with sellers of all kinds.

Tools for self-tracking and personal informatics are new, already becoming popular, and in need of much thinkig about how personal data is gathered, stored and shared -- concerns that are near and dear to those who follow VRM.

Each panelist is either developing tools in these categories or has experience with new tools and the issues involved. Doc Searls, of the Berkman Center and ProjectVRM, will moderate the panel, and we expect discussion with participants (there will be no "audience" here) to be lively and informative.

==== Moderator ====
'''Doc Searls''' - [http://cyber.law.harvard.edu/ Berkman Center]

==== Panelists & Their Projects ====
'''Ben Rubin''' - [http://myzeo.com Zeo]

Ben is the co-founder and CTO of Zeo Inc. Zeo has created and recently launched the world's first personal sleep coach.

'''Adriana Lukas''' - [http://themineproject.org/ The Mine! Project]

In addition to working on the Mine! project designed to turn individual user into a platform by helping him to capture, manage and share data on his own terms, she also runs [http://www.vrmhub.net/ VRM Hub] in London and disrupts companies [http://www.mediainfluencer.net/about/ for living].

'''Tim Hwang''' - [http://www.webecologyproject.org Web Ecology Project]

In addition to the Web Ecology Project, Tim Founded [http://roflcon.org ROFLCon] and [http://awesomefoundation.org The Awesome Foundation], and [http://upcoming.yahoo.com/event/2171174/ Information Superhighway]. He is working on a book on the mechanics of web culture and memes online.

'''Keith Hopper''' - [http://cyber.law.harvard.edu/projectvrm/ListenLog ListenLog]

Keith works on digital product strategy for [http://npr.org NPR]. He is the creator of [http://keithhopper.com/blog/nprbackstory NPRbackstory], was a contributing author for the book [http://www.amazon.com/Collective-Intelligence-Creating-Prosperous-World/dp/097156616X/ref=pd_bbs_sr_4?ie=UTF8&s=books&qid=1208206490&sr=8-4 Collective Intelligence], and has done some [http://keithhopper.com/about other fun stuff].

==== Sesions ====

(Wiki note takers will fill in the sessions below. The canonical session outline will be on the wall of the room during the workshop.)

'''''Session 1'''''
* [[Creating an Open Zeo ecosystem - how open should we be]]?
* [[VRM and Healthcare Session]]: Just give me the *&%^ data!

'''''Session 2'''''
* Medialogging

'''''Session 3'''''
* [[VRM Research opportunities]]

'''''Research possibilities'''''

ProjectVRM is classifed as a ''research'' project by the Berkman Center, and conducting research of some kind is part of ProjectVRM's charter. So we have a brief session near the end of the day to talk about the possibilities here, based on discussion during the last two days.

''''' Reports from group sessions '''''

''''' Wrap-up and next steps '''''

==Space/Location==

We have a the John Chipman Gray Room in Pound Hall (on the second floor) in Harvard Law School booked for both days. (Among other things, [http://thinkexist.com/quotes/john_chipman_gray/ Gray said], "âIt is a step for further advance to see what has been won from chaos already.") The room is the one over the bike racks on the south side of Pound Hall, which is on Massachusetts Avenue ("Mass Ave") next to the big construction project.

The room will have plenty of chairs and tables for group sessions.

Note: Parking is scarce and expensive in Cambridge. Public Transportation is best.

[http://cyber.law.harvard.edu/projectvrm/Image:Grayroom.jpg Here is a map] of Harvard Law School, with the John Chipman Gray room highlighted.

== Name ==

The first workshop, also at Harvard, was called just [[VRMWorkshop]], then [[VRM Workshop 2008]]. The second was called [[VRM West Coast Workshop 2009]]. We chose "VRM East Coast Workshop 2009" as a way to stay sort-of in compliance with that poor naming convention. The name "VRooM" was chosen by suggestion from the ProjectVRM mailing list.

The new workshop naming convention will be VRooM (location) (year). Until we come up with something else.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Creating an Open Zeo ecosystem - how open should we be

2009-11-27T06:52:16Z

Maniac:

Creating an Open Zeo ecosystem session

Attendees:
* John Eckman
* Tom Stites
* Ben Rubin
* Keith Hopper
* Doc Searls
* Robbin Lubbock
* Bob Wayland
* Alan Hoving

Where we have been - you use the SD card to upload your data to the web site.

What are the various ways we could open this data?

# Excel download of sleep features
# OpenAPI - access your sleep data from anywhere on the web (data export) (Read, Write, or Both)
# Aggregated data - sharing / access - how do other 40 yr old women in Duluth sleep
# Open up the data real time - data comes out of the serial port, do we publish the format
# Make it an open application platform - let other people write apps on it.

Weâre leaning towards the open platform, but we have to make sure we do it responsibly.

How many users? Largest sleep database in the world, well over 30,000 points of data.

Reach out along social media space - FB group (300 fans), twitter account (600 followers).

To what extent are you feeding conversation? (What arcana exists where people talk about what they learned from their Zeo)

People are talking about their ZQ score - weâre seeing the 1% of that online, but people are having the conversation.

Doc recommends registering the OtherThird.com - for the other third of your life which is sleep.

A. Create a planet, aggregating content from around the web about sleep - make yourself the Lord of Sleep.

B. Then, once you have some critical mass - make a big push out of the fact that the user owns their sleep data - I use a zeo, I own my sleep data.

C. Go to the users - what should we all do with this data? The people in the community. These are issues best studied in aggregate, we think there is value in it, how can we best leverage it?

---

At the end of the day, the building of a commuity around what youâre doing is where the value is - sleep optimization / sleep data / focus on sleep issues not just sleep data.

Reaching out to existing communities - where can we find folks who are already having this issue.

Doug Mayer who runs car talk forums - folks who want to answer questions versus folks with question.

---

Forum recomendations - Vanilla, Ning, BBPress,

---

What about data owership:

Weâre right at the beginning of this and we donât know whatâs around the curve. Weâve got the folks who are zealots, and folks who donât care at all, and not much in between.

You need to be able to redraw the picture as you go - drawing your picture in pencil as you go.

Youâve bitten off a market corner thatâs really large but focused.

You have to have a clear policy about the data. This policy reassures the concerned but also creates the space for having the possibility to do interesting work down the road.

What kinds of policy make sense for data usage? What should you allow or not allow?

Difficulty of traditional challenges - the default corporate culture today would be to keep the data private.

Keith - the key value here is going to be the community, which will require honestly. Also, youâre going to get a lot more exposure by being open. Finally youâre also going to get some interesting results coming out of the research.

Whats the argument to make to those concerned about regulatory issues and those from a more traditional background who worry about giving away the data?

----

What prevents a competitor from coming along and ripping off the interface and use? What would keep people from taking the SD that has the data on it and using it for other purposes?

When people impersonate you, thatâs a sign youâve won. Donât worry about Elvis impersonators - youâll always be better at it than you.
---

Devilâs Advocate positions:
- let people access their data, but only through a web API
- let people access their data off the SD card but decrypt it if you use an app where youâve accepted a developer version.

Whatâs wrong with that?

Feels like the company is setting the terms whereby the user can access his data - why is it the companies place to set these terms?

What would be better would be to say this is your data to use as you please, but here are some terms of service you should request - there are lots of people who will want your data, but this is what you should require from them.

The shift from âyou give us ownershipâ to âyou give us a right to use a copyâ in photo sharing services - there are steps beyond this you can explore.

Example: you can use this data for non-commercial, aggregate level research studies.

What you want ultimately is a trusted relationship with your community of users - thatâs a huge value if they know that they trust. Thatâs more important than the cheap opportunity youâd miss out on from selling the userâs data.

You have to be the shining example of safeguarding the users data.

Whatâs the benefit to the consumer of interacting with you? The most important thing is to build trust with the community.
- youâre gonna sleep better
- youâre gonna become part of a community
- youâll see your own behavior normalized in an aggregate set (where does my sleep disruption sit on a scale)

What will build trust?
- a user data covenant is one part of a broader picture
- accurate results, helpful results
- transparency into the data
- contest type stuff - the X prize for sleep

Open is horizontal, closed is vertical - you can do either, you can even play at both.

Apple as the prime counter example - they manage to [hdo things but stay closed.

Be ready to jump - let the market tell you.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

What is to be done

2009-11-27T06:49:32Z

Maniac:

Two approaches to driving VRM Usage

#industry and vendor driven
#web and user driven
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Committees

2009-11-27T06:49:10Z

Maniac: /* VRM Compliance Committee */

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

== VRM Vision Committee ==

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

== [[Standards_Committee | VRM Standards Committee]] ==

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

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

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

== VRM Organisation Committee ==

Doc Searls & Brett & Charles Andres & Joe Andrieu
Charter process for subgroups see [[http://wiki.idcommons.net/index.php/Working_Groups]]

== VRM Usage Committee ==

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

[[What is to be done?]]

== VRM Compliance Committee ==
(and Standards? see VRM Requirements and specs)
Iain Henderson & Brett
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Standards Committee Teleconference 2009 01 21

2009-11-27T06:48:42Z

Maniac: /* Next Meeting */

==Standards Committee Teleconference Call Notes==
Drafted by Joe Andrieu, January 21, 2009

==Other Calls==
[[Category:Standards Committee Teleconferences]]
[[:Category:Standards Committee Teleconferences]]

==Attendees==
*Joe Andrieu
*Drummond Reed

==Agenda==
#Criteria as work for committee
#Review the criteria

==Notes==

===Standards Criteria===
I'd like to move the work of the committee to focusing on an [http://www.opensource.org/ OSI] style framework for criteria for VRM Service Specifications.

We started this process in Mountain View:

http://docs.google.com/Doc?id=dc4jjg2j_141htc37p97&hl=en

With the idea that we would eventually have a list of criteria with descriptions similar to the Open Source Definition at OSI:

http://www.opensource.org/docs/osd

Joe needs to get Doc on board with this work focus. Once that happens, we'll dive in. Hopefully by next meeting.

===User Driven Services===
Joe also briefed Drummond on the conversations around User-Driven Services as a unifying term for what we are working on and how that might fit into the emerging organizational gestalt.

More as that occurs.

==Action Items==

==Next Meeting==
[[Standards_Committee_Teleconference_2009_02_04 | February 04]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

Standards Committee

2009-11-27T06:47:00Z

Maniac:

The objective of the Standards Committee is to
'''Ensure the Development and publishing of open standards and specifications for VRM services'''.

This page will be the central point of organization for the committee.

The near term strategies of the standards committee are three-fold:
#Work on VRM [[Services]], starting with the [[Personal Address Manager Service]], which started life as the Change of Address Use Case at IIW2007b.
#Develop an organizational capability in creating and working with use cases
#Regular bi-weekly teleconferences.
##[[Standards Committee Teleconference 2009 01 21]]
##[[:Category:Standards Committee Teleconferences]]

#Regular quarterly face-to-face meetings

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.

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.

[[Standards Committee Face to Face 2008 October]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

About Page

2009-11-27T06:45:15Z

Maniac:

See [[Project VRM:About]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.sempatim.net seviÅme]

September 30 2009 Conference Call

2009-11-26T21:03:52Z

Maniac: /* Doc's Book and Research */

==Conference Call Notes==
Drafted by Judi C, September 30, 2009

==IRC==
#vrm at chat.freenode.net

==Other Calls==
[[Category:conference call]]
[[:Category:conference call]]

==Attendees==
* Joe Andrieu
* Dean Landsman
* Iain Henderson
* Alan Mitchell
* Doc Searls
* Judi Clark
* Keith Hopper
* Drummond Reed

==Notes==

===Blog, Tweet our Meeting===
Please tweet using #VRM about east coast meeting. Blog about it as well, using VRM as a tag.

===Need to involve Health Care===
Dean is talking with Mike Kirkwood, Mark Scrimshire, to come to the Oct workshop. Important to get health care contingent and commercial (enterprise) world to hear benefits of VRM world
Dean suggests Doc invite Adrian Grouper; Doc saw Adrian recently at Berkman

Doc: part of what's going on with health care thing is market speaking (signal cutting out some). Couple things I want to do: put up a web page as landing site (will coordinate w Dean who owns domain and has been hosting) - right now redirects to long URL elsewhere. Doc wants to have this happen before the meeting. Also: we need an animal (mascot) to symbolize what they do. Also need a shorter name for what the workshops are (about), like IIW*. Now it's a sentence not a name. Can add location afterwords (VRM2Boston). Dean suggests using regular numbers, not roman numerals.

Alan: seems sensible.

===Doc's Book and Research===
Doc: after long period of silence, Harvard Biz Press got in touch about his book: now called Intention Economy: What happens when Customers get Real Power. Will take historical angle. Owns intentioneconomy.* - will work on site in sync w writing. On side: consulting group in London, at a meeting, most had read new Cluetrain and new VRM chapter.

At workshop, want research to be on agenda. Under new theme at Berkman, Doc has obligation to do research on VRM. Thoughts welcome on what that research might be.

Joe sent Doc a draft email re pricing mechanisms, shifts because of Internet. Dean: we need a backchannel for draft discussion. Doc: whole concept of signaling mechanisms is interesting, worth exploring. Look at Andrew McAfee's work (andrewmcafee.org @beaker) at Sloan/MIT on Enterprise 2.0 - Doc has been assigned w mentoring him. Would also like Eric von Hipple to come. (?)

Ian: re research: Kantara has some $$ to go toward consumer research.

<a href="http://www.sempatim.net/" title="video" target="_blank">video</a>

<a href="http://www.sempatim.net/" title="seviÅme" target="_blank">seviÅme</a>
<a href="http://www.bisikis.com/" title="sikiÅ" target="_blank">sikiÅ</a>
<a href="http://www.sikisme.tk/" title="sikiÅme" target="_blank">sikiÅme</a>
<a href="http://www.videolarabak.net/" title="video" target="_blank">video</a>
<a href="http://www.ekelebek.com/" title="chat , kelebek">chat</a>
<a href="http://www.oztoplist.com/" title="site ekle, toplist" target="_blank">toplist</a>

<a href="http://www.ucretsizpornizle.com/" title="porn izle" target="_blank">porn izle</a>
<a href="http://www.isexizle.com/" title="sex izle" target="_blank">sex izle</a>

===Progress report===

Joe: Eve presented where she's at (UMA) - a version of oAuth and validation to access a resource; some statement of terms, mechanism for requesting party to say they met those terms. Exterior to protocol for specifications, terms open to implementers.

Dean: any thoughts re meeting starting on 12th, also Doc re dinners? Doc: hit up JP for sponsorship. Name of place in Harvard Square...(Daedalus)

VRM vision

2009-11-26T20:51:22Z

Maniac: /* Additional Links */

VRM, or Vendor Relationship Management, is the reciprocal of CRM or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]. VRM describes a set of tools, technologies and services that help individuals go to market and manage relationships with vendors. In turn, vendors who align themselves to these tools, technologies and services will have the opportunity to build better relationships with their customers.

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.

== Principles ==

VRM recognizes a series of principles <ref>[http://blogs.law.harvard.edu/vrm/2008/07/09/because-principles-are-good-to-have/ "Because principles are good to have"], ProjectVRM Blog, 2008-07-16</ref>
. These are:
# VRM provides tools for customers to manage relationships with vendors. These tools are personal. They can also be social, but they are personal first.
# VRM tools are are customer tools. They are driven by the customer, and not under vendor control. Nor to they work only inside any one vendorâs exclusive relationship environment.
# VRM tools relate. This means they engage vendorsâ systems (e.g. CRM) in ways that work for both sides.
# VRM tools support transaction and conversation as well as relationship.
# With VRM, customers are the central âpoints of integrationâ for their own data.
# With VRM, customers control their own data. They control the data they share, and the terms on which that data is shared.
# With VRM, customers can assert many things. Among these are requests for products or services, preferences, memberships, transaction histories and terms of service.
# There is no limit on the variety of data and data types customers can hold â and choose to share with vendors and others on grounds that the customer controls.
# VRM turns the customer, and productive customer-vendor relationships, into platforms for many kinds of businesses.
# VRM is based on open standards, open APIs and open code. This will support a rising tide of activity that will lift an infinite variety of business boats, and other social goods.

== History ==
CRM systems for the duration have borne the full burden of relating with customers. VRM will provide customers with the means to bear some of that weight, and to help make markets work for ''both'' vendors and customers in ways that don't require the former to "lock in" the latter.

''TODO â details for this section:
* Where name came from
* Where idea came from (relationship with the Cluetrain Manifesto)
** Core concepts & shifting landscape: Internet increasing alienation between consumer and vendor, etc.
* How VRM has helped leverage (and tries to see ahead of) ideas being worked on in the identity space, etc.
''

== Problems With CRM ==
CRM, as originally envisaged, was a reasonably attractive proposition to the end customer. The idea was that an organisation would build a more complete view of the customer across their many touchpoints (retail, phone, email, events, etc.), and then, via investing in software, changing culture, and integrating marketing, sales and service, the organization would be able to be more responsive to the customers needs and provide more satisfying sales and service.

However, more often than not, organisations underestimated the cost of the cultural change â or decided (wrongly) they could do without it. Many also tended to focus more on the cost saving potential of the new technologies than the relationship improvement potential. But one structural problem emerged to surpass all the tactical issues with the vision or how it was deployed: ''it is impossible for any one organisation to build a comprehensive view of their customer''. Some, with great effort, can build a complete view of THEIR OWN relationship with a customer; but they will still be largely unaware of the many other supply relationships that the customer typically maintains (over 100 would not be unusual).

Only the individual, when given access to the necessary tools and processes, can create anything approaching a complete view of their supply requirements.

== Project VRM ==

''TODO â details for this section:
* Berkman Center - Steering Committee
* Doc Searls, Champion
* Objectives
''

== Challenges for VRM ==
For VRM to work, vendors must have a reason to value it, and customers must have reasons to invest the necessary time, effort and attention to making it work. Solving this "chicken-and-egg" problem for both sides is the primary challenge for VRM.

''TODO â details for this section:
* Iconoclastic anti-vendor perception
* Need killer apps
''

== VRM Capabilities & Standards ==

Following are some of the generic capabilities listed at the [http://projectvrm.org Project VRM website] that are anticipated to emerge as part of VRM adoption.

=== Personal Data Stores ===

This is a generic term for one or more services that help individuals gather, store, protect, analyze, share and use information describing themselves, their relationships, their transactions, and their intentions.

VRM envisions that personal data stores will become the means by which individuals plan, administer and organize many aspects of their daily lives as well as conduct interactions and transactions with vendors. With personal data stores, individuals will be able to pull together their own:

* Administrative records and details
* Contact databases: friends, family, colleagues etc.
* Transaction histories: products and services purchases, etc.
* Interaction histories: records of correspondence
* Supplier data ('my doctor', 'my plumber', etc.)
* Personal preferences e.g. 'favored' brands and organizations vs 'blacklisted' brands and organizations
* Plans for life projects (trips, moving home etc)
* Information gathered and collected to help inform decisions and actions about all the above.

=== Personal Data Analytics ===

Just as vendors mine and analyse the data in their CRM systems to better understand their customers, individuals will be able to mine and analyse the VRM data in their own personal data stores to better understand their needs and make better buying decisions. Personal data analytics can help users:

* Track trends such as personal spending, calorie intake, household energy usage, car mileage, etc.
* Use 'people like you' comparisons to highlight areas where their resources could be better managed.
* Anticipate and understand spending changes after major life events, such as marriage, having children, getting divorced, etc.

=== Request for Proposal (RFP) ===

A Request for Proposal (RFP) is a message sent from an individual to a company, set of companies, or marketplace declaring the individual's need for a product or service. RFPs are a "reverse market" where customers publish their needs/requirements/specifications and vendors can respond with their offer/price/terms. This creates an environment where the consumer has a direct the product or solution, as opposed to accepting a solution that by it's very nature is advantageous to the vendor.

RFPs can range from simple commodity requests (e.g. insurance renewal, new lawnmower, laptop computer) to specifications for products or services that do not even exist yet. They can take many forms:

* ''One-to-one'', where a named individual sends his request directly to one or more named companies
* ''Aggregated'', where multiple individuals' requests are collated and passed on to companies by an intermediary. Companies then respond to these RFPs either on an individual or collective basis.
* ''Anonymized'', where an intermediary informs a company or set of companies that a specific number of customers are seeking out a particular product or service, but access is only provided through the intermediary until a transaction is closed.

=== Permissions Management and Reverse Messaging ===

Though "permission marketing" has become a buzzword, in practice it has not lived up to its hype. True permission management must put the individual fully in control, allowing them to specify the "rules of engagement" for marketing relationships and to maintain that control over time.

Permissions management covers both receiving information and releasing information on a timely and relevant basis. In the former case, for example, an individual may be planning to buy a new car in June. He could specify his willingness to receive messages about new cars, in a specific price bracket, from specific brands/dealers, in the months of April and May, but be assured that all such communications will cease June 1. This is also called "reverse messaging", and its success hinges completely on the individual's confidence that they have 100% control over the reverse messaging channel, i.e., they can fine tune it or shut it off just as they can with their TV. This can be accomplished using specially-generated addresses (such as a custom email or instant messaging address) whose lifespan is controlled by the user.

Individuals can also choose what data to release to what vendors, for what purposes, on what terms and conditions. For example, a person may want to release information about:

* Medical history and lifestyle, to health researchers, on an anonymous basis, for free, for the purposes of cancer research.
* Their current inventory of hardware and software, to a specialist retailer/reseller, on a named but once-only use basis, for the purposes of advice on solving a computing problem or buying a new peripheral.
* Clothing and cosmetic brand preferences, on an anonymous basis, to marketing companies, in return for a fee.

=== Power of Attorney Services ===

Many aspects of managing a supply relationship are tedious and time-consuming, such as renewing insurance or performing scheduled maintainance on a vehicle. As a result many buyers settle for something far from the best value just to avoid the hassle.

With power of attorney services, individuals can give buying agents permission to act on their behalf, within certain parameters, without the need for specific detailed negotiation. For example, the individual may give power of attorney to the agent to sweep the market for best prices for insurance contracts with equivalent terms, one month before their current contract is due to come to an end.

=== Problem Solving Communities (PSCs) ===

Before purchasing a product or service, individuals often need to answer a long series of questions, such as:

* What are the available options?
* What things do I need to do achieve my desired outcome?
* How do I do x or y?
* What are the hidden pitfalls that I ought to be aware of?
* Who can I trust?
* Which is better for somebody in my circumstances, option A or option B?

Although online and offline services exist to help individuals in some cases, often the best source of information is other individuals facing the same decision. Problem solving communities tap this potential by collecting answers other people have discovered and making them available, avoiding the need for each new individual to reinvent the wheel.

VRM has the potential to bring real economies of scale to this process.
If it costs $100 to research and formulate a good answer to a certain question, then it adds $100 to the cost of the product or service in question. But if the same answer is used 1000 times over, the unit cost falls from $100 to $0.1: a productivity boost of 99.9%.

=== Personal Scenario Planning ===

Lastly, there are some events in our lives which few of us encounter often enough to become expert at handling them: getting married or divorced, moving, organizing a trip round the world, coping with a life threatening illness or accident, surviving the death of partner, etc.

Scenario Planning is like a specialized type of problem solving community. It identifies best practices, pitfalls to watch out for, and other essential knowledge about a key life event. For example, if you are getting married, a scenario planning service can help you organize details such as venue, ceremony, invites, attire, presents, catering, travel, honeymoon, etc.

Since many of these decisions involve vendor relationships, scenario planning can integrates many of the other components of VRM systems, bringing them all to bear to simplify what can otherwise be an overwhelming set of choices in a short period of time.

== Related Initiatives ==

=== Internet Identity ===
VRM is closely related to Internet identity for the simple reason that in order to control their own data and relationships across vendors, users must be able to assert their identity independent from any particular vendor relationship.

Widely known as "user-centric identity", this field includes technologies such as [http://en.wikipedia.org/wiki/OpenID OpenID], [http://en.wikipedia.org/wiki/I-cards information cards (i-cards)], the [http://en.wikipedia.org/wiki/Higgins_project Higgins Project], and [http://en.wikipedia.org/wiki/XDI XDI]. All of these technologies seek to provide users with a way to control their identity, data, and relationships without dependence on any one vendor or service provider.

=== Data Portability (DP) ===

[http://en.wikipedia.org/wiki/DataPortability Data portability] seeks to do for all forms of data what [http://en.wikipedia.org/wiki/Telephone_number_portability telephone number portability] has done for phone numbers. DP promotes the ability for users to move and share their identity, contacts, photos, videos, or any other form of personal data from one website or web service to another. Like Internet identity, data portability is essential to VRM because without it, users can be "locked in" to vendor relatioships and restricted from full freedom-of-choice.

=== Relationship Cards (R-Cards) ===

Relationship cards, commonly called r-cards, are a new type of [http://en.wikipedia.org/wiki/I-cards information card (i-card)] developed by the [http://en.wikipedia.org/wiki/Higgins_project Higgins Project] that enable automated data sharing relationships. R-cards can instantiate any type of relationship â person-to-person, person-to-vendor, or vendor-to-vendor â and can be used to share and automatically synchronize changes to any type of data, from an email address to an loyalty points balance to a wedding gift registry.

See the details under the Wikipedia [[http://en.wikipedia.org/wiki/I-cards i-card] entry.

== VRM Example Uses ==

''TODO â details of this section.''
List practical, leading examples of best proposed uses for VRM. Link to Use Cases (if any)
* Personal Address Manager
''

== VRM Companies ==

''TODO â details of this section.''
Companies, sellers, vendors all may have existing examples of VRM. Please post them here.
''

== Additional Links ==
* [[VRM FAQ]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

== References ==
<references />

VRM as Disruptive Innovation

2009-11-26T20:50:52Z

Maniac:

'''Session Proposal:''' Get initial traction with VRM by focusing on specific vendor problems that are best suited to VRM and specific businesses that are uniquely positioned to benefit from VRM tools.

'''Results:''' Suggestions included the USPS COA problem, personal RFP for long-tail aggregators (like etsy.com's alchemy feature), CRM-capability and donations for independent artists and SMBs, solve alias problem for DMM/Axiom/etc, sharing local health care provider data access, geographic data sharing (e.g. healthcare providers); community data banks

I've done a couple posts on this topic. More to come.
* [http://keithhopper.com/essay/why-vrm-is-good-for-business Why VRM is Good for Business]
* [http://keithhopper.com/blog/long-tail-consumer-demand The Long Tail of Customer Demand]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

VRM FAQ

2009-11-26T20:50:21Z

Maniac: /* How can companies "implement" VRM when it is the individual who is managing the relationships? Doesn't it create a conceptual mess that risks smuggling the corporation as relationship manager back in by the back door? */

== What is VRM? ==
'''V'''endor '''R'''elationship '''M'''anagement. The one-liner is that, "VRM is the inverse of CRM - [http://en.wikipedia.org/wiki/Customer_relationship_management Customer Relationship Management]".

== How is VRM the inverse of CRM? ==

== What are some typical examples of how an individual would use VRM? ==

''
* Change-of-address
* Digital receipts
* Personal RFPs
''

== Why would companies support VRM? ==

== How did VRM get started? ==

== Is there a VRM industry association? How does it represent individuals? ==

== How is VRM related to Internet identity? ==

== How is VRM related to data portability? ==

== What's a relationship button (relbutton or r-button)? ==

== What's a relationship card? ==

== Is VRM about technical standards or business principles? ==
[My question was not about technical standards versus business principles. It relates to what VRM looks like. Is VRM defined solely in terms of technical standards, or does it also include new services and business models that stand on the side of the individual when dealing with vendors and change the nature of commercial relationships? I think that clearly it has to. VRM is not just a technology.

I may have been my mis-reading the 5 levels of maturity, but the 'flavour' of what came across was that in the end, it's really all about clever new bits of technology. Alan]

Yes. It is both clever bits of code and new best practices for businesses. Doc Searls has made it clear from the beginning that Project VRM is a development project: that the end goal is working code that makes a difference in the real world. At the same time, Doc has also made it clear that the ultimate goal is fixing the marketplace, which means that new best practices '''will''' emerge.

Joe Andrieu advocates a drive towards interoperable relationship services--using both standards and running code--which will transform the marketplace by giving companies a new way to increase their profits. By giving companies a winning proposition, we can get them to adopt new methodologies and new business principles. This is similar to the way that the web was adopted because it made business sense, and as it was adopted, radically changed how companies and customers relate. Without http and HTML the transformation that enabled the Cluetrain Manifesto never would've happened, and in fact, it was the openness of those standards that enabled the world wide web to displace Lotus Notes as intranetware and AOL/Compuserve as online services. Joe sees a similar technology-led VRM revolution, where Project VRM catalyzes change by assuring standards and applications that enable individuals to play in the marketplace on their own terms in a way that also improves businesses' bottom lines.

== How can companies "implement" VRM when it is the individual who is managing the relationships? Doesn't it create a conceptual mess that risks smuggling the corporation as relationship manager back in by the back door? ==
To Sean Bohan, while the user is in charge (driving the relationship) there still needs to be some corresponding structures on the Vendor side to accept/interact/transact with that VRM'd user. There needs to be a nut for the bolt. Vendors must have some form of acceptance, some framework that can work with customers who are in charge. Compliant and Aligned both work for me, but I was trying to get across the idea that there is commitment, acceptance and more importantly, '''work''' on the Vendor's side to be VRM compliant. Doc said in the past this needs to be Win-Win for the vendors too, and "Implement" is something a BigCo guy would understand (I get something out of implementation). "Implement" may be the wrong word (it was workin form me in the wee hours of the morning) - and we can change it. I think the idea of "smuggling the corporation as relationship manager back in" is also something that needs to be discussed in the context of compliance and standards (which Brett was crystal clear on in the last call). Not sure which committee would handle that or if it is a grenade the whole group should jump on at once.

Joe Andrieu agrees: there must be a nut for the bolt '''and''' users are not going to build their own bolt. There is a need for Vendors to implement the "receiving" side of the VRM equation. This isn't about tools that are one-sided on behalf of the user. Full participation means both Vendors and individuals participate and benefit. Also, someone needs to build those tools for the individuals. In this latter sense, companies "implementing" VRM are those tool providers enabling individuals to participate in VRM relationship services.

[VRM is not SAP and the slightest hint that it is is extremely dangerous. We are talking at two different levels here. Operationally speaking, companies have to 'implement' changes to become a bolt that fits the nut. That goes without saying.

But at another psyschological/presentational level the word 'implement' fits and reinforces corporations' customer control agenda. We have to work effectively at both levels: the message to the corporation has to be 'you will only realise the win-wins by handing over control - i.e. letting the customer manage the relationship'. So it is as much about all the baggage corporate types simply assume when they hear a word, as it is about technically correct English. Alan]

Alan, respectfully, I have to disagree with the statement "the message to the corporation has to be 'you will only realise the win-wins by handing over control - i.e. letting the customer manage the relationship'." That's putting things into an extreme that is neither palatable nor necessary. I would suggest instead that what we are saying to corporations is "here is an opportunity to create more value for your customers and your bottom line. It requires rethinking what is important to you in terms of control, but at the end of the day it gives you greater predictability, better product insights, and deeper, more meaningful relationships with more loyal customers." The '''political''' argument that companies need to give up control is no more appealing to me than any of the other political consumer movements out there, from Carbon-neutral to not-tested on animals to Fair Trade. These movements (which I actually support politically) are at their core ideological and therefore subject to extreme limitations, namely a lack of common ground with those who don't agree with '''your''' agenda. VRM on the other hand, like the World Wide Web, is enabling a radically new type of marketplace that will be adopted by individuals and companies alike because it is, unequivocally, '''economically''' superior, no agenda required. No need to debate the ideology--just point to the bottom line. IMO, any other debate is unnecessarily controversial. --[[User:Joe.andrieu|Joe.andrieu]] 17:13, 18 April 2008 (EDT)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Usage Committee

2009-11-26T20:49:38Z

Maniac: /* Approaches to driving VRM Usage */

The objective of the Usage Committee is to
'''Drive VRM usage'''

This page will be the central point of organization for the committee.

== Committee members ==

*Adriana Lukas
*Chris Carfi (present and reporting for duty!)
*Deb Schultz
*Alan Mitchell
*Dean Landsman
*Sean Bohan
*Kaliya Hamlin
*Bart Stevens

== Approaches to driving VRM Usage ==

#industry/vendor driven
#web/user driven
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

The Mine! Project

2009-11-26T20:49:14Z

Maniac:

[http://themineproject.org/ The Mine! Project] is an active and growing open source VRM development project launched in 2008 by [http://www.mediainfluencer.net/ Adriana Lukas] and [http://www.crypticide.com/dropsafe/ Alec Muffett].

From the project's [http://themineproject.org/index.php/about/ About] page:

"The Mine! project is about equipping people with tools and functionality that will help them:

1. take charge of their data (content, relationships, transactions, knowledge),
2. arrange (analyse, manipulate, combine, mash-up) it according to their needs and preferences and
3. share it on their own terms
4. whilst connected and networked on the web.

"The Mine! aims to be an (infra)structure for other solutions - VRM (relationships with individuals and vendors, transactions), self-defined identity, authentication, data portability and hopefully many more."

For more, go to [[http://themineproject.org/ the project site].
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Read Log

2009-11-26T20:48:29Z

Maniac:

A Read Log is like a [[Listen Log]], but for readers of digital text.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Principles

2009-11-26T20:47:03Z

Maniac: /* Solve real-world problems */

This page is a draft proposal. Please send any comments to [mailto:joe@switchbook.com] or to the Project VRM [[mailing list]].

==Charter==
Create an ecosystem of tools, protocols, and services that help users manage vendor relationships.
==Principles==
#User control
#Reduce, Reuse, Recycle (Don't Reinvent the Wheel)
#Reciprocity & Everybody Wins
#Leverage network effects
#Relationships are more than transactions
#Solve real-world problems

===User control===
Work from the perspective of the end-user. Users should control who, how, and what happens throughout the entire process. The process should create value for the user first, vendors and others second. Note that by creating value for users, there should be plenty to go around. See Reciprocity.
===Reduce, Reuse, Recycle===
Don't Reinvent the Wheel. A lot of technology and solutions have already been developed to address various pieces of our online world. When possible, reuse existing tech and learn from prior experiences. That means researching what has already been done and integrating the past whenever possible.
===Reciprocity & Everybody Wins===
VRM should create value for everyone in the value chain. Although the focus is on the user (see User-centricity), each link in the relationship should come out better after implementing a VRM Protocol. When everbody wins, it will be much easier to convince everyone to participate.
===Leverage network effects===
Network effects scale as more people participate. Whenever possible, build systems with this characteristic. In particular, reducing transaction costs across many different transactions can dramatically change a market, even when those costs are relatively small part of each transaction. So, use network effects to leverage the value of our efforts as far and wide as possible.
===Relationships are more than transactions===
Although vendor relationships are ultimately bounded by transactions, they begin well before and continue well after. Build systems that enable rich, long-lived relationships in ways that create real value.
===Solve real-world problems===
People have lots of challenges and frustrations with existing sales, shopping, and support systems. Pick one and re-invent it from a user perspective. If putting the user in control creates real value with minimal investment by the vendor, we have a good chance of getting traction with both users and vendors.

This is an early draft. I encourage corrections and addendums. Especially from our fearless leader. =) [[User:Joe.andrieu|Joe.andrieu]] 00:29, 2 February 2007 (EST)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Personal Health Records

2009-11-26T20:46:38Z

Maniac:

The time to explore this topic is now.

The Obama Administration is discussing [http://www.whitehouse.gov/search/?keywords=personal%20health%20records personal health records]. The senate (Senator Jay Rockefeller) is offering [http://thomas.loc.gov/cgi-bin/bdquery/z?d111:s890: this bill] according to this [http://rockefeller.senate.gov/press/record.cfm?id=311951& press release]:

''The Health Information Technology Public Utility Act of 2009 will build upon the successful use of âopen sourceâ electronic health records by the Department of Veterans Affairs as well as the âopen source exchange model,â which was recently expanded among federal agencies through the Nationwide Health Information Network-Connect initiative.''

We all have our own personal health records. Most of our records are in archives and records departments of various doctors' offices, hospitals, and health care facilities.

Insurance companies also have copies, and many decisions are made based on what's in our records. We may or may not know about the information, its significance, or its effects on our policies.

The medical profession has a key stake in having standards in place that facilitate proper access to necessary records. The [http://www.index.va.gov/search/va/va_search.jsp?SQ=&TT=1&QT=%22personal+health+records%22&searchbtn=Search VA Hospital], [http://xnet.kp.org/newscenter/pressreleases/nat/2009/042209myhealthmgr.html Kaiser Permanente], and the [http://www.informationweek.com/news/showArticle.jhtml?articleID=216900387 Mayo Clinic] are models of patient records exchanges. Notable players in this space are [http://msdn.microsoft.com/en-us/healthvault/default.aspx Microsoft] and [http://googleblog.blogspot.com/2009/03/google-health-helping-you-better.html Google].

There are at least a couple of groups ([http://hitsp.org/ Healthcare Information Technology Standards Panel], [http://e-patients.net/ e-patients.net ]) working on making patient records interoperable.

What's going on? How can we help? What skill sets can we bring to the table?
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Mailing list

2009-11-26T20:45:49Z

Maniac:

[http://cyber.law.harvard.edu/lists/info/projectvrm The list.]

[http://cyber.law.harvard.edu/lists/subscribe/projectvrm Subscribing.]

Post by mailing to projectvrm AT eon.law.harvard.edu.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Identity issues

2009-11-26T20:45:05Z

Maniac:

Very much a stub...

For VRM to work, there's a minimum requirement of a GUID for each seeker. For reasons outlined in the [[privacy issues]] section, I don't believe that seekers' RFPs should contain contact information. In this context a GUID could be as simple as as public URL; (And yes, I'd really like to come up with a better term than "seeker," but nothing's yet come to mind.)

In light of Don Marti's elegant Upside-down buyer's guide idea (currently living in [[Project ideas]]), publicly verifiable vendor identity goes from a nice-to-have to a virtual requirement. While it doesn't seem to make sense for seeker identity, does a DNS-overload approach (think Domain Keys or SPF) make sense as a partial mechanism for establishing vendor ID? If so, does that automatically disallow third parties that don't have Web presence/commerce of their own?

Note possibility of reputation coming into play here: reliable identity is key if the repuation/trustworthiness of a vendor (or another seeker, as a source of information about a vendor) is a factor in offer evaluation...and it seems like it should be, at some point. Very nice extension of the idea.

Dropping a link in here so that I don't forget: [http://blog.joeandrieu.com/2006/12/03/internet-identity-reputation-networks-and-more/ Andrieu on Reputation Networks and More]. The longer it rolls around in my head, the more significant reputation seems to be in this whole process.

----

Feel free to edit this part... MikeWarot (Ka9dgx)

VRM can't work without identity. To be clear, I'll use the conventional terms for things...

If I as a consumer want to use VRM to offer the chance to sell to potential vendors, I have to provide a secure channel for getting information back to me. In the CRM world, the Corporate Presence (Website, etc) serve as a defacto means of security the identity of the Vendor, and the means of securing the identity of the consumer is usually by withholding goods or services until some form of payment is tendered, making the identity of the consumer a lower priority for the vendor, because they don't care... they just want to sell and get paid.

In a VRM world, the situation is completely inverted... the consumer knows who they are, and must provide some proof that they are willing to pay... but have no means of verifying the identity (and thus reputation) of a Vendor within the VRM framework... and thus must eventually revert to the CRM model unless some alternative means is provided.

----

I bring this up because one of the examples I recently suggested was VRM as a tip jar. In order for it to work on a large scale, there has to be some identity proof for the Vendor, even if the consumer doesn't have goods to withhold, because they don't want to pay for fraudulent claims... their money should go to the right person.

Unless there is some form of identity verification both ways, with some mutually trusted party in the middle, VRM is going to face an uphill battle for adoption.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Health VRM

2009-11-26T20:44:26Z

Maniac:

Mike Kirkwood. â Healthcare discussion
Mike@polka.com

Focusing on the space of a âMe serviceâ for the healthcare industry

Includes âHealth Journalingâ app for itunes

Thereâs personal health records

Took engine that was user focused, and offered it to the providers.

Kaiser
Healthnet

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.

Finding that the record doesnât change that often

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

Itâs a big deal

Sean Bohan â says that the big things are conformance (using your meds right)

40% of the problems is adherence

and 10% is fatal combination.

Sean â the other side is disease managementâ¦ Healthcare providers will offload patient management to small companies that would outcall

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.

So the providers and payers want to incent people to take care of themselves so they donât end up in the critical phase.

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.

This system would be part of the service delivery solution.

Can put HealthVault or Google Health in the middle.

So there are other players in the mix.. like the hospital or the doctor.

They would solicit the patient maintained data

HIPAA and HL7 data privacy issues had prevented this stuff from happening before.

Can add glucose monitor, heartbeat monitor (an Observation Engine) will then publish to the provider

Mike asserts that this sort of system should adhere to the 10 points that Joe brought up in the User Controled User session.

How is it secured. How is the data disposed of.

E.g. What does Blue Cross want?
(not necessarily the clinician)

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.

So the payer might foot the bill for the solution just to know whether someone is adhering to the drug administration requirements.

Adherence might be a little dicierâ¦ âCan it answer âdid he take his medsââ

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

Sean â you still need the education.

Observation â 70% of the pills advertised directly on TV are prescribed.

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

Jim Morris says â the medical profession feels like they are controlling us with the ânon-complianceâ issues.

If there was ever a case where user empowerment this is it

Joe asks â have you looked at the data rights issues especially when it gets to âin aggregateâ reporting.

A: in the Polka view, you should be in control of both your data and âin aggregateâ.

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.

The control should be imposed for both individual and aggregated data

Clinical team can say what they want from the person.

Give them an iPhone and the app for monitoring their activity.

De-identivcation needs to take place right behind the Observation Engine.

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.

Then there are people in the Disease management group who wouldnât want the data to be made available.

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.

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

Asa- You can set up the stream to determine that âyou pay this side and charge that sideâ.

The incentive is you might get an iPhone and a Watch to get people to participate.

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.â

Insurance companies already say that they give you a better rate.

The weakness is that âpeople donât input data consistentlyâ

A: Beckton Dickinson has added Bluetooth to the devices that collect blood samples and all that

Joe â you would set this up so people would do it because they are doing something else â a point of sale dynamic

Mike â we had tracking on an iPhone (if people put in the data)â¦ So we added a public/private Twitter like microblog (140 characters)

Added a Type and in-depth object
Added location

The Tweet describes the situtation

Then can add tags with Diet info and it gets mapped to the diet tool or whatever.

Sean â need a perpetual carrot.

Can also package it as a game.

Itâs not the game device. Itâs the game dynamics and the participatory nature

Thereâs a tweet-what-you-eat service

Q: does this scale. Or what percentage of the population will be tweeting or not.

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.

Info will go through the observation engine where it will become part of the aggregate.

Then they will start to incentivize users in ways that make it âcompulsoryâ

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.

Sean â this idea of journaling (tracking) you do when youâre training for a marathon.

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.

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)â¦

One of the things we started implementing, included location (named, address or lat/long)

We learned that âhealth is untouchableâ because of HIPAA and that sort of thing.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
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.

Joe recommends watching âSubsidized Fateâ â¦

Because people that want to use our data will use game design to add the dynamics and participation that we require.

Firefox plugin

2009-11-26T20:43:38Z

Maniac: /* Working Notes */

=Overview=
Seeker toolbox implementation does not necessarily need to be browser plugin; could also be a standalone application using this model, but the browser plugin approach offers a few possible advantages:

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REF: attentiontrust.org/root.net
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Conference call archive

2009-11-26T20:42:01Z

Maniac: /* March 5, 2008 */

==Current/Most Recent Conference Call==
*[[meeting notes 2007 07 11]]

==Prior Conference Calls==
===July 11, 2007===
*[[meeting notes 2007 07 11]]

===July 3, 2007===
*[[meeting notes 2007 07 03]]

===June 20, 2007===
*[[meeting notes 2007 06 20]]

===June 13, 2007===
*[[meeting notes 2007 06 13]]

===May 23, 2007===
*[[meeting notes 2007 05 23]]

===May 16, 2007===
*[[meeting notes 2007 05 16]]

===May 9, 2007===
*[[meeting notes 2007 05 09]]

===May 2, 2007===
*[[meeting notes 2007 05 02]]

===March 21, 2007===
*[[meeting notes 2007 03 21]]
*[http://vrm.land-com.net/VRM_Conf03212007.mp3 audio 2007 03 21]

===March 8, 2007===
*[[meeting notes 2007 03 08]]
*no audio
===February 21, 2007===
*no meeting notes
*[http://www.vrm.land-com.net/VRM_Conf02222007.mp3 audio 2007 02 21]
===February 8, 2007===
*[[meeting notes 2007 02 08]]
*[http://www.vrm.land-com.net/VRM_Conf02082007.mp3 audio 2007 02 08]

===March 5, 2008===
*[[http://cyber.law.harvard.edu/projectvrm/March_5_2008_Conference_Call]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

===March 19, 2008===
*[[http://cyber.law.harvard.edu/projectvrm/March_19_2008_Conference_Call]]

Blogs

2009-11-26T20:41:21Z

Maniac: /* Doc Searls' posts on VRM (includes Linux Journal essays) */

== Blog posts on VRM ==

* [http://blogs.law.harvard.edu/vrm/ ProjectVRM's own blog]
* Technorati [http://technorati.com/search/VRM VRM search]
* Technorati [http://technorati.com/tag/vrm VRM tag search]
* Gooogle Blogsearch [http://blogsearch.google.com/blogsearch?hl=en&q=vrm&btnG=Search+Blogs VRM search]
* Pierre-Philippe Cormeraie: [http://pierre-philippe.blogspot.com/2007/01/nownow-une-approche-vrm-du-service-svp.html NowNow : une approche VRM du service SVP?]
* Johannes Ernst: [http://netmesh.info/jernst/Digital_Identity/doc-searls-vendor-relationship-management.html Doc Searls: Vendor Relationship Management]
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/07/doc-appears-to-have-an-epiphany/ Doc does appear to have an epiphany]
* Dennis Kennedy: [http://www.denniskennedy.com/blog/2006/10/meme_to_watch_identity_and_vrm.html Meme to Watch: VRM and CRM]
* J.P. Rangaswami: [http://blogs.telegraph.co.uk/technology/shanerichmond/nov06/customereconomics.htm Economics of the Customer]
* Denise Howell: [http://betweenlawyers.corante.com/archives/2006/09/06/vlfs_should_embrace_vrm.php VLFs should embrace VRM]
* Denise Howell: [http://blogs.zdnet.com/Howell/?p=67 Monetizing the urge to recommend]
* Alceste: [http://barking.alceste.ch/?p=44 CRM is dead, long live VRM]
* Phil Windley: [http://www.windley.com/archives/2006/12/vendor_relationship_matters.shtml Vendor Relationship Matters]
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/08/time-to-rethink-the-basis-of-marketing-data/ Time to rethink the basis of marketing data]
* Dave Winer: [http://www.scripting.com/2006/12/05.html#When:9:22:36PM Note to Terry Semel: Get on board with VRM.]
* Bernie Goldbach: [http://irish.typepad.com/irisheyes/2006/12/podleaders_shou.html Podleaders should talk VRM]
* Colin Henderson: [http://bankwatch.wordpress.com/2006/12/07/doc-appears-to-have-an-epiphany/ Vendor Relations Management]
* Dennis Kennedy: [http://www.denniskennedy.com/blog/2006/10/meme_to_watch_identity_and_vrm.html Meme to watch: Identity and VRM]
* Harold Gilchrist: [http://www.podcastbrowser.com/blog/?p=284 The Gang says the user is in charge]
* Shane Williamson: [http://shanewilliamson.spaces.live.com/Blog/cns!200D676A335D69C6!1113.entry WARNING: Vendor Relationship Management may make your company successful]
* Rob Kleine: [http://www.gentleye.com/digito-society/?p=662 Doc on VRM or Your CRM Just Exploded!]
* Heinz Wittenbrinks: [http://heinz.typepad.com/lostandfound/2006/12/vrm.html VRM]
* Whitney McNamara: [http://www.blackmailr.com/smr/2006/10/09/lunchtime-musings-what-doc-searls-still-wants/ What Doc Searls (still) Wants...]
* Jeremie Miller: [http://jeremie.com/blog/index.php?entry=entry061211-160116 What does the R mean in VRM?]
* Britt Blaser: [http://www.blaserco.com/blogs/?p=42 VRM Entry Point]
* Gave Wachob: [http://blog.wachob.com/2006/12/doc_searls_has_.html Candidate/Campaign Relationship Management]
* Sean Coon: [http://www.seancoon.org/2006/12/doc_and_vrm.html Doc on VRM]
* Ethan Zuckerman: [http://www.ethanzuckerman.com/blog/?p=1145 Doc Searls, live, not in the ceiling]
* Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2006/12/13/incredible-inevitable-identity/ Incredible Inevitable Identity]
* Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2006/12/03/internet-identity-reputation-networks-and-more/ Internet Identity -> Reputation Networks and more]
* Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2006/11/21/vrm-make-a-gesture-create-a-market/ VRM: Make a gesture, create a market]
* SteveX: [http://blog.stevex.net/index.php/2006/12/13/vendor-relationship-management/ Vendor Relationship Management]
* ChrisKelly.org: [http://www.chriskelley.org/?p=401 Data Exchange]
* Christopher Carfi: [http://www.socialcustomer.com/2006/12/vrm_vendor_rela.html VRM - Vendor Relationship Management]
* Paul Trevithick: [http://sp.typepad.com/blog/2006/12/docs_vrm_projec.html Doc's VRM Project]
* Denise Howell: [http://blogs.zdnet.com/Howell/?p=69 Vendor Relationship Management and the Support Economy]
* RussDev Blog: [http://www.russdev.com/wp-blog/2006/12/16/suppliers-vendors-vrm-is-future/ Suppliers (Vendors) - VRM Is Future.]
* Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2006/12/18/the-r-in-vrm/ The 'R' in VRM]
* Deb Schultz: [http://www.deborahschultz.com/deblog/advertising_promotion/index.html Banner ads and PV - I wish they would just die already ]
* Colin Henderson: [http://bankwatch.wordpress.com/2007/01/02/microformats-as-information-brokers-the-intelligent-agents-to-support-vrm/ Microformats as information brokers - the intelligent agents to support VRM ]
* Christopher Carfi: [http://www.socialcustomer.com/2007/01/more_on_vendor_.html That Nagging Voice of the Human Customer]
* Drummond Reed: [http://www.equalsdrummond.name/?p=91 VRM: VROOOM!]
* Pierre-Philippe Cormeraie: [http://pierre-philippe.blogspot.com/2007/01/vrm-crm-20.html VRM = CRM 2.0?]
* Colin Henderson: [http://bankwatch.wordpress.com/2007/01/05/microformats-as-information-brokers-revisited/ Microformats as information brokers - revisited]
* USVO: [http://blog.usvo.com/?p=35 The Customer Revolt]
* Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2007/01/19/shopatron-redefines-vendor-relationships/ Shopatron redefines Vendor Relationships]
* Christopher Carfi: [http://www.socialcustomer.com/2007/01/vrm_scenarios.html VRM Scenarios]
*Joe Andrieu<nowiki>[</nowiki>[http://www.switchbook.com/#Joe @]<nowiki>]</nowiki>: [http://blog.joeandrieu.com/2007/01/23/vrm-process/ VRM Process]
* Phil Whitehouse: [http://philwhitehouse.blogspot.com/2008/04/vrm-tiddlywiki.html VRM TiddlyWiki]
* Keith Hopper: [http://keithhopper.com/taxonomy/term/15 VRM tag on keithhopper.com]

== Doc Searls' posts on VRM (includes [http://www.linuxjournal.com/blog/800285 Linux Journal essays)] ==

* [http://doc.weblogs.com/2006/11/20#vrmInquiry VRM Inquiry]
* [http://doc.weblogs.com/2006/11/16#thisIsWhyIWantVrm This is why I want VRM]
* [http://doc.weblogs.com/2006/11/19#turningFunnelsIntoMegaphones Turning funnels into megaphones]
* [http://doc.weblogs.com/2006/10/08#howVrmHelpsCrm How VRM helps CRM]
* [http://www.linuxjournal.com/node/1000137 Let's go bust some silos]
* [http://www.linuxjournal.com/node/1000089 Turning the world i-side out]
* [http://www.linuxjournal.com/node/1000035 The Intention Economy]
* [http://doc.weblogs.com/2006/11/27#abuseCaseForVrm Abuse case for VRM]
* [http://doc.weblogs.com/2006/12/07#relations Relations]
* [http://www.linuxjournal.com/node/1000153 Can we relate?]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Website planning

2009-11-26T20:40:25Z

Maniac: /* Random Thoughts */

==Website Purpose & Goals==
#Facilitate VRM development
##"Internal"
##External
#Introduce, educate, and evangelize to the public

==Users==
Categories & Examples

===Editors===
*Doc
*Joe
*Dean

===Person at Large Company===
*Johnson & Johnson
===Person at Small/Medium Size Company===
*Marketing guy
*CEO/COO type
===Press===
*TV
*Print
*Blogger
===Manufacturers/Vendors===
*Acme manufacturing company
A newbie to VRM, but interested in learning more and potentially contributing.

==Use Cases/Scenarios==
===Large Company Contact===
*Request help or information
===Contributor===
*Update specification
===Potential collaborator, contributor, developer===
*Exploring, investigating, considering getting involved.

==Content/Functionality Ideas==
*VRM ''website'' that is educational, promoting
*Project VRM ''wiki'' for contributors and developers
*Feedback
**Form
**Wiki
**Email
**Have we missed anything? Help us help you.
*Tools
**Ways to do RFPs
**Ways to work with consumers other than command & control
**Ways to be user-centric
**Checklist
***Are you ready for VRM?
*How to Contribute
**Commit
**Promote
**Contribute--input, feedback ("is there a VRM initiative you deploy that hasn't been mentioned here?")
**Collaborate--co-create, drive efforts
**Initiatives
**Action Items
*List of Contributors
*Press Coverage
*Blog Coverage
*Press Information
*Jabber Server/Channel
*Technology
**Code base
**Protocols
**Third-party software
*Secure Area
Password protected area where we can post
links to material that would be relevant to working groups, but which
would not necessarily be suitable for being put in the public domain.
*Events
*Introduction
*Social Network (Haystack)
*Assessment tool http://www.dataprotectionscorecard.com (suggested by Iain Henderson)

==Constraints & Requirements==
===Berkman Friendly===
===Wiki Wiki Wiki===
===Cross Browser===
*Internet Explorer
**6.0
**7.0
*Firefox
**1.5
**2.0
*Safari
===Cross Platform===
*Windows
**Win2k
**Windows XP
*Macintosh
**OS X

==Open Questions==
==Random Thoughts==
http://www.apache.org is a good example
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

==Action Items==
Joe: Top-level site-map structure thingy proposal. By next wednesday. (Confer with Chris before then.)
==Draft layout==
[[Image:VRM_Home_Page.gif]]

Vision Committee

2009-11-26T20:39:45Z

Maniac:

The objective of the Vision Committee is to
'''Define and advocate a clear vision for a VRM world'''.

This page will be the central point of organization for the committee.

This is a placeholder page, soon to be replaced by committee members.

12-31-2007:
Charles: Here is input for defining a Vision for VRM and for our Organization.
[http://www.e-pix.com/VRM/Vision.html VRM Vision draft]

Discussion, Comments, Changes, Additions, Subtractions Welcome.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

VRM Workshop

2009-11-26T20:38:56Z

Maniac: Redirecting to VRM Workshop 2008

#REDIRECT [[VRM Workshop 2008]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

VRM lexicon

2009-11-26T20:38:29Z

Maniac: /* Other sources */

== Lexicon ==

Currently a list. We need to add definitions. And links to definitions.

* customer
* customer-driven
* -driven
* Listen Log (the general topic) and ListenLog (the development project0
* Media Logging
* PayChoice
* personal RFP
* user-driven
* vendor
* VRM - Vendor Relationship Management

== Other sources ==

* [http://wiki.auds.org/index.php//wiki/agreement AUDS] (contains a lexicon)
* [http://wiki.projectliberty.org/index.php/VolunteeredPersonalInformationSIG VPI]
* [http://www.vrmlabs.net/ VRM Labs] (top level... will -- or does -- contain a lexicon)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Technology

2009-11-26T20:37:45Z

Maniac:

This is something of a stub. We need a section of the wiki for architecture and design considerations. This will do for now.

Proposing the idea that the three biggest areas of concern for architecture and design are taxonomy, identity, and privacy (latter two interrelated, of course). Was planning on blogging thoughts, but will add them here if the collective buys into the idea.

* VRM [[information flow]]
* Possible [[vrm diagram]] (alternate view)

* VRM and [[taxonomy issues]]

* VRM and [[identity issues]]

* VRM and [[privacy issues]]

* Partial implementation as [[Firefox plugin]]?

* VRM and [[Liberty Alliance]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Relbutton Scenarios

2009-11-26T20:36:54Z

Maniac: /* Call Notes */

'''Note: the action has moved from this page to the [[r-button]] page.'''

"Relbutton" is a name for what we've also been calling a "buy button" or a "[[PayChoice]]" button. The "rel" stands for relationship.

[[Image:Icon4.gif]]

The button combines reciprocal symbols for customer and vendor, each represented by red "magnets" facing each other.

It can be used either by a customer to express an interest in doing business with a vendor, or by either or both sides to reveal the existence of a relationship. When that is the case, the two "magnets" appear joined. (Other configurations are reviewed below.)

Customers can use it as a "pay button" to express a willingness to buy goods that are otherwise free (such as podcasts, blogs, pieces of music or public radio stations or programs). Vendors can use it to express an interest in doing business on terms that embrace actual relationship -- including terms that are provided by the customer as well as the vendor. With it, VRM meets CRM, and each can engage and improve relations with other.

As a simple symbolic representation of willingness and commitment by both sides, the relbutton provides a visual door to back ends of capabilities and record-keeping (as well as transaction ability) that can help improve markets by making customers independent and informative contributors, and not just sources of cash and data for marketing mills.

== Basic Characteristics ==
* The Relbutton represents a free and open web service, available to both vendors and customers, providing capabilities to both
* The button can be placed by the customer on anything he or she might be willing to pay for -- or to indicate an interest in conversation or relationship.
* The button can also be displayed by the site as an signal that a displayed item (or service, or whatever) is open to either being paid for, or a relationship, or both.
* A web service API allows vendors (i.e. producers, owners, distributors, etc.) to attach Relbutton features to their site, project, products, or content
* A web service API allows consumers (i.e. users, customer, etc.) to attach Relbutton features to external vendors' site, project, products, or content
* The relbutton can also be the real as well as symbolic place where VRM and CRM meet.
* As with [http://creativecommons.org/ Creative Commons] licences and symbols, the relbutton and its functions should be [http://creativecommons.org/?s=readable readable] three ways: by humans, by machines and by lawyers.

== Visuals ==
The relbutton is a set of two images resembling two facing magnets, open toward each other. The shapes symbolize openness, choice, independence, equality and intentionality. They can appear in four ways, each expressing a different message. These are:

1. Open to relating:

[[Image:Relbutton_sm.jpg]]

2. Relating already:

[[Image:Relbutton_sm_closed.jpg]]

3. Looking to buy something:

[[Image:Relbutton_sm_left.jpg]]

4. Looking to sell something:

[[Image:Relbutton_sm_right.jpg]]

What makes these especially helpful and handy is that they give both sides all the virtues listed above. So, for example, when a vendor puts this symbol on a product or a site...

[[Image:Relbutton_sm_right.jpg]]

... they're saying "We're willing to do business with you on ''your'' terms as well as ours."

And, when the customer clicks on a closed button...

[[Image:Relbutton_sm_closed.jpg]]

... data from both sides can be brought in and displayed.

That data can be anything pertaining to relationship, history, intentionality, preference... it's wide open.

In practical and simple terms, when the customer clicks on the button, it says "hey you" to the vendor. If the vendor responds, the customer's "it's me" data repository and choice matrix comes into play. The databases on both sides might also be called "hey you" and "it's me".

As they say in the advertising business, this has legs. Lots of them.

By the way, the symbols are red for no reason other than visibility. They could be another color, or other colors. They could also be a color that changes depending on conditions outlined below.)

Britt Blaser produced this graphical explanation of the relbutton:

[[Image:Relbutton.gif]]

Note that there are many possibilities here, and the ones shown on this page are the initial few.

== Requirements ==
Before we proceed, here is what the relbutton should and should not do:
* All but symbol 4 (vendor side only) should be under the customer's control.
* It should support true two-way relationships between customers and vendors in all three market domains: transaction, conversation and relationship.
* Unlike advertising and promotion, it will be a way that the customer makes the first move. It must support the ''intentions'' of the customer first, and the vendor second.
* It should support the ability of the customer to pay whatever they please. Also for the vendor not to accept the payment. For this reason, it should allow the buyer to escrow (or record) the intention to pay, so the vendor can see that if they wish, or accept payment once the vendor puts the acceptance mechanisms in place. This should be visible exclusively to those vendors, even if they do not yet have the mechanisms in place for perceiving them, or for accepting payment. This system will allow vendors payment-acceptance and CRM systems to adapt to standard means by which customers, at their discretion, can ''transact'', ''converse with'' and ''relate with'' vendors.
* It should not provide means by which vendors coerce or entrap customers. Once relationships are established, they can be whatever customers and vendors agree upon. But as a means for "hooking up", or accepting payment, relbuttons cannot be under exclusive vendor control. For example, if a relbutton on a music site brings up a list of fixed prices for selections and albums, the customer should still have the choice of offering amounts they please, rather than just the prices offered by the vendor. This doesn't mean the vendor has to accept what the customer offers. It does mean that the customer has the means for offering what they like, including amounts higher than the vendor is asking.
* It should support the expression of preferences. This includes conditions for relationship, such as selective disclosure of personal data, conditions for the use of personal data, interest in specific (and defined) future products, and interaction requirements. Among the latter might be, for example, the preference ''not'' to receive promotional messages when calling for tech support.
* It should support customers and vendors both retaining records of interactions in the course of relationship, including transaction histories, contact histories and other variables. Among many other thints, these should be able to back each other up at times when the other party loses data.
* Both parties should be able to cease relationships, on mutually agreeable terms.
* For identity-based interactions, it should obey the [[http://www.identityblog.com/?p=352 Seven Laws of Identity]]
* A link to the [http://cyber.law.harvard.edu/projectvrm/Relbutton_Functional_Specification RelButton Functional Specification (Spec)]

== Best Fits ==
The relbutton model will likely be ideal for certain products, vendors, and verticals - perhaps with traditional companies that are seeking mechanisms to better relate to their customers, or in a market where customers are lacking the trust and control they demand. What are the characteristics for these best fits?

Alternatively, some new online environments and markets that were created specifically to disrupt artificial boundaries between vendor and consumer, such as ebay, threadless.com or even wikipedia may avoid such distinctions entirely.

"Relate" will also mean something quite different in different markets or areas. These differences need to be respected.

==Scenarios==

===Media in general===

The first use case for the relbutton is media. These include

* public media, including stations and programs
* citizen and participatory media, including otherwise free online publications
* podcasts
* online publications, including blogs
* pieces of music, or artists

Since the VRM community already includes participants from public media, and since we have been in conversation with public media folks about VRM for more than a year, that would be the best place to start prototyping and scenario-planning relbutton usage.

Subsequent use cases include

* commercial radio
* commercial television
* music
* all other forms of digital content

===The MID Radio===

An MID is a Mobile Internet Device. These include all handheld units that are capable of using the Internet via wi-fi or the cellular telephone networks. Examples range from the [http://en.wikipedia.org/wiki/Nokia_N810 Nokia N810] to the [http://apple.com/iphone iPhone] to open phones designed via [http://trolltech.com Trolltech/Nokia/] [http://code.google.com/android/ Google/Android], [http://openmoko.com OpenMoko] or any of the other emerging (and mostly Linux-based) devices and their development platforms.

([http://www.intel.com/products/mid/ Intel especially] is driving development in this category.

In the long run, radio will overcome its current fixed-transmitter and limited spectrum limits (which have been with us since AM/MW/SW radio was established in the 1920s, and FM was established in the 1940s) -- by moving to streaming via wi-fi and mobile phone systems.

We can make that run much shorter by building stream tuners for MIDs.

Their directories can be populated informally by users cutting and pasting from stream URLs on websites, or more formally by interactive web services.

They can be designed to receive streams only at bandwidths permitted by existing connection limitations, moving from one data rate stream to another as conditions permit.

They can have UIs that are either directory schema based or that allow users to fan through choices in the manner of Apple's "coverflow".

The relbutton should be a standard feature of these radio tuners to begin with. If you design a stream tuner (or, for that matter, a podcast player that allows users to interact by producing as well as consuming data), it needs to support relbuttons and relbutton-based interactions.

Where relbutton interactions are not supported, the user should still be able to accumulate data about the source of the stream or the podcast, and escrow that data for future use. (Perhaps, among other things, by advertising the fact that the user is interested in relating to the source, even though the source does not yet support the relbutton. This will allow demand to be heard, even if supply is not yet ready.)

Here are some graphical mock-ups of how the relbutton might be used with an iPhone stream or podcast "tuner":

[[Image:Iphonebrowsing 1.jpg|800px]]

[[image:Iphonerelationshipflow 1.jpg|800px]]

Note: The relbutton is now the [[r-button]] (making it parallel to [http://www.equalsdrummond.name/?p=135 the r-card]). Conversation and development continue on the page at that last link.

== Call Notes ==
[http://cyber.law.harvard.edu/projectvrm/August_19_2008_Conference_Call Relbutton Call notes, August 19, 2008]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Random Notes from Jan 25th VRM Developers Meeting

2009-11-26T20:36:06Z

Maniac:

Note: ''these are my notes from our meeting in Redwood City at the Sofitel, jotted onto the laptop during the day â emphasis and interpretations mine. Often Iâve put the speakerâs name in front of a statement or comments. Please feel free to add, change, correct ,edit, enhance, expand and expound.''
--Dean Landsman

'''Jan 25 2007 VRM Meeting - Sofitel, Redwood City CA'''

This is the relationship market
User-centric identity
Relating through federating? (NB: tantamount to large companies having safe sex w each other using each others data)

The Giving up of Competition (or, Competition As We Know It) (â¦as They Know It)

Markets: 3 levels â transaction conversation relationship --- this is the totality of negotiation (no order required for these to prosper)

Markets can grow and thrive at any of three levels: '''transaction''', '''conversation''' and '''relationship'''.

Conversation â learn -- perceive value (buy or sell) via relationship

Markets as relationships (conversations morph into relationships)

''' Problem w/ CRM = vendor solely owns/determines the relationship '''

This meeting, this initiative: It is a development project, not just research

Populate the wiki with more stuff â coherence re whatâs going on â input from those of us here â add experience of group (developers, etc) to move concept forward

Are large sums of money fighting VRM? Room says perhaps, maybe not yet, perhaps VRM not engaged yet at monolith level . . . . Doc: none fight User-Centric ID

VRM tools = instruments of independence and identity â to enable engagement (w/ vendors). Customer becomes voluntary participant in a relationship, not a categorized objectified statistic.

Does ''relationship'' transcend ''fear'' & ''greed'' (as motivators for corporations)?

Brands & relationship increase profit â how to express relationship? Kaliyah: What are the protocols involved? Method of engagement?

Value for vendors -- visibility leads to better management

Price less relevant than relationship

Commodity goods ... Passion goods

Avery: Language â legal (liability) identity, contract relationships

**3 Tracks: 1.technical 2.Market 3. Language/Law

**Is there a DNS for VRM?

Joe: 1.relationship â 2. process & principles (a la microformats) 3. single entity or different solutions (personal health different from personal RFP) (Johannes: arenât they the same thing? The essence of functionality is the same)

Joe: Vendor discovery different from personal RFP, or *as* personal RFP. We need to enable around different domains

Doc: Necessity is the mother of invention; invention mother of necessity

Kevin: Microformats puts data in structure of html -- converge schemas, not like XML, not use this arbitrary schema â no need for import export scripts. â Re-use names of things in other microformats (name, address, these fields are the same, allows for consistency, a uniform set of terms, designations, etc.)

Drummond: relationships persist beyond transaction (brand = recall + relationship or perception) if relationship is about perception, then personal RFP is a small aspect. XRI is about another layer of indentifiers, standard of ID above DNS
XRI are to Uri as _________________ (''note: I missed this, couldnât hear'')
Persistent Identity === XRI can help â¦ FOCUS on advantages of cross references â semantics â markup identifiers XRIs are nanoformats --- synonym mgmt - XRI dictionaries to solve mapping problem

turns mapping into a service ---

Joe: ''mentioned domain name, redacted in the event Joe has not gone public with this yet'' (not populated yet)

Doc re search â can a VRM be the pony â¦ that which helps search? â package intentionality for results not for ad medium optimization

Can VRM improve the search experience?

Web: born w/o a directory â chaos requires glue (needles, haystacks) or specificityâ¦coherence
Self organizing?

Chris Carfi: vendor-customer --- relationship levels â control -- vendor driven or customer driven â purely transactional in nature (see Chrisâs matrix)

Lower left: push/vendor induced/consumer has no power/vendor managed predictive if/then bombardment

Joe : if a relationship is not expressed or expressable, then it is NOT a relationship

DFL: do not confuse relationship w/ perception

ChrisCarfi: âMeVilleâ reputable anonymity // personal RFP // payment systems // pure transaction in MeVille: vendor orgs maintain transaction history â how is this done in MeVille? Is it necessary? Control, not ownership â of data â who is responsible for maintaining this info? Access to records . . .

General discussion of credit card transactions as an example â¦ individual owning and/or having access to this data â the receipt and the charge card record
Joe: not just the charge, but the receipt with the line charges. Gabe: image transmission difficult

Drummond: xRDI = xri data interchange
Transaction summary w/ receipt â can be transited
XRI rcpt + dictionary service = properly coded data

ChrisCarfi: global village â customer interested in longer term relationshuip â about process, convenience, what it means, external issues --- passion, local merchant, PREFERENCES where price becomes a smaller component of the [purchase] decision.

CC: I want to offer a loyalty program to my vendors

CC: many facets to personal or professional identity

'''NOTES FROM NPR BREAKOUT DISCUSSION GROUP'''

Upcoming NPR meeting: âDoc as emissary from The Netâ public non commercial broadcasting

Doc: what are the mechanisms for making something work?
Net as inventory of progams
Aka Podcasts
K: Build an attention payerâ¦create a norm around giving â¦. A donation should go to the music and the program. On your listening device tracking exists, to record what user has downloaded -- aggregate this data, on a monthly basis distribute this to the artistsâ¦paid via the program producer to the artists, et al designate an amount, pay it out pro rata based on attn (listening) paid to programming

DL: all sorts of time/attention intent issues cloud this model â time is not a proper measure of attention, this is a failure of the basic ratings system as it presently exists, and may increase with the PPM

Soundexchange internet radio stations â metrics â repetitionâ

NPR Stations â need to increase revenues, increase communications backânâforth with their listeners ***and thus, the VRM model ***

Jake Shapiro Public Radio Exchange PRX â
Music brains K spoke with them about i-tags Robert Kaye
Microformat for media === metadata
Itags: generic tagging for rich media

Kaliyah: âI want to hang out with the TAL communityâ (TAL = This American Life)

radiolab.org

Kevinâs Mediagora (side discussion, relevant although ancillary)

----

Iain: Info in a shoebox â connected personal info service

1. Privacy preference service (like Do Not Call,across all channels)

2. RFP service -- 2 buckets of XML : I wish to buy, I wish to sell

3. iBroker NY & London â build an identity on the site of the individual that has some sense of identity

append existing âclub cardsâ to each other

----

Joeâs group â relationships & expressions â see Wiki [http://tinyurl.com/38ldr8]

'''TASKS, PLANS'''
Set up regular '''bi-weekly conference call''' (''note to self: take care of this'')
1:30 eastern Thursdays Feb 8th
'''Bold text'''
Growth Topics and areas of concentration:
Policy technology marketing
Use cases
Policy
Tracks

Derive policy requirements out of Cluetrain Manifesto

Desired outcome of VRM will become clear through use cases

David & Kaliya work on Open ID involvement
Group blog w/ RSS via Venus ( via David)
Define â Project VRM Definition VRM on wiki page (all contribute, group effort)
Domain brainstorm page (by domain we mean categories, not URLs!)
Brainstorm domains
Use case scenarios
Brett â use case process

Develop commonalities among umbrella categories from the use cases (technical and policy requirements, et al)

Joe domain = the main point â¦..I wanna work on that â letâs develop boundaries, specifics, etc.

--[[User:DeanLand|deanland]] 19:53, 7 February 2007 (EST)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Prototyping VRM Mobile Social, iPhone

2009-11-26T20:35:09Z

Maniac:

Stuart- Prototyping a mobile VRM that leverages Social Network fabric

iPhone is a good conduit

Phone
SMS
Email
3.0 notification
Bluetooth

Stuart says that we have all these ways to contact people

iPhone adds location

Adds time

Presence â and what Iâm doing

Things that recognize that âstate has changedâ

Relationships provide context regarding âWho are you?â

The questions revolve around access control

âWe have this thing in our pocket that provides all these things to us, but we have no controlâ¦

â¦on the other side, the people have no idea whatâs happening on this end.â

It doesnât have to do with calls necessarily, but when it âescalatesâ from a message

Rules for Pre-call Information

Recipient only knows phone number if the caller is not in the directory

The originator really has no control over what information is provided

Using the rideshare use caseâ¦ thereâs an issue surrounding the Buddylist

Using Google Voice you can treat each caller differently â¦

Right now Google Voice gives you a âflavorâ of all the rules you can attach to incoming calls

Ribbit could be a platform for all of these services

Voice mail treatment on an iPhone is an issue because the iPhone voice mail store is on the device, not on a shared host

Comment â originator may want to indicate a different originating phone

Originator may also want to send a pre-call alert â IM/SMS (the Can you talkâ message)

Caveat â you will pile all kinds of capabilities for the power users â but other people wonât use it.

So you need to monitor and analyze all that behavior and deliver

You can establish groups.

Another way to look at it is that you can have my GrandCentral # and it is related to all the ways that I can be reached and will be associated

Need to talk about the difference between synchronous/asynchronous

Is it that important to do a synchronous conversation.

So basically it gets down to hooking up a system where the caller is in control

âIn a VRM world, the phone owner is in controlâ and how you get there is to take away the possibility of the caller to control the terms and conditions

This could be the origination vehicle

The systemic smarts are much more interesting than the granular control

Because the granular stuff should be automated.

You can trick thisâ¦ just get a fictitious number and point it where you want

**Stuart has an idea for a Craigâs list for Twitter (called Twitmark) instead of a phone number and address you put a Twitter handle, but whatâs missing is the escalation to a phone number. The other thing thatâs missing is that you have to do an abbreviated link to (e.g. a Craigâs list ad)â¦

Another idea that was brought up is the Farley Fileâ¦ whereby you keep track of all the people that you meet.

The phone gets it backwards, inbound now might be able to relate it to a record in the phone infrastructureâ¦ But what if you have a âWhoâs this?â button to relate other stuff in the social graph and CRM space to figure out whoâs calling.

Observation â thereâs probably a latency issue. Unless you preload some set of most likely callers and their might be other premapping.

People can more accustomed to âpromiscuous messagingâ â that is basically adsâ¦ âI need xâ or âIâm selling Yâ then you can also use location awareness to figure out whoâs twittering nearbyâ¦

Observation â youâre social graph and list of people youâre in touch with

One of the premises for this discussion is that if VRM is going to work, it will be on a mobile device.

Observation â there are a lot of interesting initiatives underway and we have to figure out how they will bolt together.

Some compete
Some could augment each other.

Weâre talking a lot about the requester time. And not how you find relevant providers â¦ So you need to know âhow sees thisâ?

A: in the twitter exampleâ¦ Daycare companies might have a âbot monitoring peopleâs requests, determining where the person is. They can send a direct messageâ¦ And they may have their own filter

Narrowcast exchangesâ¦

Which Phil Wolff â calls âsearchâ

E.g Rent-a-Coder
O-Desk
E-lance

Where you have not a job offer but a short gig. So you craft a message

**Capability goes in seek of a need and vice versa***

Thereâs an aggregation function to be served.

If youâre looking specifically for a pair of tennis shoes specificallyâ¦ Itâs not readily apparent exactly how you get to there from here.

Angieâs list + ribbit exposes the latency issue

Stuart is saying that â as things âescalate toward a transactionâ and Darius is wondering how you get there from hereâ¦ Can you make this a âcheck boxâ item in their lsting that âfor an extra $2 to add a phone numberâ for the duration of the interest.

Phweet demonstrates that the identity layer can be set up independent of other services.

It will work anywhere and it is initiated on the basis of a text exchange. The contract is a URL for that exchange.

You probably have it in your headâ¦ Thatâs a feature, not a product.

How do you make a product
How do you build usage.

Phil â Talked to an eBay employee latelyâ¦ Asked why do you think eBay never embraced Skypeâ¦ He said that eBayâs attachment to keeping the conversation controlled so that they couldnât be cut out of the equation, so they made it harder

As market makers they are also getting a percentage of the transaction so they just put up barriers.

Buy in depends on âwhat their stake isâ if you think the transaction will go on outside their walled garden, they wonât buy in .

E.g. you can architect this so that an assigned, ephemeral URL can be a revenue opportunity for Twitter. The Tweet controls how long the thing stays nailed up. You can do it on Twitter or Identica or anywhere. You can set up a VRM like relationship. And thatâs what makes it interesting

Closingâ¦ align VRM with the core metrics of each of the service providers.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Process

2009-11-26T20:34:29Z

Maniac: /* Draft VRM Process */

This page is a draft proposal. Please send any comments to [mailto:joe@andrieu.net] or to the Project VRM [[mailing list]].

(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)

==VRM Process==
One thing that Iâve been noodling lately is how we, as a community, can organize our efforts around VRM.

===Microformats Inspiration===
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.

===A Standard Process===
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.

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.

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:
<blockquote>
Before diving into creating a new technical spec, step outside and look around a bit.
</blockquote>

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*

===Scenarios===
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.

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.

==='''''Protocol''''' as VRM Output===
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:

* To develop a new VRM Protocol, one would shephard it through the VRM process on the Project VRM wiki.
* To implement a component of, or software that connects with, a VRM Protocol, one would implement the interfaces and protocols of that Interchange.
* The VRM Loan Protocol currently supports mortgage applications.
* The VRM pRFP Protocol allows for the secure, identity-controlled digital requests-for-proposals in an open marketspace.

Protocal seems to work. However, I would definitely appreciate feedback and alternative suggestions for such a term.

==Draft VRM Process==
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

#'''Problem Domain''' 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.
#'''Current Scenarios''' Brief prose descriptions of actual instances of the problem.
#'''Desired Scenarios''' Brief prose descriptions about how it might all be made better.
#'''Existing Efforts''' 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.
##'''Software'''
##'''Protocols'''
##'''Formats'''
##'''Initiatives'''
##'''Organizations'''
#'''Users''' 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. 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.
##'''End users'''
##'''Vendor users'''
##'''Supporting Users'''(retailers? regulators?)
##'''Implementors'''
#'''Use Cases''' 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.
##'''Abstract, High-Level Use Cases''' 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.
##'''Concrete Detailed Use Cases''' 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).
##'''Abstract, Detailed Use Cases''' 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.
#'''Brainstorming''' Free-form inspirations and ideas about how to realize one or more of those use cases.
#'''Draft''' 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.
##'''Entities'''
##'''Communications'''
###'''Protocols'''
###'''Formats'''
###'''Transactions'''
#'''Proposal''' 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.
#'''Published Standard''' 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.
#'''Reference Implementation''' 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.
#'''Implementation Directory''' 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.)

Feedback is definitely welcome.
[[User:Joe.andrieu|Joe.andrieu]] 09:28, 23 January 2007 (EST)
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Personal Address Manager Service

2009-11-26T20:33:09Z

Maniac: /* Organizations/Movements */

This Standard is being developed according to the VRM [[Use Cases|Use Case]] guidelines.

When possible, elements of the Requirements Model are incorporated directly herein. Otherwise, a link is provided for downloading supporting documents.

==Status==
[[:Category:Working Draft|Working Draft]]
[[Category:Working Draft]]

==Schedule==
{| border="1"
|+ '''Proposed Schedule for First Draft'''
! Item !! Who? !! Comment !! 2/20 !! 3/5 !! 3/19 !! 6/2 !! 7/2 !! 8/2 !! 9/2 !! 10/2 !! 11/2
|-
! Use Case Description
| J. Andrieu || ||XXX|| || || || || || || ||
|-
! Actors
| J. Andrieu || ||XXX|| || || || || || || ||
|-
! Roles
| J. Andrieu || ||XXX|| || || || || || || ||
|-
! Role Map
| J. Andrieu || || ||XXX|| || || || || || ||
|-
! Role Profiles
| J. Andrieu || || ||XXX|| || || || || || ||
|-
! High Level Use Cases
| J. Andrieu || || || ||XXX|| || || || || ||
|-
! Scenarios
| J. Andrieu || Need input! || || || ||XXX|| || || || ||
|-
! Abstract Use Case Narratives
| J. Andrieu || || || || || ||XXX|| || || ||
|-
! Specific Use Case Narratives
| J. Andrieu || || || || || ||XXX|| || || ||
|-
! Use Case Diagrams
| J. Andrieu || || || || || || ||XXX|| || ||
|-
! Use Case Maps
| J. Andrieu || || || || || || ||XXX|| || ||
|-
! Constraints and Requirements
| J. Andrieu || || || || || || || ||XXX|| ||
|-
! Policy Requirements
| J. Andrieu || || || || || || || ||XXX|| ||
|-
! Technology Review
| J. Andrieu || || || || || || || || ||XXX||
|-
! Formats and Protocols
| J. Andrieu || || || || || || || || || ||XXX
|}

Target date for announcing first complete draft: VRM Workshop June 2008

==Description==
The Personal Address Manager Service (PAM Service or PAM) allows anyone to manage their preferred (self-asserted) postal address(es) in one place and have it automatically be propagated and used by others, as authorized.

==Actors==
A list of all Actors supported by the system.
;Individuals: people who use a postal address as a point of contact for receiving correspondence. Also individuals who wish to contact others through a postal address.
;Organizations: entities who rely on a postal address as a way to reach individuals with whom they have existing relationships. Could be a for-profit corporation, sole proprietorship, non-profit, or government agency. Also entities who wish to contact others through a postal address.

Note that this service is specifically NOT designed to support organizations who rely on postal addresses as a way to reach individuals with whom the want to create a relationship, who we will refer to as "Direct Marketers" for lack of a better term. For this Service, Use Cases which support Direct Marketers are explicitly out of scope.

==Roles==
;AddressOwner:Anyone who use a postal address as a point of contact. This entity controls the data in the address and who has access.
;AddressUser:Anyone who wants to reach an AddressOwner at their postal address.
;AddressOwnerDelegate:Anyone authorized by an AddressOwner to act on their behalf. ''Specializes AddressOwner''.
;AddressUserDelegate:Anyone authorized by an AddressUser to act on their behalf. ''Specializes AddressUser''.
;AddressRequester:Individuals or organizations who request a postal address on demand for either immediate or perpetual use. ''Specializes AddressUser''.
;AddressSubscriber:Individuals or organizations who subscribe for updates to an individual's address. ''Specializes AddressUser''.
;OnlineAddressSubscriber:AddressSubscribers who will receive updates electronically. ''Specializes AddressSubscriber''
;OfflineAddressSubscriber:AddressSubscribers who will receive updates via postal service. ''SpecializesAddressSubscriber''
;Administrator:An individual with "administrator" privileges at the PAM service provider.

==Role Map==
A visual representation of the supported Roles and their relationships to one another.

[[image:PAM_Role_Map.png]]

==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 role needs from the system design.

===AddressOwner===
* Average Internet user. Understands websites, email, etc., but doesn't necessarily understand any of the underlying technology (HTML, http, SMTP, etc.). Web friendly but not especially tech savvy.
* Updates address on average once/year, although many users will spend years in between usage.
* Authorizations occur more frequently, so that interface is more familiar.
* Has list of authorized Requestors/Subscribers for address updates in various formats and for various services (DMV, utilities, magazine subscriptions, websites, etc.)
* Could have addresses anywhere on the planet.

===AddressOwner Delegate===
* Specializes AddressOwner
* Authorized by the AddressOwner to manage authorizations and edit addresses.
* May serve as delegate for multiple AddressOwners
* Can be expected to be moderately more tech-savvy than the average AddressOwner, but they could have the role just because they are the person in the household with the most geek skills.

===AddressUser===
* Anyone who wants to reach the AddressOwner via their current postal address as managed in the Personal Address manager.
* May be offline or online.
* Selected by virtue of the AddressOwner's desire to use the Personal Address Manager for this AddressUser.
* Could be anywhere on the planet.

===AddressUser Delegate===
* Anyone authorized by an AddressUser to act on their behalf.
* Typically this is a shipping or mailing service
* High technical sophistication
* Likely to have automated systems for managing large numbers of AddressOwners and AddressUsers.

===AddressRequester===
* Specializes AddressUser
* Internet-savvy entity who wants to make sure they always have the latest postal address for contacting users. Capable of implementing (or using) fairly sophisticated web services
* Manages tens to millions of users... small or large organization or individual.
* Will use the Personal Address Manager for on-demand queries.
* Sometimes handles mailings in-house, sometimes through third-party mailing house.

===AddressSubscriber===
* Specializes AddressUser
* Maintains own database and will not be relying on the Personal Address Manager for on-demand usage.

===OfflineAddressSubscriber===
* Specialized AddressSubscriber
* No Internet access expected or required.
* Will be reached via postal mail.

===OnlineAddressSubscriber===
* Specialized AddressSubscriber
* Average Internet User
* Has email address
* May have contact manager software capable of more sophisticated processing
** Or may manually process incoming email updates
===Administrator===
* Technically adept
* Has access to file system
* Needs system control at a finer level than simply deleting files.

==High Level Use Cases==
A list of all supported use cases in the system, identifying all required use cases by title.

1 AddressOwner Manages Address
1.1 AddressOwner Creates Address
1.2 AddressOwner Reviews Address
1.3 AddressOwner Changes Address
1.4 AddressOwner Deletes Address

2 AddressOwner Manages AddressUsers
2.1 AddressOwner Uploads AddressUsers
2.2 AddressOwner Authorizes AddressUser
2.3 AddressOwner Manages AddressUser Permissions
2.4 AddressOwner Deletes AddressUser

3 AddressOwner Manages Delegates
3.1 AddressOwner Authorizes Delegate
3.2 AddressOwner Unauthorizes Delegate
3.3 AddressOwner Removes Delegate

4 AddressUser Manages Delegates
4.1 AddressUser Authorizes Delegate
4.2 AddressUser Unauthorizes Delegate
4.3 AddressUser Removes Delegate

5 AddressUser discovers Personal Address Manager service for AddressOwner
6 AddressUser Requests Authorization
7 Delegate requests authorization
8 AddressRequester Requests Current Address
9 AddressSubscriber Activates Subscription
10 AddressSubscriber Deactivates Subscription
11 AddressOwner Accesses Activity Log
12 AddressUser reports address change
13 AddressOwner acknowledges address change
14 AddressOwner downloads data
15 AddressOwner authorizes automated export
16 AddressOwner creates account
17 AddressOwner deactivates account
18 AddressOwner deletes account
19 Administrator creates account
20 Administrator deactivates account
21 Administrator deletes account

==Scenarios==
A Scenario is a prose descriptions of a user's interaction with the system as one example of the Use Case that explains the context, the interaction, and the benefit.

Each scenario should be a short paragraph, containing the following elements:
# Why the actor is engaged in this use case? What happened? What motivated them to contact the system and begin the transaction?
# What does the actor do? Identify the keys actions taken by the actor during the use case.
# What does the actor get out of the system? Include both the actor's benefits and what the system does for them.

The goal is to have a simple, straightforward picture of why the Use Case matters and what happens to fulfill the Actor's needs. This should capture both the human elements of who & why and the functional elements of actions & results.

Each Use Case should have at least one scenario. Please number the scenarios, restarting the numbering for each Use Case.

===Use Case 1 AddressOwner Manages Address===

====Scenario 1:1 General Address Edit====
Betty needs to update her address at her Personal Address Manager. She goes to her service provider's website, authenticates herself using OpenID, and pulls up the Address Management interface. She edits one or more addresses and logs off. The system records the edits, both in the datastore and in the log files, and propagates update messages to current subscribers.

===Use Case 1.1 AddressOwner Creates Address===
'''Specializes Use Case 1 AddressOwner Manages Address'''

====Scenario 1.1:1 Bob creates first address====
Bob decides to try out the personal address service because he is about to move. He signs up with a service provider, creates a home address using his current address--specifying '''not''' to send updates yet--and confirms his email address with the provider. The system sets up a new account, discoverable by authorized AddressUsers and sends a confirmation email to Bob. (Bob's next action is likely to be one of the variations of [[Personal_Address_Manager_Service#Use Case 2 AddressOwner Manages AddressUsers | Use Case 2 AddressOwner Manages AddressUsers]])

====Scenario 1.1:2 Betty creates alternative address====
Betty is going to be sending a number of purchases to her Mother's place over the next few months. She goes to her Personal Address Manager and adds a new Alternative Address, giving it a name (Mom's Address), and making sure her current address remains the default for new purchases. The system records the new address, making it available to authorized AddressUsers who specifically ask for Betty's "Mom's Address". Betty's next step might be [[Personal_Address_Manager_Service#Use Case 2 AddressOwner Manages AddressUsers | Use Case 2 AddressOwner Manages AddressUsers]] or she might just wait until she is purchasing an item that she wants to ship to Mom before authorizing any AddressUsers.

===Use Case 1.2 AddressOwner Reviews Address===
====Scenario 1.2:1 Betty double checks her address====
Betty is wondering if the current address is correct. She logs in and reviews the addresses currently presented to authorized AddressUsers. The address is correct, so she does nothing further. (If it was incorrect, the next step is likely [[Personal_Address_Manager_Service#Use Case 1.3 AddressOwner Changes Address | Use Case 1.3 AddressOwner Changes Address]]

===Use Case 1.3 AddressOwner Changes Address===
====Scenario 1.3:1 Bob gets a new job====
Bob just got a new job and is moving from Los Angeles to San Francisco and recently selected his new home. He has an address to send to existing vendors. He visits the Personal Address Manager Service and inputs his new address. The service confirms the new address, date of the move, and the subscribers it will contact, logging the transaction. The system sends out the notices and keeps track of delivery so Bob can later verify receipt of the update. If Bob needs to manage AddressUsers, he likely goes to one of the variants of [[Personal_Address_Manager_Service#Use Case 2 AddressOwner Manages AddressUsers | Use Case 2 AddressOwner Manages AddressUsers]].

===Use Case 1.4 AddressOwner Deletes Address===
====Scenario 1.4:1 Betty deletes Mom's address====
Betty decides she no longer wants her Mother's address listed as a way to contact her (Betty). She logs in and deletes it. The system removes the address and logs the transaction.

===Use Case 2 AddressOwner Manages AddressUsers===
===Use Case 2.1 AddressOwner Uploads AddressUsers===
====Scenario 2.1:1 Bob uploads Outlook File====
Bob just created his account and wants to load all of his contacts in his Outlook contact database as AddressUsers. After exporting his Outlook contacts, Bob logs into the PAM service, selects upload, specifies the export file and submits. The server parses the file and shows Bob a list of contacts successfully imported.

===Use Case 2.2 AddressOwner Authorizes AddressUser===

====Scenario 2.2:1 Real-time authorization request====

Betty is at the website of a Vendor who she wants to set up as an AddressUser. She tells the AddressUser to use her PAM. The AddressUser finds the PAM and requests authorization as a AddressRequester, redirecting Betty to the PAM interface for authorization. The PAM verifies the AddressUsers credentials (to the extent possible), authenticates Betty (or uses existing session information to skip this step), and presents the request for authorization to Betty. Betty reviews the request and confirms that this AddressUser should be authorized for the specified access. The PAM redirects back to the AddressUser so that Betty can continue her transaction.

====Scenario 2.2:2 Email request (fulfilled via real-time authorization started at AddressUser's site) ====

Bob is a long time customer of NetFlix. When NetFlix upgrades to support Personal Address Managers, it sends an email to Bob requesting authorization for Subscription access to Bob's PAM. Bob gets the email and visits NetFlix to trigger the authorization. The rest is just like [[Personal_Address_Manager_Service#Scenario 1 Real-time authorization request|Scenario 1 Real-time authorization request]]

====Scenario 2.2:3 Email request (fulfilled at PAM service) ====

Sally is a long time Twitter user, where she has stored her iName as a discovery service. Twitter develops a new service that utilizes the Personal Address Manager and discovers Sally's PAM Service. It submits a request directly to the PAM for authorization as a AddressSubscriber. The PAM authenticates Twitter and sends an email to Sally notifying her of the request. She visits the PAM, reviews the request, and authorizes Twitter as an AddressSubscriber to her work address.

===Use Case 2.3 AddressOwner Manages AddressUser Permissions===

====Scenario 2.3:1 Frank switches all of his AddressUsers to AddressRequesters====
Frank is a long time PAM user and has decided that AddressUsers who cannot support real-time address use through the AddressRequester role will no longer get updates via AddressSubscriber. He logs into the PAM, selects manage permissions and changes all authorized AddressSubscribers to be authorized AddressRequesters only. The PAM sends those Subscribers a notice of their changed status.

====Scenario 2.3:2 Sally changes a trusted AddressUser's permissions to include her home address====
Sally is a satisfied customer of Brand X Boutique, who currently has authorization to access Sally's business address. Sally wants to ship a product to her home. She logs into the PAM, selects the AddressUser's Permissions, authorizing access to her home address in addition to the work address already authorized.

====Scenario 2.3:3 Betty changes a trusted AddressUser's permissions (triggered at AddressUser's site)====
Betty is at a trusted site, Expedia, where she is completing a transaction. Expedia is already an authorized AddressRequester, so it presents the current address for confirmation. Betty would prefer to use one of her other addresses, so she tells Expedia to request additional addresses from her PAM. Expedia redirects Betty to the PAM service, requesting additional addresses. The PAM authenticates Expedia and presents Betty with a a web page for approving access to her addresses. Betty selects the appropriate address, indicating "one time only" and the PAM redirects back to Expedia with the requested data and access rights. Betty completes her transaction at Expedia.

===Use Case 2.4 AddressOwner Deletes AddressUser===
====Scenario 2.4:1 Bob deletes Apple as AddressUser====
Bob has decided he no longer wants Apple to have access to any of his PAM services. He logs into the PAM, selects Apple as an AddressOwner, and selects "delete". The PAM confirms the deletion, asking Bob whether or not to notify Apple of the deletion. Bob confirms and indicates "Do not notify". The PAM deletes the AddressUser and records the change in the log.

===Use Case 3 AddressOwner Manages Delegates===
===Use Case 3.1 AddressOwner Authorizes Delegate===

====Scenario 3.1:1 Bob gives executive assistant authority over work address (email)====
The company is moving Bob to a new address so he gives his executive assistant Mike authority to manage his "work" address. He visits the PAM, identifies his assistant by email, and sets the permissions. The PAM service sends Mike an email informing him of the new authority with directions for authenticating. Mike visits the PAM, authenticates, and now has authority to manage Bob's address.

====Scenario 3.1:2 Bob gives executive assistant authority over work address (OpenID)====
Identical to Scenario 1, except that Bob identifies Mike by OpenID. In this case, the PAM discovers Mike's preferred contact method and contacts Mike appropriately. When Mike logs into the PAM, Mike's iName identity provider is used to authenticate.

'''QUESTION''' Is OpenID always gauranteed to provide a contact method? Or do we need a scenario where Mike is identified by OpenID, but contacted via an email specified by Bob at the time of authorization?

===Use Case 3.2 AddressOwner Unauthorizes Delegate===
====Scenario 3.2:1 Bob's Exec. Asst. Mike Quits====
Mike quits. Bob visits the PAM and revokes Mike's authorization.

===Use Case 3.3 AddressOwner Removes Delegate===
====Scenario 3.3:1 Bob Quits====
Bob quits. He visits the PAM and revokes Mike's authorization.

===Use Case 4 AddressUser Manages Delegates===
===Use Case 4.1 AddressUser Authorizes Delegate===
===Use Case 4.2 AddressUser Unauthorizes Delegate===
===Use Case 4.3 AddressUser Removes Delegate===

===Use Case 5 AddressUser discovers Personal Address Manager service for AddressOwner===
===Use Case 6 AddressUser Requests Authorization===
===Use Case 7 Delegate requests authorization===
===Use Case 8 AddressRequester Requests Current Address===
===Use Case 9 AddressSubscriber Activates Subscription===
===Use Case 10 AddressSubscriber Deactivates Subscription===
===Use Case 11 AddressOwner Accesses Activity Log===
===Use Case 12 AddressUser reports address change===
===Use Case 13 AddressOwner acknowledges address change===
===Use Case 14 AddressOwner downloads data===
===Use Case 15 AddressOwner authorizes automated export===
===Use Case 16 AddressOwner creates account===
===Use Case 17 AddressOwner deactivates account===
===Use Case 18 AddressOwner deletes account===
===Use Case 19 Administrator creates account===
===Use Case 20 Administrator deactivates account===
===Use Case 21 Administrator deletes account===

==Abstract Use Case Narratives==
An implementation and technology-free chronological ordering of user intention and system responsibilities for a particular use case. Based on one or more specific Scenarios, define the specific, yet technology-free, interactions that are required for the use case. These narratives will be normative, that is, they will ultimately define the requirements of the functioning system.

===AddressOwner Changes Address===
{| border="1" cellspacing="0" cellpadding="5" align="center"
! width="50%"|User Intention
! width="50%"|System Responsibility
|-
| 1. AddressOwner decides to move.
|
|-
| 2. AddressOwner expresses new address to system (optionally including scheduling information).
|
|-
|
| 3. System assures AddressUsers get the new address when they need it.
|}

WikiQuestion/suggestion: let's set this up as a template.

==Specific Use Case Narratives==
Implementation-specific sequences of user action and system response for a use case. These narratives will be illustrative, that is, they will show how a particular set of technologies can implement a particular use care--or how a specific set of technologies might require or suggest changes to the use case.

==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.
==Use Case Maps==
A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.
==Constraints & Requirements==
In addition to responding to specific use cases appropriately, every VRM Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity.

When mapping out the first set of use cases, it became clear that the a few of the core Use Cases were already substantially met by such online services as Plaxo and LinkedIn, raising the question of what would actually make a Personal Address Manager service VRM-compliant. That led directly to a handful of simple requirements that assure the user and vendors have appropriate access and controls.

#Address stored independently of any particular service provider
#AddressOwner can choose who stores canonical source (self-storage ok)
#Data should be in an open format and portable without data or service loss
#Data transfer and use is always under user control
#AddressUsers can discover the appropriate CoA service for each user
==Policy Requirements==
Implementations must meet the following policy requirements.

===Administration & Operations===
#Specified Data Visibility--Service providers must specify and implement either a visible of invisible data strategy.
##Visible Data - Data stored with the Service provider is visible to administrators.
##Invisible Data - Data stored on the Service is encrypted and not visible to administrators.
#Constrained & Logged Data Modification--All data modifications must only be made through explicit Roles as defined in the specification. All data modifications must be logged in a system activity log. All system activity must be auditable by users and their delegates.
===Representation & Warranties===
Service providers must explicitly specify, represent, and legally warrant their policies in the following areas.
#Privacy
#Security
#Survivability
#Accountability
Note: these areas need to be more clearly and completely specified. See the [[http://gss.xdi.org Global Services Specifications]] as informative of the type of self-asserted warranties will be required by Personal Address Manager Service providers.

==Technology Review==
Review relevant technology and existing services, highlighting how they inform our development, either by highlighting successful ideas or as examples of what we should avoid.
===Services===
*LinkedIn http://www.linkedin.com
*Plaxo http://www.plaxo.com
*Ryze http://www.ryze.com
===Technologies===
*FOAF http://www.foaf-project.org
*hCard http://microformats.org/wiki/hcard
*OAuth http://www.oauth.net
*OpenID http://openid.net
*XDI http://en.wikipedia.org/wiki/XDI
*Information Cards, with implemetations such as [http://www.microsoft.com/net/cardspace.aspx MS CardSpace] and [http://www.eclipse.org/higgins/ Higgins]
*Liberty Alliance Identity Web Services Framework (ID-WSF) http://www.projectliberty.org/liberty/specifications__1

===Organizations/Movements===
* DataPortability.org http://www.dataportability.org
* Microformats http://microformats.org
* Liberty Alliance Project http://www.projectliberty.org
* OpenLiberty.org http://www.openliberty.org [http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
* Concordia Project http://www.projectconcordia.org
* [http://informationcard.net Information Card Foundation]

==Formats & Protocols==
We will need formats for
#Representing an address (machine readable)
#Presenting an address (human/postal service readable)
#Personal Address Manager metadata
##Address Metadata
##*Address Name
##Authorizations
##Log data

We will need protocols for
#Authenticating AddressOwners, AddressUsers, and delegates
#Authorizing AddressUsers & Delegates
#Service discovery
#Inbound human services
#*most likely web pages
#Inbound automated services
#Outbound automated services
#*email

Organization Committee

2009-11-26T20:32:29Z

Maniac:

The objective of the Organization Committee is to
'''Create a lightweight and effective organisational structure'''

This page will be the central point of organization for the committee.

This is a placeholder page, soon to be replaced by committee members.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Category:1876 establishments

2009-11-26T20:31:19Z

Maniac: New page: [http://www.sexalemi.org sikis izle] [http://www.pornositeleri.net porno izle] [http://www.sexalemi.org sex izle] [http://www.sexalemi.org sikis] [http://www.cinsel.name sikis izle] [http:...

[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Category:Working Draft

2009-11-26T20:30:44Z

Maniac:

This page lists the current VRM Working Drafts.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

Category:Standards Committee Teleconferences

2009-11-26T20:30:21Z

Maniac:

This pages links to all of the Standards Committees Teleconference notes
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

March 21 2007 Meeting notes

2009-11-26T20:29:38Z

Maniac: /* Action Items */

==Conference Call Notes==
Drafted by Joe Andrieu, March 21, 2007
==Invitation==
==='''Next VRM Conference Call: Wednesday March 21 at 10:30 AM Pacific / 1:30 PM Eastern'''===

Here are all the key details:
*VRM Conference Call
*Date: Wednesday, March 21, 2007
*Time: 10:30 PDT, 1:30 EST
*Dial-in Number: Please note, this is the NEW NUMBER to use!!
*Conference Bridge Access Code #:

As usual we are going to record the call for potential future use as a reference audio or podcast. The MP3s of the two prior calls can be found on the Community Portal page of the Project VRM wiki.

Do you have an agenda item for the call? Please send it to the group (or to [mailto:deanland@gmail.com me (DeanLand)], if you're feeling shy).

==Other Calls==
[[Category:conference call]]
[[:Category:conference call]]

==Attendees==
* Joe Andrieu
* Dean Landsman
* Doc Searls
* Chris Carfi
* Dan Miller
* Drummond Reed
* Ty Graham

==Status==
{|
|'''what'''|| '''who'''||'''when'''||'''status'''
|-
|open id on wiki||david ||no date
|-
|group blog/RSS to wiki (venus)||doc||no date||'''needs multiple authors'''
|-
|project VRM definition/vision statements||doc||tomorrow||'''still working on it'''
|-
|brainstorm Initiatives||all||ongoing
|-
|write up Public media initiative||Doc||Monday||'''done'''
|-
|Set up Jabber Host for conference calls||doc||next week|| progress is being made
|-
|Polish VRM website||Joe||meeting in one week Next Item||working meeting happened.
|-
|Bullwhip effect reference||Chris||Tomorrow||'''done'''
|}

==Notes==
===Supernova===
From Deborah Schulz:
Two ways that we can participate at Supernova:

1- There will be an entire track on the "challenge day" devoted to the changing nature of markets/marketing. Perfect for some VRM discussions. Kevin (and I) really want Doc to participate in one of those conversations

2- have a second Project VRM face to face as part of the Unconference day before the official conference starts.

This looks like a good way to reach out, even though our speakers won't be a highlight of the conference.

===Second Project===
Coming from Iain Henderson:

Desire to see a second project or guidance on how to do so. The radio program isn't as applicable over here in Europe.

I'm happy to take the lead on a project that relates to personal information and VRM - that is the space of most interest to me; I logged an initiative around that on the wiki a while back, although that one is big and wide - so maybe I need to come up with a smaller bite sized chunk, e.g. customers making cross-organisation purchase data available to preferred suppliers as Whit blogged about earlier in the week. I could have a prototype of that up and running before the May 14th event if that would be useful?

Doc:
There is already a home for the Public Radio initiative, called Pub Forge, driven by the folks already in that space. The VRM group is in a great positive to support, rather than drive that initiative.
===Process & Organization Development===
This leads directly to how we grow our efforts organizationally.
While we are new, we are operating as a Berkman project. The most inner group are the folks on these conference calls, volunteering to help move this idea from concept to reality. Then, heading outward is the Berkman support infrastructure and brand and resources. Then, further out are other projects that interrelate and help.

Our role is to be the authority on VRM so we can help other folks doing VRM, but not necessarily doing the work ourselves.

As we figure out what VRM is, having some sort of kit that would help people VRM-ify a company or process.

One of the driving questions is: in the simplest form, what is VRM in its most fundamental:
1. It's for the user, comes from the user, everything else is subordinated. Not so much user-centric, i.e., transforming existing systems toward the user, but a program that starts and is controlled from the user.

Something Doc has observed about all the Open Source efforts, although there is some moral center, there is some individual who is ''in charge'', who has the moral authority to drive the process. Perhaps the best example is Linus and Linux. He has some basic principles that drive the style.

It's not so morally tied in, but if you look at Asterix, Mark Spencer has self-appointed as the determinator of what is or is not appropriate.

Recently at SXSW there was a great conversation about ''the final arbitrator'' and a team of validators, with a meritocratic view of how contributions are vetted.

One challenge is the disjoint between end users and the corporations that build the systems. In those cases, the population that is most impacted is often outside the process.

In these cases, there is some entity working as a proxy for the user, setting a framework for how we create value. It turns out to be a thankless job, because it is often invisible to the beneficiary. But if it actually builds momentum and grows out of Berkman into the real world, we can create a set of practices, design theory, etc., that can have significant impact.

Doc is seeking to get clear on his role. He is by nature a bit of a firestarter... sparking the fire and moving on. But he wants to be more active and more involved. No two open source projects are the same and plus, this isn't quite an open source project. I'd most like to see that the projects of the people on the team are doing becomes VRMy and succeeds. It is an interesting question, especially once we get funded. In fact, we just got a small amount of funding from an unexpected source. So things are developing. That begs the question of what do we want to do and how do we want to apply this money through the Berkman system.

Berkman likes to hold events or hire students. Those are two of their models for action. They have others.

How can we help what any of "you guys" are doing? Maybe there is some kind of standards and practices thing. Something that we could provide.

Question: What are the big payoffs for the average Internet users?

It allows consumers to be customers and not just consumers. It provides tools for both independence from vendor silos and engagement with vendors in a way that none of us have experienced yet.

One example: Single-sign on. The ability to control your identity as you sign on to various things across the net. The process at Yahoo wrt Flickr is incredibly frustrating. Doc has had to create three new Yahoo sign-ons trying to login to Flickr, and it is apparently still broken. We should be able to just login and forget about it. We don't need logins for the local store. Why do I need it online?

The difference is that VRM continues beyond the initiation of the relationship (Identity).

What we want to be able to do is share the meta-data around the relationship with the vendor. For example, a VRM wishlist would live with me as the user, not embedded in the vendor's silo. Where both parties have mutual access to that data.

Another example is projection. When I show up at a site, it should warp around me, just knowing what I want, based on standard identity-based preferences (such as text-size).

If you have a VRM-savvy client, you can get that projection without a separate interface.

Architecturally there is nothing that happens on the side of the customer. So, the websites can't even handle it. Can one organization do it? This is a revolution we are trying to start, and we can start at the edges.

Another point to be made is that when we look at CRM, there is no problem with Best Buy or Circuit City taking your wishlist if you choose to give it to them. We are creating a tool that lets Vendors and Users manage these engagements. CRM companies don't really care about users, its more about customer-specific marketing. The idea is to put this out in the user control. There is no problem with doing both. Say, I go to a given store and I ask for an XXXX. From the rest of my life, I'm likely to get hid with XXX-related ads. But it may be largely irrelevant to me, and is a waste of their marketing output. With VRM, we can avoid that.

If I were to put out a personal RFP that I were to buy a car and I control who can respond. As opposed to signing up for SPAM and offers, etc. I don't want to be locked into that consumer category. VRM allows users to emanate, but having control.

Amazon lets you have wishlist and share your wishlist. So perhaps part of what we might do is provide some sort of rating system about how VRM-y a vendor is.

I'd like to extend this beyond just VENDOR management, but also to have a personal RFI, extending beyond the personal vendor-customer relationship and creates new vendors out of people. There is a huge new potential in this area.

User-side, isolated customization.
*Client side CSS
*Grease monkey

But we don't need to be isolated. Think of a client-side plug-in with the opportunity to provide identity-aware cookies/data to the service. This data can be used to drive common customization capabilities in a manner that ''engages'' the vendor rather than just isolating the user.
===Projects & Events===
IIW
Identity Open Space in Brussels

Let's look towards some of these events as landmarks as some of our work that we are doing independently.

Joe: I'd like to get a few visual and narrative explanations of how VRM fits into the big picture:
* Map of related efforts (ecosystem), especial wrt identity efforts
* Kernel/user space map: what is the core of VRM and what is use case specific?

In linux, the management of the ideal kernel drives design and development. Period. Don't add code to the kernal unless it improved the entire kernel, even if it /would/ help some particular application.

Our challenge is that we don't have a well defined kernel yet. We have a few underlying principles and a variety of use cases. We need to map out how these inter-relate.

==Action Items==
{|
|'''what'''|| '''who'''||'''when'''||'''status'''
|-
|open id on wiki||david ||no date
|-
|group blog/RSS to wiki (venus)||doc||no date||'''needs multiple authors'''
|-
|project VRM definition/vision statements||doc||tomorrow||'''still working on it'''
|-
|brainstorm Initiatives||all||ongoing
|-
|write up Public media initiative||Doc||Monday||'''done'''
|-
|Set up Jabber Host for conference calls||doc||next week|| progress is being made
|- [http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
|More work VRM website||Joe||meeting in one week||first meeting productive
|-
|Add Bullwhip effect reference to wiki||Joe||Next Wednesday||'''new'''
|-
|Get personal database started as an initiative||Joe & Doc||Next Wednesday||'''new'''
|}

==Next Meeting==
April 4, 1:30PM EST/10:30AM PST

April 16 2008 Conference Call

2009-11-26T20:28:54Z

Maniac: /* Action Items */

==Conference Call Notes==
Drafted by Joe Andrieu, April 16, 2008 

==IRC==
#vrm at chat.freenode.net

==Other Calls==
[[Category:conference call]]
[[:Category:conference call]]

==Attendees==
* Joe Andrieu
* Dean Landsman
* Doc Searls
* Keith Hopper
* Renee Lloyd
* Iain Henderson
* Chris Carfi
* Drummond Reed
* Alan Mitchell

==Previous Action Items==

==Notes==

===Introductions===
Introduction to Renee Lloyd. She is a lawyer with lots of experience with startups and engineers, including open source efforts and at RSA. Some time at the IP offices of Harvard. Now at Berkman, advocating the law and role of lawyers in a positive, helpful framework.

===Vision Committee (Dean)===
Wikipedia sandbox page has been developed. Please check it out and contribute.

[[VRM_vision]]

We would like to get this polished enough to move to Wikipedia before next week in Munich.

Doc remains on the button for a white paper on the VRM vision. That has been interrupted a bit by the recent medical engagements.

Sean Bohan (and others) have made excellent progress on a VRM Maturity model. Please take a look and give feedback. Solid document, but now needs to work through consensus to approval and annointment by our benevolent dictator.

===Standards Committee (Joe)===
Challenges getting outside input on the Personal Address Manager. Consensus is that we get the most engagement in real-time, in-person meetings. So let's do more of those.

Several good Relbutton conversations. Next step from the standards perspective is to map out, in the PayChoice case, what the desired relations are for the radio stations. PayChoice is fairly straightforward, but there are other ways to relate to a given audio program. Let's figure those out and we can talk about how we use the relbutton to manage those relations.

This American Life experimented with a direct support request that only went out on a podcast. The result was far higher than expected.

Re: iTunes, Doc wants to get this far enough downstream so we can say here are the icons, here are the liberty pieces, here are the public interactive pieces... present a fait-accompli to the folks at Apple.

Question: are there issues with Liberty's links? Doc says not really. CardSpace already represents the WS* side of things (which is not Liberty). Drummond agrees. The Liberty perspective verse the MS perspective verses OSS perspective... we can't say any one of those are right. The market will sort it out.

Keith mentioned conversations with Parity to understand what they offer. He will also be talking with folks from WBEZ and KCRW, who expressed interest in the relbutton at the Media Re:public forum.

Doc & Renee discussed how the contract & access rights terms can be modularly standardized, akin to Creative Commons, with their three criteria: machine readable, human readable, lawyer readable.

The different kinds of data could be presented or shared according to these common terms.

What we need to do next is to unpack the potential ways we can relate. The traditional membership fee and t-shirt is just one model. There are other ways to construct the relationships.

===Organization Committee (Doc)===
Started a conversation with Renee about how we might protect VRM from being hijacked as a marketing term. There's a thought that we need an organization in place. But maybe there are other options.

===Usage Committee (Adriana)===
no report

===Compliance Committee (Iain) ===
Will be preparing a proposal based on using a UK based organization.

===Events===
====VRM2008====
Joe will be there. Charles Andres might be. Iain and Doc won't make it. Not sure about anyone else.

We expect about 20-25 folks there, which is enough to get some energy going, but still intimate enough for Doc to contribute from someone's laptop.

===Open Discussion===
====Twitter Feed====
Keith Hopper created a VRM pipe clone in the twitterverse using @vrm. [http://twitter.com/VRM @vrm] now retweets VRM posts from folks it is following (which is most of the VRM leadership).

===Action Items===
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

==Next Meeting==
[[April 30 2008 Conference Call]]

PayChoice

2009-11-26T20:28:09Z

Maniac: /* FAQ */

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

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

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

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

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

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

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

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

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

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

=== Micro-accounting ===

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

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

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

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

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

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

=== Projects ===

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

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

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

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

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

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

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

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

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

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

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

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

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

There is also the need to address the likelihood that advertising -- the primary source of income for many media enterprises -- will either be severely diminished or go away, simply because ways will be found for demand to find supply that are more efficient than the guesswork that advertising involves. PayChoice will be one way to take advantage of this inevitable shift in the marketplace.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[[Category:Media Logging]]

VRM West Coast Workshop 2009

2009-11-26T20:27:24Z

Maniac: /* Materials */

The first ProjectVRM West Coast Workshop (tag [http://technorati.com/tag/vrm2009 vrm2009]) took place on Friday-Saturday 15-16 May, 2009 at [http://www.sap.com/usa/index.epx SAP Labs] at [http://maps.google.com/maps?f=q&hl=en&geocode=&q=3410+Hillview+Ave.,+Palo+Alto,+CA+94304,+USA&sll=40.768582,-74.492798&sspn=0.372862,0.744324&ie=UTF8&z=16&iwloc=addr&om=1 3410 Hillview Street in Palo Alto]. (This is a beautiful space in the hills of Palo Alto, overlooking San Francisco Bay, with plenty of parking. And we thank SAP kindly for making it available.)

The event went from 9am to roughly 5pm on both days.

As with earlier VRM gatherings, the purpose of the workshop was to bring people together and make progress on any number of VRM topics and projects. The workshop was an "unconference" on the open space model, which means session topics were chosen by participants.

In open space there are no speakers or panels -- just participants, gathered to get work done and enjoy doing it. Participation includes contributing to the workshop wiki. [http://en.wikipedia.org/wiki/Open_Space_Technology Here is the Wikipedia page on open space.]

== Registration ==

The workshop was free. Registration was through [http://vrmwestcoast2009.eventbrite.com/ this EventBrite link]. [[VRM West Coast Workshop 2009 Attendees]] is also a partial list of attendees.

== Topics ==

Here are some of the topics discussed at the workshop:

* [[Defining 1st and 4th Parties]]
* [[Personal Data Stores]] - the fundamentals that apply to them regardless of context/application
* [[Personal Health Records]]
* [[VRM + CRM]]
* [[ListenLog]] (open source public radio project)
* [[EmanciPay]] (PayChoice)
* [[VRM + Open Source]]
* [[VRM + Patient Driven Health Care]], which also involves [[Personal Health Records]]
* [[VRM + Enterprises]]
* [[VRM and retail]]
* [[VRM and search]]
* [[The Mine! Project]]
* [[ProtectServe]]
* [[User Asserted Terms of Service]]
* Getting rid of those tick-boxes.... (Volunteered Personal Information & Data Sharing Agreements)
* [[VRM Marketing]] (Marketing committee + others)
* [[VRM organization(s)]] (Start-up committee - picking up where we shouldn't leave off))
* [[VRM + Enterprises]]
* [[FCRA: Access to credit data]] (D&B, FICO score compilation and access to credit)
* [[VRM + RideSharing]] Is Ridesharing support a VRM business?
* [[What is it going to take to get this great change started?]]
* [[What can go wrong with our VRM vision (and how do we avoid that?)]]
* [[Developing Communities of Interest]]
* [[Drafting an Agreement]]

== Agenda ==
''Below was a live agenda.''

'''''Session 1'''''
* '''A:''' [[Reality of VRM]]: Market Drive Approach, not Technology (top down vs bottom up) (Furrier)
* '''B:''' [[Identity Options for Personal Data]] (simplified) (Keith Hopper)

'''''Session 2'''''
* '''A:'''
* '''B:''' [[User Driven Services]] (Joe Andrieu)

'''''Session 3'''''
* '''A:''' [[Health VRM]] (Mike)
* '''B:''' [[Terminology]]

'''''Session 4'''''
* '''A:''' [[Personal Data Stores]]: why and how central to VRM (Drummond and Iain)
* '''A.1''' [[Access to Credit Data]]

'''[[Wrap-up Day 1]]'''

'''Day 2'''

'''''Session 5'''''
* '''A:''' [[Personal RFPs]]
* '''B:''' [[Prototyping VRM Mobile Social, iPhone]]

'''''Session 6'''''
* '''A:''' [[Personal Data Stores, Mobile Prototypes]]
* '''B:''' [[How big is market for 4th Party Services?]]

'''''Session 7'''''
* '''A:''' [[User Driven Search]]

'''''Session 8'''''
* '''A:''' [[Giving Local Business and Voice in Age of Yelp]]
* '''B:''' [[4th Party: What Defines One?]]

'''''Session 9:'''''
* '''A:''' [[VRM Marketing]]
* '''B:''' [[The role of social enterprises in VRM]]

'''''Session 10:'''''
* '''A:''' [[Terminology]] continued
* '''B:''' [[EmanciPay & Rel Button]]

== Schedule ==

=== Friday May 15 ===

Morning Refreshments - 8:30

Opening 9-11
* TBD (will involve brief reports from various VRM projects)

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

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

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

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

4:30-5:30 Larry Chiang made Hot Dogs. They were amazing. [http://search.twitter.com/search?q=%23swFoo+%40larryChiang/ #hotdogs]

7:00PM:
===='''Non-hosted Dinner'''====
* Location: TBD
* Time: TBD
* Attendees (please add your name here if you plan to attend so we can get reservations):
** Iain Henderson
** Doc Searls
** Judi Clark
** Maurice Sharp
** Keith Hopper
** Joe Andrieu
** Drummond Reed
** Markus Sabadello
** William Heath
** Craig Burton

=== Saturday May 16 ===

Morning Refreshments - 8:30 (Open. We provide this ourselves. How to do this is TBD.)

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

Sessions: 9am-4pm
* 9:00-10:00 Session 5
* 10:10-11:10 Session 6
* 11:20-12:30 Session 7
* 12:30-1:45 LUNCH - Pizza, ordered in. We'll pass the hat to pay for it.
* 1:45-2:45 Session 7
* 3:00-4:00 Session 8

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

== Location ==

SAP Labs is a beautiful facility with plenty of parking in the hills of southwest Palo Alto. A map is [http://maps.google.com/maps?f=q&hl=en&geocode=&q=3410+Hillview+Ave.,+Palo+Alto,+CA+94304,+USA&sll=40.768582,-74.492798&sspn=0.372862,0.744324&ie=UTF8&z=16&iwloc=addr&om=1 here].

== Materials ==

This list is maintained to make it easier for the next session to copy and paste.

* Blank name tags
* Easels with pads
* Markers
* Large sticky edged post-it notes
* Stacks of paper or cards for posting topics on the wall
* Wide paper to put up on the wall and create the spreadsheet of topics and locations
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]

R-button

2009-11-26T20:26:45Z

Maniac: /* Domain names */

The r-button is a short name for a ''relationship button''. This button can be used to request, establish and maintain relationships between entities on the Web, including transactions. In the latter sense an r-button can also be seen as a pay button, but its functionalities are not limited to transaction. (For more about how it might work in a transactional context, see [[EmanciPay]].)

The r-button is being developed by the VRM community primarily to provide a means for individuals to express their interest in relating to vendors of goods and services -- on those individuals' terms, and not just those of the vendors. It can also be used by vendors to express interest in relating to individual customers on mutually agreeable terms.

The purpose of the r-button is to open and represent relationships are two-way rather than one-way. It is how VRM meets CRM, for the good of both.

The r-button will open markets to countless opportunities that are locked out by the lock-in approaches of traditional vendor-driven business relationships. In this old model, the vendor sets all the terms and conditions -- and in too many cases making only educated guesses at what customers actually want. With VRM, they'll know.

Here is the current basic r-button design:

[[Image:Icon4.gif]]

The button combines reciprocal symbols for customer and vendor, each represented by red "magnets" facing each other.

There will be smaller and simpler versions for use, for example, on mobile devices and in browser location fields (where symbols for RSS and bookmarks now appear).

== Visuals ==
The r-button is two icons in one. Each represents a magnet. Both are open to and facing, each other. This shape symbolizes openness, choice, independence, equality and intentionality. The paired icons can appear in four ways, each expressing a different relationship state:

1. Looking to buy something or to pay for otherwise free goods:

[[Image:Relbutton_sm_left.jpg]]

2. Looking to sell something or to offer a service:

[[Image:Relbutton_sm_right.jpg]]

3. In process of establishing a relationship:

[[Image:Relbutton_sm.jpg]]

4. Already in relationship:

[[Image:Relbutton_sm_closed.jpg]]

What makes these especially helpful and handy is that they give both sides all the virtues listed above. So, for example, when a vendor puts this symbol on a product or a site...

[[Image:Relbutton_sm_right.jpg]]

... they're saying "We're willing to do business with you on ''your'' terms as well as ours."

And, when the customer clicks on a closed button...

[[Image:Relbutton_sm_closed.jpg]]

... data from both sides can be brought in and displayed.

That data can be anything pertaining to relationship history, intentionality, preference... it's wide open.

As we consider what the r-button represents both for actions and for state, it helps to bear in mind Don Norman's principles of design, listed in his landmark book, [http://www.jnd.org/books.html#33 The Design of Everyday Things]:

# Visibility. By looking, the user can tell the state of the device and the alternatives for action.
# A good conceptual model. The designer provides a good conceptual model for the user, with consistency in the presentation of operations and results and a coherent, consistent system image.
# Good mappings. It is possible to determine the relationships between actions and results, between controls and their effects, and between the system state and what is visible.

== Basic Characteristics ==
* The r-button represents a free and open web service, with its own API, available to both vendors and customers, providing capabilities to both
* The button can be placed or activated by the customer on anything he or she might be willing to pay for -- or to indicate an interest in conversation or relationship
* The button can be displayed by the vendor as a signal that the vendor is open to hearing terms the customer presents.
* As with [http://creativecommons.org/ Creative Commons] licences and symbols, the r-button and its functions should be [http://creativecommons.org/?s=readable readable] three ways: by humans, by machines and by lawyers.

== Requirements ==
Before we proceed, here is what the r-button should and should not do:
* All but symbol 2 (vendor side only) should be under the customer's control.
* It should support true two-way relationships between customers and vendors in all three market domains: transaction, conversation and relationship.
* Unlike advertising and promotion, it will be a way that the customer can make the first move. It must support the ''intentions'' of the customer, and not just of the vendor.
* It should support the willingness of the customer to pay whatever they please. (Also to be willing to hear no and to negotiate the difference.)
* It should allow the customer to escrow (or record) the intention to pay, so the vendor can see that fact if customer wishes, and accept payment once the vendor puts the acceptance mechanisms in place. Customer intentions to pay or to relate in other ways should be visible exclusively to those vendors, even if the vendors do not yet have the mechanisms in place for perceiving them, or for accepting payment. This system will allow vendors' payment-acceptance and CRM systems to adapt to standard means by which customers, at their discretion, can ''transact'', ''converse with'' and ''relate with'' vendors.
* It should not provide means by which vendors coerce, entrap or otherwise "lock in" or "own" customers. Once relationships are established, they can be whatever customers and vendors agree upon. But as a means for "hooking up", or accepting payment, r-buttons cannot be under exclusive vendor control. For example, if a r-button on a music site brings up a list of fixed prices for selections and albums, the customer should still have the choice of offering amounts they please, rather than just the prices offered by the vendor. This doesn't mean the vendor has to accept what the customer offers. It does mean that the customer has means for offering what they like, including amounts higher than the vendor is asking.
* It should support the expression of preferences. This includes conditions for relationship, such as selective disclosure of personal data, conditions for the use of personal data, interest in specific (and defined) future products, and interaction requirements. Among the latter might be, for example, the preference ''not'' to receive promotional messages when calling for tech support.
* It should support customers and vendors both retaining records of interactions in the course of relationship, including transaction histories, contact histories and other variables. Among many other things, these should be able to back each other up at times when the other party loses data.
* Both parties should be able to cease relationships, on mutually agreeable terms.
* Selective disclosure of data by both parties is essential to the operation and success of the system. Customers should be able to reveal no more about themselves, their intentions, and their interests, than the situation requires. Once in relationship, selective disclosure is also essential for establishing and maintaining trust.
* For identity-based interactions, r-button relationships should obey the [[http://www.identityblog.com/?p=352 Seven Laws of Identity]]
* A link to the [http://cyber.law.harvard.edu/projectvrm/R-button_Functional_Specification R-Button Functional Specification (Spec)]
* While r-button functions can support an endless variety of intermediary and third-party services (such as negotiation, brokerage, concierge service and secure data storage), at its base level the r-button on the customer side should support complete autonomy and independence from third parties. In other words, the customer should be able to keep his or her own data stores of intentions, transactions, preferences, and other variables.

==Scenarios==

===Media in general===

The first use case for the r-button is media. These include

* public media, including stations and programs
* citizen and participatory media, including otherwise free online publications
* podcasts
* online publications, including blogs
* pieces of music, along with artists and producers

The VRM community already includes participants from public media, and many public media entities are interested in rolling out r-button based VRM as a means for scaffolding a new business model that can reduce MLOTT, or Money Left On The Table by current (subscription and sponsorship) business models. This model, called [[PayChoice]], is the first and only model to provide listeners and viewers with the means to initiate relationships, and to pay whatever sum they want for whatever goods they want, with minimal friction.

In traditional public media membership models, transaction is too often conflated with relationship. Too often "membership" consists of an exchange of cash for promotional goods, and an implicit "agreement" to be subject to direct mail and other appeals for additional donations. With r-button based relationships, membership can mean much more for both parties.

In fact, as listeners and viewers face more choices of more ways to obtain programming, it is essential for stations to start relating in more ways, and to take leadership from listeners and viewers in doing so. With the r-button and VRM, relationships can be far more rich and real. And stations can begin to intermediate other relationships as well, for example with recording artists and guests on shows.

Localization will also become a matter of content and interaction, rather than of signal coverage. And localization will become an essential means of survival and prosperity as stations pass from the analog to the digital age, and iPhones and their like become the transistor radios of our time.

Subsequent use cases include

* commercial radio
* commercial television
* music
* all other forms of digital content

===r-button on hand-held phones and computers===
The MID, or Mobile Internet Device category has become white hot in the two months since Apple opened the iPhone to third party applications. The explosion of apps on the iPhone platform has established a whole new product category -- one in which the telephony is one application among a countless assortment of others, including radio.

The first generation of iPhone apps includes at least four radio tuners that tune in to data streams broadcast on the Net. Our own tests of these apps make clear that online streaming through the cell system to cars offers major advantages over conventional FM and AM radio transmission. For example, Doc Searls listened to Boston's WBUR from Lancaster to Santa Barbara, California, a distance of 130 miles on both highways and backroads, with only one interruption from a dropped AT&T cell system signal -- and the stream was quickly restored. Over that same stretch no terrestrial radio signal equaled the performance of WBUR over Doc's iPhone. It beat all the Los Angeles FM stations with powers upwards of 100kw atop Mt. Wilson, plus all of the regional public stations (KPCC, KCRW, KCLU) and their many translators.

===r-buttons on radio apps===

Radio is the first place we'll test out, shake down and standardize the r-button as the doorway to markets where customers as well as vendors are "in charge," and countless new products and services can be built on top of better customer expression and control of personal data.

For this we will either create a new radio tuner for the iPhone or work with one of the current tuner developers. Either way we will produce a tuner in which the r-button is supported.

The r-button should be a standard feature of these radio tuners to begin with. If you design a stream tuner (or, for that matter, a podcast player that allows users to interact by producing as well as consuming data), it needs to support r-buttons and r-button-based interactions.

===r-button affordances===

In his book [http://www.jnd.org/books.html#426 The Design of Everyday Things], Donald Norman says "the term ''affordance'' refers to the perceived and actual properties of the thing, primarily those fundamental properties that determine just how the thing could possibly be used."

As operative icons, r-buttons have the affordances of magnets.

The r-button is two icons, or two magnets, in one. The left magnet is the user's.

[[Image:Relbutton_sm_left.jpg]]

It activates two choices: 1) to express the intention to relate in one of a variety of ways (pay something, record data, send a message, assert terms); and 2) to visit the user's data store, which may contain many different kinds of data (e.g. standing requests, transaction records, links to [http://www.equalsdrummond.name/?p=135 r-cards] or other identity assertion mechanisms -- none of these are ever visible to anybody other than the user or -- in highly controlled conditions -- trusted third parties). The user can also click on the vendor's magnet, to see if the vendor is willing to engage, and in what ways. The right magnet is the vendor's.

[[Image:Relbutton_sm_right.jpg]]

Through it the vendor expresses a willingness to engage with customers, to do business with them, and to establish relationships (which may be enduring or transitory, depending on the goods or services being offered). To the customer this button signals a willingness to at least listen to customers' offerings, terms and conditions. These will inevitably (and necessarily) standardize quickly once r-button based interaction becomes common.

There are states between first contact and established relationship, such as when a vendor responds to a personal RFP (request for proposal -- say, for purchase of a stroller for twins in a given city in the next 24 hours) -- but the customer has not yet agreed to buy. In these cases contact code is exchanged, reddening both sides of the r-button, but not joining them:

[[Image:Relbutton_sm.jpg]]

This configuration can also represent past relationships. In this case the symbol means that contact has been established in the past, and clicking on the icon will bring up relevant information from each party's own data store.

Once a relationship is in effect, the two magnets into a single object:

[[Image:Relbutton_sm_closed.jpg]]

In each case either party can query their own data stores to discover the status of the relationship. And replicate what data they like in other data bases.

Since r-buttons are two buttons (or magnets) in one, and two-in-one icons are a novel idea, all four r-button configurations can fall behind a single open r-button:

[[Image:Icon4.gif]]

====On iPhone====
On the iPhone, this symbol will be one of several that appear in the tab bar at the bottom of the screen. (iPhone developers can see where this is [http://developer.apple.com/iphone/library/documentation/UserExperience/Conceptual/MobileHIG/WorkingWithUIElements/chapter_8_section_2.html#//apple_ref/doc/uid/TP40006556-CH3-SW10 iP here].

Here is are two early mock-ups showing the r-button in iPhone tabs:

[[Image:Iphonebrowsing 1.jpg|800px]]

[[image:Iphonerelationshipflow 1.jpg|800px]]

====On Browsers====
On browsers, the r-button will appear as via add-on or extension as an icon in top of the browser frame (what was called the "chrome," until Google gave that name to a whole new browser), to the right or left of the address bar. This is where Delicioius and other add-ons also appear. One good example of a multi-part icon is [https://addons.mozilla.org/en-US/firefox/addon/5756 Taboo's]. In fact, it is on Taboo's icon pair that this example of one r-button approach is based:

[[Image:Kqed_chrome.jpg]]

Note that this is meant for discussion purposes (for example, to see if the r-button works in this layout, which it appears to do).

==Other items==

===Domain names===

Doc has purchased for the project the following variants on r-button:

#r-button.com
#r-button.org
#rbuttn.com
#rbuttn.org
#rbttn.com
#rbttn.org

And Joe has purchased

#rbutton.org
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[[Category:Media Logging]]

Media Logging

2009-11-26T20:25:58Z

Maniac:

Media Logging is required for [[EmanciPay]] to work.

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.

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

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

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

[[Category:Media Logging]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]