Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

Date

Apr 08, 2014

Attendees

Goals

  • Discussing Next Steps: What the 
    • 1.  a standard specification - a common structure for consents to create a consent receipt, based on a consent map that links the structure and questions to legal requirements,  

      - a consent map

      - A common receipt structure

      2. A way to provision receipts - (Open Source)

      3. A registry & proxy (registry): has to provide many functions: for - picking a personal cloud/device config,   A way to independently communicate. 

      4.  UX: We need a dashboard to manage pre- during, & post consent data - Consent receipt Reader to begin with. 

  • Trust Marks (our definition)  - They all use a consent model if they display a logo or Mark of some sort.  A mark is used for implied consent to provide assurance of the use of process and that can provide confidence to the user. 

Discussion Items

TimeItemWhoNotes
    

Action Items

  •  
  • No labels