Information Sharing GROUP Teleconference

Date and Time

• Date: 18 Oct 2010
• Time: 6am HST | 9 PDT | 12 EDT | 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
• Judi Clark (non-voting)
• Eve Maler
• Iain Henderson

Apologies

Mark Lizar

Agenda

1. Attendance
2. Prior Action Item Review
3. New Business
4. Information Sharing Agreement
5. Action Item Review

Minutes

1. Attendance

We noted that 3 people on the call were voting members and that the group DID meet quorum on this call. Eve moved to approve Oct 4 notes, Ian seconded, motion approved.

2. Prior Action Item Review

• Kantara reports: in Kantara format, Renee has not sent comments, blog no longer relevant
• Kalia's Personal Data ecosystem: needs to be inclusive, no clear governance (no details); Kaliya is thinking about these things.
• Iain: Update on TBS proposal: main focus to turn to info sharing agreements
• All: Please blog about these reports! (About the call for comments)
• Trent: Touch base with marketing committee (9/28/2010) about PR for reports

3. New Business

Iain noted that UK efforts are picking up steam, last week announced diff orgs involved. Technical side beginning in Nov.

UMA is holding a meeting at IIW, resource registration (informing authorization manager) this week, more specificity in scenarios (current oAuth non-restful). New bounty program to be announced to encourage structured help.

Budgeting?

4. Information Sharing Agreement

Context: Individual has info that may be used by an organization, no agreement exists today. Example would be helpful to demonstrate--car buying scenario or real life example from Mydex, possible hybrid? E.g, Electoral role (can we vote): individual moves to an area, contacts local council, initiates process to register to vote (usually F2F), that info finds its way into credit bureau and marketing service providers. Problem: is an old, leaky system, no visibility of process. Tick box: I will allow my info to be used for marketing purposes. Individual's role doesn't appear in records for 3 months -- that's how long it takes to process. How does whole country update with change of address? If there's an info sharing agreement with local council, data can submit with high level of assurance, processed more efficiently, confirmed with individual promptly and can be used elsewhere. Quicker and cheaper. Personal attribute in data store: can share under their conditions. Technology + Agreement.

Info sharing agreement: individual, sharing verified info about address, created jointly w council, giving it to other players (here, BT). Conversations will happen over next 6 weeks. BT can then provide another token back to individual for relationship (verified attribute).

What do recipients need on Council side? Council will be fair, they want the change, electoral role records are public. Negative forces: language is a barrier. How does this consensus building forum contribute to the process? Advisory role. Existing prototype agreement? Not yet, working with variable options for testing. After write-up next week, that may end up with different agreement than what's in the field.

UMA: is it a P2P, P2self, P2service. Do they have a login at Council? No presence now, would be a P2service sharing service, needs to be provisioned with representative data (persistent URL?), protection needs to be in place, perms & policies to collect, login & approve, allowance policies. This scenario will be helpful to UMA too.

Technical roll-out: does council have own system that will provisioning? Council has current data, will verify individual's data, host & authorization manager will be Mydex. PDS (personal data store) some data, sep service for managing that and other data. PDS assumes perfect ownership, overstates case (data as content (photos?)), but not a natural way to talk about it. Personal data isn't meta, it's web content; not same as delivering calendar data as personal representation. Not about being identity attributes. Releasing, adding, serving, storing data. Not same as PII like status update. Personal meta-data is what's important in our conversation.

Our conversation is more like librarians than authors. Others (content-side) are creating the stories, but meta-data is about usability, reference and connection.

Iain moved to use electoral role scenario for our work moving forward, Eve seconded, motion carried.

5. Action Items Review

Joe will submit final proposed draft for group vote on Kantara Reports

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

Next Regular Meeting

25 Oct 2010
6am 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

Next Standard Agreement Meeting

TBA
6am 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.