[Openid-specs-digital-credentials-protocols] DCP WG call - Minutes 02-29-2024

[Oliver Terbu]

# Intros

Nemja, developer for Sicpa, building a platform for decentralized identity.

# Agenda

- PR 276: on claims structure
- PR 155: Terminology
- Issue 93: pickup at batch endpoint and issued credential copies again, LSP needs that functionality
- Postponed request_uri extension discussion, because Torsten is needed

# PR 276

Recap on the issue related to #276

It does not appear to have an agreement on the PR. A lot of people have requested changes.

Feeling on the APAC call: not in a state where we should rush it in ID-1. General agreement but it takes some time to get implementation experience to get it into ID-2.

Discussion on whether we should add some words to the spec for ID-1 that we know there were issues with this part of the spec and we planned to do the changes. PR 280 was raised for that reason. No agreement on PR 280 yet. No precedent for anything like that before.

The question was raised if we should add a note that there are some changes expected in that paragraph in ID-2?

No strong opinion from the group whether or not to include a note in ID-1.

# PR 155

Some discussion on the scope of the PR and the issue.
- Clarified that OID4VCI is not dealing with the distinction between the holder and subject.
- Clarified that it is more about having multiple credentials of the same type.
- Clarified that credential versions are beyond this PR and part of another issuer/discussion.

The group is encouraged to take a look at PR #155.

Participants on the call found it useful to have a relationship diagram describing how the terms relate to each other.

# Issue 93

Also relates to terminology PR 155.

Main question how to update credential request to issue multiple copies in one request, e.g., the same credential bound to multiple keys.

There are various approaches described in the issue. The most popular is using the batch credential endpoint and having multiple proofs per credential request.

The group is asked to engage in the discussion.

Most participants on the call agreed that the proposed changes to the credential request to optimize for receiving multiple copies make sense. There was also the concern raised that this increases the complexity of the specification.

Participants on the call seemed positive about having a dedicated metadata parameter to indicate the max. number of credential copies that can be requested in one request. This could simplify error responses.

PR needed as a next step.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openid.net/pipermail/openid-specs-digital-credentials-protocols/attachments/20240229/78a20d69/attachment-0001.html>