Page Comparison

...

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 selection 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. streamlining 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 (In Progress)

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. 

...

• Optional
  • Create a Common Terms option to layer policies for different consent context. e.g. mobile phone, physical location, online service 
  • Option would be on first page for use in creating legal.txt file and would demonstrate the ability to create certified data sets
    • link existing policies to layered notice

Image RemovedImage Added   

• Create Legal.txt

...

1. Consent
   1. 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. 
      1. 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) 
   2. 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 selection 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 of choice

 Image Added

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

1. 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. streamlining user experience. 
         1. Would require a receipt viewing capability, preferably on aggregate and current view as well. (by identity would be useful too)

Issue: unique-title

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

...