Skip to content

Conversation

@bc-pi
Copy link
Member

@bc-pi bc-pi commented Feb 6, 2024

Slightly reword the first sentence of the intro and include SD-JWT VC in the (non-exhaustive) list of formats

# Introduction

This specification defines an API that is used to issue Verifiable Credentials. W3C formats [@VC_DATA] as well as other Credential formats, like [@ISO.18013-5], are supported.
This specification defines an OAuth protected API for the issuance of Verifiable Credentials. Credentials can be of any format, including, but not limited to, W3C formats [@VC_DATA], mDL [@ISO.18013-5], and SD-JWT VC [@I-D.ietf-oauth-sd-jwt-vc].
Copy link
Member

Choose a reason for hiding this comment

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

I don't want to be picky but not all endpoints defined in this specification are OAuth protected.

You might also want to use "Verifiable Credentials" in the second sentence.

Copy link
Collaborator

Choose a reason for hiding this comment

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

we are not talking about Authz/Token endpoints here. All endpoints used for the issuance (Credential, Batch, Deferred, Notification) are OAuth protected.

Copy link
Member

Choose a reason for hiding this comment

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

@Sakurann , I didn't refer to Authz/Token endpoints. This specification also defines & introduces /.well-known/openid-credential-issuer that isn't an OAuth protected API.

Copy link
Collaborator

Choose a reason for hiding this comment

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

Let's not be picky at that level in the introduction.

Co-authored-by: Kristina <52878547+Sakurann@users.noreply.github.com>
@Sakurann Sakurann merged commit 0289cf3 into main Feb 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

9 participants