- From: Joe Andrieu <joe@legreq.com>
- Date: Tue, 21 Sep 2021 12:59:21 -0700
- To: "Credentials Community Group" <public-credentials@w3.org>
- Message-Id: <a8b94849-54fe-4af2-8290-a781b33a95ac@www.fastmail.com>
Here's a rendering of the work flow from the supply chain folks (Erich Schuh and I sat down with Orie and Mike to tease this out). It advances the conversation from a non-chapi use case. Notably, some additional definitions XXX App = The server that instantiates the business rules that drive XXX behavior XXX Service = The service/software that provides the XXX specific functionality, driven by the XXX App. For example, in the USCIS Digital Green Card case *Issuer App* = the website run by USCIS that interfaces with beneficiaries and knows who gets a green card. It drives the Issuer Service. *Issuer Service *= the SaaS run by, e.g., Digital Bazaar, which provides VC issuance capability to clients We've started using this pattern across all three roles and are working through updating the CHAPI flow. -j -- Joe Andrieu, PMP joe@legreq.com LEGENDARY REQUIREMENTS +1(805)705-8651 Do what matters. http://legreq.com <http://www.legendaryrequirements.com/>
Attachments
- application/pdf attachment: VC_Verification_3.pdf
Received on Tuesday, 21 September 2021 20:00:02 UTC