- From: <sysbot+notifier@w3.org>
- Date: Wed, 24 Apr 2024 16:15:05 +0000
- To: public-transition-announce@w3.org
This is a transition request for a Candidate Recommendation CR Request for Bitstring Status List v1.0 - vc-bitstring-status-list from https://github.com/w3c/transitions/issues/603 # Document title, URLs, estimated publication date - Bitstring Status List v1.0 - Final URL: https://www.w3.org/TR/2024/CR-vc-bitstring-status-list-20240509/ - Proposed publication date: 09 May 2024 - Editors' draft: https://w3c.github.io/vc-bitstring-status-list/CR/2024-CR1/ # Abstract - https://w3c.github.io/vc-bitstring-status-list/CR/2024-CR1/#abstract # Status - https://w3c.github.io/vc-bitstring-status-list/CR/2024-CR1/#sotd # Link to group's decision to request transition - https://www.w3.org/2017/vc/WG/Meetings/Minutes/2024-04-24-vcwg#resolution1 # Changes This is the first Candidate Recommendation for the first Recommendation attempt for this specification. It does not have a changelog other than the changes since FPWD, which can be found here: https://github.com/w3c/vc-bitstring-status-list/commits/main/?until=2024-04-24 # Requirements satisfied Yes. # Dependencies met (or not) The normative dependencies are on the VC Data Model which is in CR. # Wide Review Issues processed: - https://github.com/w3c/vc-bitstring-status-list/issues?q=is:issue+ PRs processed: - https://github.com/w3c/vc-bitstring-status-list/pulls?q=is:pr+ Horizontal reviews: * TAG: https://github.com/w3ctag/design-reviews/issues/874 * PING: https://github.com/w3cping/privacy-request/issues/127 * Security: https://github.com/w3c/security-request/issues/62 * a11y: https://github.com/w3c/a11y-request/issues/70 * i18n: https://github.com/w3c/i18n-request/issues/222 Additionally, Simone Onofri is gathering reviewers to do a more thorough review of the Bitstring Status list specification during the Candidate Recommendation phase. Liaisons: * There are participants' overlap with the following groups: * RDF Canonicalization and Hashing Working Group * Decentralized Identifier Working Group * Credentials Community Group * Internet Engineering Task Force * Internet Engineering Task Force Crypto Forum Research Group * Hyperledger Aries * Decentralized Identity Foundation Interoperability Working Group * IMS Global * ISO/IEC JTC 1/SC 17/WG 10 * ISO/IEC JTC 1/SC 17/WG 4 * Web of Things Working Group * Joint meeting at W3C TPAC 2023 * APA Working Group * See horizontal reviews * National Institute of Standards and Technology, U.S. Department of Commerce * DHS actively engaged w/ NIST over VCWG + Justin Richer NIST SP 800-63-C work * The American Civil Liberties Union * Presentations given to ACLU and CDT over the years via PING and other venues * ACLU, EFF, CDT, and EPIC paper speaking positively about VCs: https://www.eff.org/document/10-16-2023-aclu-eff-epic-comments-re-tsa-nprm-mdls * European Telecommunications Standards Institute * EU Digital Wallet cites/uses VCWG output + ARF + EBSI + EUDI Wallet # Formal Objections None. # Implementation * Test vectors & test suite (to be improved upon soon) * https://w3c.github.io/w3c/vc-bitstring-status-list-test-suite/ * Existing Experimental Implementations * NOTE: StatusList2021 was renamed to BitstringStatusList * [Cheqd](https://docs.cheqd.io/identity/credential-service/status-lists) * [Circle](https://developers.circle.com/verite/docs/status-registry-practices) * [Digital Bazaar](https://github.com/digitalbazaar/vc-bitstring-status-list) * [Mesur.io](https://github.com/mesur-io/vc-status-list-2021) * [Microsoft](https://learn.microsoft.com/en-us/entra/verified-id/whats-new) * [Trustbloc](https://pkg.go.dev/github.com/trustbloc/vc-go/status/validator/statuslist2021) * [WaltId](https://docs.walt.id/v/ssikit/concepts/credential-statuses/status-list-2021-entry) # Patent disclosures None, see - https://www.w3.org/groups/wg/vc/ipr/ --- cc: cc: @msporny @dlongley @mprorock @mkhraisha -- This email was generated automatically using https://github.com/w3c/transition-issues-bot
Received on Wednesday, 24 April 2024 16:15:10 UTC