Project VRM - User contributions [en]

Media Logging

2009-12-04T09:46:38Z

Kelebek:

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.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.cinsel-sohbet.com cinsel sohbet]

Project VRM talk:Community Portal

2009-12-03T13:02:28Z

Kelebek:

merhaba, benim Åirket http://www.dataforcecrm.com olduÄunu. Biz bu sitenin gerÃ§ek dÃ¼nya Intel gibi mÃ¼Återileri ile deyimiyle Ã¶Ärenin Ã¼zerine bir talep VRM vardÄ±r.

Jim
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikisi]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikisi]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek sohbet]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org sohbet sohbet]
[http://www.siberchat.net sohbet]
[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 sohbet]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr sohbet gay]
[http://www.cinsel-sohbet.com cinsel sohbet]

VRM Workshop

2009-12-03T13:01:44Z

Kelebek: 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.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.cinsel-sohbet.com cinsel sohbet]

Category:Standards Committee Teleconferences

2009-12-03T13:00:31Z

Kelebek:

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.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.cinsel-sohbet.com cinsel sohbet]

Standards Committee

2009-12-03T13:00:07Z

Kelebek:

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.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.cinsel-sohbet.com cinsel sohbet]

Scenarios

2009-12-03T12:59:08Z

Kelebek:

