[Openid-specs-digital-credentials-protocols] Super-delayed notes DCP WG + SIOP meeting minutes: May 9, 2024
Lukasz Jaromin
lukasz.jaromin at raidiam.com
Tue Jun 11 20:06:02 UTC 2024
Hi All,
I found this email sitting in my outbox. Please find the meeting notes from May meeting below.
Attendees:
- Kristina Yasuda
- Joseph Heenan
- Andrea Prian
- Jin Wen
- Michael Jones
- Pedro Felix
- Lukasz Jaromin
- Brian Campbell
- Bjorn Hjelm
Jospeh shared the Agenda:
1. IPR reminder/ Note-taking
2. Introductions/re-introductions
3. Agenda bashing/adoption
4. Events/External orgs
5. In person WG meeting at identiverse
6. OIDF invited experts to FedCM/BrowserAPI group
7. VCI: Concept and Terminology Cleanup, Part 1, https://github.com/openid/OpenID4VCI/pull/155
8. VCI: rework credential and batch credential endpoint, https://github.com/openid/OpenID4VCI/pull/293
9. VP: What is allowed in client_metadata? https://github.com/openid/OpenID4VP/issues/17
10. Other Open PRs/Issues
Call for any other business:
Lukasz wanted to talk about the Transaction Data document and open-ended types list the if time permits.
External Orgs updates:
* Announcement on Identiverse in 2.5 weeks now. We plan in-person working group meeting with hybrid options. It will be in the morning. We need to know how many people is coming. Sign up for the event please at https://www.eventbrite.com/e/openid-foundation-dcp-wg-hybrid-meeting-at-identiverse-tickets-902324616217
* EIC: It was considered to do in-person meeting, but it may be challenging to find time during the event
PRs:
- VCI #155 Terminology PRs got merged into VCI spec.
- VCI #293 Highlights from the Tue call on restructure of “proofs” JSON structure
Discussion on transaction data document. Kristina explained motivation behind the document. This is still to be determined how this proposal will be reflected in the specification and where the types will be defined.
Issues:
- VP #17 summary of the issue and problem description
- Info regarding work in progress on explainer of query language changes
- VP #25 direct_post response - issue can be closed. Redirect uri only make sense on the same device. We can create a PR.
https://github.com/openid/OpenID4VP/issues/25 Pedro will create PR.
- VCI #94 Problem description and discussion on how to address a problem of no clientid (in e.g. subsequent refresh token flow) when pre-authorized flow is used that does not require client pre-registration. Some potential ideas have been discussed like use of OpenID federation, registration of client with DCR or some ephemeral clientids. Problem to be explored further offline and in subsequent calls.
Regards
LJ
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240611/67b06cb2/attachment-0001.html>
More information about the Openid-specs-digital-credentials-protocols
mailing list