Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

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.

...

Terms in the Receipt So far (from Hack May 10) MVC Receipt
--Timestamp
--UserID
-- Location & - ( Consent DialogUrl: (the url of the consent dialog)
-- DNT header (true; false)Plocaton - (NA) 
--Revoke consent URL

--Policy URLS that have a been agreed to
--Json signature

  • Domain URL (owner of consent)Preferences Captured from User

 

Section 2: (I for implied and E explicit)  (implied and explicit consent) 

...

(From work to date)

 

 

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

TimeItemWhoNotes
    

Action Items

...