Information Sharing GROUP Teleconference

Date and Time

• Date: 8 Nov 2010
• Time: 7am HST | 9 PST | 12 EST | 5pm UK
• Please join my meeting via GoToMeeting
• Join the conference call:
  • Skype: +9900827042954214
  • US Dial-In: +1-201-793-9022
  • UK Dial-In: +44 (0) 8454018081
  • Room Code: 2954214
  • GoToMeeting ID: 844-771-298

Attendees

• Joe Andrieu
• Iain Henderson
• Judi Clark

Apologies

• Eve Maler

Agenda

1. Attendance
2. Prior Action Item Review
3. New Business
4. Update from IIW
5. Next steps on Information Sharing Agreements
6. Action Item Review

Minutes

1. Attendance

We noted that three people on the call were voting members and that the group did not meet quorum on this call.

2. Prior Action Item Review

• Judi: review minutes for ratified meetings, change titles accordingly.
• Joe: Add agenda item for next week re Trent and PR for those reports - LC didn't have quorum to approve, Judi is reworking Info Sharing, Iain questioned need for line numbers. Not officially approved as of today. Will check progress next week.
• Iain/Trent: update on OECD meeting - 3rd anniversary of when Privacy principles were established, five sessions relevant, two mentioned personal data stores, concept was well received. Iain has dialog with Ann Kavorkian, Ontario data commissioner, and past Australia data commissioner. OECD thinks they'll change their policy in next 2 years, don't know how yet (market moves quicker than they do). Judi suggested scenario planning techniques may help. Iain: empowerment over privacy. Joe: privacy leads to isolation and sand-boxing. Sharing without control is problematic.
• Eve: will send intros to Joe and Ian Glazer - DONE - Privacy Mirror (Facebook app) - simpler cousin to ISharedWhat.
• Eve will send a note to LC re: procedural hole -- what are LC operating procedures? Need clarification on LC approval process, lack of specificity and outcome once a doc was submitted to LC.
• Judi: final review of two drafts above - revising Info Sharing (as editor), not going to review second draft.

• Iain: write up about info sharing agreement about electoral role scenario - just starting. Looking for feedback for IP issues between MyDex and Kantara. MyDex is giving a right to Kantara to use, questions re: matching funds procedures.

3. New Business

•  none

4. Update from IIW

• Joe focused on getting ISharedWhat and info simulator launched, got good feedback on visualizing info being shared.
• AT&T will be launching a personal data store product in January 2011 (Will Laury), pushing for digital receipts. Iain: research at Sainsbury's 24 miles of paper receipts each week.
• Lots of sessions around personal data ecosystem. Sarah Dopp is part of Kaliya's work. In general, terminology remains a problem.
• Joe & Doc: what's "customer commons" in progress, framing the work is key.
• Kynetx had a good dev day, potential development there in open sourcing. PDS in cloud, authorization manager; a way to switch context from P2B login to B2P login. Kynetx rules engine pulls rules from other places. MyDex making their API available to Kynetx next week, good conversation.

5. Next steps on Information Sharing Agreements

•  Iain needs to get framing foundation down in wiki.

6. Action Items Review

• Judi: review minutes for ratified meetings, change titles accordingly.
• Judi: revising Info Sharing report.
• Joe: Add agenda item for next week re Trent and PR for those reports.
• Iain: write up about info sharing agreement about electoral role scenario,
• Iain will follow up with Lucy on procedures for last year's funds, with Joni for next year's funds
• Iain will get framing foundation into wiki re: Info Sharing Agreements

• Follow up LC re: procedural hole -- what are LC operating procedures? Need clarification on LC approval process, lack of specificity and outcome once a doc was submitted to LC.

Next Regular Meeting

15 November 2010
7am Hawaii, 9am Pacific, Midday Eastern, 5pm UK
Skype: +9900827042954214
US Dial-In: +1-201-793-9022
UK Dial-In: +44 (0) 8454018081
Room Code: 2954214

NOTE: Do not follow the code with a "#" symbol as it may cause the code not to be recognized.