2024 10 30 Meeting Notes

2024-10-30 (B Call)

Organizer: Tim Cappalli

Scribe: None

Agenda

• Administrivia
• Intros from any new folks?
• Ecosystem updates
  • Fed ID WG charter updates
  • Incubation
  • OpenID DCP working group
• EU Engagement Letter
• PR & Issue Review
  • Top level request object structure should be fully defined by protocol identifier (#185)
  • CGR1 blockers:
    • Add additional examples (#181), (PR)
    • Add a way to check what protocols are supported (#168)
    • Add initial intro text (#182)
    • Privacy considerations (#183)
    • Security considerations (#184)
    • Require JSON Types (#179)
• Issues without owners triage: https://github.com/WICG/digital-credentials/issues?q=is%3Aissue+is%3Aopen+no%3Aassignee
• AOB

Attendees

Please add your name and affiliation

• Tim Cappalli (Okta)
• Ted Thibodeau (he/him) (OpenLink Software)
• Hiroyuki Sano (Sony)
• Brian Campbell (Ping)
• Marcos (Apple)
• Nick Doty (CDT)

Notes

No one took notes, so these bullets are based on Tim Cappalli's recollection of the meeting. Shortened meeting due to IIW.

EU Engagement Letter

Received EU engagement letter. W3C lawyers evaluating. Open ID Foundation also received one for the OID4VP and VCI specs

Top level request object structure should be fully defined by protocol identifier (#185)

• Brian: Understand concern in the issue but don't think its necessary as signed is simply "request" and additional top level properties may be necessary over time.

Protocol versioning also came up

• "openid4vp" protocol name will implicitly be v1. Future updates can append a version
• Tim to create issue in OID4* repos asking about future numbering

Privacy and Security Consideration section

• Marcos: not super concerned about the security considerations section as the spec itself should be designed to be secure.

General discussion about CGR1

A spirited discussion happened regarding living specs vs versioned docs. At TPAC 2024, we agreed to spin out a snapshot of the spec as a Community Group report allowing external parties such as Open ID and the EU to reference the document.

Marcos stated that this is a living document and we shouldn't spin a versioned Community Group report, and that the W3C doesn't produce static documents.

Ted responded that the W3C does indeed produce static and versioned documents.

Tim to follow up offline.