Information Sharing Work Group Teleconference

Date and Time

Tuesday, Jul 23 : 4:30pm PDT, 7:30pm EDT
Wednesday, Jul 24 : 12:30am UK, 9:30am JT, 11:30pm NZDT
Please join my meeting via GoToMeeting

Join the conference call
- Skype: +99051000000481
- US Dial-In: +1-805-309-2350
- UK Dial-In: +44-20-3137-5285
- Conference ID: 178-2540
- GoToMeeting ID: 844-771-298

Attendees

Joe Andrieu
Lionel Klee

Apologies

Colin Wallis

Agenda

Attendance
Approval of Prior Minutes & Other Motions
Prior Action Item Review
Continuing Business
1. Survey
2. Rechartering
New Business
1. Simplified Label
Action Item Review
Next meeting schedule

Minutes

1. Attendance

We noted that with 2 of 4 voting members in attendance, quorum was not met.

2. Motions

None

3. Prior Action Item Review

4. Continuing Business

Survey

Suspended indefinitely. We learned a lot in the process that we can apply right now to the label. But we don't have the resources or manpower to engage in a proper study.

Rechartering

Need input from Mark.

5. New Business

Revisions

Which fields can we get rid of? Then, what can we revise in terms of language?

Keep, Combine, Fold, Cut

Shared Data
Data Source
Data Recipient
Location
Contact
Purpose
For How Long
Output To
Revocation
Redistribution
Access
Additional Terms
Related Agreements
3rd Party Ratings
Author

What is highest priority?

Who wants it? Data Recipient
For What? Purpose
What do they want? Shared Data
Can I unshare?
What do others say? 3rd Party Ratings
About the recipient (below the fold/behind the tab)
1. Location
  1. Legal entity
  2. Data Storage & Use
  3. Legal jurisdiction
2. Contact
  1. Disputes
  2. Support
  3. Questions
Data management (below the fold/behind the tab)
1. Data Source
2. Outputs
3. Redistribution
4. Access (View the data)
5. Revocation (action)
6. Persistence
Related
1. Additional Terms
2. Applicable Policies
3. Related Agreements
Label Author

Ways a label can be authored.

Just the user and the RP. (Web form) "I want to know more" Label data provided by RP
Data store, e.g., Facebook, user and RP. Facebook provides Label data (or equivalent).
Broker service. Datastore -> Broker || permission interface with user || Broker -> RP. Broker provides the label data.
Label service. Source -> RP. Label source plugin provides out-of-band label data.
App Store integration. AppStore gets data from RP, show label to user.
App integration, with in the app. Data from RP.

There are two primary use cases:

The RP is proactive
The RP is passive

Either the RP or the user must be proactive. If we can define a label that works in both situations, we're good. We just have to find the connection between the two.

6. Action Items

7. Next Meeting

Tuesday August 13 : 12:30 pm PDT, 3:30pm EDT, 8:30pm UK,
Wednesday August 14 : 4:30am JT, 7:30am NZT
60 minutes

Browser not supported