Page Comparison

...

To achieve this, use cases have been suggested: 

1. What was unfinished in v1.1. (update to v.1.2 ) 
2. legal notice as an identity governance framework: a consent notice receipt and consent withdraw (v1.2)
   1. Life Cycle of a Consent Notice Receipt 
   2. Delegation of liability and risk between stakeholders
   3. A notice and notification requirements doc for the V2
3. Privacy as Expected: Active state UI  - 2FC (two factor notice for identity management permission grants)
4. Binding: UMA Protocol in a Consent Notice Receipt

Unfinished in the Consent Receipt - V1.1 

1. The consent receipt was written in conjunction with comments to ISO/IEC 29184 Online privacy notices and consent,  this standard providing online notice requirements for privacy and security techniques.  (this is now published July 6, 2020)
2. The onbehalf field was used in multiple different contexts and reflected out of date UK Data Protection Act language.
   1. GDPR provided needed updates and requirements for consent record structure and specification: (see GDPR extension)
      1. Delegation of risk and liability between stakeholders,
3. PaE: NoticePrivacy as Expected - A transparency risk UI,  Notice, a public governance framework UI for purpose driven surveillance transparency (or Active State idEntity governance)
   
   1. notice receipt, for any legal justification : consent notice record +
   2. privacy agreement for consent by design
   3. contract notice receipt : an international transparency baselinefor every consent