Date
May 20, 2014
...
- Consent Receipt Spec Intro Dev and review - 10 min
- review and further develop intro to the specification - 15 min
- Define Terms - Michiel v. John terms - review the terms and approaches by both
- Tech Task - Create this Specification in a CISWG Git Hub Page (with the CISWG License) (note: email sent to Oliver to do this)
- Link spec to CISWG wiki (how should we do this?)
- Plan the next steps to creating the specification and developing a working demo
Introduction to the
...
Consent Receipt Specification v.01
The purpose of the MVC specification (or the consent receipt header) is to standardise the recordation of consent and the collection of consent specific policy links. As well as to make standard a link to withdraw consent.
The first section (or header) of the consent receipt provides the basic needed information to record that a consent
was providedconsent provision, and the policies under which it was provided. This header is what we have called in the past the MVC.
The second part of the consent receipt is intended to draw out (from the policies) the minimum legal (or common) legally required notice requirements for consent and to display or link to these in the policy. Either by with a direct link to the policy section with the legal notice requirement and the relevant section or by scraping the policy and entering it here. All of the notice requirements for consent by jurisdiction and industry are to found in a reference document called the "Consent Notice Map". (needs link)
...
- Implied or Implicit consent (
Discussion Items
| Time | Item | Who | Notes |
|---|---|---|---|
Action Items
...