Project VRM - User contributions [en]

Main Page

2011-08-24T10:47:00Z

Tcarroll: removed LOTS of spam links

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal  the customer side  of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking of slave-owners when dealing with customers. With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls] when he became a fellow at the Center in 2006. (He has been an alumnus fellow since September 2010). The purpose of the project is to encourage VRM development and to conduct research on its premises and its progress.

When the project began, Doc saw it as "a way to fulfill the promise of [http://www.smslaan.org Sms lån][http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue":

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, companies, allied associations and individuals, in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events.

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

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable) ? VRM tools and services will answer these and many other questions that could not be asked before the Internet and came along  and cannot be asked, as long as sellers continue to hold all the relationship cards.

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones''  to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social, in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers
#Base relationship-managing tools on open standards, open APIs (application program interfaces). This will support a rising tide of activity that will lift an infinite variety of business boats plus other social goods.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:
*[http://www.azigo.com/ Azigo.com]
*[http://www.banyanproject.com/ The Banyan Project]
*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org]
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]
*[http://kynetx.com Kynetx], which also does [http://hvr.me HoverMe]
*[[ListenLog]]
*[https://github.com/quartzjer/Locker#readme The Locker Project]
*[http://themineproject.org/ The Mine! Project]
*[http://mydex.org/ MyDex]
*[http://www.vrm.cl/ myinfo.cl]
*[http://newgov.us/ NewGov.us]
*[http://www.paoga.com/ Paoga]
*[http://pegasuspublic.wikispaces.com/ Pegasus]
*[http://personal.com Personal.com]
*[http://personaldataecosystem.org/ Personal Data Ecosystem]
*[[Personal RFP]]
*[http://projectdanube.org/ ProjectDanube]
*[http://www.projectnori.org/ Project Nori]*[http://www.qiycorporate.com/ QIY]
*[[r-button]]
*[http://sing.ly/ Singly]
*[http://www.socialnori.org/ Social Nori]
*[http://www.switchbook.com/ SwitchBook]
*[http://telehash.org Telehash]
*[http://www.thumbtack.com/ Thumbtack]
*[http://www.trustfabric.com/ TrustFabric]
*[http://kantarainitiative.org/confluence/display/uma/ UMA]
*[http://www.vrmhub.net VRM Hub]
*[http://www.vrmlabs.net VRM Labs]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

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

== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]

=== Past Events ===
2011
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12], May 3-5, Mountain View, CA
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]]
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. You can also edit this wiki by signing up at the top of this page.

Main Page

2011-08-24T10:37:58Z

Tcarroll: /* VRM Development Work */ removed several spam links, added azigo.com, alphabetized list

== About VRM ==

VRM stands for '''Vendor Relationship Management'''. VRM tools provide customers with both ''independence'' from vendors and ''better ways of engaging'' with vendors. [http://www.writers-write.co.uk Essay writing] The same tools can also support individuals' relations with schools, churches, government entities and other kinds of organizations.

In a narrow sense, VRM is the reciprocal the customer side of CRM (or [http://en.wikipedia.org/wiki/Customer_Relationship_Management Customer Relationship Management]). VRM tools provide customers with the means to bear their side of the relationship burden. They relieve CRM of the perceived need to "capture," "acquire," "lock in," "manage," and otherwise employ the language and thinking [http://www.allwritingsource.co.uk/essay-writing-service.php Essay Writing] of slave-owners when dealing with customers.[http://www.writers-write.co.uk/article-buy-essay.php uk essay writing] With VRM operating on the customer's side, CRM systems will no longer be alone in trying to improve the ways companies relate to customers. Customers will be also be involved, as fully empowered participants, rather than as captive followers.[http://www.writers-write.co.uk/custom-assignment-help.php assignment help] [http://www.teethwhiteningathomev.com/ Teeth whitening]

VRM development projects are listed below.

== Project VRM ==

[http://projectvrm.org ProjectVRM] is a project of [http://cyber.law.harvard.edu the Berkman Center for Internet & Society] at Harvard University. It was created by [http://en.wikipedia.org/wiki/Doc_Searls Doc Searls] when he became a fellow at the Center in 2006. (He has been an alumnus fellow since September 2010). [http://www.writers-write.co.uk/statistics-help.php statistics help] The purpose of the project is to encourage VRM development and to conduct research on its premises and its progress.[http://www.essaymojo.co.uk/essay-service.php UK Essay Writing]

When the project began,[http://www.writers-write.co.uk/statistics-help.php statistics help] Doc saw it as "a way to fulfill the promise of [http://www.smslaan.org Sms lån][http://cluetrain.com ''The Cluetrain Manifesto'']'s Prime Clue": [http://www.diamondlinks.net link building services]

[[Image:Not-1.gif]]

Doc believed that customer reach would only exceed vendor grasp if customers had the tools for the job. So Doc created ProjectVRM to support the creation and building of those tools.

Since then the VRM community has grown to include many development projects, companies, allied associations and individuals,[http://www.writers-write.co.uk/university-essays.php University essays] in addition to ProjectVRM itself. The community's work is outlined in this wiki, and discussed on its [http://cyber.law.harvard.edu/projectvrm/Mailing_list mailing list], its [http://blogs.law.harvard.edu/vrm blog] and in workshops and other events.

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

== VRM and the Economy ==

The economic goal of VRM is to improve relationships between Demand and Supply by providing new and better ways for the former to engage with and drive the latter.

This is not possible when all the tools of engagement are provided by suppliers, and all those tools are different. For example, most customers today carry around up to dozens of "loyalty" cards and key-ring tags, each with its own vendor-provided means for controlling interactions and providing benefits. These inconvenience both buyers and sellers, and limit the intelligence that can be gathered and put to use by either party. [http://www.writers-write.co.uk/dissertation-writing-help.php Dissertation writing service] What if buyers had the ability to advertise their shopping lists to the sellers with which they have relationships? What if buyers were able to establish and maintain loyalty on their own terms and in their own ways? What if customers' ability to express preferences and advertise demand were improved to the point where sellers could reduce money wasted on advertising and other forms of guesswork? What if it were quick and easy for customers to say what they'll pay for what they want, on their own terms (and to pay on the spot, if the terms are mutually agreeable)[http://www.essayinn.co.uk Essay Writing] ? VRM tools and services will answer these and many other questions that could not be asked before the Internet and [http://www.ascomsa.net/ hosting] came along and cannot be asked, as long as sellers continue to hold all the relationship cards.[http://www.writers-write.co.uk/dissertation-writing-help.php Dissertation writing service]

www.kraldost.com

== VRM Principles ==

VRM development work is based on the belief that ''free customers are more valuable than captive ones'' to themselves, to vendors, and to the larger economy. To be free 

#Relationships must be voluntary.
#Customers must enter relationships with vendors as independent actors.
#Customers must be the points of integration for their own data.
#Customers must have control of data they generate and gather. They must be able to share data selectively, voluntarily, and control the terms of its use.
#Customers must be able to assert their own terms of engagement and service.
#Customers must be free to express their demands and intentions outside of any one company's control.
[http://www.dissertationinn.co.uk/ dissertation help uk]

VRM research work probes the willingness and ability of customers to assert and enjoy independence from vendors -- and of vendors' willingness and ability to value and engage with independent customers. [http://www.dissertationinn.co.uk/dissertation-service/ dissertation writing service] It also follows changes in the marketplace as VRM tools come into use.

== VRM Goals ==

In the "Markets Are Relationships" chapter of the [http://www.cluetrain.com/Cluetrain_10/index.html 10th Anniversary edition] of ''The Cluetrain Manifesto'', Doc Searls writes this about the purposes of VRM efforts:

#Provide tools for individuals to manage relationships with organizations. These tools are personal. That is, they belong to the individual in the sense that they are under the individual's control. They can also be social,[http://www.dissertationinn.co.uk/dissertation-proposal/ dissertation proposal] in the sense that they can connect with others and support group formation and action. But they need to be personal first.
#Make individuals the collection centers for their own data, so that transaction histories, health records, [http://longtermcareinsuranceinfo.com/ long term care insurance], membership details, service contracts, and other forms of personal data are no longer scattered throughout a forest of silos.
#Give individuals the ability to share data selectively, without disclosing more personal information than the individual allows.
#Give individuals the ability to control how their data is used by others, and for how long. At the individual's discretion, this may include agreements requiring others to delete the individual's data when the relationship ends.[http://www.dissertationinn.co.uk/dissertation-writers/ dissertation writers]
#Give individuals the ability to assert their own terms of service, reducing or eliminating the need for organization-written terms of service that nobody reads and everybody has to "accept" anyway.
#Give individuals means for expressing demand in the open market, outside any organizational silo, without disclosing any unnecessary personal information.
#Make individuals platforms for business by opening the market to many kinds of third party services that serve buyers as well as sellers of [http://katyperryfirework.net katy perry firework]
#Base relationship-managing tools on open standards, open APIs (application program interfaces), and open [http://www.easyunlocks.com/ blackberry unlock codes]. This will support a rising tide of activity that will lift an infinite variety of business boats, a [http://www.hybridcab.com/ hybrid cab] plus other social goods.

== VRM Development Work ==

Here is a partial list of VRM development efforts. Some are organizations, some are commercial entities, some are standing open source code development efforts:
*[http://www.azigo.com/ Azigo.com]
*[http://www.banyanproject.com/ The Banyan Project]
*[[EmanciPay]]
*[[FCRA: Access to credit data]]
*[[GRM: Government Relationship Management]]
*[http://higgins-project.org higgins-project.org]
*[http://kantarainitiative.org/confluence/display/infosharing/Home Information Sharing Workgroup at Kantara]
*[http://kynetx.com Kynetx], which also does [http://hvr.me HoverMe]
*[[ListenLog]]
*[https://github.com/quartzjer/Locker#readme The Locker Project]
*[http://themineproject.org/ The Mine! Project]
*[http://mydex.org/ MyDex]
*[http://www.vrm.cl/ myinfo.cl]
*[http://newgov.us/ NewGov.us]
*[http://www.paoga.com/ Paoga]
*[http://pegasuspublic.wikispaces.com/ Pegasus]
*[http://personal.com Personal.com]
*[http://personaldataecosystem.org/ Personal Data Ecosystem]
*[[Personal RFP]]
*[http://projectdanube.org/ ProjectDanube]
*[http://www.projectnori.org/ Project Nori]*[http://www.qiycorporate.com/ QIY]
*[[r-button]]
*[http://sing.ly/ Singly]
*[http://www.socialnori.org/ Social Nori]
*[http://www.switchbook.com/ SwitchBook]
*[http://telehash.org Telehash]
*[http://www.thumbtack.com/ Thumbtack]
*[http://www.trustfabric.com/ TrustFabric]
*[http://kantarainitiative.org/confluence/display/uma/ UMA]
*[http://www.vrmhub.net VRM Hub]
*[http://www.vrmlabs.net VRM Labs]
*[http://code.google.com/p/webfinger/ webfinger]

== ProjectVRM Committees ==

*[[Vision Committee]]
*[[Marketing Committee]]
*[[Standards Committee]]
*[[Organization Committee]]
*[[Usage Committee]]
*[[Compliance Committee]]
*[[Steering Committee]]
* [http://www.headlicetreatmentworld.com/ head lice treatment]
== ProjectVRM Resources ==

* ProjectVRM [[mailing list]]
* ProjectVRM [http://blogs.law.harvard.edu/vrm blog]
* [[VRM FAQ]]
* VRM [Twitter stream http://twitter.com/vrm]

Conference Call archive and audio links can be found at the [[Project_VRM:Community_Portal | Community Portal]] page.

== VRM Events ==

Also see [http://cyber.law.harvard.edu/projectvrm/Events Events] page.
ProjectVRM events take place once or twice per year:
=== Upcoming Events ===
2011
* [http://iiw13.eventbrite.com/ IIW XIII (2011-B)] October 18-20, 2011, Mountain View, CA]

=== Past Events ===
2011
* [http://www.customessayhelp.com/write-my-essay.html write my essay]
*[http://www.internetidentityworkshop.com/iiw-12/ IIW #12], May 3-5, Mountain View, CA
*[http://www.cvent.com/events/conversational-commerce-conference/event-summary-f70a703bbabf4cda930c1412dee2bf4f.aspx Conversational Commerce Conference], February 2-3, San Francisco
* [http://impact.kynetx.com/ IMPACT/2011], March 22-23, Salt Lake City, UT
* VRM Gathering at [[SXSW Interactive 2011]]
* [http://iiw12.eventbrite.com/ IIW XII (2011-A)] May 3-5, 2011, Mountain View, CA

2010
* [[VRM+CRM%202010]] August 26-27 Harvard University, Cambridge, MA

2009
* [[VRooM Leadership Workshop]] took place on 31 Oct * 1 Nov in Mountain View, CA
* [[VRM East Coast Workshop 2009]] (VRooM 2009) took place on 12-13 October at Harvard University
* [http://www.logodesignmaestro.co.uk custom logo design]
* [[VRM at SXSW 2009]] were meetings during SXSW in March 2009, Austin, TX
* [[VRM West Coast Workshop 2009]] took place May 15-16, 2009 in Palo Alto, CA
* [http://www.iyap.se Iyap][http://www.coppervalleycustomhomes.com custom home builders]
* [[[http://www.sungatetours.com/inca-trail.html Inca Trail Tours] took place June 15-17 in Peru, South America.

2008
* [[VRM2008]] took place in Munich on 21/22 April 2008
* [[VRM Workshop 2008]] took place in July 2008 at Harvard University
* [http://www.essaymojo.co.uk/write-my-essay.php Write My Essay]
* [http://www.essaymojo.co.uk/UK-Essay-Help.php Buy Essay]

[http://www.vrmhub.net/ VRM Hub] is a series of monthly meetings in London.

Other meetings and workshops take place before and during [http://www.internetidentityworkshop.com/ Internet Identity Workshops] in Mountain View, California, each Fall and Spring. VRM is also a topic at [http://kynetximpactspring2010.eventbrite.com/ Kynetx Impact] conferences.

== ProjectVRM Participation ==

Sign up for the [http://cyber.law.harvard.edu/lists/info/projectvrm Project VRM mailing list]. You can also edit this wiki by signing up at the top of this page.[http://www.mightydesigners.com/ Logo Design Contest]|[http://www.customessayhelp.com/essay-help.html buy essay]

Personal Address Manager Service

2008-10-15T14:45:52Z

Tcarroll: /* Organizations/Movements */

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

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

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

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

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

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

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

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

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

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

[[image:PAM_Role_Map.png]]

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

===Organizations/Movements===
* DataPortability.org http://www.dataportability.org
* Microformats http://microformats.org
* Liberty Alliance Project http://www.projectliberty.org
* OpenLiberty.org http://www.openliberty.org
* 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

Personal Address Manager Service

2008-10-15T14:44:41Z

Tcarroll: /* 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===
===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

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

VRM Workshop 2008

2008-06-10T17:19:04Z

Tcarroll: Added Tom Carroll

The first ProjectVRM Workshop (tag [http://technorati.com/tag/pvrmw2008a pvrmw2008a]) will be hosted by ProjectVRM and the [http://cyber.law.harvard.edu Berkman Center], here at [http://harvard.edu Harvard University], on Monday-Tuesday 14-15 July.

We're thinking of calling it "Relacon", in the model of Bloggercon, the first of which was conducted by Dave Winer here at Harvard, in 2003. It was a good model for many unconferences that followed, incluidng the [http://iiw.idcommons.net/index.php/Main_Page IIW -- Internet Identity Workshop], an outstanding and highly productive workshop that has been happening twice a year since Fall 2005. VRM was a big topic at the last one, and perhaps the next one too. This VRM workshop is posed as the first at which the VRM conversation finally breaks off on its own from incubation at the IIWs.

The main purpose of the workshop is to work on development: moving code forward, and bringing existing code together. Also for the various committees to get together in physical space to move their work forward as well.

There won't be a cost to the event, but our budget is minimal, so basically what we'll be doing is making use of a small block Harvard classrooms at a time when school is out of session.

If you can come, please add your name to the attendee list. If working with a wiki is daunting for you (as it is for most people), please send me your name and I'll add it to the list. My email: dsearls AT cyber.law.harvard.edu

- Doc Searls

Attendee List:

[http://doc.searls.com Doc Searls] 
[http://www.mediainfluencer.com Adriana Lukas] 
[http://www.ichoosr.com Bart Stevens] 
[http://xri.net/=charles-andres Charles Andres] 
[http://land-com.net Dean Landsman] 
Iain Henderson 
[http://blog.joeandrieu.com Joe Andrieu] 
[http://xri.net/=jtrentadams/(+about) J. Trent Adams] 
[http://adrian.medcommons.net/ Adrian Gropper] 
[http://www.identitywoman.net Kaliya Hamlin, Identity Woman] 
[http://www.red-sweater.com/blog/ Daniel Jalkut] 
[http://www.socialcustomer.com Christopher Carfi] 
[http://2idi.com/contact/=mary.ruddy Mary Ruddy] 
[http://keithhopper.com Keith Hopper] 
[http://www.brucemacvarish.com Bruce MacVarish] 
[http://identity4all.blogspot.com/ Peter Davis] (tentative) 
[http://equalsdrummond.name/ Drummond Reed] ([http://xri.net/=drummond contact page]) (tentative) 
[http://www.xmlgrrl.com Eve Maler] (tentative) 
[http://www.parity.com/team.html#tom Tom Carroll] (tentative)