- From: Dmitri Zagidulin <dzagidulin@gmail.com>
- Date: Wed, 22 Sep 2021 11:27:41 -0400
- To: Credentials Community Group <public-credentials@w3.org>
- Message-ID: <CANnQ-L6dBxSP84+BgOeZKFn8uADKPy_0XoKVACJVKNdM4-DuiQ@mail.gmail.com>
Great job on the diagram! Is there a way to denote that a step is optional? (I spose one could put '(optional)' next to the text, in parens, but just curious what your design thoughts are.) On Tue, Sep 21, 2021 at 4:02 PM Joe Andrieu <joe@legreq.com> wrote: > 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> > > >
Received on Wednesday, 22 September 2021 15:31:12 UTC