| Excerpt | ||
|---|---|---|
| ||
It may be easiest to edit the incomplete links in the template text below in "wiki markup" mode. |
Abstract
This document is a product of the CISWG Work Group. It records the scenarios and use cases governing the development of consent receipt and guiding associated implementations and deployments.
A Scenario specifying a receipt data schema
Status
| Excerpt | ||
|---|---|---|
| ||
Generating a change history automatically is handy because it's hard to capture the link to a saved revision and then put the link at the top of the document (making yet another revision!). But if the change history gets too long, you might want to delete it, make occasional PDF snapshots and attach them to this page, then link from this Status section to a short list of each new snapshot. |
This document is currently under active development. Its latest version can always be found here. See the Change History at the end of this document for its revision number.
Editors
Mark Lizar
Intellectual Property Notice
The CISWG Work Group operates under Option ABC and the publication of this document is governed by the policies outlined in this option.
...
Table of Contents
| Excerpt | ||
|---|---|---|
| ||
You can find help on this macro at http://kantarainitiative.org/confluence/renderer/notationhelp.action, under Confluence Content. |
| Table of Contents | ||||||||
|---|---|---|---|---|---|---|---|---|
|
...
Introduction and Instructions
This document is a product of the CISWG Work Group. It records the scenarios and use cases governing the development of the Consent Receipt Schema (CRS) and guiding associated implementations and deployments.
...
Edit the descriptions of technical issues and scope questions to reflect (or point to) group decisions about how to handle them.
...
| Anchor | ||||
|---|---|---|---|---|
|
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.
Background Not unlike a
Economic Performance:
A receipt you get when you buy something , which you then submit for 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. Like costs. 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. Better
Experience
Better managed preferences result in better user experience.
...
Governance:
A receipt can also be used for governance, for instance, the Tax authorities can use a 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 change provided and the receipt against the price advertised to make sure of compliance.
...
- Pre-Consent
- a website/server with form for a company to generate a legal.txt file
- Publishing legal.txt
- An embed code is created for company to put behind their consent buttons on the website
- Consent
- A service user selects the consent '+ receipt' option to collect a receipt
- The id used by the service user to provision consent is used to send the receipt.
- With no pre arranged application, a modal box will appear asking for slection of identifier to use with the receipt
- this could be social login, email, etc
- the receipt is then accepted and stored by the digital identity being used for the consent
- With no pre arranged application, a modal box will appear asking for slection of identifier to use with the receipt
- The id used by the service user to provision consent is used to send the receipt.
- A service user selects the consent '+ receipt' option to collect a receipt
- Post - Consent
- TOSSOS - Receipts are used to compare policy changes using TOSSOS
- TOS;Dr - Receipts are used to look up TOS;Dr rating
- Out of Scope
- Browser Plugin - Receipts are captured and used automatically to make policy responsive and to customise experience, reduces steps in stage 2. streamling user experience.
- Would require a receipt viewing capability, preferably on aggregate and current view as well. (by identity would be useful too)
- Browser Plugin - Receipts are captured and used automatically to make policy responsive and to customise experience, reduces steps in stage 2. streamling user experience.
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.
...
- Focus first on creating a legal.txt file with the existing schema
- Create webpage with Minimum Viable Consent Form
- Create Legal.txt
- Publish Legal.TXT
- Create Embed Code for Consent to be used by other organisations
- Optional
- Create a Common Terms option on first page for use in creating legal.txt file
- link existing policies to layered notice
- Create a Common Terms option on first page for use in creating legal.txt file
Use Case: Demonstrator Scenario 1, Stage 2: Consent (Pending)
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
-
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.)
...
| Anchor | ||||
|---|---|---|---|---|
|
| Change History |
|---|