...

This document is a product of the XXX CISWG Work Group. It records the scenarios and use cases governing the development of XXX and guiding associated implementations and deployments.

...

Anchor
scenario-template scenario-template

Scenario: unique-title (Pending)

Submitted by: participant-name

...

 Mark Lizar

The goal of this document scenario is to help create a specification for a standard receipt schema and a demonstrator for creating, providing and using a minimum viable consent receipt. The demonstrator and scenario will aim to produce a specification for the data schema of consent receipt.  The demonstrator will illustrates the receipt and its use. Once completed we will finish drafting the specification and explore its utility.  

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 aim here is to

Intended Use

Use Case: unique-title Demonstrator (Pending)

Submitted by: participant-name(Provide description of a use case matching this scenario with all technical particulars, such as the topological configuration of protocol endpoint entities, listings and assessments of technical issues, and anything else helpful.) Mark Lizar

So far this looks like --> Scenario 1

Pre-Consent

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

- This creates an embed code that is put behind a consent button,

- this publishes legal.txt to a common place - (Open Notice database)

Consent

When a consent is provisioned using the button 

- a receipt is created  at the point of consent, the identity used to provision the consent is used to deliver the consent receipt

-  

Post Consent

- the initial consent is used to identify the parties and collect the preferences and options available, From companies this may be. marketing materials, items on sale, etc.  For people, this may be do not track, proof of age, etc. 

Issue: unique-title

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

...