Add appendix with issuance, verification, and presentation examples - #684
Add appendix with issuance, verification, and presentation examples#684eric-schuh wants to merge 2 commits into
Conversation
Adding sequence diagrams that detail simple examples of issuance, verification--of both a single, and multiple VCs, and in person presentation of a VC.
Co-authored-by: Ted Thibodeau Jr <tthibodeau@openlinksw.com>
dlongley
left a comment
dlongley
left a comment
There was a problem hiding this comment.
Preview not working so hard to review visually, but noticed a spelling mistake. If we can't get the preview working reviewers can paste the mermaid into another tool, but ideally we get that fixed here.
| Note left of VWF: Initiate exchange including the created VP. | ||
|
|
||
| VWF->>VC: Validate VP | ||
| VC->>VC: Apply buisiness rules |
There was a problem hiding this comment.
| VC->>VC: Apply buisiness rules | |
| VC->>VC: Apply business rules |
| Note left of VWF: Initiate exchange including the requested VP. | ||
|
|
||
| VWF->>VC: Validate VP | ||
| VC->>VC: Apply buisiness rules |
There was a problem hiding this comment.
| VC->>VC: Apply buisiness rules | |
| VC->>VC: Apply business rules |
| Note left of IWF: Initiate exchange by POSTing an empty JSON object. | ||
|
|
||
| IWF->>IC: Coordinate | ||
| IC->>IC: Apply buisiness rules |
There was a problem hiding this comment.
| IC->>IC: Apply buisiness rules | |
| IC->>IC: Apply business rules |
There was a problem hiding this comment.
Looked at the sequence diagrams via another mermaid tool. They aren't correct as they have the workflow service talking with the coordinator system to carry out the tasks that it actually carries out.
Additionally, any business rules that can't be encoded into a workflow itself are applied before a workflow -- and any that need to occur after a workflow are handled via redirects, which can be interaction URLs for "interstitial" business rules that enable, for example, a user to "stay their wallet".
We should correct this before merging.
3 participants
First pass at addressing #561. I added 4 examples:
My main question is around the two verification examples and ensuring that they do accurately represent two different ways the holder coordinator and service could behave to achieve nominally the same result.
💥 Error: 500 Internal Server Error 💥
PR Preview failed to build. (Last tried on Aug 4, 2026, 6:50 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build bikeshed/ReSpec specs
🔗 Related URL
Error output:
This seems to be an issue with the Spec Generator service. PR Preview doesn't manage this service and so has no control over it. If you've identified an issue with it, you can report the issue to the maintainers of Spec Generator directly. Please be courteous. Thank you!
If you don't have enough information above to solve the error by yourself or if the issue doesn't seem related to Spec Generator, you can file an issue with PR Preview.