Date

May 20, 2014

Attendees

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

Notes/Things to address

Implied or Implicit consent
- John suggest that we create space for implied consent in the original spec so that we can further extend the same spec in the future.
- Mark suggested that the URL (location of data controller) be defined as location of consent so that this could be the URL of the consent option and in the future be useful for location of physical spaces with policies/notices that equate to implied consent.
- Discussed extending section 2 with ( E & I) E for explicit, I for implied, and that we leave implied open, as for physical location we can make a PLocation field in the header, but leave this blank
A separate section for Capturing the consent preferences from the user in the consent session
- e.g. DNT (at the moment this is in the header, but should this be moved to a section 4? A report section of the receipt ?

Discussion Items

Time	Item	Who	Notes