[Wg-infosharing] Meeting Minutes, Teleconference on 19th Oct 2009

Iain Henderson iain.henderson at mydex.org
Thu Oct 22 02:01:52 EDT 2009


Hi Folks, here are the meeting minutes from the Information Sharing  
call on Monday 19th Oct.

Meeting minutes on the wiki, and reproduced below.

Next Meeting 26th October 2009

Time: 9am PDT | 12.00 EDT | 4pm UK time, 5pm CET

Note - as clocks are changing at different times in different places,  
we've decided to stick with USA time as the anchor - so 9am as usual  
for the West Coast'ers.

Dial-In: Skype: +9900827042954214
US Dial-In: +1-201-793-9022
UK Dial-In: +44 (0) 8454018081
Room Code: 2954214

Regards

Iain

MEETING MINUTES

Date: 19th, October, 2009 Time: 9 PDT | 12 EDT | 5pm UK.

Attendees

Iain Henderson (voting)
Trent Adams (voting)
Joe Andrieu (voting)
Mark Lizar (voting)
Eve Maler (voting)
Henrik Beiring (voting)


1. Quorum and Voting Having completed the process of allowing the  
group to self-describe as Voting or Observers, we noted that the 6  
people on the call were voting members and that the group had quorum  
on this call.

2. Previous Meeting Notes Having quorum in place, the group agreed to  
ratify all previous meeting notes for the record, those not having had  
any management of quorum, nor any significant policy decisions been  
made. All meeting minutes going forward will include management of  
quorum.

3. Car Buying Scenario

The group continued to work through the main car buying scenario,  
focusing on section 7 on the buyer side (Relationship Development).  
The concluding state of this work is shown below, and its development  
will continue on the next call.

7. Relationship Development

7a. 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).

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

7c Over the course of using her vehicle and getting it serviced, Sally  
learns about the Road Warrior program that the manufacturer offers to  
help customers who take frequent Roadtrips. She had heard about this  
on one of her favorite TV shows and it came up in her Twitter feed  
recently. She visits the manufactuer's website and signs up, pointing  
them to her personal datastore, and provisioning the manufacturer for  
access to her "roadtrip" travel dates and in-car location information  
for use by the Road Warrior Program. She requests "speed trap"  
notifications and construction alerts. She authorizes anonymized use  
of her usage data for civic planning and road maintenance and  
identified use for smart offers from her list of approved suppliers  
when she's in their neighborhood. Sally's unique ID in her driver's  
key logs her into the Road Warrior system. As she travels, occasional  
relevant notices appear, on the dashboard interface. Sally also has  
the pleasure of knowing her usage data is being smartly utilized in an  
anonymous fashion to help manage and develop the roadways. On her way  
home from a customer visit, Sally asks the Road Warrior Negotiator  
interface to find her a good spot to fill up the tank. The system  
analyzes her route and sends out a personal RFP to those stations  
within 1000 feet (1/5 mile). Those online respond with a customized  
bid for gas. For those not online, the Road Warrior system responds  
with their known pricing data [Q: where does this data come from today 
\?]. She picks one and a visit to that station is calculated into her  
route.

Questions:

[How does she pay and/or identify herself to the station, if at all?]  
On her drive, she stops and gets the gas... Another: husband has  
different road warrior preferences and doesn't want to be notified of  
the stuff she has.

Note for Data Sharing Agreement: Scope of what data When you get it  
What you can do with it

Iain Henderson
iain.henderson at mydex.org

This email and any attachment contains information which is private  
and confidential and is intended for the addressee only. If you are  
not an addressee, you are not authorised to read, copy or use the e- 
mail or any attachment. If you have received this e-mail in error,  
please notify the sender by return e-mail and then destroy it.




-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://kantarainitiative.org/pipermail/wg-infosharing/attachments/20091022/c62bfe1e/attachment.html 


More information about the Wg-infosharing mailing list