'''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.cinsel-sohbet.com cinsel sohbet]

Principles

2009-12-03T12:58:27Z

Kelebek: /* 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.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.cinsel-sohbet.com cinsel sohbet]

PayChoice

2009-12-03T12:57:52Z

Kelebek: /* 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.

[[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.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.cinsel-sohbet.com cinsel sohbet]

Mailing list

2009-12-03T12:57:25Z

Kelebek:

[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.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.cinsel-sohbet.com cinsel sohbet]

Information flow

2009-12-03T12:56:54Z

Kelebek:

As it emerged at the white board during a VRM session at [http://iiw.windley.com/wiki/Workshop2006b Internet Identity Workshop].

http://cyber.law.harvard.edu/projectvrm/images/c/ca/Vendor-relationship-management-flow.jpg

Some prose describing this diagram on [http://netmesh.info/jernst/Digital_Identity/doc-searls-vendor-relationship-management.html Johannes Ernst's Blog].

[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Upside-down buyers' guide]: a simple flow for, for example, ordering servers, using an RFQ microformat and the existing Technorati tag system.
[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.cinsel-sohbet.com cinsel sohbet]

Committees

2009-12-03T12:56:15Z

Kelebek: /* 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.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.cinsel-sohbet.com cinsel sohbet]

Expressions of Relationships

2009-12-03T12:55:51Z

Kelebek: /* Some interesting questions / thoughts */

These are my rough notes of what is being written on the flip chart during the VRM meeting breakout on 2006-01-25.

==Relationships vs. Expressions==
* [http://socialcustomer.typepad.com/vrm_expression_matrix.pdf Relationships v. Expressions (PDF)]

==Types of Relationships==
* marriage
* business partnership
* counselor
* subscription
* friendship
* family
* membership
* fanboy
* contract
* employment
* confucian
* mentor / advisor
* citizenship
* blacklist
* champion
* familiar stranger
* colleague
* teacher
* stalker
* neighbor
* patron
* customer
* vendor
* circle of trust
* sponsor
* priest / shaman / rabbi / ...
* advocate
* alumni
* nemesis
* cohorts
* shared experience
* enemy

==Expressions of Relationships==
You know it is a relationship when ...
* there are implications for the future
* expectations
* recognition
* subscription
* payment
* tipping
* genealogy
* hate sites
* strong feelings
* recommend
* contract
* employment
* ask advice
* expose yourself to vulnerability ("trust")
* blacklist
* conversation
* stalking
* repeat patronage
* badmouth
* reliance
* federation
* referral/introduction
* sponsor
* invite
* rebuff
* evaluate
* hug / PDA
* advocate
* commenting (e.g. blogs)
* give gifts
* find
* respond
* keep apprised
* request
* extend credit
* support
* vouch
* shared experience
* having coffee
* conferences

==Dimensions==
* Time
* Transparency
* Intensity
* Frequency
* Commitment
* Control
* Potential to real
* Latent to explicit
* Reciprocity
* Symmetry
* Frequency of interaction
* Cardinality

== Some interesting questions / thoughts ==
* Are we presuming that relationships are bidirectional? (e.g. crush) No ...
* Relationships are not boolean -- there is a degree, e.g. very close vs. "have heard of some guy.."
* Law/lawyers as a source of a relationship taxonomy
* Confucianism as a source of relationship taxonomy
* A social network that doesn't allow you to include your enemies isn't worth having.
[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.cinsel-sohbet.com cinsel sohbet]

Health VRM

2009-12-03T12:55:28Z

Kelebek:

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.

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.
[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.cinsel-sohbet.com cinsel sohbet]

Initiatives

2009-12-03T12:54:55Z

Kelebek:

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.cinsel-sohbet.com cinsel sohbet]

ListenLog Meeting Notes

2009-12-03T12:54:24Z

Kelebek: /* Notes on Identity Requirements */

[[Category:Media Logging]]
[[Category:Conference call]]

Below are meeting notes and ongoing issues and action item lists. For a detailed description of ListenLog, visit the main [[ListenLog]] page.

==1/12==
===Parking Lot===
* Where is data stored (by default)? Does it sync to a local store or just stream out?
* Is there any concern from collaboration stations and partners that there's no exclusive access to data / analytics?
* What data do we capture? Application behavior data in addition to basic listen data? What about rating data? Location data?
** Should the standard by minimal for extensibility vs. maximal for enhanced value/functionality
** Privacy concerns (EFF Chair Brad Templeton)
* Security / encryption on the stored data? Which bits?
* How best to communicate and promote the ListenLog concept and where the key benefits and differentiators are? How do we address naysayers and differentiate from alternative approaches, e.g. APML?
* How do we do identity? How do we make it swappable? Do we use icards, openID, Oauth?
* How do we start the service without identity? (e.g. access to device ID?)
* Do users have control over what's stored?
* What's the absolute minimum of device-side functionality?
** Opt-out(?)
** Change repository
** Assign identity
* Where does legal and TOS come in? (see rights and contracts below)
* Does anyone enforce standards compliance?
* Who does the work / coding?
** PRX + who?
* Do we think about revenue / sustainability? PRX has two roles here - one to build codebase and standards for storage, the other to think about services and how we'd use the data.
* Do we do opt out for data capture? (probably yes)
* Do we provide "public by default," e.g. ubiquitious, anonymous access to the data out of the box (probably no)
* Can we open source iphone bit? Publicly available libraries?
* What's in the first release?
** Should we provide ability for users to release data? How and to whom? What capacity for sharing? What terms? Anon vs. nonanon?
* Does there need to be database legal protection underlying data rights access to drive user terms?

==1/13==
* How do we make the data inherently more anonymous?
** Match account data between logs
** Make timestamp and LAT-LONG fuzzy?
* What data rights can a user authorize for third parties?
** propagation rights (the grantee can't extend to someone else)
** public rights vs. directed/granted rights (e.g. for anyone to use vs. for specific entity to use)
*** anon/non-anonymous
*** Most rights issues/rats nests are associated with granted rights
** How long you can use the data for? Keep the data?
** Rights to cease use, remove data(?) + confirmation(?)
** Can't use this to try and find/identify someone - reverse-engineering rights
** commercial/non-commercial?
** Contact me (e.g. DNC)
** Compare to IRB
* Contract rights
** Investigate proactively - what is it that pandora might want to do? What is reasonable?
*** give me audio recommendations
*** use for product development
** Don't cross-correlate/aggregate (e.g. social network correlation, Ben Laurie) - piercing identity/privacy data
** Endorsement / assignment to my identity

===Core Requirements===
* what data is going to be captured
* where is it stored and in what format
* how does one identify oneself / assign identity
* what's the minimum functionality that needs to live on the device
* what's the minimum functionality that needs to live remotely
* additional / core functionality to prove value necessary?
* Determine protections for communication and storage between client app and repository authenticated, encrypted, etc.

===Action Items===
* Draft functional requirements
* Doc talk to Berkman legal re: user rights / terms

==1/20==
* There is a core set of things to figure out to proceed with this project. We'll focus on those:
** What data will we capture?
** What format will we send and store the data in?
** How is this data being transmitted and stored?
** How do we maintain integrity, privacy, and provide the required minimum of user control (e.g. "delete my data")?
** How do we assign or associate identity?

* In discussing data capture, Keith argued for being minimal and conservative and providing a mechanism for extending
* Agreement that our proposed data, format, and services will deal with listening attention data only; both for on-demand (file) audio as well as streaming audio
* Open question about whether Sound Exchange / RIAA requires specific formats, if so, might be nice to comply
* XRI be resolved / discoverability

* XDI can be used to transmit and/or store; X3 looks promising
* XRI = identifier - resolvable to an XDI endpoint
* XDI dictionary - like an XML schema
* XRI authority resolution server (open XRI)
* community iname registry
* inumber (this is how you handle reassignment)
* At what level will we register?
* How will we maintain this registry?
* How will other applications that write to LL handle XRI? Will they resolve to their own server?
*What about dupes?
**xri synonyms is the answer?
* Use iname registration for digital identity?
** might not need an icard selector on the iphone
** Simpler way?

===Action Items===
* Diagram high-level architecture
* Prep for discussing identity options next week
* Look into Sound Exchange reporting formats and PBcore formats

==2/26==
===Action Items===
* Make some design decisions to get us started with POC development
* Create a boxes and arrows diagram to help represent the data sets and functional entities and where they live
* Have a convo with berkman RE: servers and hosting the user data
* Identity + claimant - how best to handle user identity (focus on near-term)?
* XDI dictionary - designing what info is sent to log, registrants, etc.
* Revisit user functionality on wiki - what do we really need to do? What role should XRI/XDI (and existing OpenXRI code) do for us here?

==3/3==
===Notes on Identity Requirements===

When does identity happen? There are at least three contexts where we handle identity

#Capture data implicitly
##No registration
##Linked to phone
#Access to data provisioned through phone
#Sending listen activity to other data store providers instead of the default store

Perhaps there are others, but these three seem clear so far.

By way of thinking about identity, it is worth noting that there are four distinct functional aspects of identity. Something I call the Identity Quartet (blog post imminent!)

# For authentication, logging into services (username:jandrieu)
# For presentation, e.g., as handle on MySpace or Facebook or WOrld of Warcraft (name: Thor the Destroyer)
# Internally for database level handling of the attributes & privileges associated with a user (users.primaryKey=1023304)
# As a service endpoint, e.g., joe@andrieu.net

Flexible identity systems separate these four elements. Lazy ones combine, such as using my email address as my username. Or displaying my email address when I comment on a bulletin board system. A good system has distinct identifiers for each of these roles, and in fact, sophisticated ones could/should allow multiple different identifiers of the same functional class, for the same user, such as allowing an individual to have multiple characters on WoW, Iain Henderson calls this aspect of identity "personnas".

So, between the first set of contexts and the four functional types, we should be able to map out what we need for ListenLog.

-j
[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.cinsel-sohbet.com cinsel sohbet]

===Identity Workflow===
How identity in the LL app(s) might work. This is a proposed workflow based on my limited understanding of how identity systems work:

[[User:Khopper|Khopper]] 15:19, 10 March 2009 (UTC)

# ID the data: iPhone app by default will create a unique ID for each install (likely created by combining application ID + device ID) in order to appropriately key the log data to a unique instance (individual)
# Claim the data: In order to get access to this data beyond the phone, the individual must associate the existing unique ID in #1 with a more friendly and portable identity (i.e. user ID). This could be through a unique external or internal identification process. External might be something like OpenID, internal might be created and assigned through an integrated user registration process. This would have to happen on the phone.
# To complete the association, the user must authenticate (internally or externally)
# The LL datastore must associate the UniqueID in #1 with the userID in #2. Ideally, this will be obfuscated in some way to protect the identity of the user (is this possible?).
# To retrieve the data remotely (e.g. on a website that lets you browse your LL data), you must provide identity credentials and authenticate. This will locate the data and validate your access to it.
# To write to the data remotely through another application or device (e.g. Pandora), you must follow steps 1-4 above. This should be standardized as part of the LL specification. It is conceivable that there are use cases where data needs to be merged or split by application ID, by user ID, or by Unique ID.

PAM One night Stands

2009-12-03T12:53:35Z

Kelebek:

This VRM Workshop session covered the concept of the Personal Address Manager.

The scene setting points covered:

First Assumption - Privacy
Differences from long running relationships
- Mutual policy negotiation - pain-free
- Default policy bucket
- No identifier
Easy to produce end of relationship artifacts
Win-Win for customers and vendors
- Removing barriers to exit is attractive.
A use case was examined: Single Stop Online Shopping

With Address
With Personal Delivery Service (eg. relationship wth UPS, Fedex etc.)
With Vendor Delivery Service (eg. Vendors own delivery service that respects PAM token)
With Address from Personal Address Manager

Is the "With Address" scenario a Personal Address Manager (PAM) case? However the PAM might be the place where user relationship policies are stored. "With Address" was eliminated as a policy statement by vendors.

The "with Delivery Service" was selected to analyze.

'''Roles: '''
Shopper (S:)
Merchant (M:)

'''Assumption:''''''Bold text'''
Policy Assurance and Warranty

'''Scenario:'''
Step 1.

S: Shop at a compliant store

M: Offer VRM ("use VRM" button on the web page)

Step 2.

S: Click "Use VRM"

M: Endpoint Request

Step 3.

S: VRM Discovery End point - ie. PAM Address pointer

M: Push to provision

Step 4.

S: Provision vendor

S: Give Vendor token (with policy)

M: Policy agreement

M: Use token to get address

M: Use Address

M: Delete

M: Confirmation of End of use

Side notes:

Initiatives are underway to build a policy framework. (SAML and WS-Policy?)

This was a complex discussion to develop the scenario. Edits to refine this discussion can be made on the VRM Workshop Wiki in the Personal Address Manager page.

Also posted to [http://ekive.blogspot.com/2008/07/vrm-and-personal-address-manager.html EKIVE Blog]
[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.cinsel-sohbet.com cinsel sohbet]

Personal Data Stores

2009-12-03T12:52:59Z

Kelebek:

Drummond Reedâs â Personal Data Store
With Iain Henderson to address as well

On Board:

PDS:

What should be in it? (at a minimum) and (ideally)
Whatâs it for?

What is its essential characteristics/components

Where does it reside?

Where does it fit in the overall OSI Model and the VRM architecture

Why is it important?

When is it deployed?

How is it managed â what policies apply?

Does it have to be standard? Cabn there be many types?

What are the points of failure?

Drummond â the concept of PDS has been central to VRM

This is to talk about why? And to look specifically at the PDS

One starting point is âWhy is it importantâ/

Another is âwhat is essential?â

When we wrap up, we ask â On what points are we not in agreement?

Iain describes myDex though Slide show

Observation â Enterprise CRM architecture have multiple attributes but only store data for a year. If well designed, âimportant dataâ will be stored in Analytical System and data warehouse. Which holds the atomic level of data and stores it for the duration of a decisionmaking cycle.

Analytical systems tracks who bought what, where and why?==> to anticipate what to do next

First order concern is quality â meaning completeness, accuracy and several other attributesâ¦

Evidence is that âCRM Needs to be fixedâ â spending 200 bps is not enough to fulfill requirements. Okay at collecting info on customer. Not so good on tracking customer/product/outlet info in a usable fashion

Definition of âPersonal Data Store â (admittedly not a helpful term) A generic term to âsource, store, enhance and selectively disclose my personal informationâ

Needs to run on the same principles as the CRMâ¦ Systems will do the doingâ¦.

The personal data warehouse is the missing element.

In CRM the identity layer is at the top end
PDS resides on top. With the sources

Sees 3,500 attributes over 70 years (is what each individual has)

''(Thematic) Individuals have less tools, more attributes to control, fewer resources to monitor and track.''

Craig Burton â it is important and extensible as well.
A: So you need to identify the important attributes versos

To determine whatâs important, just identify what info you might need to get your life started again.

Next slide depicts Interactions and transactions with all sorts of businesses and govât entities. With the Identity Layer at the core.

*No CRM database can handle persona so you go about creating multiple ones to transact and interactx in the world.

Important â This is a logical design, not a physical designâ¦

It has been posited that Interactions are whatâs being monitored and that Transactions are a type of interaction.

Joe Andreiu â says we can get to the Model T version that does okay

Next slide â Current state of Who has what dataâ¦

Was My Data, Your data, Everybodyâs Data, âTheir Dataâ

Everybodyâs data = public domain â all sorts of data thatâs avaialbe.
âTheir Data (or parasitic tailings) â what Experian, Acxiom etc, collect about you

Your dat â include a vendors products /services, policies, pricesâ¦
And guesses regarding view of a customers preferences, requirementsâ¦

Our Data â identifiers, clams,/Assertions and transactionsâ¦

MY DATA â is stuff known only to meâ¦ Circumstances, Assets, Liabilities, preferencesâ¦

There are also back channels which are interactions between the parasites, vendors, and the publicly available stores.

At Liberty Alliance they have been discussing âVolunteered Informationâ

Finally, Thereâs the Target State

In 10 years time 80 percent of customer management prcesses will startywith âMYDATAâ (me)

So the customer will be in more control and overt interactions will be between the vendor

Toxic will be bad for both vendors and customers â they destroy trust.

''Drummond â 3 times Iâve heard that âThe customer is the point of integrationâ (which originated from Joe Andrieu)''

âCustomer as Point of Integrationâ

Joe says âAnalysis and Insightâ revolved around the vendor dataâ¦ It is the source of Googleâs competitive advantage â¦

Craig Burton â but Googleâs source of distrust was doing personal data storage for Google to tag and index

PDS has âroots in two placesâ

1) Doc Searls â personal experience with the medical treatment across several care givers and each introduced errors in their systems so that they could not reconcile or synchronizeâ¦ The conclusion is that it would have been more efficient and less dangerous if Doc had been the single repository providing to access to the data on an as needed basis.

2) The other side is âStymergyâ which is the general term for how ants find the shortest path to food. It is also the answer to a distribution problem for multiple trucks between warehouses. They send out ants randomly, the one that comes back first, his trail is doubled.

Balance between exploration and exploitation. They mark their environment. Joe articulates that the data should be stored centrally and when multiple companies or individuals want access, they should not seek out things from one another. They should get it from the individualâs data store

Stuart- Why wouldnât you just ask Amazon.com or Google to do a better job of making your information accessible to other apps. So I can assemble it at my command from the multiple sources.

Joeâs answer â youâre asking about data portability.
Iain says (itâs because youâd be operating under their terms and conditions)

Joe says it is because personal data store is not just âthe dataâ it is about setting up mechanisms for permissioning information in, out based behind your own front end (called identity)

And youâre going to have all sorts of front ends or âService Specificationsâ (Liberty calls them Service Interface Specification)

Status updates
Addresses
Music ratings
Search Activities
Personal RFPs
Personal Healthcare records
SMTP/POP

And itâs all under your control

Sop the question is whether the hub is about authentication (identity layer)
And permissioning

*** so there is a multi-billion battle raging over control of permissioning for status updates.

Iain â youâre still missing the link between doing data and planning data.

Doc sees the user as the point of integration and also origination.

Else â a problem solving thing which gets brought up.

That is the ossified way that existing systems work
In medical system, fârinstanceâ¦ there is a kiretsu of equipment providers, suppliers etc where it is hard to get data from individuals or companies. Incompatibility between media, age of PC, etc.

You are going to have this architecture work better in some cases rather than others.

Iain, where thereâs failure in ERP or CRM itâs because the system is trying to do too much and gets clogged up.

So you need to make the distinction between getting stuff done and when you have to do long-term planning.

Per Drummond â donât you end up answering the question by establishing the framework for these the service interfaces service provier (Facebook, Myspace, Plaxo)â¦. And those service providers would manage one or more of the service specification intervfaces.

Joe is saying that it is easier to solve and optimize the âshortest pathâ solution for specific tasks then to define the personal data store that does it all.

Iain is saying that it will have to do the analytics earlier and constantly.

Architecturally you sidestep it by providing a service thatâs operational and do it in a way that is consistent with doing the analytical and do it in a way thatâs consistent with identity based permissions.

So you donât have to do them all if you can solve one of them seamlessly.

Drummond will explain what XDI is all about as a protocol:

The idea of getting all sorts of schemas to talk to one another is a real probalem. HtML canât. XML cannot.

About trusted Data sharing. And itâs about permission

Craig says that XDI is not a protocol. It is a language structure

He wants to know âwhat does it resolve toâ if I write a command and it gets abstracted to something that then resolves to the data and its location. So if you want to share some of your data that resides elsewhere, like in multiple banksâ¦

''The Data doesnât have to live at the hubâ¦ But control does''

Craig â it resolves around a URL and then I can react to it based on a structured card

Card
Rule Set
Data set

Resolved to a URL and it gives permission to access to where that data can be found. And enable data set mashup.

E.g. iphone with a GPS Google Map moment. âTell me where the lone palms hotel is in relationship to meâ tell me where I am and where I go.

Itâs mashup that needs to include all that data.

CyberCrack!

Ad active rules to operate on your data store, and the mashup of all the services

I just want to get this group to define the architecture to put it into the hands of the developer community./

E.g. Amazon.comâs EC2 setting up all sort of things (like 30 years of census data)

Q: When you say ârule setsâ do you just mean permissions?

A: (using the MyDex example - ) as a proof of concept, no browser is required. Any program and any entity can subscribe to the other info an dlocation and all or part be âin the cloudâ

Switchbook has all the info distilled on the hard drive, there is a copy in the cloud for back up purposes. It doesnât have to be in the cloud. And thereâs code in the client to handle I/O

When you get to rulesâ¦ You put functionality in the cloud that handles services and can find them in the cloud.

Customer write the rules.

Stuartâ¦ Example is embedding a twitpics or a URL in a twitâ¦ Iâm publishing something that can then be seen by anyone or everyone. Or how do I add a âsmart URLâ to a tweet so that I can publish to everyone, but the URL has a set of criteria behind it or around it that is controlled by the higher order infrastructure.

Can use a medium like Twitter to infect the world with XDI and XRI

If all or portions of your data are addressable, it can be made accessible to the rest of the world. If you make it abstract. If itâs inside the âIdentity Layerâ it can be under the control of the user. One of the key purposes of the next step, which is XDIâ¦ The same format says that I can store the âpermissionsâ (sometimes called ârulesâ) so that I can access the Link contract. So that the read/write instructions can attached to another set of rules to do something like letting the gas company

Go To Wiki.kynetics.com (it explains the rules that Phil Wendly has developed)

Joe says that Grease Monkey does it as well. But Craig Burton says that kineticsâ¦ is what we should be interested in.

Joe says HTML 5 is being deployed now in browsers.

Craig: I would strongly recommend that we do this in a way that is somewhere between Wiki-based and Selecter-based that is Strong foundation for VRM.

Joe, part of this is about deploymentâ¦ âI hate JaSon because it is inherently insecureâ but they have ways to do secure parsing of Jasonâ¦ But it was adopted because it provided trivially easy way to do it insecurely and native to JAVAscript.

We want to play friendly with them.

Question, gas company needs employment data about me. 1 to 1 federation on their own terms. VRM way. Passport agency acts as a node and permissions allows Gas company to get info from passport agency.

Data liquidity is what itâs all about.

Read it as âpermissionedâ or âunpermissionedâ and the reason that there is so much unpermissioned is because âthereâs no technology in useâ to support permissioned. Which is an argument for Portable Permissioning.

Joe-looking at Switchbook in this context is that your identity is stringly around what you give permission for.

Switchbook defines you by your âsearch mapâ itâs a file that is orthogonal to all your other identifiers. Itâs Switchbox has a âSearchMapâ document at its core. It is the context where your current browsing shows where youâve been and what youâve done and all that.

Idea is that we shouldnât get hung up on the protocol right now. Just define how entities interact and figure out the mesh points.

In the IDWSF model, how you talk to the gas company is permissions based. They may send you an email or something and you set it up with your IDWSF model.

Drummond: Now we talk about our questions.

1) Why is it important?

Initial â The thing that will put the individual back in control of personal information. Meaning the information that is important to the person.

Itâs the store that you personally have control of, it could be anything.

Will allow us to be more promiscuous with our data because we know it will be stored in a trusted way.

It is a context for control.

Because if you abuse it, I know your pheromone trail?

Benefit is that it will improve my quality life, based on my decisions.

Itâs important because it is valuable? It can be bartered>

It is economically transformational>

Jim â Like credit cards, this lowered the friction and reduces guesswork and waste from the vendor side. Which increases value.

Best case you provide the best possible outcome for both parties.

It is more efficiently economically. (the economy will operate more efficiently)

It enables what weâre calling the fourth party services (what VRM is promising).

Markâs point â Itâs a way to organize VRM.

What weâre talking about as the personal data store is to create a better marketplace by providing the way the individuals are regarded by buyers/sellers/governments.

It helps people organize their lives. It enhances efficiency and productivity.

Framework for new use conventions that we donât foresee right now (think of browsingâ¦ or logging onto the bank)

Itâs implementable

Now letâs look to points of failure:

Adriana would say that there are point-to-point identity free interactions that donât require this.

Aside â Kim Cameron says that âIdentityâ is not an identifier. It is just a set of claims that require context. You can have a claimless set of claims in a container.

It is about 4 different identifiers:

Authentication
Presentation
Reference ID (how to be reached email address)
Internal ID

This is your identity online

Are there VRM-y things that donât have a personal data store as part of itâ¦ The answer is noâ¦

You need a place for your stuffâ¦

Q: Where does it have to resideâ¦ It could be anywhere as long as itâs accessible by the applications

Q: Isnât really a permission and control hub? Answer is ânoâ it is still about the data with rules established as to the permission and conditions under which

Weâve gone in circles around what is a relationship manager as opposed to a relation service.

Iain says, itâs all about how you operate around the dataâ¦ Need to clarify how to source, store, enhance and selectively disclose data.

Drummond â the other place the Identity comes in is that the idea of the role of the user in terms of control is akin to the control they have over their bank account. But the bank has authority.

The relationship someone has with Equifax, for instance, is Massively Passively

Another parallel is like the spam filter, where we have passive benefit but virtually no control.

Jim Morris asked what this would be like if it were Communist China and there was an argument for centralized â¦ Drummond, from the point of view of market (as opposed to moral), this is the mechanism for giving user control.

This is about distributed planning.

Has anyone looked at giving control of the personal ID store to a centralized trusted entityâ¦

Bullets for tomorrow:

Privacy:
*IP addresses are they trackedâ¦
*Iâm worried about Google tracking activity

User Experience
*complex
*could create opportunity for errors
*Mashing on toes

Conformance and compliance
(if I share data, how will I know if people abide)
a
Reputational authority (how do I know you are who you say you are)

Service dependability
Business dependability

Portability?
Inadequate choice of SPs

Data Breach and fear of data breach (Honey Pot)
[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.cinsel-sohbet.com cinsel sohbet]

Process

2009-12-03T12:51:40Z

Kelebek: /* 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.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.cinsel-sohbet.com cinsel sohbet]

Questions raised

2009-12-03T12:50:58Z

Kelebek:

* 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.cinsel-sohbet.com cinsel sohbet]

Taxonomy issues

2009-12-03T12:50:33Z

Kelebek:

Very much a stub...sorry for the current "stream of consciousness" character of this -- will be cleaning it all up as soon as possible.

There's a lot of work here. RFPs should allow for widely varying degrees of specificity. Ideally, a seeker should be able to create an RFP for:
<ul><li>a blackberry 7130c</li>
<li>a cell phone with bluetooth and EDGE support</li>
<li>a cell phone costing less than $250</li>
<li>a cell phone</li></ul>
Even before considering the different attributes required by different types of requests (travel planning vs. product purchase, for example) it's clear that creating a workable microformat for RFPs will be a fascinating (and frustrating) process. It's worth noting, though, that work in this area pays off in many ways.

Desirable: RFP attribute "package," optional, linking multiple RFPs. Indicator to vendors that the seeker is interested in the entire package (implicitly asserting that offers that cover the entire package are preferable/required? Or explicit flag?) -- plane ticket RFP, car rental RFP, hotel RFP, linked by package ID. Five different books, linked by package ID. Possibly worthwhile on both ends: seeker only wants A if they can also get B, vendor can tailor offer/discounts based on total package.

Note to self: Marti's "fulfillment" RFP attribute is an elegant addition. Does seem to suggest that authoritative, verifiable identity for vendors goes from "extremely useful" to "non-negotiable," though. Note also that it makes authoritative seeker identity even more significant: if seekers provide feedback that (is | may be) used to establish vendor reputation as an evaluation factor, there's significant incentive to astroturf.

Suggests the desirability of a parallel reputation system that covers both vendors and seekers. Consider how long an entity has had a public presence, RFP/feedback patterns. Unfortunately seems to also suggest that there could be an actual need for some third-part(y|ies), handling the seeker/vendor DB stuff outlined in the VRM diagram: in addition to pointers to requests/offers, the archive retains history. In this case I guess one would want as many competing versions as possible, so that clients can poll multiple and use their own systems to resolve differing data.
[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.cinsel-sohbet.com cinsel sohbet]

The Matrix (Blue Pill)

2009-12-03T12:50:01Z

Kelebek:

'''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.cinsel-sohbet.com cinsel sohbet]

