Difference between revisions of "Mobile Driver's License Presentation"
From MgmtWiki
(→Actors) |
(→Actors) |
||
| Line 10: | Line 10: | ||
* Verifier = The entity that defines what proofs they require from a Holder (via a Presentation Definition) in order to proceed with an interaction. | * Verifier = The entity that defines what proofs they require from a Holder (via a Presentation Definition) in order to proceed with an interaction. | ||
* mDL verifier = entity using an mDL reader to verify an mDL | * mDL verifier = entity using an mDL reader to verify an mDL | ||
| + | |||
| + | ==Transaction== | ||
| + | # The holder and verifier establish a session | ||
| + | # The verifier asks for mDL data | ||
| + | # mDL send data by value or by reference | ||
| + | # The verifier may or may not request other data | ||
==Reference== | ==Reference== | ||
Revision as of 18:28, 14 January 2021
Full Title or Meme
Mobile Driver's License Presentation maps ISO 18013-5 wallet presentation to DIF Presentation Exchange.
Context
- The DIF Presentation Exchange is looking for test cases. This is such a test case (ie a use case with teeth).
- This use case looks at the wallet as the source of Presentation Statements, which is not necessarily the full scope of the DIF WG.
Actors
- Holder = The entity that submits proofs to a Verifier to satisfy the requirements described in a Presentation Definition (may or may not be the subject)
- mDL holder = individual to whom an mDL is issued = legitimate holder of the driving privileges reflected on an mDL = subject of the mDL
- Verifier = The entity that defines what proofs they require from a Holder (via a Presentation Definition) in order to proceed with an interaction.
- mDL verifier = entity using an mDL reader to verify an mDL
Transaction
- The holder and verifier establish a session
- The verifier asks for mDL data
- mDL send data by value or by reference
- The verifier may or may not request other data
Reference
- GitHub issues of the Presentation Exchange.
