-
Notifications
You must be signed in to change notification settings - Fork 11
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
3 changed files
with
217 additions
and
0 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| # Document title, URLs, estimated publication date | ||
|
|
||
| Data Integrity ECDSA Cryptosuites v1.0 | ||
| https://w3c.github.io/vc-di-ecdsa/CR/2023-09-28/ | ||
| 28 September 2023 | ||
|
|
||
| # Abstract | ||
|
|
||
| https://w3c.github.io/vc-di-ecdsa/CR/2023-09-28/#abstract | ||
|
|
||
| # Status | ||
|
|
||
| https://w3c.github.io/vc-di-ecdsa/CR/2023-09-28/#sotd | ||
|
|
||
| # Link to group's decision to request transition | ||
|
|
||
| PROPOSAL: Publish the Data Integrity ECDSA Cryptosuites v1.0 | ||
| specification as a Candidate Recommendation on 28 September 2023 | ||
| (https://w3c.github.io/vc-di-ecdsa/CR/2023-09-28/) with a CR period | ||
| ending on the last day of November 2023 and with exit criteria | ||
| requiring two independent implementations of each mandatory (MUST) | ||
| feature in the specification. | ||
|
|
||
| # Changes | ||
|
|
||
| https://w3c.github.io/vc-di-ecdsa/CR/2023-09-28/#revision-history | ||
|
|
||
| # Requirements satisfied | ||
|
|
||
| Yes. | ||
|
|
||
| # Dependencies met (or not) | ||
|
|
||
| There is one dependency on Multibase, which is expected to be | ||
| published by a new IETF Multiformats Working Group. If the | ||
| dependencies fail to materialize in a stable way, the specification | ||
| contains specific Multibase values that can be used such that an | ||
| external dependency is not necessary. | ||
|
|
||
| # Wide Review | ||
|
|
||
| Issues processed: | ||
| https://github.com/w3c/vc-di-ecdsa/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| PRs processed: | ||
| https://github.com/w3c/vc-di-ecdsa/pulls?q=is%3Apr+is%3Aclosed | ||
|
|
||
| Horizontal reviews: | ||
| * TAG: https://github.com/w3ctag/design-reviews/issues/850 | ||
| * PING: https://github.com/w3cping/privacy-request/issues/120 | ||
| * Security: https://github.com/w3c/security-request/issues/55 (request timeout), https://github.com/w3cping/privacy-request/issues/120 | ||
| * a11y: https://github.com/w3c/vc-data-integrity/issues/97 (request timeout) | ||
| * i18n: https://github.com/w3c/vc-data-integrity/issues/96 (request timeout) | ||
|
|
||
| # Issues addressed | ||
|
|
||
| https://github.com/w3c/vc-di-ecdsa/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| # Formal Objections | ||
|
|
||
| None. | ||
|
|
||
| # Implementation | ||
|
|
||
| 3 independent implementations for the existing test suites: | ||
|
|
||
| https://w3c.github.io/vc-di-ecdsa-test-suite/ | ||
|
|
||
| # Patent disclosures | ||
|
|
||
| https://www.w3.org/groups/wg/vc/ipr/ | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,72 @@ | ||
| # Document title, URLs, estimated publication date | ||
|
|
||
| Data Integrity EdDSA Cryptosuites v1.0 | ||
| https://w3c.github.io/vc-di-eddsa/CR/2023-09-28/ | ||
| 28 September 2023 | ||
|
|
||
| # Abstract | ||
|
|
||
| https://w3c.github.io/vc-di-eddsa/CR/2023-09-28/#abstract | ||
|
|
||
| # Status | ||
|
|
||
| https://w3c.github.io/vc-di-eddsa/CR/2023-09-28/#sotd | ||
|
|
||
| # Link to group's decision to request transition | ||
|
|
||
| PROPOSAL: Publish the Data Integrity EdDSA Cryptosuites v1.0 | ||
| specification as a Candidate Recommendation on 28 September 2023 | ||
| (https://w3c.github.io/vc-di-eddsa/CR/2023-09-28/) with a CR period | ||
| ending on the last day of November 2023 and with exit criteria | ||
| requiring two independent implementations of each mandatory (MUST) | ||
| feature in the specification. | ||
|
|
||
| # Changes | ||
|
|
||
| https://w3c.github.io/vc-di-eddsa/CR/2023-09-28/#revision-history | ||
|
|
||
| # Requirements satisfied | ||
|
|
||
| Yes. | ||
|
|
||
| # Dependencies met (or not) | ||
|
|
||
| There is one dependency on Multibase, which is expected to be | ||
| published by a new IETF Multiformats Working Group. If the | ||
| dependencies fail to materialize in a stable way, the specification | ||
| contains specific Multibase values that can be used such that an | ||
| external dependency is not necessary. | ||
|
|
||
| # Wide Review | ||
|
|
||
| Issues processed: | ||
| https://github.com/w3c/vc-di-eddsa/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| PRs processed: | ||
| https://github.com/w3c/vc-di-eddsa/pulls?q=is%3Apr+is%3Aclosed | ||
|
|
||
| Horizontal reviews: | ||
| * TAG: https://github.com/w3ctag/design-reviews/issues/850 | ||
| * PING: https://github.com/w3cping/privacy-request/issues/120 | ||
| * Security: https://github.com/w3c/security-request/issues/55 (request timeout), https://github.com/w3cping/privacy-request/issues/120 | ||
| * a11y: https://github.com/w3c/vc-data-integrity/issues/97 (request timeout) | ||
| * i18n: https://github.com/w3c/vc-data-integrity/issues/96 (request timeout) | ||
|
|
||
| # Issues addressed | ||
|
|
||
| https://github.com/w3c/vc-di-eddsa/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| # Formal Objections | ||
|
|
||
| None. | ||
|
|
||
| # Implementation | ||
|
|
||
| 4 independent implementations for the existing test suites: | ||
|
|
||
| https://w3c.github.io/vc-di-eddsa-test-suite/ | ||
|
|
||
| # Patent disclosures | ||
|
|
||
| https://www.w3.org/groups/wg/vc/ipr/ | ||
|
|
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,73 @@ | ||
| # Document title, URLs, estimated publication date | ||
|
|
||
| Verifiable Credential Data Integrity 1.0 | ||
| https://w3c.github.io/vc-data-integrity/CR/2023-09-28/ | ||
| 28 September 2023 | ||
|
|
||
| # Abstract | ||
|
|
||
| https://w3c.github.io/vc-data-integrity/CR/2023-09-28/#abstract | ||
|
|
||
| # Status | ||
|
|
||
| https://w3c.github.io/vc-data-integrity/CR/2023-09-28/#sotd | ||
|
|
||
| # Link to group's decision to request transition | ||
|
|
||
| PROPOSAL: Publish the Verifiable Credential Data Integrity 1.0 | ||
| specification as a Candidate Recommendation on 28 September 2023 | ||
| (https://w3c.github.io/vc-data-integrity/CR/2023-09-28/) with a CR | ||
| period ending on the last day of November 2023 and with exit criteria | ||
| requiring two independent implementations of each mandatory (MUST) | ||
| feature in the specification. | ||
|
|
||
| # Changes | ||
|
|
||
| https://w3c.github.io/vc-data-integrity/CR/2023-09-28/#revision-history | ||
|
|
||
| # Requirements satisfied | ||
|
|
||
| Yes. | ||
|
|
||
| # Dependencies met (or not) | ||
|
|
||
| There are two dependencies on Multibase and Multihash, which are | ||
| expected to be published by a new IETF Multiformats Working Group. If | ||
| the dependencies fail to materialize in a stable way, the | ||
| specification (and the cryptosuite specifications) contain specific | ||
| Multibase and Multihash values that can be used such that an external | ||
| dependency is not necessary. | ||
|
|
||
| # Wide Review | ||
|
|
||
| Issues processed: | ||
| https://github.com/w3c/vc-data-integrity/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| PRs processed: | ||
| https://github.com/w3c/vc-data-integrity/pulls?q=is%3Apr+is%3Aclosed | ||
|
|
||
| Horizontal reviews: | ||
| * TAG: https://github.com/w3ctag/design-reviews/issues/850 | ||
| * PING: https://github.com/w3cping/privacy-request/issues/120 | ||
| * Security: https://github.com/w3c/security-request/issues/55 (request timeout), https://github.com/w3cping/privacy-request/issues/120 | ||
| * a11y: https://github.com/w3c/vc-data-integrity/issues/97 (request timeout) | ||
| * i18n: https://github.com/w3c/vc-data-integrity/issues/96 (request timeout) | ||
|
|
||
| # Issues addressed | ||
|
|
||
| https://github.com/w3c/vc-data-integrity/issues?q=is%3Aissue+is%3Aclosed | ||
|
|
||
| # Formal Objections | ||
|
|
||
| None. | ||
|
|
||
| # Implementation | ||
|
|
||
| 7 independent implementations for the existing test suites: | ||
|
|
||
| https://w3c.github.io/vc-data-integrity/implementations/#test-suite-reports | ||
|
|
||
| # Patent disclosures | ||
|
|
||
| https://www.w3.org/groups/wg/vc/ipr/ | ||
|
|