Are VCs a necessary hurdle on the path to DID adoption?
Are VCs A Necessary Hurdle On The Path To DID Adoption?
Convener: Adrian Gropper
Tags for the session - technology discussed/ideas considered:
Discussion notes, key understandings, outstanding questions, observations, and, if appropriate to this discussion: action items, next steps:
Background techy info from Tuesday’s session 1D :http://docs.google.com/document/d/1KX6Xcm_jAzj_CWMhoYjFBOX7KXE8vVEgYHua6Kj_AKo/edit
JH - Service Endpoint MS - Provider vs. Patient same Identity? PA - DID WG - VC maybe w/o DID DC - Learn about separation / credentialing products EF - avoid schema rigidity JH - newbie KK - workday product manager OS - VC without DID - works on sidetree
Path A - SDS - Secure Data Store - Service endpoint to data store in DID
- a pipe between an identifier and an attribute
- where to get the info
- like an Info Endpoint in OpenID Connect
Path B - Service Endpoint to Authorization Server in DID
- Separation of Concerns
DIDs don’t have a business model so people bundle VC added value for business reasons
AS first already has adoption /
TxAuth as a new OAuth3 model for the DID service endpoint
Gov wants a process to hold verifiers accountable
Platforms don’t benefit from a separation of concerns AS vs RS
Issuer-held credential and signed credential
VC not efficient for pharma or surveillance
15:48:21 From Orie Steele : Everything needs a business model, or it dies for lack of reproduction.
16:46:37 From Adrian Gropper : http://blog.petrieflom.law.harvard.edu/2020/04/29/covid19-privacy-surveillance-community-organizations/
16:49:19 From Adrian Gropper : http://docs.google.com/document/d/1F9yUn1kYaSiSlLGyijmGDkZdl3hWh5Zs0Z9JBKpYH7s/edit