...

Edit the descriptions of technical issues and scope questions to reflect (or point to) group decisions about how to handle them.

...

Anchor
scenario-template scenario-template

Scenario:

...

Minimum Viable Consent Receipt (Pending)

Submitted by: Mark Lizar

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. 

...

Economic Performance of Consent:

A commercial receipt you get when you buy something received at point of purchase has many uses, it can be submitted to a third party, either to show a budget and costs, or to report on what was purchased and for how much.  It is a great tool for reducing friction, saves time, money.  Like a transaction receipt, consents can also be submitted to a third party, it can be compared, counted, and like purchasing preferences, consent preferences can also be collected.  

Experience of Consent

Hypothesis: Better managed preferences result in better user experience.  

Governance of Consent:

A receipt can also be used for governance, for instance, the Tax authorities can use a commercial receipt to check and see if the sales are hidden, the purchaser can use a receipt to be sure of the cost of goods and compare the currency change provided and the receipt against the price advertised to make sure of compliance.  

...

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 post consent  to achieve the use case specified.  

...

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. 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
3. Post - Consent
   1. TOSSOS - Receipts are used to compare policy changes using TOSSOS
   2. TOS;Dr - Receipts are used to look up TOS;Dr rating
   3. Out of Scope
      1. Browser Plugin - Receipts are captured and used automatically  to make policy responsive and to customise experience, reduces steps in stage 2. streamling user experience. 
         1. Would require a receipt viewing capability, preferably on aggregate and current view as well. (by identity would be useful too)

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

Submitted by: Mark Lizar

The primary focus is to create the first legal.txt (which I think at the time of this writing is already done) and develop a process for an organisation to distribute a consent receipt. 

...

• Notes: 
  • Exploring a Common Terms approach to layer policies for different consent context. e.g. mobile phone, physical location, online service 
    • based on existing standards and best practices
  • Option would be on first page for use in creating legal.txt file and would demonstrate the ability to create context specific consent receipts. 
    • link existing policies to layered notice
• Thought/Discussion Needed:
  • Publishing, 
    • where should legal.txt be published? (multiple places?)
    • How will/can people get and use their receipts? 
      • A list of use cases
        1. compare TOS or Privacy policy for changes
        2. retrieve TOS;Dr reputation 

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

...

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

The consent rec

Issue: unique-title

(Provide technical commentary on the issues brought up by this use case.)

...