<orie> noting that DIF PE supports other protocols
<orie> whereas vp request spec is currently only implemented in CHAPI.
<orie> we have an implementation of it in trace interop
<orie> but are likely going to replace it
<orie> especially give the challenges with interop with the other protocols that are created by not using DIF PE
<phil.l> many issuers are interested in the use of the credentials they create and holders then package and send as presentation.This is understandable, and at the same time problematic for privacy. A point to consider in the audit question.
Topic: Holder Architecture Diagram
<dmitriz> I'm curious - has anyone ever encountered an API (or data model) spec where audit issues were in scope?
<orie> yikes to the scoping summary
<phil.l> There are use cases where the reason someone would do the presentation creation is external is that they are doing so from cloud-based client. This is an equity issue if a cloud service can't be used. I recognize the security & privacy implications...
<orie> if it helps I can speak to Universal Wallet Interop spec, and how I see it supporting the vc http api not replacing it
<orie> the diagram does make it clear that holders have internal and external apis