Excerpt | ||
---|---|---|
| ||
It may be easiest to edit the incomplete links in the template text below in "wiki markup" mode. |
...
- Consent
- The org, who has generated a LEGALS.TXT and embed code, cuts and pastes the code, which links to the LEGALS.TXT, file and adds it to the code in the current consent option that exists on the website.
- We can generate three different types of buttons. (I agree button, Check box opt-in, I have read and understand terms and service - but with the receipt option)
- 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 selection 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 of choice
- With no pre arranged application, a modal box will appear asking for selection of identifier to use with the receipt
- The id used by the service user to provision consent is used to send the receipt.
- Including Data in the Receipt for the recipient
- This should include all reasonable elements that can be captured at that point and provided in a receipt format.
- DNT Header, URI links for privacy or terms, IP Addresses, (full list is pending). As well as a counter.
- This should include all reasonable elements that can be captured at that point and provided in a receipt format.
- The org, who has generated a LEGALS.TXT and embed code, cuts and pastes the code, which links to the LEGALS.TXT, file and adds it to the code in the current consent option that exists on the website.
Scenario 1: Part 2
Scenario 1: Part 2: A
Scenario 1: Part 2 : B -Digital Identity
Scenario 1 Part 2: C
Scenario 1 Part 2
...
...
:: D - Consent Receipt View
Scenario 1 Part 2: Consent Summary (on Aggregate) View : (Note this is currently out of scope of this Scenario)
Use Case: Demonstrator Scenario 1, Stage 3: Post-Consent (Pending)
- 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. streamlining 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. streamlining user experience.
Scenario 1; Part 3 Wire Frames - (in Progress Through Stage 1 & 2)
Issue: unique-title
(Provide technical commentary on the issues brought up by this use case.)
...
Anchor | ||||
---|---|---|---|---|
|
Change History |
---|