Help:Contents

2009-12-03T12:47:15Z

Kelebek: /* Can I be Automatically Alerted Through Email? */

It's easy to start editing pages on this wiki! It is the job of every registered user to try and improve these pages. Wikis work best when everyone is involved and adding, editing, reworking, and checking the contents.

==== How Do I Start? ====
Log in (you must have a login to edit). Click on the "edit" tab at the top of any page. You will then begin editing the page you are on. There is a helpful [[Help:Cheatsheet|Cheatsheet]] to learn the basics of formatting your changes.

==== Can I Practice? ====
You bet. Try out editing on the [[Project_VRM:Sandbox|Sandbox]] Page. Anything goes there.

==== When Should I Jump In? ====
A Wiki benefits from the "[http://en.wikipedia.org/wiki/Wikipedia:Be_bold_in_updating_pages Be bold]" philosophy. If you see something that can be improved, do not hesitate to do it yourself. Improvements come from the iterative additions and edits of all of us. Pages keep a revision history, so nothing can't be undone (click on the "history" tab at the top of the page).

==== What Happens When There is Disagreement? ====
If someone disagrees with you, or you with them, then good! We've inspired involvement, and through edits and discussion on the [[Help_Talk:Contents|Talk Page]], consensus can be reached (each wiki page has its own respective talk page). Wikis work great for emerging concepts and themes like VRM that will benefit from exploration and the evolution of mutual agreement. Paradoxically, edits that introduce diversions from commonly-held understanding is what helps best build and spread editorial consensus.

==== When Should We Use the Talk Page? ====
Every wiki page has a talk page. Click on the "discussion" tab at the top of the page to get there. Whenever you have a question that's holding you back from an edit or when conversation seems more appropriate than document-building. Please sign your comments on the talk page with four tildes ("<nowiki>~~~~</nowiki>") which will automatically drop in your username and time stamp.

==== How Do I Keep Track of What's Going On? ====
There is a special page called "[[Special:Recentchanges|Recent Changes]]" that keeps a running list of all recent changes to the wiki. Think of this like a news feed of what's going on. Check out what other people are doing. Piggyback on their changes.

You can also watch pages by clicking on the "watch" tab at the top of a page. This adds the page to your personal [[Special:Watchlist|Watchlist]]. You can visit this page any time to see what changes have been made, by whom, and when. For example, you can add the [[VRM vision]] page to your watchlist by clicking [http://cyber.law.harvard.edu/projectvrm/watch/VRM_vision here]. There are all sorts of additional [[Special:Specialpages|Special Pages]] that are worth checking out.

==== Can I be Automatically Alerted Through Email? ====
You can receive email alerts when changes happen to watched pages by adjusting your [[Special:Preferences|Preferences]] 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://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.cinsel-sohbet.com cinsel sohbet]

Interesting Links

2009-12-03T12:46:49Z

Kelebek:

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

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

Events

2009-12-03T12:46:27Z

Kelebek: /* Past Events */

==Future Events==

* [http://cyber.law.harvard.edu/projectvrm/VRM_East_Coast_Workshop_2009 VRM East Coast Workshop 2009], 12-13 October 2009 at Harvard Law School, Cambridge, MA.
* [http://cyber.law.harvard.edu/projectvrm/VRooM_Leadership_Workshop November 2009 Leadership Workshop], Location TBA
* [http://www.internetidentityworkshop.com/ Internet Identity Workshop 2009 (IIWIX, IIW)], 3-5 November 2009 at the Computer History Museum in Mountain View, CA.

==Past Events==

[[VRM West Coast Workshop 2009]]

[[VRMworkshop]] at Harvard Law School, July 2008

[[VRM Hacker Session]] November 9th 2007 London

[http://www.supernova2006.com/ Supernova] 20-22 June, 2007 San Francisco

[http://conferences.oreillynet.com/os2007/ OSCon] 23-27 July, Portland

[http://conference.digitalidworld.com/2007/ Digital ID World (DIDW)] 24-26 September 2007, San Francisco

[http://www.windley.com/events/iiw2007a/announcement Internet Identity Workshop (IIW)] May 14-15, 2007, Mountain View, CA

[https://events.projectliberty.org/details.php?id=11 Identity Open Space (IOS)], 26-27 April, 2007 Brussels

[[Notes from VRM & Public Media Workshop]] at the Berkman Center, April 4, 2007
* Includes follow-up brainstorming ideas from April 6, 2007

[http://cyber.law.harvard.edu/identity/Mobile_Identity_Workshop Mobile Identity Workshop], January 26, 2007

[[Notes from VRM Meeting]], January 25, 2007

[[Notes from Internet Identity Workshop 2006b]], December 4-6, 2006
[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.cinsel-sohbet.com cinsel sohbet]

Project VRM:Community Portal

2009-12-03T12:45:50Z

Kelebek: /* 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.cinsel-sohbet.com cinsel sohbet]

Main Page

2009-12-03T12:45:20Z

Kelebek: /* VRM Lexicon */

== 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 sÃ¶zlÃ¼k]]

* [Http: / / wiki.auds.org / index.php / / wiki / anlaÅmasÄ± AUDS] (kullanÄ±cÄ± iÅlerinde hizmet ... adÄ±nÄ± hala sÃ¼rÃ¼cÃ¼lÃ¼) AnlaÅmasÄ± - bir sÃ¶zlÃ¼k iÃ§erir
[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.cinsel-sohbet.com cinsel sohbet][http://www.hiphopalemi.net sohbet]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr sohbet gay]
[http://www.cinsel-sohbet.com cinsel sohbet]

== 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!

Main Page

2009-12-03T12:44:59Z

Kelebek: /* VRM Lexicon */

== 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 sÃ¶zlÃ¼k]]

* [Http: / / wiki.auds.org / index.php / / wiki / anlaÅmasÄ± AUDS] (kullanÄ±cÄ± iÅlerinde hizmet ... adÄ±nÄ± hala sÃ¼rÃ¼cÃ¼lÃ¼) AnlaÅmasÄ± - bir sÃ¶zlÃ¼k iÃ§erir
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikisi]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikisi]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek sohbet]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org sohbet sohbet]
[http://www.siberchat.net sohbet]
[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 sohbet]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr sohbet gay]
[http://www.cinsel-sohbet.com cinsel sohbet]

== 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!