Date and Time

Date: Monday, October 12th, 2009

Time: 6:00 PDT | 9:00 EDT | 13:00 UTC

Attendees

Iain Henderson
Joe Andrieu
Eve Maler
Henrik Beiring
Mark Lizar

Minutes

The group did not reach quorum; this issue will be re-visited on next weeks call, by which time the member base will have self-categorised into Active and OBSERVER.

The group discussed and developed the Car Buying Scenario and worked through items 6 and 7 on the individual side. See below:

6. Relationship Maintenance (Data Quality and base level communications)

About one year after receiving her new car, Sally and her husband move to Oxford, a nearby town with a different dealer. Using her personal datastore, she informs her online vendors of her pending move, including the old auto dealer and Chryota, the manufacturer, as well as local council parking authority, and the Drivers & Vehicle Licensing Agency (DVLA), which gets an email from the personal datastore. On her dashboard, she can check to see which suppliers have confirmed receipt of the new information. Unfortunately, the DVLA doesn't respond. As a value-added service, her personal datastore provider offers an auto-generated PDF that Sally can print, sign, & mail to DVLA with the requisite information. At about the schedule time, Sally and her husband actually move and she checks in with the dashboard to both confirm the transition and to verify which vendors have her new information. Those vendors who are fully integrated with the personal datastore have electronically confirmed the new address. A few of the government agencies have requested a validated change of address, so Sally directs her personal datastore provider to provide the appropriate agencies with the Verified Change of Address (Identity and Data Assurance Level 2 - UK ... matches US level 3) see NIST 800-63 for related identity assurance standards.

7. Relationship Development

In response to her change of address, Chryota also notifies Sally, via her dashboard, that there is a new local dealer who might be more convenient. Sally does some quick research on the "new" dealer, who has a good trust rating and good comments from users. Sally accepts Chryota's recommendation and provisions the new dealer for access to her car's service and data record. Upon provisioning, Sally receives a welcome message from the new dealer with a brief outline of additional services now available (they weren't offered by her old dealer).

At the appropriate schedule, Sally's "digital dashboard" at her personal datastore provider reminds her of her maintenance appointments. She confirms the appointment online and drives in to the dealer and gets a ride back to work. Sally gets an SMS notifying her that the dealer has proposed work to be done. She logs into the digital dashboard and sees that the dealer has suggested--in addition to the planned maintenance - tire replacement because of a manufacturer warning. She does a quick search online about the notice, and decides she against it. The underinflation warning from the manufacturer is valid, but the community discussion groups (and the manufacturer) agree that most vehicles don't need to replace the tires if the vehicle is less than two years old. She informs the dealer to continue with just the scheduled maintenance. The vehicle assessment, her online research, and a record of all work done is stored in her personal datastore.

http://kantarainitiative.org/confluence/display/infosharing/Scenario+-+Buying+a+Car

Pushing forward on this scenario work will be the focus of the next few conference calls, aiming for presentation at the upcoming IIW event.

Iain agreed to draft a starting point for the ten scenario components on the vendor side.

Next Meeting
Date: Monday, October 19, 2009
Time: 09:00 PDT | 12:00 EDT | 17:00 UK (Time Chart)
Dial-In: Skype: + 9900827043671716; US Dial-In: +1-201-793-9022
Conference Room Number: 2954214

Browser not supported