Page Status: DRAFT
Priority: P2
Description (User Story)
We want to establish a platform of principles to ensure the integrity, safety and privacy of our identity product.
Our goal is to create a trusted identity presentment experience that aligns with our core privacy tenants of minimization, control, transparency and security. These efforts foster trust across the entire ecosystem and are a fundamental pillar of adoption.
Narrative
In order to foster adoption, it is essential that we create a trusted experience for all participants. During presentment, this consists of elevating awareness around what data is being requested, by whom, whether the relying party intends on storing this data and if so, what are they planning on doing with the stored data. The Wallet provider should incorporate these elements into their presentment UI in order to create a transparent presentment experience.
1) All data elements that are being requested by the relying party should be clearly outlined and visible
2) The mDL holder should be clearly aware of who is requesting the mDL information. This should be done via displaying the name and icon for the relying party in the presentment sheet in a way that is clear and legible.
3) The intent to retain variable per data element should be displayed clearly to the user for increased transparency.
4) The intent to retain variable should be supported by an up to date identity data privacy policy. This identity specific data use policy should be accessible from within the mDL holder's Wallet. The data use policy should offer simple explanations outlining why the relying party plans on storing the data and for how long.
Secondary Use Case (optional)
This is a sample added by john
Actors
| Actor | Role in the use case |
|---|---|
| Alice | |
| Bob | |
| etcetera |
User Stories
| Element | Detail | Notes |
|---|---|---|
| As a, | <description of user> | |
| I want | <functionality> | |
| so that | <benefit> | |
| Acceptance Criteria | ||
| Given | <how things begin> | |
| When | <action taken> | |
| Then | <outcome of taking action> | |
Prerequisites / Assumptions
Use Case Details
Privacy
Data Provided
Data Retained
Diagram
Steps
Primary Use Case
The anticipated normal sequence
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Secondary Use Case(s)
Alternate or variant sequences
| # | Step | Description |
|---|---|---|
| 1 | ||
| 2 | ||
| 3 | ||
| 4 |
Sequence Diagram
End State
Describe what measures or signifies the end of the case
Success
Markers or metrics that indicate success
Failure
Markers or metrics that indicate failure
References
Champion / Stakeholder
List of the people that created the use case
Related Material
Resources and Links
Page Tasks
- Type your task here, using "@" to assign to a user and "//" to select a due date