Request for new section 6.3 How a Verifiable Credential may be issued within a process

[RieksJ]

Section 6.1 describes a generic process flow in which users can go to a web-site, request a credential, and obtain one (or not).

However, it is very useful to also have a user sequence that is initiated by a Service Provider (SP) website, that offers the generation and issuance of a credential in which, e.g., the current status of that process is being asserted. Some examples:

• a user applies for a parking license (physical piece of paper); the SP can immediately decide that it will provide one, but it will take 3 weeks to produce it and deliver it. The SP can then offer the user to issue a credential stating that the parking license is forthcoming, so that if the user gets a parking ticket, (s)he would not need to pay a fine.
• a user that is browsing at an SP, just to see some status of an order, or the data that the SP has on her, may be offered VCs of various types that the SP would be willing to issue in case the usere were interested.

The flow would go something like this:

1. Jane browses to the website of SP
2. SP offers to issue a VC of specific kinds (e.g. by presenting a QR code)
3. Jane may choose to use her user agent to obtain one or more of such VCs (e.g. by scanning a QR code, or clicking a button with a deep link)
4. SP generates the credential (no need to do the entire provisioning as per New user/issuer task - Provide Claim #141, as the 'access control' part thereof has implicitly been taken care of), and issues it to Jane's user agent.
5. Jane accepts the received VC (implicitly or explicitly)