Personal Address Manager Service

This Standard is being developed according to the VRM Use Case guidelines.

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

Status

Working Draft

Schedule

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 postal address 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

Addressee

Anyone who use a postal address as a point of contact.

Addressor

Anyone who wants to reach an Addressee at their postal address.

AddresseeDelegate

Anyone authorized by an Addressee to act on their behalf. Specializes Addressee.

AddressorDelegate

Anyone authorized by an Addressor to act on their behalf. Specializes Addressor.

AddressRequester

Individuals or organizations who request a postal address on demand for either immediate or perpetual use. Specializes Addressor.

AddressSubscriber

Individuals or organizations who subscribe for updates to an individual's address. Specializes Addressor.

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.

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.

Addressee

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

Addressee Delegate

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

Addressor

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

Addressor Delegate

• Anyone authorized by an Addressor 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 Addressees and Addressors.

AddressRequester

• Specializes Addressor
• 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 Addressor
• 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 Addressee Manages Address
1.1 Addressee Creates Address 
1.2 Addressee Reviews Address
1.3 Addressee Changes Address
1.4 Addressee Deletes Address

2 Addressee Manages Addressors
2.1 Addressee Uploads Addressors
2.2 Addressee Authorizes Addressor
2.3 Addressee Manages Addressor Permissions 
2.4 Addressee Deletes Addressor

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

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

5 Addressor discovers Personal Address Manager service for Addressee
6 Addressor Requests Authorization
7 Delegate requests authorization
8 AddressRequester Requests Current Address
9 AddressSubscriber Activates Subscription
10 AddressSubscriber Deactivates Subscription
11 Addressee Accesses Activity Log
12 Addressor reports address change
13 Addressee acknowledges address change
14 Addressee downloads data
15 Addressee authorizes automated export
16 Addressee creates account
17 Addressee deactivates account
18 Addressee 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:

1. Why the actor is engaged in this use case? What happened? What motivated them to contact the system and begin the transaction?
2. What does the actor do? Identify the keys actions taken by the actor during the use case.
3. 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 Addressee Manages Address

Scenario 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 Addressee Creates Address

Specializes Use Case 1 Addressee Manages Address

Scenario 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 Addressors and sends a confirmation email to Bob. (Bob's next action is likely to be one of the variations of Use Case 2 Addressee Manages Addressors)

Scenario 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 Addressors who specifically ask for Betty's "Mom's Address". Betty's next step might be Use Case 2 Addressee Manages Addressors or she might just wait until she is purchasing an item that she wants to ship to Mom before authorizing any Addressors.

Use Case 1.2 Addressee Reviews Address

Scenario 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 Addressors. The address is correct, so she does nothing further. (If it was incorrect, the next step is likely Use Case 1.3 Addressee Changes Address

Use Case 1.3 Addressee Changes Address

Scenario 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 Addressors, he likely goes to one of the variants of Use Case 2 Addressee Manages Addressors.

Use Case 1.4 Addressee Deletes Address

Scenario 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.1 Addressee Uploads Addressors

Scenario 1 Bob uploads Outlook File

Bob just created his account and wants to load all of his contacts in his Outlook contact database as Addressors. 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 Addressee Authorizes Addressor

Scenario 1 Real-time authorization request

Betty is at the website of a Vendor who she wants to set up as an Addressor. She tells the Addressor to use her PAM. The Addressor finds the PAM and requests authorization as a AddressRequester, redirecting Betty to the PAM interface for authorization. The PAM verifies the Addressors 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 Addressor should be authorized for the specified access. The PAM redirects back to the Addressor so that Betty can continue her transaction.

Scenario 2 Email request (fulfilled via real-time authorization started at Addressor'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 Scenario 1 Real-time authorization request

Scenario 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 Addressee Manages Addressor Permissions

Scenario 1 Frank switches all of his Addressors to AddressRequesters

Frank is a long time PAM user and has decided that Addressors 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 Sally changes a trusted Addressor'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 Addressor's Permissions, authorizing access to her home address in addition to the work address already authorized.

Scenario 3 Betty changes a trusted Addressor's permissions (triggered at Addressor'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 Addressee Deletes Addressor

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 Addressee, 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 Addressor and records the change in the log.

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.

Addressee Changes Address

User Intention	System Responsibility
1. Addressee decides to move.
2. Addressee expresses new address to system (optionally including scheduling information).
	3. System assures Addressors 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.

1. Address stored independently of any particular service provider
2. Addressee can choose who stores canonical source (self-storage ok)
3. Data should be in an open format and portable without data or service loss
4. Data transfer and use is always under user control
5. Addressors can discover the appropriate CoA service for each user

Policy Requirements

Implementations must meet the following policy requirements.

Administration & Operations

1. Specified Data Visibility--Service providers must specify and implement either a visible of invisible data strategy.
   1. Visible Data - Data stored with the Service provider is visible to administrators.
   2. Invisible Data - Data stored on the Service is encrypted and not visible to administrators.
2. 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.

1. Privacy
2. Security
3. Survivability
4. Accountability

Note: these areas need to be more clearly and completely specified. See the [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
• CardSpace http://www.microsoft.com/net/cardspace.aspx
• 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

1. Representing an address (machine readable)
2. Presenting an address (human/postal service readable)
3. Personal Address Manager metadata
   1. Address Metadata
      • Address Name
   2. Authorizations
   3. Log data

We will need protocols for

1. Authenticating Addressees, Addressors, and delegates
2. Authorizing Addressors & Delegates
3. Service discovery
4. Inbound human services
   • most likely web pages
5. Inbound automated services
6. Outbound automated services
   • email