Skip to content

Conversation

javereec
Copy link

As discussed in the WG call on October 9th, I've added references to the relevant extension points in the specification. I've also improved the wording to say that the list is exhaustive.

Would like for someone to check if the wording of the points is correct, in particular the one below

- Which X.509 certificate profile to use

@jogu jogu requested a review from c2bo October 16, 2025 15:46
- Whether to use the W3C Digital Credentials API, Redirects with custom URL schemes and/or Redirects with claimed `https` scheme URIs for presentation (see (#scope))
- Which Credential format to support across issuance and presentation (see (#scope))
- Whether to use Signed Issuer Metadata or not (see (#issuer-metadata))
- How to make a Credential Offer to the Wallet (see (#credential-offer))

Choose a reason for hiding this comment

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

Suggested change
- How to make a Credential Offer to the Wallet (see (#credential-offer))
- How a Credential Offer is made available to the Wallet (see (#credential-offer))

I'm not sure what the exact intention was in the rephrasing, but I'm not sure if How to make a Credential Offer to the Wallet captures the same meaning as to send.

- Support or restriction of additional cryptographic suites and hash algorithms
This document intentionally leaves certain extensions for ecosystems to define, in order to enable broad compatibility across differing or even conflicting requirements. Below are the extension points listed in this specification:

- Whether to adopt a presentation profile, issuance profile, or both (see (#scope))
Copy link
Member

Choose a reason for hiding this comment

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

Would it make sense to formulate this a bit more generic - something like this?

Suggested change
- Whether to adopt a presentation profile, issuance profile, or both (see (#scope))
- Which profiles (e.g., presentation or issuance profiles) to adopt (see (#scope))

- Which Credential format to support across issuance and presentation (see (#scope))
- Whether to use Signed Issuer Metadata or not (see (#issuer-metadata))
- How to make a Credential Offer to the Wallet (see (#credential-offer))
- Which key attestation format to use (see (#key-attestation))
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- Which key attestation format to use (see (#key-attestation))
- Which Key Attestation format to use (see (#key-attestation))

- Whether to use Signed Issuer Metadata or not (see (#issuer-metadata))
- How to make a Credential Offer to the Wallet (see (#credential-offer))
- Which key attestation format to use (see (#key-attestation))
- Which wallet attestation format to use (see (#wallet-attestation))
Copy link
Member

Choose a reason for hiding this comment

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

Suggested change
- Which wallet attestation format to use (see (#wallet-attestation))
- Which Wallet Attestation format to use (see (#wallet-attestation))

@Sakurann Sakurann added this to the 1.0 Final milestone Oct 17, 2025
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.

4 participants