...
The user wants to be able to carry a collection of credentials with them that can give then access to physical locations as well as digital assets. The user needs to believe that they are in control of the release of their information and that the information will be handled security once released. The function of the holder's platform must include the acquisition, display, protection and creation of a presentation of the appropriate user attributes to the verifier. The holder must be able to trust the platform to protect their interests. The issuer must be able to trust the wallet to follow their policies, the verifier must be able to trust the platform to prove that presences and ownership of the presented attributes of a real-world human user of the platform. In addition the platform might be required to prove "liveness" of thee the real-world human at that the time that the presentation was made.
...
The user caries back-up documents that can be used when the digital ecosystem is non-functional.
Actors
| Actor | Role in the use case |
|---|---|
| Holder | The human user of the mobile credentials. The first person (I, we) of this story. |
| Device | A smartphone or other mobile computing device including the operating system (OS) software. |
| Wallet | An application running on the OS that has access to protected storage on the device. Often called a native app. |
| Issuer | of a mobile credential. |
| Verifier | of one or more mobile credentials. |
Taxonomy
| Term | Definition |
|---|---|
| Credential | A protected structure given by the issue to the holder's wallet. For example the mdoc from ISO 18013-5 |
| Presentation | A protected message given by the holder's wallet to the verifier. It will contain only that user data that is needed for the purpose of the transaction. |
| Purpose | A structured list of attributes and the retention permissions from some trusted authority. For example the US TSA list of attributes needed to enter an airport. |
User Stories
| Element | Detail | Notes | ||||
|---|---|---|---|---|---|---|
| As a, | human user | Typically this is the holder of the credentials. | ||||
| I want | access | to either a real-world or a digital resource | ||||
| so that | I can complete whatever task that currently has my attention. | without cognitive dissonance. | ||||
| Acceptance Criteria | ||||||
| Given | The user has a modern smartphone that comes with, or has installed, a wallet application that holds modern mobile credentials. | Laptops also will work, but the smartphone limitations are more germane to this use case. | ||||
| When | I start any task that requires identity credentials. | or when I start planning for future needs. | ||||
| Then | I consider the credentials I might need to complete my task. This is typically on a website that tells me how access is granted. | The user should not need much special knowledge to complete this step. | ||||
| As Needed | I migrate to an issuer web site using either the browser or the wallet, as appropriate to acquire new credentials. | |||||
| Fall back | I can scan some credentials from hard copy for entry into the secure store along with the fully digital credentials. See video for example. |
| ||||
...