Or is that stretching the layering/separation of concerns too far? If a selective example makes sense, the 1.1 use cases section could look something like:
A license-holder needs to present an entire mDL for verification to a foreign government agency while traveling (Example 1)
An eCommerce website requests just a few pieces of information for verification by presenting a vocabulary-based, privacy preserving request (Example 2), which the same license holder uses to present a verifiable subset of the license contents (Example 3).
Then we throw the frame into Example 2 and the resulting VP into Example 3 and we've made the argument for wrapping mDLs in VCs crystal clear to non-technical skimmers of this document.
Or is that stretching the layering/separation of concerns too far? If a selective example makes sense, the 1.1 use cases section could look something like:
Then we throw the frame into Example 2 and the resulting VP into Example 3 and we've made the argument for wrapping mDLs in VCs crystal clear to non-technical skimmers of this document.