Excerpt | ||
---|---|---|
| ||
It may be easiest to edit the incomplete links in the template text below in "wiki markup" mode. |
...
- 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 - Receitps are used to compare policy changes using TOSSOS
- TOS;Dr - Receipts are used to look up TOS;Dr rating
- Out of Scope
- Receipts are used to
Use Case: Demonstrator Scenario 1, Stage 1: Pre-Consent (Pending)
Submitted by: Mark Lizar
So far this looks like --> Scenario 1
- 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
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.
Scope of Work for Stage 1
- 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 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.
...