Random Notes from Jan 25th VRM Developers Meeting
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)
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 
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.
--deanland 19:53, 7 February 2007 (EST)