RE: Interoperability SURVEY for DIF Interop

Thanks a lot!
Which mean that for the purpose of this survey, WACI-DIDComm might have been enough as a choice.

From: Stephen Curran <swcurran@cloudcompass.ca>
Sent: Thursday, October 20, 2022 9:59 AM
To: Kristina Yasuda <Kristina.Yasuda@microsoft.com>
Cc: Torsten Lodderstedt <torsten@lodderstedt.net>; Kaliya Identity Woman <kaliya@identitywoman.net>; Credentials Community Group <public-credentials@w3.org>
Subject: Re: Interoperability SURVEY for DIF Interop

Regards the DIDComm / WACI-DIDComm separation.

DIDComm is a peer-to-peer (2- and n-wise) messaging protocol based on the use of DIDs thats support the exchange of messages that themselves make up protocols.  So two parties might establish a DIDComm connection, and then use protocols on top of DIDComm to exchange credentials and proofs. Many other interactions are possible, beyond credential exchange.

WACI<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdecentralized-identity%2Fwallet-and-credential-interactions&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C84ac3122bc984123004108dab2bc7826%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638018819806014002%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=pcO2oA2hG4ggp8rWFag589BM4MH5%2FelgGlr%2FbjSx2MA%3D&reserved=0> (Wallet and Credential Interactions) are a specific set of protocols run on top of DIDComm to exchange credentials and proofs. WACI uses credential exchange protocols derived for DIDComm V2 from the Aries credential exchange protocols that work on DIDComm v1.

On Thu, Oct 20, 2022 at 9:40 AM Kristina Yasuda <Kristina.Yasuda@microsoft.com<mailto:Kristina.Yasuda@microsoft.com>> wrote:
+1 to Torsten's question.

(assuming you meant OpenID4VC family - there is no "standardized way" to use OIDC.Core with VCs)
For presentation of Credentials OpenID Connect is too vague: it should be 1/ OpenID4VP only 2/OpenID4VP + SIOPv2 as separate options.
For issuance, OpenID4VCI.
And to clarify, OpenID4VP and OpenID4VCI have "OpenID" in the name because they are being worked on in OIDF and are related to claims, but they are OAuth 2.0-based.

Also, Could someone please educate me why is WACI-DIDComm and DIDComm are separate?

And JSON-JWT should probably be separated into JSON-encoding (not usign @context - section 6.1 of vc-data-model) and JSON-LD encoding (full use of @context - Section 6.2 of vc-data-mode), these two do not exactly interoperate and survey results will be incomplete without this distinction.

Cheers,
Kristina


From: Torsten Lodderstedt <torsten@lodderstedt.net<mailto:torsten@lodderstedt.net>>
Sent: Tuesday, October 11, 2022 1:53 AM
To: Kaliya Identity Woman <kaliya@identitywoman.net<mailto:kaliya@identitywoman.net>>
Cc: Credentials Community Group <public-credentials@w3.org<mailto:public-credentials@w3.org>>
Subject: Re: Interoperability SURVEY for DIF Interop

Hi Kaliya,

thanks for conducting this survey. That's important work!

I noticed you list "OpenID Connect" as protocol option. Do you really mean "OpenID Connect" (which is possible) or are you referring to the "OpenID 4 Verifiable Credentials" protocol family? It is dedicated for VCs and thus pretty different from OpenID Connect. Perhaps it makes sense to list both.

best regards,
Torsten.

Am 11.10.2022 um 06:18 schrieb Kaliya Identity Woman <kaliya@identitywoman.net<mailto:kaliya@identitywoman.net>>:

Hi CCG,

 One of the hats that I wear is co-chairing the DIF Interoperability Working Group. We have two new co-chairs - Brent Shambaugh and Daniel Bluhm.

We are doing a survey to understand more about what is out there in terms of formats and Interoperability clusters.

Here is a link to the survey.

https://docs.google.com/forms/d/e/1FAIpQLSfbFh4DQeyI0msXsWvfpbrtYEfgQrGRD7tw4d2Rg0NEyhvcKQ/viewform?usp=sf_link<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fdocs.google.com%2Fforms%2Fd%2Fe%2F1FAIpQLSfbFh4DQeyI0msXsWvfpbrtYEfgQrGRD7tw4d2Rg0NEyhvcKQ%2Fviewform%3Fusp%3Dsf_link&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C84ac3122bc984123004108dab2bc7826%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638018819806014002%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=xJgHjaaEN9at688k9CTseNRgj3YAMVr6iyN8by6NkoQ%3D&reserved=0>

- Kaliya




--

Stephen Curran
Principal, Cloud Compass Computing, Inc. (C3I)
Chair - Sovrin Foundation (sovrin.org)

Schedule a Meeting: https://calendly.com/swcurran<https://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcalendly.com%2Fswcurran&data=05%7C01%7CKristina.Yasuda%40microsoft.com%7C84ac3122bc984123004108dab2bc7826%7C72f988bf86f141af91ab2d7cd011db47%7C1%7C0%7C638018819806014002%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=GoSIjrMGvsVubjyKYMjin31Al2nZVV8GxX3XxZbq9Xw%3D&reserved=0>