/
Weekly Meeting 2013 08 06 Notes

Weekly Meeting 2013 08 06 Notes

Aug 06, 2013

Information Sharing Work Group Teleconference

1 Date and Time | 2 Attendees | 3 Apologies | 4 Agenda | 5 Minutes | 6 1. Attendance | 7 2. Motions | 8 3. Prior Action Item Review | 9 4. Continuing Business

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

  1. Attendance

  2. Approval of Prior Minutes & Other Motions

  3. Prior Action Item Review

  4. Continuing Business

    1. Survey

    2. Rechartering

  5. New Business

    1. Simplified Label

  6. Action Item Review

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

  1. Shared Data

  2. Data Source

  3. Data Recipient

  4. Location

  5. Contact

  6. Purpose

  7. For How Long

  8. Output To

  9. Revocation

  10. Redistribution

  11. Access

  12. Additional Terms

  13. Related Agreements

  14. 3rd Party Ratings

  15. Author

What is highest priority?

  1. Who wants it? Data Recipient

  2. For What? Purpose

  3. What do they want? Shared Data

  4. Can I unshare?

  5. What do others say? 3rd Party Ratings

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

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

  8. Related 

    1. Additional Terms

    2. Applicable Policies

    3. Related Agreements

  9. Label Author

 

Ways a label can be authored.

  1. Just the user and the RP. (Web form) "I want to know more"  Label data provided by RP

  2. Data store, e.g., Facebook, user and RP. Facebook provides Label data (or equivalent).

  3. Broker service. Datastore -> Broker || permission interface with user || Broker -> RP.  Broker provides the label data.

  4. Label service. Source -> RP. Label source plugin provides out-of-band label data.

  5. App Store integration. AppStore gets data from RP, show label to user.

  6. App integration, with in the app. Data from RP.

There are two primary use cases:

  1. The RP is proactive

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