Page Comparison

...

The goal of this scenario is to create a specification for a receipt schema and a demonstrator for creating, providing and using a minimum viable consent receipt. 

Background

 Not unlike a receipt you get when you buy something, which you then submit for a third party, either to show a budget and costs, or to report on what was purchased and for how much.   Like costs, consents can be counted, and like purchasing preferences, consent preferences collected.  Better managed preferences result in better user experience. 

...

1. Create a consent receipt generator, --> Common Terms, Legal.TXT
2. Create a consent receipt button,  --> Embed Code, publish legal.txt
3. Provision a consent to a service user
4. Service user, uses the receipt  to achieve the use case specified.  

The demonstrator includes 3 stages, 1. Pre-Consent, 2. Consent 3. Post-Consent

1. Pre-Consent
   1. a website/server with form for a company to generate a legal.txt file
   2. Publishing legal.txt
   3. An embed code is created for company to put behind their consent buttons on the website
2. Consent
   1. A service user selects the consent '+ receipt' option to collect a receipt
      1. The id used by the service user to provision consent is used to send the receipt. 

...

1. 1. 1. 1. With no pre arranged application, a modal box will appear  asking for slection of identifier to use with the receipt
            1. this could be social login, email, etc
         2. the receipt is then accepted and stored by the digital identity being used for the consent
2. Post - Consent

Use Case: Demonstrator Scenario 1, Stage 1: Pre-Consent (Pending)

Submitted by: Mark Lizar

So far this looks like --> Scenario 1

Pre-Consent 

- Common Terms - links existing policies to consent fields and semantics 

...