GDPR Extension

[smartopian]

Harsh has helped me pull together a spreadsheet to help align the CRv1.1 with the GDPR Extension

https://docs.google.com/spreadsheets/d/1OPIuYdaTLqIQforseLS4YY0RDxy4gYoYF55sVbTp2PQ/edit#gid=0

Also, we can discuss as an option, drafting an update to the CR v1.1 with the GDPR extension updated terms and addition as a really quick and easy way to get a new base draft for addressing comments below. I suspect many of the issues to be addressed.

[iainh1]

Mark, it’s not that clear to me the big picture of where we are with Consent Receipt spec and the various versions. Do we have a marketing document anywhere that summarises the current approved version, and then the proposed evolutions? Thanks Iain

…

On 11 Jul 2019, at 11:36, Mark Lizar ***@***.***> wrote: Discuss as an option, drafting an update to the CR v1.1 with the GDPR extension updated terms and addition as a quick way to get a new base draft for addressing comments. Link to CR_Ext. (coming soon) — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub, or mute the thread.

[smartopian]

Hi Iain, We do not have anything like that. But, this would effectively be summarised as an update from the minimum consent receipt to a full consent receipt spec that works for the GDPR and (in theory) all other jurisdictions.

…

On 11 Jul 2019, at 13:05, Iain Henderson ***@***.***> wrote: Mark, it’s not that clear to me the big picture of where we are with Consent Receipt spec and the various versions. Do we have a marketing document anywhere that summarises the current approved version, and then the proposed evolutions? Thanks Iain > On 11 Jul 2019, at 11:36, Mark Lizar ***@***.***> wrote: > > Discuss as an option, drafting an update to the CR v1.1 with the GDPR extension updated terms and addition as a quick way to get a new base draft for addressing comments. > > Link to CR_Ext. (coming soon) > > — > You are receiving this because you are subscribed to this thread. > Reply to this email directly, view it on GitHub, or mute the thread. — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub <#122?email_source=notifications&email_token=ABR6VZZY7PH7VLFP2RBVO2DP64O2BA5CNFSM4IA7JAD2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZWPQZY#issuecomment-510457959>, or mute the thread <https://github.com/notifications/unsubscribe-auth/ABR6VZZZSA7DMBNYNI5ZAR3P64O2BANCNFSM4IA7JADQ>.