-
Notifications
You must be signed in to change notification settings - Fork 12
Add references to Ecosystem Implementation Guidelines section #312
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.
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
base: main
Are you sure you want to change the base?
Add references to Ecosystem Implementation Guidelines section #312
Conversation
- 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)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 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)) |
There was a problem hiding this comment.
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?
- 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)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- 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)) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Which wallet attestation format to use (see (#wallet-attestation)) | |
- Which Wallet Attestation format to use (see (#wallet-attestation)) |
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