-
Notifications
You must be signed in to change notification settings - Fork 31
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
CR Snapshot Update Request for Verifiable Credential Data Integrity 1.0, EdDSA and ECDSA Cryptosuites - vc-data-integrity, vc-di-ecdsa, vc-di-eddsa #657
Comments
Raised w3cping/privacy-request#146 and w3c/security-request#78. |
Request deadline has passed without any reactions. |
Approved. With the understanding that security folks will keep looking at this (#58). |
Documents published and announced, see, e.g., https://www.w3.org/news/2024/five-candidate-recommendation-snapshots-published-by-the-verifiable-credentials-working-group/. Closing. |
Document URLs
Link to group's decision to request transition
https://www.w3.org/2017/vc/WG/Meetings/Minutes/2024-09-27-vcwg#resolution2
Link to previous Candidate Recommendation transition or update request
#573
Substantive changes
See "Changes since the First Candidate Recommendation" at each link below:
Any changes in requirements?
None
Wide Review of substantive changes
None of the substantive changes since CR1 are related to Accessibility, Internationalization, Architecture, or Privacy. Some Security-related changes have been made, but the Security review is pending the creation of Security Interest Group. We have written to each group above to get confirmation on if they concur with our analysis.
With respect to wide review, changes to each specification has been circulated on a weekly basis to the W3C Credentials Community Group, which contains over 560+ individuals, with a number of them providing continued feedback since CR1. For example:
https://lists.w3.org/Archives/Public/public-credentials/2024Oct/0031.html
The test suites run on a weekly basis and implementers actively track how their implementations are performing. Ecosystem reports are also available and are tracked and commented on by organizations adopting vendor solutions:
https://canivc.com/
Multiple implementers have also reviewed changes and have confirmed that they will implement or plan to implement all substantive changes since CR1.
Issues status
See, respectively:
Formal Objections
None
Any changes in implementation information?
Seven more implementations have been added to the test suites since CR1, bringing the total implementations registered to thirteen (13) across all data integrity cryptographic suites:
https://github.com/w3c/vc-test-suite-implementations/tree/main/implementations
Deadline for further comments
30 days
Any changes in patent disclosures?
None
cc: @msporny @brentzundel @Wind4Greg @dlongley
(Edited 2024.10.26 by IH: updated the wide review section)
The text was updated successfully, but these errors were encountered: