Project VRM - User contributions [en]

The Matrix (Blue Pill)

2009-12-01T12:31:36Z

Hiphopalemi:

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

Taxonomy issues

2009-12-01T12:29:10Z

Hiphopalemi:

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]

Information flow

2009-12-01T12:24:45Z

Hiphopalemi:

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]

Firefox plugin

2009-12-01T12:24:09Z

Hiphopalemi: /* Working Notes */

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

REF: attentiontrust.org/root.net
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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-01T12:20:06Z

Hiphopalemi: /* 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-01T12:18:57Z

Hiphopalemi:

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]

ListenLog Meeting Notes

2009-12-01T12:17:33Z

Hiphopalemi: /* Identity Workflow */

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

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

Notes from VRM

2009-12-01T12:16:34Z

Hiphopalemi:

''Notes from the notetaker: There was so much covered and so much discussed on this day - I did not attempt to scribe the event. Alas, below are merely my own self-directed thoughts that emerged. Please add your own if you were present.'' -[http://cyber.law.harvard.edu/projectvrm/?title=User:Khopper Keith Hopper]

'''Objective:'''

How can the public broadcasting audience member take greater control of their relationship with public media? (â¦and as the audience becomes the former audience, how does this relationship change?)

'''Background Thoughts:'''

* Relationship does not equal transaction â in envisioning a vendor relationship tool, we need to think beyond just financial transactions (e.g. donation software)
* Incremental, internal change is not what weâre looking for here. Instead, letâs identify new ideas for experimentation on the fringes of the industry. These ideas should allow individuals to flex their creative consumer muscles in this new participatory landscape. Existing public media, broadcasters, shows, and distributors will serve as the relationships, platform, and ethos to leverage
* Letâs not attempt to address or work inside the existing public broadcasting infrastructure â a better strategy might be to 'end-run' a solution that imagines new ideas from a variety of committed individuals and asks for permission from the stations, shows, and distributors to explore these ideas. If the ideas get traction, the existing players can get involved to their level of comfort and in the ways they see valuable
* There seems to be an overlap between what's going on in participatory culture and what exists in public broadcasting. The potential exists to tap a whole new generation of creative consumers who will 'discover' public broadcasting and want to adopt it for its potential as a non-commercial, open network designed explicitly to serve the public. Can we stimulate this adoption?
[[Image:public-radio-participation.jpg]]

* Can we reduce the friction of listener giving? Perhaps provide a capacity to donate directly to shows/programs?
* Project VRM shouldnât code software, but rather lay out ideas, standards, and support for others who can
* What's the device that will eventually replace the radio? How will this impact public radio and the relationship with the (former) listeners?
* What does the long tail of public media look like?
** Leverages democratized tools of production and redistributable media
** Leverages the cheap, fast, and widespread distribution of end-to-end environments and the benefits of aggregation
** Uses filter technology to drive demand down the tail
* If we were to reinvent public radio in an end-to-end environment like the internet, what would it look like? How would it compare to what exists, and what important differences might emerge? Can we fill those gaps?

'''Ideas for action:'''

* Make public radio the 'test project' for a vendor relationship management tool
* Provide a capacity for end-users to publish their iTunes playlists of public radio podcasts â provide a tool or environment that aggregates and features listener playlists
* Is there stuff we can do with RDS (or HD, PAD, etc.), such as publish texting codes for listeners to use in providing feedback or funding linked to specific stations, programs, and times?
* Use the existing NPR podcast directory as a platform for additional capability â specifically, experimentation with an online donation linked to podcasts
* Get a conversation or survey going with the end-users, mashup folks, or those formally known as the audience to get a better idea of needs/desires and to brainstorm ideas for creative production/control over public media
** As a creative consumer, what is it that I want to do with public media? What are my 'lego blocks'?
* Investigate a new model for a public radio station ''not'' centered on broadcast
** Embrace end-user control over programming, funding, content creation, and overall relationship
** Incorporate participatory programming direction (e.g. guest programmers, vote programs into timeslots, etc.)
** Incorporate online-only shows; act as test market for new shows
** Re-invent the traditional show model (ala Radio Open Source) to be truly conversational and participatory (What might this look like?)
** Use financial models like fundable.org to collect threshold capital to fund desired programming
** Use a small terrestrial station to carry stream and get CPB certification and permit audio use in podcasts (whatâs the secret, here?)
* Build a configurable and redistributable âuser-as-public-radio-stationâ model, integrating various streams and podcasts from around the web into a cohesive and personalized internet public radio station (e.g. KPR = Keith Public Radio)
[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]

PAM One night Stands

2009-12-01T12:15:46Z

Hiphopalemi:

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-01T12:14:56Z

Hiphopalemi:

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]

Questions raised

2009-12-01T12:12:41Z

Hiphopalemi:

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

User Driven Services

2009-12-01T12:11:43Z

Hiphopalemi:

User Driven Services â Joe Andrieu

Introduced a series of blog posts for user driven services
See blog: [http://blog.joeandrieu.com/]

Issues that arose that led to the idea of user driven services to tackle the general issues of interactions between individuals and a system

See blog for definitions

But in general â a System is something built for a particular goal

User is an individual â not a computer an actual individual

Services is an interaction that creates value

User driven service definition

âServices that maximize value creation by maximizing user control and authority.â

There are a spectrum of possibilities

And there is a continuum of âuser driven servicesâ

You could argue that Google, for instance, is very user drivenâ¦ on a first order level

But they donât conform to many of the characteristics

# impulse form the User
# Control
# Transparcncy
# Data portability
# Service endpoint portability
# Self hosting
# User generativity
# Improvability
# Self-managed identity
# Duty of Care

Question - what do you see as the value of adding all these criteria over the relatively random stuff thatâs going on

Answer from Joe â this is the basis for many conversations. And the conversation regarding VRM was always future. User-driven gives a way to ground it in specific instancesâ¦ like whether a mobile app to tie into a company internet, he wanted to make it more user-driven.

Weâre part of a huge transformation of our society, started with The Enlightenmentâ¦ just figuring out what it means on the internet

Doc: the problem comes up even since Ben Franklinâ¦

Added it includes time travelâ¦ The pace of correspondence is so much faster

Added 4th party discussion makes it more easy to define crisply and clearly

Now we need to define what âfouth party isâ because âvrm is not about user-driven, itâs about how the end-statement changes everything.â Itâs transformational if you can address the end-state

User-driven has instances. Whereas Fourth-party is a category of participant or service provider (not always acting on behalf of the user)

Google figures that they would win in the âopenâ game with their semantic labeling and they expose their APIs to let them

Joe â for Switchbook, we think our algorithms are better.

Issue raised â âUser driven works for some ?? and not othersâ¦

Doc says â the characteristics define a number of bullets that dictate how you let people in without locking them in and locking them down.

Joe â like Umar Haque (phonetic)â¦

He has some this and shares the core tenet that, weâre not doing a moral argument. Weâre coming from the idea that thereâs money left on the table because of faster response time and less waste.

Itâs economically stupid to do it the old way.

Service enpoint portability â you can change service provider without anyting falling apart

Self-hosting = you control the dagt

User-generative = means that the user should be able to add value

Improvability is the âAâ in NEAâ¦

Self managed ID â to be dealt with

Duty of care

Docâs question â who does this apply to? Different users may attach more or less importance to each one

But the service provider has to do them all and be responsive to all requirements and maintain sustainable advantageâ¦ But not locking people in.

1) reprise: Impulse of user - this is not about data miningâ¦ it is about the system responding to a gesture of intent.

The internet is really good at this.

Q: is this really targeting individualsâ¦ The service needs to be at the architectural level and this is about an individual interacting with a service (that could be a 4th party interacting with a 2nd party on behalf of the first party)

E.g. that will come up is a personal RFPâ¦ but it might benefit from group interaction because it could be group buying

e.g. might be eBay because it aggregates a whole lot of sellers.

Alan Mitchell â says that your describing a cell that interacts with a larger organismâ¦

A: This is the pattern of behaviors that make the cell survivable for the organism to live. Itâs that system level that Iâm trying to describe

Doc: a distinction is that we start with the individual (cell) how do we give it the right nutrients to support VRM, not just consumer â like Consumer Reports. Thatâs not are starting point.

Joe: itâs part of our Jui Jitsuâ¦ where we shift the weight.

Don Marti talks about the upside down buyers guide â putting the buyers in control

2) control â Users control the servicesâ¦ E.g. can

Control is not a great word â but the gang put that down. Users should have control

Also comment that service provider should respect the directives of the user.

Issue is whether this expects too much of the user. You could also grant it to tohers.

Doc â we are pouring all sort of responsibility on the usersâ¦ BUT SO ARE VENDORS â with self-service and all. But then again, we can make control as simple as possible.

The issue is whether there is a âstandard default arrangementâ (policies) which is how the things are all the time.

The fact is that if people donât voteâ¦ Theyâre happy.

Itâs something you tackle at the policy levelâ¦ it is distributable, but fluid. Bo said âepisodicâ you care to control what you care about it.

Next up (not discussed ) is âterms of serviceâ that VRM assertsâ¦

â¨Transparency is straightforward â people let you know what they want you to knowâ¦ Alain asked does it apply to all the discounts and incentives etcâ¦

A: this is about increasing value by maximizing control and authority

Q2: this is a principle of design â so it has to do with how the service is designed.

A: well the system does require design..

Q3- therefore the user is not in control and itâs not transparent.

A: the people who design the system define reality. Because weâre using Web technology and thatâs already defvined. But the term âtransparencyâ has a waterâs edge.

But the question is, âWhere do you draw the line?â like motives, margins and incentives are a big part of transparency.

Allainâs answer is that âfor a fourth party serviceâ transpareny has to include motives and incentives.

Is transparency âfull disclosureâ

A: there are five categories of transparencyâ¦

This is a new dimension of the Caveat Emptor akin to the FDA having all the

Transparency is not a âdictateâ it is something that user driven services will need to be survivableâ¦ and it means clear understanding of policy.

Alain â weâre getting to the heart of the organizational world where the vendor needs to assert what it does not intend to be transparent.

Darius â in the real world, the service provider will publish service agreements and people will operate under it and it will either work or it wonât.

It is not the primary place where people make a decision.

Q: is there a registry where people could log on and check

Bill Washburn â there should be a dialogue around a quantitative approach to transparency to a qualitative view regarding âwhat should be the major areas of concern.â

So this will be rescheduled to tomorrow.

Suggestion is to talk about âdefining 4th party services in a way that would have a ârulebookâ with criteria that should be conformed toâ

Joe was wondering whether you could apply these criteria to Web based activityâ¦ like SMTP or Web Hosting.
[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]

VRM Marketing

2009-12-01T12:10:58Z

Hiphopalemi:

Scumbag Marketers-

Dean lays down the law :

We need enterprise buy in for this to work. (meaning large companies, brick n mortar and online and have CRM)

Don has brought up there there are a lot of companies that might want to sell what looks like CRM and it might not be with the best intent.

Itâs all about money and they may say âwhatâs in it for me?â

We have a few candidates in mind â¦ we know the right person there. Itâs the highest of C persons because it has to come from the top or else weâre fighting our way through all the little fiefdomsâ¦ Because they have to be told

Pushback â Chris: look at Frank Eliason at ComcastCares who did grassroots, Twitterbased end-run.

Deb-Based on experience with P&G going to the top and pushing down even with smart big companies could be hard. So higher ups and infulentials

* Weâve agreed on Influentials and horizontal

Phil Wolff â another challenge, might be to understand the systems they are using and pull through with an existing vendors.

Sean, VRM isnât going to replace CRMâ¦ Itâs not a replacementâ¦ Think about Oracle/Sun for example, they may be incorporating VRM into part of their solution.

* So we have to take a multi-pronged approach
* We have to target each and speak in their language.

Gam â At sephora, they started at the top and were pushed progressively down to the group that was doing Facebook and they were only interested in their âthe Fan siteâ so then it got totally diffused and sent out.

Sean says weâre tight but we still donât talk in a way that has appeal horizontally among non-geeks

Doc says that there are a few people who get it the first time out. And now we (this group) needs to get out their with a set of stories that highlights the curb appeal

Weâve played down the marketing VRM until some code has been written and there are some examples out there.

Weâve been watching the best people rising and the people who really get it doing some cool stuff.

Now within 6mo to a year. Weâll have PublicRadio. Weâll have Gamâs thing andtcetera. And Debâs gonna have the one pager.

Debâs observation â there are all sorts of consultants saying âyou donât bet itâ and evangelizing around Searchi optimization and blogging.

Deb has community managers at CPG, that means they get that. The future of e-commerce is the next step and âthis is it.â

Dean is channeling Allan â he says that weâre making a statement and getting internal buy in. The mission now should be to get buy in from them and get them to pay something like $10K.

Deb says, they need a real story.

Chris says â We have two products nowâ¦ One was VRMâ¦ The next one is a very distinct product which is âa seat at the table to influence creation of VRMâ

It is Access, privilege and Influence and it should have a price attached to it.

Don â there is definitely value to them. We just have to bring it to their attention.

Chris is saying once again that it has value to them

There will be more of a story when the ClueTrain Manifesto update comes out it will clarify the connection.

Conceptual DNA exists.

Doc says also â by bureaucratizing what we do, some good things happened, but thereâs some organization issues.

* Joyce, Judi, Dean and Renee are going to blend things back together. Renee Lloyd has the best way to articulate this and get the organization.

Dean: Big Company buy in will get companies getting big and small companies interested.

Doc has confidence that the major CRM companies are going to buy into this. Doc is planning to have a combined CRM/VRM session and CRM will sponsor, attend and bring customers.

Q: is there going to be a certification process. And The 4th party concept will be baked in. And certification will protect the concept and clarify. There will be a VRM seal of approval.

Per Dean: VRM as a brand is not sexyâ¦ And itâs not our consumer brand.
Doc says that like the word ATM, people use them but necessarily use the term

Seanâs observation â the name isnât as important as the fact that we have more clay on the piece and, besides, the naming folks at McCann or whatever will âmake a hashâ of any name we might come from

Philâs idea â there are two sides that will make this work. Weâve been focusing on the plumbing sideâ¦ And not the moms and pops or the people that are using it.

Sean is saying that there are stories to be told
Deb says that we need the idiot CNN reporter can say the narrative

Jeff Schwartzâ¦ Agreed that itâs not ready,

Chris Anderson and Tim OâReilley are not sold on it. But some others might be.

Sean: need the manifesto, need the North Star,

Paul: thereâs not one user story, There are many orthogonal ones.

Deb: What we should do is have Sean, Doc or Dean give their elevator pitch.

And Whatâs your story to Mom.

Dean â Big go hears: These days we know that people have more communications platforms where you hear them speak. They are telling you what you had used as predictive, you can now get directly from them.

We enable this data to come in and we make it so you can use info from both sides.

Deb: weâve heard that this is social media stuff is happening. Does it help me sell more stuff.

Paul â said that thereâs a fourth party story for the shopper.

Doc: starts with a question:

Which do you hate more, loyalty cards or bad customer service? And dependeing on which one you go down that path.

Then the story is that the companies are already outsourcing their customer service to you. This is your chance to take better control of that.

Jeff asks: why would a vendor want you to give control to the customers?

Doc: Ask what do you hate most about your business
A: Guessworkâ¦ You can get rid of the waste that occurs because of guess work

* Weâre equipping pull as VRM turns push into pull.

Thereâs so much buzz about listening to your customer and enterprise âgets thatâ but theyâre using market research data, customer research, and market effectiveness studies.

We need to use âthe equippingâ wordâ¦ Ergo not the monitoring stuff

Don â the difference between marketing salesâ¦ Tell the marketing guy that VRM shortens the sales cycles, increases loyalty, costs lessâ¦

Sales guy â¦ you tell them that they gotta have it.

Jeff Schwartz â says the good thing is to say things

Cover Fear of loss and Desire for gain

Sean says â this levels the playing field between big companies and you. You can interact with them eye-to-eye, peer-to-peer. No more loyalty cards. Iâm doing it to GMâ¦

Leveling the playing field is the big deal.

Philâs asking whether we have a shopping list regarding the talent we need

Sean says that we need a grassroots movement sort of structure.
[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]

VRM lexicon

2009-12-01T12:10:17Z

Hiphopalemi: /* Other sources */

== Lexicon ==

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

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

== Other sources ==

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

VRM Workshop

2009-12-01T12:09:32Z

Hiphopalemi: 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]

Website planning

2009-12-01T12:08:56Z

Hiphopalemi: /* Action Items */

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

==Users==
Categories & Examples

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

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

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

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

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

==Open Questions==
==Random Thoughts==
http://www.apache.org is a good example
==Action Items==
Joe: Top-level site-map structure thingy proposal. By next wednesday. (Confer with Chris before then.)
[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]

==Draft layout==
[[Image:VRM_Home_Page.gif]]

The Mine! Project

2009-12-01T12:08:14Z

Hiphopalemi:

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

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

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

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

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

