Skip to content

Editorial changes to multiple/batch credential issuance section #511

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 8 commits into from
Jun 10, 2025
Merged

Editorial changes to multiple/batch credential issuance section #511

Changes from 1 commit
Commits
Show all changes
8 commits
Select commit Hold shift + click to select a range
6307ab6
Editorial changes to multiple/batch credential issuance section
sloops77 May 20, 2025
86a39cb
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 May 23, 2025
b99464c
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 2, 2025
4c893eb
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 3, 2025
da57887
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 3, 2025
70a837a
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 9, 2025
50c457a
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 9, 2025
e28d670
Update openid-4-verifiable-credential-issuance-1_0.md
sloops77 Jun 10, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 4 additions & 6 deletions openid-4-verifiable-credential-issuance-1_0.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -158,10 +158,10 @@ To this end, extension points to add Credential Format specific parameters in th
Credential Format Profiles for IETF SD-JWT VC [@I-D.ietf-oauth-sd-jwt-vc], ISO mDL [@ISO.18013-5], and W3C VCDM [@VC_DATA] are specified in (#format-profiles).
Other specifications or deployments can define their own Credential Format Profiles using the above-mentioned extension points.

### Multiple Credential Issuance
### Batch Credential Issuance

This specification enables the issuance of Verifiable Credentials through the Credential Endpoint.
A single request message to this endpoint may request the issuance of one or more Verifiable Credentials.
A single request message to this endpoint may request the issuance of one or more Verifiable Credentials in a batch.

Credentials can vary in their format, including Credential Format Profile-specific parameters, in their contents known as the Credential Dataset, and in the cryptographic data such as Issuer signatures, hashes, and keys used for Cryptographic Key Binding.
Credentials can therefore vary in the following dimensions:
Expand All @@ -170,11 +170,9 @@ Credentials can therefore vary in the following dimensions:
- Credential Format
- Cryptographic Data

In the context of a single request, all issued Credentials MUST share the same Credential Format and Credential Dataset. However, they MAY contain different Cryptographic Data, such as being bound to different cryptographic keys (e.g., to ensure unlinkability between the Credentials).
In the context of a single request, all issued Credentials belonging to the batch MUST share the same Credential Format and Credential Dataset. However, they MAY contain different Cryptographic Data, such as being bound to different cryptographic keys (e.g., to ensure unlinkability between the Credentials).
To issue multiple Verifiable Credentials with differing Credential Formats or Credential Datasets, multiple requests MUST be sent to the Credential Endpoint.

In the course of the authorization process, the Credential Issuer MAY also request Credential presentation as a means to authenticate or identify the End-User during the issuance flow, as described in (#use-case-5).
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

why was this deleted?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@Sakurann I was editing the batch credential section. I didn't understand why a reference to presentation based authentication was here. I think it needs to be moved but maybe it makes more sense for me to restore it and get this merged asap, and then it can be sorted out in #509

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I agree it seems to be placed in the wrong section. Can we move it somewhere more sensible than deleting it or is it already mentioned elsewhere?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@paulbastian @Sakurann i moved the section to the introduction to authorization code flow.

Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I'm happy with this change.


### Issuance Flow Variations

The issuance can have multiple characteristics that can be combined depending on the use cases:
Expand Down Expand Up @@ -2734,7 +2732,7 @@ Wallet Providers may also provide a market place where Issuers can register to b

# Acknowledgements {#Acknowledgements}

We would like to thank Richard Barnes, Paul Bastian, Vittorio Bertocci, Christian Bormann, John Bradley, Brian Campbell, Gabe Cohen, David Chadwick, Andrii Deinega, Giuseppe De Marco, Mark Dobrinic, Daniel Fett, Pedro Felix, George Fletcher, Christian Fries, Timo Glasta, Mark Haine, Fabian Hauck, Roland Hedberg, Joseph Heenan, Alen Horvat, Andrew Hughes, Jacob Ideskog, Lukasz Jaromin, Edmund Jay, Michael B. Jones, Tom Jones, Judith Kahrer, Takahiko Kawasaki, Niels Klomp, Ronald Koenig, Micha Kraus, Markus Kreusch, Philipp Lehwalder, Adam Lemmon, Dave Longley, David Luna, Daniel McGrogan, Jeremie Miller, Kenichi Nakamura, Rolson Quadras, Nat Sakimura, Sudesh Shetty, Oliver Terbu, Dimitri James Tsiflitzis, Mike Varley, Arjen van Veen, Jan Vereecken, David Waite, Jacob Ward for their valuable feedback and contributions to this specification.
We would like to thank Richard Barnes, Paul Bastian, Vittorio Bertocci, Christian Bormann, John Bradley, Brian Campbell, Gabe Cohen, David Chadwick, Andrii Deinega, Giuseppe De Marco, Mark Dobrinic, Daniel Fett, Pedro Felix, George Fletcher, Christian Fries, Timo Glasta, Mark Haine, Fabian Hauck, Roland Hedberg, Joseph Heenan, Alen Horvat, Andrew Hughes, Jacob Ideskog, Lukasz Jaromin, Edmund Jay, Michael B. Jones, Tom Jones, Judith Kahrer, Takahiko Kawasaki, Niels Klomp, Ronald Koenig, Micha Kraus, Markus Kreusch, Philipp Lehwalder, Adam Lemmon, Dave Longley, David Luna, Daniel McGrogan, Jeremie Miller, Kenichi Nakamura, Andres Olave, Rolson Quadras, Nat Sakimura, Sudesh Shetty, Oliver Terbu, Dimitri James Tsiflitzis, Mike Varley, Arjen van Veen, Jan Vereecken, David Waite, Jacob Ward for their valuable feedback and contributions to this specification.

# Notices

Expand Down