Information Sharing GROUP Teleconference

Date and Time

• Date: 18th January 2010
• Time: 7 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 (voting)
• Judi Clark (voting)
• Trent Adams (voting)
• Iain Henderson (voting)
• Eve Maler (voting)
• Colin Soutar (voting )
• Mike Kirkwood (voting)
• Dervla O'Reilly (staff)

Apologies

Agenda

1. Attendance
2. Prior Action Item Review
3. Lexicon
4. New Business
5. Action Item Review

Minutes

1. Attendance

We welcome new participant Mike Kirkwood, Polka joining the group.

Robin Wilton and Michael Becker were removed as voting participants.

We noted that the 7 people on the call were voting members and that the group had quorum on this call.

Minutes were approved from Jan. 11 meeting.

2. Prior Action Items

• Iain: model for functional requirements doc

I suggest we use this model/ requirements listing that we initially evolved in the VPI Special Interest Group. It is already on the wiki, and starts off with a listing of the capabilities that would need to be built on the side of the individual in order to operate in the customer-supplier engagement framework (in Sally's position). As these were put together in mid 2009 we need to sense-check whether these need to be updated. We can discuss them, update them, and start to then use the rest of that sheet/ other columns to get into what existing tech might support the build/ deployment of these capabilities.

This is a good starting point, needs to be updated.

http://kantarainitiative.org/confluence/display/infosharing/VPI+Technology+Options+Draft+0.3

• Iain: Develop funding path (contract, direct project) with Brett, Kantara (email) by next meeting. To kick off, need to put info on wiki about what's already been done. List all groups working around legal/contractual info sharing space: P3, ID Commons, data portability, UMA, LC list. Need to create charter for sub-group (P3 moving in that direction, IIW also breaks into smaller chunks, informal UMA webinar theme). We're creating sub-committee w own sandbox & own deliverable.

Joe and Iain have agreed on the requirement for the proposed funding work and communicated that to Brett. The ball is with Brett to respond on whether this approach remains acceptable, and if so then we need to identify resource options that could undertake the work (building out the work currently being driven by volunteer effort).

Iain Henderson to follow-up with Brett McDowell

• Joe will create draft of charter and sandbox on wiki, will keep on same mailing list. Agreements Sub-Committee.

All to provide input to charter and sandbox on the wiki. The group will use the same the same mailing list.

The group will use the same bridge.

• Iain: ref. 10 vendor scenarios, after 1/22/10, Iain to schedule a realtime conversation to share the draft review when received from Mark Lizar.

3. New Business

4. Lexicon

Lexicon:

5. Action Item Review

• Iain to follow up with Brett McDowell regarding the funding path.

• All to provide input to charter and sandbox on the wiki. The group will use the same the same mailing list.

• The Standard Agreement Subgroup - use the same bridge for the group.

• After 1/22/10, Iain to schedule a realtime conversation regarding 10 vendor scenarios to share the draft review when received from Mark Lizar.

• Joe to draft an attempt of the shared information providing input from everyone

• Joe to update the Lexicon to simplify things. With private store, make sure it has sharing capability.

• Iain: ref. 10 vendor scenarios, after 1/22/10, Iain to schedule a realtime conversation to share the draft review when received from Mark Lizar.

Next Meeting

25 January 2010
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.