For more, go to [[http://themineproject.org/ the project site].
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Relbutton Scenarios

2009-12-01T12:07:36Z

Hiphopalemi: /* Call Notes */

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

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

[[Image:Icon4.gif]]

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

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

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

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

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

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

1. Open to relating:

[[Image:Relbutton_sm.jpg]]

2. Relating already:

[[Image:Relbutton_sm_closed.jpg]]

3. Looking to buy something:

[[Image:Relbutton_sm_left.jpg]]

4. Looking to sell something:

[[Image:Relbutton_sm_right.jpg]]

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

[[Image:Relbutton_sm_right.jpg]]

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

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

[[Image:Relbutton_sm_closed.jpg]]

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

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

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

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

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

Britt Blaser produced this graphical explanation of the relbutton:

[[Image:Relbutton.gif]]

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

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

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

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

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

==Scenarios==

===Media in general===

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

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

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

Subsequent use cases include

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

===The MID Radio===

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

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

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

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

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

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

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

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

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

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

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

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

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

== Call Notes ==
[http://cyber.law.harvard.edu/projectvrm/August_19_2008_Conference_Call Relbutton Call notes, August 19, 2008]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Read Log

2009-12-01T12:06:50Z

Hiphopalemi:

A Read Log is like a [[Listen Log]], but for readers of digital text.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Prototyping VRM Mobile Social, iPhone

2009-12-01T12:06:28Z

Hiphopalemi:

Stuart- Prototyping a mobile VRM that leverages Social Network fabric

iPhone is a good conduit

Phone
SMS
Email
3.0 notification
Bluetooth

Stuart says that we have all these ways to contact people

iPhone adds location

Adds time

Presence â and what Iâm doing

Things that recognize that âstate has changedâ

Relationships provide context regarding âWho are you?â

The questions revolve around access control

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

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

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

Rules for Pre-call Information

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

The originator really has no control over what information is provided

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

Using Google Voice you can treat each caller differently â¦

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

Ribbit could be a platform for all of these services

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

Comment â originator may want to indicate a different originating phone

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

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

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

You can establish groups.

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

Need to talk about the difference between synchronous/asynchronous

Is it that important to do a synchronous conversation.

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

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

This could be the origination vehicle

The systemic smarts are much more interesting than the granular control

Because the granular stuff should be automated.

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

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

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

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

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

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

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

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

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

Some compete
Some could augment each other.

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

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

Narrowcast exchangesâ¦

Which Phil Wolff â calls âsearchâ

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

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

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

Thereâs an aggregation function to be served.

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

Angieâs list + ribbit exposes the latency issue

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

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

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

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

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

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

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

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

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

Closingâ¦ align VRM with the core metrics of each of the service providers.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Privacy issues

2009-12-01T12:06:03Z

Hiphopalemi:

Hereâs a possible VRM privacy model for discussion, based on [http://www-306.ibm.com/software/data/db2/eas/anonymous/ existing tools that I work with at IBM]

As a real-world example, Iâm planning on switching cell-phone carriers in February this year, and I also need a new cell phone. In this case, I could enter my needs into a VRM system, which would anonymously store them (in a centralized database via a Web site/Web service, or locally to some kind of P2P client.).

As for how to store the info and identify needsâ¦. Somehow we have to be able to identify the cell phone needed. I suppose that UPC codes could be used or some other identifier, translated from a master list of products offered. The cell phone plan entry is a little more nebulous. Not sure how that one would be identified, other than needs based on a customer formâ¦.minutes needed, family plan, coverage, etcâ¦.(Iâll just skip over this little part for nowâ¦..:)

After the needs are recorded, they would be anonymized via a one-way hash (we currently use the [http://en.wikipedia.org/wiki/SHA-1 SHA-1] algorithm). The original data is still in its original state, but only accessible to the person who created it. Other customers can not see any data but their own.

Hashed entries are stored separately and available for querying by Vendors. Vendors would have to register to receive a shared hash key. That key would allow Vendors to query customer needs, but only for products that they provide, via unique, shared codes.

Vendors can not see customer data. They can only query data with products that they have on offer, via a unique shared ID. The VRM system notifies the customer when a match is found, not the Vendor.

The VRM system could optionally notify the vendor when a match is found, for statistical purposes (comparing hits to products sold, for example), but this binary hit/no hit value is all the vendor would have. The customer remains anonymous until they choose to purchase a product or service.

Customers that are notified when a match is found would be anonymously directed to a Web page or Web Service with an offer for the specific product that they are looking for. It is then up to the customer to decide if they want to pursue the product with that vendor (take the relationship to the next level).

If the offers are all Web Service based, tools could be built to aggregate and compare offers that are returned when needs are recorded. Going even further, the tools could be built to link to product and service reviews, and complete the transaction once a decision is made.

In my real-world example, I would shop for a cell phone and service options online, anonymously, and decide on one or more products that Iâm interested in, pretty much the same way I do now. I would then record my cell phone preferences and service needs in the VRM system. My needs would be hashed and added to the hash values that are accessible to Vendors (via a centralized or P2P-style decentralized system). Registered cell phone vendor A can query the hashed data using the same unique IDs (UPCs or other value) that I entered when I recorded my need. If thereâs a match, I would be notified of an offer from that Vendor by the VRM system. At the same time, Cell phone service provider B could query my plan needs via shared plan IDs or via plan parameters, and offer me a cell phone and cell phone service bundle in conjunction with a cell phone provider.

I would review these offers anonymously and decide which is best for me. Once I have made a decision, I would contact the vendor (via the VRM system, or directly) and proceed with the purchase. The purchase would be my first direct, non-anonymous contact with the vendor.

Once a decision is reached and a purchase has been made, I would remove the record of my needs from the VRM system, and no longer receive offers for that specific product or service.

Things that need more thought, more discussion:
This model only works assuming multiple vendors are trying to sell you the same, somewhat easily identified product or service. For vague items that donât easily fit into this model (video service providers, holiday travel, catering, many other services), more thought is neededâ¦
[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 Address Manager Service

2009-12-01T12:05:37Z

Hiphopalemi: /* Technologies */

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

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

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

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

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

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

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

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

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

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

[[image:PAM_Role_Map.png]]

==Profiles==
A detailed description of each Role's expectations, capability, and requirements for the system, forming an operational context for that particular role. Developed to enough detail to distinguish what this particular role needs from the system design.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===Use Case 21 Administrator deletes account===

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

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

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

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

==Use Case Diagrams==
Both abstract and specific use cases may be diagramed visually to represent the transaction flow between various system components. For abstract use cases, the diagrams will be normative. For specific use cases, they will be illustrative.
==Use Case Maps==
A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.
==Constraints & Requirements==
In addition to responding to specific use cases appropriately, every VRM Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity.

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

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

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

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

===Organizations/Movements===
* DataPortability.org http://www.dataportability.org
* Microformats http://microformats.org
* Liberty Alliance Project http://www.projectliberty.org
* OpenLiberty.org http://www.openliberty.org
* Concordia Project http://www.projectconcordia.org
* [http://informationcard.net Information Card Foundation]

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

We will need protocols for
#Authenticating AddressOwners, AddressUsers, and delegates
#Authorizing AddressUsers & Delegates
#Service discovery
#Inbound human services
#*most likely web pages
#Inbound automated services
#Outbound automated services
#*email
[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 Address Manager Service

2009-12-01T12:04:31Z

Hiphopalemi: /* Use Case 20 Administrator deactivates account */

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

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

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

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

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

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

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

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

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

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

[[image:PAM_Role_Map.png]]

==Profiles==
A detailed description of each Role's expectations, capability, and requirements for the system, forming an operational context for that particular role. Developed to enough detail to distinguish what this particular role needs from the system design.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===Use Case 21 Administrator deletes account===

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

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

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

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

==Use Case Diagrams==
Both abstract and specific use cases may be diagramed visually to represent the transaction flow between various system components. For abstract use cases, the diagrams will be normative. For specific use cases, they will be illustrative.
==Use Case Maps==
A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.
==Constraints & Requirements==
In addition to responding to specific use cases appropriately, every VRM Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity.

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

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

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

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

===Organizations/Movements===
* DataPortability.org http://www.dataportability.org
* Microformats http://microformats.org
* Liberty Alliance Project http://www.projectliberty.org
* OpenLiberty.org http://www.openliberty.org
* Concordia Project http://www.projectconcordia.org
* [http://informationcard.net Information Card Foundation]

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

We will need protocols for
#Authenticating AddressOwners, AddressUsers, and delegates
#Authorizing AddressUsers & Delegates
#Service discovery
#Inbound human services
#*most likely web pages
#Inbound automated services
#Outbound automated services
#*email
[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 Address Manager Service

2009-12-01T12:03:51Z

Hiphopalemi: /* Formats & Protocols */

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

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

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

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

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

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

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

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

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

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

[[image:PAM_Role_Map.png]]

==Profiles==
A detailed description of each Role's expectations, capability, and requirements for the system, forming an operational context for that particular role. Developed to enough detail to distinguish what this particular role needs from the system design.

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

==Use Case Diagrams==
Both abstract and specific use cases may be diagramed visually to represent the transaction flow between various system components. For abstract use cases, the diagrams will be normative. For specific use cases, they will be illustrative.
==Use Case Maps==
A visual representation of the multiple use cases that comprise a particular service and their relationship to one another.
==Constraints & Requirements==
In addition to responding to specific use cases appropriately, every VRM Service shall define its own set of constraints and requirements to complete the specification of the service. Many requirements will be applicable to most, if not all, VRM services, such as those inspired by tenets of data portability and user-centric identity.

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

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

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

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

===Organizations/Movements===
* DataPortability.org http://www.dataportability.org
* Microformats http://microformats.org
* Liberty Alliance Project http://www.projectliberty.org
* OpenLiberty.org http://www.openliberty.org
* Concordia Project http://www.projectconcordia.org
* [http://informationcard.net Information Card Foundation]

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

We will need protocols for
#Authenticating AddressOwners, AddressUsers, and delegates
#Authorizing AddressUsers & Delegates
#Service discovery
#Inbound human services
#*most likely web pages
#Inbound automated services
#Outbound automated services
#*email
[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]

Initiative Brainstorming

2009-12-01T12:02:13Z

Hiphopalemi: /* Draft */

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

==Initiative Brainstorming==
Anyone may add or expand on current ideas for VRM. Simply add to this page and start filling in elements to fully describe the idea. Feel free to start small. Time and other people's contributions can turn even a short headline into something we can work with.

If you have an idea? Copy the template and start filling it in. Brainstorming rules apply:
*Everything is ok, as long as it is a viable VRM idea, inline with VRM [[Principles]].
*If you don't like an idea, improve it or suggest an alternative.

As ideas develop, flesh out the details. Eventually you will probably want to address the "standard" questions, such as
*What's the problem?
*Where does the problem occur?
*Who participates?
*How might we fix it?

Then leave room for discussion. In the discussion area, please sign your comments. And remember, anyone can update the entry itself, but if you aren't sure your idea fits or if you have concerns about a particular element, add it to the discussion.

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]] and is removed from this list. During the 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.

Multiple ideas may be merged into one or one split into multiple. Discussion is probably most effective on the mailing list, with suggestions and thoughts eventually finding their way here after getting fleshed out in email.

Here's a strawman example:
===Digital Receipts===
====Introduction====
Today, we can automatically get our credit card transactions imported into Quicken or QuickBooks or Excel or whatever application we want to use for managing our finances. Why not the line items from the receipts?
====Problem====
I can't get the line items from my purchase receipt on my credit card report. Sure, I can get the credit card data into Quicken, but I'd like to have the line item information so I can more accurately track my spending.
====Where/Context====
In retail and online when I download my transaction history.
====Who====
Retailers, credit card companies, consumers, and business consumers. In fact, this may be even more valuable for small businesses that need to put the line items into different accounts in QuickBooks!
====How====
The line-item data is there, on my receipt! Can't this go online or be sent to my credit card company? I'd like for it to automagically be incorporated when possible when I put the credit card history into Quicken. I have no idea how this might actually be implemented. Perhaps just with my loyalty card and I can download it online, but there would need to be a way to link the line-item report with the credit card history. Otherwise, I might get duplicates.
====Discussion====

==Brainstorm==

===Operation 20%===

====Introduction====
The goal here is to double the contribution rate by listeners and viewers to their public radio and television stations.
*a more detailed introduction by Doc Searls: http://www.linuxjournal.com/node/1000231

====Problem====
Public radio has been around since the turn of the Sixties. Originally called "listener sponsored radio" (primarily by the Pacifica stations), public broadcasting has grown steadily since the advent of National Public Radio (NPR) in the early 1970s. Today NPR is the leading radio network in the U.S. and a solid national institution. Other suppliers of programming PRI, APM, PRX, et. al. have enlarged the variety and depth of programming available over public radio. Through the same time-frame, public television has also grown and thrived.

====Where/Context====
Both forms of public media, however, face the same financial challenge: only about 10% of listeners and viewers contribute to the stations they hear or watch. Put in more blunt financial terms, the customer-to-consumer ratio is 1-to-10.

In both formal and informal surveys, listeners and viewers who don't pay say they would be far more likely to pay if the process were easier.

Making that process easier is the challenge of Operation 20%. Our goal is to double the payment rate, and double the amount of money contributed by viewers and listeners. And our strategy is to provide tools on the listeners' and viewers' side that make contributions easier, and that support improvede relationships between those customers (no longer just consumers) and the stations, networks and producers who bring them the goods. These may end up being the first VRM Vendor Relationship Management tools.

====Who====
In meetings at NPR, and in discussions at both the IMA public media and Berkman-led Beyond Broadcast conferences in February 2007, Doc Searls vetted ProjectVRM's interest in helping relieve this long-standing problem. The response was entirely positive.

Then in early March 2007, the [http://www.loc.gov/crb/ Copyright Royalty Board] of the Library of Congress released [http://www.kurthanson.com/archive/news/030207/index.shtml new royalty rates and requirements] for both commercial and noncommercial stations webcasting online, erasing a distinction between the two that had stood since public broadcasters worked a "carve-out" from the commercial rates in 2002. Unless Congress (which created the CRB in 2004) makes changes in the ruling, or otherwise changes the game, noncommercial radio will face higher (and escalating) costs for using RIAA-licensed music. This adds urgency on the need to go forward with systems that increase the participation rate of listeners to public radio. (And, for that matter, to commercial online radio in as well, since the higher rates are [http://www.linuxjournal.com/node/1000196 a death-sentence for U.S.-based online radio] in general unless ways can be found for listeners to raise their contribution rates.)

====How====
"Operation 20%" is a place-holder name for this initiative. Some other names are under consideration, but not yet disclosed because the domain names associated with them have not been purchased. Anybody is also free to recommend names. A good place to do that is on the ProjectVRM [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list].

The [http://www.beyondbroadcast.net/wiki07/index.php?title=Working_Groups#Public_Radio_and_Open_Source.3B_Facilitating_Technology_Collaboration_-_Held_in_The_Landau_Building_.28Bldg._66.29.2C_Room_156Public radio and Open Source] working group at Beyond Broadcast, and its organization, [http://www.beyondbroadcast.net/wiki07/index.php?title=Pubforge.org PubForge], are allied efforts that need to be coordinated as well.

====Discussion====
This initiative, along with others, will be on the front-burner both at Berkman Center meeting(s) in the first week of April (when Doc is in Cambridge), and at the [http://www.windley.com/events/iiw2007a/ Internet Identity Workshop] in Mountain View, California (Bay Area, between San Francisco and San Jose), on May 14-16.

===SYO Share Your OPML Project===
====Introduction====
Dave Winer has three posts that outline the Share Your OPML (SYO) project, and progress in developing it:
* [http://www.scripting.com/2006/11.html#opportunityKnocks Opportunity Knocks]
* [http://www.scripting.com/2007/01/04.html#opportunityKnocksTry2 Opportunity Knocks Try #2]
* [http://www.scripting.com/2007/01/05.html#opportunityKnocksTry3 Opportunity Knocks Try #3]
* I've deployed a first pass at what Dave proposes in #3. This is for testing and feedback purposes only. Any uploaded data to this development site will possibly and most likely be swept clean during future development phases. Here at [http://dev.glistn.com http://dev.glistn.com]
====Problem====
====Where/Context====
====Who====
====How====
====Discussion====

===Upside-down buyer's guide===
====Introduction====
[http://zgp.org/~dmarti/blosxom/business/upside-down-bg.html Don Marti writes],

''Doc has been contemplating business, identity and vendor lock-in, and makes me think about an interesting experiment -- use links, tags, and a microformat to help people buy a "commodity" IT product, the 1U or 2U rack-mount Linux server.''
====Problem====
====Where/Context====
====Who====
====How====
''First step would be to come up with a microformat for a "server RFQ". At the beginning of the experiment, these could be relatively loose -- just a bunch of "ol"s with "id"s such as "required-parts" "preferred-parts", "disliked-parts", "forbidden-parts", "required-features" and so on.''

''There would also be a section for "status", which would be time until buying decision, "deferred" "cancelled" or "ordered". If and when the idea got more popular, the RFQ could be more detailed, and sites and apps could offer server RFQ construction wizards. The nice thing about using a microformat is that (1) it's human-readable in a browser and (2) you can add free-form commentary on what you like or don't like in a server.''

''So you want to buy a server? Write your server RFQ, put it up with a rel="tag" link to a Technorati tags page for "server RFQs". and another tag link to a new, unique tags page just for that one, such as "joe@example.com-2005-07-09".''

''Along come the vendors who want to sell you a box, and are naturally watching the "server RFQs" tag like hawks, I mean like some animal that doesn't want to eat you. Like Easter Bunnies? Vendor sales person checks your RFQ, makes a page for you with links to matching products and a rel=tag link to "joe@example.com-2005-07-09". This is highly automatable, but careful, vendors -- don't spam. A future web-based product configurator should be able to crawl a server RFQ page and come up with a good quotation in response.''

''Now, you, the buyer, just watch the RSS feed for joe@example.com-2005-07-09 -- hey presto, it turns into your own personalized Server Buyers' Guide! When you buy the server, you change the "status" field on the RFP to "ordered", and add a link to the vendor you bought from. This is to (1) give the good vendors Google Juice and (2) let vendors know you're serious in the future so they'll pay attention to your RFQs. ''
====Discussion====

===Setting terms of service===
====Introduction====
In [http://www.usatoday.com/money/perfi/credit/2006-12-15-card-fees-usat_x.htm Credit card fees can suck you in Consumers pay high price for increasingly complex policies], in USA Today, Kathy Chu reports,

''Remember when most of us paid only an annual fee on credit cards? Today, late fees and over-the-limit fees are replacing that annual fee. Add in a dizzying array of extra charges: for phone payments, "expedited" online payments, credit card use overseas and balance transfers from other cards.''

''At a time when Americans wield more plastic than ever â 692 million credit cards, with $711 billion of debt â fees and policies have grown so complex that even regulators struggle to grasp them.''

''In the holiday shopping frenzy, consumers are especially vulnerable to card fees, because more of them are likely to pay late or exceed their credit limit, according to industry consultants Nilson Report and Moebs Services.''

''Lots of card issuers offer low initial interest rates these days. But once they've pulled you in, they often replace "fixed" rates with floating rates â which can rise â and impose penalty rates of up to 30% even on those with good credit.''

''"It's like economic Darwinism," says Chi Chi Wu of the National Consumer Law Center, an advocacy group. "The business model has changed from one rate and annual fee to all these different tiers and fees designed to make money."''

This is a perfect example of what CRM does without the benefit of VRM.
====Problem====
====Where/Context====
====Who====
====How====
We need something on the customers' side that directly tells vendors and the whole credit card marketplace "Either give me the terms I want (e.g. 30 day grace period, X% or lower fixed interest rate, $X cap on annual fees) or I'll take my business elsewhere."
====Discussion====
Wouldn't it be great for customers to operate in a bloc on this kind of thing? I'd love to see an organized group of consumers that organize themselves and deal as one with major organlzations- much the way labor unions negotiate on behalf of workers. This could work in a number of industries, but the credit industry is screaming for this kind of reform. Say, for instance, a group of several thousand cardholders organized themselves and they're dissatisfied with the way a bank reprices consumer accounts after a single late payment. The bloc could contact the bank and competitors, and either choose a better vendor or force the bank to change their policy for the bloc or lose a sizeable amount of customers.

Banks and many other institutions ''compete'', but it seems there is little competition. An average consumer might switch to an account with a better interest rate, and find much later on that the change was a horrible mistake because of fine print they didn't have the time, education, knowledge or wherewithal to learn about. For this to work, members of the bloc (or whatever you call it) would have to agree to make changes with the bloc, and the bloc would need to be run by independent, intelligent managers- sort of a mutual fund for consumer services.

===Educators vs. Cold Callers===
====Introduction====
Russ, [http://www.russdev.com/wp-blog/about-me/ a network manager at a UK high school], [http://www.russdev.com/wp-blog/2006/12/16/suppliers-vendors-vrm-is-future/ writes],

''We have the technology already, itâs called blogs. I am currently setting up a blog so suppliers at work can subscribe to an RSS feed and it provides them with information on what I want.''

''But not everyone uses RSS so the fact that most blogs have the function to view posts as web pages, plus the ability to email out new posts to people means you have that angle covered. The more I read on this concept the more it addresses some of the major problems we as customers have and suppliers have with customers.''
====Problem====
====Where/Context====
====Who====
====How====
====Discussion====

===Personal Health Records===

====Introduction====
Today, medical information is locked in cabinets and largely isolated behind doctor's and institutional barriers. Much of this arrangement is about protecting our rights to privacy. Kudos for that. However, the primary need in the realm of medical information, is quality health and health services... the secrecy is a solution to a constraint, not a requirement of the underlying need.
====Problem====
This unfortunate silo nature of the existing medical data system results in a loss of transparency and choice when individuals want to work with different providers. This lack of access and control leaves patients with restricted vendor management options.
====Who====
At the Internet Identity Workshop (iiw2006b), Doc brought this to light in the context of Johnson & Johnson's interest in providing enhanced drug packaging services, such as custom daily packets for people with complicated drug regimens. Unfortunately, J&J can't offer this service because of a systemic inability to access customer information effectively--even when the customer wants them too.

In a December 2007 [http://www.google.com/press/podium/markle.html speach], Google's Vice President Adam Bosworth echoed this need:

<blockquote>
Google can find all the most relevant answers to any query you submit across the entire web in less than a one-third of a second and yet, in general, your physician cannot get the lab results from your last specialist without paper and fax. (...)
Your physician cannot always reliably and optimally treat you without a comprehensive knowledge of what has been wrong with you in the past, how you were treated, and how you responded to the treatment. The lack of easily accessible, comprehensive medical records results in people being in more pain for longer than they should be. (...)

We should not accept this. We should not accept that the institutional barriers of the system cause tens of thousands to die unnecessarily and hundreds of thousands at the very least to suffer without cause while we pay an enormous bill.

So what can be done? We should start at the beginning. Letâs put the patients in charge of their health and medical information. Letâs build a system which puts the people who are sick in control. For every single medical and health-related event, letâs make sure that patients can effortlessly retrieve and share their information in its totality and then use it to ensure that they get the best quality of care possible. It is their health.
</blockquote>

Thanks to Philipp Lenssen of [http://blog.outer-court.com/ Blogoscoped] for the [http://blog.outer-court.com/archive/2007-01-12-n25.html quote].
====How====
====Where/Context====
====Discussion====
There is an active development effort around "Personal Health Records," with "Dossia" as one significant umbrella project. Google provides a significant amount of information on Dossia and PHRs.

===Personal Knowledge Banks===

====Introduction====

For many years, organizations have gathered and used information on the parties with whom they interact (customers, partners or suppliers etc). This underpins much of what they do. Two specific types of information systems have emerged as being necessary and of value for effective deployment:

- Operational systems that âget the job doneâ (e.g. CRM applications, procurement systems, billing engines, fulfillment systems etc.)
- Analytical systems that underpin longer term knowledge gathering, planning and decision-making (e.g. enterprise data warehouse, single/ complete customer view, business intelligence)

The cost of putting such capabilities in place is falling dramtically, and personal need/ ability to fund their own equivalents is rising â so a new requirement is emerging, that of professional-grade information management and use services for individuals. VRM has much to gain from this development.

====Problem====

As daily life increasingly relies on digital technologies and data, individuals increasingly become dependent on data silos that are run by organizations they interact with. These organizations, by their nature, do not necessarily have the best interests of the individual as their raison dâetre. For example, the individual now has to âsign onâ and leave personal information trails in many more places than ever before. In turn, privacy-invading marketing practices leverage these information trails to target individuals with communications. The combination of more targeting data being available and less expensive communications channels means that the individual are spending more time being exposed to messages; when the vast majority of these messages are based on relatively poor quality data input then the time of these individuals is being abused by suppliers.
Public sector organizations have less to gain in terms of gathering information for marketing purposes â but data gathering and use by large, public sector bodies has its own âbig-brotherâ related downsides.

In parallel, existing approaches individuals are able to take to managing personal âlifeâ information are inadequate. The shoebox full of important documents is no longer relevant when those documents are digital. The PDA/ cell-phone/ PC address book combos do some basic tasks well, but are limited by their relatively narrow architectures. The various personal finance/ personal health/ lifestyle management applications have many upsides, but are based on locking in the customer to a proprietary architectures and a seller-centric business model.

====Where/Context====

An individual, on average, has 50 â 100 suppliers of some significant to them (some have many more). Each of these suppliers will typically be running or building some equivalent of their âsingle customer viewââ, and each will typically also store personal information on that individual in 4-5 operational systems. This issue applies across most aspects of life, and the vast majority of industry sectors.

The logic for this data gathering is that a) data has value to the organization, and b) that there is nowhere else to get it from.

The spend on âsingle customer viewâ across organizations and sectors amounts to many billions per annum, with considerable growth forecast for the foreseeable future.

The Personal Knowledge Bank offers an alternate option â enabling suppliers to âgo to the sourceâ rather than maintain a copy, especially when the source contains richer, deeper, more accurate data than is available elsewhere. It also enables much more besides (for now we shall focus on the enabling VRM aspectsâ).

====Who====

Personal Knowledge Banks are most likely to be run as a service that an individual outsources to one or more agent(s) who have built the architecture and technology environment to run such services professionally and cost-effectively (as organizations do around credit rating etc).

These services could theoretically be run by existing organizations that manage personal information well â with the killer proviso that a truly functional Personal Knowledge Bank can only be run by buyer-centric organization, i.e. those architected to support the buyer. In doing so they may also support the seller, but their primary orientation must be buyer-centric.

====How====

Some of the key components of a Personal Knowledge Bank are:

- A rich, deep (preferably open) data architecture recognizing both analytical and operational requirements

- An identity layer (person-centric and ideally interoperable with top down identity protocols)

- Security

- Front-end applications

- Information hygiene and management processes

Above all else, there should be a recognition that such tools and the processes around them will evolve rather than appear in âbig bangâ mode. Organizations began their information management and usage journeys 30 to 40 years ago â and they continue to become âbigger/ better/ fasterâ each year. The individual equivalents will also be a journey rather than a destination.

====Discussion====

We must get beyond thinking of Personal Knowledge Banks (or however they come to be named) as technology projects. Yes, they are â but in practice there are far wider/ higher barriers to be addressed around process, data gathering and âcultureâ. That said, the return on investment for an individual that will emerge will make a compelling case for over-coming these barriers.

==Initiative Template==
To add an Initiative, click on the edit link directly to the right. That will bring up a wiki editor with the following sections and this paragraph.

Copy the list of sections, including "Initiative Name" and paste them '''above''' the "Initiative Template" section header. Then fill in the details. Replace "Initiative Name" with the name of your initiative and add a few sentences (or more) for each section.

Once you save the page, you will be able to edit each section individually, using its own edit link.

===Initiative Name===
====Introduction====
====Problem====
====Where/Context====
====Who====
====How====
====Discussion====

==Draft==
This is a draft proposal. I'm particularly interested in both real Initiative Ideas and improvements to the template.
[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 issues

2009-12-01T12:01:44Z

Hiphopalemi:

Very much a stub...

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

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

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

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

----

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

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

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

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

----

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

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

Conference call archive

2009-12-01T12:00:19Z

Hiphopalemi: /* March 19, 2008 */

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

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

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

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

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

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

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

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

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

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

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

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

===March 19, 2008===
*[[http://cyber.law.harvard.edu/projectvrm/March_19_2008_Conference_Call]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Blogs

2009-12-01T11:59:41Z

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

== Blog posts on VRM ==

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

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

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

Action Items 1 25 Meeting

2009-12-01T11:59:10Z

Hiphopalemi:

{|
|'''what'''|| '''who'''||'''where'''
|-
|open id on wiki||david ||no date
|-
|group blog/RSS to wiki (venus)||david||no date
|-
|project VRM definition||doc||1 week
|-
|thurs, 1:30pm EST concall setup||dean||8 feb
|-
|Initiative brainstorm page||joe||1 feb '''DONE'''
|-
|brainstorm Initiatives||all||ongoing
|-
|relationship/expression matrix||chris/deb||feb 1
|}
[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]

Technology

2009-12-01T11:57:35Z

Hiphopalemi:

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

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

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

* VRM and [[taxonomy issues]]

* VRM and [[identity issues]]

* VRM and [[privacy issues]]

* Partial implementation as [[Firefox plugin]]?

* VRM and [[Liberty Alliance]]
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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-01T11:56:57Z

Hiphopalemi:

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

Process

2009-12-01T11:56:17Z

Hiphopalemi: /* 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]

Principles

2009-12-01T11:55:45Z

Hiphopalemi: /* 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]

Initiatives

2009-12-01T11:55:21Z

Hiphopalemi:

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]

Events

2009-12-01T11:54:50Z

Hiphopalemi: /* 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]

Usage Committee

2009-12-01T11:53:55Z

Hiphopalemi: /* Approaches to driving VRM Usage */

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

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

== Committee members ==

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

== Approaches to driving VRM Usage ==

#industry/vendor driven
#web/user driven
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Organization Committee

2009-12-01T11:53:26Z

Hiphopalemi:

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

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

This is a placeholder page, soon to be replaced by committee members.
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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-01T11:53:03Z

Hiphopalemi:

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]

Personal RFP

2009-12-01T11:51:31Z

Hiphopalemi:

An [http://www.techcrunch.com/2009/09/15/redbeacon-wins-the-top-prize-at-techcrunch50-2009/ RFP] is a buyer-initiated procurement protocol used by businesses, governments and other large organizations. It is, literally, what the letters stand for: a Request For Proposal. Among a suite of similar TLAs (three letter acronyms) that begin with "Request for" -- RFI (Request for Information), RFQ (Request for Quotation), RFT (Request for Tender) -- RFP is the most familiar.

RFPs, however, are about as personal as heavy construction. They're something only big organizations do.

In a VRM context, however, an RFP is something an individual should be able to do in the open marketplace. An individual should be able to issue an RFP that says, for example,

- "I need a stroller for twins in Glasgow in the next three hours."
- "I need a ThinkPad T60 power supply near SFO this afternoon."
- "I need to rent a minivan that seats six and has a roof rack in Salt Lake City next week."
- "I need wheel rims for a 1967 Peugeot 404."
- "I need a 200 watt 220-110 volt power converter in Copenhagen this afternoon"

[[http://dilbert.com/blog/entry/hunter_becomes_the_prey/ Scott Adams calls this]] "broadcast shopping."

The customer can also provide a sum he or she is willing to pay. He or she should be able to do this in a way that is secure and involves minimal disclosure of personal information.

There are many ways this can be done now, through non-substitutable websites and services. Craigs List and eBay both provide means for requesting products. Twitter does too.

What makes a personal RFP a VRM protocol is the substitutability of the services answering the request. The customer should be able to express demand in the open marketplace rather than only within a single intermediary's silo or walled garden.

Personal RFPs can be thought of as a form by which demand advertises to supply, rather than vice versa. It involves no guesswork about what the customer wants, or whether there is money on the table.

As matters currently stand, there is an enormous sum of demand -- such as the RFPs mentioned above -- that can result in MLOTT (Money Left On The Table) if the supply side fails to hear the demand and complete a sale. There is no equivalent of the RFP, RFI and RFQ for individuals. Yet the demand exists. Money is there. What we need is the table.

That table is a set of protocols, rituals and systems for routing requests from demand to supply, and responses back. Setting up that table is a primary challenge for VRM.
[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-01T11:50:44Z

Hiphopalemi: /* 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-01T11:49:55Z

Hiphopalemi:

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

Interesting Links

2009-12-01T11:45:53Z

Hiphopalemi:

[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.sempatim.net seviÅme]

User:Joe.andrieu

2009-12-01T11:44:29Z

Hiphopalemi:

I sometimes talk about VRM on my [http://blog.joeandrieu.com blog].

My full contact information can be found at http://www.switchbook.com/#Joe

If you would like an account on this wiki, email [mailto:joe@switchbook.com me]:

*Your full name
*Your email address
*And a brief introduction. Just a sentence or so to convince me you are a real person and not a bot.
[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]

User:Deb

2009-12-01T11:42:57Z

Hiphopalemi:

Random thoughts on VRM

How to integrate in to current 'new marketing' discussions to get industry to understand broad implications and power of model
To chris' point - let's not reinvent the wheel.
[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]

VRM discussion in podcasts

2009-12-01T11:38:11Z

Hiphopalemi:

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

VRM2008

2009-12-01T11:32:25Z

Hiphopalemi: /* Thanks */

This is the base page for VRM2008 at the European Identity Conference in Munich April 21-22, 2008.

If you are at the unconference, please feel free to contribute here. Just click the edit button. If there is no edit button, first create an account or log in. Once you are logged in, you can also click on the "edit" links for each section.

==Sessions==
This will become a session list. Enclose Session names in double brackets and it will become a link to a separate page for that session. This is the easiest way to create a new wiki page for your session. Even better, if you prepend the session name with VRM2008, we can guarantee it will be unique for the unconference. Then you can use a "pipe" | character to have a more user friendly name. See the Personal Address Manager session for an example:
* [[VRM2008 Personal Address Manager|Personal Address Manager]]
* [[VRM2008 User-centric Search|User-centric Search]]
* [[VRM2008 Higgens/OpenIDSAML InfoCards as VRM enabler]]
* [[VRM2008 VRM and Advertising]]
* [[VRM2008 Phil and Paul get married (BT)]]
* [[VRM2008 Rel Button]]
* [[VRM2008 Business Value/Aspects of VRM]]

==Attendees==
Please feel free to add yourself as an attendee, with any contact information you might want to offer to others interested in VRM.
*Doc Searls
*Joe Andrieu (facilitator) mailto:joe@switchbook.com
*Bart Stevens (facilitator) mailto:bart.stevens@ichoosr.com
*Charles Andres mailto:candres@parityinc.net
*Phil Whitehouse mailto:phil.whitehouse@gmail.com
*Paul Downey

==Thanks==
Joe Andrieu and Bart Stevens would like to extend a special thanks to Kuppinger Cole and Joerg Resch for their gracious support and sponsorship. This meeting wouldn't have been possible without them.

We'd also like to thank all the participants who took the time to join us for the conversation. You are the folks who create the potential for meetings like this to create real value for all of us.
[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-01T11:31:56Z

Hiphopalemi: /* Join Us! */

== About VRM ==

VRM, or Vendor Relationship Management, is the reciprocal of CRM or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]. It provides customers with tools for engaging with vendors in ways that work for both parties.

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

The goal of VRM is to improve the relationship between Demand and Supply by providing new and better ways for the former to relate to the latter. In a larger sense, VRM immodestly intends to improve markets and their mechanisms by equipping customers to be independent leaders and not just captive followers in their relationships with vendors and other parties on the supply side of the marketplace.

For VRM to work, vendors must have reason to value it, and customers must have reasons to invest the necessary time, effort and attention to making it work. Providing those reasons to both sides is the primary challenge for VRM.

== Project VRM ==

[http://projectvrm.org Project VRM] is a community-driven effort, led by [http://cyber.law.harvard.edu The Berkman Center for Internet and Society] at Harvard University, to support the creation and building of VRM tools. ProjectVRM carries forward thinking by various parties around the world. These include ideas brought up by Doc Searls and his fellow [http://cluetrain.com Cluetrain Manifesto] authors, work of the [http://www.rightsideup.net/ Buyer Centric Commerce Forum] and other allied efforts in the U.K., and many sessions at Internet Identity Workshops.

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

In addition to this wiki, ProjectVRM has [http://blogs.law.harvard.edu/vrm a blog] and a [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list].

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

== VRM Principles ==

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

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

In a broader way, the same should be true of individuals relating to organizations. With VRM, however, our primary focus is on customer relationships with vendors, or sellers.

== VRM Goals ==

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

== VRM Current Topics ==

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

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

== VRM Committees ==

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

== Allied Efforts ==

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

== Resources ==

* ProjectVRM [[mailing list]]

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

* [[VRM FAQ]]

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

* Project VRM [[committees]]

* VRM and -related [[events]]

* VRM [[Initiatives]]

* VRM [[Principles]]

* VRM [[Process]]

* VRM [[scenarios]]

* VRM [[technology]]

* VRM coverage in [[blogs]]

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

* [[Questions raised]] by VRM

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

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

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

* [[Website planning]]

* Other [[related efforts]]

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

== VRM Lexicon ==

* [[VRM lexicon]]

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

== VRM Events ==

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

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

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

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

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

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

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

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

== Join Us! ==

Looking to contribute to the Project VRM Wiki? Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list], send an email to the owners, and we'll get you up and running!
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.pornositeleri.org porno siteleri]
[http://www.sexpormok.net sex]
[http://www.mynetsohbet.net mynet sohbet]
[http://www.hiphopalemi.net chat]
[http://www.hiphopalemi.net rap]
[http://www.kelebekchat.net kelebek]
[http://www.gaychat.gen.tr gay chat]
[http://www.cinsel-sohbet.com cinsel sohbet]

Committees

2009-12-01T11:31:04Z

Hiphopalemi: /* 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]

Personal Health Records

2009-12-01T11:30:35Z

Hiphopalemi:

The time to explore this topic is now.

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

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

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

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

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

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

What's going on? How can we help? What skill sets can we bring to the table?
[http://www.sexalemi.org sikis izle]
[http://www.pornositeleri.net porno izle]
[http://www.sexalemi.org sex izle]
[http://www.sexalemi.org sikis]
[http://www.cinsel.name sikis izle]
[http://www.cinsel.name.tr sikis]
[http://www.hiphopalemi.net hiphop]
[http://www.kelebekchat.net kelebek chat]
[http://www.kelebeksohbet.org kelebek sohbet]
[http://www.chatsohbet.org chat sohbet]
[http://www.siberchat.net chat]
[http://www.pornositeleri.net porno]
[http://www.pornositeleri.org porno izle]
[http://www.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]

Media Logging

2009-12-01T11:30:01Z

Hiphopalemi:

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]