8 Pull requests merged by 4 people

• Tidied up document using tidy-html5

  #355 merged Aug 22, 2025

• chore(README): add useful links

  #342 merged Aug 22, 2025

• chore: link up various key terms

  #353 merged Aug 22, 2025

• Tidied up document using tidy-html5

  #351 merged Aug 20, 2025

• chore: bring back the missing </section> tag

  #350 merged Aug 19, 2025

• Editorial: mark some sections as informative

  #347 merged Aug 19, 2025

• chore: remove unnecessary section tag

  #348 merged Aug 19, 2025

• Editorial: Add Acknowledgements section

  #314 merged Aug 19, 2025

1 Pull request opened by 1 person

• chore(explainer): fix link to risk.md from ping

  #354 opened Aug 21, 2025

1 Issue closed by 1 person

• Editorial: Add references to definitions in the privacy considerations

  #284 closed Aug 22, 2025

3 Issues opened by 2 people

• Proposal to Add Comprehensive Testing Support for the Digital Credentials API

  #357 opened Aug 22, 2025

• Add DigitalCredentialIssuanceResponse partial

  #356 opened Aug 22, 2025

• Add a terminology section

  #352 opened Aug 20, 2025

25 Unresolved conversations

Sometimes conversations happen on old items that aren’t yet closed. Here is a list of all the Issues and Pull Requests with unresolved conversations.

• Editorial: clean up scope section

  #339 commented on Aug 22, 2025 • 15 new comments

• chore: fix links pointing to old repo

  #341 commented on Aug 22, 2025 • 5 new comments

• Limit scope to UA boundary

  #344 commented on Aug 22, 2025 • 4 new comments

• Editorial: make digital wallets out of scope

  #338 commented on Aug 22, 2025 • 0 new comments

• Define interaction between platform credential chooser and the user agent

  #306 commented on Aug 21, 2025 • 0 new comments

• Add a11y guidance for user agents

  #238 commented on Aug 21, 2025 • 0 new comments

• Ensure that credential issuers do not discriminate based on the user’s device or OS

  #349 commented on Aug 22, 2025 • 0 new comments

• what restrictions can the issuer put on wallets that it provisions into?

  #84 commented on Aug 22, 2025 • 0 new comments

• Document WG security review requirements for protocols

  #215 commented on Aug 21, 2025 • 0 new comments

• privacy review for registry inclusion

  #226 commented on Aug 21, 2025 • 0 new comments

• Registry requirements should not use RFC2119 language

  #240 commented on Aug 21, 2025 • 0 new comments

• Protocol registry: Reviewing is not sufficient

  #255 commented on Aug 21, 2025 • 0 new comments

• Protocol registry: royalty free requirement

  #256 commented on Aug 21, 2025 • 0 new comments

• Protocol registry: specification availability

  #257 commented on Aug 21, 2025 • 0 new comments

• registration of and commitment to a particular use case and purpose

  #266 commented on Aug 21, 2025 • 0 new comments

• Can we require protocols to support unlinkable revocation?

  #280 commented on Aug 21, 2025 • 0 new comments

• user agents should limit to protocols listed in the registry that meet the group's requirements

  #288 commented on Aug 21, 2025 • 0 new comments

• Is a registry needed?

  #345 commented on Aug 21, 2025 • 0 new comments

• proof of authentication

  #296 commented on Aug 21, 2025 • 0 new comments

• Requests' size should be checked before transient activation

  #202 commented on Aug 21, 2025 • 0 new comments

• [spec] Update scope around issuance/create to be specific to credential manager selection

  #343 commented on Aug 21, 2025 • 0 new comments

• Figure out a system for displaying contributors in the spec

  #311 commented on Aug 21, 2025 • 0 new comments

• enumerated values for purpose, sharing and retention in API method

  #209 commented on Aug 20, 2025 • 0 new comments

• require in-context in-content explanation and an element for user-initiated presentation

  #208 commented on Aug 20, 2025 • 0 new comments

• Most users will experience a no-matching-credential dead-end

  #104 commented on Aug 19, 2025 • 0 new comments