Re: VC-HTTP-API new sequence diagram

I had some minor questions about a few details, e.g. what's a "Data
Ready Package"?
Also, since it mentions WebKMS, I was wondering what's the current state
of that, and is anyone actually using it in conjunction with the VC API.

But in general, I think this digram is very useful, nice job!
I agree with the App/Service terminology, it helps to illustrate where
the VC API comes into play and where it doesn't.

Markus

On 21.09.21 21:59, Joe Andrieu 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 <mailto:joe@legreq.com>
> LEGENDARY REQUIREMENTS                                                
>        +1(805)705-8651
> Do what matters.                                                      
>                      http://legreq.com
> <http://www.legendaryrequirements.com>
>
>