Verifiable Credentials Working Group - Activity in 2023
No matches.
TR publications
-
19 documents published.
-
Data Integrity ECDSA Cryptosuites v1.0 published twice as a Candidate Recommendation Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published twice as a Candidate Recommendation Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Verifiable Credentials JSON Schema Specification published as a Candidate Recommendation Draft. History of Verifiable Credentials JSON Schema Specification
-
Verifiable Credential Data Integrity 1.0 published as a Candidate Recommendation Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published 7 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Securing Verifiable Credentials using JOSE and COSE published 4 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
BBS Cryptosuite v2023 published twice as a Working Draft. History of BBS Cryptosuite v2023
-
Past meetings
Participants
-
4 participants joined.
-
Peter Davis (Onfido) joined.
-
Oliver Terbu (Mattr Limited) joined.
-
Peter Davis (Onfido) joined.
-
Waheed Ashraf (INSIGHT - The Centre for Data Analytics) joined.
-
-
5 participants left.
-
Peter Davis (Onfido) left.
-
Peter Davis (Onfido) left.
-
Orie Steele (Transmute) left.
-
Oliver Terbu (Mattr Limited) left.
-
Logan Porter (Mattr Limited) left.
-
-
2 organizations joined.
-
Onfido joined.
-
INSIGHT - The Centre for Data Analytics joined.
-
-
3 organizations left.
-
Onfido left.
-
Onfido left.
-
Transmute left.
-
GitHub
w3c/vc-jose-cose
-
18 issues opened.
-
Inconsistent versions w3c/vc-jose-cose#214, by @David-Chadwick.
-
Remove mentions of "proof" from Section 6.1 w3c/vc-jose-cose#211, by @msporny.
-
Example 13 description is wrong w3c/vc-jose-cose#210, by @msporny.
-
Explicitly allow key format conversion w3c/vc-jose-cose#209, by @msporny.
-
Data format for COSE_Key expression in Controller Document is undefined w3c/vc-jose-cose#208, by @msporny.
-
COSE algorithms and examples not specified w3c/vc-jose-cose#207, by @msporny.
-
Algorithms are poorly defined / unimplementable w3c/vc-jose-cose#206, by @msporny.
-
Unclear semantics wrt. JWT claims vs. VC properties w3c/vc-jose-cose#205, by @msporny.
-
Media types are incorrect; usage can't be counted on w3c/vc-jose-cose#204, by @msporny.
-
Section on Wallets is not necessary w3c/vc-jose-cose#203, by @msporny.
-
Conformance classes are not defined w3c/vc-jose-cose#202, by @msporny.
-
Support JWT-secured VCs w3c/vc-jose-cose#201, by @msporny.
-
Add an example for selective disclosure w3c/vc-jose-cose#199, by @thereisnogabe.
-
https://w3c.github.io/vc-jose-cose/ is not being updated w3c/vc-jose-cose#196, by @selfissued.
-
Horizontal Review Tracking w3c/vc-jose-cose#195, by @thereisnogabe.
-
Text about obtaining the right verification key w3c/vc-jose-cose#194, by @David-Chadwick.
-
Spec should be more specific about implementation details w3c/vc-jose-cose#192, by @kdenhartog.
-
Do we need an SD-JWT profile for W3C VCs? w3c/vc-jose-cose#191, by @David-Chadwick.
-
-
6 issues closed.
-
https://w3c.github.io/vc-jose-cose/ is not being updated w3c/vc-jose-cose#196.
-
Do we need an SD-JWT profile for W3C VCs? w3c/vc-jose-cose#191.
-
Write an algorithm for verifying VC/VP JWTs w3c/vc-jose-cose#187.
-
Add examples for COSE Sign1 Detached Payloads w3c/vc-jose-cose#174.
-
Add COSE Example w3c/vc-jose-cose#182.
-
Can registered JWT claims be used only in the JOSE header?? w3c/vc-jose-cose#135.
-
-
16 issues received 36 new comments.
-
Do we need an SD-JWT profile for W3C VCs? w3c/vc-jose-cose#191 (10 comments by @David-Chadwick, @galund, @iherman, @OR13, @selfissued, @thereisnogabe)
-
Text about obtaining the right verification key w3c/vc-jose-cose#194 (4 comments by @David-Chadwick, @selfissued)
-
Spec should be more specific about implementation details w3c/vc-jose-cose#192 (4 comments by @kdenhartog, @selfissued)
-
Change the registration request for SD-JWT w3c/vc-jose-cose#179 (2 comments by @selfissued, @TallTed)
-
Adjust Explicit Typing Guidance regarding `typ` w3c/vc-jose-cose#184 (2 comments by @selfissued, @TallTed)
-
https://w3c.github.io/vc-jose-cose/ is not being updated w3c/vc-jose-cose#196 (2 comments by @iherman, @selfissued)
-
Should JOSE/COSE verification strip out or inline @context values? w3c/vc-jose-cose#188 (1 comment by @selfissued)
-
-
7 pull requests opened.
-
Improving explanation of SD-JWT w3c/vc-jose-cose#215, by @David-Chadwick.
-
Update Abstract w3c/vc-jose-cose#213, by @David-Chadwick.
-
Update Title w3c/vc-jose-cose#212, by @David-Chadwick.
-
Reference Key Discovery section w3c/vc-jose-cose#200, by @selfissued.
-
Correct SD-JWT-VC references w3c/vc-jose-cose#198, by @selfissued.
-
Update index.html: do not set the publish date in the editor's draft w3c/vc-jose-cose#197, by @iherman.
-
Remove myself as editor w3c/vc-jose-cose#193, by @OR13.
-
-
7 pull requests merged.
-
Update index.html: do not set the publish date in the editor's draft w3c/vc-jose-cose#197.
-
Correct SD-JWT-VC references w3c/vc-jose-cose#198.
-
Add placeholder algorithms w3c/vc-jose-cose#190.
-
Remove myself as editor w3c/vc-jose-cose#193.
-
Add COSE examples w3c/vc-jose-cose#185.
-
Update references w3c/vc-jose-cose#189.
-
Remove duplicate descriptive language w3c/vc-jose-cose#183.
-
-
1 pull request closed.
-
Remove requests for multiple suffixes w3c/vc-jose-cose#186.
-
-
7 pull requests received 21 new comments.
-
Add placeholder algorithms w3c/vc-jose-cose#190 (10 comments by @iherman, @jyasskin, @OR13, @selfissued)
-
Remove requests for multiple suffixes w3c/vc-jose-cose#186 (4 comments by @iherman, @OR13, @selfissued, @TallTed)
-
Update index.html: do not set the publish date in the editor's draft w3c/vc-jose-cose#197 (1 comment by @iherman)
-
w3c/vc-bitstring-status-list
-
7 issues opened.
-
Remove `ttl` w3c/vc-bitstring-status-list#120, by @dlongley.
-
Rename `reference` to `statusReference` w3c/vc-bitstring-status-list#114, by @dlongley.
-
Rename "size" to "statusSize" w3c/vc-bitstring-status-list#113, by @dlongley.
-
Conformance classes need to be defined w3c/vc-bitstring-status-list#101, by @msporny.
-
Invalid JSON in Example 1 w3c/vc-bitstring-status-list#98, by @samuelmr.
-
Verification algorithm should say what happens if schema isn't followed w3c/vc-bitstring-status-list#97, by @jyasskin.
-
Credential Type Mismatch between the Spec and the Schema w3c/vc-bitstring-status-list#96, by @hkny.
-
-
14 issues closed.
-
How to understand herd privacy in using bit string? w3c/vc-bitstring-status-list#54.
-
Vocabulary definitions w3c/vc-bitstring-status-list#81.
-
Would like multiple status to be capable of representation in a status list w3c/vc-bitstring-status-list#42.
-
Specify bit order for status list w3c/vc-bitstring-status-list#36.
-
Media type pairings w3c/vc-bitstring-status-list#78.
-
Add guidance on rfc3642 w3c/vc-bitstring-status-list#55.
-
Trusted origins, list issuers vs hosts w3c/vc-bitstring-status-list#43.
-
Randomization w3c/vc-bitstring-status-list#41.
-
Should "noise" be added during "updates" w3c/vc-bitstring-status-list#40.
-
Define priority for a single credential with multiple statuses w3c/vc-bitstring-status-list#37.
-
Can the spec relax/remove the requirement on minimal bit length? w3c/vc-bitstring-status-list#14.
-
Status-List-2021 without the VC w3c/vc-bitstring-status-list#4.
-
Add a "reason code" w3c/vc-bitstring-status-list#12.
-
Invalid JSON in Example 1 w3c/vc-bitstring-status-list#98.
-
-
36 issues received 52 new comments.
-
Unify design of status lists to support multi-bit values w3c/vc-bitstring-status-list#73 (6 comments by @msporny, @samuelmr)
-
Credential Type Mismatch between the Spec and the Schema w3c/vc-bitstring-status-list#96 (2 comments by @msporny)
-
How to understand herd privacy in using bit string? w3c/vc-bitstring-status-list#54 (2 comments by @msporny)
-
Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation w3c/vc-bitstring-status-list#80 (1 comment by @msporny)
-
Is it possible to support multiple purposes? w3c/vc-bitstring-status-list#47 (1 comment by @msporny)
-
Align bitstring structure and IETF Token Status List structure? w3c/vc-bitstring-status-list#93 (1 comment by @msporny)
-
Implementation guidelines around how StatusList2021Credential is secured/encoded. w3c/vc-bitstring-status-list#52 (1 comment by @msporny)
-
Add privacy considerations for multi-bit correlation w3c/vc-bitstring-status-list#86 (1 comment by @msporny)
-
Verification algorithm should say what happens if schema isn't followed w3c/vc-bitstring-status-list#97 (1 comment by @msporny)
-
Should validation algorithm check size of bitstring? w3c/vc-bitstring-status-list#87 (1 comment by @msporny)
-
Add section on expected server HTTP status codes w3c/vc-bitstring-status-list#64 (1 comment by @msporny)
-
Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) w3c/vc-bitstring-status-list#51 (1 comment by @msporny)
-
clarify protocol for retrieval of a status list w3c/vc-bitstring-status-list#44 (1 comment by @msporny)
-
Would like multiple status to be capable of representation in a status list w3c/vc-bitstring-status-list#42 (1 comment by @msporny)
-
Handling Right to Erasure in encodedList and Validate Algorithm w3c/vc-bitstring-status-list#23 (1 comment by @msporny)
-
Can the spec relax/remove the requirement on minimal bit length? w3c/vc-bitstring-status-list#14 (1 comment by @msporny)
-
-
21 pull requests opened.
-
Add at risk issue marker regarding multibit status entries. w3c/vc-bitstring-status-list#123, by @msporny.
-
Add examples for multiple status lists and multiple entries in a single status list w3c/vc-bitstring-status-list#122, by @msporny.
-
Rename "herd privacy" to "group privacy". w3c/vc-bitstring-status-list#121, by @msporny.
-
Add "at risk" marker noting bitstring format might change in CR. w3c/vc-bitstring-status-list#119, by @msporny.
-
Add guidance on how to secure status lists. w3c/vc-bitstring-status-list#118, by @msporny.
-
Add privacy consideration section about Multistatus Correlation. w3c/vc-bitstring-status-list#117, by @msporny.
-
Raise malformed value error on malformed values. w3c/vc-bitstring-status-list#116, by @msporny.
-
Raise error when status list size does not meet minimum threshold. w3c/vc-bitstring-status-list#115, by @msporny.
-
Add mechanism to retrieve historical status list information. w3c/vc-bitstring-status-list#112, by @msporny.
-
Add section on Processing Errors. w3c/vc-bitstring-status-list#111, by @msporny.
-
Clarify base64 encoding as base64url encoding. w3c/vc-bitstring-status-list#110, by @msporny.
-
Update BitstringStatusList context to align with latest spec. w3c/vc-bitstring-status-list#109, by @msporny.
-
Update VCDM dependency to VCDM v2.0. w3c/vc-bitstring-status-list#108, by @msporny.
-
Add protocol statements related to pub/sub of status lists. w3c/vc-bitstring-status-list#107, by @msporny.
-
Clarify what credential status information is about. w3c/vc-bitstring-status-list#106, by @msporny.
-
Add formal vocabulary definitions. w3c/vc-bitstring-status-list#105, by @msporny.
-
Throw RANGE_ERROR for indexes outside the length of a bitstring. w3c/vc-bitstring-status-list#104, by @msporny.
-
Add note specifying that issuer might be different for status lists. w3c/vc-bitstring-status-list#103, by @msporny.
-
Add conformance classes to specification. w3c/vc-bitstring-status-list#102, by @msporny.
-
Rename "status" to "message" for `statusPurpose` feature. w3c/vc-bitstring-status-list#100, by @msporny.
-
Remove myself as editor w3c/vc-bitstring-status-list#99, by @OR13.
-
-
3 pull requests merged.
-
Remove myself as editor w3c/vc-bitstring-status-list#99.
-
Update the echidna script w3c/vc-bitstring-status-list#95.
-
Add section on media types w3c/vc-bitstring-status-list#92.
-
-
20 pull requests received 85 new comments.
-
Add formal vocabulary definitions. w3c/vc-bitstring-status-list#105 (20 comments by @dlongley, @iherman, @msporny)
-
Raise error when status list size does not meet minimum threshold. w3c/vc-bitstring-status-list#115 (13 comments by @David-Chadwick, @dlongley, @msporny, @TallTed)
-
Clarify what credential status information is about. w3c/vc-bitstring-status-list#106 (6 comments by @David-Chadwick, @TallTed)
-
Add protocol statements related to pub/sub of status lists. w3c/vc-bitstring-status-list#107 (4 comments by @David-Chadwick, @TallTed)
-
Add section on Processing Errors. w3c/vc-bitstring-status-list#111 (4 comments by @David-Chadwick, @dlongley, @TallTed)
-
Update BitstringStatusList context to align with latest spec. w3c/vc-bitstring-status-list#109 (4 comments by @dlongley, @msporny)
-
Throw RANGE_ERROR for indexes outside the length of a bitstring. w3c/vc-bitstring-status-list#104 (4 comments by @iherman, @msporny, @TallTed)
-
Clarify base64 encoding as base64url encoding. w3c/vc-bitstring-status-list#110 (4 comments by @dlongley)
-
Add conformance classes to specification. w3c/vc-bitstring-status-list#102 (4 comments by @iherman, @msporny, @TallTed)
-
Add privacy consideration section about Multistatus Correlation. w3c/vc-bitstring-status-list#117 (3 comments by @David-Chadwick)
-
Add mechanism to retrieve historical status list information. w3c/vc-bitstring-status-list#112 (3 comments by @David-Chadwick, @TallTed)
-
Rename "status" to "message" for `statusPurpose` feature. w3c/vc-bitstring-status-list#100 (3 comments by @dlongley, @msporny, @TallTed)
-
Add note specifying that issuer might be different for status lists. w3c/vc-bitstring-status-list#103 (3 comments by @David-Chadwick, @TallTed)
-
Raise malformed value error on malformed values. w3c/vc-bitstring-status-list#116 (2 comments by @David-Chadwick, @dlongley)
-
Rename "herd privacy" to "group privacy". w3c/vc-bitstring-status-list#121 (2 comments by @kimdhamilton, @msporny)
-
Add "at risk" marker noting bitstring format might change in CR. w3c/vc-bitstring-status-list#119 (1 comment by @David-Chadwick)
-
Add examples for multiple status lists and multiple entries in a single status list w3c/vc-bitstring-status-list#122 (1 comment by @dlongley)
-
w3c/vc-test-suite-implementations
-
1 issue opened.
-
EWF issuer with the tag `Ed25519Signature2020` is issuing a VC with `Ed25519Signature2018` proof type w3c/vc-test-suite-implementations#9, by @JSAssassin.
-
-
4 pull requests opened.
-
Add my implementation w3c/vc-test-suite-implementations#11, by @HelgeKrueger.
-
Update `Testing locally` section in `README.md`. w3c/vc-test-suite-implementations#10, by @JSAssassin.
-
Remove unused "method" property from configs. w3c/vc-test-suite-implementations#8, by @JSAssassin.
-
Remove `vc-api` tag. w3c/vc-test-suite-implementations#7, by @JSAssassin.
-
-
2 pull requests merged.
-
Remove unused "method" property from configs. w3c/vc-test-suite-implementations#8.
-
Remove `vc-api` tag. w3c/vc-test-suite-implementations#7.
-
-
2 pull requests received 11 new comments.
-
Add my implementation w3c/vc-test-suite-implementations#11 (8 comments by @HelgeKrueger, @JSAssassin)
-
Remove unused "method" property from configs. w3c/vc-test-suite-implementations#8 (3 comments by @BigBlueHat, @JSAssassin)
-
w3c/vc-data-model
-
13 issues opened.
-
phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work w3c/vc-data-model#1402, by @TallTed.
-
Clarify embedded proof extension point w3c/vc-data-model#1400, by @msporny.
-
Verifying a VC should return the same credential regardless of the verification method w3c/vc-data-model#1399, by @David-Chadwick.
-
Ensure `credentialStatus` `id` field is optional w3c/vc-data-model#1398, by @dlongley.
-
Specify what kind of processing is safe on a returned document w3c/vc-data-model#1388, by @msporny.
-
Specify that it is important to validate the `issuer` value w3c/vc-data-model#1386, by @msporny.
-
Allow extensions to ProblemDetails object w3c/vc-data-model#1384, by @ghost.
-
Update algorithms section to normatively depend on the INFRA specification w3c/vc-data-model#1378, by @msporny.
-
Rewrite verification algorithm in a way that does not cause layer violations w3c/vc-data-model#1377, by @msporny.
-
Separate verification from validation in verification algorithm w3c/vc-data-model#1376, by @msporny.
-
Remove repetition of normative statements in verification algorithm w3c/vc-data-model#1375, by @msporny.
-
Specify guarantees that all securing mechanisms must provide. w3c/vc-data-model#1374, by @msporny.
-
Bug in the context file? w3c/vc-data-model#1373, by @iherman.
-
-
20 issues closed.
-
Verifying a VC should return the same credential regardless of the verification method w3c/vc-data-model#1399.
-
Specify that it is important to validate the `issuer` value w3c/vc-data-model#1386.
-
Allow extensions to ProblemDetails object w3c/vc-data-model#1384.
-
Clarify section on verifiable credential graph w3c/vc-data-model#1365.
-
Define algorithm for verification w3c/vc-data-model#1337.
-
Make validation normative w3c/vc-data-model#1328.
-
Update algorithms section to normatively depend on the INFRA specification w3c/vc-data-model#1378.
-
Separate verification from validation in verification algorithm w3c/vc-data-model#1376.
-
Remove repetition of normative statements in verification algorithm w3c/vc-data-model#1375.
-
Specify guarantees that all securing mechanisms must provide. w3c/vc-data-model#1374.
-
Request profile parameter from `application/vc` w3c/vc-data-model#1363.
-
Add mechanism to embed externally secured VCs in a VP w3c/vc-data-model#1352.
-
Clarify the domain and range of the `verifiablePresentation.verifiableCredential` property w3c/vc-data-model#1366.
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290.
-
Improve Verification Algorithms section w3c/vc-data-model#1362.
-
Cross-check the `domain`/`range` statements in the vocabulary with the VCDM spec w3c/vc-data-model#1319.
-
Bug in the context file? w3c/vc-data-model#1373.
-
Default context contains terms outside of the spec w3c/vc-data-model#1314.
-
Consider mandating securing RDF graph for all securing mechanisms w3c/vc-data-model#1327.
-
Update i18n example w3c/vc-data-model#1289.
-
-
1 issue reopened.
-
Default context contains terms outside of the spec w3c/vc-data-model#1314, by @iherman.
-
-
30 issues received 140 new comments.
-
Clarify section on verifiable credential graph w3c/vc-data-model#1365 (13 comments by @andresuribe87, @iherman, @msporny, @OR13, @TallTed)
-
Specify guarantees that all securing mechanisms must provide. w3c/vc-data-model#1374 (10 comments by @awoie, @iherman, @msporny, @OR13)
-
Update 4.9 Securing Verifiable Credentials w3c/vc-data-model#1316 (8 comments by @iherman, @msporny, @OR13, @TallTed)
-
Specify that it is important to validate the `issuer` value w3c/vc-data-model#1386 (8 comments by @awoie, @iherman, @msporny)
-
Rewrite verification algorithm in a way that does not cause layer violations w3c/vc-data-model#1377 (7 comments by @iherman, @msporny, @OR13)
-
Clarify the domain and range of the `verifiablePresentation.verifiableCredential` property w3c/vc-data-model#1366 (7 comments by @andresuribe87, @brentzundel, @dlongley, @iherman, @msporny, @OR13)
-
Bug in the context file? w3c/vc-data-model#1373 (7 comments by @BigBlueHat, @davidlehn, @gkellogg, @iherman, @pchampin)
-
Update algorithms section to normatively depend on the INFRA specification w3c/vc-data-model#1378 (6 comments by @iherman, @jyasskin, @msporny, @OR13)
-
Authorized Presenters w3c/vc-data-model#1359 (6 comments by @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Separate verification from validation in verification algorithm w3c/vc-data-model#1376 (5 comments by @iherman, @msporny, @OR13)
-
Request profile parameter from `application/vc` w3c/vc-data-model#1363 (5 comments by @iherman, @msporny, @OR13)
-
Add mechanism to embed externally secured VCs in a VP w3c/vc-data-model#1352 (5 comments by @iherman, @msporny)
-
Specify what kind of processing is safe on a returned document w3c/vc-data-model#1388 (4 comments by @iherman, @msporny)
-
Remove repetition of normative statements in verification algorithm w3c/vc-data-model#1375 (4 comments by @iherman, @jyasskin, @msporny)
-
Consider mandating securing RDF graph for all securing mechanisms w3c/vc-data-model#1327 (4 comments by @awoie)
-
Ensure `credentialStatus` `id` field is optional w3c/vc-data-model#1398 (3 comments by @iherman, @msporny)
-
Verifying a VC should return the same credential regardless of the verification method w3c/vc-data-model#1399 (3 comments by @dlongley, @msporny, @selfissued)
-
Add mechanism to cryptographically secure non-credential VP properties (contexts etc) w3c/vc-data-model#1360 (3 comments by @iherman, @msporny)
-
Default context contains terms outside of the spec w3c/vc-data-model#1314 (3 comments by @iherman, @mtaimela, @OR13)
-
phrasing and/or punctuation for input "inputBytes or inputDocument and inputMediaType" needs work w3c/vc-data-model#1402 (2 comments by @msporny, @TallTed)
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290 (2 comments by @brentzundel, @msporny)
-
Cross-check the `domain`/`range` statements in the vocabulary with the VCDM spec w3c/vc-data-model#1319 (1 comment by @msporny)
-
-
25 pull requests opened.
-
Update context to include latest BitstringStatusList changes. w3c/vc-data-model#1406, by @msporny.
-
Add RANGE_ERROR to list of potential errors. w3c/vc-data-model#1405, by @msporny.
-
Jwt example diagrams w3c/vc-data-model#1404, by @iherman.
-
Add embedded securing mechanism specification requirements w3c/vc-data-model#1403, by @msporny.
-
Refine status language and make credential status `id` optional. w3c/vc-data-model#1401, by @msporny.
-
Correct layering violations related to the proof property w3c/vc-data-model#1397, by @selfissued.
-
Update references to controller document w3c/vc-data-model#1396, by @msporny.
-
Add missing digestMultibase value in base context. w3c/vc-data-model#1395, by @msporny.
-
Use new Securing Mechanism Verify Proof interface w3c/vc-data-model#1394, by @msporny.
-
Clarify how issuer validation occurs. w3c/vc-data-model#1393, by @msporny.
-
Add requirement for securing mechanisms to have post-verification documentation. w3c/vc-data-model#1392, by @msporny.
-
Clarify that ProblemDetails can be extended for any reason. w3c/vc-data-model#1391, by @msporny.
-
Clarify that non-objects aren't allowed as VC graphs. w3c/vc-data-model#1390, by @msporny.
-
Clarify that "proof" is an extension point w3c/vc-data-model#1389, by @msporny.
-
Updating the vocab diagram w3c/vc-data-model#1387, by @iherman.
-
Remove myself as editor w3c/vc-data-model#1385, by @OR13.
-
Add normative references to INFRA in algorithms w3c/vc-data-model#1383, by @msporny.
-
Remove mentions to media type parameters w3c/vc-data-model#1382, by @msporny.
-
Remove document conformance checking algorithm section w3c/vc-data-model#1381, by @msporny.
-
Add requirements for securing mechanism specifications. w3c/vc-data-model#1380, by @msporny.
-
Add support for Enveloped Verifiable Credentials (2nd attempt) w3c/vc-data-model#1379, by @msporny.
-
Add the `EnvelopedVerifiableCredential` class to the vocabulary w3c/vc-data-model#1372, by @iherman.
-
Add `relatedResource` property to `VerifiablePresentation` w3c/vc-data-model#1370, by @msporny.
-
Incorporate status checking into verification algorithm w3c/vc-data-model#1369, by @msporny.
-
Mike is at Self-Issued Consulting w3c/vc-data-model#1368, by @selfissued.
-
-
17 pull requests merged.
-
Use new Securing Mechanism Verify Proof interface w3c/vc-data-model#1394.
-
Clarify how issuer validation occurs. w3c/vc-data-model#1393.
-
Clarify that "proof" is an extension point w3c/vc-data-model#1389.
-
Add missing digestMultibase value in base context. w3c/vc-data-model#1395.
-
Clarify that ProblemDetails can be extended for any reason. w3c/vc-data-model#1391.
-
Clarify that non-objects aren't allowed as VC graphs. w3c/vc-data-model#1390.
-
Updating the vocab diagram w3c/vc-data-model#1387.
-
Add normative references to INFRA in algorithms w3c/vc-data-model#1383.
-
Remove mentions to media type parameters w3c/vc-data-model#1382.
-
Remove document conformance checking algorithm section w3c/vc-data-model#1381.
-
Add requirements for securing mechanism specifications. w3c/vc-data-model#1380.
-
Remove myself as editor w3c/vc-data-model#1385.
-
Add support for Enveloped Verifiable Credentials (2nd attempt) w3c/vc-data-model#1379.
-
Add verification algorithm to specification. w3c/vc-data-model#1338.
-
Update context to match spec for name/description. w3c/vc-data-model#1367.
-
Remove unnecessary vocab comments in vocabulary.yml w3c/vc-data-model#1361.
-
Mike is at Self-Issued Consulting w3c/vc-data-model#1368.
-
-
4 pull requests closed.
-
Add `relatedResource` property to `VerifiablePresentation` w3c/vc-data-model#1370.
-
Incorporate status checking into verification algorithm w3c/vc-data-model#1369.
-
Add mechanism to embed enveloped VCs in VPs. w3c/vc-data-model#1358.
-
Add the `EnvelopedVerifiableCredential` class to the vocabulary w3c/vc-data-model#1372.
-
-
26 pull requests received 385 new comments.
-
Add verification algorithm to specification. w3c/vc-data-model#1338 (71 comments by @awoie, @iherman, @jyasskin, @kdenhartog, @msporny, @OR13, @TallTed)
-
Clarify that "proof" is an extension point w3c/vc-data-model#1389 (26 comments by @iherman, @msporny, @selfissued, @TallTed)
-
Add support for Enveloped Verifiable Credentials (2nd attempt) w3c/vc-data-model#1379 (26 comments by @brianorwhatever, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Incorporate status checking into verification algorithm w3c/vc-data-model#1369 (24 comments by @andresuribe87, @dlongley, @iherman, @jyasskin, @longpd, @msporny, @OR13, @TallTed)
-
Add mechanism to embed enveloped VCs in VPs. w3c/vc-data-model#1358 (24 comments by @andresuribe87, @BigBlueHat, @brentzundel, @iherman, @msporny, @OR13)
-
Clarify how issuer validation occurs. w3c/vc-data-model#1393 (16 comments by @awoie, @dlongley, @iherman, @msporny, @selfissued, @TallTed)
-
Add `relatedResource` property to `VerifiablePresentation` w3c/vc-data-model#1370 (16 comments by @BigBlueHat, @iherman, @jandrieu, @msporny, @OR13, @thereisnogabe)
-
Add normative references to INFRA in algorithms w3c/vc-data-model#1383 (15 comments by @iherman, @jyasskin, @msporny, @TallTed)
-
Remove mentions to media type parameters w3c/vc-data-model#1382 (13 comments by @iherman, @msporny, @OR13, @TallTed)
-
Correct layering violations related to the proof property w3c/vc-data-model#1397 (12 comments by @iherman, @msporny, @selfissued, @TallTed)
-
Update references to controller document w3c/vc-data-model#1396 (11 comments by @brianorwhatever, @iherman, @jandrieu, @msporny, @selfissued, @TallTed)
-
Add the `EnvelopedVerifiableCredential` class to the vocabulary w3c/vc-data-model#1372 (10 comments by @iherman, @msporny, @OR13, @TallTed)
-
Mike is at Self-Issued Consulting w3c/vc-data-model#1368 (9 comments by @iherman, @msporny, @selfissued)
-
Use new Securing Mechanism Verify Proof interface w3c/vc-data-model#1394 (7 comments by @dlongley, @iherman, @msporny, @selfissued)
-
Clarify that non-objects aren't allowed as VC graphs. w3c/vc-data-model#1390 (5 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Update context to match spec for name/description. w3c/vc-data-model#1367 (5 comments by @BigBlueHat, @brentzundel, @iherman, @OR13)
-
Clarify that ProblemDetails can be extended for any reason. w3c/vc-data-model#1391 (4 comments by @iherman, @msporny, @TallTed)
-
Add requirement for securing mechanisms to have post-verification documentation. w3c/vc-data-model#1392 (4 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add embedded securing mechanism specification requirements w3c/vc-data-model#1403 (3 comments by @msporny, @TallTed)
-
Add missing digestMultibase value in base context. w3c/vc-data-model#1395 (3 comments by @iherman, @msporny)
-
Remove unnecessary vocab comments in vocabulary.yml w3c/vc-data-model#1361 (2 comments by @brentzundel, @iherman)
-
w3c/vc-di-ecdsa-test-suite
-
1 issue opened.
-
running local tests w3c/vc-di-ecdsa-test-suite#25, by @HelgeKrueger.
-
-
1 issue closed.
-
running local tests w3c/vc-di-ecdsa-test-suite#25.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
Get issuer and vc holder used in test data generation from test config. w3c/vc-di-ecdsa-test-suite#24, by @JSAssassin.
-
Removes `ecdsa-rdfc-2019` related tests and replaces terms `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-ecdsa-test-suite#23, by @JSAssassin.
-
Unpin node in gh actions. w3c/vc-di-ecdsa-test-suite#22, by @JSAssassin.
-
-
1 pull request merged.
-
Unpin node in gh actions. w3c/vc-di-ecdsa-test-suite#22.
-
-
1 pull request closed.
-
Removes `ecdsa-rdfc-2019` related tests and replaces terms `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-ecdsa-test-suite#23.
-
-
1 pull request received 1 new comment.
-
Removes `ecdsa-rdfc-2019` related tests and replaces terms `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-ecdsa-test-suite#23 (1 comment by @JSAssassin)
-
w3c/vc-di-eddsa-test-suite
-
1 issue opened.
-
Error: seedMultibase required w3c/vc-di-eddsa-test-suite#28, by @HelgeKrueger.
-
-
1 issue closed.
-
Error: seedMultibase required w3c/vc-di-eddsa-test-suite#28.
-
-
1 issue received 5 new comments.
-
Error: seedMultibase required w3c/vc-di-eddsa-test-suite#28 (5 comments by @aljones15, @HelgeKrueger, @JSAssassin)
-
-
3 pull requests opened.
-
Add `.vscode` and `.localImplementationsConfig.cjs` to `.gitignore`. w3c/vc-di-eddsa-test-suite#30, by @JSAssassin.
-
Add a default key seed for VC Generator w3c/vc-di-eddsa-test-suite#29, by @aljones15.
-
Unpin node in gh actions. w3c/vc-di-eddsa-test-suite#27, by @JSAssassin.
-
-
2 pull requests merged.
-
Add a default key seed for VC Generator w3c/vc-di-eddsa-test-suite#29.
-
Unpin node in gh actions. w3c/vc-di-eddsa-test-suite#27.
-
w3c/vc-di-eddsa
-
2 issues opened.
-
Add language clarifying that context injection must happen before canonicalisation w3c/vc-di-eddsa#72, by @rflechtner.
-
Proof serialization signature doesn't match what vc-data-integrity expects w3c/vc-di-eddsa#71, by @jyasskin.
-
-
2 issues closed.
-
Is Example 15 / 16 correct? w3c/vc-di-eddsa#38.
-
Fix byte length of `publickKeyMultibase` to 34 w3c/vc-di-eddsa#66.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Proof Set and Chain Test Vectors w3c/vc-di-eddsa#70, by @Wind4Greg.
-
-
4 pull requests merged.
-
Proof Set and Chain Test Vectors w3c/vc-di-eddsa#70.
-
Fix byte length of `publickKeyMultibase`. w3c/vc-di-eddsa#67.
-
Update auto-publish.yml w3c/vc-di-eddsa#69.
-
Added the final CR Version w3c/vc-di-eddsa#68.
-
-
4 pull requests received 27 new comments.
-
Proof Set and Chain Test Vectors w3c/vc-di-eddsa#70 (23 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
w3c/vc-data-integrity
-
5 issues opened.
-
cryptosuite missing from property list in 2.1 Proofs w3c/vc-data-integrity#232, by @HelgeKrueger.
-
Clarify when and how to perform context injection w3c/vc-data-integrity#231, by @rflechtner.
-
Ensure exposition text on relationship to VCs mentions checking verification relationship against proof purpose w3c/vc-data-integrity#229, by @dlongley.
-
Specify what kind of processing is safe on a returned document w3c/vc-data-integrity#228, by @msporny.
-
Context injection can lead to interference between proofs on a document, breaking verification of jcs-based proofs w3c/vc-data-integrity#225, by @rflechtner.
-
-
1 issue closed.
-
Specify what kind of processing is safe on a returned document w3c/vc-data-integrity#228.
-
-
6 issues received 9 new comments.
-
Ensure exposition text on relationship to VCs mentions checking verification relationship against proof purpose w3c/vc-data-integrity#229 (4 comments by @dlongley, @TallTed)
-
cryptosuite missing from property list in 2.1 Proofs w3c/vc-data-integrity#232 (1 comment by @dlongley)
-
Specify what kind of processing is safe on a returned document w3c/vc-data-integrity#228 (1 comment by @msporny)
-
Ensure proper capitalization of "context" and "vocabulary" w3c/vc-data-integrity#183 (1 comment by @seabass-labrax)
-
Context injection can lead to interference between proofs on a document, breaking verification of jcs-based proofs w3c/vc-data-integrity#225 (1 comment by @rflechtner)
-
-
4 pull requests opened.
-
Define proof properties no longer defined in VCDM w3c/vc-data-integrity#230, by @selfissued.
-
Make Verify Proof match the interface used by JOSE/COSE proof verification w3c/vc-data-integrity#227, by @jyasskin.
-
Define algorithm input and output types. w3c/vc-data-integrity#226, by @jyasskin.
-
Binding Proof Chains Together w3c/vc-data-integrity#224, by @Wind4Greg.
-
-
5 pull requests merged.
-
Define proof properties no longer defined in VCDM w3c/vc-data-integrity#230.
-
Binding Proof Chains Together w3c/vc-data-integrity#224.
-
Update echidna.yml w3c/vc-data-integrity#223.
-
Added the final CR Version w3c/vc-data-integrity#220.
-
Updated the URL-s in the vocabulary w3c/vc-data-integrity#212.
-
-
7 pull requests received 66 new comments.
-
Binding Proof Chains Together w3c/vc-data-integrity#224 (47 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
Define algorithm input and output types. w3c/vc-data-integrity#226 (9 comments by @dlongley, @jyasskin)
-
Make Verify Proof match the interface used by JOSE/COSE proof verification w3c/vc-data-integrity#227 (6 comments by @jyasskin, @msporny, @OR13)
-
w3c/vc-di-ecdsa
-
2 issues closed.
-
Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition w3c/vc-di-ecdsa#22.
-
2 issues received 2 new comments.
-
Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? w3c/vc-di-ecdsa#26 (1 comment by @msporny)
-
Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition w3c/vc-di-ecdsa#22 (1 comment by @msporny)
-
-
1 pull request opened.
-
Fix skolemize existing blank node identifier bug. w3c/vc-di-ecdsa#46, by @dlongley.
-
-
3 pull requests merged.
-
Fix skolemize existing blank node identifier bug. w3c/vc-di-ecdsa#46.
-
Update auto-publish.yml w3c/vc-di-ecdsa#45.
-
Added the final CR Version w3c/vc-di-ecdsa#44.
-
-
3 pull requests received 4 new comments.
-
Fix skolemize existing blank node identifier bug. w3c/vc-di-ecdsa#46 (2 comments by @msporny, @TallTed)
-
w3c/vc-data-model-2.0-test-suite
-
15 pull requests opened.
-
Update gh workflows to use latest actions. w3c/vc-data-model-2.0-test-suite#54, by @JSAssassin.
-
Remove validFrom/validUntil from non time based tests w3c/vc-data-model-2.0-test-suite#53, by @aljones15.
-
Add in Verifiable Presentations to start of test title about verifiab… w3c/vc-data-model-2.0-test-suite#52, by @aljones15.
-
Space VC context test title. w3c/vc-data-model-2.0-test-suite#51, by @aljones15.
-
Expand issuer property tests. w3c/vc-data-model-2.0-test-suite#50, by @aljones15.
-
Update test title for credentialSubjects. w3c/vc-data-model-2.0-test-suite#49, by @aljones15.
-
Add initial issuer.description tests. w3c/vc-data-model-2.0-test-suite#48, by @aljones15.
-
Add issuer name tests. w3c/vc-data-model-2.0-test-suite#47, by @aljones15.
-
Update language for narrow type test. w3c/vc-data-model-2.0-test-suite#46, by @aljones15.
-
Type urls unordered set w3c/vc-data-model-2.0-test-suite#45, by @aljones15.
-
Separate VP & VC no type tests. w3c/vc-data-model-2.0-test-suite#44, by @aljones15.
-
Update test title for subsequent items in @context. w3c/vc-data-model-2.0-test-suite#43, by @aljones15.
-
Separate VC & VP context order tests. w3c/vc-data-model-2.0-test-suite#42, by @aljones15.
-
Separate MUST include @context test by VC & VP. w3c/vc-data-model-2.0-test-suite#41, by @aljones15.
-
Change non-conforming test title & remove issuer test. w3c/vc-data-model-2.0-test-suite#40, by @aljones15.
-
-
13 pull requests merged.
-
Update gh workflows to use latest actions. w3c/vc-data-model-2.0-test-suite#54.
-
Type urls unordered set w3c/vc-data-model-2.0-test-suite#45.
-
Remove validFrom/validUntil from non time based tests w3c/vc-data-model-2.0-test-suite#53.
-
Add issuer name tests. w3c/vc-data-model-2.0-test-suite#47.
-
Update test title for credentialSubjects. w3c/vc-data-model-2.0-test-suite#49.
-
Update language for narrow type test. w3c/vc-data-model-2.0-test-suite#46.
-
Space VC context test title. w3c/vc-data-model-2.0-test-suite#51.
-
Add in Verifiable Presentations to start of test title about verifiab… w3c/vc-data-model-2.0-test-suite#52.
-
Separate VP & VC no type tests. w3c/vc-data-model-2.0-test-suite#44.
-
Update test title for subsequent items in @context. w3c/vc-data-model-2.0-test-suite#43.
-
Separate VC & VP context order tests. w3c/vc-data-model-2.0-test-suite#42.
-
Separate MUST include @context test by VC & VP. w3c/vc-data-model-2.0-test-suite#41.
-
Change non-conforming test title & remove issuer test. w3c/vc-data-model-2.0-test-suite#40.
-
-
6 pull requests received 23 new comments.
-
Expand issuer property tests. w3c/vc-data-model-2.0-test-suite#50 (7 comments by @aljones15, @BigBlueHat, @dlongley)
-
Add initial issuer.description tests. w3c/vc-data-model-2.0-test-suite#48 (6 comments by @aljones15, @JSAssassin)
-
Update language for narrow type test. w3c/vc-data-model-2.0-test-suite#46 (4 comments by @aljones15, @BigBlueHat)
-
Add in Verifiable Presentations to start of test title about verifiab… w3c/vc-data-model-2.0-test-suite#52 (1 comment by @aljones15)
-
w3c/vc-di-ed25519signature2020-test-suite
-
3 pull requests opened.
-
Update eslint dev deps to latest and add `.vscode` to `.gitignore`. w3c/vc-di-ed25519signature2020-test-suite#47, by @JSAssassin.
-
Add default key seed for key gen. w3c/vc-di-ed25519signature2020-test-suite#46, by @aljones15.
-
Unpin node in gh actions. w3c/vc-di-ed25519signature2020-test-suite#45, by @JSAssassin.
-
-
2 pull requests merged.
-
Add default key seed for key gen. w3c/vc-di-ed25519signature2020-test-suite#46.
-
Unpin node in gh actions. w3c/vc-di-ed25519signature2020-test-suite#45.
-
w3c/vc-di-bbs-test-suite
-
3 pull requests opened.
-
Cleanup (Removes remaining ECDSA related terms and key types) w3c/vc-di-bbs-test-suite#3, by @JSAssassin.
-
Update implementations package w3c/vc-di-bbs-test-suite#2, by @JSAssassin.
-
Removes `ecdsa-rdfc` tests and replaces the term `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-bbs-test-suite#1, by @JSAssassin.
-
-
2 pull requests merged.
-
Update implementations package w3c/vc-di-bbs-test-suite#2.
-
Removes `ecdsa-rdfc` tests and replaces the term `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-bbs-test-suite#1.
-
-
2 pull requests received 4 new comments.
-
Cleanup (Removes remaining ECDSA related terms and key types) w3c/vc-di-bbs-test-suite#3 (2 comments by @BigBlueHat, @JSAssassin)
-
Removes `ecdsa-rdfc` tests and replaces the term `ecdsa-sd-2023` with `bbs-2023` w3c/vc-di-bbs-test-suite#1 (2 comments by @BigBlueHat)
-
w3c/vc-di-bbs
-
4 issues opened.
-
Selective disclosure of identified nodes w3c/vc-di-bbs#107, by @dwaite.
-
Security and Privacy Self Review w3c/vc-di-bbs#106, by @Wind4Greg.
-
Internationalization Review for VC DI BBS w3c/vc-di-bbs#103, by @Wind4Greg.
-
Accessibility Self-Review for VC DI BBS w3c/vc-di-bbs#102, by @Wind4Greg.
-
-
19 issues closed.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-bbs#92.
-
Hashing (bbs-proof-2023) w3c/vc-di-bbs#84.
-
Define: Transformation (bbs-proof-2023) w3c/vc-di-bbs#83.
-
Define: Verify Proof (bbs-proof-2023) w3c/vc-di-bbs#82.
-
Define: Add Proof (bbs-proof-2023) w3c/vc-di-bbs#81.
-
Use CBOR to compress `proof` w3c/vc-di-bbs#80.
-
Add Support For Bound Signatures w3c/vc-di-bbs#79.
-
Need separate cryptosuite for `signature` and `proof` w3c/vc-di-bbs#75.
-
Signature/proof formats are undocumented w3c/vc-di-bbs#61.
-
Blank node labels may leak information w3c/vc-di-bbs#60.
-
Require certain statements to be revealed in a proof w3c/vc-di-bbs#28.
-
Required reveal statements w3c/vc-di-bbs#23.
-
The application of blank node identifiers w3c/vc-di-bbs#10.
-
Included rationale for `requiredRevealStatements` w3c/vc-di-bbs#3.
-
Reuse ECDSA-SD Primitives where Possible, Use JSON Pointers w3c/vc-di-bbs#93.
-
Update JWK examples to match the BLS JWK draft w3c/vc-di-bbs#58.
-
-
20 issues received 34 new comments.
-
Selective disclosure of identified nodes w3c/vc-di-bbs#107 (9 comments by @dlongley, @dwaite, @Wind4Greg)
-
Apparent inconsistency in `proofValue` examples & normative multibase statement w3c/vc-di-bbs#95 (4 comments by @AFlowOfCode, @dlongley, @Wind4Greg)
-
Hosted JSON-LD context should expose itself as `ld+json` instead of `json` w3c/vc-di-bbs#90 (1 comment by @Wind4Greg)
-
Define: Proof Configuration, Serialization, Verification (bbs-proof-2023) w3c/vc-di-bbs#85 (1 comment by @Wind4Greg)
-
-
3 pull requests opened.
-
Add Explainer w3c/vc-di-bbs#105, by @Wind4Greg.
-
Add Privacy Considerations Section w3c/vc-di-bbs#104, by @Wind4Greg.
-
Privacy Considerations w3c/vc-di-bbs#101, by @Wind4Greg.
-
-
3 pull requests merged.
-
Add Explainer w3c/vc-di-bbs#105.
-
Add Privacy Considerations Section w3c/vc-di-bbs#104.
-
Add Security Considerations Section w3c/vc-di-bbs#100.
-
-
1 pull request closed.
-
Privacy Considerations w3c/vc-di-bbs#101.
-
-
3 pull requests received 16 new comments.
w3c/vc-json-schema
-
2 pull requests opened.
-
add Mike Prorock to editor list w3c/vc-json-schema#232, by @mprorock.
-
Remove myself as editor w3c/vc-json-schema#231, by @OR13.
-
-
3 pull requests merged.
-
Remove myself as editor w3c/vc-json-schema#231.
-
add Mike Prorock to editor list w3c/vc-json-schema#232.
-
Update auto-publish.yml w3c/vc-json-schema#230.
-
-
2 pull requests received 9 new comments.
-
add Mike Prorock to editor list w3c/vc-json-schema#232 (6 comments by @iherman, @mprorock, @TallTed, @thereisnogabe)
-
w3c/vc-bitstring-status-list-test-suite
-
2 pull requests opened.
-
Update implementations package. w3c/vc-bitstring-status-list-test-suite#32, by @JSAssassin.
-
Unpin node in gh actions. w3c/vc-bitstring-status-list-test-suite#31, by @JSAssassin.
-
-
2 pull requests merged.
-
Update implementations package. w3c/vc-bitstring-status-list-test-suite#32.
-
Unpin node in gh actions. w3c/vc-bitstring-status-list-test-suite#31.
-
w3c/vcalm
-
1 issue opened.
-
signing VC in sd-jwt format w3c/vcalm#357, by @ThierryThevenet.
-
-
1 issue closed.
-
Should vc http api use PE Spec for query format? w3c/vcalm#174.
-
-
10 issues received 14 new comments.
-
Support BitstringStatusList (was: StatusList2021, was: RevocationStatus2020) w3c/vcalm#214 (2 comments by @msporny)
-
BbsBls sig test fixtures (valid by various W3C docs) not permitted by current OpenAPI spec w3c/vcalm#194 (1 comment by @msporny)
-
PROPOSAL: Spec will recommend AGAINST Issuer <> Verifier flows over https w3c/vcalm#186 (1 comment by @msporny)
-
6 pull requests opened.
-
Ignore package-lock.json. w3c/vcalm#356, by @BigBlueHat.
-
Fix OpenAPI validity & publishing. w3c/vcalm#355, by @BigBlueHat.
-
Update workflows to Node v20.x; use latest actions w3c/vcalm#354, by @BigBlueHat.
-
Fix, clarify, or update links in README. w3c/vcalm#352, by @BigBlueHat.
-
Add text about base URL. Fix #244. w3c/vcalm#351, by @BigBlueHat.
-
-
5 pull requests received 8 new comments.
-
added Workflow system in introduction, both to the diagram and the prose w3c/vcalm#353 (2 comments by @TallTed)
w3c/vc-test-suite
-
1 issue opened.
-
Add tests that verifiers reject non-compact JSON-LD representations w3c/vc-test-suite#136, by @jyasskin.
-
w3c/vc-use-cases
-
2 pull requests received 3 new comments.
-
updated verify claim and added validate claim. images updated w3c/vc-use-cases#149 (2 comments by @jandrieu)
-
w3c/vc-extensions
-
1 pull request opened.
-
Rename status-list-2021 to bitstring-status-list w3c/vc-extensions#31, by @jyasskin.
-
-
2 pull requests merged.
-
Rename status-list-2021 to bitstring-status-list w3c/vc-extensions#31.
-
Adds a "Securing Mechanisms" section to the directory w3c/vc-extensions#30.
-
-
2 pull requests received 3 new comments.
-
Adds a "Securing Mechanisms" section to the directory w3c/vc-extensions#30 (2 comments by @iherman, @msporny)
-
w3c/cid
-
1 issue received 1 new comment.
TR publications
-
19 documents published.
-
Data Integrity ECDSA Cryptosuites v1.0 published as a Candidate Recommendation Snapshot. History of Data Integrity ECDSA Cryptosuites v1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published as a Candidate Recommendation Snapshot. History of Data Integrity EdDSA Cryptosuites v1.0
-
Verifiable Credential Data Integrity 1.0 published as a Candidate Recommendation Snapshot. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials JSON Schema Specification published as a Candidate Recommendation Snapshot. History of Verifiable Credentials JSON Schema Specification
-
Verifiable Credentials Data Model v2.0 published 4 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Securing Verifiable Credentials using JOSE and COSE published twice as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
Bitstring Status List v1.0 published as a Working Draft. History of Bitstring Status List v1.0
-
Verifiable Credentials JSON Schema Specification published 5 times as a Working Draft. History of Verifiable Credentials JSON Schema Specification
-
BBS Cryptosuite v2023 published as a Working Draft. History of BBS Cryptosuite v2023
-
Data Integrity ECDSA Cryptosuites v1.0 published as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published as a Working Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Past meetings
Participants
-
3 participants joined.
-
Nas Hajia (Autodesk) joined.
-
Samuel Schlesinger (Google LLC) joined.
-
Cole Davis (Switchchord) joined.
-
-
1 participant left.
-
Mary Dwyer (Dfinity Stiftung) left.
-
-
2 organizations joined.
-
Autodesk joined.
-
Switchchord joined.
-
GitHub
w3c/vc-data-model
-
15 issues opened.
-
Clarify the domain and range of the `verifiablePresentation.verifiableCredential` property w3c/vc-data-model#1366, by @andresuribe87.
-
Clarify section on verifiable credential graph w3c/vc-data-model#1365, by @andresuribe87.
-
Do VCs still need Media Types with Multiple Suffixes? w3c/vc-data-model#1364, by @jyasskin.
-
Request profile parameter from `application/vc` w3c/vc-data-model#1363, by @OR13.
-
Improve Verification Algorithms section w3c/vc-data-model#1362, by @msporny.
-
Add mechanism to cryptographically secure non-credential VP properties (contexts etc) w3c/vc-data-model#1360, by @dmitrizagidulin.
-
Authorized Presenters w3c/vc-data-model#1359, by @thereisnogabe.
-
Add mechanism to embed externally secured VCs in a VP w3c/vc-data-model#1352, by @brentzundel.
-
Non-normative changes from Jeffrey Yasskin's review w3c/vc-data-model#1348, by @msporny.
-
Normative changes from Jeffrey Yasskin's review w3c/vc-data-model#1347, by @msporny.
-
Confused by "all times MUST be specified as offsets against Universal Coordinated Time (UTC)." w3c/vc-data-model#1343, by @jyasskin.
-
Issuer appears to be defined using a non-JSON-LD data model w3c/vc-data-model#1342, by @jyasskin.
-
credentialSubject doesn't say how to identify the "subjects" of the verifiable credential. w3c/vc-data-model#1341, by @jyasskin.
-
Define algorithm for verification w3c/vc-data-model#1337, by @msporny.
-
Recommend how authors set default language and direction w3c/vc-data-model#1335, by @msporny.
-
-
32 issues closed.
-
Normative changes from Jeffrey Yasskin's review w3c/vc-data-model#1347.
-
Add `relatedResource` to `VerifiablePresentation` w3c/vc-data-model#1265.
-
Prefer Arrays and Objects. w3c/vc-data-model#1292.
-
Add @TallTed and @iherman to Editors list w3c/vc-data-model#1273.
-
Confused by "all times MUST be specified as offsets against Universal Coordinated Time (UTC)." w3c/vc-data-model#1343.
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247.
-
Address Metadata-Driven Correlation w3c/vc-data-model#1244.
-
Issuer appears to be defined using a non-JSON-LD data model w3c/vc-data-model#1342.
-
credentialSubject doesn't say how to identify the "subjects" of the verifiable credential. w3c/vc-data-model#1341.
-
Recommend how authors set default language and direction w3c/vc-data-model#1335.
-
Clarify what conformance means to the issuers/verifiers w3c/vc-data-model#1300.
-
Recommend that authors don't use `@base` in `@context` w3c/vc-data-model#1266.
-
NIST defines "credential" differently w3c/vc-data-model#1047.
-
Pre-CR review from Jeffrey Yasskin w3c/vc-data-model#1285.
-
Document the value of processing as JSON-LD w3c/vc-data-model#1227.
-
W3C Caused by: com.apicatalog.jsonld.JsonLdError: Unexpected response code [429] w3c/vc-data-model#1330.
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206.
-
Controller Documents w3c/vc-data-model#1307.
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010.
-
Allow string values in JOSE properties in base JSON-LD context w3c/vc-data-model#1275.
-
Encourage the use of OHTTP w3c/vc-data-model#1267.
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264.
-
Updating figures 6 and 7 w3c/vc-data-model#1318.
-
signatures should be on quoted graphs w3c/vc-data-model#1248.
-
Add cryptographic hashes for vocabulary files w3c/vc-data-model#1261.
-
Add Security Consideration to avoid key reuse w3c/vc-data-model#1284.
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246.
-
Revert language change on the definition of Subject w3c/vc-data-model#1235.
-
Revisit validation vs verification w3c/vc-data-model#1232.
-
Conformance requirements for normative context w3c/vc-data-model#1185.
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959.
-
Internationalization Review for VCDM 2.0 w3c/vc-data-model#1155.
-
-
1 issue reopened.
-
Internationalization Review for VCDM 2.0 w3c/vc-data-model#1155, by @iherman.
-
-
48 issues received 156 new comments.
-
Add VC-JWT diagrams to core specification w3c/vc-data-model#1135 (15 comments by @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Cross-check the `domain`/`range` statements in the vocabulary with the VCDM spec w3c/vc-data-model#1319 (12 comments by @iherman, @msporny, @TallTed)
-
Add `relatedResource` to `VerifiablePresentation` w3c/vc-data-model#1265 (10 comments by @brentzundel, @dmitrizagidulin, @iherman, @msporny, @OR13)
-
Consider mandating securing RDF graph for all securing mechanisms w3c/vc-data-model#1327 (9 comments by @alenhorvat, @awoie, @mtaimela, @peacekeeper)
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290 (8 comments by @awoie, @brentzundel, @iherman, @jandrieu, @msporny)
-
Confused by "all times MUST be specified as offsets against Universal Coordinated Time (UTC)." w3c/vc-data-model#1343 (8 comments by @aphillips, @jyasskin, @msporny)
-
Issuer appears to be defined using a non-JSON-LD data model w3c/vc-data-model#1342 (7 comments by @jyasskin, @msporny, @seabass-labrax)
-
Request profile parameter from `application/vc` w3c/vc-data-model#1363 (6 comments by @iherman, @OR13, @selfissued)
-
Add mechanism to cryptographically secure non-credential VP properties (contexts etc) w3c/vc-data-model#1360 (5 comments by @dmitrizagidulin, @iherman, @OR13)
-
Recommend how authors set default language and direction w3c/vc-data-model#1335 (4 comments by @aphillips, @msporny)
-
Improve Verification Algorithms section w3c/vc-data-model#1362 (3 comments by @iherman, @OR13, @selfissued)
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247 (3 comments by @iherman, @msporny)
-
credentialSubject doesn't say how to identify the "subjects" of the verifiable credential. w3c/vc-data-model#1341 (3 comments by @msporny)
-
Clarify what conformance means to the issuers/verifiers w3c/vc-data-model#1300 (3 comments by @iherman, @msporny)
-
Do VCs still need Media Types with Multiple Suffixes? w3c/vc-data-model#1364 (2 comments by @OR13, @selfissued)
-
Use a better example for bidirectional text (Editorial) w3c/vc-data-model#1313 (2 comments by @aphillips, @TallTed)
-
Recommend that authors don't use `@base` in `@context` w3c/vc-data-model#1266 (1 comment by @msporny)
-
Include credentialSubject examples that use URLs rather than DIDs w3c/vc-data-model#1309 (1 comment by @msporny)
-
Allow string values in JOSE properties in base JSON-LD context w3c/vc-data-model#1275 (1 comment by @msporny)
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264 (1 comment by @msporny)
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246 (1 comment by @msporny)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @msporny)
-
Consider abandoning drafts for non-data-integrity-proof securing formats w3c/vc-data-model#1315 (1 comment by @TallTed)
-
clarify relationship to the `proof` property and the specifications defining how to secure VCs w3c/vc-data-model#1312 (1 comment by @iherman)
-
-
19 pull requests opened.
-
Update context to match spec for name/description. w3c/vc-data-model#1367, by @BigBlueHat.
-
Remove unnecessary vocab comments in vocabulary.yml w3c/vc-data-model#1361, by @iherman.
-
Add mechanism to embed enveloped VCs in VPs. w3c/vc-data-model#1358, by @msporny.
-
Address @jyasskin's pre-Candidate Recommendation review comments w3c/vc-data-model#1357, by @msporny.
-
Add section on Data Theft to Privacy Considerations. w3c/vc-data-model#1356, by @msporny.
-
Add section on metadata-based correlation. w3c/vc-data-model#1355, by @msporny.
-
Update Editors to reflect contributions. w3c/vc-data-model#1354, by @msporny.
-
Massaging text for default language and direction w3c/vc-data-model#1353, by @TallTed.
-
Update JSON Processing section to Credential-Type-Specific Processing. w3c/vc-data-model#1351, by @msporny.
-
(editorial) Assorted grammar, markup, source formatting, etc. w3c/vc-data-model#1350, by @TallTed.
-
Update normative language related to issuer value. w3c/vc-data-model#1349, by @msporny.
-
Clarify credentialSubject requirements to improve testability. w3c/vc-data-model#1346, by @msporny.
-
catching omissions from change requests on #1295 w3c/vc-data-model#1345, by @TallTed.
-
Clarify normative statement related to timezone offsets. w3c/vc-data-model#1344, by @msporny.
-
Use JSON-LD keywords for languages. w3c/vc-data-model#1340, by @BigBlueHat.
-
Explain default language expression. w3c/vc-data-model#1339, by @BigBlueHat.
-
Add verification algorithm to specification. w3c/vc-data-model#1338, by @msporny.
-
Add conformance classes for issuers and verifiers. w3c/vc-data-model#1336, by @msporny.
-
Rebase PR #1297 w3c/vc-data-model#1334, by @msporny.
-
-
22 pull requests merged.
-
Address @jyasskin's pre-Candidate Recommendation review comments w3c/vc-data-model#1357.
-
Add section on Data Theft to Privacy Considerations. w3c/vc-data-model#1356.
-
Add section on metadata-based correlation. w3c/vc-data-model#1355.
-
Update Editors to reflect contributions. w3c/vc-data-model#1354.
-
Massaging text for default language and direction w3c/vc-data-model#1353.
-
Update JSON Processing section to Credential-Type-Specific Processing. w3c/vc-data-model#1351.
-
Update normative language related to issuer value. w3c/vc-data-model#1349.
-
Use JSON-LD keywords for languages. w3c/vc-data-model#1340.
-
Clarify normative statement related to timezone offsets. w3c/vc-data-model#1344.
-
(editorial) Assorted grammar, markup, source formatting, etc. w3c/vc-data-model#1350.
-
Clarify credentialSubject requirements to improve testability. w3c/vc-data-model#1346.
-
catching omissions from change requests on #1295 w3c/vc-data-model#1345.
-
Explain default language expression. w3c/vc-data-model#1339.
-
Add conformance classes for issuers and verifiers. w3c/vc-data-model#1336.
-
Warn that using dynamic processor features might lead to less interoperability w3c/vc-data-model#1276.
-
Warn authors that usage of global JSON-LD keywords might harm interoperability w3c/vc-data-model#1271.
-
Add comparison to NIST definition w3c/vc-data-model#1332.
-
Improve the explanation of using graphs in VCDM w3c/vc-data-model#1326.
-
Rebase PR #1297 w3c/vc-data-model#1334.
-
Update to Terms of Use description w3c/vc-data-model#1295.
-
Add links to static copies of vocabulary files and hashes w3c/vc-data-model#1279.
-
Add section on key management. w3c/vc-data-model#1323.
-
-
5 pull requests closed.
-
Add comment on localizing vocabulary terms. w3c/vc-data-model#1333.
-
Additional updates regarding proof w3c/vc-data-model#1317.
-
First pass at updating validation language w3c/vc-data-model#1297.
-
Remove JSON Processing section w3c/vc-data-model#1298.
-
Align JWT/JWS fields with IETF RFCs. w3c/vc-data-model#1325.
-
-
31 pull requests received 415 new comments.
-
Add verification algorithm to specification. w3c/vc-data-model#1338 (166 comments by @andresuribe87, @dlongley, @iherman, @jyasskin, @msporny, @OR13, @selfissued, @TallTed)
-
Use JSON-LD keywords for languages. w3c/vc-data-model#1340 (22 comments by @aphillips, @BigBlueHat, @msporny, @TallTed)
-
Explain default language expression. w3c/vc-data-model#1339 (21 comments by @aphillips, @BigBlueHat, @dlongley, @iherman, @jandrieu, @msporny, @TallTed)
-
Update to Terms of Use description w3c/vc-data-model#1295 (21 comments by @David-Chadwick, @iherman, @msporny, @TallTed)
-
Propose better JSON-LD processing text w3c/vc-data-model#1302 (18 comments by @iherman, @OR13, @TallTed)
-
Warn that using dynamic processor features might lead to less interoperability w3c/vc-data-model#1276 (17 comments by @David-Chadwick, @iherman, @msporny, @TallTed)
-
Add comparison to NIST definition w3c/vc-data-model#1332 (15 comments by @andresuribe87, @brentzundel, @dlongley, @iherman, @jandrieu, @longpd, @OR13, @TallTed)
-
Update normative language related to issuer value. w3c/vc-data-model#1349 (14 comments by @jyasskin, @msporny, @OR13, @TallTed)
-
Address @jyasskin's pre-Candidate Recommendation review comments w3c/vc-data-model#1357 (13 comments by @iherman, @jyasskin, @msporny, @TallTed, @thereisnogabe)
-
Clarify normative statement related to timezone offsets. w3c/vc-data-model#1344 (12 comments by @aphillips, @dlongley, @iherman, @jandrieu, @msporny, @TallTed)
-
Add conformance classes for issuers and verifiers. w3c/vc-data-model#1336 (12 comments by @andresuribe87, @David-Chadwick, @iherman, @msporny, @seabass-labrax, @TallTed, @thereisnogabe)
-
Add mechanism to embed enveloped VCs in VPs. w3c/vc-data-model#1358 (11 comments by @andresuribe87, @dlongley, @iherman, @longpd, @msporny)
-
Update JSON Processing section to Credential-Type-Specific Processing. w3c/vc-data-model#1351 (10 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add comment on localizing vocabulary terms. w3c/vc-data-model#1333 (8 comments by @iherman, @msporny, @OR13, @TallTed)
-
Add section on Data Theft to Privacy Considerations. w3c/vc-data-model#1356 (8 comments by @dlongley, @kdenhartog, @msporny, @TallTed)
-
Add section on metadata-based correlation. w3c/vc-data-model#1355 (7 comments by @dlongley, @msporny, @TallTed)
-
Clarify credentialSubject requirements to improve testability. w3c/vc-data-model#1346 (7 comments by @dlongley, @jyasskin, @msporny)
-
First pass at updating validation language w3c/vc-data-model#1297 (7 comments by @brentzundel, @iherman, @jandrieu, @msporny, @TallTed)
-
(editorial) Assorted grammar, markup, source formatting, etc. w3c/vc-data-model#1350 (6 comments by @iherman, @msporny, @TallTed)
-
Update Editors to reflect contributions. w3c/vc-data-model#1354 (4 comments by @iherman, @msporny, @TallTed)
-
Warn authors that usage of global JSON-LD keywords might harm interoperability w3c/vc-data-model#1271 (4 comments by @iherman, @msporny, @TallTed)
-
Improve the explanation of using graphs in VCDM w3c/vc-data-model#1326 (2 comments by @iherman, @msporny)
-
Add links to static copies of vocabulary files and hashes w3c/vc-data-model#1279 (1 comment by @brentzundel)
-
w3c/vc-jose-cose
-
9 issues opened.
-
Should JOSE/COSE verification strip out or inline @context values? w3c/vc-jose-cose#188, by @jyasskin.
-
Write an algorithm for verifying VC/VP JWTs w3c/vc-jose-cose#187, by @jyasskin.
-
Adjust Explicit Typing Guidance regarding `typ` w3c/vc-jose-cose#184, by @OR13.
-
Add COSE Example w3c/vc-jose-cose#182, by @OR13.
-
Update normative guidance for `vc` and `vp` claims w3c/vc-jose-cose#180, by @OR13.
-
Change the registration request for SD-JWT w3c/vc-jose-cose#179, by @OR13.
-
Add comments on encryption re:OpenID w3c/vc-jose-cose#175, by @thereisnogabe.
-
Add examples for COSE Sign1 Detached Payloads w3c/vc-jose-cose#174, by @thereisnogabe.
-
Add a reference to Data Integrity Specification Registries when it exists w3c/vc-jose-cose#173, by @thereisnogabe.
-
-
7 issues closed.
-
Update normative guidance for `vc` and `vp` claims w3c/vc-jose-cose#180.
-
Example does not correspond to description in section 5.3.1 w3c/vc-jose-cose#167.
-
Broken links to iss w3c/vc-jose-cose#168.
-
Missing word and missing referent in section 2 w3c/vc-jose-cose#169.
-
Add a reference to Data Integrity Specification Registries when it exists w3c/vc-jose-cose#173.
-
Remove internationalization considerations section? w3c/vc-jose-cose#172.
-
credentialSchema property not fully correct in PR#159 examples w3c/vc-jose-cose#164.
-
-
12 issues received 29 new comments.
-
Change the registration request for SD-JWT w3c/vc-jose-cose#179 (7 comments by @msporny, @OR13, @selfissued, @TallTed)
-
credentialSchema property not fully correct in PR#159 examples w3c/vc-jose-cose#164 (5 comments by @David-Chadwick, @TallTed, @thereisnogabe)
-
Add a reference to Data Integrity Specification Registries when it exists w3c/vc-jose-cose#173 (4 comments by @msporny, @thereisnogabe)
-
Should JOSE/COSE verification strip out or inline @context values? w3c/vc-jose-cose#188 (2 comments by @OR13)
-
Example does not correspond to description in section 5.3.1 w3c/vc-jose-cose#167 (1 comment by @thereisnogabe)
-
Update normative guidance for `vc` and `vp` claims w3c/vc-jose-cose#180 (1 comment by @thereisnogabe)
-
-
9 pull requests opened.
-
Add placeholder algorithms w3c/vc-jose-cose#190, by @OR13.
-
Update references w3c/vc-jose-cose#189, by @selfissued.
-
Remove requests for multiple suffixes w3c/vc-jose-cose#186, by @OR13.
-
Add COSE examples w3c/vc-jose-cose#185, by @OR13.
-
Remove duplicate descriptive language w3c/vc-jose-cose#183, by @selfissued.
-
Disallow vc and vp claims in head or payloads w3c/vc-jose-cose#181, by @thereisnogabe.
-
(editorial) improve language by inverting a couple of parentheticals w3c/vc-jose-cose#178, by @TallTed.
-
(editorial) fix some typos, markup, and punctuation w3c/vc-jose-cose#177, by @TallTed.
-
Fix a few issues, formatting, issue tagging w3c/vc-jose-cose#176, by @thereisnogabe.
-
-
4 pull requests merged.
-
Disallow vc and vp claims in head or payloads w3c/vc-jose-cose#181.
-
(editorial) improve language by inverting a couple of parentheticals w3c/vc-jose-cose#178.
-
(editorial) fix some typos, markup, and punctuation w3c/vc-jose-cose#177.
-
Fix a few issues, formatting, issue tagging w3c/vc-jose-cose#176.
-
-
5 pull requests received 52 new comments.
-
Remove duplicate descriptive language w3c/vc-jose-cose#183 (21 comments by @OR13, @selfissued, @TallTed, @thereisnogabe)
-
Remove requests for multiple suffixes w3c/vc-jose-cose#186 (13 comments by @andresuribe87, @OR13, @selfissued, @TallTed)
-
Fix a few issues, formatting, issue tagging w3c/vc-jose-cose#176 (8 comments by @OR13, @TallTed, @thereisnogabe)
-
Disallow vc and vp claims in head or payloads w3c/vc-jose-cose#181 (3 comments by @OR13, @selfissued, @thereisnogabe)
-
w3c/vc-bitstring-status-list-test-suite
-
1 issue opened.
-
Rename test suite & tag to align with the change in spec name. w3c/vc-bitstring-status-list-test-suite#26, by @JSAssassin.
-
-
4 pull requests opened.
-
Pin node version in gh actions and use latest versions. w3c/vc-bitstring-status-list-test-suite#30, by @JSAssassin.
-
Fix assertion for contexts and use `vc-api-test-suite-implementations` with latest DB implementations w3c/vc-bitstring-status-list-test-suite#29, by @JSAssassin.
-
Export template data w3c/vc-bitstring-status-list-test-suite#28, by @aljones15.
-
Pin node to v20.8.0. w3c/vc-bitstring-status-list-test-suite#27, by @BigBlueHat.
-
-
4 pull requests merged.
-
Pin node version in gh actions and use latest versions. w3c/vc-bitstring-status-list-test-suite#30.
-
Fix assertion for contexts and use `vc-api-test-suite-implementations` with latest DB implementations w3c/vc-bitstring-status-list-test-suite#29.
-
Export template data w3c/vc-bitstring-status-list-test-suite#28.
-
Pin node to v20.8.0. w3c/vc-bitstring-status-list-test-suite#27.
-
-
2 pull requests received 3 new comments.
-
Fix assertion for contexts and use `vc-api-test-suite-implementations` with latest DB implementations w3c/vc-bitstring-status-list-test-suite#29 (2 comments by @BigBlueHat, @JSAssassin)
-
w3c/vc-di-eddsa-test-suite
-
2 issues opened.
-
Links to implementations w3c/vc-di-eddsa-test-suite#25, by @HelgeKrueger.
-
Switch gh actions node version back to 20.x w3c/vc-di-eddsa-test-suite#22, by @JSAssassin.
-
-
1 issue closed.
-
Switch gh actions node version back to 20.x w3c/vc-di-eddsa-test-suite#22.
-
-
1 issue received 1 new comment.
-
Switch gh actions node version back to 20.x w3c/vc-di-eddsa-test-suite#22 (1 comment by @JSAssassin)
-
-
3 pull requests opened.
-
Pin node version and upgrade actions to latest versions. w3c/vc-di-eddsa-test-suite#26, by @JSAssassin.
-
Updates tag names required to run the test suite. w3c/vc-di-eddsa-test-suite#24, by @JSAssassin.
-
Export template data w3c/vc-di-eddsa-test-suite#23, by @aljones15.
-
-
4 pull requests merged.
-
Pin node version and upgrade actions to latest versions. w3c/vc-di-eddsa-test-suite#26.
-
Update tests w3c/vc-di-eddsa-test-suite#21.
-
Updates tag names required to run the test suite. w3c/vc-di-eddsa-test-suite#24.
-
Export template data w3c/vc-di-eddsa-test-suite#23.
-
-
2 pull requests received 8 new comments.
-
Updates tag names required to run the test suite. w3c/vc-di-eddsa-test-suite#24 (1 comment by @TallTed)
w3c/vc-di-ed25519signature2020-test-suite
-
4 pull requests opened.
-
Update gh actions and pin node version back. w3c/vc-di-ed25519signature2020-test-suite#44, by @JSAssassin.
-
Switch node version to 20.x in gh actions. w3c/vc-di-ed25519signature2020-test-suite#43, by @JSAssassin.
-
Export template data w3c/vc-di-ed25519signature2020-test-suite#42, by @JSAssassin.
-
Pin node to v20.8.0. w3c/vc-di-ed25519signature2020-test-suite#41, by @BigBlueHat.
-
-
4 pull requests merged.
-
Update gh actions and pin node version back. w3c/vc-di-ed25519signature2020-test-suite#44.
-
Switch node version to 20.x in gh actions. w3c/vc-di-ed25519signature2020-test-suite#43.
-
Export template data w3c/vc-di-ed25519signature2020-test-suite#42.
-
Pin node to v20.8.0. w3c/vc-di-ed25519signature2020-test-suite#41.
-
w3c/vc-di-ecdsa-test-suite
-
3 issues opened.
-
Switch gh actions node version back to 20.x w3c/vc-di-ecdsa-test-suite#17, by @JSAssassin.
-
Evaluate if the current tests are sufficient / accurate for addressing the following normative statements in the spec w3c/vc-di-ecdsa-test-suite#16, by @JSAssassin.
-
Consider moving the following tests into `data-integrity-test-suite-assertion` library w3c/vc-di-ecdsa-test-suite#15, by @JSAssassin.
-
-
1 issue closed.
-
Switch gh actions node version back to 20.x w3c/vc-di-ecdsa-test-suite#17.
-
-
1 issue received 1 new comment.
-
Switch gh actions node version back to 20.x w3c/vc-di-ecdsa-test-suite#17 (1 comment by @JSAssassin)
-
-
4 pull requests opened.
-
Use latest `setup-node` and `checkout` actions v4 and pin node version in gh actions w3c/vc-di-ecdsa-test-suite#21, by @JSAssassin.
-
Adds `ecdsa-sd-2023` tests. w3c/vc-di-ecdsa-test-suite#20, by @JSAssassin.
-
Update tags required to run the tests and the report structure. w3c/vc-di-ecdsa-test-suite#19, by @JSAssassin.
-
Add template data w3c/vc-di-ecdsa-test-suite#18, by @aljones15.
-
-
5 pull requests merged.
-
Use latest `setup-node` and `checkout` actions v4 and pin node version in gh actions w3c/vc-di-ecdsa-test-suite#21.
-
Adds `ecdsa-sd-2023` tests. w3c/vc-di-ecdsa-test-suite#20.
-
Update tests. w3c/vc-di-ecdsa-test-suite#13.
-
Update tags required to run the tests and the report structure. w3c/vc-di-ecdsa-test-suite#19.
-
Add template data w3c/vc-di-ecdsa-test-suite#18.
-
-
3 pull requests received 19 new comments.
-
Update tags required to run the tests and the report structure. w3c/vc-di-ecdsa-test-suite#19 (9 comments by @BigBlueHat, @JSAssassin, @TallTed)
-
w3c/vcalm
-
1 issue received 4 new comments.
-
Clarification on endpoints style for issuance , verification and derivation w3c/vcalm#343 (4 comments by @BigBlueHat, @dlongley, @jruizaranguren, @msporny)
-
-
3 pull requests opened.
-
add PR tips to CONTRIBUTING.md w3c/vcalm#350, by @jrhender.
-
Add Privacy Considerations section on "phone home". w3c/vcalm#349, by @msporny.
-
Bump specification version to v0.4. w3c/vcalm#348, by @msporny.
-
-
1 pull request closed.
-
Bump specification version to v0.4. w3c/vcalm#348.
-
-
3 pull requests received 21 new comments.
-
Add Privacy Considerations section on "phone home". w3c/vcalm#349 (10 comments by @David-Chadwick, @TallTed)
-
w3c/vc-di-bbs
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Add Security Considerations Section w3c/vc-di-bbs#100, by @Wind4Greg.
-
Rebased version of PR #94 w3c/vc-di-bbs#99, by @msporny.
-
-
2 pull requests merged.
-
Removing myself (tobias) as editor w3c/vc-di-bbs#97.
-
Rebased version of PR #94 w3c/vc-di-bbs#99.
-
-
2 pull requests closed.
-
Update to use JSON Pointers and Selective Disclosure Primitives w3c/vc-di-bbs#94.
-
Wind4 greg sd primitives w3c/vc-di-bbs#98.
-
-
4 pull requests received 5 new comments.
-
Update to use JSON Pointers and Selective Disclosure Primitives w3c/vc-di-bbs#94 (2 comments by @msporny)
-
w3c/vc-data-model-2.0-test-suite
-
3 pull requests opened.
-
Unpin node 20.8 w3c/vc-data-model-2.0-test-suite#39, by @aljones15.
-
Export template data w3c/vc-data-model-2.0-test-suite#38, by @aljones15.
-
Pin node to v20.8.0. w3c/vc-data-model-2.0-test-suite#37, by @BigBlueHat.
-
-
3 pull requests merged.
-
Unpin node 20.8 w3c/vc-data-model-2.0-test-suite#39.
-
Pin node to v20.8.0. w3c/vc-data-model-2.0-test-suite#37.
-
Export template data w3c/vc-data-model-2.0-test-suite#38.
-
-
2 pull requests received 2 new comments.
w3c/vc-test-suite-implementations
-
3 pull requests opened.
-
Use JSON & example.com URLs in README. w3c/vc-test-suite-implementations#6, by @BigBlueHat.
-
Update tag names for ecdsa and eddsa test suites. w3c/vc-test-suite-implementations#5, by @JSAssassin.
-
Add .gitignore to exclude node_modules/. w3c/vc-test-suite-implementations#4, by @BigBlueHat.
-
-
3 pull requests merged.
-
Update tag names for ecdsa and eddsa test suites. w3c/vc-test-suite-implementations#5.
-
Use JSON & example.com URLs in README. w3c/vc-test-suite-implementations#6.
-
Add .gitignore to exclude node_modules/. w3c/vc-test-suite-implementations#4.
-
-
1 pull request received 5 new comments.
-
Update tag names for ecdsa and eddsa test suites. w3c/vc-test-suite-implementations#5 (5 comments by @BigBlueHat, @JSAssassin)
-
w3c/vc-extensions
-
1 pull request opened.
-
Adds a "Securing Mechanisms" section to the directory w3c/vc-extensions#30, by @msporny.
-
-
1 pull request merged.
-
Update and rename credential-schema-2023.json to credential-schema.json w3c/vc-extensions#29.
-
-
1 pull request received 5 new comments.
-
Adds a "Securing Mechanisms" section to the directory w3c/vc-extensions#30 (5 comments by @jyasskin, @OR13, @selfissued)
-
w3c/vc-test-suite
-
1 issue opened.
-
Inputs For Verifiable Credentials with `proof` properties Do Not Match Data Integrity Specs w3c/vc-test-suite#135, by @LuisOsta.
-
-
3 issues received 3 new comments.
-
Inputs For Verifiable Credentials with `proof` properties Do Not Match Data Integrity Specs w3c/vc-test-suite#135 (1 comment by @LuisOsta)
-
-
1 pull request received 1 new comment.
w3c/vc-use-cases
-
2 pull requests opened.
-
GS1 identification use case w3c/vc-use-cases#151, by @ghost.
-
Refactored examples to use inclusion w3c/vc-use-cases#150, by @ghost.
-
-
1 pull request merged.
-
Refactored examples to use inclusion w3c/vc-use-cases#150.
-
-
2 pull requests received 16 new comments.
-
GS1 identification use case w3c/vc-use-cases#151 (11 comments by @paulfdietrich, @TallTed, @tsnyder-gs1us)
-
updated verify claim and added validate claim. images updated w3c/vc-use-cases#149 (5 comments by @TallTed)
-
w3c/vc-bitstring-status-list
-
2 issues opened.
-
Precise timestamps of status changes w3c/vc-bitstring-status-list#94, by @thereisnogabe.
-
Align bitstring structure and IETF Token Status List structure? w3c/vc-bitstring-status-list#93, by @brentzundel.
-
-
1 issue closed.
-
Rename specification to "Herd Privacy Status List" w3c/vc-bitstring-status-list#90.
-
-
2 issues received 2 new comments.
-
Rename specification to "Herd Privacy Status List" w3c/vc-bitstring-status-list#90 (1 comment by @msporny)
-
1 pull request opened.
-
Update the echidna script w3c/vc-bitstring-status-list#95, by @iherman.
-
-
1 pull request received 4 new comments.
w3c/vc-json-schema
-
1 issue opened.
-
Provide for localization of a VC JSON Schema document w3c/vc-json-schema#224, by @aphillips.
-
-
1 issue closed.
-
Provide for localization of a VC JSON Schema document w3c/vc-json-schema#224.
-
-
2 issues received 4 new comments.
-
Provide for localization of a VC JSON Schema document w3c/vc-json-schema#224 (3 comments by @andresuribe87, @aphillips, @thereisnogabe)
-
[i18n] no need to refer considerations on data serialization defined in the core? w3c/vc-json-schema#222 (1 comment by @aphillips)
-
-
6 pull requests opened.
-
Update auto-publish.yml w3c/vc-json-schema#230, by @iherman.
-
Added the final CR version w3c/vc-json-schema#229, by @iherman.
-
Including commits that were missed w3c/vc-json-schema#228, by @andresuribe87.
-
fix cr end w3c/vc-json-schema#227, by @thereisnogabe.
-
update CR date to November 14 w3c/vc-json-schema#226, by @thereisnogabe.
-
Renamed `name` to `title` and added `lang` & `dir`. w3c/vc-json-schema#225, by @andresuribe87.
-
-
5 pull requests merged.
-
Added the final CR version w3c/vc-json-schema#229.
-
Including commits that were missed w3c/vc-json-schema#228.
-
Renamed `name` to `title` and added `lang` & `dir`. w3c/vc-json-schema#225.
-
fix cr end w3c/vc-json-schema#227.
-
update CR date to November 14 w3c/vc-json-schema#226.
-
-
1 pull request received 14 new comments.
-
Renamed `name` to `title` and added `lang` & `dir`. w3c/vc-json-schema#225 (14 comments by @andresuribe87, @aphillips)
-
w3c/vc-di-ecdsa
-
2 pull requests opened.
-
Update auto-publish.yml w3c/vc-di-ecdsa#45, by @iherman.
-
Added the final CR Version w3c/vc-di-ecdsa#44, by @iherman.
-
w3c/vc-di-eddsa
-
1 issue opened.
-
Fix byte length of `publickKeyMultibase` to 34 w3c/vc-di-eddsa#66, by @JSAssassin.
-
-
3 pull requests opened.
-
Update auto-publish.yml w3c/vc-di-eddsa#69, by @iherman.
-
Added the final CR Version w3c/vc-di-eddsa#68, by @iherman.
-
Fix byte length of `publickKeyMultibase`. w3c/vc-di-eddsa#67, by @JSAssassin.
-
-
1 pull request received 3 new comments.
w3c/vc-data-integrity
-
2 issues opened.
-
Find somewhere to parse bytes into an RDF dataset w3c/vc-data-integrity#222, by @jyasskin.
-
Discrepancy Between DataIntegrityProof EdDSA `eddsa-2022` vs Crypto Suite `eddsa-rdfc-2022` Definition w3c/vc-data-integrity#221, by @LuisOsta.
-
-
1 issue closed.
-
Internationalization Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#96.
-
-
3 issues received 16 new comments.
-
Discrepancy Between DataIntegrityProof EdDSA `eddsa-2022` vs Crypto Suite `eddsa-rdfc-2022` Definition w3c/vc-data-integrity#221 (8 comments by @dlongley, @LuisOsta, @msporny, @Wind4Greg)
-
Domain and range of sec:publicKey w3c/vc-data-integrity#74 (7 comments by @melvincarvalho, @msporny, @silverpill)
-
Internationalization Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#96 (1 comment by @aphillips)
-
-
2 pull requests opened.
-
Update echidna.yml w3c/vc-data-integrity#223, by @iherman.
-
Added the final CR Version w3c/vc-data-integrity#220, by @iherman.
-
-
1 pull request received 1 new comment.
w3c/vc-confidence-method
-
1 issue opened.
-
Add DID Confidence Method w3c/vc-confidence-method#10, by @thereisnogabe.
-
w3c/vc-jose-cose-test-suite
-
1 issue received 6 new comments.
-
Positive and negative testing for Accept header in requests w3c/vc-jose-cose-test-suite#8 (6 comments by @msporny, @OR13, @rhofvendahl, @TallTed)
-
TR publications
-
31 documents published.
-
Verifiable Credentials Data Model v2.0 published 5 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Verifiable Credentials JSON Schema Specification published 4 times as a Working Draft. History of Verifiable Credentials JSON Schema Specification
-
Securing Verifiable Credentials using JOSE and COSE published 6 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
BBS Cryptosuite v2023 published twice as a Working Draft. History of BBS Cryptosuite v2023
-
Data Integrity ECDSA Cryptosuites v1.0 published 6 times as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published 4 times as a Working Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Verifiable Credential Data Integrity 1.0 published 4 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Past meetings
-
8 meetings.
Participants
-
1 chair appointed.
-
Brent Zundel became a chair.
-
-
2 chairs stepped down.
-
Kristina Yasuda stepped down as a chair.
-
Brent Zundel stepped down as a chair.
-
-
4 participants joined.
-
Erez Kalman (Akamai Technologies) joined.
-
Brent Zundel (Yubico) joined.
-
Sten Reijers (Ver.iD) joined.
-
Tomasz Mielnicki (Entersekt) joined.
-
-
6 participants left.
-
Brent Zundel (Yubico) left.
-
Steve Cole (Merchant Advisory Group) left.
-
Zaïda Rivai (Danube Tech GmbH) left.
-
Bernhard Fuchs (Danube Tech GmbH) left.
-
Ahamed Azeem (Danube Tech GmbH) left.
-
Markus Sabadello (Danube Tech GmbH) left.
-
-
3 organizations joined.
-
Akamai Technologies joined.
-
Ver.iD joined.
-
Onfido joined.
-
-
1 organization left.
-
Danube Tech GmbH left.
-
GitHub
w3c/vc-data-model
-
20 issues opened.
-
Add validation to lifecycle details image w3c/vc-data-model#1331, by @msporny.
-
W3C Caused by: com.apicatalog.jsonld.JsonLdError: Unexpected response code [429] w3c/vc-data-model#1330, by @tuanphampmt.
-
Make validation normative w3c/vc-data-model#1328, by @jandrieu.
-
Consider mandating securing RDF graph for all securing mechanisms w3c/vc-data-model#1327, by @awoie.
-
Cross-check the `domain`/`range` statements in the vocabulary with the VCDM spec w3c/vc-data-model#1319, by @iherman.
-
Updating figures 6 and 7 w3c/vc-data-model#1318, by @iherman.
-
Update 4.9 Securing Verifiable Credentials w3c/vc-data-model#1316, by @OR13.
-
Consider abandoning drafts for non-data-integrity-proof securing formats w3c/vc-data-model#1315, by @OR13.
-
Default context contains terms outside of the spec w3c/vc-data-model#1314, by @mtaimela.
-
Use a better example for bidirectional text (Editorial) w3c/vc-data-model#1313, by @iherman.
-
clarify relationship to the `proof` property and the specifications defining how to secure VCs w3c/vc-data-model#1312, by @Sakurann.
-
Section 3 "Core Data Model" clean up w3c/vc-data-model#1311, by @Sakurann.
-
Make Section 4.1 non-normative w3c/vc-data-model#1310, by @Sakurann.
-
Include credentialSubject examples that use URLs rather than DIDs w3c/vc-data-model#1309, by @selfissued.
-
Controller Documents w3c/vc-data-model#1307, by @brentzundel.
-
(Editorial) Use a three level deep TOC in the VCDM spec w3c/vc-data-model#1306, by @iherman.
-
Remove the at risk issue marker for `Evidence` w3c/vc-data-model#1303, by @OR13.
-
add explicit notes where terminology in the spec diverges from things elsewhere w3c/vc-data-model#1301, by @Sakurann.
-
Clarify what conformance means to the issuers/verifiers w3c/vc-data-model#1300, by @Sakurann.
-
address normative statements in non-normative sections w3c/vc-data-model#1299, by @Sakurann.
-
-
7 issues closed.
-
Better visualization of data model w3c/vc-data-model#1095.
-
Consider abandoning drafts for non-data-integrity-proof securing formats w3c/vc-data-model#1315.
-
Add references to Sub-Resource Integrity w3c/vc-data-model#1237.
-
are `domain` and `range` correct for all properties in data model? w3c/vc-data-model#1263.
-
Address normative concept of VerifiableCredentialGraph w3c/vc-data-model#1240.
-
Mitigating Location Correlation via Common Issuers w3c/vc-data-model#1245.
-
Add `revoked` and `expired` to verification method classes w3c/vc-data-model#1262.
-
-
1 issue reopened.
-
Add validation to lifecycle details image w3c/vc-data-model#1331, by @jandrieu.
-
-
30 issues received 115 new comments.
-
signatures should be on quoted graphs w3c/vc-data-model#1248 (17 comments by @iherman, @kaefer3000, @melvincarvalho, @msporny)
-
Consider abandoning drafts for non-data-integrity-proof securing formats w3c/vc-data-model#1315 (12 comments by @alenhorvat, @awoie, @msporny, @OR13, @peacekeeper)
-
Consider mandating securing RDF graph for all securing mechanisms w3c/vc-data-model#1327 (10 comments by @alenhorvat, @awoie, @mtaimela, @OR13)
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010 (9 comments by @alenhorvat, @clehner, @David-Chadwick, @lalc, @lineko, @msporny, @Sakurann, @TallTed)
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290 (9 comments by @awoie, @brentzundel, @dlongley, @msporny, @OR13, @thereisnogabe)
-
Default context contains terms outside of the spec w3c/vc-data-model#1314 (9 comments by @AFlowOfCode, @brentzundel, @dlongley, @mtaimela, @OR13)
-
Update 4.9 Securing Verifiable Credentials w3c/vc-data-model#1316 (7 comments by @brentzundel, @msporny, @OR13)
-
Internationalization Review for VCDM 2.0 w3c/vc-data-model#1155 (7 comments by @aphillips, @David-Chadwick, @iherman, @msporny, @Sakurann)
-
W3C Caused by: com.apicatalog.jsonld.JsonLdError: Unexpected response code [429] w3c/vc-data-model#1330 (2 comments by @davidlehn, @msporny)
-
are `domain` and `range` correct for all properties in data model? w3c/vc-data-model#1263 (2 comments by @iherman)
-
Use a better example for bidirectional text (Editorial) w3c/vc-data-model#1313 (2 comments by @aphillips, @iherman)
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206 (1 comment by @msporny)
-
Allow string values in JOSE properties in base JSON-LD context w3c/vc-data-model#1275 (1 comment by @msporny)
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246 (1 comment by @msporny)
-
Address normative concept of VerifiableCredentialGraph w3c/vc-data-model#1240 (1 comment by @msporny)
-
clarify relationship to the `proof` property and the specifications defining how to secure VCs w3c/vc-data-model#1312 (1 comment by @Sakurann)
-
Add `revoked` and `expired` to verification method classes w3c/vc-data-model#1262 (1 comment by @brentzundel)
-
address normative statements in non-normative sections w3c/vc-data-model#1299 (1 comment by @brentzundel)
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264 (1 comment by @iherman)
-
-
18 pull requests opened.
-
Add comment on localizing vocabulary terms. w3c/vc-data-model#1333, by @OR13.
-
Add comparison to NIST definition w3c/vc-data-model#1332, by @OR13.
-
Kristina stepping down as a co-chair w3c/vc-data-model#1329, by @Sakurann.
-
Improve the explanation of using graphs in VCDM w3c/vc-data-model#1326, by @iherman.
-
Align JWT/JWS fields with IETF RFCs. w3c/vc-data-model#1325, by @msporny.
-
Add section on trust boundaries in privacy considerations. w3c/vc-data-model#1324, by @msporny.
-
Add section on key management. w3c/vc-data-model#1323, by @msporny.
-
Add suggestion to use Oblivious HTTP when fetching resources. w3c/vc-data-model#1322, by @msporny.
-
Replacement of the diagrams (figure 6 and 8), and their descriptions w3c/vc-data-model#1321, by @iherman.
-
Add definition of well formed w3c/vc-data-model#1320, by @OR13.
-
Additional updates regarding proof w3c/vc-data-model#1317, by @OR13.
-
Remove "proof" clauses from initial examples w3c/vc-data-model#1308, by @selfissued.
-
Remove CL Signature Example w3c/vc-data-model#1305, by @OR13.
-
Editorial cleaning w3c/vc-data-model#1304, by @OR13.
-
Propose better JSON-LD processing text w3c/vc-data-model#1302, by @OR13.
-
Remove JSON Processing section w3c/vc-data-model#1298, by @OR13.
-
First pass at updating validation language w3c/vc-data-model#1297, by @jandrieu.
-
Add `relatedResource` and `digestSRI` to the vocabulary w3c/vc-data-model#1296, by @iherman.
-
-
8 pull requests merged.
-
Kristina stepping down as a co-chair w3c/vc-data-model#1329.
-
Add section on trust boundaries in privacy considerations. w3c/vc-data-model#1324.
-
Add suggestion to use Oblivious HTTP when fetching resources. w3c/vc-data-model#1322.
-
Editorial cleaning w3c/vc-data-model#1304.
-
Add `relatedResource` and `digestSRI` to the vocabulary w3c/vc-data-model#1296.
-
Remove CL Signature Example w3c/vc-data-model#1305.
-
Remove "proof" clauses from initial examples w3c/vc-data-model#1308.
-
Privacy considerations around issuer location w3c/vc-data-model#1286.
-
-
3 pull requests closed.
-
Explain JSON-LD further. w3c/vc-data-model#1270.
-
removes ToU from the main text while keeping it in the reserved extension points table w3c/vc-data-model#1294.
-
Replacement of the diagrams (figure 6 and 8), and their descriptions w3c/vc-data-model#1321.
-
-
23 pull requests received 517 new comments.
-
Propose better JSON-LD processing text w3c/vc-data-model#1302 (152 comments by @awoie, @BigBlueHat, @brentzundel, @brianorwhatever, @davidlehn, @dlongley, @iherman, @msporny, @OR13)
-
Update to Terms of Use description w3c/vc-data-model#1295 (55 comments by @brentzundel, @David-Chadwick, @davidlehn, @iherman, @msporny, @OR13, @TallTed)
-
Add section on trust boundaries in privacy considerations. w3c/vc-data-model#1324 (46 comments by @brentzundel, @iherman, @kdenhartog, @msporny, @TallTed, @thereisnogabe)
-
First pass at updating validation language w3c/vc-data-model#1297 (45 comments by @andresuribe87, @iherman, @jandrieu, @msporny, @OR13, @thereisnogabe)
-
Additional updates regarding proof w3c/vc-data-model#1317 (31 comments by @dlongley, @iherman, @msporny, @OR13, @thereisnogabe)
-
Warn that using dynamic processor features might lead to less interoperability w3c/vc-data-model#1276 (28 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Add `relatedResource` and `digestSRI` to the vocabulary w3c/vc-data-model#1296 (24 comments by @davidlehn, @iherman, @msporny, @TallTed)
-
Improve the explanation of using graphs in VCDM w3c/vc-data-model#1326 (20 comments by @dlongley, @iherman, @OR13, @TallTed, @thereisnogabe)
-
Add suggestion to use Oblivious HTTP when fetching resources. w3c/vc-data-model#1322 (16 comments by @kdenhartog, @martinthomson, @msporny, @ShivanKaul, @TallTed)
-
Warn authors that usage of global JSON-LD keywords might harm interoperability w3c/vc-data-model#1271 (15 comments by @brianorwhatever, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Add section on key management. w3c/vc-data-model#1323 (14 comments by @brianorwhatever, @dlongley, @iherman, @kdenhartog, @msporny, @TallTed)
-
Explain JSON-LD further. w3c/vc-data-model#1270 (12 comments by @BigBlueHat, @brentzundel, @dlongley, @iherman, @msporny, @OR13)
-
Remove JSON Processing section w3c/vc-data-model#1298 (9 comments by @BigBlueHat, @dlongley, @iherman, @OR13)
-
Align JWT/JWS fields with IETF RFCs. w3c/vc-data-model#1325 (8 comments by @iherman, @msporny, @OR13, @peacekeeper, @thereisnogabe)
-
Add links to static copies of vocabulary files and hashes w3c/vc-data-model#1279 (7 comments by @iherman, @msporny, @TallTed)
-
Remove "proof" clauses from initial examples w3c/vc-data-model#1308 (7 comments by @andresuribe87, @iherman, @OR13, @peacekeeper)
-
Replacement of the diagrams (figure 6 and 8), and their descriptions w3c/vc-data-model#1321 (5 comments by @dlongley, @iherman)
-
Privacy considerations around issuer location w3c/vc-data-model#1286 (3 comments by @iherman, @thereisnogabe)
-
removes ToU from the main text while keeping it in the reserved extension points table w3c/vc-data-model#1294 (2 comments by @David-Chadwick, @iherman)
-
w3c/vc-bitstring-status-list
-
2 issues opened.
-
Status-List-2021 LD-Context broken w3c/vc-bitstring-status-list#91, by @F-Node-Karlsruhe.
-
Rename specification to "Herd Privacy Status List" w3c/vc-bitstring-status-list#90, by @msporny.
-
-
1 issue closed.
-
Status-List-2021 LD-Context broken w3c/vc-bitstring-status-list#91.
-
-
6 issues received 12 new comments.
-
Status-List-2021 LD-Context broken w3c/vc-bitstring-status-list#91 (5 comments by @msporny, @victormartinez-work)
-
Define priority for a single credential with multiple statuses w3c/vc-bitstring-status-list#37 (1 comment by @OR13)
-
-
2 pull requests opened.
-
Add section on media types w3c/vc-bitstring-status-list#92, by @OR13.
-
Mark repo as host of rec-track work w3c/vc-bitstring-status-list#89, by @dontcallmedom.
-
-
1 pull request merged.
-
Mark repo as host of rec-track work w3c/vc-bitstring-status-list#89.
-
-
1 pull request received 1 new comment.
w3c/vc-di-bbs
-
2 issues opened.
-
Apparent inconsistency in `proofValue` examples & normative multibase statement w3c/vc-di-bbs#95, by @AFlowOfCode.
-
Reuse ECDSA-SD Primitives where Possible, Use JSON Pointers w3c/vc-di-bbs#93, by @Wind4Greg.
-
-
1 issue closed.
-
Complete FPWD w3c/vc-di-bbs#88.
-
-
2 issues received 7 new comments.
-
Reuse ECDSA-SD Primitives where Possible, Use JSON Pointers w3c/vc-di-bbs#93 (5 comments by @dlongley, @msporny, @Wind4Greg)
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-bbs#92 (2 comments by @msporny, @selfissued)
-
-
4 pull requests opened.
-
Wind4 greg sd primitives w3c/vc-di-bbs#98, by @msporny.
-
Removing myself (tobias) as editor w3c/vc-di-bbs#97, by @tplooker.
-
Add GregB and Manu as editors. w3c/vc-di-bbs#96, by @msporny.
-
Update to use JSON Pointers and Selective Disclosure Primitives w3c/vc-di-bbs#94, by @Wind4Greg.
-
-
2 pull requests merged.
-
Add GregB and Manu as editors. w3c/vc-di-bbs#96.
-
Removing myself from the work item w3c/vc-di-bbs#91.
-
-
3 pull requests received 102 new comments.
-
Update to use JSON Pointers and Selective Disclosure Primitives w3c/vc-di-bbs#94 (99 comments by @brianorwhatever, @dlongley, @iherman, @msporny, @TallTed, @Wind4Greg)
-
w3c/vc-json-schema
-
1 issue opened.
-
[i18n] no need to refer considerations on data serialization defined in the core? w3c/vc-json-schema#222, by @himorin.
-
-
3 issues closed.
-
Security and Privacy Self-Review Questionnaire w3c/vc-json-schema#167.
-
Internationalization Review for VC JSON Schema w3c/vc-json-schema#164.
-
[i18n] no need to refer considerations on data serialization defined in the core? w3c/vc-json-schema#222.
-
-
3 issues received 5 new comments.
-
[i18n] no need to refer considerations on data serialization defined in the core? w3c/vc-json-schema#222 (3 comments by @himorin, @iherman, @thereisnogabe)
-
-
4 pull requests opened.
-
i18n feedback w3c/vc-json-schema#223, by @thereisnogabe.
-
Missing fragment ID w3c/vc-json-schema#221, by @iherman.
-
Update SoTD text w3c/vc-json-schema#220, by @thereisnogabe.
-
Update CR Date w3c/vc-json-schema#219, by @thereisnogabe.
-
-
5 pull requests merged.
-
i18n feedback w3c/vc-json-schema#223.
-
Missing fragment ID w3c/vc-json-schema#221.
-
Update SoTD text w3c/vc-json-schema#220.
-
Update CR Date w3c/vc-json-schema#219.
-
Add section on revision history w3c/vc-json-schema#218.
-
w3c/vc-bitstring-status-list-test-suite
-
1 issue opened.
-
Intermittent failure of tests w3c/vc-bitstring-status-list-test-suite#25, by @JSAssassin.
-
w3c/vc-data-integrity
-
5 issues opened.
-
Add test vectors that use i18n strings w3c/vc-data-integrity#218, by @msporny.
-
Add issue marker noting desired convergence w/ controller documents in vc-jose-cose w3c/vc-data-integrity#216, by @msporny.
-
Explain that data integrity secures underlying RDF graph w3c/vc-data-integrity#215, by @Sakurann.
-
Show i18n best practice in example w3c/vc-data-integrity#211, by @msporny.
-
Is the value space definition for `multibase` correct? w3c/vc-data-integrity#209, by @iherman.
-
-
6 issues closed.
-
Add issue marker noting desired convergence w/ controller documents in vc-jose-cose w3c/vc-data-integrity#216.
-
Is the value space definition for `multibase` correct? w3c/vc-data-integrity#209.
-
Show i18n best practice in example w3c/vc-data-integrity#211.
-
I think the diagram key should be changed from `Graph Containment` to `Contains` w3c/vc-data-integrity#203.
-
Apply diagram changes w3c/vc-data-integrity#175.
-
Remove references to multibase w3c/vc-data-integrity#191.
-
-
7 issues received 22 new comments.
-
Add issue marker noting desired convergence w/ controller documents in vc-jose-cose w3c/vc-data-integrity#216 (6 comments by @iherman, @msporny, @selfissued)
-
Show i18n best practice in example w3c/vc-data-integrity#211 (6 comments by @aphillips, @iherman, @msporny)
-
Is the value space definition for `multibase` correct? w3c/vc-data-integrity#209 (4 comments by @iherman, @msporny)
-
Explain that data integrity secures underlying RDF graph w3c/vc-data-integrity#215 (3 comments by @dlongley, @peacekeeper, @selfissued)
-
I think the diagram key should be changed from `Graph Containment` to `Contains` w3c/vc-data-integrity#203 (1 comment by @brentzundel)
-
-
5 pull requests opened.
-
Add potential for Controller Document spec at risk marker. w3c/vc-data-integrity#219, by @msporny.
-
Clarify the value space of the multibase datatype. w3c/vc-data-integrity#214, by @msporny.
-
Add Internationalization section w3c/vc-data-integrity#213, by @msporny.
-
Updated the URL-s in the vocabulary w3c/vc-data-integrity#212, by @iherman.
-
[Editorial] Making the diagram dark-mode safe w3c/vc-data-integrity#210, by @iherman.
-
-
5 pull requests merged.
-
Add potential for Controller Document spec at risk marker. w3c/vc-data-integrity#219.
-
Clarify the value space of the multibase datatype. w3c/vc-data-integrity#214.
-
Add Internationalization section w3c/vc-data-integrity#213.
-
[Editorial] Making the diagram dark-mode safe w3c/vc-data-integrity#210.
-
Remove normative dependency on Multibase and Multihash. w3c/vc-data-integrity#196.
-
-
6 pull requests received 48 new comments.
-
Remove normative dependency on Multibase and Multihash. w3c/vc-data-integrity#196 (28 comments by @iherman, @msporny, @selfissued)
-
Add Internationalization section w3c/vc-data-integrity#213 (7 comments by @aphillips, @msporny, @TallTed)
-
Add potential for Controller Document spec at risk marker. w3c/vc-data-integrity#219 (5 comments by @iherman, @msporny, @TallTed)
-
Clarify the value space of the multibase datatype. w3c/vc-data-integrity#214 (1 comment by @msporny)
-
w3c/vc-jose-cose
-
5 issues opened.
-
Remove internationalization considerations section? w3c/vc-jose-cose#172, by @aphillips.
-
Missing word and missing referent in section 2 w3c/vc-jose-cose#169, by @bert-github.
-
Broken links to iss w3c/vc-jose-cose#168, by @bert-github.
-
Example does not correspond to description in section 5.3.1 w3c/vc-jose-cose#167, by @bert-github.
-
credentialSchema property not fully correct in PR#159 examples w3c/vc-jose-cose#164, by @David-Chadwick.
-
-
10 issues closed.
-
Accessibility Self-Review for VC-JWT w3c/vc-jose-cose#94.
-
Security and Privacy Self-Review Questionnaire w3c/vc-jose-cose#93.
-
Internationalization Review for VC JOSE COSE w3c/vc-jose-cose#95.
-
File PING request once rename is complete w3c/vc-jose-cose#128.
-
signature profiles w3c/vc-jose-cose#136.
-
Add guidance on "flat" vs "compact". w3c/vc-jose-cose#107.
-
We need to specify the exact format of DID URL we expect w3c/vc-jose-cose#158.
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117.
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64.
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30.
-
-
15 issues received 24 new comments.
-
Can registered JWT claims be used only in the JOSE header?? w3c/vc-jose-cose#135 (3 comments by @OR13)
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117 (2 comments by @OR13, @selfissued)
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30 (2 comments by @OR13, @selfissued)
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64 (1 comment by @selfissued)
-
7 pull requests opened.
-
fixing a few typos in index.html w3c/vc-jose-cose#171, by @TallTed.
-
Add guidance on serialization and profile w3c/vc-jose-cose#170, by @OR13.
-
fix double json copy paste bug w3c/vc-jose-cose#166, by @OR13.
-
Fix json and data uri examples w3c/vc-jose-cose#165, by @OR13.
-
Address `kid` w3c/vc-jose-cose#163, by @OR13.
-
Add the initial examples from the core data model w3c/vc-jose-cose#162, by @OR13.
-
Add controller examples w3c/vc-jose-cose#161, by @OR13.
-
-
8 pull requests merged.
-
fixing a few typos in index.html w3c/vc-jose-cose#171.
-
Add guidance on serialization and profile w3c/vc-jose-cose#170.
-
fix double json copy paste bug w3c/vc-jose-cose#166.
-
Fix json and data uri examples w3c/vc-jose-cose#165.
-
Add the initial examples from the core data model w3c/vc-jose-cose#162.
-
Address `kid` w3c/vc-jose-cose#163.
-
Add controller examples w3c/vc-jose-cose#161.
-
Add Cred Metadata to Example w3c/vc-jose-cose#159.
-
-
4 pull requests received 19 new comments.
-
Add the initial examples from the core data model w3c/vc-jose-cose#162 (6 comments by @OR13, @selfissued)
w3c/vc-di-eddsa-test-suite
-
2 pull requests opened.
-
Update tests w3c/vc-di-eddsa-test-suite#21, by @JSAssassin.
-
Temporarily pin node to v20.8.0 in gh actions. w3c/vc-di-eddsa-test-suite#20, by @JSAssassin.
-
-
1 pull request merged.
-
Temporarily pin node to v20.8.0 in gh actions. w3c/vc-di-eddsa-test-suite#20.
-
w3c/vc-render-method
-
1 issue opened.
-
Rename 'SvgRenderingTemplate2023' type to 'SvgRenderingTemplate' w3c/vc-render-method#4, by @dmitrizagidulin.
-
-
1 issue received 1 new comment.
-
Rename 'SvgRenderingTemplate2023' type to 'SvgRenderingTemplate' w3c/vc-render-method#4 (1 comment by @TallTed)
-
-
2 pull requests opened.
-
Add renderMethod context to example. w3c/vc-render-method#6, by @dmitrizagidulin.
-
Rename 'SvgRenderingTemplate2023' type to 'SvgRenderingTemplate'. w3c/vc-render-method#5, by @dmitrizagidulin.
-
w3c/vc-confidence-method
-
1 issue opened.
-
Why is `confidenceMethod` inside the `credentialSubject`? w3c/vc-confidence-method#9, by @brianorwhatever.
-
-
3 issues closed.
-
Why is `confidenceMethod` inside the `credentialSubject`? w3c/vc-confidence-method#9.
-
Deploy github pages build w3c/vc-confidence-method#5.
-
Deployment link is broken w3c/vc-confidence-method#7.
-
-
3 issues received 5 new comments.
-
Why is `confidenceMethod` inside the `credentialSubject`? w3c/vc-confidence-method#9 (3 comments by @brianorwhatever, @dlongley)
-
-
1 pull request merged.
-
Add CCG properties w3c/vc-confidence-method#4.
-
-
1 pull request closed.
-
change repo link from @spruceid to @w3c-ccg w3c/vc-confidence-method#8.
-
-
1 pull request received 1 new comment.
-
change repo link from @spruceid to @w3c-ccg w3c/vc-confidence-method#8 (1 comment by @brianorwhatever)
-
w3c/vc-di-ecdsa-test-suite
-
2 pull requests opened.
-
Temporarily pin `node` to `v20.8.0` in gh actions. w3c/vc-di-ecdsa-test-suite#14, by @JSAssassin.
-
Update tests. w3c/vc-di-ecdsa-test-suite#13, by @JSAssassin.
-
-
1 pull request merged.
-
Temporarily pin `node` to `v20.8.0` in gh actions. w3c/vc-di-ecdsa-test-suite#14.
-
-
1 pull request received 1 new comment.
-
Temporarily pin `node` to `v20.8.0` in gh actions. w3c/vc-di-ecdsa-test-suite#14 (1 comment by @aljones15)
-
w3c/vc-test-suite-implementations
-
1 pull request opened.
-
Update DB `eddsa-2022` issuer. w3c/vc-test-suite-implementations#3, by @JSAssassin.
-
-
1 pull request merged.
-
Update DB `eddsa-2022` issuer. w3c/vc-test-suite-implementations#3.
-
w3c/vc-use-cases
-
1 pull request received 1 new comment.
-
updated verify claim and added validate claim. images updated w3c/vc-use-cases#149 (1 comment by @TallTed)
-
w3c/vc-test-suite
-
1 issue received 3 new comments.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (3 comments by @OR13)
-
-
1 pull request received 1 new comment.
w3c/vcalm
-
2 issues opened.
-
Mediated Presentation definition w3c/vcalm#541, by @robdefeo.
-
Status of the spec w3c/vcalm#540, by @robdefeo.
-
-
2 issues received 2 new comments.
-
Clarification on endpoints style for issuance , verification and derivation w3c/vcalm#343 (1 comment by @jruizaranguren)
-
w3c/vc-di-eddsa
-
1 issue opened.
-
Test vector issue in B.1 Representation: eddsa-rdfc-2022 w3c/vc-di-eddsa#65, by @AFlowOfCode.
-
-
2 issues closed.
-
Test vector issue in B.1 Representation: eddsa-rdfc-2022 w3c/vc-di-eddsa#65.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-eddsa#62.
-
-
2 issues received 2 new comments.
-
Test vector issue in B.1 Representation: eddsa-rdfc-2022 w3c/vc-di-eddsa#65 (1 comment by @AFlowOfCode)
-
-
1 pull request opened.
-
Update test vectors based on update to @context w3c/vc-di-eddsa#64, by @Wind4Greg.
-
-
2 pull requests merged.
-
Update test vectors based on update to @context w3c/vc-di-eddsa#64.
-
Remove references to Multiformats specifications. w3c/vc-di-eddsa#63.
-
-
2 pull requests received 12 new comments.
-
Remove references to Multiformats specifications. w3c/vc-di-eddsa#63 (11 comments by @iherman, @msporny, @selfissued)
-
w3c/vc-di-ecdsa
-
1 issue closed.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-ecdsa#39.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update Test Vectors w3c/vc-di-ecdsa#43, by @Wind4Greg.
-
-
4 pull requests merged.
-
Update Test Vectors w3c/vc-di-ecdsa#43.
-
Make all Multicodec / Multibase references non-normative. w3c/vc-di-ecdsa#42.
-
createInitialSelection: Fix parameter references. w3c/vc-di-ecdsa#41.
-
Enhance description of skolemizeExpandedJsonLd, variable naming, id string w3c/vc-di-ecdsa#40.
-
-
4 pull requests received 10 new comments.
-
Make all Multicodec / Multibase references non-normative. w3c/vc-di-ecdsa#42 (4 comments by @iherman, @msporny)
-
Enhance description of skolemizeExpandedJsonLd, variable naming, id string w3c/vc-di-ecdsa#40 (4 comments by @dlongley, @msporny, @Wind4Greg)
-
w3c/cid
-
1 issue opened.
-
Clarity on binary data headers in multikey definition w3c/cid#36, by @dbluhm.
-
w3c/vc-imp-guide
-
1 issue opened.
-
Add section describing value of JSON-LD w3c/vc-imp-guide#71, by @brentzundel.
-
w3c/vc-data-model-2.0-test-suite
-
1 issue opened.
-
Make sure we properly test ToU w3c/vc-data-model-2.0-test-suite#36, by @brentzundel.
-
w3c/vc-extensions
-
1 pull request received 1 new comment.
-
Update and rename credential-schema-2023.json to credential-schema.json w3c/vc-extensions#29 (1 comment by @OR13)
-
TR publications
-
27 documents published.
-
Verifiable Credentials Data Model v2.0 published 8 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Data Integrity ECDSA Cryptosuites v1.0 published twice as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Securing Verifiable Credentials using JOSE and COSE published 7 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
Verifiable Credentials JSON Schema Specification published 6 times as a Working Draft. History of Verifiable Credentials JSON Schema Specification
-
Verifiable Credential Data Integrity 1.0 published 3 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published as a Working Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Past meetings
-
12 meetings.
Participants
-
8 participants joined.
-
Johan de Swardt (Entersekt) joined.
-
Joaquin Salvachua (Universidad Politécnica de Madrid) joined.
-
Duy-Tung LUU (CANTON CONSULTING) joined.
-
Jean-Yves ROSSI (CANTON CONSULTING) joined.
-
David Trang (Universities Admissions Centre) joined.
-
Nick Clark (Universities Admissions Centre) joined.
-
Dudley Collinson (Universities Admissions Centre) joined.
-
Juan Caballero (Protocol Labs) joined.
-
-
4 participants left.
-
Matthieu Bosquet (Inrupt Inc.) left.
-
Brandon Baraban (Koodos Labs) left.
-
Justin Richer (Gen) left.
-
Sten Reijers (Ver.iD) left.
-
-
3 organizations joined.
-
Universidad Politécnica de Madrid joined.
-
CANTON CONSULTING joined.
-
Universities Admissions Centre joined.
-
GitHub
w3c/vc-use-cases
-
4 issues closed.
-
Document Prescription Use Case w3c/vc-use-cases#38.
-
Holder Bundling of Separate Claims w3c/vc-use-cases#75.
-
update diagrams w3c/vc-use-cases#109.
-
New icons for Verifiable Claims Roleas w3c/vc-use-cases#80.
-
-
4 issues received 5 new comments.
-
w3c/vc-use-cases#38 (1 comment by @jandrieu)
-
1 pull request opened.
-
updated verify claim and added validate claim. images updated w3c/vc-use-cases#149, by @jandrieu.
-
-
1 pull request merged.
-
Miscellaneous cleanup w3c/vc-use-cases#148.
-
-
2 pull requests received 39 new comments.
-
updated verify claim and added validate claim. images updated w3c/vc-use-cases#149 (38 comments by @iherman, @jandrieu, @philarcher, @seabass-labrax, @TallTed, @thereisnogabe)
-
w3c/vc-di-ecdsa
-
1 issue opened.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-ecdsa#39, by @selfissued.
-
-
4 issues closed.
-
Add definition for secretKeyMultibase serialization w3c/vc-di-ecdsa#35.
-
Ensure to pass SHA-384 param and fetch verification method early to get key size w3c/vc-di-ecdsa#32.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-ecdsa#29.
-
Add normative guidance that Deterministic signatures SHOULD be used w3c/vc-di-ecdsa#28.
-
-
5 issues received 6 new comments.
-
Ensure to pass SHA-384 param and fetch verification method early to get key size w3c/vc-di-ecdsa#32 (1 comment by @msporny)
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-ecdsa#29 (1 comment by @msporny)
-
Add normative guidance that Deterministic signatures SHOULD be used w3c/vc-di-ecdsa#28 (1 comment by @msporny)
-
4 pull requests opened.
-
Make all Multicodec / Multibase references non-normative. w3c/vc-di-ecdsa#42, by @msporny.
-
createInitialSelection: Fix parameter references. w3c/vc-di-ecdsa#41, by @Wind4Greg.
-
Enhance description of skolemizeExpandedJsonLd, variable naming, id string w3c/vc-di-ecdsa#40, by @Wind4Greg.
-
Selective Disclosure Test Vectors w3c/vc-di-ecdsa#38, by @Wind4Greg.
-
-
5 pull requests merged.
-
Selective Disclosure Test Vectors w3c/vc-di-ecdsa#38.
-
Add secretKeyMultibase representation. w3c/vc-di-ecdsa#37.
-
Add which cryptographic hash function to use for RDF-CANON. w3c/vc-di-ecdsa#36.
-
deterministic ECDSA SHOULD be used w3c/vc-di-ecdsa#34.
-
Simplify language that warns of invalid examples w3c/vc-di-ecdsa#31.
-
-
7 pull requests received 23 new comments.
-
Make all Multicodec / Multibase references non-normative. w3c/vc-di-ecdsa#42 (8 comments by @iherman, @msporny, @TallTed)
-
Selective Disclosure Test Vectors w3c/vc-di-ecdsa#38 (6 comments by @dlongley, @msporny, @Wind4Greg)
-
Enhance description of skolemizeExpandedJsonLd, variable naming, id string w3c/vc-di-ecdsa#40 (4 comments by @dlongley, @Wind4Greg)
-
Add which cryptographic hash function to use for RDF-CANON. w3c/vc-di-ecdsa#36 (2 comments by @msporny)
-
w3c/vc-data-model
-
13 issues opened.
-
Clarify evidence section to point to OBv3 evidence property usage w3c/vc-data-model#1293, by @msporny.
-
Prefer Arrays and Objects. w3c/vc-data-model#1292, by @OR13.
-
Multiple Credential Status Lists w3c/vc-data-model#1291, by @bruno-zimmermann-bit.
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290, by @awoie.
-
Update i18n example w3c/vc-data-model#1289, by @OR13.
-
Pre-CR review from Jeffrey Yasskin w3c/vc-data-model#1285, by @msporny.
-
Normative requirement for securing a VC or VP w3c/vc-data-model#1282, by @andresuribe87.
-
Allow string values in JOSE properties in base JSON-LD context w3c/vc-data-model#1275, by @msporny.
-
Tell a bit more about `verificationMethod` type schema w3c/vc-data-model#1274, by @Voronar.
-
Add @TallTed and @iherman to Editors list w3c/vc-data-model#1273, by @msporny.
-
Encourage the use of OHTTP w3c/vc-data-model#1267, by @awoie.
-
Recommend that authors don't use `@base` in `@context` w3c/vc-data-model#1266, by @msporny.
-
Add `relatedResource` to `VerifiablePresentation` w3c/vc-data-model#1265, by @OR13.
-
-
6 issues closed.
-
Normative requirement for securing a VC or VP w3c/vc-data-model#1282.
-
Protected term errors when supporting v1 and v2 w3c/vc-data-model#1150.
-
Arrays of Arrays are problematic in VCDM w3c/vc-data-model#1132.
-
Security and Privacy Self-Review Questionnaire w3c/vc-data-model#1157.
-
Add guidance on ignoring optional fields w3c/vc-data-model#1027.
-
Spec does not contain "name" and "description" terms in the context w3c/vc-data-model#1214.
-
-
1 issue reopened.
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247, by @Sakurann.
-
-
32 issues received 141 new comments.
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264 (21 comments by @aphillips, @BigBlueHat, @dlongley, @gkellogg, @iherman, @msporny, @shigeya, @TallTed)
-
are `domain` and `range` correct for all properties in data model? w3c/vc-data-model#1263 (14 comments by @brentzundel, @bumblefudge, @iherman, @OR13)
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010 (12 comments by @David-Chadwick, @hendersonweb, @iherman, @MizukiSonoko)
-
Internationalization Review for VCDM 2.0 w3c/vc-data-model#1155 (11 comments by @aphillips, @iherman, @msporny, @Sakurann, @shigeya)
-
JSON-only processors and VCDM 2.0 conformance w3c/vc-data-model#1290 (10 comments by @awoie, @dlongley, @OR13, @selfissued, @thereisnogabe)
-
Add `relatedResource` to `VerifiablePresentation` w3c/vc-data-model#1265 (8 comments by @dmitrizagidulin, @iherman, @jandrieu, @msporny, @Sakurann)
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247 (6 comments by @iherman, @kdenhartog, @Sakurann)
-
Prefer Arrays and Objects. w3c/vc-data-model#1292 (5 comments by @brianorwhatever, @dmitrizagidulin, @gobengo, @OR13)
-
Add `revoked` and `expired` to verification method classes w3c/vc-data-model#1262 (5 comments by @dlongley, @iherman, @OR13)
-
Conformance requirements for normative context w3c/vc-data-model#1185 (3 comments by @iherman, @msporny, @OR13)
-
Multiple Credential Status Lists w3c/vc-data-model#1291 (2 comments by @bruno-zimmermann-bit, @msporny)
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246 (2 comments by @iherman)
-
Mitigating Location Correlation via Common Issuers w3c/vc-data-model#1245 (2 comments by @iherman, @Sakurann)
-
Allow string values in JOSE properties in base JSON-LD context w3c/vc-data-model#1275 (2 comments by @iherman, @selfissued)
-
Normative requirement for securing a VC or VP w3c/vc-data-model#1282 (2 comments by @Sakurann, @thereisnogabe)
-
Document the value of processing as JSON-LD w3c/vc-data-model#1227 (2 comments by @iherman, @msporny)
-
Address normative concept of VerifiableCredentialGraph w3c/vc-data-model#1240 (2 comments by @iherman, @msporny)
-
Security and Privacy Self-Review Questionnaire w3c/vc-data-model#1157 (2 comments by @awoie, @brentzundel)
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206 (1 comment by @msporny)
-
Recommend that authors don't use `@base` in `@context` w3c/vc-data-model#1266 (1 comment by @msporny)
-
Section title and contents mismatch on "Complex Language Markup" w3c/vc-data-model#1254 (1 comment by @iherman)
-
Spec does not contain "name" and "description" terms in the context w3c/vc-data-model#1214 (1 comment by @msporny)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @iherman)
-
-
17 pull requests opened.
-
Update to Terms of Use description w3c/vc-data-model#1295, by @David-Chadwick.
-
removes ToU from the main text while keeping it in the reserved extension points table w3c/vc-data-model#1294, by @Sakurann.
-
Fix various aspects of privacy.html w3c/vc-data-model#1288, by @TallTed.
-
Sync v2 context with data integrity context. w3c/vc-data-model#1287, by @dlongley.
-
Privacy considerations around issuer location w3c/vc-data-model#1286, by @thereisnogabe.
-
Add normative text requiring protecting VCs and VPs w3c/vc-data-model#1283, by @andresuribe87.
-
Add normative requirements related to context processing w3c/vc-data-model#1281, by @msporny.
-
Add definition of Verifiable Credential Graph and why it exists w3c/vc-data-model#1280, by @msporny.
-
Add links to static copies of vocabulary files and hashes w3c/vc-data-model#1279, by @msporny.
-
Base classes are defined now in the spec w3c/vc-data-model#1278, by @iherman.
-
Fix markup, typos, and a small fix. w3c/vc-data-model#1277, by @davidlehn.
-
Warn that using dynamic processor features might lead to less interoperability w3c/vc-data-model#1276, by @msporny.
-
Add base classes and fragment identifiers for vocabulary. w3c/vc-data-model#1272, by @msporny.
-
Warn authors that usage of global JSON-LD keywords might harm interoperability w3c/vc-data-model#1271, by @msporny.
-
Explain JSON-LD further. w3c/vc-data-model#1270, by @BigBlueHat.
-
updated entity to include abstract nouns w3c/vc-data-model#1269, by @jandrieu.
-
Adding the jsonSchema property to the vocabulary w3c/vc-data-model#1268, by @iherman.
-
-
14 pull requests merged.
-
Add normative text requiring protecting VCs and VPs w3c/vc-data-model#1283.
-
Fix various aspects of privacy.html w3c/vc-data-model#1288.
-
Sync v2 context with data integrity context. w3c/vc-data-model#1287.
-
Add normative requirements related to context processing w3c/vc-data-model#1281.
-
Add definition of Verifiable Credential Graph and why it exists w3c/vc-data-model#1280.
-
Fix markup, typos, and a small fix. w3c/vc-data-model#1277.
-
Add base classes and fragment identifiers for vocabulary. w3c/vc-data-model#1272.
-
updated entity to include abstract nouns w3c/vc-data-model#1269.
-
Base classes are defined now in the spec w3c/vc-data-model#1278.
-
Add validation section regarding holder w3c/vc-data-model#1199.
-
Adding the jsonSchema property to the vocabulary w3c/vc-data-model#1268.
-
Sync and fix bugs in v2 context. w3c/vc-data-model#1259.
-
Guidance around arrays w3c/vc-data-model#1258.
-
Address optionality of fields w3c/vc-data-model#1256.
-
-
1 pull request closed.
-
Add Verification Method types to v2 context w3c/vc-data-model#1260.
-
-
23 pull requests received 250 new comments.
-
Explain JSON-LD further. w3c/vc-data-model#1270 (53 comments by @BigBlueHat, @davidlehn, @dlongley, @iherman, @nadalin, @peacekeeper, @Sakurann, @TallTed, @thereisnogabe, @wip-abramson)
-
Add links to static copies of vocabulary files and hashes w3c/vc-data-model#1279 (32 comments by @BigBlueHat, @davidlehn, @iherman, @msporny, @OR13, @TallTed)
-
Warn that using dynamic processor features might lead to less interoperability w3c/vc-data-model#1276 (19 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @pchampin, @TallTed)
-
Add normative text requiring protecting VCs and VPs w3c/vc-data-model#1283 (15 comments by @andresuribe87, @jandrieu, @msporny, @TallTed, @thereisnogabe)
-
updated entity to include abstract nouns w3c/vc-data-model#1269 (15 comments by @brentzundel, @dlongley, @iherman, @msporny, @TallTed)
-
Adding the jsonSchema property to the vocabulary w3c/vc-data-model#1268 (14 comments by @iherman, @TallTed, @thereisnogabe)
-
Warn authors that usage of global JSON-LD keywords might harm interoperability w3c/vc-data-model#1271 (13 comments by @aphillips, @BigBlueHat, @brianorwhatever, @dlongley, @iherman, @msporny, @OR13, @seabass-labrax, @TallTed)
-
Fix markup, typos, and a small fix. w3c/vc-data-model#1277 (12 comments by @davidlehn, @iherman, @msporny, @TallTed)
-
Add base classes and fragment identifiers for vocabulary. w3c/vc-data-model#1272 (11 comments by @iherman, @msporny, @TallTed)
-
Guidance around arrays w3c/vc-data-model#1258 (9 comments by @brentzundel, @iherman, @msporny, @TallTed)
-
Sync and fix bugs in v2 context. w3c/vc-data-model#1259 (8 comments by @dlongley, @iherman, @msporny, @OR13)
-
Add Verification Method types to v2 context w3c/vc-data-model#1260 (7 comments by @dlongley, @iherman, @Sakurann)
-
Privacy considerations around issuer location w3c/vc-data-model#1286 (5 comments by @msporny, @TallTed)
-
Address optionality of fields w3c/vc-data-model#1256 (5 comments by @brentzundel, @iherman, @OR13, @TallTed)
-
Add normative requirements related to context processing w3c/vc-data-model#1281 (4 comments by @iherman, @msporny, @TallTed)
-
Sync v2 context with data integrity context. w3c/vc-data-model#1287 (3 comments by @dlongley, @msporny, @OR13)
-
Add section about Names and Descriptions of credentials. w3c/vc-data-model#1252 (1 comment by @iherman)
-
w3c/vc-di-eddsa
-
1 issue opened.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-eddsa#62, by @selfissued.
-
-
2 issues closed.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-eddsa#57.
-
Add definition for secretKeyMultibase serialization w3c/vc-di-eddsa#56.
-
-
3 issues received 3 new comments.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-eddsa#57 (1 comment by @msporny)
-
1 pull request opened.
-
Remove references to Multiformats specifications. w3c/vc-di-eddsa#63, by @msporny.
-
-
2 pull requests merged.
-
Add secretKeyMultibase definition. w3c/vc-di-eddsa#61.
-
Add advisements to read Data Integrity considerations sections. w3c/vc-di-eddsa#60.
-
-
3 pull requests received 13 new comments.
-
Remove references to Multiformats specifications. w3c/vc-di-eddsa#63 (11 comments by @iherman, @msporny, @TallTed)
-
Add advisements to read Data Integrity considerations sections. w3c/vc-di-eddsa#60 (1 comment by @msporny)
-
w3c/vc-data-integrity
-
10 issues opened.
-
What's a "document"? w3c/vc-data-integrity#208, by @jyasskin.
-
The definition of "cryptographic suite" should include or point to its whole definition w3c/vc-data-integrity#207, by @jyasskin.
-
Verify Proof should take the cryptographic suite as a parameter w3c/vc-data-integrity#206, by @jyasskin.
-
representation-eddsa-rdfc-2022 Test Vector Issue w3c/vc-data-integrity#204, by @a-c-brown.
-
I think the diagram key should be changed from `Graph Containment` to `Contains` w3c/vc-data-integrity#203, by @TallTed.
-
https://w3id.org/security/data-integrity/v1 is an octet-stream w3c/vc-data-integrity#200, by @jeswr.
-
Correct statements about standardization of multibase and multihash w3c/vc-data-integrity#192, by @selfissued.
-
Remove references to multibase w3c/vc-data-integrity#191, by @selfissued.
-
Add explanation about why proof graphs are used w3c/vc-data-integrity#190, by @msporny.
-
`expires rdfs:domain` intersection vs `expires schema:domainIncludes` union w3c/vc-data-integrity#188, by @TallTed.
-
-
10 issues closed.
-
[EDDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#195.
-
[ECDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#194.
-
Add Privacy Consideration for previous signers in proof chains w3c/vc-data-integrity#168.
-
Correct statements about standardization of multibase and multihash w3c/vc-data-integrity#192.
-
https://w3id.org/security/data-integrity/v1 is an octet-stream w3c/vc-data-integrity#200.
-
`expires rdfs:domain` intersection vs `expires schema:domainIncludes` union w3c/vc-data-integrity#188.
-
Adjustments to the `revoked` property w3c/vc-data-integrity#182.
-
When converting to RDF, ensure that BASE URL is null. w3c/vc-data-integrity#180.
-
Inconsistencies in our URLs w3c/vc-data-integrity#177.
-
Add reference back to VC Data Model Security and Privacy Considerations sections w3c/vc-data-integrity#167.
-
-
15 issues received 44 new comments.
-
I think the diagram key should be changed from `Graph Containment` to `Contains` w3c/vc-data-integrity#203 (5 comments by @iherman, @msporny)
-
Remove references to multibase w3c/vc-data-integrity#191 (5 comments by @BigBlueHat, @iherman, @msporny, @OR13)
-
Correct statements about standardization of multibase and multihash w3c/vc-data-integrity#192 (4 comments by @iherman, @msporny, @OR13)
-
representation-eddsa-rdfc-2022 Test Vector Issue w3c/vc-data-integrity#204 (4 comments by @a-c-brown, @dlongley, @Wind4Greg)
-
`expires rdfs:domain` intersection vs `expires schema:domainIncludes` union w3c/vc-data-integrity#188 (4 comments by @iherman, @TallTed)
-
[ECDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#194 (3 comments by @msporny)
-
Add Privacy Consideration for previous signers in proof chains w3c/vc-data-integrity#168 (3 comments by @msporny)
-
need resourceIntegrity in vocab and under w3c w3c/vc-data-integrity#193 (3 comments by @iherman, @OR13)
-
Add reference back to VC Data Model Security and Privacy Considerations sections w3c/vc-data-integrity#167 (3 comments by @bob420-svg, @msporny)
-
[EDDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#195 (2 comments by @msporny)
-
https://w3id.org/security/data-integrity/v1 is an octet-stream w3c/vc-data-integrity#200 (2 comments by @davidlehn, @TallTed)
-
When converting to RDF, ensure that BASE URL is null. w3c/vc-data-integrity#180 (1 comment by @msporny)
-
-
7 pull requests opened.
-
Add `previousProof` term mapping definition. w3c/vc-data-integrity#202, by @dlongley.
-
Fix context media types served by github pages. w3c/vc-data-integrity#201, by @dlongley.
-
Add sections on security/privacy and c14n method selection. w3c/vc-data-integrity#199, by @msporny.
-
Add section on previous proof privacy consideration. w3c/vc-data-integrity#198, by @msporny.
-
Update status of Multibase and Multihash at IETF. w3c/vc-data-integrity#197, by @msporny.
-
Remove normative dependency on Multibase and Multihash. w3c/vc-data-integrity#196, by @msporny.
-
Updated vocabulary and diagram w3c/vc-data-integrity#189, by @iherman.
-
-
9 pull requests merged.
-
Add `previousProof` term mapping definition. w3c/vc-data-integrity#202.
-
Add sections on security/privacy and c14n method selection. w3c/vc-data-integrity#199.
-
Add section on previous proof privacy consideration. w3c/vc-data-integrity#198.
-
Update status of Multibase and Multihash at IETF. w3c/vc-data-integrity#197.
-
Fix context media types served by github pages. w3c/vc-data-integrity#201.
-
Updated vocabulary and diagram w3c/vc-data-integrity#189.
-
Align context URLs with vocabulary URLs. w3c/vc-data-integrity#186.
-
Ensure that base URL is set to null when processing as RDF. w3c/vc-data-integrity#185.
-
Add `revoked` and `expires` properties to JsonWebKey context. w3c/vc-data-integrity#184.
-
-
1 pull request closed.
-
Update controller document reference w3c/vc-data-integrity#99.
-
-
11 pull requests received 98 new comments.
-
Remove normative dependency on Multibase and Multihash. w3c/vc-data-integrity#196 (40 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @selfissued, @TallTed)
-
Add sections on security/privacy and c14n method selection. w3c/vc-data-integrity#199 (22 comments by @dlongley, @iherman, @kdenhartog, @msporny, @TallTed)
-
Updated vocabulary and diagram w3c/vc-data-integrity#189 (14 comments by @iherman, @msporny, @TallTed)
-
Add `revoked` and `expires` properties to JsonWebKey context. w3c/vc-data-integrity#184 (6 comments by @dlongley, @msporny, @OR13, @TallTed)
-
Add section on previous proof privacy consideration. w3c/vc-data-integrity#198 (4 comments by @msporny, @TallTed)
-
Ensure that base URL is set to null when processing as RDF. w3c/vc-data-integrity#185 (3 comments by @msporny)
-
Update status of Multibase and Multihash at IETF. w3c/vc-data-integrity#197 (2 comments by @msporny, @TallTed)
-
w3c/vc-jose-cose
-
4 issues opened.
-
Controller Documents vs DID Documents w3c/vc-jose-cose#160, by @OR13.
-
We need to specify the exact format of DID URL we expect w3c/vc-jose-cose#158, by @TallTed.
-
Add guidance on using JWT-VCs when using the SD-JWT media types w3c/vc-jose-cose#157, by @selfissued.
-
Controller document examples w3c/vc-jose-cose#154, by @OR13.
-
-
23 issues closed.
-
Explain relationship between controller documents and JOSE headers w3c/vc-jose-cose#106.
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-jose-cose#31.
-
JWT exp claim w3c/vc-jose-cose#39.
-
Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` w3c/vc-jose-cose#141.
-
Add guidance on using JWT-VCs when using the SD-JWT media types w3c/vc-jose-cose#157.
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118.
-
Describe how `cnf` is allowed to be used for "binding" w3c/vc-jose-cose#52.
-
Clarify relationship between validity times w3c/vc-jose-cose#133.
-
Should we comment on "principle"? w3c/vc-jose-cose#35.
-
JWT - securing mechanism or not? w3c/vc-jose-cose#132.
-
typ for COSE w3c/vc-jose-cose#67.
-
Better references to OIDC key discovery w3c/vc-jose-cose#127.
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#22.
-
Add Privacy and Security Considerations w3c/vc-jose-cose#34.
-
Provide guidance on use of `cty` in JOSE / COSE w3c/vc-jose-cose#47.
-
Guidance on collisions between VC property names and registered JWT claims w3c/vc-jose-cose#98.
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9.
-
Update guidance for `application/vc+jwt` w3c/vc-jose-cose#72.
-
Update `application/vc+ld+jwt` w3c/vc-jose-cose#71.
-
Change `typ` values for JSON-LD claim sets? w3c/vc-jose-cose#57.
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15.
-
Deprecate `vc` & `vp` ? w3c/vc-jose-cose#119.
-
-
40 issues received 103 new comments.
-
Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` w3c/vc-jose-cose#141 (7 comments by @alenhorvat, @msporny, @OR13, @Sakurann, @selfissued)
-
JWT - securing mechanism or not? w3c/vc-jose-cose#132 (7 comments by @alenhorvat, @OR13, @selfissued)
-
Can registered JWT claims be used only in the JOSE header?? w3c/vc-jose-cose#135 (6 comments by @alenhorvat, @iherman, @OR13, @Sakurann, @selfissued)
-
File PING request once rename is complete w3c/vc-jose-cose#128 (6 comments by @awoie, @Sakurann, @selfissued)
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30 (6 comments by @BigBlueHat, @iherman, @Sakurann, @selfissued)
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64 (5 comments by @David-Chadwick, @Sakurann, @selfissued)
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-jose-cose#31 (4 comments by @BigBlueHat, @iherman, @Sakurann, @selfissued)
-
We need to specify the exact format of DID URL we expect w3c/vc-jose-cose#158 (4 comments by @msporny, @OR13, @selfissued)
-
Explain relationship between controller documents and JOSE headers w3c/vc-jose-cose#106 (3 comments by @iherman, @OR13, @selfissued)
-
Add guidance on "flat" vs "compact". w3c/vc-jose-cose#107 (3 comments by @OR13, @Sakurann, @selfissued)
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (3 comments by @iherman, @Sakurann, @selfissued)
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117 (3 comments by @iherman, @OR13, @Sakurann)
-
Guidance on collisions between VC property names and registered JWT claims w3c/vc-jose-cose#98 (3 comments by @Sakurann)
-
Clarify relationship between validity times w3c/vc-jose-cose#133 (2 comments by @iherman, @Sakurann)
-
Describe how `cnf` is allowed to be used for "binding" w3c/vc-jose-cose#52 (2 comments by @iherman, @selfissued)
-
Add guidance on using JWT-VCs when using the SD-JWT media types w3c/vc-jose-cose#157 (1 comment by @selfissued)
-
Add external references to Privacy and Security sections w3c/vc-jose-cose#81 (1 comment by @selfissued)
-
Determine whether to include content from Verifiable Credentials Implementation Guidelines w3c/vc-jose-cose#28 (1 comment by @Sakurann)
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15 (1 comment by @Sakurann)
-
-
11 pull requests opened.
-
Add Cred Metadata to Example w3c/vc-jose-cose#159, by @David-Chadwick.
-
Use Correct Names for Things w3c/vc-jose-cose#156, by @selfissued.
-
Tighten "cnf" claim description w3c/vc-jose-cose#155, by @selfissued.
-
add guidance on kid w3c/vc-jose-cose#153, by @Sakurann.
-
point to an ietf cose wg adopted draft for a COSE typ header w3c/vc-jose-cose#152, by @Sakurann.
-
explain the usage of exp and iat jwt claims w3c/vc-jose-cose#151, by @Sakurann.
-
Opinions w3c/vc-jose-cose#150, by @bob420-svg.
-
Remove JWT references (keep SD-JWT) w3c/vc-jose-cose#149, by @OR13.
-
replace openid-configuration well-known URI with jwt issuer well-known URI w3c/vc-jose-cose#148, by @Sakurann.
-
clarify that what is secured is a document conforming to vcdm w3c/vc-jose-cose#147, by @Sakurann.
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#146, by @Sakurann.
-
-
11 pull requests merged.
-
Add support for DIDs w3c/vc-jose-cose#144.
-
Use Correct Names for Things w3c/vc-jose-cose#156.
-
Tighten "cnf" claim description w3c/vc-jose-cose#155.
-
add guidance on kid w3c/vc-jose-cose#153.
-
Remove JWT references (keep SD-JWT) w3c/vc-jose-cose#149.
-
explain the usage of exp and iat jwt claims w3c/vc-jose-cose#151.
-
clarify that what is secured is a document conforming to vcdm w3c/vc-jose-cose#147.
-
point to an ietf cose wg adopted draft for a COSE typ header w3c/vc-jose-cose#152.
-
replace openid-configuration well-known URI with jwt issuer well-known URI w3c/vc-jose-cose#148.
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#146.
-
Changes to normative statements w3c/vc-jose-cose#143.
-
-
1 pull request closed.
-
Opinions w3c/vc-jose-cose#150.
-
-
12 pull requests received 216 new comments.
-
Add support for DIDs w3c/vc-jose-cose#144 (111 comments by @bob420-svg, @iherman, @melvincarvalho, @msporny, @OR13, @Sakurann, @selfissued, @TallTed)
-
Remove JWT references (keep SD-JWT) w3c/vc-jose-cose#149 (30 comments by @alenhorvat, @BigBlueHat, @bob420-svg, @danielfett, @iherman, @OR13, @Sakurann, @TallTed)
-
explain the usage of exp and iat jwt claims w3c/vc-jose-cose#151 (14 comments by @David-Chadwick, @iherman, @Sakurann, @selfissued, @TallTed)
-
add guidance on kid w3c/vc-jose-cose#153 (12 comments by @iherman, @jandrieu, @msporny, @OR13, @Sakurann, @selfissued, @TallTed)
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#146 (11 comments by @OR13, @Sakurann, @selfissued, @TallTed)
-
Changes to normative statements w3c/vc-jose-cose#143 (11 comments by @iherman, @OR13, @Sakurann, @TallTed)
-
Use Correct Names for Things w3c/vc-jose-cose#156 (8 comments by @iherman, @OR13, @selfissued, @TallTed)
-
Tighten "cnf" claim description w3c/vc-jose-cose#155 (4 comments by @andresuribe87, @iherman, @OR13, @TallTed)
-
clarify that what is secured is a document conforming to vcdm w3c/vc-jose-cose#147 (3 comments by @Sakurann, @TallTed)
-
replace openid-configuration well-known URI with jwt issuer well-known URI w3c/vc-jose-cose#148 (3 comments by @OR13, @selfissued)
-
point to an ietf cose wg adopted draft for a COSE typ header w3c/vc-jose-cose#152 (2 comments by @Sakurann, @TallTed)
-
w3c/vc-test-suite
-
2 issues opened.
-
config.json.example comments could use valid JSON w3c/vc-test-suite#133, by @marnanel.
-
README.nd and config.json.example differ as to sequence of install operations w3c/vc-test-suite#132, by @marnanel.
-
-
2 issues received 20 new comments.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (19 comments by @alanhkarp, @alenhorvat, @David-Chadwick, @iherman, @longpd, @OR13, @Sakurann, @TallTed)
-
-
1 pull request opened.
-
Credivera, Update Test Suite to Support REST APIs w3c/vc-test-suite#131, by @adam-credivera.
-
w3c/vc-bitstring-status-list
-
5 issues opened.
-
Queries regarding the Specification w3c/vc-bitstring-status-list#88, by @arnabghose997.
-
Should validation algorithm check size of bitstring? w3c/vc-bitstring-status-list#87, by @andresuribe87.
-
Add privacy considerations for multi-bit correlation w3c/vc-bitstring-status-list#86, by @msporny.
-
Split design space into two different types of status lists w3c/vc-bitstring-status-list#85, by @msporny.
-
Cascading status updates w3c/vc-bitstring-status-list#84, by @OR13.
-
-
7 issues closed.
-
Queries regarding the Specification w3c/vc-bitstring-status-list#88.
-
Split design space into two different types of status lists w3c/vc-bitstring-status-list#85.
-
Versioning w3c/vc-bitstring-status-list#50.
-
Hexstrings vs. Bitstrings w3c/vc-bitstring-status-list#5.
-
Preventing multiple single-credential status lists per issuer w3c/vc-bitstring-status-list#6.
-
Define TTL and caching behavior for lists w3c/vc-bitstring-status-list#38.
-
Verification should fail for revocable credentials for status list that cannot be deferenced w3c/vc-bitstring-status-list#39.
-
-
17 issues received 40 new comments.
-
Cascading status updates w3c/vc-bitstring-status-list#84 (8 comments by @brianorwhatever, @ghost, @iherman, @msporny, @OR13, @paulfdietrich, @Sakurann, @thereisnogabe)
-
auto-publishing using echidna? w3c/vc-bitstring-status-list#82 (6 comments by @iherman, @OR13, @TallTed)
-
Split design space into two different types of status lists w3c/vc-bitstring-status-list#85 (4 comments by @iherman, @msporny, @Sakurann, @thereisnogabe)
-
Can the spec relax/remove the requirement on minimal bit length? w3c/vc-bitstring-status-list#14 (3 comments by @iherman, @jandrieu, @thehenrytsai)
-
clarify protocol for retrieval of a status list w3c/vc-bitstring-status-list#44 (3 comments by @andresuribe87, @iherman, @jandrieu)
-
Add section on expected server HTTP status codes w3c/vc-bitstring-status-list#64 (2 comments by @iherman, @Sakurann)
-
Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation w3c/vc-bitstring-status-list#80 (2 comments by @kdenhartog, @Sakurann)
-
Add privacy considerations for multi-bit correlation w3c/vc-bitstring-status-list#86 (1 comment by @iherman)
-
Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) w3c/vc-bitstring-status-list#51 (1 comment by @iherman)
-
Preventing multiple single-credential status lists per issuer w3c/vc-bitstring-status-list#6 (1 comment by @msporny)
-
-
1 pull request merged.
-
Example both with revocation and suspension w3c/vc-bitstring-status-list#83.
-
-
1 pull request received 1 new comment.
-
Example both with revocation and suspension w3c/vc-bitstring-status-list#83 (1 comment by @brentzundel)
-
w3c/vc-json-schema
-
1 issue opened.
-
Pre-CR normative dependencies will trigger a 2nd CR w3c/vc-json-schema#210, by @msporny.
-
-
6 issues closed.
-
Pre-CR normative dependencies will trigger a 2nd CR w3c/vc-json-schema#210.
-
Add guidance for wallets when using JsonSchemaCredential and selected disclosure w3c/vc-json-schema#202.
-
Formalize the jsonSchema property in the VCDM vocabulary? w3c/vc-json-schema#206.
-
Test suite w3c/vc-json-schema#134.
-
Getting to a REC w3c/vc-json-schema#135.
-
Add guidance on inclusion of unique tracking identifiers w3c/vc-json-schema#201.
-
-
1 issue reopened.
-
Pre-CR normative dependencies will trigger a 2nd CR w3c/vc-json-schema#210, by @thereisnogabe.
-
-
3 issues received 14 new comments.
-
Pre-CR normative dependencies will trigger a 2nd CR w3c/vc-json-schema#210 (11 comments by @iherman, @msporny, @OR13, @thereisnogabe)
-
Formalize the jsonSchema property in the VCDM vocabulary? w3c/vc-json-schema#206 (2 comments by @iherman, @thereisnogabe)
-
-
8 pull requests opened.
-
Add section on revision history w3c/vc-json-schema#218, by @thereisnogabe.
-
Prepare for CR w3c/vc-json-schema#217, by @thereisnogabe.
-
Address normative references issues w3c/vc-json-schema#216, by @thereisnogabe.
-
fix a plural that should be singular w3c/vc-json-schema#215, by @TallTed.
-
typo and language fixes w3c/vc-json-schema#214, by @TallTed.
-
Add privacy considerations around data minimization w3c/vc-json-schema#213, by @thereisnogabe.
-
Address part of 210 w3c/vc-json-schema#212, by @thereisnogabe.
-
Add test suite to readme; term definition for jsonschema w3c/vc-json-schema#211, by @thereisnogabe.
-
-
8 pull requests merged.
-
Prepare for CR w3c/vc-json-schema#217.
-
Address normative references issues w3c/vc-json-schema#216.
-
Add privacy considerations around data minimization w3c/vc-json-schema#213.
-
Address part of 210 w3c/vc-json-schema#212.
-
fix a plural that should be singular w3c/vc-json-schema#215.
-
typo and language fixes w3c/vc-json-schema#214.
-
Add test suite to readme; term definition for jsonschema w3c/vc-json-schema#211.
-
Discourage Unique tracking IDs w3c/vc-json-schema#209.
-
-
7 pull requests received 43 new comments.
-
Address normative references issues w3c/vc-json-schema#216 (21 comments by @andresuribe87, @iherman, @msporny, @OR13, @thereisnogabe)
-
Add test suite to readme; term definition for jsonschema w3c/vc-json-schema#211 (9 comments by @iherman, @TallTed, @thereisnogabe)
-
w3c/vc-di-bbs
-
1 issue opened.
-
Remove references to MULTIBASE and MULTICODEC w3c/vc-di-bbs#92, by @selfissued.
-
-
1 issue received 29 new comments.
-
Hashing (bbs-proof-2023) w3c/vc-di-bbs#84 (29 comments by @brianorwhatever, @dlongley, @OR13, @Wind4Greg)
-
-
1 pull request opened.
-
Removing myself from the work item w3c/vc-di-bbs#91, by @OR13.
-
-
1 pull request received 1 new comment.
w3c/cid
-
1 issue opened.
-
Define "valid" w3c/cid#35, by @jyasskin.
-
w3c/vc-extensions
-
1 pull request opened.
-
Update and rename credential-schema-2023.json to credential-schema.json w3c/vc-extensions#29, by @thereisnogabe.
-
w3c/vc-jose-cose-test-suite
-
1 issue opened.
-
Positive and negative testing for Accept header in requests w3c/vc-jose-cose-test-suite#8, by @rhofvendahl.
-
-
3 issues received 6 new comments.
-
Representing extension validation in tests w3c/vc-jose-cose-test-suite#9 (3 comments by @bob420-svg, @OR13, @thereisnogabe)
-
Positive and negative testing for Accept header in requests w3c/vc-jose-cose-test-suite#8 (1 comment by @bob420-svg)
-
w3c/vc-data-model-2.0-test-suite
-
1 issue received 1 new comment.
w3c/vcalm
-
1 issue received 1 new comment.
TR publications
-
47 documents published.
-
Verifiable Credential Data Integrity 1.0 published 9 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published 13 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Verifiable Credentials JSON Schema Specification published 11 times as a Working Draft. History of Verifiable Credentials JSON Schema Specification
-
Data Integrity ECDSA Cryptosuites v1.0 published 6 times as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Data Integrity EdDSA Cryptosuites v1.0 published 3 times as a Working Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Securing Verifiable Credentials using JOSE and COSE published 5 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
Past meetings
-
10 meetings.
Participants
-
2 participants joined.
-
Nicholas Steele (1Password) joined.
-
Benjamin Young (Digital Bazaar) joined.
-
-
2 participants left.
-
Philip Feairheller (GLEIF) left.
-
Benjamin Young (Digital Bazaar) left.
-
-
1 organization left.
-
Crossword Cybersecurity left.
-
GitHub
w3c/vc-data-model
-
21 issues opened.
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264, by @msporny.
-
are `domain` and `range` correct for all properties in data model? w3c/vc-data-model#1263, by @TallTed.
-
Add `revoked` and `expired` to verification method classes w3c/vc-data-model#1262, by @OR13.
-
Add cryptographic hashes for vocabulary files w3c/vc-data-model#1261, by @msporny.
-
Section title and contents mismatch on "Complex Language Markup" w3c/vc-data-model#1254, by @shigeya.
-
signatures should be on quoted graphs w3c/vc-data-model#1248, by @bblfish.
-
Add Security Consideration to avoid key reuse w3c/vc-data-model#1284, by @msporny.
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247, by @awoie.
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246, by @awoie.
-
Mitigating Location Correlation via Common Issuers w3c/vc-data-model#1245, by @awoie.
-
Address Metadata-Driven Correlation w3c/vc-data-model#1244, by @awoie.
-
Recommend that DIDs are used with VCs w3c/vc-data-model#1243, by @thereisnogabe.
-
Address normative concept of VerifiableCredentialGraph w3c/vc-data-model#1240, by @OR13.
-
`expires` header for https://www.w3.org/2018/credentials/v1 is in the past w3c/vc-data-model#1239, by @jeswr.
-
Add references to Sub-Resource Integrity w3c/vc-data-model#1237, by @thereisnogabe.
-
Revert language change on the definition of Subject w3c/vc-data-model#1235, by @jandrieu.
-
[VC-JWT] Reference is wrong w3c/vc-data-model#1233, by @nikosft.
-
Revisit validation vs verification w3c/vc-data-model#1232, by @OR13.
-
Minor change to validFrom requested w3c/vc-data-model#1231, by @David-Chadwick.
-
Document the value of processing as JSON-LD w3c/vc-data-model#1227, by @OR13.
-
VCDM editors draft has incorrect link for published version w3c/vc-data-model#1224, by @brentzundel.
-
-
20 issues closed.
-
Media Types and HTTP w3c/vc-data-model#1118.
-
Indicating Encrypted VCs in VPs w3c/vc-data-model#938.
-
Provide guidance for when hash values do not match specification text w3c/vc-data-model#1177.
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860.
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965.
-
Clarify credentialStatus w3c/vc-data-model#991.
-
Minor change to validFrom requested w3c/vc-data-model#1231.
-
Ensure the base context doesn't constrain lower-maturity specifications w3c/vc-data-model#1175.
-
Missing security considerations on MITM, cloning etc. w3c/vc-data-model#1138.
-
`validFrom` and `validUntil` fields need better specification of `dateTime` w3c/vc-data-model#1193.
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009.
-
How should we refer to the Securing specifications? w3c/vc-data-model#1105.
-
Address "Credential" vs "VerifiableCredential" w3c/vc-data-model#1126.
-
[VC-JWT] Reference is wrong w3c/vc-data-model#1233.
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089.
-
VCDM editors draft has incorrect link for published version w3c/vc-data-model#1224.
-
Missing term in the vcdm spec w3c/vc-data-model#1216.
-
Entities and Parties w3c/vc-data-model#1173.
-
Media types other than vc+ld+json w3c/vc-data-model#1048.
-
Document how VCs are processed as JSON today w3c/vc-data-model#1201.
-
-
48 issues received 198 new comments.
-
signatures should be on quoted graphs w3c/vc-data-model#1248 (25 comments by @bblfish, @brentzundel, @dlongley, @iherman, @msporny, @TallTed)
-
Address normative concept of VerifiableCredentialGraph w3c/vc-data-model#1240 (22 comments by @iherman, @OR13, @TallTed)
-
Revert language change on the definition of Subject w3c/vc-data-model#1235 (16 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @RieksJ, @TallTed)
-
Minor change to validFrom requested w3c/vc-data-model#1231 (14 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @TallTed)
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010 (12 comments by @David-Chadwick, @hendersonweb, @OR13, @TallTed)
-
`expires` header for https://www.w3.org/2018/credentials/v1 is in the past w3c/vc-data-model#1239 (7 comments by @iherman, @msporny, @OR13)
-
Spec does not contain "name" and "description" terms in the context w3c/vc-data-model#1214 (5 comments by @iherman, @msporny, @selfissued)
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206 (5 comments by @brentzundel, @iherman, @msporny, @OR13)
-
Recommend that DIDs are used with VCs w3c/vc-data-model#1243 (5 comments by @iherman, @jandrieu, @OR13, @selfissued, @thereisnogabe)
-
are `domain` and `range` correct for all properties in data model? w3c/vc-data-model#1263 (4 comments by @dlongley, @OR13, @TallTed)
-
Protected term errors when supporting v1 and v2 w3c/vc-data-model#1150 (4 comments by @dlongley, @iherman, @msporny)
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089 (4 comments by @brentzundel, @iherman)
-
Add Security Consideration to avoid key reuse w3c/vc-data-model#1284 (4 comments by @kdenhartog, @msporny, @Wind4Greg)
-
Recommend that authors don't use `@language` in `@context` w3c/vc-data-model#1264 (3 comments by @aphillips, @msporny)
-
Revisit validation vs verification w3c/vc-data-model#1232 (3 comments by @iherman, @longpd, @thereisnogabe)
-
Add `revoked` and `expired` to verification method classes w3c/vc-data-model#1262 (3 comments by @dlongley, @iherman, @OR13)
-
Conformance requirements for normative context w3c/vc-data-model#1185 (3 comments by @brentzundel, @iherman, @OR13)
-
Strengthening Trust Boundaries for Holder Software in Verifiable Credential Processing w3c/vc-data-model#1246 (3 comments by @iherman, @jandrieu, @kdenhartog)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (2 comments by @brentzundel, @msporny)
-
Provide guidance for when hash values do not match specification text w3c/vc-data-model#1177 (2 comments by @iherman, @msporny)
-
VCDM editors draft has incorrect link for published version w3c/vc-data-model#1224 (2 comments by @brentzundel, @iherman)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (1 comment by @brentzundel)
-
Section title and contents mismatch on "Complex Language Markup" w3c/vc-data-model#1254 (1 comment by @iherman)
-
Addressing Verifier Stored Data Vulnerabilities and Legal Compliance w3c/vc-data-model#1247 (1 comment by @iherman)
-
`validFrom` and `validUntil` fields need better specification of `dateTime` w3c/vc-data-model#1193 (1 comment by @msporny)
-
Ensure the base context doesn't constrain lower-maturity specifications w3c/vc-data-model#1175 (1 comment by @msporny)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @iherman)
-
-
27 pull requests opened.
-
Add Verification Method types to v2 context w3c/vc-data-model#1260, by @OR13.
-
Sync and fix bugs in v2 context. w3c/vc-data-model#1259, by @msporny.
-
Guidance around arrays w3c/vc-data-model#1258, by @brentzundel.
-
VCDM Media Types and HTTP w3c/vc-data-model#1257, by @brentzundel.
-
Address optionality of fields w3c/vc-data-model#1256, by @brentzundel.
-
Editorial - update links to non-expired versions w3c/vc-data-model#1255, by @m00sey.
-
Vocabulary fixes — replacement of #1241 w3c/vc-data-model#1253, by @iherman.
-
Add section about Names and Descriptions of credentials. w3c/vc-data-model#1252, by @msporny.
-
Outline plan to mitigate normative context risk when transitioning to Proposed Recommendation w3c/vc-data-model#1251, by @msporny.
-
Apply range requirements to validFrom/validUntil. w3c/vc-data-model#1250, by @msporny.
-
Provide actionable guidance related to base context hash value. w3c/vc-data-model#1249, by @msporny.
-
Add sd-jwt registered claim names to v2 context w3c/vc-data-model#1242, by @OR13.
-
Vocabulary fixes w3c/vc-data-model#1241, by @OR13.
-
Add language on mitm, replay, spoofing attacks w3c/vc-data-model#1238, by @thereisnogabe.
-
Added an SVG diagram of the vocabulary. w3c/vc-data-model#1236, by @iherman.
-
Update links from VC-JWT to VC-JOSE-COSE w3c/vc-data-model#1234, by @andresuribe87.
-
Removing the serviceEndpoint vocabulary item w3c/vc-data-model#1230, by @iherman.
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis w3c/vc-data-model#1229, by @iherman.
-
Added reserved confidenceMethod property to the vocabulary — bis w3c/vc-data-model#1228, by @iherman.
-
Added reserved confidenceMethod property to the vocabulary w3c/vc-data-model#1226, by @iherman.
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 w3c/vc-data-model#1225, by @iherman.
-
Add aud registered claim to v2 context w3c/vc-data-model#1223, by @OR13.
-
Add exp registered claim to v2 context w3c/vc-data-model#1222, by @OR13.
-
Add nbf registered claim to v2 context w3c/vc-data-model#1221, by @OR13.
-
Add iat registered claim to v2 context w3c/vc-data-model#1220, by @OR13.
-
Add cnf registered claim to v2 context w3c/vc-data-model#1219, by @OR13.
-
Added JsonSchemaCredential to the vocabulary, and remove '2023' from JsonSchema2023 w3c/vc-data-model#1218, by @iherman.
-
-
27 pull requests merged.
-
VCDM Media Types and HTTP w3c/vc-data-model#1257.
-
Add section about Names and Descriptions of credentials. w3c/vc-data-model#1252.
-
Editorial - update links to non-expired versions w3c/vc-data-model#1255.
-
Vocabulary fixes — replacement of #1241 w3c/vc-data-model#1253.
-
Outline plan to mitigate normative context risk when transitioning to Proposed Recommendation w3c/vc-data-model#1251.
-
Apply range requirements to validFrom/validUntil. w3c/vc-data-model#1250.
-
Provide actionable guidance related to base context hash value. w3c/vc-data-model#1249.
-
Add language on mitm, replay, spoofing attacks w3c/vc-data-model#1238.
-
Add sd-jwt registered claim names to v2 context w3c/vc-data-model#1242.
-
Added an SVG diagram of the vocabulary. w3c/vc-data-model#1236.
-
Update links from VC-JWT to VC-JOSE-COSE w3c/vc-data-model#1234.
-
Refer to VC-SPECS-DIR for proof types. w3c/vc-data-model#1212.
-
Clarify the difference between a "credential" and a "verifiable credential" w3c/vc-data-model#1211.
-
Added reserved confidenceMethod property to the vocabulary — bis w3c/vc-data-model#1228.
-
Removing the serviceEndpoint vocabulary item w3c/vc-data-model#1230.
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis w3c/vc-data-model#1229.
-
Add aud registered claim to v2 context w3c/vc-data-model#1223.
-
Add exp registered claim to v2 context w3c/vc-data-model#1222.
-
Add nbf registered claim to v2 context w3c/vc-data-model#1221.
-
Add iat registered claim to v2 context w3c/vc-data-model#1220.
-
Add cnf registered claim to v2 context w3c/vc-data-model#1219.
-
Add section on JSON Processing. w3c/vc-data-model#1202.
-
Added JsonSchemaCredential to the vocabulary, and remove '2023' from JsonSchema2023 w3c/vc-data-model#1218.
-
Update term definition for vc json schemas as creds w3c/vc-data-model#1215.
-
Better not set §B as non-normative (minor editorial) w3c/vc-data-model#1200.
-
Add confidenceMethod to table of reserved terms and v2 `@context` w3c/vc-data-model#1142.
-
Add section on Ecosystem Compatibility. w3c/vc-data-model#1203.
-
-
5 pull requests closed.
-
Add "author" and "party" to terminology, rewrite "claim" terminology w3c/vc-data-model#1172.
-
Vocabulary fixes w3c/vc-data-model#1241.
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 w3c/vc-data-model#1225.
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101.
-
Added reserved confidenceMethod property to the vocabulary w3c/vc-data-model#1226.
-
-
37 pull requests received 695 new comments.
-
Add "author" and "party" to terminology, rewrite "claim" terminology w3c/vc-data-model#1172 (132 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @msporny, @OR13, @RieksJ, @TallTed, @thereisnogabe)
-
Add section on JSON Processing. w3c/vc-data-model#1202 (55 comments by @alenhorvat, @awoie, @brentzundel, @dlongley, @iherman, @mprorock, @msporny, @mtaimela, @OR13, @Sakurann, @selfissued, @TallTed, @thereisnogabe)
-
Add language on mitm, replay, spoofing attacks w3c/vc-data-model#1238 (52 comments by @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Add validation section regarding holder w3c/vc-data-model#1199 (48 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @longpd, @OR13, @RieksJ, @TallTed)
-
Clarify the difference between a "credential" and a "verifiable credential" w3c/vc-data-model#1211 (45 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @selfissued, @TallTed, @thereisnogabe)
-
Update term definition for vc json schemas as creds w3c/vc-data-model#1215 (41 comments by @andresuribe87, @dlongley, @iherman, @mprorock, @msporny, @OR13, @thereisnogabe)
-
Add section about Names and Descriptions of credentials. w3c/vc-data-model#1252 (40 comments by @aphillips, @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Sync and fix bugs in v2 context. w3c/vc-data-model#1259 (33 comments by @dlongley, @iherman, @msporny, @OR13, @seabass-labrax, @selfissued)
-
Add sd-jwt registered claim names to v2 context w3c/vc-data-model#1242 (26 comments by @brentzundel, @dlongley, @iherman, @msporny, @OR13, @peacekeeper, @Sakurann, @TallTed)
-
Added reserved confidenceMethod property to the vocabulary w3c/vc-data-model#1226 (24 comments by @iherman, @msporny, @OR13, @TallTed)
-
Guidance around arrays w3c/vc-data-model#1258 (18 comments by @andresuribe87, @brentzundel, @msporny, @OR13, @TallTed)
-
Apply range requirements to validFrom/validUntil. w3c/vc-data-model#1250 (15 comments by @David-Chadwick, @longpd, @msporny, @TallTed, @thereisnogabe)
-
Added JsonSchemaCredential to the vocabulary, and remove '2023' from JsonSchema2023 w3c/vc-data-model#1218 (14 comments by @iherman, @msporny, @OR13, @thereisnogabe)
-
Provide actionable guidance related to base context hash value. w3c/vc-data-model#1249 (12 comments by @iherman, @msporny, @TallTed, @thereisnogabe)
-
Outline plan to mitigate normative context risk when transitioning to Proposed Recommendation w3c/vc-data-model#1251 (11 comments by @iherman, @msporny, @OR13)
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 w3c/vc-data-model#1225 (10 comments by @brentzundel, @iherman, @msporny, @TallTed, @thereisnogabe)
-
Add Verification Method types to v2 context w3c/vc-data-model#1260 (9 comments by @dlongley, @msporny, @OR13)
-
Vocabulary fixes — replacement of #1241 w3c/vc-data-model#1253 (9 comments by @iherman, @msporny, @OR13, @seabass-labrax)
-
Add aud registered claim to v2 context w3c/vc-data-model#1223 (9 comments by @brentzundel, @msporny, @OR13)
-
Address optionality of fields w3c/vc-data-model#1256 (8 comments by @brentzundel, @jandrieu, @longpd, @msporny, @TallTed)
-
Added reserved confidenceMethod property to the vocabulary — bis w3c/vc-data-model#1228 (8 comments by @awoie, @iherman, @msporny, @TallTed)
-
Add section on Ecosystem Compatibility. w3c/vc-data-model#1203 (7 comments by @iherman, @msporny, @SmithSamuelM)
-
Update links from VC-JWT to VC-JOSE-COSE w3c/vc-data-model#1234 (6 comments by @andresuribe87, @iherman, @msporny, @TallTed, @thereisnogabe)
-
Add confidenceMethod to table of reserved terms and v2 `@context` w3c/vc-data-model#1142 (6 comments by @brentzundel, @iherman, @TallTed)
-
Editorial - update links to non-expired versions w3c/vc-data-model#1255 (5 comments by @m00sey, @msporny, @TallTed, @thereisnogabe)
-
Add cnf registered claim to v2 context w3c/vc-data-model#1219 (5 comments by @brentzundel, @davidlehn, @iherman, @msporny, @OR13)
-
Add nbf registered claim to v2 context w3c/vc-data-model#1221 (4 comments by @brentzundel, @davidlehn, @msporny, @OR13)
-
Add exp registered claim to v2 context w3c/vc-data-model#1222 (3 comments by @brentzundel, @msporny, @OR13)
-
Add iat registered claim to v2 context w3c/vc-data-model#1220 (3 comments by @brentzundel, @msporny, @OR13)
-
Better not set §B as non-normative (minor editorial) w3c/vc-data-model#1200 (2 comments by @iherman, @msporny)
-
Editorial update index.html: use JsonSchema and not JsonSchema2023 — bis w3c/vc-data-model#1229 (1 comment by @msporny)
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101 (1 comment by @Sakurann)
-
w3c/vcalm
-
6 issues opened.
-
Add callback url to exchanges? w3c/vcalm#347, by @brianorwhatever.
-
Add callback url to exchanges? w3c/vcalm#346, by @brianorwhatever.
-
Automating Verifiable Credential transfers w3c/vcalm#345, by @msporny.
-
Clarify how VC API is different from OID4 w3c/vcalm#344, by @msporny.
-
-
4 issues closed.
-
Add callback url to exchanges? w3c/vcalm#346.
-
Snapshot VC Issuer/Verifier API for VCWG? w3c/vcalm#304.
-
Microsoft calls their REST API "VC API" w3c/vcalm#342.
-
Docs with broken links/empty sections w3c/vcalm#215.
-
-
10 issues received 19 new comments.
-
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.) w3c/vcalm#285 (5 comments by @brianorwhatever, @dmitrizagidulin, @msporny)
-
Clarification on endpoints style for issuance , verification and derivation w3c/vcalm#343 (1 comment by @msporny)
-
w3c/vc-data-integrity
-
17 issues opened.
-
Clarify difference between a `verificationMethod` in a proof vs. a controller document w3c/vc-data-integrity#187, by @msporny.
-
Ensure proper capitalization of "context" and "vocabulary" w3c/vc-data-integrity#183, by @msporny.
-
Adjustments to the `revoked` property w3c/vc-data-integrity#182, by @OR13.
-
When converting to RDF, ensure that BASE URL is null. w3c/vc-data-integrity#180, by @msporny.
-
Inconsistencies in our URLs w3c/vc-data-integrity#177, by @iherman.
-
Apply diagram changes w3c/vc-data-integrity#175, by @iherman.
-
[EDDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#195, by @msporny.
-
[ECDSA] Highlight security/privacy trade-offs between RDF-CANON and JCS w3c/vc-data-integrity#194, by @msporny.
-
Add normative guidance that @context files SHOULD be cached w3c/vc-data-integrity#170, by @msporny.
-
Add Privacy Consideration for previous signers in proof chains w3c/vc-data-integrity#168, by @msporny.
-
Add reference back to VC Data Model Security and Privacy Considerations sections w3c/vc-data-integrity#167, by @msporny.
-
Conformance classes usage of the word "data model" w3c/vc-data-integrity#165, by @msporny.
-
Is another context required to express JsonWebKey or Multikey? w3c/vc-data-integrity#164, by @msporny.
-
Add sec:cryptosuiteString data type to vocabulary w3c/vc-data-integrity#161, by @msporny.
-
Clearly define conformance classes w3c/vc-data-integrity#159, by @msporny.
-
Do not assume errors can be surfaced w3c/vc-data-integrity#157, by @msporny.
-
Add definition sections for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#151, by @msporny.
-
-
22 issues closed.
-
Add normative guidance that @context files SHOULD be cached w3c/vc-data-integrity#170.
-
Should this suite normatively require integrity checking of the context files? w3c/vc-data-integrity#179.
-
Is another context required to express JsonWebKey or Multikey? w3c/vc-data-integrity#164.
-
Add sec:cryptosuiteString data type to vocabulary w3c/vc-data-integrity#161.
-
Expand use of `previousProof` to allow an array, define in security vocabulary w3c/vc-data-integrity#120.
-
Potential attacks on `previousProof` and algorithmic mitigations w3c/vc-data-integrity#87.
-
Expiration Date w3c/vc-data-integrity#78.
-
relating an agent to their key? w3c/vc-data-integrity#110.
-
Clearly define conformance classes w3c/vc-data-integrity#159.
-
Do not assume errors can be surfaced w3c/vc-data-integrity#157.
-
Add definition sections for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#151.
-
Add table for all error conditions w3c/vc-data-integrity#136.
-
Ensure that documents that drop data throw errors w3c/vc-data-integrity#131.
-
Add JsonWebKey definition in Data Integrity w3c/vc-data-integrity#130.
-
Missing term definitions in the spec w3c/vc-data-integrity#129.
-
Specify a default context if JSON-LD processing is required w3c/vc-data-integrity#88.
-
Domain and range of sec:publicKey w3c/vc-data-integrity#74.
-
domain of publicKeyJWK should be rdf:JSON w3c/vc-data-integrity#73.
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66.
-
Explain how proof types are mapped to URLs w3c/vc-data-integrity#60.
-
domain should be a string or array w3c/vc-data-integrity#29.
-
Add at least one unsigned properties w3c/vc-data-integrity#90.
-
-
29 issues received 83 new comments.
-
Apply diagram changes w3c/vc-data-integrity#175 (21 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Is another context required to express JsonWebKey or Multikey? w3c/vc-data-integrity#164 (6 comments by @msporny, @OR13)
-
Add reference back to VC Data Model Security and Privacy Considerations sections w3c/vc-data-integrity#167 (2 comments by @bob420-svg, @msporny)
-
Add normative guidance that @context files SHOULD be cached w3c/vc-data-integrity#170 (2 comments by @msporny)
-
Should this suite normatively require integrity checking of the context files? w3c/vc-data-integrity#179 (2 comments by @msporny)
-
Add sec:cryptosuiteString data type to vocabulary w3c/vc-data-integrity#161 (2 comments by @msporny)
-
Expand use of `previousProof` to allow an array, define in security vocabulary w3c/vc-data-integrity#120 (2 comments by @msporny)
-
Potential attacks on `previousProof` and algorithmic mitigations w3c/vc-data-integrity#87 (2 comments by @msporny)
-
Add definition sections for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#151 (2 comments by @msporny)
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (2 comments by @msporny, @OR13)
-
When converting to RDF, ensure that BASE URL is null. w3c/vc-data-integrity#180 (1 comment by @msporny)
-
Ensure proper capitalization of "context" and "vocabulary" w3c/vc-data-integrity#183 (1 comment by @msporny)
-
Specify a default context if JSON-LD processing is required w3c/vc-data-integrity#88 (1 comment by @msporny)
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66 (1 comment by @msporny)
-
-
25 pull requests opened.
-
Align context URLs with vocabulary URLs. w3c/vc-data-integrity#186, by @msporny.
-
Ensure that base URL is set to null when processing as RDF. w3c/vc-data-integrity#185, by @msporny.
-
Add `revoked` and `expires` properties to JsonWebKey context. w3c/vc-data-integrity#184, by @msporny.
-
Add cryptosuiteString to v2 context, preserving older v1 context. w3c/vc-data-integrity#181, by @msporny.
-
Align `datetimes` to `dateTimeStamp` values to ensure timezone. w3c/vc-data-integrity#178, by @msporny.
-
Add multibase datatype definition w3c/vc-data-integrity#176, by @msporny.
-
Add section on Resource Integrity and `digestMultibase`. w3c/vc-data-integrity#174, by @msporny.
-
Add section on "Other" Security and Privacy Considerations w3c/vc-data-integrity#173, by @msporny.
-
Add guidance on context and URL caching in general w3c/vc-data-integrity#172, by @msporny.
-
Updated the vocabulary and added a diagram w3c/vc-data-integrity#171, by @iherman.
-
Fix basic requirements of `proof` w3c/vc-data-integrity#166, by @TallTed.
-
Adding domain and defined_by to revoked w3c/vc-data-integrity#163, by @iherman.
-
Add `cryptosuiteString` subtype for the `cryptosuite` property. w3c/vc-data-integrity#162, by @msporny.
-
Add conformance classes to specification. w3c/vc-data-integrity#160, by @msporny.
-
Allow errors to be conveyed based on execution environment. w3c/vc-data-integrity#158, by @msporny.
-
Update domain to support arrays of domain values. w3c/vc-data-integrity#156, by @msporny.
-
Add text on difference between proof and VC validity periods. w3c/vc-data-integrity#155, by @msporny.
-
Add revoked definition and anchor for vocabulary. w3c/vc-data-integrity#154, by @msporny.
-
Add anchor and definition for proof property. w3c/vc-data-integrity#153, by @msporny.
-
Define anchors for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#152, by @msporny.
-
Add a JsonWebKey context file. w3c/vc-data-integrity#150, by @dmitrizagidulin.
-
Add a Multikey context file. w3c/vc-data-integrity#149, by @dmitrizagidulin.
-
Add vocab definitions for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#148, by @dmitrizagidulin.
-
Add Dmitri to codeowners and editors. w3c/vc-data-integrity#147, by @dmitrizagidulin.
-
Fix Mastodon spelling. w3c/vc-data-integrity#146, by @dmitrizagidulin.
-
-
34 pull requests merged.
-
Add cryptosuiteString to v2 context, preserving older v1 context. w3c/vc-data-integrity#181.
-
Align `datetimes` to `dateTimeStamp` values to ensure timezone. w3c/vc-data-integrity#178.
-
Add multibase datatype definition w3c/vc-data-integrity#176.
-
Add section on Resource Integrity and `digestMultibase`. w3c/vc-data-integrity#174.
-
Add section on "Other" Security and Privacy Considerations w3c/vc-data-integrity#173.
-
Add guidance on context and URL caching in general w3c/vc-data-integrity#172.
-
Updated the vocabulary and added a diagram w3c/vc-data-integrity#171.
-
Fix basic requirements of `proof` w3c/vc-data-integrity#166.
-
Adding domain and defined_by to revoked w3c/vc-data-integrity#163.
-
Add `cryptosuiteString` subtype for the `cryptosuite` property. w3c/vc-data-integrity#162.
-
Add text on difference between proof and VC validity periods. w3c/vc-data-integrity#155.
-
Extended proof chain algorithms w3c/vc-data-integrity#145.
-
Add conformance classes to specification. w3c/vc-data-integrity#160.
-
Allow errors to be conveyed based on execution environment. w3c/vc-data-integrity#158.
-
Update domain to support arrays of domain values. w3c/vc-data-integrity#156.
-
Add revoked definition and anchor for vocabulary. w3c/vc-data-integrity#154.
-
Add anchor and definition for proof property. w3c/vc-data-integrity#153.
-
Correcting previously mis-corrected sentence w3c/vc-data-integrity#143.
-
Add JSON Web Key to specification w3c/vc-data-integrity#135.
-
Define anchors for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#152.
-
Add a JsonWebKey context file. w3c/vc-data-integrity#150.
-
Add a Multikey context file. w3c/vc-data-integrity#149.
-
Add vocab definitions for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#148.
-
Add Dmitri to codeowners and editors. w3c/vc-data-integrity#147.
-
Clarify how proof types (and terms) are mapped to URLs. w3c/vc-data-integrity#133.
-
add missing comma w3c/vc-data-integrity#144.
-
Added final versions of some properties (with anchors) w3c/vc-data-integrity#142.
-
Added the error terms to the vocabulary w3c/vc-data-integrity#141.
-
Fix Mastodon spelling. w3c/vc-data-integrity#146.
-
Add errors with anchors to the specification. w3c/vc-data-integrity#140.
-
Add section on Securing Data Losslessly. w3c/vc-data-integrity#139.
-
Add section on context injection. w3c/vc-data-integrity#138.
-
Update range of Multikey and JsonWebKey w3c/vc-data-integrity#137.
-
Explain use of each verify proof option. w3c/vc-data-integrity#134.
-
-
38 pull requests received 261 new comments.
-
Add JSON Web Key to specification w3c/vc-data-integrity#135 (37 comments by @dlongley, @dmitrizagidulin, @iherman, @msporny, @OR13, @selfissued, @TallTed)
-
Add `cryptosuiteString` subtype for the `cryptosuite` property. w3c/vc-data-integrity#162 (20 comments by @iherman, @msporny, @TallTed)
-
Extended proof chain algorithms w3c/vc-data-integrity#145 (19 comments by @dlongley, @dmitrizagidulin, @msporny, @TallTed, @Wind4Greg)
-
Clarify how proof types (and terms) are mapped to URLs. w3c/vc-data-integrity#133 (19 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add text on difference between proof and VC validity periods. w3c/vc-data-integrity#155 (18 comments by @David-Chadwick, @dlongley, @msporny, @TallTed)
-
Add multibase datatype definition w3c/vc-data-integrity#176 (15 comments by @iherman, @msporny, @TallTed)
-
Add guidance on context and URL caching in general w3c/vc-data-integrity#172 (15 comments by @dlongley, @msporny, @TallTed)
-
Updated the vocabulary and added a diagram w3c/vc-data-integrity#171 (12 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Define anchors for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#152 (12 comments by @dlongley, @dmitrizagidulin, @msporny, @TallTed)
-
Add vocab definitions for secretKeyJwk and secretKeyMultibase w3c/vc-data-integrity#148 (9 comments by @dlongley, @dmitrizagidulin, @iherman, @msporny, @OR13)
-
Add section on context injection. w3c/vc-data-integrity#138 (9 comments by @dmitrizagidulin, @msporny, @TallTed)
-
Add section on Resource Integrity and `digestMultibase`. w3c/vc-data-integrity#174 (7 comments by @msporny, @TallTed)
-
Update controller document reference w3c/vc-data-integrity#99 (6 comments by @dmitrizagidulin, @iherman, @OR13)
-
Add section on Securing Data Losslessly. w3c/vc-data-integrity#139 (5 comments by @dlongley, @msporny, @TallTed)
-
Ensure that base URL is set to null when processing as RDF. w3c/vc-data-integrity#185 (4 comments by @dlongley, @iherman, @msporny)
-
Correcting previously mis-corrected sentence w3c/vc-data-integrity#143 (4 comments by @msporny, @TallTed)
-
Added the error terms to the vocabulary w3c/vc-data-integrity#141 (4 comments by @iherman, @msporny)
-
Add errors with anchors to the specification. w3c/vc-data-integrity#140 (4 comments by @JSAssassin, @msporny, @TallTed)
-
Align `datetimes` to `dateTimeStamp` values to ensure timezone. w3c/vc-data-integrity#178 (3 comments by @brianorwhatever, @msporny)
-
Add `revoked` and `expires` properties to JsonWebKey context. w3c/vc-data-integrity#184 (3 comments by @msporny, @OR13, @TallTed)
-
Add section on "Other" Security and Privacy Considerations w3c/vc-data-integrity#173 (3 comments by @msporny, @TallTed)
-
Add conformance classes to specification. w3c/vc-data-integrity#160 (3 comments by @msporny, @TallTed)
-
Allow errors to be conveyed based on execution environment. w3c/vc-data-integrity#158 (3 comments by @msporny, @TallTed)
-
Update domain to support arrays of domain values. w3c/vc-data-integrity#156 (3 comments by @msporny, @TallTed)
-
Add anchor and definition for proof property. w3c/vc-data-integrity#153 (3 comments by @iherman, @msporny, @TallTed)
-
Add revoked definition and anchor for vocabulary. w3c/vc-data-integrity#154 (2 comments by @msporny, @TallTed)
-
Add cryptosuiteString to v2 context, preserving older v1 context. w3c/vc-data-integrity#181 (1 comment by @msporny)
-
Added final versions of some properties (with anchors) w3c/vc-data-integrity#142 (1 comment by @msporny)
-
w3c/vc-bitstring-status-list
-
1 issue opened.
-
auto-publishing using echidna? w3c/vc-bitstring-status-list#82, by @brentzundel.
-
-
1 pull request opened.
-
Example both with revocation and suspension w3c/vc-bitstring-status-list#83, by @nissimsan.
-
-
1 pull request merged.
-
chore: update title and urls to contexts w3c/vc-bitstring-status-list#69.
-
-
1 pull request reopened.
-
chore: update title and urls to contexts w3c/vc-bitstring-status-list#69, by @msporny.
-
-
1 pull request received 3 new comments.
-
chore: update title and urls to contexts w3c/vc-bitstring-status-list#69 (3 comments by @mprorock, @msporny)
-
w3c/vc-jose-cose
-
3 issues opened.
-
Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` w3c/vc-jose-cose#141, by @OR13.
-
signature profiles w3c/vc-jose-cose#136, by @alenhorvat.
-
Can registered JWT claims be used only in the JOSE header?? w3c/vc-jose-cose#135, by @Sakurann.
-
-
1 issue closed.
-
Change spec name? w3c/vc-jose-cose#49.
-
-
13 issues received 42 new comments.
-
Clarify relationship between validity times w3c/vc-jose-cose#133 (7 comments by @David-Chadwick, @OR13, @TallTed)
-
Can registered JWT claims be used only in the JOSE header?? w3c/vc-jose-cose#135 (5 comments by @alenhorvat, @Sakurann, @TallTed)
-
Withdraw `application/vc+ld+json+jwt` and `application/vp+ld+json+jwt` w3c/vc-jose-cose#141 (3 comments by @brentzundel, @dwaite, @mprorock)
-
Better references to OIDC key discovery w3c/vc-jose-cose#127 (3 comments by @OR13, @Sakurann, @selfissued)
-
Define Controller Documents in the Core Data Model w3c/vc-jose-cose#140 (2 comments by @selfissued, @thereisnogabe)
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117 (1 comment by @vdods)
-
6 pull requests opened.
-
Add support for DIDs w3c/vc-jose-cose#144, by @OR13.
-
Changes to normative statements w3c/vc-jose-cose#143, by @OR13.
-
Fix example plugin w3c/vc-jose-cose#142, by @OR13.
-
Update examples w3c/vc-jose-cose#139, by @OR13.
-
Editorial clean up w3c/vc-jose-cose#138, by @OR13.
-
Add section on wallets / clients w3c/vc-jose-cose#137, by @OR13.
-
-
6 pull requests merged.
-
Fix example plugin w3c/vc-jose-cose#142.
-
Update examples w3c/vc-jose-cose#139.
-
Add section on wallets / clients w3c/vc-jose-cose#137.
-
Editorial clean up w3c/vc-jose-cose#138.
-
Address Ambiguity Regarding Multiple Structured Suffixes w3c/vc-jose-cose#123.
-
remove securing json w3c/vc-jose-cose#88.
-
-
8 pull requests received 107 new comments.
-
Address Ambiguity Regarding Multiple Structured Suffixes w3c/vc-jose-cose#123 (20 comments by @alenhorvat, @andresuribe87, @OR13, @Sakurann, @TallTed)
-
Changes to normative statements w3c/vc-jose-cose#143 (14 comments by @andresuribe87, @OR13, @Sakurann)
w3c/vc-json-schema
-
6 issues opened.
-
Formalize the jsonSchema property in the VCDM vocabulary? w3c/vc-json-schema#206, by @iherman.
-
Encourage usage of OHTTP during schema resolution w3c/vc-json-schema#203, by @andresuribe87.
-
Add guidance for wallets when using JsonSchemaCredential and selected disclosure w3c/vc-json-schema#202, by @andresuribe87.
-
Add guidance on inclusion of unique tracking identifiers w3c/vc-json-schema#201, by @andresuribe87.
-
Clarify the usage of the `id` property in `credentialSubject` when using `JsonSchemaCredential` w3c/vc-json-schema#197, by @thereisnogabe.
-
JSON schema's `type` and VC.context.JsonSchema.type w3c/vc-json-schema#194, by @andresuribe87.
-
-
15 issues closed.
-
Add guidance for using JSON Schemas in ZKP/Selectively Disclosable Credentials w3c/vc-json-schema#137.
-
Encourage usage of OHTTP during schema resolution w3c/vc-json-schema#203.
-
Language on nesting of credential schemas when using JsonSchemaCredential w3c/vc-json-schema#159.
-
Support YAML schema representations w3c/vc-json-schema#142.
-
Clarify the usage of the `id` property in `credentialSubject` when using `JsonSchemaCredential` w3c/vc-json-schema#197.
-
JSON schema's `type` and VC.context.JsonSchema.type w3c/vc-json-schema#194.
-
Add note about media types w3c/vc-json-schema#157.
-
Add warning for improperly formed schemes using multiple schemas w3c/vc-json-schema#136.
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122.
-
Add language for handling implementation mismatches w3c/vc-json-schema#181.
-
How does using JSON Schemas enable interoperability? w3c/vc-json-schema#106.
-
Consider removing versioning from the name w3c/vc-json-schema#179.
-
Add text to clarify when to use JsonSchema2023 over CredentialSchema2023 w3c/vc-json-schema#173.
-
Section 3.1.1 encourages dereferencable IRIs w3c/vc-json-schema#176.
-
Update term definitions to match the VCDM's vocab w3c/vc-json-schema#182.
-
-
11 issues received 24 new comments.
-
Clarify the usage of the `id` property in `credentialSubject` when using `JsonSchemaCredential` w3c/vc-json-schema#197 (8 comments by @dlongley, @TallTed, @thereisnogabe)
-
Formalize the jsonSchema property in the VCDM vocabulary? w3c/vc-json-schema#206 (3 comments by @andresuribe87, @iherman, @thereisnogabe)
-
Add guidance on inclusion of unique tracking identifiers w3c/vc-json-schema#201 (2 comments by @andresuribe87, @thereisnogabe)
-
JSON schema's `type` and VC.context.JsonSchema.type w3c/vc-json-schema#194 (2 comments by @thereisnogabe)
-
Being able to normatively reference JSON Schema w3c/vc-json-schema#133 (2 comments by @iherman, @Relequestual)
-
Add guidance for using JSON Schemas in ZKP/Selectively Disclosable Credentials w3c/vc-json-schema#137 (1 comment by @thereisnogabe)
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122 (1 comment by @andresuribe87)
-
How does using JSON Schemas enable interoperability? w3c/vc-json-schema#106 (1 comment by @thereisnogabe)
-
-
15 pull requests opened.
-
Discourage Unique tracking IDs w3c/vc-json-schema#209, by @andresuribe87.
-
Change hard to test must to recommended w3c/vc-json-schema#208, by @thereisnogabe.
-
Encourage OHTTP to prevent linking schema requests w3c/vc-json-schema#207, by @andresuribe87.
-
Updated the respec plugin version w3c/vc-json-schema#205, by @andresuribe87.
-
Clarified the value of `credentialSchema` when type is JsonSchemaCredential w3c/vc-json-schema#204, by @andresuribe87.
-
Add OpenAPI/YAML Representation w3c/vc-json-schema#200, by @thereisnogabe.
-
Guidance on using JsonSchemaCredential w3c/vc-json-schema#199, by @thereisnogabe.
-
Media types for plain json schema, JWT, and SD-JWT w3c/vc-json-schema#198, by @thereisnogabe.
-
Change plugin to one that supports vc-jose-cose with VCDM 2.0 w3c/vc-json-schema#196, by @andresuribe87.
-
Added validation examples. w3c/vc-json-schema#195, by @andresuribe87.
-
Added warning to avoid composition problems. w3c/vc-json-schema#193, by @andresuribe87.
-
Remove year as a version w3c/vc-json-schema#192, by @thereisnogabe.
-
update section on storage, content integrity protection w3c/vc-json-schema#191, by @thereisnogabe.
-
Add guidance on when to use each type w3c/vc-json-schema#190, by @thereisnogabe.
-
Add language to address implementation mismatches w3c/vc-json-schema#189, by @thereisnogabe.
-
-
16 pull requests merged.
-
Change hard to test must to recommended w3c/vc-json-schema#208.
-
Encourage OHTTP to prevent linking schema requests w3c/vc-json-schema#207.
-
Updated the respec plugin version w3c/vc-json-schema#205.
-
Clarified the value of `credentialSchema` when type is JsonSchemaCredential w3c/vc-json-schema#204.
-
Add OpenAPI/YAML Representation w3c/vc-json-schema#200.
-
Guidance on using JsonSchemaCredential w3c/vc-json-schema#199.
-
Media types for plain json schema, JWT, and SD-JWT w3c/vc-json-schema#198.
-
Change plugin to one that supports vc-jose-cose with VCDM 2.0 w3c/vc-json-schema#196.
-
Added warning to avoid composition problems. w3c/vc-json-schema#193.
-
Added validation examples. w3c/vc-json-schema#195.
-
Add language to address implementation mismatches w3c/vc-json-schema#189.
-
update section on storage, content integrity protection w3c/vc-json-schema#191.
-
Add guidance on when to use each type w3c/vc-json-schema#190.
-
Remove year as a version w3c/vc-json-schema#192.
-
Rename IRI to URL and point to RFC w3c/vc-json-schema#188.
-
Update term definitions according to the core vocab w3c/vc-json-schema#185.
-
-
14 pull requests received 131 new comments.
-
Add OpenAPI/YAML Representation w3c/vc-json-schema#200 (20 comments by @andresuribe87, @OR13, @TallTed, @thereisnogabe)
-
Change plugin to one that supports vc-jose-cose with VCDM 2.0 w3c/vc-json-schema#196 (19 comments by @andresuribe87, @OR13, @TallTed, @thereisnogabe)
-
Clarified the value of `credentialSchema` when type is JsonSchemaCredential w3c/vc-json-schema#204 (16 comments by @andresuribe87, @iherman, @msporny, @OR13, @thereisnogabe)
-
Media types for plain json schema, JWT, and SD-JWT w3c/vc-json-schema#198 (14 comments by @andresuribe87, @OR13, @thereisnogabe)
-
Add language to address implementation mismatches w3c/vc-json-schema#189 (14 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Guidance on using JsonSchemaCredential w3c/vc-json-schema#199 (12 comments by @andresuribe87, @dlongley, @OR13, @TallTed, @thereisnogabe)
-
update section on storage, content integrity protection w3c/vc-json-schema#191 (10 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Encourage OHTTP to prevent linking schema requests w3c/vc-json-schema#207 (4 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Added warning to avoid composition problems. w3c/vc-json-schema#193 (4 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
w3c/vc-json-schema-test-suite
-
4 pull requests opened.
-
Update TBD impl w3c/vc-json-schema-test-suite#4, by @thereisnogabe.
-
Update README; add GitHub Action w3c/vc-json-schema-test-suite#3, by @thereisnogabe.
-
Test Vectors - TBD impl fully working w3c/vc-json-schema-test-suite#2, by @thereisnogabe.
-
structure for test runners w3c/vc-json-schema-test-suite#1, by @thereisnogabe.
-
-
4 pull requests merged.
-
Update TBD impl w3c/vc-json-schema-test-suite#4.
-
Update README; add GitHub Action w3c/vc-json-schema-test-suite#3.
-
Test Vectors - TBD impl fully working w3c/vc-json-schema-test-suite#2.
-
structure for test runners w3c/vc-json-schema-test-suite#1.
-
w3c/vc-jose-cose-test-suite
-
9 issues opened.
-
Representing extension validation in tests w3c/vc-jose-cose-test-suite#9, by @OR13.
-
Update secured-vc-with-schema-credential w3c/vc-jose-cose-test-suite#7, by @andresuribe87.
-
Expiration and Activation w3c/vc-jose-cose-test-suite#6, by @OR13.
-
Test cases for controller documents w3c/vc-jose-cose-test-suite#5, by @OR13.
-
Covering normative statements via testcases w3c/vc-jose-cose-test-suite#4, by @OR13.
-
Add support for SD-JWT w3c/vc-jose-cose-test-suite#3, by @OR13.
-
Add support for COSE w3c/vc-jose-cose-test-suite#2, by @OR13.
-
Commit the testcase generator code? w3c/vc-jose-cose-test-suite#1, by @OR13.
-
How to test `credentialStatus` and `credentialSchema`? w3c/vc-jose-cose-test-suite#11, by @OR13.
-
-
3 issues received 3 new comments.
-
Representing extension validation in tests w3c/vc-jose-cose-test-suite#9 (1 comment by @thereisnogabe)
-
How to test `credentialStatus` and `credentialSchema`? w3c/vc-jose-cose-test-suite#11 (1 comment by @OR13)
-
w3c/vc-di-ecdsa
-
6 issues opened.
-
Add definition for secretKeyMultibase serialization w3c/vc-di-ecdsa#35, by @msporny.
-
Ensure to pass SHA-384 param and fetch verification method early to get key size w3c/vc-di-ecdsa#32, by @dlongley.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-ecdsa#29, by @msporny.
-
Add normative guidance that Deterministic signatures SHOULD be used w3c/vc-di-ecdsa#28, by @msporny.
-
Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? w3c/vc-di-ecdsa#26, by @bnewbold.
-
Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition w3c/vc-di-ecdsa#22, by @bnewbold.
-
-
5 issues received 17 new comments.
-
Confirming `EcdsaSecp256r1VerificationKey2019` -> `Multikey` transition w3c/vc-di-ecdsa#22 (12 comments by @bnewbold, @dmitrizagidulin, @msporny, @OR13, @peacekeeper)
-
Clarifying `publicKeyMultibase` encoding: `did:key` style with multicodec code, or not? w3c/vc-di-ecdsa#26 (2 comments by @bnewbold, @msporny)
-
Ensure to pass SHA-384 param and fetch verification method early to get key size w3c/vc-di-ecdsa#32 (1 comment by @msporny)
-
Add normative guidance that Deterministic signatures SHOULD be used w3c/vc-di-ecdsa#28 (1 comment by @msporny)
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-ecdsa#29 (1 comment by @msporny)
-
-
9 pull requests opened.
-
Add secretKeyMultibase representation. w3c/vc-di-ecdsa#37, by @dmitrizagidulin.
-
Add which cryptographic hash function to use for RDF-CANON. w3c/vc-di-ecdsa#36, by @msporny.
-
deterministic ECDSA SHOULD be used w3c/vc-di-ecdsa#34, by @Wind4Greg.
-
Add pointers back to Data Integrity Privacy and Security Considerations sections w3c/vc-di-ecdsa#33, by @msporny.
-
Simplify language that warns of invalid examples w3c/vc-di-ecdsa#31, by @seabass-labrax.
-
Update selective disclosure functions and their use in ecdsa-sd sign, derive, verify. w3c/vc-di-ecdsa#27, by @dlongley.
-
Cryptosuite Naming: Update example 4 and test vectors w3c/vc-di-ecdsa#25, by @Wind4Greg.
-
Change poison graph mitigation into advisement w3c/vc-di-ecdsa#24, by @msporny.
-
Update crypto-suite names w3c/vc-di-ecdsa#23, by @Wind4Greg.
-
-
7 pull requests merged.
-
Add pointers back to Data Integrity Privacy and Security Considerations sections w3c/vc-di-ecdsa#33.
-
Cryptosuite Naming: Update example 4 and test vectors w3c/vc-di-ecdsa#25.
-
Change poison graph mitigation into advisement w3c/vc-di-ecdsa#24.
-
Update crypto-suite names w3c/vc-di-ecdsa#23.
-
Mitigate poison datasets in ECDSA when canonicalizing. w3c/vc-di-ecdsa#21.
-
Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification w3c/vc-di-ecdsa#20.
-
-
1 pull request closed.
-
Add helper functions for performing selective disclosure w3c/vc-di-ecdsa#19.
-
-
12 pull requests received 113 new comments.
-
Update selective disclosure functions and their use in ecdsa-sd sign, derive, verify. w3c/vc-di-ecdsa#27 (50 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
deterministic ECDSA SHOULD be used w3c/vc-di-ecdsa#34 (15 comments by @dlongley, @TallTed, @Wind4Greg)
-
Add which cryptographic hash function to use for RDF-CANON. w3c/vc-di-ecdsa#36 (11 comments by @iherman, @msporny, @TallTed, @Wind4Greg)
-
Add pointers back to Data Integrity Privacy and Security Considerations sections w3c/vc-di-ecdsa#33 (8 comments by @msporny, @TallTed)
-
Add secretKeyMultibase representation. w3c/vc-di-ecdsa#37 (6 comments by @dlongley, @TallTed, @Wind4Greg)
-
Simplify language that warns of invalid examples w3c/vc-di-ecdsa#31 (6 comments by @dlongley, @seabass-labrax, @TallTed)
-
Mitigate poison datasets in ECDSA when canonicalizing. w3c/vc-di-ecdsa#21 (6 comments by @msporny, @OR13)
-
Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification w3c/vc-di-ecdsa#20 (3 comments by @msporny, @yamdan)
-
w3c/vc-di-eddsa
-
2 issues opened.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-eddsa#57, by @msporny.
-
Add definition for secretKeyMultibase serialization w3c/vc-di-eddsa#56, by @dmitrizagidulin.
-
-
1 issue closed.
-
privateKeyMultibase w3c/vc-di-eddsa#4.
-
-
2 issues received 7 new comments.
-
Point Privacy and Security Considerations section back to Data Integrity w3c/vc-di-eddsa#57 (1 comment by @msporny)
-
7 pull requests opened.
-
Add secretKeyMultibase definition. w3c/vc-di-eddsa#61, by @dmitrizagidulin.
-
Add advisements to read Data Integrity considerations sections. w3c/vc-di-eddsa#60, by @msporny.
-
Simplify language that warns of invalid examples w3c/vc-di-eddsa#59, by @seabass-labrax.
-
Cryptosuite Naming: Update example 3 and data integrity test vectors w3c/vc-di-eddsa#55, by @Wind4Greg.
-
Remove mis-implementation Issue w3c/vc-di-eddsa#54, by @Wind4Greg.
-
Update Cryptosuite Names. w3c/vc-di-eddsa#53, by @Wind4Greg.
-
Revise cryptosuite names w3c/vc-di-eddsa#52, by @Wind4Greg.
-
-
5 pull requests merged.
-
Simplify language that warns of invalid examples w3c/vc-di-eddsa#59.
-
Cryptosuite Naming: Update example 3 and data integrity test vectors w3c/vc-di-eddsa#55.
-
Remove mis-implementation Issue w3c/vc-di-eddsa#54.
-
Update Cryptosuite Names. w3c/vc-di-eddsa#53.
-
Add EdDSA mitigation for dataset poisoning. w3c/vc-di-eddsa#51.
-
-
1 pull request closed.
-
Revise cryptosuite names w3c/vc-di-eddsa#52.
-
-
6 pull requests received 14 new comments.
-
Add EdDSA mitigation for dataset poisoning. w3c/vc-di-eddsa#51 (7 comments by @msporny, @OR13, @TallTed)
-
Cryptosuite Naming: Update example 3 and data integrity test vectors w3c/vc-di-eddsa#55 (1 comment by @msporny)
-
w3c/vc-test-suite
-
1 issue received 27 new comments.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (27 comments by @dmitrizagidulin, @iherman, @longpd, @OR13, @TallTed)
-
w3c/vc-use-cases
-
1 pull request opened.
-
Miscellaneous cleanup w3c/vc-use-cases#148, by @ghost.
-
w3c/vc-test-suite-implementations
-
2 pull requests opened.
-
Updates Trinsic's issuers to match the config in the `implementations` repo in `w3c-ccg` to support `Ed25519Signature2020`. w3c/vc-test-suite-implementations#2, by @JSAssassin.
-
Add Trinsic implementation entry w3c/vc-test-suite-implementations#1, by @tmarkovski.
-
-
2 pull requests merged.
-
Updates Trinsic's issuers to match the config in the `implementations` repo in `w3c-ccg` to support `Ed25519Signature2020`. w3c/vc-test-suite-implementations#2.
-
Add Trinsic implementation entry w3c/vc-test-suite-implementations#1.
-
-
1 pull request received 1 new comment.
-
Updates Trinsic's issuers to match the config in the `implementations` repo in `w3c-ccg` to support `Ed25519Signature2020`. w3c/vc-test-suite-implementations#2 (1 comment by @w3cbot)
-
w3c/vc-di-eddsa-test-suite
-
1 pull request opened.
-
Remove error names from test descriptions. w3c/vc-di-eddsa-test-suite#19, by @JSAssassin.
-
-
1 pull request merged.
-
Remove error names from test descriptions. w3c/vc-di-eddsa-test-suite#19.
-
w3c/vc-di-ecdsa-test-suite
-
1 pull request opened.
-
Removes error name from test description. w3c/vc-di-ecdsa-test-suite#12, by @JSAssassin.
-
-
1 pull request merged.
-
Removes error name from test description. w3c/vc-di-ecdsa-test-suite#12.
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
Remove error names from test descriptions. w3c/vc-di-ed25519signature2020-test-suite#40, by @JSAssassin.
-
-
1 pull request merged.
-
Remove error names from test descriptions. w3c/vc-di-ed25519signature2020-test-suite#40.
-
w3c/vc-extensions
-
1 issue opened.
-
Organize at least W3C Recommendations in their own section w3c/vc-extensions#27, by @jandrieu.
-
-
1 issue received 3 new comments.
-
Organize at least W3C Recommendations in their own section w3c/vc-extensions#27 (3 comments by @iherman, @jandrieu, @OR13)
-
-
1 pull request opened.
-
Add 1EdTech Open Badges v3 Evidence extension. w3c/vc-extensions#28, by @msporny.
-
-
2 pull requests merged.
-
Add 1EdTech Open Badges v3 Evidence extension. w3c/vc-extensions#28.
-
Add "Media Type Extensions" category. w3c/vc-extensions#14.
-
-
2 pull requests received 13 new comments.
-
Add "Media Type Extensions" category. w3c/vc-extensions#14 (12 comments by @iherman, @msporny, @OR13, @Sakurann, @selfissued, @TallTed)
-
w3c/vc-data-model-2.0-test-suite
-
2 issues received 3 new comments.
-
test approach for resource integrity w3c/vc-data-model-2.0-test-suite#35 (2 comments by @iherman, @OR13)
-
@type is not an URI test does not fail when using JSON-LD processor w3c/vc-data-model-2.0-test-suite#27 (1 comment by @aljones15)
-
-
4 pull requests opened.
-
Remove notes w3c/vc-data-model-2.0-test-suite#34, by @aljones15.
-
Use ?. check on result.errors to prevent test from throwing w3c/vc-data-model-2.0-test-suite#33, by @aljones15.
-
Use an invalid url with https protocol for invalid url tests. w3c/vc-data-model-2.0-test-suite#32, by @aljones15.
-
Update the respec info with one new Author and valid github and spec … w3c/vc-data-model-2.0-test-suite#31, by @aljones15.
-
-
6 pull requests merged.
-
Update the respec info with one new Author and valid github and spec … w3c/vc-data-model-2.0-test-suite#31.
-
Fix vps w3c/vc-data-model-2.0-test-suite#26.
-
Remove notes w3c/vc-data-model-2.0-test-suite#34.
-
Use an invalid url with https protocol for invalid url tests. w3c/vc-data-model-2.0-test-suite#32.
-
Use ?. check on result.errors to prevent test from throwing w3c/vc-data-model-2.0-test-suite#33.
-
Skip refreshService tests (these should be in a separate suite). w3c/vc-data-model-2.0-test-suite#30.
-
-
3 pull requests received 22 new comments.
-
Update the respec info with one new Author and valid github and spec … w3c/vc-data-model-2.0-test-suite#31 (6 comments by @aljones15, @msporny)
-
Use an invalid url with https protocol for invalid url tests. w3c/vc-data-model-2.0-test-suite#32 (3 comments by @aljones15, @filip26, @msporny)
w3c/vc-di-bbs
-
1 issue opened.
-
Hosted JSON-LD context should expose itself as `ld+json` instead of `json` w3c/vc-di-bbs#90, by @j-steinbach.
-
-
1 issue received 5 new comments.
-
Hosted JSON-LD context should expose itself as `ld+json` instead of `json` w3c/vc-di-bbs#90 (5 comments by @dlongley, @j-steinbach, @tmarkovski)
-
w3c/vc-confidence-method
-
1 pull request opened.
-
change repo link from @spruceid to @w3c-ccg w3c/vc-confidence-method#8, by @TallTed.
-
TR publications
-
36 documents published.
-
Verifiable Credential Data Integrity 1.0 published 5 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials JSON Schema Specification 2023 published 6 times as a Working Draft. History of Verifiable Credentials JSON Schema Specification 2023
-
Verifiable Credentials Data Model v2.0 published 14 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Data Integrity ECDSA Cryptosuites v1.0 published 4 times as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.0
-
Securing Verifiable Credentials using JOSE and COSE published 3 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
Data Integrity EdDSA Cryptosuites v1.0 published 4 times as a Working Draft. History of Data Integrity EdDSA Cryptosuites v1.0
-
Past meetings
-
7 meetings.
Participants
-
3 participants joined.
-
Sebastian Crane (W3C Invited Experts) joined.
-
Hyojin Song (LG Electronics) joined.
-
Nicholas Lansley (GS1) joined.
-
-
1 participant left.
-
Erhard Brand (Entersekt) left.
-
-
1 organization joined.
-
LG Electronics joined.
-
GitHub
w3c/vc-data-model
-
16 issues opened.
-
Add link to Linked Data Best Practices w3c/vc-data-model#1217, by @msporny.
-
Missing term in the vcdm spec w3c/vc-data-model#1216, by @iherman.
-
Spec does not contain "name" and "description" terms in the context w3c/vc-data-model#1214, by @aljones15.
-
Document issuer defined vocabulary and use of @vocab w3c/vc-data-model#1210, by @msporny.
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206, by @OR13.
-
proof property is not compacted with v2 context w3c/vc-data-model#1204, by @filip26.
-
Document how VCs are processed as JSON today w3c/vc-data-model#1201, by @msporny.
-
Define `verification material` find replace `public keys` w3c/vc-data-model#1197, by @OR13.
-
Move Data Schemas to Basic Concepts section w3c/vc-data-model#1196, by @thereisnogabe.
-
`validFrom` and `validUntil` fields need better specification of `dateTime` w3c/vc-data-model#1193, by @aphillips.
-
Explain that natural language examples are illustrative w3c/vc-data-model#1192, by @aphillips.
-
Example could include @language w3c/vc-data-model#1191, by @aphillips.
-
Portions of data model spec should be considered for removal w3c/vc-data-model#1188, by @mprorock.
-
Derived Credential Presentations w3c/vc-data-model#1187, by @abhishekmaha23.
-
Conformance requirements for normative context w3c/vc-data-model#1185, by @OR13.
-
Add OPTIONAL to conformace section w3c/vc-data-model#1184, by @awoie.
-
-
29 issues closed.
-
Add references in vocabulary that link back to the VCDM document w3c/vc-data-model#1061.
-
(Editorial) systematically adding an anchor to each property w3c/vc-data-model#1080.
-
Portions of data model spec should be considered for removal w3c/vc-data-model#1188.
-
Accessibility Self-Review for VCDM 2.0 w3c/vc-data-model#1156.
-
Move Data Schemas to Basic Concepts section w3c/vc-data-model#1196.
-
Change `credentialSubject` to `subject` w3c/vc-data-model#1128.
-
Verification of multiple credential schemas w3c/vc-data-model#950.
-
Vocabulary normative, context isn't? w3c/vc-data-model#1103.
-
VC Vocabulary v2.0 does not have any term definitions w3c/vc-data-model#1117.
-
proof property is not compacted with v2 context w3c/vc-data-model#1204.
-
Guidance on `application/ld+json` w3c/vc-data-model#1040.
-
Provide guidance when media type is incorrect w3c/vc-data-model#1015.
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846.
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881.
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090.
-
Derived Credential Presentations w3c/vc-data-model#1187.
-
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? w3c/vc-data-model#1134.
-
Question about verifiable presentations w3c/vc-data-model#996.
-
(tracking issue) apparent copy-paste error in #1144 needs fixing w3c/vc-data-model#1161.
-
Make `validFrom` optional w3c/vc-data-model#1133.
-
Add `render` property to a core VC data model w3c/vc-data-model#928.
-
Handle predicate for confidenceMethod in JSON-LD context w3c/vc-data-model#1116.
-
RsaSignature2018 v1 spec definitions w3c/vc-data-model#1151.
-
Add OPTIONAL to conformace section w3c/vc-data-model#1184.
-
Check status privacy w3c/vc-data-model#1148.
-
Remove reference to OdrlPolicy2017 w3c/vc-data-model#1123.
-
Remove reference to DocumentVerification2018 w3c/vc-data-model#1124.
-
Remove reference toCredentialManagerPresentation w3c/vc-data-model#1125.
-
-
57 issues received 137 new comments.
-
Conformance requirements for normative context w3c/vc-data-model#1185 (11 comments by @dlongley, @iherman, @OR13, @TallTed)
-
Entities and Parties w3c/vc-data-model#1173 (7 comments by @David-Chadwick, @iherman, @jandrieu, @RieksJ, @TallTed)
-
Portions of data model spec should be considered for removal w3c/vc-data-model#1188 (5 comments by @brentzundel, @iherman, @OR13, @TallTed)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (5 comments by @brentzundel, @iherman, @OR13)
-
Move Data Schemas to Basic Concepts section w3c/vc-data-model#1196 (4 comments by @brentzundel, @iherman, @msporny)
-
`validFrom` and `validUntil` fields need better specification of `dateTime` w3c/vc-data-model#1193 (4 comments by @David-Chadwick, @filip26, @iherman, @msporny)
-
Ensure the base context doesn't constrain lower-maturity specifications w3c/vc-data-model#1175 (4 comments by @iherman, @msporny, @OR13)
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009 (4 comments by @brentzundel, @David-Chadwick, @msporny, @OR13)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (4 comments by @awoie, @David-Chadwick, @filip26, @TallTed)
-
VC Vocabulary v2.0 does not have any term definitions w3c/vc-data-model#1117 (4 comments by @brentzundel, @iherman, @msporny)
-
Define `verification material` find replace `public keys` w3c/vc-data-model#1197 (4 comments by @msporny, @OR13, @TallTed)
-
Derived Credential Presentations w3c/vc-data-model#1187 (4 comments by @abhishekmaha23, @brentzundel)
-
Add references in vocabulary that link back to the VCDM document w3c/vc-data-model#1061 (3 comments by @brentzundel, @iherman)
-
(Editorial) systematically adding an anchor to each property w3c/vc-data-model#1080 (3 comments by @brentzundel, @iherman)
-
How should we refer to the Securing specifications? w3c/vc-data-model#1105 (3 comments by @iherman, @msporny, @OR13)
-
Change `credentialSubject` to `subject` w3c/vc-data-model#1128 (3 comments by @brentzundel, @iherman, @paulfdietrich)
-
proof property is not compacted with v2 context w3c/vc-data-model#1204 (3 comments by @dlongley, @filip26)
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881 (3 comments by @brentzundel, @iherman, @OR13)
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090 (3 comments by @brentzundel, @iherman, @OR13)
-
Define what a credential validity does mean w3c/vc-data-model#1176 (2 comments by @filip26, @iherman)
-
Document issuer defined vocabulary and use of @vocab w3c/vc-data-model#1210 (2 comments by @dlongley, @msporny)
-
Address "Credential" vs "VerifiableCredential" w3c/vc-data-model#1126 (2 comments by @iherman, @msporny)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (2 comments by @msporny, @thereisnogabe)
-
Add `render` property to a core VC data model w3c/vc-data-model#928 (2 comments by @iherman, @Sakurann)
-
Spec does not contain "name" and "description" terms in the context w3c/vc-data-model#1214 (1 comment by @iherman)
-
Allowing expanded `type` values in conforming documents w3c/vc-data-model#1206 (1 comment by @iherman)
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089 (1 comment by @iherman)
-
Explain that natural language examples are illustrative w3c/vc-data-model#1192 (1 comment by @iherman)
-
Missing security considerations on MITM, cloning etc. w3c/vc-data-model#1138 (1 comment by @iherman)
-
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? w3c/vc-data-model#1134 (1 comment by @thereisnogabe)
-
Handle predicate for confidenceMethod in JSON-LD context w3c/vc-data-model#1116 (1 comment by @brentzundel)
-
Add language that there is generally no relationship between a VP and their VCs other than integrity protection w3c/vc-data-model#1165 (1 comment by @awoie)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (1 comment by @awoie)
-
-
19 pull requests opened.
-
Update term definition for vc json schemas as creds w3c/vc-data-model#1215, by @thereisnogabe.
-
Minor correction to viewBox so that all text becomes visible. w3c/vc-data-model#1213, by @fabienpe.
-
Refer to VC-SPECS-DIR for proof types. w3c/vc-data-model#1212, by @msporny.
-
Clarify the difference between a "credential" and a "verifiable credential" w3c/vc-data-model#1211, by @msporny.
-
Vocabulary improvement Phase 1 w3c/vc-data-model#1209, by @iherman.
-
minor language fix w3c/vc-data-model#1208, by @TallTed.
-
Move data schemas to basic concepts section w3c/vc-data-model#1207, by @thereisnogabe.
-
Add section on Ecosystem Compatibility. w3c/vc-data-model#1203, by @msporny.
-
Add section on JSON Processing. w3c/vc-data-model#1202, by @msporny.
-
Better not set §B as non-normative (minor editorial) w3c/vc-data-model#1200, by @iherman.
-
Add validation section regarding holder w3c/vc-data-model#1199, by @OR13.
-
Add language around multiple schemas; update example w3c/vc-data-model#1198, by @thereisnogabe.
-
Remove outdated v1.0 JWT claim registrations. w3c/vc-data-model#1195, by @msporny.
-
Add vocab terms for status list 2021 w3c/vc-data-model#1194, by @thereisnogabe.
-
Adjust media types to reflect updates w3c/vc-data-model#1190, by @OR13.
-
Add section on media type precision. w3c/vc-data-model#1189, by @msporny.
-
Add interoperable way for holder-asserted claims in a VP w3c/vc-data-model#1186, by @brentzundel.
-
Add dateTimeStamp regex and explanation of representing time. w3c/vc-data-model#1183, by @msporny.
-
removing remaining references to JSON w3c/vc-data-model#1182, by @Sakurann.
-
-
22 pull requests merged.
-
Minor correction to viewBox so that all text becomes visible. w3c/vc-data-model#1213.
-
Vocabulary improvement Phase 1 w3c/vc-data-model#1209.
-
minor language fix w3c/vc-data-model#1208.
-
Move data schemas to basic concepts section w3c/vc-data-model#1207.
-
Add interoperable way for holder-asserted claims in a VP w3c/vc-data-model#1186.
-
Add graph node identifiers for registered claims w3c/vc-data-model#1149.
-
Remove outdated v1.0 JWT claim registrations. w3c/vc-data-model#1195.
-
Adjust media types to reflect updates w3c/vc-data-model#1190.
-
Add language around multiple schemas; update example w3c/vc-data-model#1198.
-
Add vocab terms for status list 2021 w3c/vc-data-model#1194.
-
Add section on media type precision. w3c/vc-data-model#1189.
-
Add dateTimeStamp regex and explanation of representing time. w3c/vc-data-model#1183.
-
removing remaining references to JSON w3c/vc-data-model#1182.
-
Rationalize and clarify IANA Considerations w3c/vc-data-model#1163.
-
add vc-json-schema to vocab and context w3c/vc-data-model#1178.
-
Presentations w3c/vc-data-model#1181.
-
fix typo in vp+ld+json IANA considerations w3c/vc-data-model#1180.
-
remove 'credential' and 'presentation' from 'type' examples table w3c/vc-data-model#1179.
-
made validFrom optional, fixes #1133 w3c/vc-data-model#1168.
-
Updated privacy language in diagram w3c/vc-data-model#1174.
-
add issue numbers to at risk extension points w3c/vc-data-model#1171.
-
Update example types w3c/vc-data-model#1170.
-
-
1 pull request closed.
-
Media types other than vc+ld+json w3c/vc-data-model#1100.
-
-
35 pull requests received 813 new comments.
-
Add section on Ecosystem Compatibility. w3c/vc-data-model#1203 (166 comments by @alenhorvat, @awoie, @brentzundel, @David-Chadwick, @dlongley, @iherman, @jandrieu, @m00sey, @mprorock, @msporny, @mtaimela, @OR13, @pfeairheller, @Sakurann, @TallTed, @thereisnogabe)
-
Add interoperable way for holder-asserted claims in a VP w3c/vc-data-model#1186 (84 comments by @andresuribe87, @brentzundel, @David-Chadwick, @dlongley, @iherman, @jandrieu, @longpd, @msporny, @OR13, @Sakurann, @TallTed)
-
Add validation section regarding holder w3c/vc-data-model#1199 (78 comments by @awoie, @brentzundel, @dlongley, @iherman, @jandrieu, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Presentations w3c/vc-data-model#1181 (63 comments by @awoie, @brentzundel, @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Add "author" and "party" to terminology, rewrite "claim" terminology w3c/vc-data-model#1172 (60 comments by @brentzundel, @davidlehn, @dlongley, @iherman, @jandrieu, @msporny, @OR13, @RieksJ, @TallTed, @thereisnogabe, @wip-abramson)
-
Add section on JSON Processing. w3c/vc-data-model#1202 (53 comments by @awoie, @brentzundel, @dlongley, @iherman, @jandrieu, @mprorock, @msporny, @mtaimela, @OR13, @Sakurann, @TallTed, @thereisnogabe)
-
Add graph node identifiers for registered claims w3c/vc-data-model#1149 (51 comments by @alenhorvat, @andresuribe87, @brentzundel, @davidlehn, @gannan08, @iherman, @mprorock, @msporny, @OR13)
-
Add dateTimeStamp regex and explanation of representing time. w3c/vc-data-model#1183 (50 comments by @aphillips, @davidlehn, @dlongley, @iherman, @msporny, @OR13, @pchampin, @TallTed)
-
Add language around multiple schemas; update example w3c/vc-data-model#1198 (25 comments by @brentzundel, @dlongley, @msporny, @OR13, @thereisnogabe)
-
Clarify the difference between a "credential" and a "verifiable credential" w3c/vc-data-model#1211 (24 comments by @David-Chadwick, @dlongley, @msporny, @TallTed)
-
Add section on media type precision. w3c/vc-data-model#1189 (17 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add confidenceMethod to table of reserved terms and v2 `@context` w3c/vc-data-model#1142 (14 comments by @awoie, @brentzundel, @iherman, @msporny, @OR13)
-
add vc-json-schema to vocab and context w3c/vc-data-model#1178 (13 comments by @msporny, @thereisnogabe)
-
Move data schemas to basic concepts section w3c/vc-data-model#1207 (7 comments by @davidlehn, @iherman, @msporny, @thereisnogabe)
-
Minor correction to viewBox so that all text becomes visible. w3c/vc-data-model#1213 (6 comments by @fabienpe, @msporny, @TallTed, @w3cbot)
-
Remove outdated v1.0 JWT claim registrations. w3c/vc-data-model#1195 (6 comments by @iherman, @msporny, @OR13)
-
made validFrom optional, fixes #1133 w3c/vc-data-model#1168 (6 comments by @awoie, @msporny, @TallTed)
-
Better not set §B as non-normative (minor editorial) w3c/vc-data-model#1200 (5 comments by @iherman, @msporny, @OR13)
-
Refer to VC-SPECS-DIR for proof types. w3c/vc-data-model#1212 (4 comments by @msporny, @OR13, @seabass-labrax)
-
fix typo in vp+ld+json IANA considerations w3c/vc-data-model#1180 (4 comments by @brentzundel, @davidlehn, @msporny, @TallTed)
-
Add vocab terms for status list 2021 w3c/vc-data-model#1194 (3 comments by @TallTed, @thereisnogabe)
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101 (3 comments by @iherman, @OR13)
-
Update term definition for vc json schemas as creds w3c/vc-data-model#1215 (1 comment by @thereisnogabe)
-
Remove JSON section in lieu of `application/vc+ld+json`. w3c/vc-data-model#1088 (1 comment by @msporny)
-
remove 'credential' and 'presentation' from 'type' examples table w3c/vc-data-model#1179 (1 comment by @msporny)
-
w3c/vc-data-integrity
-
10 issues opened.
-
Add table for all error conditions w3c/vc-data-integrity#136, by @msporny.
-
Add diagrams and test vectors for `previousProof` w3c/vc-data-integrity#132, by @msporny.
-
Ensure that documents that drop data throw errors w3c/vc-data-integrity#131, by @msporny.
-
Add JsonWebKey definition in Data Integrity w3c/vc-data-integrity#130, by @msporny.
-
Missing term definitions in the spec w3c/vc-data-integrity#129, by @iherman.
-
Expand use of `previousProof` to allow an array, define in security vocabulary w3c/vc-data-integrity#120, by @msporny.
-
Add guidance on perma-caching contexts to align with VCDM w3c/vc-data-integrity#115, by @msporny.
-
Add optional prover-generated nonce value to increase privacy w3c/vc-data-integrity#114, by @awoie.
-
relating an agent to their key? w3c/vc-data-integrity#110, by @bblfish.
-
Add clarification for `verificationMethod` property being optional. w3c/vc-data-integrity#108, by @JSAssassin.
-
-
25 issues closed.
-
Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#97.
-
Apply guidance from RCH WG on processing poisoned graphs w3c/vc-data-integrity#82.
-
Add guidance on perma-caching contexts to align with VCDM w3c/vc-data-integrity#115.
-
Specify how relative URLs should be processed w3c/vc-data-integrity#77.
-
How to use cryptographic suites w3c/vc-data-integrity#84.
-
Add optional prover-generated nonce value to increase privacy w3c/vc-data-integrity#114.
-
Add clarification for `verificationMethod` property being optional. w3c/vc-data-integrity#108.
-
Add requirements on cryptosuite contexts such as `@protected` w3c/vc-data-integrity#48.
-
Determine how cryptographic suites are named and versioned w3c/vc-data-integrity#38.
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18.
-
Missing "created" invalidates signature? w3c/vc-data-integrity#23.
-
URLs in current editors draft all seem to be invalid w3c/vc-data-integrity#37.
-
Is the sec entry in vocab/security/vocabulary.jsonld and vocab/security/vocabulary.ttl wrong? w3c/vc-data-integrity#72.
-
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? w3c/vc-data-integrity#14.
-
nonce property w3c/vc-data-integrity#34.
-
either nonce or challenge is redundant w3c/vc-data-integrity#30.
-
What attributes are included in proof options? w3c/vc-data-integrity#27.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26.
-
serialization, canonicalized values and normalized datasets w3c/vc-data-integrity#11.
-
Authenticity checks w3c/vc-data-integrity#3.
-
Example that demonstrates input(s) and what gets fed to the signature algorithms? w3c/vc-data-integrity#19.
-
Which options are "input options"? w3c/vc-data-integrity#16.
-
Review on 2023-01-26 by Greg Bernstein w3c/vc-data-integrity#81.
-
Broken link to CAIP-10Account ID Specification w3c/vc-data-integrity#71.
-
Mentioning how to retrieve the public key w3c/vc-data-integrity#24.
-
-
45 issues received 131 new comments.
-
Expand use of `previousProof` to allow an array, define in security vocabulary w3c/vc-data-integrity#120 (12 comments by @dlongley, @iherman, @msporny, @TallTed, @Wind4Greg)
-
Specify how relative URLs should be processed w3c/vc-data-integrity#77 (8 comments by @msporny, @OR13)
-
Add optional prover-generated nonce value to increase privacy w3c/vc-data-integrity#114 (8 comments by @awoie, @dlongley, @msporny, @TallTed)
-
Determine how cryptographic suites are named and versioned w3c/vc-data-integrity#38 (8 comments by @HelgeKrueger, @msporny, @silverpill, @Wind4Greg)
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (7 comments by @lemoustachiste, @msporny)
-
URLs in current editors draft all seem to be invalid w3c/vc-data-integrity#37 (6 comments by @iherman, @msporny)
-
Domain and range of sec:publicKey w3c/vc-data-integrity#74 (5 comments by @bblfish, @csarven, @msporny)
-
Apply guidance from RCH WG on processing poisoned graphs w3c/vc-data-integrity#82 (5 comments by @gkellogg, @msporny, @OR13)
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66 (3 comments by @dlongley, @msporny)
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18 (3 comments by @msporny, @Wind4Greg)
-
Review on 2023-01-26 by Greg Bernstein w3c/vc-data-integrity#81 (3 comments by @msporny, @Wind4Greg)
-
JWS proof least significant bit change w3c/vc-data-integrity#68 (3 comments by @mkhraisha, @msporny)
-
Specify a default context if JSON-LD processing is required w3c/vc-data-integrity#88 (2 comments by @msporny)
-
Add diagrams and test vectors for `previousProof` w3c/vc-data-integrity#132 (2 comments by @msporny, @Wind4Greg)
-
Missing "created" invalidates signature? w3c/vc-data-integrity#23 (2 comments by @David-Chadwick, @msporny)
-
Add guidance on perma-caching contexts to align with VCDM w3c/vc-data-integrity#115 (2 comments by @msporny)
-
Is the sec entry in vocab/security/vocabulary.jsonld and vocab/security/vocabulary.ttl wrong? w3c/vc-data-integrity#72 (2 comments by @msporny)
-
Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#97 (1 comment by @msporny)
-
Add clarification for `verificationMethod` property being optional. w3c/vc-data-integrity#108 (1 comment by @msporny)
-
Add requirements on cryptosuite contexts such as `@protected` w3c/vc-data-integrity#48 (1 comment by @msporny)
-
Should this suite normatively require integrity checking of the context files? w3c/vc-data-integrity#179 (1 comment by @dmitrizagidulin)
-
Example that demonstrates input(s) and what gets fed to the signature algorithms? w3c/vc-data-integrity#19 (1 comment by @msporny)
-
serialization, canonicalized values and normalized datasets w3c/vc-data-integrity#11 (1 comment by @msporny)
-
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? w3c/vc-data-integrity#14 (1 comment by @msporny)
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (1 comment by @msporny)
-
-
29 pull requests opened.
-
Extended proof chain algorithms w3c/vc-data-integrity#145, by @Wind4Greg.
-
add missing comma w3c/vc-data-integrity#144, by @TallTed.
-
Correcting previously mis-corrected sentence w3c/vc-data-integrity#143, by @TallTed.
-
Added final versions of some properties (with anchors) w3c/vc-data-integrity#142, by @iherman.
-
Added the error terms to the vocabulary w3c/vc-data-integrity#141, by @iherman.
-
Add errors with anchors to the specification. w3c/vc-data-integrity#140, by @msporny.
-
Add section on Securing Data Losslessly. w3c/vc-data-integrity#139, by @msporny.
-
Add section on context injection. w3c/vc-data-integrity#138, by @msporny.
-
Update range of Multikey and JsonWebKey w3c/vc-data-integrity#137, by @msporny.
-
Add JSON Web Key to specification w3c/vc-data-integrity#135, by @msporny.
-
Explain use of each verify proof option. w3c/vc-data-integrity#134, by @msporny.
-
Clarify how proof types (and terms) are mapped to URLs. w3c/vc-data-integrity#133, by @msporny.
-
Require cryptosuite specifications to mitigate against poison graphs. w3c/vc-data-integrity#128, by @msporny.
-
Vocabulary pruning and improvement phase 1 w3c/vc-data-integrity#127, by @iherman.
-
Data Integrity Cryptosuites naming convention update w3c/vc-data-integrity#126, by @Wind4Greg.
-
Add requirement for protection of terms w3c/vc-data-integrity#125, by @Wind4Greg.
-
Add expires proof attribute w3c/vc-data-integrity#124, by @Wind4Greg.
-
Clarify verificationMethod for controller document w3c/vc-data-integrity#123, by @Wind4Greg.
-
Add creator generated nonce to proof. w3c/vc-data-integrity#122, by @Wind4Greg.
-
Added algorithms related to proof sets and chains. w3c/vc-data-integrity#121, by @Wind4Greg.
-
Add section on relationship to Verifiable Credentials w3c/vc-data-integrity#119, by @msporny.
-
Make "created" proof attribute optional. w3c/vc-data-integrity#118, by @Wind4Greg.
-
Add guidance to recommend usage of DataIntegrityProof pattern. w3c/vc-data-integrity#117, by @msporny.
-
Add hashes for context and vocab files. w3c/vc-data-integrity#116, by @msporny.
-
Add Greg and Sebastian as Editors to VC Data Integrity w3c/vc-data-integrity#113, by @msporny.
-
Add Accessibility Considerations section w3c/vc-data-integrity#112, by @msporny.
-
Add Internationalization Considerations section. w3c/vc-data-integrity#111, by @msporny.
-
Fix the sec prefix in the vocabulary. w3c/vc-data-integrity#109, by @msporny.
-
Remove outdated issues that have been addressed. w3c/vc-data-integrity#106, by @msporny.
-
-
21 pull requests merged.
-
Require cryptosuite specifications to mitigate against poison graphs. w3c/vc-data-integrity#128.
-
Vocabulary pruning and improvement phase 1 w3c/vc-data-integrity#127.
-
Data Integrity Cryptosuites naming convention update w3c/vc-data-integrity#126.
-
Add requirement for protection of terms w3c/vc-data-integrity#125.
-
Add expires proof attribute w3c/vc-data-integrity#124.
-
Clarify verificationMethod for controller document w3c/vc-data-integrity#123.
-
Add creator generated nonce to proof. w3c/vc-data-integrity#122.
-
Added algorithms related to proof sets and chains. w3c/vc-data-integrity#121.
-
Add section on relationship to Verifiable Credentials w3c/vc-data-integrity#119.
-
Make "created" proof attribute optional. w3c/vc-data-integrity#118.
-
Add guidance to recommend usage of DataIntegrityProof pattern. w3c/vc-data-integrity#117.
-
Add hashes for context and vocab files. w3c/vc-data-integrity#116.
-
Add Greg and Sebastian as Editors to VC Data Integrity w3c/vc-data-integrity#113.
-
Add Accessibility Considerations section w3c/vc-data-integrity#112.
-
Add Internationalization Considerations section. w3c/vc-data-integrity#111.
-
Fix the sec prefix in the vocabulary. w3c/vc-data-integrity#109.
-
Remove outdated issues that have been addressed. w3c/vc-data-integrity#106.
-
Fix examples and point to specifications w3c/vc-data-integrity#105.
-
Add related links to other specifications. Fix references. w3c/vc-data-integrity#104.
-
Cite Multibase normatively w3c/vc-data-integrity#102.
-
Update MULTIBASE Reference w3c/vc-data-integrity#101.
-
-
28 pull requests received 170 new comments.
-
Added algorithms related to proof sets and chains. w3c/vc-data-integrity#121 (27 comments by @msporny, @OR13, @TallTed, @Wind4Greg)
-
Add hashes for context and vocab files. w3c/vc-data-integrity#116 (27 comments by @iherman, @jyasskin, @msporny, @TallTed)
-
Data Integrity Cryptosuites naming convention update w3c/vc-data-integrity#126 (14 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add JSON Web Key to specification w3c/vc-data-integrity#135 (12 comments by @iherman, @mprorock, @msporny, @OR13)
-
Explain use of each verify proof option. w3c/vc-data-integrity#134 (9 comments by @dlongley, @msporny)
-
Add errors with anchors to the specification. w3c/vc-data-integrity#140 (8 comments by @iherman, @msporny, @TallTed)
-
Add guidance to recommend usage of DataIntegrityProof pattern. w3c/vc-data-integrity#117 (8 comments by @dlongley, @msporny, @TallTed)
-
Add creator generated nonce to proof. w3c/vc-data-integrity#122 (7 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
Add Internationalization Considerations section. w3c/vc-data-integrity#111 (7 comments by @aphillips, @msporny, @Wind4Greg)
-
Make "created" proof attribute optional. w3c/vc-data-integrity#118 (6 comments by @msporny, @TallTed, @Wind4Greg)
-
Add Greg and Sebastian as Editors to VC Data Integrity w3c/vc-data-integrity#113 (6 comments by @iherman, @msporny, @seabass-labrax, @Wind4Greg)
-
Require cryptosuite specifications to mitigate against poison graphs. w3c/vc-data-integrity#128 (5 comments by @msporny, @TallTed)
-
Fix examples and point to specifications w3c/vc-data-integrity#105 (5 comments by @msporny, @TallTed)
-
Vocabulary pruning and improvement phase 1 w3c/vc-data-integrity#127 (4 comments by @dlongley, @iherman, @msporny)
-
Add expires proof attribute w3c/vc-data-integrity#124 (4 comments by @David-Chadwick, @msporny, @TallTed)
-
Clarify how proof types (and terms) are mapped to URLs. w3c/vc-data-integrity#133 (3 comments by @iherman, @msporny)
-
Add section on relationship to Verifiable Credentials w3c/vc-data-integrity#119 (3 comments by @dlongley, @msporny)
-
Add requirement for protection of terms w3c/vc-data-integrity#125 (2 comments by @msporny, @TallTed)
-
Clarify verificationMethod for controller document w3c/vc-data-integrity#123 (1 comment by @TallTed)
-
Add related links to other specifications. Fix references. w3c/vc-data-integrity#104 (1 comment by @msporny)
-
w3c/vc-data-model-2.0-test-suite
-
5 issues opened.
-
Testing optional properties with null w3c/vc-data-model-2.0-test-suite#29, by @filip26.
-
New test proposal: validFrom must be before validUntil when both present w3c/vc-data-model-2.0-test-suite#28, by @filip26.
-
@type is not an URI test does not fail when using JSON-LD processor w3c/vc-data-model-2.0-test-suite#27, by @filip26.
-
Double Check 2 Credentials Tests related to mapping to urls w3c/vc-data-model-2.0-test-suite#24, by @aljones15.
-
Test that implementations can create VPs w3c/vc-data-model-2.0-test-suite#10, by @aljones15.
-
-
1 issue closed.
-
Test contains negative tests where URNs are expected to fail in place of URLs w3c/vc-data-model-2.0-test-suite#5.
-
-
3 issues received 4 new comments.
-
Test contains negative tests where URNs are expected to fail in place of URLs w3c/vc-data-model-2.0-test-suite#5 (2 comments by @aljones15, @clehner)
-
@type is not an URI test does not fail when using JSON-LD processor w3c/vc-data-model-2.0-test-suite#27 (1 comment by @filip26)
-
-
18 pull requests opened.
-
Skip refreshService tests (these should be in a separate suite). w3c/vc-data-model-2.0-test-suite#30, by @aljones15.
-
Fix vps w3c/vc-data-model-2.0-test-suite#26, by @aljones15.
-
Remove before block issue & prove for stability. w3c/vc-data-model-2.0-test-suite#25, by @aljones15.
-
Add examples context w3c/vc-data-model-2.0-test-suite#23, by @aljones15.
-
Correct typo readme w3c/vc-data-model-2.0-test-suite#22, by @aljones15.
-
Use more accurate examples in README.md. w3c/vc-data-model-2.0-test-suite#21, by @msporny.
-
Check id tests w3c/vc-data-model-2.0-test-suite#20, by @aljones15.
-
Remove test that requires validFrom and test data. w3c/vc-data-model-2.0-test-suite#19, by @aljones15.
-
Remove context order tests w3c/vc-data-model-2.0-test-suite#18, by @aljones15.
-
Use standard readme w3c/vc-data-model-2.0-test-suite#17, by @aljones15.
-
Removes the my custom context test from the suite. w3c/vc-data-model-2.0-test-suite#16, by @aljones15.
-
Review statements, add FIXMES, correct text & typos. w3c/vc-data-model-2.0-test-suite#15, by @aljones15.
-
Replace https://www.w3.org/ns/credentials/examples/v2 with inline con… w3c/vc-data-model-2.0-test-suite#14, by @aljones15.
-
Remove VCDM from package.json test command. w3c/vc-data-model-2.0-test-suite#13, by @aljones15.
-
Remove not implemented from tests and report. w3c/vc-data-model-2.0-test-suite#12, by @aljones15.
-
Remove example server and example implementation. w3c/vc-data-model-2.0-test-suite#11, by @aljones15.
-
Use vc2.0 as tag and repo name. w3c/vc-data-model-2.0-test-suite#9, by @aljones15.
-
Replace prove w3c/vc-data-model-2.0-test-suite#8, by @aljones15.
-
-
15 pull requests merged.
-
Review statements, add FIXMES, correct text & typos. w3c/vc-data-model-2.0-test-suite#15.
-
Remove before block issue & prove for stability. w3c/vc-data-model-2.0-test-suite#25.
-
Add examples context w3c/vc-data-model-2.0-test-suite#23.
-
Remove test that requires validFrom and test data. w3c/vc-data-model-2.0-test-suite#19.
-
Correct typo readme w3c/vc-data-model-2.0-test-suite#22.
-
Use standard readme w3c/vc-data-model-2.0-test-suite#17.
-
Use more accurate examples in README.md. w3c/vc-data-model-2.0-test-suite#21.
-
Check id tests w3c/vc-data-model-2.0-test-suite#20.
-
Remove context order tests w3c/vc-data-model-2.0-test-suite#18.
-
Removes the my custom context test from the suite. w3c/vc-data-model-2.0-test-suite#16.
-
Remove VCDM from package.json test command. w3c/vc-data-model-2.0-test-suite#13.
-
Remove not implemented from tests and report. w3c/vc-data-model-2.0-test-suite#12.
-
Remove example server and example implementation. w3c/vc-data-model-2.0-test-suite#11.
-
Use vc2.0 as tag and repo name. w3c/vc-data-model-2.0-test-suite#9.
-
Replace prove w3c/vc-data-model-2.0-test-suite#8.
-
-
1 pull request closed.
-
Replace https://www.w3.org/ns/credentials/examples/v2 with inline con… w3c/vc-data-model-2.0-test-suite#14.
-
-
8 pull requests received 16 new comments.
-
Remove test that requires validFrom and test data. w3c/vc-data-model-2.0-test-suite#19 (3 comments by @aljones15, @msporny)
-
Replace https://www.w3.org/ns/credentials/examples/v2 with inline con… w3c/vc-data-model-2.0-test-suite#14 (1 comment by @aljones15)
-
Remove example server and example implementation. w3c/vc-data-model-2.0-test-suite#11 (1 comment by @aljones15)
w3c/vc-bitstring-status-list
-
4 issues opened.
-
Vocabulary definitions w3c/vc-bitstring-status-list#81, by @iherman.
-
Section 4.3 should be improved to suggest utilization of OHTTP to prevent correlation w3c/vc-bitstring-status-list#80, by @kdenhartog.
-
Media type pairings w3c/vc-bitstring-status-list#78, by @OR13.
-
Security and Privacy Questionnaire w3c/vc-bitstring-status-list#77, by @mkhraisha.
-
-
1 issue closed.
-
Statuslist2021entry example inaccurate? w3c/vc-bitstring-status-list#71.
-
-
3 issues received 5 new comments.
-
Statuslist2021entry example inaccurate? w3c/vc-bitstring-status-list#71 (1 comment by @andresuribe87)
-
3 pull requests opened.
-
Fixing example typo w3c/vc-bitstring-status-list#79, by @andresuribe87.
-
fixes example JSON w3c/vc-bitstring-status-list#76, by @mkhraisha.
-
add explainer w3c/vc-bitstring-status-list#75, by @mkhraisha.
-
-
4 pull requests merged.
-
update contexts in examples to point to v2 w3c/vc-bitstring-status-list#74.
-
Fixing example typo w3c/vc-bitstring-status-list#79.
-
fixes example JSON w3c/vc-bitstring-status-list#76.
-
add explainer w3c/vc-bitstring-status-list#75.
-
-
5 pull requests received 32 new comments.
-
chore: update title and urls to contexts w3c/vc-bitstring-status-list#69 (12 comments by @iherman, @mprorock, @msporny)
w3c/vc-json-schema
-
10 issues opened.
-
Monitor the JSON Schema organization for publication of a long term support JSON Schema spec w3c/vc-json-schema#183, by @thereisnogabe.
-
Update term definitions to match the VCDM's vocab w3c/vc-json-schema#182, by @thereisnogabe.
-
Add language for handling implementation mismatches w3c/vc-json-schema#181, by @thereisnogabe.
-
Require all implementers to support at least one common JSON Schema version w3c/vc-json-schema#180, by @thereisnogabe.
-
Consider removing versioning from the name w3c/vc-json-schema#179, by @thereisnogabe.
-
Change VerifiableCredentialSchema2023 to use a new property with the @json type w3c/vc-json-schema#178, by @thereisnogabe.
-
Section 3.1.1 encourages dereferencable IRIs w3c/vc-json-schema#176, by @kdenhartog.
-
Add text to clarify when to use JsonSchema2023 over CredentialSchema2023 w3c/vc-json-schema#173, by @thereisnogabe.
-
What is the difference between JsonSchema2023 and CredentialSchema2023? w3c/vc-json-schema#172, by @msporny.
-
Add text describing implementation's ability to auto-select an applicable JSON Schema version w3c/vc-json-schema#171, by @thereisnogabe.
-
-
8 issues closed.
-
Change VerifiableCredentialSchema2023 to use a new property with the @json type w3c/vc-json-schema#178.
-
What is the difference between JsonSchema2023 and CredentialSchema2023? w3c/vc-json-schema#172.
-
Require all implementers to support at least one common JSON Schema version w3c/vc-json-schema#180.
-
Example of the credentialSchema.id resolution to schema w3c/vc-json-schema#19.
-
Accessibility Self-Review for VC JSON Schema w3c/vc-json-schema#163.
-
Consider adding language on schema immutability w3c/vc-json-schema#120.
-
Add text describing implementation's ability to auto-select an applicable JSON Schema version w3c/vc-json-schema#171.
-
Being able to normatively reference JSON Schema w3c/vc-json-schema#133.
-
-
12 issues received 18 new comments.
-
What is the difference between JsonSchema2023 and CredentialSchema2023? w3c/vc-json-schema#172 (5 comments by @dmitrizagidulin, @iherman, @msporny, @thereisnogabe)
-
Example of the credentialSchema.id resolution to schema w3c/vc-json-schema#19 (2 comments by @andresuribe87, @thereisnogabe)
-
Monitor the JSON Schema organization for publication of a long term support JSON Schema spec w3c/vc-json-schema#183 (2 comments by @thereisnogabe)
-
Change VerifiableCredentialSchema2023 to use a new property with the @json type w3c/vc-json-schema#178 (1 comment by @thereisnogabe)
-
Add language for handling implementation mismatches w3c/vc-json-schema#181 (1 comment by @thereisnogabe)
-
Consider adding language on schema immutability w3c/vc-json-schema#120 (1 comment by @thereisnogabe)
-
-
9 pull requests opened.
-
Rename IRI to URL and point to RFC w3c/vc-json-schema#188, by @andresuribe87.
-
Remove resolution section w3c/vc-json-schema#187, by @andresuribe87.
-
Update language around the defined types and their usages w3c/vc-json-schema#186, by @thereisnogabe.
-
Update term definitions according to the core vocab w3c/vc-json-schema#185, by @thereisnogabe.
-
Require at least one JSON Schema version w3c/vc-json-schema#184, by @thereisnogabe.
-
Added related resource text and example w3c/vc-json-schema#177, by @andresuribe87.
-
Add details on JSON schema processing w3c/vc-json-schema#175, by @thereisnogabe.
-
update credentialschema to verifiablecredentialschema w3c/vc-json-schema#174, by @thereisnogabe.
-
Add normative references for 3 json schema versions w3c/vc-json-schema#170, by @thereisnogabe.
-
-
7 pull requests merged.
-
Update language around the defined types and their usages w3c/vc-json-schema#186.
-
Require at least one JSON Schema version w3c/vc-json-schema#184.
-
Remove resolution section w3c/vc-json-schema#187.
-
Added related resource text and example w3c/vc-json-schema#177.
-
Add details on JSON schema processing w3c/vc-json-schema#175.
-
update credentialschema to verifiablecredentialschema w3c/vc-json-schema#174.
-
Add normative references for 3 json schema versions w3c/vc-json-schema#170.
-
-
6 pull requests received 45 new comments.
-
Update language around the defined types and their usages w3c/vc-json-schema#186 (13 comments by @andresuribe87, @iherman, @msporny, @thereisnogabe)
-
Add details on JSON schema processing w3c/vc-json-schema#175 (10 comments by @OR13, @TallTed, @thereisnogabe)
-
Update term definitions according to the core vocab w3c/vc-json-schema#185 (7 comments by @iherman, @TallTed, @thereisnogabe)
-
Added related resource text and example w3c/vc-json-schema#177 (7 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Add normative references for 3 json schema versions w3c/vc-json-schema#170 (5 comments by @iherman, @OR13, @thereisnogabe)
-
w3c/vc-use-cases
-
1 pull request opened.
-
Fake edit index.html w3c/vc-use-cases#147, by @jandrieu.
-
-
1 pull request merged.
-
Bona fide shopper w3c/vc-use-cases#145.
-
-
3 pull requests received 6 new comments.
w3c/vc-di-ecdsa
-
1 issue opened.
-
Remove `proofValue` MUST be a detached ECDSA normative statement w3c/vc-di-ecdsa#15, by @JSAssassin.
-
-
2 issues closed.
-
Remove `proofValue` MUST be a detached ECDSA normative statement w3c/vc-di-ecdsa#15.
-
Excelsior Pass divergence w3c/vc-di-ecdsa#3.
-
-
2 issues received 8 new comments.
-
Remove `proofValue` MUST be a detached ECDSA normative statement w3c/vc-di-ecdsa#15 (6 comments by @dlongley, @JSAssassin, @msporny, @TallTed)
-
-
7 pull requests opened.
-
Mitigate poison datasets in ECDSA when canonicalizing. w3c/vc-di-ecdsa#21, by @msporny.
-
Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification w3c/vc-di-ecdsa#20, by @msporny.
-
Add helper functions for performing selective disclosure w3c/vc-di-ecdsa#19, by @msporny.
-
Remove "detached". Clarify `proofValue` meanging w3c/vc-di-ecdsa#18, by @Wind4Greg.
-
Add Greg and Sebastian as Editors to ECDSA Cryptosuites w3c/vc-di-ecdsa#17, by @msporny.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-ecdsa#16, by @msporny.
-
Add links to related specifications at top of document. w3c/vc-di-ecdsa#14, by @msporny.
-
-
4 pull requests merged.
-
Remove "detached". Clarify `proofValue` meanging w3c/vc-di-ecdsa#18.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-ecdsa#16.
-
Add Greg and Sebastian as Editors to ECDSA Cryptosuites w3c/vc-di-ecdsa#17.
-
Add links to related specifications at top of document. w3c/vc-di-ecdsa#14.
-
-
7 pull requests received 19 new comments.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-ecdsa#16 (5 comments by @dlongley, @msporny, @TallTed)
-
Add ecdsa-sd-2023 cryptosuite to ECDSA Cryptosuites specification w3c/vc-di-ecdsa#20 (4 comments by @dlongley, @msporny, @Wind4Greg)
-
Add Greg and Sebastian as Editors to ECDSA Cryptosuites w3c/vc-di-ecdsa#17 (4 comments by @iherman, @msporny, @seabass-labrax)
-
Mitigate poison datasets in ECDSA when canonicalizing. w3c/vc-di-ecdsa#21 (3 comments by @pchampin, @TallTed)
-
Add helper functions for performing selective disclosure w3c/vc-di-ecdsa#19 (1 comment by @dlongley)
-
w3c/vc-di-eddsa
-
2 issues closed.
-
Necessary adjustments to the security vocabulary w3c/vc-di-eddsa#33.
-
-
4 issues received 16 new comments.
-
Necessary adjustments to the security vocabulary w3c/vc-di-eddsa#33 (6 comments by @dmitrizagidulin, @iherman, @msporny)
-
Is Example 15 / 16 correct? w3c/vc-di-eddsa#38 (5 comments by @dmitrizagidulin, @HelgeKrueger, @msporny, @silverpill, @Wind4Greg)
-
Consider making verification method id to be multicodec (instead of just JWK thumbprint) w3c/vc-di-eddsa#5 (1 comment by @dmitrizagidulin)
-
-
4 pull requests opened.
-
Add EdDSA mitigation for dataset poisoning. w3c/vc-di-eddsa#51, by @msporny.
-
Add Greg and Sebastian as Editors to EdDSA Cryptosuites w3c/vc-di-eddsa#50, by @msporny.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-eddsa#49, by @msporny.
-
Add list of related specifications to top of document. w3c/vc-di-eddsa#48, by @msporny.
-
-
3 pull requests merged.
-
Add Greg and Sebastian as Editors to EdDSA Cryptosuites w3c/vc-di-eddsa#50.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-eddsa#49.
-
Add list of related specifications to top of document. w3c/vc-di-eddsa#48.
-
-
4 pull requests received 19 new comments.
-
Set the normative definition of Multikey to the Data Integrity spec. w3c/vc-di-eddsa#49 (8 comments by @dmitrizagidulin, @msporny, @TallTed)
-
Add Greg and Sebastian as Editors to EdDSA Cryptosuites w3c/vc-di-eddsa#50 (5 comments by @brentzundel, @iherman, @msporny, @seabass-labrax)
-
Add list of related specifications to top of document. w3c/vc-di-eddsa#48 (3 comments by @msporny, @TallTed)
-
w3c/vcalm
-
1 issue opened.
-
Questions regarding `QueryByExample` structure and handling w3c/vcalm#538, by @geel9.
-
-
5 issues closed.
-
updateCredentialStatus PATCH instead of POST? w3c/vcalm#339.
-
API lacks required discoverability features w3c/vcalm#218.
-
Production utilities endpoints w3c/vcalm#333.
-
-
8 issues received 8 new comments.
-
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.) w3c/vcalm#285 (1 comment by @msporny)
w3c/vc-confidence-method
-
3 issues opened.
-
Deployment link is broken w3c/vc-confidence-method#7, by @RajeevDash007.
-
Get w3id domain resolving w3c/vc-confidence-method#6, by @brianorwhatever.
-
Deploy github pages build w3c/vc-confidence-method#5, by @brianorwhatever.
-
-
1 pull request opened.
-
Add CCG properties w3c/vc-confidence-method#4, by @brianorwhatever.
-
w3c/vc-di-eddsa-test-suite
-
8 pull requests opened.
-
Renames package name to `vc-di-eddsa-test-suite`. w3c/vc-di-eddsa-test-suite#18, by @JSAssassin.
-
minor language and markup fixes w3c/vc-di-eddsa-test-suite#17, by @TallTed.
-
minor language and markup fixes w3c/vc-di-eddsa-test-suite#16, by @TallTed.
-
Fix test suite name in README. w3c/vc-di-eddsa-test-suite#15, by @JSAssassin.
-
Update `README.md`. w3c/vc-di-eddsa-test-suite#14, by @JSAssassin.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-di-eddsa-test-suite#13, by @JSAssassin.
-
Remove `not-implemented` cells from test report. w3c/vc-di-eddsa-test-suite#12, by @JSAssassin.
-
Removes general verify proof tests and uses `checkDataIntegrityProofVerifyErrors` to test them. w3c/vc-di-eddsa-test-suite#11, by @JSAssassin.
-
-
7 pull requests merged.
-
Renames package name to `vc-di-eddsa-test-suite`. w3c/vc-di-eddsa-test-suite#18.
-
minor language and markup fixes w3c/vc-di-eddsa-test-suite#16.
-
Fix test suite name in README. w3c/vc-di-eddsa-test-suite#15.
-
Update `README.md`. w3c/vc-di-eddsa-test-suite#14.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-di-eddsa-test-suite#13.
-
Remove `not-implemented` cells from test report. w3c/vc-di-eddsa-test-suite#12.
-
Removes general verify proof tests and uses `checkDataIntegrityProofVerifyErrors` to test them. w3c/vc-di-eddsa-test-suite#11.
-
-
1 pull request closed.
-
minor language and markup fixes w3c/vc-di-eddsa-test-suite#17.
-
-
4 pull requests received 6 new comments.
-
Renames package name to `vc-di-eddsa-test-suite`. w3c/vc-di-eddsa-test-suite#18 (2 comments by @msporny)
-
Removes general verify proof tests and uses `checkDataIntegrityProofVerifyErrors` to test them. w3c/vc-di-eddsa-test-suite#11 (1 comment by @JSAssassin)
-
w3c/vc-di-ecdsa-test-suite
-
10 pull requests opened.
-
Update `package.json` description and `respecConfig` subtitle. w3c/vc-di-ecdsa-test-suite#11, by @JSAssassin.
-
Fix test for unmatching `cryptosuite` field and add assertion for w3c/vc-di-ecdsa-test-suite#10, by @aljones15.
-
Fix test for unmatching cryptosuite field and add assertion for `error.status`. w3c/vc-di-ecdsa-test-suite#9, by @JSAssassin.
-
Fix test for unmatching `cryptosuite` field and add assertion for `error.status` w3c/vc-di-ecdsa-test-suite#8, by @JSAssassin.
-
minor language and markup fixes w3c/vc-di-ecdsa-test-suite#7, by @TallTed.
-
Update `README.md`. w3c/vc-di-ecdsa-test-suite#6, by @JSAssassin.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-di-ecdsa-test-suite#5, by @JSAssassin.
-
Remove `not implemented` implementations from test report. w3c/vc-di-ecdsa-test-suite#4, by @JSAssassin.
-
Add issuance date to initial vc. w3c/vc-di-ecdsa-test-suite#3, by @JSAssassin.
-
Add tests for verify proof w3c/vc-di-ecdsa-test-suite#2, by @JSAssassin.
-
-
9 pull requests merged.
-
Update `package.json` description and `respecConfig` subtitle. w3c/vc-di-ecdsa-test-suite#11.
-
Fix test for unmatching `cryptosuite` field and add assertion for `error.status` w3c/vc-di-ecdsa-test-suite#8.
-
minor language and markup fixes w3c/vc-di-ecdsa-test-suite#7.
-
Update `README.md`. w3c/vc-di-ecdsa-test-suite#6.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-di-ecdsa-test-suite#5.
-
Remove `not implemented` implementations from test report. w3c/vc-di-ecdsa-test-suite#4.
-
Add issuance date to initial vc. w3c/vc-di-ecdsa-test-suite#3.
-
Add issuer and interop tests. w3c/vc-di-ecdsa-test-suite#1.
-
Add tests for verify proof w3c/vc-di-ecdsa-test-suite#2.
-
-
2 pull requests closed.
-
Fix test for unmatching cryptosuite field and add assertion for `error.status`. w3c/vc-di-ecdsa-test-suite#9.
-
Fix test for unmatching `cryptosuite` field and add assertion for w3c/vc-di-ecdsa-test-suite#10.
-
-
7 pull requests received 34 new comments.
-
Add issuer and interop tests. w3c/vc-di-ecdsa-test-suite#1 (24 comments by @aljones15, @JSAssassin, @msporny)
-
Update `package.json` description and `respecConfig` subtitle. w3c/vc-di-ecdsa-test-suite#11 (2 comments by @msporny)
-
Fix test for unmatching cryptosuite field and add assertion for `error.status`. w3c/vc-di-ecdsa-test-suite#9 (1 comment by @JSAssassin)
-
Remove `not implemented` implementations from test report. w3c/vc-di-ecdsa-test-suite#4 (1 comment by @JSAssassin)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 issue received 1 new comment.
-
Test suite does not deference verificationMethod w3c/vc-di-ed25519signature2020-test-suite#23 (1 comment by @aljones15)
-
-
6 pull requests opened.
-
Update `README.md`. w3c/vc-di-ed25519signature2020-test-suite#39, by @JSAssassin.
-
Use `mocha-w3c-interop-reporter@1.4.0`. w3c/vc-di-ed25519signature2020-test-suite#38, by @JSAssassin.
-
Fix tag to filter implementations. w3c/vc-di-ed25519signature2020-test-suite#37, by @JSAssassin.
-
Removes `not-implemented` implementations from test report. w3c/vc-di-ed25519signature2020-test-suite#36, by @JSAssassin.
-
Update package name to `di-ed25519signature2020-test-suite`. w3c/vc-di-ed25519signature2020-test-suite#35, by @JSAssassin.
-
Remove general data integrity proof format and verify tests and use latest `data-integrity-test-suite-assertion` lib. w3c/vc-di-ed25519signature2020-test-suite#34, by @JSAssassin.
-
-
6 pull requests merged.
-
Update `README.md`. w3c/vc-di-ed25519signature2020-test-suite#39.
-
Use `mocha-w3c-interop-reporter@1.4.0`. w3c/vc-di-ed25519signature2020-test-suite#38.
-
Fix tag to filter implementations. w3c/vc-di-ed25519signature2020-test-suite#37.
-
Removes `not-implemented` implementations from test report. w3c/vc-di-ed25519signature2020-test-suite#36.
-
Remove general data integrity proof format and verify tests and use latest `data-integrity-test-suite-assertion` lib. w3c/vc-di-ed25519signature2020-test-suite#34.
-
Update package name to `di-ed25519signature2020-test-suite`. w3c/vc-di-ed25519signature2020-test-suite#35.
-
-
1 pull request received 12 new comments.
-
Update `README.md`. w3c/vc-di-ed25519signature2020-test-suite#39 (12 comments by @JSAssassin, @msporny, @TallTed)
-
w3c/vc-jose-cose
-
5 issues opened.
-
Clarify relationship between validity times w3c/vc-jose-cose#133, by @David-Chadwick.
-
JWT - securing mechanism or not? w3c/vc-jose-cose#132, by @alenhorvat.
-
File PING request once rename is complete w3c/vc-jose-cose#128, by @mprorock.
-
Define Controller Documents in the Core Data Model w3c/vc-jose-cose#140, by @OR13.
-
Better references to OIDC key discovery w3c/vc-jose-cose#127, by @OR13.
-
-
19 issues closed.
-
No normative statement wrt. JWT encoding of `verifiableCredential` as base64url w3c/vc-jose-cose#3.
-
clarify that `vc` `vp` claims do not include entire VC/VPs w3c/vc-jose-cose#4.
-
Support for multiple signatures w3c/vc-jose-cose#6.
-
Various discussion points for VC-JWT Specification w3c/vc-jose-cose#14.
-
vc-jws w3c/vc-jose-cose#12.
-
Confusing text about "If no JWS is present" w3c/vc-jose-cose#23.
-
How best to describe the VC-JWT Production Rules w3c/vc-jose-cose#36.
-
Address the `alg` language per the comment here w3c/vc-jose-cose#37.
-
Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. w3c/vc-jose-cose#42.
-
clearer wording for step 2 w3c/vc-jose-cose#43.
-
F2F mapping converstation w3c/vc-jose-cose#53.
-
Add guidance on what to do id `proof` is present in VC-JWT w3c/vc-jose-cose#62.
-
Why do we have a v1.1 in this specification? w3c/vc-jose-cose#65.
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66.
-
Add guidance on mapping to the core data model w3c/vc-jose-cose#69.
-
Define how to obtain verification keys for vc-jwt w3c/vc-jose-cose#70.
-
Interpretation of Day 3 Resolutions w3c/vc-jose-cose#73.
-
Handling of "type" not clear in v2 w3c/vc-jose-cose#76.
-
Determine if Privacy Section can be normative w3c/vc-jose-cose#82.
-
-
1 issue reopened.
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64, by @OR13.
-
-
30 issues received 56 new comments.
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64 (9 comments by @David-Chadwick, @iherman, @mprorock, @OR13)
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117 (5 comments by @OR13, @TallTed)
-
Define Controller Documents in the Core Data Model w3c/vc-jose-cose#140 (3 comments by @iherman, @msporny)
-
clarify that `vc` `vp` claims do not include entire VC/VPs w3c/vc-jose-cose#4 (3 comments by @OR13, @TallTed)
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9 (2 comments by @OR13, @TallTed)
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15 (2 comments by @OR13, @TallTed)
-
No normative statement wrt. JWT encoding of `verifiableCredential` as base64url w3c/vc-jose-cose#3 (1 comment by @OR13)
-
Determine whether to include content from Verifiable Credentials Implementation Guidelines w3c/vc-jose-cose#28 (1 comment by @OR13)
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66 (1 comment by @OR13)
-
-
8 pull requests opened.
-
Testing Echidna w3c/vc-jose-cose#130, by @OR13.
-
update echidna shortname w3c/vc-jose-cose#129, by @OR13.
-
Necessary respec changes w3c/vc-jose-cose#126, by @iherman.
-
Rename work item w3c/vc-jose-cose#125, by @OR13.
-
Add deprecated claim names w3c/vc-jose-cose#124, by @OR13.
-
Address Ambiguity Regarding Multiple Structured Suffixes w3c/vc-jose-cose#123, by @OR13.
-
Add key discovery example w3c/vc-jose-cose#122, by @OR13.
-
9 pull requests merged.
-
Updates w3c/vc-jose-cose#131.
-
Testing Echidna w3c/vc-jose-cose#130.
-
Add deprecated claim names w3c/vc-jose-cose#124.
-
update echidna shortname w3c/vc-jose-cose#129.
-
Necessary respec changes w3c/vc-jose-cose#126.
-
Add key discovery example w3c/vc-jose-cose#122.
-
Clarify json ld is not a cwt claimset w3c/vc-jose-cose#120.
-
Add sd-jwt example w3c/vc-jose-cose#114.
-
Add comments on key discovery w3c/vc-jose-cose#111.
-
-
2 pull requests closed.
-
Change short name to vc-jose-cose w3c/vc-jose-cose#115.
-
Rename work item w3c/vc-jose-cose#125.
-
-
12 pull requests received 147 new comments.
-
Address Ambiguity Regarding Multiple Structured Suffixes w3c/vc-jose-cose#123 (44 comments by @brentzundel, @dlongley, @msporny, @OR13, @TallTed)
-
Change short name to vc-jose-cose w3c/vc-jose-cose#115 (11 comments by @brentzundel, @iherman, @OR13)
-
w3c/vc-test-suite
-
1 issue received 3 new comments.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (3 comments by @iherman, @longpd)
-
w3c/vc-render-method
-
1 issue closed.
-
Update repo About link. w3c/vc-render-method#3.
-
-
1 issue received 1 new comment.
w3c/vc-bitstring-status-list-test-suite
-
2 pull requests opened.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-bitstring-status-list-test-suite#24, by @JSAssassin.
-
Fixes interop tests report, moves tests for verification of revoked and suspended status list credentials into `verify.js` tests. w3c/vc-bitstring-status-list-test-suite#23, by @JSAssassin.
-
-
2 pull requests merged.
-
Use `mocha-w3c-interop-reporter@1.4`. w3c/vc-bitstring-status-list-test-suite#24.
-
Fixes interop tests report, moves tests for verification of revoked and suspended status list credentials into `verify.js` tests. w3c/vc-bitstring-status-list-test-suite#23.
-
w3c/vc-di-bbs
-
2 issues received 4 new comments.
w3c/vc-extensions
-
1 issue received 3 new comments.
-
Rename repository to `vc-specs` before FPWD w3c/vc-extensions#17 (3 comments by @brentzundel, @iherman)
-
-
3 pull requests opened.
-
Update references to VCWG Data Integrity cryptosuites. w3c/vc-extensions#26, by @msporny.
-
feat: add Ethr Revocation 2022 .json w3c/vc-extensions#25, by @lleifermann.
-
OCI DSCSA credentials w3c/vc-extensions#24, by @alexcolganLD.
-
-
5 pull requests merged.
-
Update references to VCWG Data Integrity cryptosuites. w3c/vc-extensions#26.
-
feat: add Ethr Revocation 2022 .json w3c/vc-extensions#25.
-
OCI DSCSA credentials w3c/vc-extensions#24.
-
Register withdrawn work item w3c/vc-extensions#22.
-
register spec w3c/vc-extensions#21.
-
-
2 pull requests received 6 new comments.
-
Update references to VCWG Data Integrity cryptosuites. w3c/vc-extensions#26 (4 comments by @msporny, @OR13)
-
w3c/cid
-
1 issue received 2 new comments.
TR publications
-
20 documents published.
-
Securing Verifiable Credentials using JOSE and COSE published 7 times as a Working Draft. History of Securing Verifiable Credentials using JOSE and COSE
-
Verifiable Credential Data Integrity 1.0 published as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published 5 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
JSON Web Signatures for Data Integrity Proofs published as a Working Draft. History of JSON Web Signatures for Data Integrity Proofs
-
ECDSA Cryptosuite v2019 published 3 times as a Working Draft. History of ECDSA Cryptosuite v2019
-
Verifiable Credentials JSON Schema Specification 2023 published twice as a Working Draft. History of Verifiable Credentials JSON Schema Specification 2023
-
EdDSA Cryptosuite v2022 published as a Working Draft. History of EdDSA Cryptosuite v2022
-
Past meetings
-
8 meetings.
Participants
-
3 participants joined.
-
Paolo De Rosa (W3C Invited Experts) joined.
-
Margery Clacy (Centre for Inclusive Design) joined.
-
Bruno Vavala (W3C Invited Experts) joined.
-
-
2 organizations joined.
-
Centre for Inclusive Design joined.
-
Intel Corporation joined.
-
GitHub
w3c/vc-json-schema
-
4 issues opened.
-
Security and Privacy Self-Review Questionnaire w3c/vc-json-schema#167, by @thereisnogabe.
-
Add language around not including PII or sensitive information in JSON Schemas w3c/vc-json-schema#166, by @thereisnogabe.
-
Internationalization Review for VC JSON Schema w3c/vc-json-schema#164, by @thereisnogabe.
-
Accessibility Self-Review for VC JSON Schema w3c/vc-json-schema#163, by @thereisnogabe.
-
-
4 issues closed.
-
Add language around not including PII or sensitive information in JSON Schemas w3c/vc-json-schema#166.
-
Add section on i18n considerations w3c/vc-json-schema#148.
-
Add section on accessibility considerations w3c/vc-json-schema#147.
-
Add section on warning for reserved words in JSON schema versions w3c/vc-json-schema#146.
-
-
1 issue reopened.
-
Being able to normatively reference JSON Schema w3c/vc-json-schema#133, by @thereisnogabe.
-
-
6 issues received 17 new comments.
-
Being able to normatively reference JSON Schema w3c/vc-json-schema#133 (9 comments by @iherman, @msporny, @OR13, @Relequestual, @thereisnogabe)
-
Security and Privacy Self-Review Questionnaire w3c/vc-json-schema#167 (3 comments by @iherman, @thereisnogabe)
-
Internationalization Review for VC JSON Schema w3c/vc-json-schema#164 (2 comments by @andresuribe87, @thereisnogabe)
-
Exact URL-s for the JsonSchema2023 and CredentialSchema2023 w3c/vc-json-schema#154 (1 comment by @OR13)
-
-
4 pull requests opened.
-
add a11y and i18n text w3c/vc-json-schema#169, by @thereisnogabe.
-
Add section addressing PII in schemas w3c/vc-json-schema#168, by @thereisnogabe.
-
fix language, punctuation, etc., in EXPLAINER.md & README.md w3c/vc-json-schema#165, by @TallTed.
-
Add EXPLAINER.md w3c/vc-json-schema#162, by @thereisnogabe.
-
-
5 pull requests merged.
-
Add section addressing PII in schemas w3c/vc-json-schema#168.
-
add a11y and i18n text w3c/vc-json-schema#169.
-
fix language, punctuation, etc., in EXPLAINER.md & README.md w3c/vc-json-schema#165.
-
Add EXPLAINER.md w3c/vc-json-schema#162.
-
Add section on reserved keywords w3c/vc-json-schema#161.
-
-
4 pull requests received 17 new comments.
-
Add section addressing PII in schemas w3c/vc-json-schema#168 (4 comments by @andresuribe87, @OR13, @TallTed, @thereisnogabe)
w3c/vc-data-model
-
18 issues opened.
-
Provide guidance for when hash values do not match specification text w3c/vc-data-model#1177, by @msporny.
-
Define what a credential validity does mean w3c/vc-data-model#1176, by @filip26.
-
Ensure the base context doesn't constrain lower-maturity specifications w3c/vc-data-model#1175, by @jyasskin.
-
Entities and Parties w3c/vc-data-model#1173, by @RieksJ.
-
Consider removing Use Cases summary from core DM w3c/vc-data-model#1169, by @brentzundel.
-
consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` w3c/vc-data-model#1162, by @TallTed.
-
(tracking issue) apparent copy-paste error in #1144 needs fixing w3c/vc-data-model#1161, by @TallTed.
-
id, issuer properties: URL or URI w3c/vc-data-model#1160, by @alenhorvat.
-
Security and Privacy Self-Review Questionnaire w3c/vc-data-model#1157, by @awoie.
-
Accessibility Self-Review for VCDM 2.0 w3c/vc-data-model#1156, by @awoie.
-
Internationalization Review for VCDM 2.0 w3c/vc-data-model#1155, by @awoie.
-
Transfer respec-vc to W3C VCWG? w3c/vc-data-model#1154, by @msporny.
-
RsaSignature2018 v1 spec definitions w3c/vc-data-model#1151, by @fabrii.
-
Protected term errors when supporting v1 and v2 w3c/vc-data-model#1150, by @OR13.
-
Check status privacy w3c/vc-data-model#1148, by @fabrii.
-
Depreciation of "Evidence" w3c/vc-data-model#1147, by @rceleste125.
-
Respec VC plugin is breaking the build w3c/vc-data-model#1145, by @OR13.
-
-
28 issues closed.
-
Presentations SHOULD expire w3c/vc-data-model#937.
-
Remove normative statements from vocab w3c/vc-data-model#1077.
-
Collusion, i.e. collaboration, between Alice and Bob w3c/vc-data-model#1136.
-
Respec VC plugin is breaking the build w3c/vc-data-model#1145.
-
Define "prover" in addition to "holder". w3c/vc-data-model#902.
-
Verifier Role Confusion w3c/vc-data-model#984.
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988.
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031.
-
Depreciation of "Evidence" w3c/vc-data-model#1147.
-
Update diagrams to not use RSA, and generally be accurate w3c/vc-data-model#1121.
-
Pull out `id` from `credentialSubject`. Change `credentialSubject` to `claims`. w3c/vc-data-model#1130.
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946.
-
Requesting content type for presentation w3c/vc-data-model#1017.
-
id, issuer properties: URL or URI w3c/vc-data-model#1160.
-
Support for SD-JWT w3c/vc-data-model#1019.
-
PresentationSchema for VPs w3c/vc-data-model#839.
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875.
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896.
-
Add "credential boilerplates" as examples w3c/vc-data-model#935.
-
Specify allowed Verifier interactions with Verifiable Data Registries w3c/vc-data-model#1016.
-
Fix media type registration language w3c/vc-data-model#1052.
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932.
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967.
-
Single Extension Point w3c/vc-data-model#1102.
-
How could we deals with chain reaction revocation of VC? w3c/vc-data-model#1072.
-
2 issues reopened.
-
Respec VC plugin is breaking the build w3c/vc-data-model#1145, by @iherman.
-
[Terminology] claim w3c/vc-data-model#995, by @brentzundel.
-
-
81 issues received 287 new comments.
-
Create the new role of issuee w3c/vc-data-model#942 (13 comments by @awoie, @brentzundel, @David-Chadwick, @iherman, @OR13, @RieksJ, @Sakurann, @TallTed)
-
RsaSignature2018 v1 spec definitions w3c/vc-data-model#1151 (11 comments by @brentzundel, @fabrii, @msporny, @OR13)
-
Define what a credential validity does mean w3c/vc-data-model#1176 (10 comments by @andresuribe87, @brentzundel, @filip26, @jandrieu, @OR13)
-
Question about verifiable presentations w3c/vc-data-model#996 (10 comments by @awoie, @brentzundel, @dlongley, @iherman, @msporny, @Sakurann, @stenreijers)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (10 comments by @agropper, @brentzundel, @David-Chadwick, @iherman, @jandrieu, @Sakurann)
-
consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` w3c/vc-data-model#1162 (8 comments by @awoie, @brentzundel, @OR13, @TallTed)
-
Vocabulary normative, context isn't? w3c/vc-data-model#1103 (7 comments by @brentzundel, @iherman, @melvincarvalho, @msporny)
-
[Terminology] claim w3c/vc-data-model#995 (7 comments by @brentzundel, @iherman, @RieksJ, @Sakurann, @TallTed)
-
Verification of multiple credential schemas w3c/vc-data-model#950 (6 comments by @brentzundel, @dlongley, @OR13, @TallTed, @thereisnogabe)
-
Collusion, i.e. collaboration, between Alice and Bob w3c/vc-data-model#1136 (6 comments by @awoie, @brentzundel, @Denisthemalice, @msporny)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (6 comments by @brentzundel, @iherman, @RieksJ, @Sakurann, @TallTed)
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090 (6 comments by @brentzundel, @iherman, @OR13, @shigeya)
-
Add guidance on ignoring optional fields w3c/vc-data-model#1027 (5 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @OR13)
-
Address "Credential" vs "VerifiableCredential" w3c/vc-data-model#1126 (5 comments by @brentzundel, @David-Chadwick, @OR13)
-
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? w3c/vc-data-model#1134 (5 comments by @iherman, @OR13, @thereisnogabe)
-
Check status privacy w3c/vc-data-model#1148 (5 comments by @brentzundel, @dlongley, @fabrii, @iherman, @OR13)
-
(Editorial) systematically adding an anchor to each property w3c/vc-data-model#1080 (5 comments by @iherman, @msporny, @Sakurann)
-
Ensure the base context doesn't constrain lower-maturity specifications w3c/vc-data-model#1175 (4 comments by @mprorock, @OR13, @selfissued)
-
Consider removing Use Cases summary from core DM w3c/vc-data-model#1169 (4 comments by @brentzundel, @msporny, @OR13)
-
Depreciation of "Evidence" w3c/vc-data-model#1147 (4 comments by @brentzundel, @TallTed, @thereisnogabe)
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932 (4 comments by @dlongley, @iherman, @OR13, @thereisnogabe)
-
Remove normative statements from vocab w3c/vc-data-model#1077 (3 comments by @brentzundel, @iherman, @msporny)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (3 comments by @filip26, @iherman, @OR13)
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881 (3 comments by @iherman, @OR13)
-
Respec VC plugin is breaking the build w3c/vc-data-model#1145 (3 comments by @iherman, @OR13, @TallTed)
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031 (3 comments by @brentzundel, @iherman, @Sakurann)
-
Remove reference to DocumentVerification2018 w3c/vc-data-model#1124 (3 comments by @brentzundel, @Sakurann, @TallTed)
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875 (3 comments by @brentzundel, @iherman, @OR13)
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896 (3 comments by @brentzundel, @iherman, @jandrieu)
-
Add "credential boilerplates" as examples w3c/vc-data-model#935 (3 comments by @brentzundel, @iherman, @OR13)
-
Specify allowed Verifier interactions with Verifiable Data Registries w3c/vc-data-model#1016 (3 comments by @brentzundel, @iherman)
-
Fix media type registration language w3c/vc-data-model#1052 (3 comments by @brentzundel, @iherman, @OR13)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (2 comments by @iherman, @OR13)
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009 (2 comments by @iherman, @OR13)
-
Remove reference toCredentialManagerPresentation w3c/vc-data-model#1125 (2 comments by @iherman, @msporny)
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089 (2 comments by @iherman, @OR13)
-
"bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders w3c/vc-data-model#821 (2 comments by @brentzundel, @iherman)
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988 (2 comments by @brentzundel)
-
(tracking issue) apparent copy-paste error in #1144 needs fixing w3c/vc-data-model#1161 (2 comments by @brentzundel, @msporny)
-
Add `render` property to a core VC data model w3c/vc-data-model#928 (2 comments by @brentzundel, @Sakurann)
-
Provide guidance when media type is incorrect w3c/vc-data-model#1015 (2 comments by @iherman, @OR13)
-
Add language that there is generally no relationship between a VP and their VCs other than integrity protection w3c/vc-data-model#1165 (1 comment by @brentzundel)
-
VC Vocabulary v2.0 does not have any term definitions w3c/vc-data-model#1117 (1 comment by @iherman)
-
Handle predicate for confidenceMethod in JSON-LD context w3c/vc-data-model#1116 (1 comment by @brentzundel)
-
How should we refer to the Securing specifications? w3c/vc-data-model#1105 (1 comment by @brentzundel)
-
Update diagrams to not use RSA, and generally be accurate w3c/vc-data-model#1121 (1 comment by @brentzundel)
-
Pull out `id` from `credentialSubject`. Change `credentialSubject` to `claims`. w3c/vc-data-model#1130 (1 comment by @thereisnogabe)
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946 (1 comment by @brentzundel)
-
Missing security considerations on MITM, cloning etc. w3c/vc-data-model#1138 (1 comment by @thereisnogabe)
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967 (1 comment by @msporny)
-
Base context v1 missing `sec:` mapping in RsaSignature2018 "@context" w3c/vc-data-model#778 (1 comment by @fabrii)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @iherman)
-
How could we deals with chain reaction revocation of VC? w3c/vc-data-model#1072 (1 comment by @brentzundel)
-
Add references in vocabulary that link back to the VCDM document w3c/vc-data-model#1061 (1 comment by @iherman)
-
22 pull requests opened.
-
Presentations w3c/vc-data-model#1181, by @brentzundel.
-
fix typo in vp+ld+json IANA considerations w3c/vc-data-model#1180, by @brentzundel.
-
remove 'credential' and 'presentation' from 'type' examples table w3c/vc-data-model#1179, by @brentzundel.
-
add vc-json-schema to vocab and context w3c/vc-data-model#1178, by @thereisnogabe.
-
Updated privacy language in diagram w3c/vc-data-model#1174, by @andresuribe87.
-
Add "author" and "party" to terminology, rewrite "claim" terminology w3c/vc-data-model#1172, by @RieksJ.
-
add issue numbers to at risk extension points w3c/vc-data-model#1171, by @brentzundel.
-
Update example types w3c/vc-data-model#1170, by @brentzundel.
-
made validFrom optional, fixes #1133 w3c/vc-data-model#1168, by @awoie.
-
Clarify sentence about derived credentials and presentations w3c/vc-data-model#1167, by @brentzundel.
-
Clean up use-cases summary w3c/vc-data-model#1166, by @brentzundel.
-
Add language clarifying VP is short-lived w3c/vc-data-model#1164, by @brentzundel.
-
Rationalize and clarify IANA Considerations w3c/vc-data-model#1163, by @TallTed.
-
Make the vocabulary URLs and values normative w3c/vc-data-model#1159, by @msporny.
-
Make the value of the base context normative. w3c/vc-data-model#1158, by @msporny.
-
Add graph node identifiers for registered claims w3c/vc-data-model#1149, by @OR13.
-
Remove script breaking echidna w3c/vc-data-model#1146, by @OR13.
-
Request vp media type w3c/vc-data-model#1144, by @OR13.
-
Remove closed issue marker w3c/vc-data-model#1143, by @OR13.
-
Add confidenceMethod to table of reserved terms and v2 `@context` w3c/vc-data-model#1142, by @OR13.
-
Add issue marker for extension point reservation discussion w3c/vc-data-model#1141, by @OR13.
-
add context integrity capabilities to the core data model w3c/vc-data-model#1140, by @mprorock.
-
-
9 pull requests merged.
-
Make the vocabulary URLs and values normative w3c/vc-data-model#1159.
-
Clean up use-cases summary w3c/vc-data-model#1166.
-
Add language clarifying VP is short-lived w3c/vc-data-model#1164.
-
Make the value of the base context normative. w3c/vc-data-model#1158.
-
add context integrity capabilities to the core data model w3c/vc-data-model#1140.
-
Add issue marker for extension point reservation discussion w3c/vc-data-model#1141.
-
Request vp media type w3c/vc-data-model#1144.
-
Remove closed issue marker w3c/vc-data-model#1143.
-
Attempt to add req list w3c/vc-data-model#1131.
-
-
4 pull requests closed.
-
Add confidence method to VCDM w3c/vc-data-model#1054.
-
Clarify sentence about derived credentials and presentations w3c/vc-data-model#1167.
-
Remove script breaking echidna w3c/vc-data-model#1146.
-
Remove DataIntegrityProof from v2 context w3c/vc-data-model#1091.
-
-
20 pull requests received 428 new comments.
-
add context integrity capabilities to the core data model w3c/vc-data-model#1140 (166 comments by @andresuribe87, @brentzundel, @davidlehn, @dlongley, @dmitrizagidulin, @iherman, @mprorock, @msporny, @OR13, @paulfdietrich, @selfissued, @TallTed, @thereisnogabe)
-
Add graph node identifiers for registered claims w3c/vc-data-model#1149 (29 comments by @brentzundel, @dlongley, @iherman, @mprorock, @msporny, @OR13, @TallTed)
-
Make the value of the base context normative. w3c/vc-data-model#1158 (29 comments by @brentzundel, @dlongley, @iherman, @jyasskin, @mprorock, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Add confidenceMethod to table of reserved terms and v2 `@context` w3c/vc-data-model#1142 (26 comments by @awoie, @brentzundel, @dlongley, @iherman, @jandrieu, @msporny, @OR13, @TallTed)
-
Make the vocabulary URLs and values normative w3c/vc-data-model#1159 (24 comments by @andresuribe87, @iherman, @msporny, @OR13)
-
Remove JSON section in lieu of `application/vc+ld+json`. w3c/vc-data-model#1088 (23 comments by @alenhorvat, @dlongley, @msporny, @mtaimela, @OR13, @Sakurann, @TallTed)
-
Clean up use-cases summary w3c/vc-data-model#1166 (18 comments by @brentzundel, @msporny, @OR13, @TallTed)
-
Add language clarifying VP is short-lived w3c/vc-data-model#1164 (12 comments by @awoie, @brentzundel, @msporny, @OR13, @Sakurann, @TallTed)
-
Clarify sentence about derived credentials and presentations w3c/vc-data-model#1167 (12 comments by @awoie, @brentzundel, @dlongley, @OR13)
-
Add issue marker for extension point reservation discussion w3c/vc-data-model#1141 (10 comments by @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Add confidence method to VCDM w3c/vc-data-model#1054 (7 comments by @awoie, @brentzundel, @jandrieu, @OR13, @TallTed)
-
add vc-json-schema to vocab and context w3c/vc-data-model#1178 (6 comments by @OR13, @TallTed, @thereisnogabe)
-
Remove script breaking echidna w3c/vc-data-model#1146 (4 comments by @iherman, @msporny, @OR13, @TallTed)
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101 (1 comment by @iherman)
-
w3c/vc-jose-cose
-
8 issues opened.
-
Deprecate `vc` & `vp` ? w3c/vc-jose-cose#119, by @OR13.
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117, by @TallTed.
-
Address VP Token interop w3c/vc-jose-cose#110, by @OR13.
-
Add guidance on converting a JSON payload to vc-jwt payload w3c/vc-jose-cose#108, by @georgepadayatti.
-
Add guidance on "flat" vs "compact". w3c/vc-jose-cose#107, by @OR13.
-
Explain relationship between controller documents and JOSE headers w3c/vc-jose-cose#106, by @andresuribe87.
-
Usage of `EdDSA` algorithm w3c/vc-jose-cose#100, by @ankurdotb.
-
consider adding registered claims VC-JWT to explainer w3c/vc-jose-cose#99, by @mprorock.
-
-
12 issues closed.
-
JWT Decoding: expirationDate w3c/vc-jose-cose#7.
-
Privacy Considerations section empty w3c/vc-jose-cose#25.
-
Security Considerations section empty w3c/vc-jose-cose#26.
-
Respec warnings and errors w3c/vc-jose-cose#27.
-
Update language to align with v2 resolutions w3c/vc-jose-cose#38.
-
Replace reference to jwt.io with embedded example w3c/vc-jose-cose#46.
-
consider adding registered claims VC-JWT to explainer w3c/vc-jose-cose#99.
-
Usage of `EdDSA` algorithm w3c/vc-jose-cose#100.
-
Add guidance on converting a JSON payload to vc-jwt payload w3c/vc-jose-cose#108.
-
Verification Method type used with VC-JWT w3c/vc-jose-cose#83.
-
Use `payload` instead of `claimset` w3c/vc-jose-cose#84.
-
-
51 issues received 72 new comments.
-
Address VP Token interop w3c/vc-jose-cose#110 (8 comments by @andresuribe87, @mprorock, @OR13, @Sakurann, @TallTed)
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (3 comments by @brentzundel, @iherman, @Sakurann)
-
Explain relationship between controller documents and JOSE headers w3c/vc-jose-cose#106 (3 comments by @OR13)
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64 (2 comments by @David-Chadwick, @OR13)
-
Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. w3c/vc-jose-cose#42 (2 comments by @dlongley, @OR13)
-
Add guidance on converting a JSON payload to vc-jwt payload w3c/vc-jose-cose#108 (2 comments by @georgepadayatti, @OR13)
-
Guidance on collisions between VC property names and registered JWT claims w3c/vc-jose-cose#98 (2 comments by @OR13)
-
Security and Privacy Self-Review Questionnaire w3c/vc-jose-cose#93 (2 comments by @OR13, @selfissued)
-
No normative statement wrt. JWT encoding of `verifiableCredential` as base64url w3c/vc-jose-cose#3 (1 comment by @OR13)
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15 (1 comment by @OR13)
-
Determine whether to include content from Verifiable Credentials Implementation Guidelines w3c/vc-jose-cose#28 (1 comment by @OR13)
-
how is `kid` to be `useful to distinguish the specific key used`? w3c/vc-jose-cose#117 (1 comment by @OR13)
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66 (1 comment by @OR13)
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (1 comment by @OR13)
-
-
13 pull requests opened.
-
Clarify json ld is not a cwt claimset w3c/vc-jose-cose#120, by @OR13.
-
chore: adjust example titles, nesting, and indents w3c/vc-jose-cose#116, by @mprorock.
-
Change short name to vc-jose-cose w3c/vc-jose-cose#115, by @mprorock.
-
Add sd-jwt example w3c/vc-jose-cose#114, by @OR13.
-
chore: update pre tag indents and lack thereof w3c/vc-jose-cose#113, by @mprorock.
-
Feature/editorial intro and format w3c/vc-jose-cose#112, by @mprorock.
-
Add comments on key discovery w3c/vc-jose-cose#111, by @OR13.
-
Add guidance on header parameters w3c/vc-jose-cose#109, by @OR13.
-
Address proof requirements w3c/vc-jose-cose#105, by @OR13.
-
Improve examples w3c/vc-jose-cose#104, by @OR13.
-
Request registration of vp content type w3c/vc-jose-cose#103, by @OR13.
-
Fix conflicts introduced by editorial fixes w3c/vc-jose-cose#102, by @OR13.
-
Editorial clean up w3c/vc-jose-cose#101, by @OR13.
-
-
12 pull requests merged.
-
chore: adjust example titles, nesting, and indents w3c/vc-jose-cose#116.
-
chore: update pre tag indents and lack thereof w3c/vc-jose-cose#113.
-
Feature/editorial intro and format w3c/vc-jose-cose#112.
-
Add guidance on header parameters w3c/vc-jose-cose#109.
-
Improve examples w3c/vc-jose-cose#104.
-
Address proof requirements w3c/vc-jose-cose#105.
-
Request registration of vp content type w3c/vc-jose-cose#103.
-
Add an explainer w3c/vc-jose-cose#96.
-
Editorial clean up w3c/vc-jose-cose#101.
-
Add Internationalization Considerations section w3c/vc-jose-cose#92.
-
Add accessibility considerations w3c/vc-jose-cose#91.
-
Add example w3c/vc-jose-cose#89.
-
-
2 pull requests closed.
-
Fix conflicts introduced by editorial fixes w3c/vc-jose-cose#102.
-
Add context integrity approach for VC-JWTs w3c/vc-jose-cose#90.
-
-
15 pull requests received 206 new comments.
-
Add comments on key discovery w3c/vc-jose-cose#111 (51 comments by @andresuribe87, @brentzundel, @dlongley, @mprorock, @OR13, @TallTed)
-
Feature/editorial intro and format w3c/vc-jose-cose#112 (38 comments by @mprorock, @OR13, @selfissued, @TallTed)
-
Improve examples w3c/vc-jose-cose#104 (34 comments by @andresuribe87, @dlongley, @iherman, @mprorock, @OR13)
-
remove securing json w3c/vc-jose-cose#88 (20 comments by @alenhorvat, @brentzundel, @iherman, @mprorock, @OR13, @paulfdietrich, @peacekeeper, @Sakurann)
-
Add context integrity approach for VC-JWTs w3c/vc-jose-cose#90 (16 comments by @mprorock, @OR13, @selfissued, @TallTed)
-
Add an explainer w3c/vc-jose-cose#96 (14 comments by @andresuribe87, @mprorock, @OR13, @selfissued, @TallTed)
-
Change short name to vc-jose-cose w3c/vc-jose-cose#115 (9 comments by @andresuribe87, @brentzundel, @iherman, @mprorock, @OR13, @Sakurann, @TallTed)
-
Request registration of vp content type w3c/vc-jose-cose#103 (5 comments by @iherman, @jandrieu, @OR13)
-
Add Internationalization Considerations section w3c/vc-jose-cose#92 (4 comments by @OR13, @selfissued, @TallTed)
-
chore: update pre tag indents and lack thereof w3c/vc-jose-cose#113 (2 comments by @mprorock, @OR13)
-
w3c/vc-data-integrity
-
1 issue opened.
-
need resourceIntegrity in vocab and under w3c w3c/vc-data-integrity#193, by @mprorock.
-
-
2 issues received 9 new comments.
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (8 comments by @dlongley, @iherman, @OR13)
-
-
7 pull requests opened.
-
Fix examples and point to specifications w3c/vc-data-integrity#105, by @msporny.
-
Add related links to other specifications. Fix references. w3c/vc-data-integrity#104, by @msporny.
-
Update CODEOWNERS to remove myself as I am not an editor on this item w3c/vc-data-integrity#103, by @mprorock.
-
Cite Multibase normatively w3c/vc-data-integrity#102, by @jyasskin.
-
Update MULTIBASE Reference w3c/vc-data-integrity#101, by @OR13.
-
Change proof id from URL to URI to better match examples. w3c/vc-data-integrity#100, by @aljones15.
-
Update controller document reference w3c/vc-data-integrity#99, by @OR13.
-
-
1 pull request merged.
-
Update CODEOWNERS to remove myself as I am not an editor on this item w3c/vc-data-integrity#103.
-
-
1 pull request closed.
-
Change proof id from URL to URI to better match examples. w3c/vc-data-integrity#100.
-
-
3 pull requests received 6 new comments.
-
Update controller document reference w3c/vc-data-integrity#99 (3 comments by @dlongley, @iherman, @OR13)
-
Fix examples and point to specifications w3c/vc-data-integrity#105 (2 comments by @msporny, @TallTed)
-
Change proof id from URL to URI to better match examples. w3c/vc-data-integrity#100 (1 comment by @aljones15)
-
w3c/vc-jose-cose-test-suite
-
1 issue received 2 new comments.
-
Proposal: use did:jwk for testing dids and vc-jwt in the vc-jwt-test-suite w3c/vc-jose-cose-test-suite#10 (2 comments by @OR13)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
Use endpoints class for issuer. w3c/vc-di-ed25519signature2020-test-suite#33, by @aljones15.
-
-
1 pull request merged.
-
Use endpoints class for issuer. w3c/vc-di-ed25519signature2020-test-suite#33.
-
-
1 pull request received 3 new comments.
-
Use endpoints class for issuer. w3c/vc-di-ed25519signature2020-test-suite#33 (3 comments by @aljones15, @JSAssassin)
-
w3c/vc-di-ecdsa-test-suite
-
1 pull request opened.
-
Add issuer and interop tests. w3c/vc-di-ecdsa-test-suite#1, by @JSAssassin.
-
-
1 pull request received 2 new comments.
w3c/vc-di-eddsa-test-suite
-
1 issue opened.
-
Do we need to add support for `eddsa-2020`? w3c/vc-di-eddsa-test-suite#9, by @JSAssassin.
-
-
1 issue closed.
-
Do we need to add support for `eddsa-2020`? w3c/vc-di-eddsa-test-suite#9.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Update `data-integrity-test-suite-assertion` package to use `main` branch. w3c/vc-di-eddsa-test-suite#10, by @JSAssassin.
-
Use KEY_SEED before CLIENT_SECRET. w3c/vc-di-eddsa-test-suite#8, by @aljones15.
-
-
2 pull requests merged.
-
Update `data-integrity-test-suite-assertion` package to use `main` branch. w3c/vc-di-eddsa-test-suite#10.
-
Use KEY_SEED before CLIENT_SECRET. w3c/vc-di-eddsa-test-suite#8.
-
w3c/vc-jws-2020
-
11 issues closed.
-
Naming of work w3c/vc-jws-2020#31.
-
Re-use `proofValue` from DataIntegrityProof instead of `jws` w3c/vc-jws-2020#25.
-
Move conformance section w3c/vc-jws-2020#27.
-
Anti-pattern: Excessive algorithm agility w3c/vc-jws-2020#20.
-
Ensure all IRIs for terms are resolvable w3c/vc-jws-2020#23.
-
Restrict secp*r1 curves w3c/vc-jws-2020#16.
-
Add links to testsuite w3c/vc-jws-2020#18.
-
Define all fields of `publicKeyJwk` w3c/vc-jws-2020#3.
-
Add `@vocab` to the context w3c/vc-jws-2020#4.
-
Rename to `di-jws-2020` ? w3c/vc-jws-2020#5.
-
PROPOSAL: Host test vectors as a single json file in this repo w3c/vc-jws-2020#2.
-
-
1 pull request merged.
-
Withdraw work item w3c/vc-jws-2020#33.
-
-
1 pull request received 9 new comments.
w3c/vc-render-method
-
1 issue opened.
-
Update repo About link. w3c/vc-render-method#3, by @davidlehn.
-
-
1 pull request opened.
-
update some links from digitalbazaar to w3c-ccg w3c/vc-render-method#2, by @TallTed.
-
-
1 pull request merged.
-
update some links from digitalbazaar to w3c-ccg w3c/vc-render-method#2.
-
w3c/vc-use-cases
-
1 issue opened.
-
Chain of GS1 credentials to identify a trade item w3c/vc-use-cases#146, by @ghost.
-
-
1 issue closed.
-
Consider "dispute" as an action w3c/vc-use-cases#134.
-
-
3 issues received 7 new comments.
-
Chain of GS1 credentials to identify a trade item w3c/vc-use-cases#146 (4 comments by @brentzundel, @jandrieu)
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (2 comments by @jandrieu, @TallTed)
-
-
1 pull request opened.
-
Bona fide shopper w3c/vc-use-cases#145, by @ghost.
-
-
2 pull requests received 6 new comments.
w3c/vc-extensions
-
1 issue opened.
-
Turn this into a W3C Draft Registry w3c/vc-extensions#23, by @jyasskin.
-
-
1 issue received 1 new comment.
-
2 pull requests opened.
-
Register withdrawn work item w3c/vc-extensions#22, by @OR13.
-
register spec w3c/vc-extensions#21, by @OR13.
-
-
4 pull requests merged.
-
Add PreconditionPolicy Terms of Use extension. w3c/vc-extensions#20.
-
update vc json schema w3c/vc-extensions#19.
-
Update extension w3c/vc-extensions#18.
-
Update CODEOWNERS w3c/vc-extensions#16.
-
-
2 pull requests received 4 new comments.
-
Add "Media Type Extensions" category. w3c/vc-extensions#14 (3 comments by @iherman, @msporny, @OR13)
-
w3c/vc-data-model-2.0-test-suite
-
4 issues opened.
-
Test contains negative tests where URNs are expected to fail in place of URLs w3c/vc-data-model-2.0-test-suite#5, by @aljones15.
-
Use Chai assertions over node assert w3c/vc-data-model-2.0-test-suite#4, by @aljones15.
-
Move it2 helper to test reporter w3c/vc-data-model-2.0-test-suite#3, by @aljones15.
-
test approach for resource integrity w3c/vc-data-model-2.0-test-suite#35, by @mprorock.
-
-
3 pull requests opened.
-
Add invalid urls w3c/vc-data-model-2.0-test-suite#7, by @aljones15.
-
Lint files w3c/vc-data-model-2.0-test-suite#6, by @aljones15.
-
Add more tests w3c/vc-data-model-2.0-test-suite#1, by @clehner.
-
-
3 pull requests merged.
-
Add invalid urls w3c/vc-data-model-2.0-test-suite#7.
-
Lint files w3c/vc-data-model-2.0-test-suite#6.
-
Add more tests w3c/vc-data-model-2.0-test-suite#1.
-
-
1 pull request reopened.
-
LICENSE.md to LICENSE.md-README.md-paths. w3c/vc-data-model-2.0-test-suite#2, by @WATCHARA24MONTHON.
-
-
3 pull requests received 35 new comments.
w3c/vcalm
-
4 issues closed.
-
Multi-format credential support w3c/vcalm#332.
-
Retro-documentation efforts towards UCR documentation w3c/vcalm#180.
-
-
11 issues received 13 new comments.
-
Clarify expected use of "description" in "Initiate Exchange" w3c/vcalm#330 (3 comments by @dlongley, @msporny)
-
BbsBls sig test fixtures (valid by various W3C docs) not permitted by current OpenAPI spec w3c/vcalm#194 (1 comment by @msporny)
-
There should be a test for issue credential with a default issuer provided w3c/vcalm#274 (1 comment by @msporny)
-
Add language clarifying the security implications of the 'domain' property in DID Authentication w3c/vcalm#300 (1 comment by @msporny)
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266 (1 comment by @msporny)
-
w3c/vc-bitstring-status-list
-
5 issues opened.
-
Unify design of status lists to support multi-bit values w3c/vc-bitstring-status-list#73, by @msporny.
-
TAG Review Request -- Submitted w3c/vc-bitstring-status-list#72, by @mkhraisha.
-
Statuslist2021entry example inaccurate? w3c/vc-bitstring-status-list#71, by @fkim7.
-
update core context w3c/vc-bitstring-status-list#70, by @mprorock.
-
Are index gaps allowed? w3c/vc-bitstring-status-list#68, by @fabrii.
-
-
2 issues closed.
-
Need examples for how to handle multiple status messages w3c/vc-bitstring-status-list#66.
-
Are index gaps allowed? w3c/vc-bitstring-status-list#68.
-
-
12 issues received 17 new comments.
-
Unify design of status lists to support multi-bit values w3c/vc-bitstring-status-list#73 (5 comments by @dlongley, @mprorock, @msporny, @OR13)
-
Implementation guidelines around how StatusList2021Credential is secured/encoded. w3c/vc-bitstring-status-list#52 (1 comment by @OR13)
-
Need examples for how to handle multiple status messages w3c/vc-bitstring-status-list#66 (1 comment by @OR13)
-
-
2 pull requests opened.
-
update contexts in examples to point to v2 w3c/vc-bitstring-status-list#74, by @mprorock.
-
chore: update title and urls to contexts w3c/vc-bitstring-status-list#69, by @mprorock.
-
-
3 pull requests merged.
-
Support for multiple status codes w3c/vc-bitstring-status-list#65.
-
Add digital bazaar credential examples w3c/vc-bitstring-status-list#67.
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46.
-
-
1 pull request closed.
-
Add JSON Web Token Examples w3c/vc-bitstring-status-list#60.
-
-
5 pull requests received 115 new comments.
-
Support for multiple status codes w3c/vc-bitstring-status-list#65 (98 comments by @andresuribe87, @brentzundel, @dlongley, @iherman, @mkhraisha, @mprorock, @msporny, @OR13, @paulfdietrich, @Sakurann, @TallTed)
-
Add digital bazaar credential examples w3c/vc-bitstring-status-list#67 (3 comments by @iherman, @msporny)
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (2 comments by @iherman, @msporny)
-
w3c/vc-di-eddsa
-
2 issues closed.
-
How is `proofConfig` meant to be serialized? w3c/vc-di-eddsa#21.
-
Security Considerations: Provable Security and Ed25519 Libraries w3c/vc-di-eddsa#45.
-
-
3 issues received 11 new comments.
-
Algorithm diff's vs. full listings w3c/vc-di-eddsa#46 (6 comments by @msporny, @TallTed, @Wind4Greg)
-
-
1 pull request merged.
-
Security Considerations: Added text on Ed25519 security properties. w3c/vc-di-eddsa#47.
-
-
1 pull request received 6 new comments.
-
Security Considerations: Added text on Ed25519 security properties. w3c/vc-di-eddsa#47 (6 comments by @msporny, @TallTed)
-
w3c/vc-confidence-method
-
3 pull requests opened.
-
feat: added abstract w3c/vc-confidence-method#3, by @awoie.
-
feat: added context dummy w3c/vc-confidence-method#2, by @awoie.
-
feat: initial w3c/vc-confidence-method#1, by @awoie.
-
-
3 pull requests merged.
-
feat: added abstract w3c/vc-confidence-method#3.
-
feat: added context dummy w3c/vc-confidence-method#2.
-
feat: initial w3c/vc-confidence-method#1.
-
w3c/vc-di-ecdsa
-
2 issues closed.
-
Initial Review, Suggestions, Test Vectors... w3c/vc-di-ecdsa#4.
-
ECDSA Signature and Curve Definition/Terminology w3c/vc-di-ecdsa#8.
-
-
1 pull request opened.
-
Test vectors for ECDSA w3c/vc-di-ecdsa#13, by @Wind4Greg.
-
-
5 pull requests merged.
-
Add JCS algorithm text w3c/vc-di-ecdsa#12.
-
Test vectors for ECDSA w3c/vc-di-ecdsa#13.
-
DraftText for security Consideration Section w3c/vc-di-ecdsa#11.
-
Added missing proof canonicalization step. w3c/vc-di-ecdsa#10.
-
Update ECDSA and curve references, update curve terminoloy w3c/vc-di-ecdsa#9.
-
-
5 pull requests received 75 new comments.
-
Add JCS algorithm text w3c/vc-di-ecdsa#12 (28 comments by @dlongley, @msporny, @OR13, @TallTed, @Wind4Greg)
-
Test vectors for ECDSA w3c/vc-di-ecdsa#13 (23 comments by @dlongley, @msporny, @OR13, @TallTed, @Wind4Greg)
-
DraftText for security Consideration Section w3c/vc-di-ecdsa#11 (22 comments by @davidlehn, @dlongley, @msporny, @TallTed, @Wind4Greg)
-
Update ECDSA and curve references, update curve terminoloy w3c/vc-di-ecdsa#9 (1 comment by @msporny)
-
TR publications
-
20 documents published.
-
Verifiable Credentials JSON Schema Specification 2023 published twice as a Working Draft. History of Verifiable Credentials JSON Schema Specification 2023
-
Verifiable Credential Data Integrity 1.0 published twice as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Securing Verifiable Credentials using JSON Web Tokens published 3 times as a Working Draft. History of Securing Verifiable Credentials using JSON Web Tokens
-
BBS Cryptosuite v2023 published as a Working Draft. History of BBS Cryptosuite v2023
-
Verifiable Credentials Data Model v2.0 published 6 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
ECDSA Cryptosuite v2019 published as a Working Draft. History of ECDSA Cryptosuite v2019
-
EdDSA Cryptosuite v2022 published 3 times as a Working Draft. History of EdDSA Cryptosuite v2022
-
Verifiable Credentials JSON Schema Specification 2023 published as a First Public Working Draft. History of Verifiable Credentials JSON Schema Specification 2023
-
BBS Cryptosuite v2023 published as a First Public Working Draft. History of BBS Cryptosuite v2023
-
Past meetings
Participants
-
3 participants joined.
-
Yen-Lin Huang (Ministry of Digital Affairs, Taiwan) joined.
-
stephan baur (Kaiser Permanente) joined.
-
Greg Bernstein (W3C Invited Experts) joined.
-
-
8 participants left.
-
Charles Lehner (W3C Invited Experts) left.
-
David Ellis (Becker-Carroll) left.
-
Andrew Whitehead (Becker-Carroll) left.
-
Scott Heger (Identity Fusion Inc) left.
-
Gregory Natran (Becker-Carroll) left.
-
Bruce Levis (Becker-Carroll) left.
-
James Dzierzanowski (Kaiser Permanente) left.
-
Jeremie Miller (Ping Identity) left.
-
-
1 organization joined.
-
Ministry of Digital Affairs, Taiwan joined.
-
-
3 organizations left.
-
Identity Fusion Inc left.
-
MFX Worldwide, Inc. left.
-
Becker-Carroll left.
-
GitHub
w3c/vc-data-model
-
17 issues opened.
-
Missing security considerations on MITM, cloning etc. w3c/vc-data-model#1138, by @awoie.
-
Collusion, i.e. collaboration, between Alice and Bob w3c/vc-data-model#1136, by @Denisthemalice.
-
Add VC-JWT diagrams to core specification w3c/vc-data-model#1135, by @msporny.
-
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? w3c/vc-data-model#1134, by @OR13.
-
Make `validFrom` optional w3c/vc-data-model#1133, by @awoie.
-
Arrays of Arrays are problematic in VCDM w3c/vc-data-model#1132, by @melvincarvalho.
-
Pull out `id` from `credentialSubject`. Change `credentialSubject` to `claims`. w3c/vc-data-model#1130, by @thereisnogabe.
-
Change `credentialSubject` to `subject` w3c/vc-data-model#1128, by @OR13.
-
Address "Credential" vs "VerifiableCredential" w3c/vc-data-model#1126, by @OR13.
-
Remove reference toCredentialManagerPresentation w3c/vc-data-model#1125, by @OR13.
-
Remove reference to DocumentVerification2018 w3c/vc-data-model#1124, by @OR13.
-
Remove reference to OdrlPolicy2017 w3c/vc-data-model#1123, by @OR13.
-
Update diagrams to not use RSA, and generally be accurate w3c/vc-data-model#1121, by @OR13.
-
Update diagrams to use latest `proof` representations w3c/vc-data-model#1120, by @OR13.
-
Media Types and HTTP w3c/vc-data-model#1118, by @OR13.
-
VC Vocabulary v2.0 does not have any term definitions w3c/vc-data-model#1117, by @andresuribe87.
-
Handle predicate for confidenceMethod in JSON-LD context w3c/vc-data-model#1116, by @awoie.
-
-
14 issues closed.
-
Add spec text around utilizing JSON Schemas for VCDM objects w3c/vc-data-model#997.
-
Address `controller` ambiguity w3c/vc-data-model#915.
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931.
-
Add "Getting Started" section w3c/vc-data-model#1071.
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890.
-
Media types do not indicate securing mechanism w3c/vc-data-model#1065.
-
Verifiable Credentials Vocabulary v2.0 not contains "name" and "description" w3c/vc-data-model#1074.
-
nonTransferable Property questions w3c/vc-data-model#960.
-
Invalid definition of context in schema w3c/vc-data-model#1059.
-
Update diagrams to use latest `proof` representations w3c/vc-data-model#1120.
-
Add "Relay Attacks" to security considerations w3c/vc-data-model#1041.
-
Rewrite Proofs (Signatures) Section w3c/vc-data-model#1104.
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789.
-
Add a unique version property to the core data model w3c/vc-data-model#1046.
-
-
42 issues received 177 new comments.
-
Pull out `id` from `credentialSubject`. Change `credentialSubject` to `claims`. w3c/vc-data-model#1130 (35 comments by @andresuribe87, @David-Chadwick, @dlongley, @jandrieu, @melvincarvalho, @msporny, @OR13, @selfissued, @TallTed, @thereisnogabe)
-
Collusion, i.e. collaboration, between Alice and Bob w3c/vc-data-model#1136 (17 comments by @Denisthemalice, @dlongley, @RieksJ, @TallTed)
-
Change `credentialSubject` to `subject` w3c/vc-data-model#1128 (15 comments by @brentzundel, @jandrieu, @martyr280, @melvincarvalho, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089 (11 comments by @brentzundel, @dlongley, @iherman, @mprorock, @OR13)
-
Address "Credential" vs "VerifiableCredential" w3c/vc-data-model#1126 (10 comments by @andresuribe87, @awoie, @David-Chadwick, @dlongley, @melvincarvalho, @OR13, @TallTed)
-
Vocabulary normative, context isn't? w3c/vc-data-model#1103 (8 comments by @iherman, @melvincarvalho, @OR13, @TallTed)
-
Single Extension Point w3c/vc-data-model#1102 (6 comments by @brentzundel, @David-Chadwick, @iherman, @msporny, @OR13, @Sakurann)
-
Guidance on `application/ld+json` w3c/vc-data-model#1040 (6 comments by @brentzundel, @melvincarvalho, @OR13, @TallTed)
-
Make `validFrom` optional w3c/vc-data-model#1133 (5 comments by @awoie, @David-Chadwick, @thereisnogabe)
-
Better visualization of data model w3c/vc-data-model#1095 (4 comments by @brentzundel, @iherman, @OR13)
-
How could we deals with chain reaction revocation of VC? w3c/vc-data-model#1072 (4 comments by @awoie, @MizukiSonoko)
-
Address `controller` ambiguity w3c/vc-data-model#915 (4 comments by @brentzundel, @iherman, @mprorock, @OR13)
-
Arrays of Arrays are problematic in VCDM w3c/vc-data-model#1132 (4 comments by @davidlehn, @melvincarvalho, @TallTed)
-
Verifiable Credentials Vocabulary v2.0 not contains "name" and "description" w3c/vc-data-model#1074 (4 comments by @brentzundel, @iherman, @OR13)
-
How should we refer to the Securing specifications? w3c/vc-data-model#1105 (3 comments by @iherman, @OR13, @thereisnogabe)
-
Add "Relay Attacks" to security considerations w3c/vc-data-model#1041 (3 comments by @OR13, @TallTed)
-
Verification of multiple credential schemas w3c/vc-data-model#950 (3 comments by @andresuribe87, @iherman, @thereisnogabe)
-
Add spec text around utilizing JSON Schemas for VCDM objects w3c/vc-data-model#997 (2 comments by @thereisnogabe)
-
Handle predicate for confidenceMethod in JSON-LD context w3c/vc-data-model#1116 (2 comments by @iherman, @Sakurann)
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090 (2 comments by @iherman, @OR13)
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031 (2 comments by @brentzundel, @OR13)
-
Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? w3c/vc-data-model#1134 (1 comment by @iherman)
-
Update diagrams to not use RSA, and generally be accurate w3c/vc-data-model#1121 (1 comment by @msporny)
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931 (1 comment by @thereisnogabe)
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967 (1 comment by @msporny)
-
Update diagrams to use latest `proof` representations w3c/vc-data-model#1120 (1 comment by @TallTed)
-
VC Vocabulary v2.0 does not have any term definitions w3c/vc-data-model#1117 (1 comment by @melvincarvalho)
-
Clarify what "reserved properties might be more formally defined in future versions" means w3c/vc-data-model#1098 (1 comment by @OR13)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (1 comment by @Sakurann)
-
Add a unique version property to the core data model w3c/vc-data-model#1046 (1 comment by @thereisnogabe)
-
-
13 pull requests opened.
-
Make things easier for developers w3c/vc-data-model#1139, by @OR13.
-
Add section on schema validity w3c/vc-data-model#1137, by @thereisnogabe.
-
Attempt to add req list w3c/vc-data-model#1131, by @OR13.
-
Modernize examples in specification w3c/vc-data-model#1129, by @msporny.
-
Add issue markers w3c/vc-data-model#1127, by @OR13.
-
Add issue markers for outdated diagrams w3c/vc-data-model#1122, by @OR13.
-
Remove Blockchain w3c/vc-data-model#1119, by @OR13.
-
Mark `evidence`, `termsOfUse`, and `refreshService` extension points at risk w3c/vc-data-model#1115, by @msporny.
-
Add usage guidance related to the `id` property. w3c/vc-data-model#1114, by @msporny.
-
Remove reserved concept of `refreshService` from the spec w3c/vc-data-model#1113, by @OR13.
-
Add note to describe use of credentialschema with selective disclosure w3c/vc-data-model#1112, by @brentzundel.
-
Add "Getting Started" section. w3c/vc-data-model#1111, by @msporny.
-
Add examples v2 context and landing page w3c/vc-data-model#1110, by @msporny.
-
-
15 pull requests merged.
-
Make things easier for developers w3c/vc-data-model#1139.
-
Add section on schema validity w3c/vc-data-model#1137.
-
Modernize examples in specification w3c/vc-data-model#1129.
-
Remove Blockchain w3c/vc-data-model#1119.
-
Add usage guidance related to the `id` property. w3c/vc-data-model#1114.
-
Mark `evidence`, `termsOfUse`, and `refreshService` extension points at risk w3c/vc-data-model#1115.
-
Add note to describe use of credentialschema with selective disclosure w3c/vc-data-model#1112.
-
Add `renderMethod` as reserved extension point. w3c/vc-data-model#1108.
-
Clarify relationship bx securing mechanisms and media types w3c/vc-data-model#1107.
-
Add "Getting Started" section. w3c/vc-data-model#1111.
-
update json schema to accurately reflect context defn w3c/vc-data-model#1064.
-
Add examples v2 context and landing page w3c/vc-data-model#1110.
-
Remove non-normative base context from specification. w3c/vc-data-model#1109.
-
Clarify proof section w3c/vc-data-model#1106.
-
Add first pass at reserved properties table w3c/vc-data-model#1097.
-
-
11 pull requests closed.
-
Added presentationSchema w3c/vc-data-model#987.
-
Add issue markers for outdated diagrams w3c/vc-data-model#1122.
-
Add issue markers w3c/vc-data-model#1127.
-
Add issuer dependent term handling w3c/vc-data-model#1083.
-
Add rendering property to VC Data Model w3c/vc-data-model#1035.
-
Remove termsOfUse from v2 context w3c/vc-data-model#1093.
-
Remove evidence w3c/vc-data-model#1092.
-
Remove reserved concept of `refreshService` from the spec w3c/vc-data-model#1113.
-
Add language clarifying multiple data schemas w3c/vc-data-model#1023.
-
Remove refreshService w3c/vc-data-model#1094.
-
Remove broken links w3c/vc-data-model#1066.
-
-
1 pull request reopened.
-
Remove refreshService w3c/vc-data-model#1094, by @OR13.
-
-
31 pull requests received 306 new comments.
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101 (35 comments by @awoie, @dlongley, @iherman, @jandrieu, @m00sey, @mprorock, @msporny, @OR13, @Sakurann, @selfissued, @TallTed, @thereisnogabe)
-
Add confidence method to VCDM w3c/vc-data-model#1054 (32 comments by @awoie, @brentzundel, @David-Chadwick, @iherman, @msporny, @OR13, @TallTed)
-
Add `renderMethod` as reserved extension point. w3c/vc-data-model#1108 (28 comments by @awoie, @brentzundel, @David-Chadwick, @dlongley, @iherman, @mprorock, @msporny, @OR13, @Sakurann, @TallTed)
-
Add usage guidance related to the `id` property. w3c/vc-data-model#1114 (21 comments by @brentzundel, @dlongley, @melvincarvalho, @msporny, @TallTed)
-
Make things easier for developers w3c/vc-data-model#1139 (12 comments by @dlongley, @msporny, @OR13, @TallTed)
-
Mark `evidence`, `termsOfUse`, and `refreshService` extension points at risk w3c/vc-data-model#1115 (12 comments by @iherman, @msporny, @TallTed, @thereisnogabe)
-
Add "Getting Started" section. w3c/vc-data-model#1111 (12 comments by @andresuribe87, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Add language clarifying multiple data schemas w3c/vc-data-model#1023 (11 comments by @brentzundel, @iherman, @msporny, @OR13, @thereisnogabe)
-
Modernize examples in specification w3c/vc-data-model#1129 (10 comments by @iherman, @longpd, @msporny, @OR13)
-
Add note to describe use of credentialschema with selective disclosure w3c/vc-data-model#1112 (10 comments by @brentzundel, @iherman, @msporny, @TallTed, @thereisnogabe)
-
Clarify relationship bx securing mechanisms and media types w3c/vc-data-model#1107 (10 comments by @andresuribe87, @brentzundel, @iherman, @msporny, @OR13)
-
Added presentationSchema w3c/vc-data-model#987 (6 comments by @brentzundel, @David-Chadwick, @iherman, @OR13)
-
Media types other than vc+ld+json w3c/vc-data-model#1100 (6 comments by @awoie, @jandrieu, @m00sey, @thereisnogabe)
-
Remove DataIntegrityProof from v2 context w3c/vc-data-model#1091 (5 comments by @iherman, @m00sey, @msporny, @OR13)
-
update json schema to accurately reflect context defn w3c/vc-data-model#1064 (5 comments by @brentzundel, @iherman, @OR13, @thereisnogabe)
-
Add rendering property to VC Data Model w3c/vc-data-model#1035 (4 comments by @iherman, @msporny, @Sakurann)
-
Add examples v2 context and landing page w3c/vc-data-model#1110 (4 comments by @iherman, @msporny, @OR13, @thereisnogabe)
-
Add issue markers for outdated diagrams w3c/vc-data-model#1122 (3 comments by @brentzundel, @msporny, @OR13)
-
Remove termsOfUse from v2 context w3c/vc-data-model#1093 (3 comments by @brentzundel, @msporny, @OR13)
-
Remove reserved concept of `refreshService` from the spec w3c/vc-data-model#1113 (2 comments by @OR13, @thereisnogabe)
-
Add first pass at reserved properties table w3c/vc-data-model#1097 (2 comments by @brentzundel, @msporny)
-
Remove non-normative base context from specification. w3c/vc-data-model#1109 (1 comment by @msporny)
-
w3c/vc-di-ecdsa
-
1 issue opened.
-
ECDSA Signature and Curve Definition/Terminology w3c/vc-di-ecdsa#8, by @Wind4Greg.
-
-
1 issue received 1 new comment.
-
4 pull requests opened.
-
Add JCS algorithm text w3c/vc-di-ecdsa#12, by @Wind4Greg.
-
DraftText for security Consideration Section w3c/vc-di-ecdsa#11, by @Wind4Greg.
-
Added missing proof canonicalization step. w3c/vc-di-ecdsa#10, by @Wind4Greg.
-
Update ECDSA and curve references, update curve terminoloy w3c/vc-di-ecdsa#9, by @Wind4Greg.
-
-
1 pull request merged.
-
Use Specref FIPS ref. w3c/vc-di-ecdsa#7.
-
-
2 pull requests received 2 new comments.
w3c/vc-json-schema
-
17 issues opened.
-
Language on nesting of credential schemas when using JsonSchemaCredential w3c/vc-json-schema#159, by @thereisnogabe.
-
Add note about media types w3c/vc-json-schema#157, by @OR13.
-
Exact URL-s for the JsonSchema2023 and CredentialSchema2023 w3c/vc-json-schema#154, by @iherman.
-
Add section on i18n considerations w3c/vc-json-schema#148, by @thereisnogabe.
-
Add section on accessibility considerations w3c/vc-json-schema#147, by @thereisnogabe.
-
Add section on warning for reserved words in JSON schema versions w3c/vc-json-schema#146, by @thereisnogabe.
-
Consider removing metadata w3c/vc-json-schema#145, by @thereisnogabe.
-
Add language on interop with JSON LD, making use of @vocab w3c/vc-json-schema#144, by @thereisnogabe.
-
Add examples of validating VC-JWT and Linked Data Proof credentials w3c/vc-json-schema#143, by @thereisnogabe.
-
Support YAML schema representations w3c/vc-json-schema#142, by @thereisnogabe.
-
Add JSON Schema for the data model w3c/vc-json-schema#141, by @thereisnogabe.
-
Add a "reference" field in the schema metadata w3c/vc-json-schema#140, by @thereisnogabe.
-
Add guidance for using JSON Schemas in ZKP/Selectively Disclosable Credentials w3c/vc-json-schema#137, by @thereisnogabe.
-
Add warning for improperly formed schemes using multiple schemas w3c/vc-json-schema#136, by @thereisnogabe.
-
Getting to a REC w3c/vc-json-schema#135, by @thereisnogabe.
-
Test suite w3c/vc-json-schema#134, by @thereisnogabe.
-
Being able to normatively reference JSON Schema w3c/vc-json-schema#133, by @thereisnogabe.
-
-
12 issues closed.
-
Exact URL-s for the JsonSchema2023 and CredentialSchema2023 w3c/vc-json-schema#154.
-
Consider removing metadata w3c/vc-json-schema#145.
-
Add language on interop with JSON LD, making use of @vocab w3c/vc-json-schema#144.
-
Add to section on extensibility w3c/vc-json-schema#107.
-
Add a "reference" field in the schema metadata w3c/vc-json-schema#140.
-
Add examples for JSON-LD and JOSE Signed Schema w3c/vc-json-schema#103.
-
Add language on which version(s) of JSON Schema are supported w3c/vc-json-schema#105.
-
Add JSON Schema for the data model w3c/vc-json-schema#141.
-
Update storage guidelines w3c/vc-json-schema#126.
-
Should the non json-ld version have an `@context` w3c/vc-json-schema#7.
-
Update Drawbacks Section w3c/vc-json-schema#108.
-
Transition work item from CCG to VCWG w3c/vc-json-schema#131.
-
-
18 issues received 27 new comments.
-
Consider adding language on schema immutability w3c/vc-json-schema#120 (6 comments by @OR13, @thereisnogabe)
-
Language on nesting of credential schemas when using JsonSchemaCredential w3c/vc-json-schema#159 (4 comments by @andresuribe87, @thereisnogabe)
-
Exact URL-s for the JsonSchema2023 and CredentialSchema2023 w3c/vc-json-schema#154 (1 comment by @thereisnogabe)
-
Add section on warning for reserved words in JSON schema versions w3c/vc-json-schema#146 (1 comment by @thereisnogabe)
-
Add examples for JSON-LD and JOSE Signed Schema w3c/vc-json-schema#103 (1 comment by @thereisnogabe)
-
Add language on which version(s) of JSON Schema are supported w3c/vc-json-schema#105 (1 comment by @thereisnogabe)
-
Add language on interop with JSON LD, making use of @vocab w3c/vc-json-schema#144 (1 comment by @TallTed)
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122 (1 comment by @thereisnogabe)
-
Should the non json-ld version have an `@context` w3c/vc-json-schema#7 (1 comment by @thereisnogabe)
-
-
13 pull requests opened.
-
Add section on reserved keywords w3c/vc-json-schema#161, by @thereisnogabe.
-
fix examples to be valid json w3c/vc-json-schema#160, by @thereisnogabe.
-
Updating the auto-publish file... w3c/vc-json-schema#158, by @iherman.
-
Missed edits from 155 w3c/vc-json-schema#156, by @thereisnogabe.
-
Update FPWD from feedback w3c/vc-json-schema#155, by @thereisnogabe.
-
update proposed publication date to May 23 2023 w3c/vc-json-schema#153, by @thereisnogabe.
-
Add fully rendered FPWD doc w3c/vc-json-schema#152, by @thereisnogabe.
-
Add FPWD w3c/vc-json-schema#151, by @thereisnogabe.
-
Added myself as editor w3c/vc-json-schema#150, by @andresuribe87.
-
remove metadata; types for credential and non-credential; add issue tags w3c/vc-json-schema#149, by @thereisnogabe.
-
Remove informative RECOMMENDED w3c/vc-json-schema#139, by @thereisnogabe.
-
Added guidance on type property relationship w3c/vc-json-schema#138, by @andresuribe87.
-
Step before preparing for FPWD w3c/vc-json-schema#132, by @thereisnogabe.
-
-
12 pull requests merged.
-
fix examples to be valid json w3c/vc-json-schema#160.
-
Missed edits from 155 w3c/vc-json-schema#156.
-
Updating the auto-publish file... w3c/vc-json-schema#158.
-
Update FPWD from feedback w3c/vc-json-schema#155.
-
update proposed publication date to May 23 2023 w3c/vc-json-schema#153.
-
Add fully rendered FPWD doc w3c/vc-json-schema#152.
-
Add FPWD w3c/vc-json-schema#151.
-
remove metadata; types for credential and non-credential; add issue tags w3c/vc-json-schema#149.
-
Added myself as editor w3c/vc-json-schema#150.
-
Remove informative RECOMMENDED w3c/vc-json-schema#139.
-
Added guidance on type property relationship w3c/vc-json-schema#138.
-
Step before preparing for FPWD w3c/vc-json-schema#132.
-
-
1 pull request closed.
-
Remove version from spec w3c/vc-json-schema#125.
-
-
11 pull requests received 61 new comments.
-
Added guidance on type property relationship w3c/vc-json-schema#138 (19 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
remove metadata; types for credential and non-credential; add issue tags w3c/vc-json-schema#149 (11 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Updating the auto-publish file... w3c/vc-json-schema#158 (5 comments by @deniak, @iherman, @thereisnogabe)
-
w3c/vc-jose-cose
-
9 issues opened.
-
Guidance on collisions between VC property names and registered JWT claims w3c/vc-jose-cose#98, by @andresuribe87.
-
TAG Review Request - SUBMITTED w3c/vc-jose-cose#97, by @mprorock.
-
Internationalization Review for VC JOSE COSE w3c/vc-jose-cose#95, by @OR13.
-
Accessibility Self-Review for VC-JWT w3c/vc-jose-cose#94, by @OR13.
-
Security and Privacy Self-Review Questionnaire w3c/vc-jose-cose#93, by @OR13.
-
Use `payload` instead of `claimset` w3c/vc-jose-cose#84, by @OR13.
-
Verification Method type used with VC-JWT w3c/vc-jose-cose#83, by @PhilippGackstatter.
-
Determine if Privacy Section can be normative w3c/vc-jose-cose#82, by @mprorock.
-
Add external references to Privacy and Security sections w3c/vc-jose-cose#81, by @mprorock.
-
-
7 issues received 9 new comments.
-
Add external references to Privacy and Security sections w3c/vc-jose-cose#81 (1 comment by @mprorock)
-
10 pull requests opened.
-
Add an explainer w3c/vc-jose-cose#96, by @mprorock.
-
Add Internationalization Considerations section w3c/vc-jose-cose#92, by @mprorock.
-
Add accessibility considerations w3c/vc-jose-cose#91, by @mprorock.
-
Add context integrity approach for VC-JWTs w3c/vc-jose-cose#90, by @mprorock.
-
Add example w3c/vc-jose-cose#89, by @OR13.
-
remove securing json w3c/vc-jose-cose#88, by @mprorock.
-
Remove version 1.0 and 1.1 mappings w3c/vc-jose-cose#87, by @OR13.
-
update title of securing json-ld section w3c/vc-jose-cose#86, by @mprorock.
-
remove 1.1 w3c/vc-jose-cose#85, by @mprorock.
-
Fix spec errors w3c/vc-jose-cose#80, by @OR13.
-
-
5 pull requests merged.
-
remove 1.1 w3c/vc-jose-cose#85.
-
update title of securing json-ld section w3c/vc-jose-cose#86.
-
Feature/editorial expansions w3c/vc-jose-cose#77.
-
Fix spec errors w3c/vc-jose-cose#80.
-
Adding echidna workflow w3c/vc-jose-cose#79.
-
-
1 pull request closed.
-
Remove version 1.0 and 1.1 mappings w3c/vc-jose-cose#87.
-
-
9 pull requests received 67 new comments.
-
Feature/editorial expansions w3c/vc-jose-cose#77 (46 comments by @andresuribe87, @brentzundel, @dlongley, @iherman, @mprorock, @OR13, @TallTed)
-
Add context integrity approach for VC-JWTs w3c/vc-jose-cose#90 (9 comments by @andresuribe87, @mprorock)
-
w3c/vcalm
-
1 issue opened.
-
Microsoft calls their REST API "VC API" w3c/vcalm#342, by @OR13.
-
-
3 issues received 3 new comments.
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266 (1 comment by @dlongley)
-
Should `Content-Type` & `Accept` headers be normative when verifying or issuing credentials? w3c/vcalm#290 (1 comment by @msporny)
-
w3c/vc-bitstring-status-list
-
2 issues opened.
-
Need examples for how to handle multiple status messages w3c/vc-bitstring-status-list#66, by @mprorock.
-
Add section on expected server HTTP status codes w3c/vc-bitstring-status-list#64, by @msporny.
-
-
2 issues received 2 new comments.
-
Need examples for how to handle multiple status messages w3c/vc-bitstring-status-list#66 (1 comment by @mprorock)
-
Add section on expected server HTTP status codes w3c/vc-bitstring-status-list#64 (1 comment by @OR13)
-
-
2 pull requests opened.
-
Add digital bazaar credential examples w3c/vc-bitstring-status-list#67, by @OR13.
-
Support for multiple status codes w3c/vc-bitstring-status-list#65, by @mprorock.
-
-
3 pull requests merged.
-
Adding the echidna workflow w3c/vc-bitstring-status-list#63.
-
fix minor Readme readability issues w3c/vc-bitstring-status-list#62.
-
Fix missing close tag. w3c/vc-bitstring-status-list#61.
-
-
4 pull requests received 71 new comments.
-
Support for multiple status codes w3c/vc-bitstring-status-list#65 (45 comments by @brentzundel, @dlongley, @iherman, @mprorock, @thereisnogabe)
-
Add JSON Web Token Examples w3c/vc-bitstring-status-list#60 (12 comments by @dlongley, @iherman, @mprorock, @msporny)
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (11 comments by @dlongley, @iherman, @mprorock, @msporny, @OR13, @selfissued)
-
Add digital bazaar credential examples w3c/vc-bitstring-status-list#67 (3 comments by @mprorock, @OR13)
-
w3c/vc-data-integrity
-
3 issues opened.
-
Security and Privacy Self-Review Questionnaire w3c/vc-data-integrity#98, by @msporny.
-
Accessibility Self-Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#97, by @msporny.
-
Internationalization Review for VC Data Integrity (and vc-di-eddsa and vc-di-ecdsa) w3c/vc-data-integrity#96, by @msporny.
-
-
1 issue closed.
-
vc:proof scope w3c/vc-data-integrity#33.
-
-
2 issues received 2 new comments.
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (1 comment by @OR13)
-
2 pull requests merged.
-
Deprecate `Ed25519Signature2020` w3c/vc-data-integrity#95.
-
Added the Multikey class w3c/vc-data-integrity#93.
-
-
2 pull requests received 2 new comments.
w3c/vc-di-eddsa
-
2 issues opened.
-
Algorithm diff's vs. full listings w3c/vc-di-eddsa#46, by @msporny.
-
Security Considerations: Provable Security and Ed25519 Libraries w3c/vc-di-eddsa#45, by @Wind4Greg.
-
-
2 issues closed.
-
Context (JSON-LD) for Examples and Test Vectors w3c/vc-di-eddsa#44.
-
jcs-eddsa-2022 review w3c/vc-di-eddsa#41.
-
-
2 issues received 3 new comments.
-
Security Considerations: Provable Security and Ed25519 Libraries w3c/vc-di-eddsa#45 (2 comments by @msporny, @Wind4Greg)
-
-
1 pull request opened.
-
Security Considerations: Added text on Ed25519 security properties. w3c/vc-di-eddsa#47, by @Wind4Greg.
-
-
4 pull requests merged.
-
Update JCS to fix proof configuration. w3c/vc-di-eddsa#43.
-
Update test vectors based on new example document w3c/vc-di-eddsa#29.
-
Update Sig2020 appendix for proof canonicalization. w3c/vc-di-eddsa#42.
-
`an Ed25519`, not `a Ed25519` w3c/vc-di-eddsa#40.
-
-
3 pull requests received 18 new comments.
-
Update test vectors based on new example document w3c/vc-di-eddsa#29 (12 comments by @msporny, @TallTed, @Wind4Greg)
-
Update JCS to fix proof configuration. w3c/vc-di-eddsa#43 (4 comments by @msporny, @OR13, @Wind4Greg)
-
Update Sig2020 appendix for proof canonicalization. w3c/vc-di-eddsa#42 (2 comments by @brentzundel, @msporny)
-
w3c/vc-extensions
-
2 pull requests opened.
-
Add PreconditionPolicy Terms of Use extension. w3c/vc-extensions#20, by @MizukiSonoko.
-
update vc json schema w3c/vc-extensions#19, by @thereisnogabe.
-
w3c/vc-di-bbs
-
9 issues opened.
-
Complete FPWD w3c/vc-di-bbs#88, by @OR13.
-
Address FPWD resolution w3c/vc-di-bbs#87, by @OR13.
-
Define: Proof Configuration, Serialization, Verification (bbs-proof-2023) w3c/vc-di-bbs#85, by @OR13.
-
Hashing (bbs-proof-2023) w3c/vc-di-bbs#84, by @OR13.
-
Define: Transformation (bbs-proof-2023) w3c/vc-di-bbs#83, by @OR13.
-
Define: Verify Proof (bbs-proof-2023) w3c/vc-di-bbs#82, by @OR13.
-
Define: Add Proof (bbs-proof-2023) w3c/vc-di-bbs#81, by @OR13.
-
Use CBOR to compress `proof` w3c/vc-di-bbs#80, by @OR13.
-
Add Support For Bound Signatures w3c/vc-di-bbs#79, by @OR13.
-
-
7 issues closed.
-
Address FPWD resolution w3c/vc-di-bbs#87.
-
BbsSignatureProof2020 is broken w3c/vc-di-bbs#62.
-
Believe it is a typo in chapter 6.1.1 step 1 w3c/vc-di-bbs#65.
-
Document the rationale for the signers public key in G2 over G1 w3c/vc-di-bbs#35.
-
Use of indices may leak information w3c/vc-di-bbs#29.
-
Add support for domain proof w3c/vc-di-bbs#6.
-
-
12 issues received 19 new comments.
-
Document the rationale for the signers public key in G2 over G1 w3c/vc-di-bbs#35 (1 comment by @OR13)
-
Privacy preserving subject authentication mechanism for application with verifiable credentials w3c/vc-di-bbs#37 (1 comment by @OR13)
-
2 pull requests opened.
-
Added the echidna script w3c/vc-di-bbs#89, by @iherman.
-
-
5 pull requests merged.
-
Added the echidna script w3c/vc-di-bbs#89.
-
Full Pass w3c/vc-di-bbs#86.
-
Clean up key formats w3c/vc-di-bbs#78.
-
Fix broken links w3c/vc-di-bbs#77.
-
Remove broken proof suite from appendix w3c/vc-di-bbs#76.
-
-
4 pull requests received 7 new comments.
w3c/vc-test-suite
-
1 issue opened.
-
credentialSubject must be a set of objects that contain one or more properties w3c/vc-test-suite#130, by @TimoGlastra.
-
w3c/vc-use-cases
-
7 issues opened.
-
Request for new section 6.3 How a Verifiable Credential may be issued within a process w3c/vc-use-cases#144, by @RieksJ.
-
Update requested for section 6.2 (VC usage) w3c/vc-use-cases#143, by @RieksJ.
-
Update requested for section 6.1 (VC creation) w3c/vc-use-cases#142, by @RieksJ.
-
New user/issuer task - Provide Claim w3c/vc-use-cases#141, by @RieksJ.
-
New user/holder task - Receive and process claim request w3c/vc-use-cases#140, by @RieksJ.
-
New user/verifier task - Request Claim w3c/vc-use-cases#139, by @RieksJ.
-
New user/issuer task - Offer Claim w3c/vc-use-cases#138, by @RieksJ.
-
-
7 issues closed.
-
Repo needs CODEOWNERs w3c/vc-use-cases#132.
-
Typo: contuning education w3c/vc-use-cases#91.
-
Update User Task Image w3c/vc-use-cases#88.
-
Consistency of 5.1 v 5.2 w3c/vc-use-cases#57.
-
New section: privacy risks w3c/vc-use-cases#52.
-
New section: gap analysis w3c/vc-use-cases#51.
-
Aggregate verifiable claims w3c/vc-use-cases#37.
-
-
21 issues received 30 new comments.
-
Expand on Use Cases for Multi Party Credentials w3c/vc-use-cases#126 (4 comments by @jandrieu, @thereisnogabe)
-
Define use case(s) that requires holder binding w3c/vc-use-cases#128 (3 comments by @awoie, @jandrieu, @TallTed)
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (2 comments by @jandrieu, @RieksJ)
-
w3c/vc-use-cases#38 (1 comment by @jandrieu)
-
Do we need distinct use-cases for verification and validation? w3c/vc-use-cases#125 (1 comment by @ghost)
-
w3c/vc-use-cases#40 (1 comment by @jandrieu)
-
w3c/vc-use-cases#39 (1 comment by @jandrieu)
-
w3c/vc-use-cases#37 (1 comment by @ghost)
-
-
1 pull request received 1 new comment.
w3c/vc-jws-2020
-
1 pull request received 4 new comments.
TR publications
-
18 documents published.
-
Verifiable Credential Data Integrity 1.0 published 3 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published 8 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
EdDSA Cryptosuite v2022 published twice as a Working Draft. History of EdDSA Cryptosuite v2022
-
ECDSA Cryptosuite v2019 published as a Working Draft. History of ECDSA Cryptosuite v2019
-
Securing Verifiable Credentials using JSON Web Tokens published as a First Public Working Draft. History of Securing Verifiable Credentials using JSON Web Tokens
-
Verifiable Credentials Status List v2021 published as a First Public Working Draft. History of Verifiable Credentials Status List v2021
-
ECDSA Cryptosuite v2019 published as a First Public Working Draft. History of ECDSA Cryptosuite v2019
-
EdDSA Cryptosuite v2022 published as a First Public Working Draft. History of EdDSA Cryptosuite v2022
-
Past meetings
-
8 meetings.
Participants
-
5 participants joined.
-
Shigeya Suzuki (Keio University) joined.
-
zhilei zhang (360) joined.
-
Michael Jones (W3C Invited Experts) joined.
-
Yasushi Minoya (Sony Group Corporation) joined.
-
Hiroyuki Sano (Sony Group Corporation) joined.
-
-
6 participants left.
-
Daniel Hardman (W3C Invited Experts) left.
-
Kyle Den Hartog (W3C Invited Experts) left.
-
Snorre Lothar von Gohren Edwin (W3C Invited Experts) left.
-
Kerri Lemoie (W3C Invited Experts) left.
-
Shigeya Suzuki (Keio University) left.
-
Michael Jones (W3C Invited Experts) left.
-
-
2 organizations joined.
-
Keio University joined.
-
360 joined.
-
-
1 organization left.
-
Keio University left.
-
GitHub
w3c/vc-data-model
-
10 issues opened.
-
How should we refer to the Securing specifications? w3c/vc-data-model#1105, by @msporny.
-
Rewrite Proofs (Signatures) Section w3c/vc-data-model#1104, by @msporny.
-
Vocabulary normative, context isn't? w3c/vc-data-model#1103, by @iherman.
-
Single Extension Point w3c/vc-data-model#1102, by @David-Chadwick.
-
Clarify what "reserved properties might be more formally defined in future versions" means w3c/vc-data-model#1098, by @msporny.
-
Better visualization of data model w3c/vc-data-model#1095, by @OR13.
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090, by @OR13.
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089, by @brentzundel.
-
(Editorial) systematically adding an anchor to each property w3c/vc-data-model#1080, by @iherman.
-
Remove normative statements from vocab w3c/vc-data-model#1077, by @awoie.
-
-
32 issues closed.
-
Zero-knowledge packed binary data format w3c/vc-data-model#949.
-
more clarity around the `id` field in the VC data model w3c/vc-data-model#973.
-
Can you use WebAuthN for Presentation Holder Binding? w3c/vc-data-model#1063.
-
Does calling something "verifiable" indicate a proof somewhere of some kind associated with it w3c/vc-data-model#1060.
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893.
-
How could an issuer indicate that the VC is deliberately fake? w3c/vc-data-model#1070.
-
Potential improvements to section "5.8 Zero-Knowledge Proofs" w3c/vc-data-model#939.
-
Do we have to introduce the `Credential` class in the VCDM vocabulary? w3c/vc-data-model#1044.
-
Query on HashLinks w3c/vc-data-model#1038.
-
`nonTransferable` property in v2.0? w3c/vc-data-model#1037.
-
Clarification on when a credentialRefresh service should be used w3c/vc-data-model#1020.
-
Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data w3c/vc-data-model#1018.
-
Move the VC Extension Registry to this Working Group w3c/vc-data-model#975.
-
Proposal: Chaining VCs via links and digests w3c/vc-data-model#952.
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831.
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933.
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985.
-
Separation of Cryptographic Verification from Business Process (and Semantic) Validation w3c/vc-data-model#986.
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758.
-
Dereferencing relative to `issuer` w3c/vc-data-model#914.
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963.
-
Breaking changes to IRIs in JSON-LD Context w3c/vc-data-model#1007.
-
Broken link in 1.0 data integrity section w3c/vc-data-model#1036.
-
Protecting integrity of `@context` w3c/vc-data-model#956.
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948.
-
Define policies for directory of related work w3c/vc-data-model#909.
-
Is a verifiable credential in JSON-LD expand form valid? w3c/vc-data-model#779.
-
Forbid expanded JSON-LD in `application/credential+ld+json` w3c/vc-data-model#1024.
-
Some questions about implementation: URIs and verificationMethod w3c/vc-data-model#945.
-
-
3 issues reopened.
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758, by @iherman.
-
Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" w3c/vc-data-model#1012, by @iherman.
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985, by @iherman.
-
-
70 issues received 256 new comments.
-
Create the new role of issuee w3c/vc-data-model#942 (30 comments by @agropper, @awoie, @David-Chadwick, @iherman, @SmithSamuelM, @TallTed, @wip-abramson)
-
"bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders w3c/vc-data-model#821 (13 comments by @agropper, @awoie, @David-Chadwick, @dlongley, @jandrieu, @TallTed)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (10 comments by @awoie, @dlongley, @OR13, @RieksJ, @thereisnogabe)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (10 comments by @brentzundel, @David-Chadwick, @iherman, @Sakurann, @TallTed)
-
more clarity around the `id` field in the VC data model w3c/vc-data-model#973 (9 comments by @AFlowOfCode, @brentzundel, @iherman, @msporny, @RieksJ)
-
Breaking changes to IRIs in JSON-LD Context w3c/vc-data-model#1007 (8 comments by @iherman, @msporny, @OR13)
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988 (7 comments by @awoie, @bumblefudge, @iherman, @jandrieu)
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881 (7 comments by @brentzundel, @filip26, @iherman, @msporny, @OR13)
-
Clarification on when a credentialRefresh service should be used w3c/vc-data-model#1020 (7 comments by @brentzundel, @David-Chadwick, @iherman, @jandrieu, @Sakurann, @TallTed)
-
Add a unique version property to the core data model w3c/vc-data-model#1046 (7 comments by @dlongley, @iherman, @TallTed, @thereisnogabe)
-
Do we have to introduce the `Credential` class in the VCDM vocabulary? w3c/vc-data-model#1044 (5 comments by @brentzundel, @iherman, @msporny, @TallTed)
-
Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data w3c/vc-data-model#1018 (5 comments by @brentzundel, @iherman, @OR13, @Sakurann)
-
Potential improvements to section "5.8 Zero-Knowledge Proofs" w3c/vc-data-model#939 (5 comments by @brentzundel, @iherman, @msporny, @Sebastian-Elfors-IDnow)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (4 comments by @awoie, @msporny, @swcurran)
-
Normative guidance regarding `@context` is not clear w3c/vc-data-model#1090 (4 comments by @iherman, @msporny, @OR13)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (4 comments by @brentzundel, @iherman, @Sakurann)
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709 (4 comments by @brentzundel, @iherman, @OR13)
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985 (4 comments by @brentzundel, @iherman, @OR13)
-
Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" w3c/vc-data-model#1012 (4 comments by @iherman, @OR13, @Sakurann)
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963 (4 comments by @brentzundel, @iherman, @jimschoening1, @OR13)
-
How could we deals with chain reaction revocation of VC? w3c/vc-data-model#1072 (3 comments by @awoie, @MizukiSonoko)
-
Does calling something "verifiable" indicate a proof somewhere of some kind associated with it w3c/vc-data-model#1060 (3 comments by @brentzundel, @iherman, @TallTed)
-
Remove normative statements from vocab w3c/vc-data-model#1077 (3 comments by @andyfmiller, @awoie, @iherman)
-
Proposal: Chaining VCs via links and digests w3c/vc-data-model#952 (3 comments by @brentzundel, @iherman)
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931 (3 comments by @dlongley, @thereisnogabe)
-
Remove 3-party Issuer-Holder-Verifier diagram and replace with 2-party Raw Credential Sender-Receiver Model w3c/vc-data-model#1008 (3 comments by @brentzundel, @iherman, @OR13)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (3 comments by @iherman, @OR13)
-
Zero-knowledge packed binary data format w3c/vc-data-model#949 (3 comments by @brentzundel, @dlongley, @iherman)
-
Vocabulary normative, context isn't? w3c/vc-data-model#1103 (2 comments by @iherman, @thereisnogabe)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (2 comments by @iherman, @OR13)
-
Why does the Data Model context file define a DataIntegrityProof RDF class? w3c/vc-data-model#1089 (2 comments by @msporny, @OR13)
-
Can you use WebAuthN for Presentation Holder Binding? w3c/vc-data-model#1063 (2 comments by @brentzundel, @iherman)
-
How could an issuer indicate that the VC is deliberately fake? w3c/vc-data-model#1070 (2 comments by @brentzundel, @iherman)
-
Move the VC Extension Registry to this Working Group w3c/vc-data-model#975 (2 comments by @brentzundel)
-
Separation of Cryptographic Verification from Business Process (and Semantic) Validation w3c/vc-data-model#986 (2 comments by @brentzundel, @iherman)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (2 comments by @iherman)
-
(Editorial) systematically adding an anchor to each property w3c/vc-data-model#1080 (2 comments by @iherman, @msporny)
-
Question about verifiable presentations w3c/vc-data-model#996 (2 comments by @iherman, @stenreijers)
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009 (2 comments by @iherman, @TallTed)
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967 (2 comments by @iherman, @msporny)
-
Clarify what "reserved properties might be more formally defined in future versions" means w3c/vc-data-model#1098 (1 comment by @David-Chadwick)
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933 (1 comment by @thereisnogabe)
-
Verifiable Credentials Vocabulary v2.0 not contains "name" and "description" w3c/vc-data-model#1074 (1 comment by @iherman)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @iherman)
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948 (1 comment by @msporny)
-
Is a verifiable credential in JSON-LD expand form valid? w3c/vc-data-model#779 (1 comment by @msporny)
-
Forbid expanded JSON-LD in `application/credential+ld+json` w3c/vc-data-model#1024 (1 comment by @msporny)
-
-
24 pull requests opened.
-
Remove non-normative base context from specification. w3c/vc-data-model#1109, by @msporny.
-
Add `renderMethod` as reserved extension point. w3c/vc-data-model#1108, by @msporny.
-
Clarify relationship bx securing mechanisms and media types w3c/vc-data-model#1107, by @brentzundel.
-
Clarify proof section w3c/vc-data-model#1106, by @brentzundel.
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101, by @selfissued.
-
Media types other than vc+ld+json w3c/vc-data-model#1100, by @m00sey.
-
Mike is now independent w3c/vc-data-model#1099, by @selfissued.
-
Add first pass at reserved properties table w3c/vc-data-model#1097, by @msporny.
-
Clarify language around ZKP data format w3c/vc-data-model#1096, by @brentzundel.
-
Remove refreshService w3c/vc-data-model#1094, by @OR13.
-
Remove termsOfUse from v2 context w3c/vc-data-model#1093, by @OR13.
-
Remove evidence w3c/vc-data-model#1092, by @OR13.
-
Remove DataIntegrityProof from v2 context w3c/vc-data-model#1091, by @OR13.
-
Remove JSON section in lieu of `application/vc+ld+json`. w3c/vc-data-model#1088, by @msporny.
-
Remove section on Disputes; no one has implemented it. w3c/vc-data-model#1087, by @msporny.
-
Fix references to old and outdated specifications. w3c/vc-data-model#1086, by @msporny.
-
Update the credentialStatus example to a real world one. w3c/vc-data-model#1085, by @msporny.
-
Minor edit to ZKP section to address Issue 939 w3c/vc-data-model#1084, by @brentzundel.
-
Add issuer dependent term handling w3c/vc-data-model#1083, by @OR13.
-
Add table of reserved properties w3c/vc-data-model#1082, by @msporny.
-
Correct media type to be vc+ld+json w3c/vc-data-model#1079, by @OR13.
-
Change the domain statement of "holder" w3c/vc-data-model#1078, by @iherman.
-
Remove "holder" from "VerifiableCredential" w3c/vc-data-model#1076, by @OR13.
-
Rephrase confusing `externally linked content` w3c/vc-data-model#1075, by @TallTed.
-
-
13 pull requests merged.
-
Mike is now independent w3c/vc-data-model#1099.
-
Fix references to old and outdated specifications. w3c/vc-data-model#1086.
-
Clarify language around ZKP data format w3c/vc-data-model#1096.
-
Remove section on Disputes; no one has implemented it. w3c/vc-data-model#1087.
-
Add table of reserved properties w3c/vc-data-model#1082.
-
Remove JSON section in lieu of `application/vc+ld+json`. w3c/vc-data-model#1088.
-
Update the credentialStatus example to a real world one. w3c/vc-data-model#1085.
-
Minor edit to ZKP section to address Issue 939 w3c/vc-data-model#1084.
-
Correct media type to be vc+ld+json w3c/vc-data-model#1079.
-
Change the domain statement of "holder" w3c/vc-data-model#1078.
-
Remove "holder" from "VerifiableCredential" w3c/vc-data-model#1076.
-
Rephrase confusing `externally linked content` w3c/vc-data-model#1075.
-
Add warning related to protecting integrity of @context w3c/vc-data-model#1051.
-
-
2 pull requests closed.
-
fix name id w3c/vc-data-model#1073.
-
Add 'render' hint property to v2 context w3c/vc-data-model#1068.
-
-
30 pull requests received 313 new comments.
-
Add table of reserved properties w3c/vc-data-model#1082 (82 comments by @awoie, @brentzundel, @David-Chadwick, @davidlehn, @dlongley, @iherman, @mprorock, @msporny, @OR13, @Sakurann, @TallTed)
-
Add confidence method to VCDM w3c/vc-data-model#1054 (47 comments by @awoie, @David-Chadwick, @dlongley, @msporny, @OR13, @TallTed, @vongohren)
-
Fix references to old and outdated specifications. w3c/vc-data-model#1086 (26 comments by @dlongley, @msporny, @OR13, @Sakurann, @selfissued, @thereisnogabe)
-
Media types other than vc+ld+json w3c/vc-data-model#1100 (19 comments by @dlongley, @m00sey, @msporny, @OR13, @selfissued, @TallTed)
-
Add issuer dependent term handling w3c/vc-data-model#1083 (15 comments by @msporny, @OR13, @TallTed)
-
Add first pass at reserved properties table w3c/vc-data-model#1097 (14 comments by @awoie, @David-Chadwick, @dlongley, @iherman, @msporny, @OR13)
-
Add guidance on Representations of Verifiable Credentials w3c/vc-data-model#1101 (13 comments by @jandrieu, @msporny, @OR13, @Sakurann, @selfissued, @TallTed)
-
Remove section on Disputes; no one has implemented it. w3c/vc-data-model#1087 (11 comments by @brentzundel, @David-Chadwick, @iherman, @msporny, @TallTed)
-
Remove JSON section in lieu of `application/vc+ld+json`. w3c/vc-data-model#1088 (11 comments by @brentzundel, @msporny, @OR13, @TallTed)
-
Remove refreshService w3c/vc-data-model#1094 (9 comments by @David-Chadwick, @dlongley, @iherman, @msporny, @OR13)
-
Clarify relationship bx securing mechanisms and media types w3c/vc-data-model#1107 (7 comments by @brentzundel, @msporny, @OR13, @TallTed)
-
Remove termsOfUse from v2 context w3c/vc-data-model#1093 (6 comments by @David-Chadwick, @dlongley, @iherman, @longpd, @OR13, @TallTed)
-
Remove DataIntegrityProof from v2 context w3c/vc-data-model#1091 (5 comments by @OR13, @thereisnogabe)
-
Update the credentialStatus example to a real world one. w3c/vc-data-model#1085 (5 comments by @davidlehn, @msporny, @TallTed)
-
Add warning related to protecting integrity of @context w3c/vc-data-model#1051 (5 comments by @msporny)
-
Add `renderMethod` as reserved extension point. w3c/vc-data-model#1108 (3 comments by @davidlehn, @msporny)
-
Clarify language around ZKP data format w3c/vc-data-model#1096 (3 comments by @brentzundel, @msporny, @stenreijers)
-
update json schema to accurately reflect context defn w3c/vc-data-model#1064 (3 comments by @brentzundel, @iherman, @thereisnogabe)
-
Minor edit to ZKP section to address Issue 939 w3c/vc-data-model#1084 (2 comments by @msporny, @Sebastian-Elfors-IDnow)
-
w3c/vc-di-bbs
-
2 issues opened.
-
Need separate cryptosuite for `signature` and `proof` w3c/vc-di-bbs#75, by @OR13.
-
w3id.org links are broken after repository migration w3c/vc-di-bbs#74, by @ctomc.
-
-
12 issues closed.
-
LDP BBS+ Signatures using JSON Pointer normalization w3c/vc-di-bbs#63.
-
Define BLS signature/commitment format w3c/vc-di-bbs#2.
-
Specify the kind of base58 encoding used w3c/vc-di-bbs#15.
-
Should we switch signature format to base64url without padding? w3c/vc-di-bbs#16.
-
Signature type doesn't specify if it's the `+` version w3c/vc-di-bbs#17.
-
Security audit on this approach w3c/vc-di-bbs#27.
-
Should credential id change for derived proofs w3c/vc-di-bbs#45.
-
Remove required reveal statements from 2020 suite w3c/vc-di-bbs#50.
-
Mention the `proofValue` and `nonce` values must be base64 encoded w3c/vc-di-bbs#51.
-
Cross linked to ZKP-LD Playground w3c/vc-di-bbs#64.
-
w3id.org links are broken after repository migration w3c/vc-di-bbs#74.
-
-
21 issues received 39 new comments.
-
Blank node labels may leak information w3c/vc-di-bbs#60 (15 comments by @BasileiosKal, @dlongley, @OR13)
-
Need separate cryptosuite for `signature` and `proof` w3c/vc-di-bbs#75 (3 comments by @dlongley, @msporny, @OR13)
-
Should we switch signature format to base64url without padding? w3c/vc-di-bbs#16 (1 comment by @OR13)
-
Document the rationale for the signers public key in G2 over G1 w3c/vc-di-bbs#35 (1 comment by @OR13)
-
Privacy preserving subject authentication mechanism for application with verifiable credentials w3c/vc-di-bbs#37 (1 comment by @OR13)
-
Qualify the proofValue term definition with @type of https://w3id.org/security#multibase w3c/vc-di-bbs#42 (1 comment by @OR13)
-
Mention the `proofValue` and `nonce` values must be base64 encoded w3c/vc-di-bbs#51 (1 comment by @OR13)
-
-
5 pull requests opened.
-
Clean up key formats w3c/vc-di-bbs#78, by @OR13.
-
Fix broken links w3c/vc-di-bbs#77, by @OR13.
-
Remove broken proof suite from appendix w3c/vc-di-bbs#76, by @OR13.
-
Initial setup after owner transfer w3c/vc-di-bbs#73, by @iherman.
-
Prepare FCGS w3c/vc-di-bbs#72, by @OR13.
-
-
2 pull requests merged.
-
Initial setup after owner transfer w3c/vc-di-bbs#73.
-
Prepare FCGS w3c/vc-di-bbs#72.
-
-
3 pull requests received 11 new comments.
w3c/vc-jose-cose
-
6 issues opened.
-
Handling of "type" not clear in v2 w3c/vc-jose-cose#76, by @astanciu.
-
Interpretation of Day 3 Resolutions w3c/vc-jose-cose#73, by @OR13.
-
Update guidance for `application/vc+jwt` w3c/vc-jose-cose#72, by @OR13.
-
Update `application/vc+ld+jwt` w3c/vc-jose-cose#71, by @OR13.
-
Define how to obtain verification keys for vc-jwt w3c/vc-jose-cose#70, by @OR13.
-
Add guidance on mapping to the core data model w3c/vc-jose-cose#69, by @OR13.
-
-
6 issues received 45 new comments.
-
Interpretation of Day 3 Resolutions w3c/vc-jose-cose#73 (26 comments by @brentzundel, @dlongley, @iherman, @jandrieu, @mprorock, @msporny, @OR13, @Sakurann, @selfissued, @thereisnogabe)
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (2 comments by @iherman, @OR13)
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66 (1 comment by @OR13)
-
-
5 pull requests opened.
-
Adding echidna workflow w3c/vc-jose-cose#79, by @iherman.
-
Mike is now independent w3c/vc-jose-cose#78, by @selfissued.
-
Feature/editorial expansions w3c/vc-jose-cose#77, by @mprorock.
-
Update README.md w3c/vc-jose-cose#75, by @OR13.
-
-
4 pull requests merged.
-
Mike is now independent w3c/vc-jose-cose#78.
-
Update README.md w3c/vc-jose-cose#75.
-
FPWD w3c/vc-jose-cose#74.
-
Editorial and non editorial changes w3c/vc-jose-cose#68.
-
-
4 pull requests received 103 new comments.
-
Editorial and non editorial changes w3c/vc-jose-cose#68 (54 comments by @brentzundel, @iherman, @msporny, @OR13, @Sakurann, @TallTed)
-
Feature/editorial expansions w3c/vc-jose-cose#77 (39 comments by @brentzundel, @dlongley, @mprorock, @OR13, @Sakurann, @TallTed)
-
w3c/vc-render-method
-
1 issue opened.
-
`renderMethod` data modeling w3c/vc-render-method#1, by @davidlehn.
-
w3c/vc-use-cases
-
1 issue opened.
-
Aggregate Verifiable Claims w3c/vc-use-cases#137, by @kjetilk.
-
-
3 issues received 6 new comments.
-
1 pull request merged.
-
grammar: Avoid “comprised of” w3c/vc-use-cases#123.
-
-
1 pull request closed.
-
Use case for Holder Binding w3c/vc-use-cases#129.
-
-
2 pull requests received 9 new comments.
w3c/vc-di-eddsa
-
3 issues opened.
-
Context (JSON-LD) for Examples and Test Vectors w3c/vc-di-eddsa#44, by @Wind4Greg.
-
jcs-eddsa-2022 review w3c/vc-di-eddsa#41, by @silverpill.
-
Is Example 15 / 16 correct? w3c/vc-di-eddsa#38, by @HelgeKrueger.
-
-
3 issues closed.
-
Algorithm Completion, Fixes, and Enhancements, and Example contexts w3c/vc-di-eddsa#30.
-
Remove the outdated portions... w3c/vc-di-eddsa#32.
-
Add JCS as canonicalization scheme w3c/vc-di-eddsa#25.
-
-
7 issues received 23 new comments.
-
Is Example 15 / 16 correct? w3c/vc-di-eddsa#38 (9 comments by @HelgeKrueger, @msporny, @silverpill, @Wind4Greg)
-
Necessary adjustments to the security vocabulary w3c/vc-di-eddsa#33 (2 comments by @iherman, @msporny)
-
Algorithm Completion, Fixes, and Enhancements, and Example contexts w3c/vc-di-eddsa#30 (1 comment by @Wind4Greg)
-
-
8 pull requests opened.
-
Update JCS to fix proof configuration. w3c/vc-di-eddsa#43, by @Wind4Greg.
-
Update Sig2020 appendix for proof canonicalization. w3c/vc-di-eddsa#42, by @Wind4Greg.
-
`an Ed25519`, not `a Ed25519` w3c/vc-di-eddsa#40, by @TallTed.
-
Moved ed255... to an appendix (bis) w3c/vc-di-eddsa#39, by @iherman.
-
Fix eddsa-2022 typos. w3c/vc-di-eddsa#37, by @davidlehn.
-
Moved ed255... to an appendix w3c/vc-di-eddsa#36, by @iherman.
-
Added yml for echidna w3c/vc-di-eddsa#35, by @iherman.
-
Fix typos and formatting. w3c/vc-di-eddsa#34, by @davidlehn.
-
-
6 pull requests merged.
-
Moved ed255... to an appendix (bis) w3c/vc-di-eddsa#39.
-
Fix eddsa-2022 typos. w3c/vc-di-eddsa#37.
-
Added yml for echidna w3c/vc-di-eddsa#35.
-
Fix typos and formatting. w3c/vc-di-eddsa#34.
-
Add proof configuration canonicalization to algorithm steps w3c/vc-di-eddsa#31.
-
Add json-eddsa-2022 cryptosuite. w3c/vc-di-eddsa#26.
-
-
1 pull request closed.
-
Moved ed255... to an appendix w3c/vc-di-eddsa#36.
-
-
8 pull requests received 57 new comments.
-
Update test vectors based on new example document w3c/vc-di-eddsa#29 (35 comments by @davidlehn, @dlongley, @iherman, @msporny, @OR13, @TallTed, @Wind4Greg)
-
Update Sig2020 appendix for proof canonicalization. w3c/vc-di-eddsa#42 (6 comments by @dlongley, @iherman, @msporny, @w3cbot)
-
Update JCS to fix proof configuration. w3c/vc-di-eddsa#43 (5 comments by @davidlehn, @iherman, @TallTed, @w3cbot, @Wind4Greg)
-
Add proof configuration canonicalization to algorithm steps w3c/vc-di-eddsa#31 (1 comment by @msporny)
-
w3c/vc-data-integrity
-
2 issues received 5 new comments.
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (3 comments by @iherman, @OR13)
-
-
5 pull requests opened.
-
Deprecate `Ed25519Signature2020` w3c/vc-data-integrity#95, by @iherman.
-
Remove myself from the editors list w3c/vc-data-integrity#94, by @mprorock.
-
Added the Multikey class w3c/vc-data-integrity#93, by @iherman.
-
Remove multibase requirement from proofValue type w3c/vc-data-integrity#92, by @OR13.
-
Use Specref VC-DATA-MODEL-2.0 ref. w3c/vc-data-integrity#91, by @davidlehn.
-
-
2 pull requests merged.
-
Remove myself from the editors list w3c/vc-data-integrity#94.
-
Use Specref VC-DATA-MODEL-2.0 ref. w3c/vc-data-integrity#91.
-
-
1 pull request closed.
-
Remove multibase requirement from proofValue type w3c/vc-data-integrity#92.
-
-
4 pull requests received 21 new comments.
-
Added the Multikey class w3c/vc-data-integrity#93 (13 comments by @dlongley, @iherman, @msporny, @OR13)
-
Remove multibase requirement from proofValue type w3c/vc-data-integrity#92 (5 comments by @mprorock, @msporny, @OR13)
-
w3c/vc-bitstring-status-list
-
5 pull requests opened.
-
Adding the echidna workflow w3c/vc-bitstring-status-list#63, by @iherman.
-
fix minor Readme readability issues w3c/vc-bitstring-status-list#62, by @mkhraisha.
-
Fix missing close tag. w3c/vc-bitstring-status-list#61, by @davidlehn.
-
Add JSON Web Token Examples w3c/vc-bitstring-status-list#60, by @OR13.
-
Correct w3c id for mprorock w3c/vc-bitstring-status-list#59, by @mprorock.
-
-
1 pull request merged.
-
Correct w3c id for mprorock w3c/vc-bitstring-status-list#59.
-
-
3 pull requests received 16 new comments.
-
Add JSON Web Token Examples w3c/vc-bitstring-status-list#60 (11 comments by @dlongley, @msporny, @OR13)
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (4 comments by @mkhraisha, @OR13)
-
w3c/vc-test-suite
-
1 issue received 17 new comments.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (17 comments by @awoie, @David-Chadwick, @iherman, @OR13, @Sakurann, @TallTed)
-
w3c/vc-di-ecdsa
-
2 issues received 3 new comments.
-
3 pull requests opened.
-
Use Specref FIPS ref. w3c/vc-di-ecdsa#7, by @davidlehn.
-
Added yml for echidna w3c/vc-di-ecdsa#6, by @iherman.
-
Fix typos and formatting. w3c/vc-di-ecdsa#5, by @davidlehn.
-
-
2 pull requests merged.
-
Added yml for echidna w3c/vc-di-ecdsa#6.
-
Fix typos and formatting. w3c/vc-di-ecdsa#5.
-
w3c/vcalm
-
1 issue closed.
-
The APIs are no longer rendered in the spec w3c/vcalm#341.
-
-
5 issues received 6 new comments.
-
Why do we believe it's a good idea to return an issued credential to an internal caller? w3c/vcalm#48 (1 comment by @msporny)
-
1 pull request received 2 new comments.
w3c/vc-extensions
-
2 issues opened.
-
Rename repository to `vc-specs` before FPWD w3c/vc-extensions#17, by @msporny.
-
-
2 issues closed.
-
Define all schema validation fields in respec w3c/vc-extensions#12.
-
Add an example JSON file the "how to register" section w3c/vc-extensions#3.
-
-
4 issues received 8 new comments.
-
4 pull requests opened.
-
Update extension w3c/vc-extensions#18, by @OR13.
-
Update CODEOWNERS w3c/vc-extensions#16, by @OR13.
-
Add "Media Type Extensions" category. w3c/vc-extensions#14, by @msporny.
-
Add media type and mapping example w3c/vc-extensions#13, by @OR13.
-
-
1 pull request merged.
-
Add registration example to respec w3c/vc-extensions#10.
-
-
1 pull request closed.
-
Add media type and mapping example w3c/vc-extensions#13.
-
-
3 pull requests received 16 new comments.
w3c/vc-json-schema
-
1 issue opened.
-
Transition work item from CCG to VCWG w3c/vc-json-schema#131, by @thereisnogabe.
-
-
2 pull requests opened.
-
Initial setup w3c/vc-json-schema#130, by @iherman.
-
update status to cg final w3c/vc-json-schema#129, by @thereisnogabe.
-
-
2 pull requests merged.
-
update status to cg final w3c/vc-json-schema#129.
-
Initial setup w3c/vc-json-schema#130.
-
-
2 pull requests received 3 new comments.
TR publications
-
9 documents published.
-
Verifiable Credentials Data Model v2.0 published 6 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Verifiable Credential Data Integrity 1.0 published 3 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Past meetings
Participants
-
6 participants joined.
-
David Chadwick (W3C Invited Experts) joined.
-
Zaïda Rivai (Danube Tech GmbH) joined.
-
Kevin Griffin (GLEIF) joined.
-
Philip Feairheller (GLEIF) joined.
-
Luis Meijueiro (Fundacion CTIC) joined.
-
Pablo COCA (Fundacion CTIC) joined.
-
-
2 participants left.
-
Cihan Saglam (Danube Tech GmbH) left.
-
David Chadwick (W3C Invited Experts) left.
-
-
2 organizations joined.
-
GLEIF joined.
-
Fundacion CTIC joined.
-
GitHub
w3c/vc-use-cases
-
1 issue received 2 new comments.
-
2 pull requests opened.
-
Issue templates w3c/vc-use-cases#136, by @ghost.
-
Inclusion for Short Use Cases w3c/vc-use-cases#135, by @jandrieu.
-
-
2 pull requests merged.
-
Issue templates w3c/vc-use-cases#136.
-
Inclusion for Short Use Cases w3c/vc-use-cases#135.
-
w3c/vc-jose-cose
-
5 issues opened.
-
typ for COSE w3c/vc-jose-cose#67, by @OR13.
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66, by @iherman.
-
Why do we have a v1.1 in this specification? w3c/vc-jose-cose#65, by @David-Chadwick.
-
How to include credential metadata in vc + jwt encoding w3c/vc-jose-cose#64, by @David-Chadwick.
-
Add guidance on what to do id `proof` is present in VC-JWT w3c/vc-jose-cose#62, by @Sakurann.
-
-
1 issue closed.
-
Should we shorten `verifiable-credential+jwt` to `vc+jwt`? w3c/vc-jose-cose#45.
-
-
1 issue reopened.
-
Should we shorten `verifiable-credential+jwt` to `vc+jwt`? w3c/vc-jose-cose#45, by @brentzundel.
-
-
5 issues received 10 new comments.
-
Should we shorten `verifiable-credential+jwt` to `vc+jwt`? w3c/vc-jose-cose#45 (6 comments by @brentzundel, @OR13, @TallTed)
-
(English) references to the VCDM spec are wrong in the 1.1 section w3c/vc-jose-cose#66 (1 comment by @TallTed)
-
Replace reference to jwt.io with embedded example w3c/vc-jose-cose#46 (1 comment by @David-Chadwick)
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9 (1 comment by @David-Chadwick)
-
-
5 pull requests opened.
-
Editorial and non editorial changes w3c/vc-jose-cose#68, by @OR13.
-
add mprorock to editor list w3c/vc-jose-cose#63, by @mprorock.
-
Shorten media types w3c/vc-jose-cose#61, by @OR13.
-
A mapping proposal w3c/vc-jose-cose#60, by @brentzundel.
-
Revert shortening of media type w3c/vc-jose-cose#59, by @OR13.
-
-
4 pull requests merged.
-
add mprorock to editor list w3c/vc-jose-cose#63.
-
A mapping proposal w3c/vc-jose-cose#60.
-
Shorten media types w3c/vc-jose-cose#61.
-
Revert shortening of media type w3c/vc-jose-cose#59.
-
-
2 pull requests closed.
-
Feature/ld examples w3c/vc-jose-cose#58.
-
Add example mapping w3c/vc-jose-cose#56.
-
-
8 pull requests received 86 new comments.
-
A mapping proposal w3c/vc-jose-cose#60 (52 comments by @awoie, @brentzundel, @iherman, @mirceanis, @OR13, @TallTed)
-
Add example mapping w3c/vc-jose-cose#56 (13 comments by @brentzundel, @dlongley, @msporny, @OR13, @peacekeeper)
-
Editorial and non editorial changes w3c/vc-jose-cose#68 (10 comments by @andresuribe87, @iherman, @TallTed)
-
Guidance on securing `application/credential+ld+json` with "authorship that can be cryptographically verified." w3c/vc-jose-cose#51 (1 comment by @brentzundel)
-
w3c/vc-data-model
-
11 issues opened.
-
Verifiable Credentials Vocabulary v2.0 not contains "name" and "description" w3c/vc-data-model#1074, by @suutaku.
-
How could we deals with chain reaction revocation of VC? w3c/vc-data-model#1072, by @MizukiSonoko.
-
Add "Getting Started" section w3c/vc-data-model#1071, by @msporny.
-
How could an issuer indicate that the VC is deliberately fake? w3c/vc-data-model#1070, by @brentzundel.
-
Audience in Verifiable Presentations? w3c/vc-data-model#1069, by @nikolockenvitz.
-
Media types do not indicate securing mechanism w3c/vc-data-model#1065, by @msporny.
-
Can you use WebAuthN for Presentation Holder Binding? w3c/vc-data-model#1063, by @OR13.
-
Add references in vocabulary that link back to the VCDM document w3c/vc-data-model#1061, by @andresuribe87.
-
Does calling something "verifiable" indicate a proof somewhere of some kind associated with it w3c/vc-data-model#1060, by @mprorock.
-
Invalid definition of context in schema w3c/vc-data-model#1059, by @xaviaracil.
-
issuer dependent credentials should be a URN w3c/vc-data-model#1058, by @melvincarvalho.
-
-
4 issues closed.
-
Audience in Verifiable Presentations? w3c/vc-data-model#1069.
-
issuer dependent credentials should be a URN w3c/vc-data-model#1058.
-
Securing the VC Data Model with JOSE w3c/vc-data-model#971.
-
Replace e.g. and i.e. with internationalization friendly text w3c/vc-data-model#1025.
-
-
25 issues received 92 new comments.
-
Do we have to introduce the `Credential` class in the VCDM vocabulary? w3c/vc-data-model#1044 (23 comments by @awoie, @David-Chadwick, @dlongley, @iherman, @msporny, @OR13, @TallTed)
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031 (13 comments by @brentzundel, @dlongley, @OR13, @peacekeeper)
-
issuer dependent credentials should be a URN w3c/vc-data-model#1058 (10 comments by @iherman, @melvincarvalho, @msporny, @OR13)
-
Does calling something "verifiable" indicate a proof somewhere of some kind associated with it w3c/vc-data-model#1060 (8 comments by @awoie, @bumblefudge, @longpd, @mprorock, @OR13, @TallTed)
-
Can you use WebAuthN for Presentation Holder Binding? w3c/vc-data-model#1063 (6 comments by @awoie, @nikosft, @OR13, @Sakurann)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (4 comments by @David-Chadwick, @dhh1128, @OR13)
-
How could an issuer indicate that the VC is deliberately fake? w3c/vc-data-model#1070 (4 comments by @David-Chadwick, @mavarley, @mwherman2000, @Sakurann)
-
Define policies for directory of related work w3c/vc-data-model#909 (3 comments by @iherman, @jandrieu, @msporny)
-
Media types do not indicate securing mechanism w3c/vc-data-model#1065 (2 comments by @Sakurann, @TallTed)
-
Audience in Verifiable Presentations? w3c/vc-data-model#1069 (2 comments by @awoie, @nikolockenvitz)
-
Invalid definition of context in schema w3c/vc-data-model#1059 (2 comments by @Sakurann, @thereisnogabe)
-
Potential improvements to section "5.8 Zero-Knowledge Proofs" w3c/vc-data-model#939 (1 comment by @brentzundel)
-
Add a unique version property to the core data model w3c/vc-data-model#1046 (1 comment by @bumblefudge)
-
Forbid expanded JSON-LD in `application/credential+ld+json` w3c/vc-data-model#1024 (1 comment by @Sakurann)
-
Add references in vocabulary that link back to the VCDM document w3c/vc-data-model#1061 (1 comment by @iherman)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (1 comment by @msporny)
-
Replace e.g. and i.e. with internationalization friendly text w3c/vc-data-model#1025 (1 comment by @thereisnogabe)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (1 comment by @OR13)
-
-
9 pull requests opened.
-
fix name id w3c/vc-data-model#1073, by @suutaku.
-
Add 'render' hint property to v2 context w3c/vc-data-model#1068, by @dmitrizagidulin.
-
update codeowners to add present authors and editors w3c/vc-data-model#1067, by @thereisnogabe.
-
Remove broken links w3c/vc-data-model#1066, by @OR13.
-
update json schema to accurately reflect context defn w3c/vc-data-model#1064, by @thereisnogabe.
-
Editorial fixes to media types section. w3c/vc-data-model#1062, by @msporny.
-
Adding the "Credential" class w3c/vc-data-model#1057, by @iherman.
-
Editorial break out of definitions for clarity w3c/vc-data-model#1056, by @mprorock.
-
Add section describing use of media types w3c/vc-data-model#1055, by @mprorock.
-
-
10 pull requests merged.
-
change ZKP section w3c/vc-data-model#1030.
-
update codeowners to add present authors and editors w3c/vc-data-model#1067.
-
Restrict JSON-LD expression to compact document form. w3c/vc-data-model#1050.
-
Editorial fixes to media types section. w3c/vc-data-model#1062.
-
Add section describing use of media types w3c/vc-data-model#1055.
-
Editorial break out of definitions for clarity w3c/vc-data-model#1056.
-
Add guidance for `credential+ld+json` for `external`proof w3c/vc-data-model#1033.
-
VC.name term definition w3c/vc-data-model#1053.
-
Setting up a user dependent namespace document w3c/vc-data-model#1049.
-
Replace JsonSchemaValidator2018 (undefined) with CredentialSchema2022 w3c/vc-data-model#1042.
-
-
5 pull requests closed.
-
Adding the "Credential" class w3c/vc-data-model#1057.
-
Add normative requirements regarding media type and proof w3c/vc-data-model#1014.
-
Propose `verifiable-credential+ld+json` media type w3c/vc-data-model#1034.
-
Add presentation media type w3c/vc-data-model#1032.
-
Remove eg and ie w3c/vc-data-model#1045.
-
-
24 pull requests received 289 new comments.
-
Add confidence method to VCDM w3c/vc-data-model#1054 (48 comments by @awoie, @bumblefudge, @dlongley, @iherman, @OR13, @paulbastian, @peppelinux, @Sakurann, @TallTed, @thereisnogabe, @tplooker, @wip-abramson)
-
Add section describing use of media types w3c/vc-data-model#1055 (48 comments by @andresuribe87, @dlongley, @iherman, @jandrieu, @mprorock, @msporny, @OR13, @Sakurann, @TallTed)
-
Adding the "Credential" class w3c/vc-data-model#1057 (34 comments by @andresuribe87, @brentzundel, @iherman, @longpd, @msporny, @OR13, @TallTed)
-
update json schema to accurately reflect context defn w3c/vc-data-model#1064 (30 comments by @dlongley, @gkellogg, @iherman, @msporny, @OR13, @thereisnogabe)
-
change ZKP section w3c/vc-data-model#1030 (15 comments by @brentzundel, @David-Chadwick, @iherman, @msporny, @Sakurann, @TallTed)
-
Add normative requirements regarding media type and proof w3c/vc-data-model#1014 (15 comments by @andres, @andresuribe87, @dlongley, @iherman, @mprorock, @msporny, @OR13, @TallTed)
-
Editorial fixes to media types section. w3c/vc-data-model#1062 (12 comments by @brentzundel, @iherman, @msporny, @OR13, @Sakurann)
-
Add guidance for `credential+ld+json` for `external`proof w3c/vc-data-model#1033 (12 comments by @dlongley, @msporny, @OR13, @TallTed)
-
Add rendering property to VC Data Model w3c/vc-data-model#1035 (10 comments by @dlongley, @gobengo, @iherman, @OR13)
-
Setting up a user dependent namespace document w3c/vc-data-model#1049 (9 comments by @iherman, @melvincarvalho, @msporny, @OR13)
-
Add 'render' hint property to v2 context w3c/vc-data-model#1068 (6 comments by @Aisp-GitHub, @brentzundel, @dmitrizagidulin, @msporny)
-
Restrict JSON-LD expression to compact document form. w3c/vc-data-model#1050 (6 comments by @iherman, @msporny, @TallTed)
-
Editorial break out of definitions for clarity w3c/vc-data-model#1056 (5 comments by @brentzundel, @iherman, @mprorock, @msporny)
-
update codeowners to add present authors and editors w3c/vc-data-model#1067 (4 comments by @David-Chadwick, @msporny, @thereisnogabe)
-
Add language clarifying multiple data schemas w3c/vc-data-model#1023 (2 comments by @thereisnogabe, @tplooker)
-
Replace JsonSchemaValidator2018 (undefined) with CredentialSchema2022 w3c/vc-data-model#1042 (2 comments by @msporny, @thereisnogabe)
-
Add warning related to protecting integrity of @context w3c/vc-data-model#1051 (1 comment by @iherman)
-
w3c/vcalm
-
5 issues opened.
-
The APIs are no longer rendered in the spec w3c/vcalm#341, by @brianorwhatever.
-
Section 3.2 should refer to OID4 w3c/vcalm#537, by @Sakurann.
-
Clarify error response code design in spec w3c/vcalm#340, by @msporny.
-
updateCredentialStatus PATCH instead of POST? w3c/vcalm#339, by @nissimsan.
-
Add clarifying statements about VC API Workflows (and exchanges) w3c/vcalm#338, by @msporny.
-
-
1 issue closed.
-
List of VC API implementations? w3c/vcalm#278.
-
-
5 issues received 13 new comments.
-
Add clarifying statements about VC API Workflows (and exchanges) w3c/vcalm#338 (5 comments by @jrhender, @msporny, @TallTed)
-
Document Instance Configuration in the VC API w3c/vcalm#267 (4 comments by @dlongley, @msporny, @OR13)
-
-
3 pull requests merged.
-
Fix linting errors in OAS files. w3c/vcalm#334.
-
Remove me from CODEOWNERS w3c/vcalm#336.
-
1 pull request closed.
-
Reference error schema on error endpoints w3c/vcalm#326.
-
-
3 pull requests received 7 new comments.
-
Add verifiablePresentationRequest property to exchange initiate. w3c/vcalm#323 (1 comment by @msporny)
w3c/vc-di-eddsa
-
3 issues opened.
-
Necessary adjustments to the security vocabulary w3c/vc-di-eddsa#33, by @iherman.
-
Remove the outdated portions... w3c/vc-di-eddsa#32, by @iherman.
-
Algorithm Completion, Fixes, and Enhancements, and Example contexts w3c/vc-di-eddsa#30, by @Wind4Greg.
-
-
2 issues closed.
-
Test Vectors Don't Verify w3c/vc-di-eddsa#14.
-
Examples for Test Vector Generation w3c/vc-di-eddsa#27.
-
-
3 issues received 5 new comments.
-
Algorithm Completion, Fixes, and Enhancements, and Example contexts w3c/vc-di-eddsa#30 (2 comments by @TallTed, @Wind4Greg)
-
-
3 pull requests opened.
-
Add proof configuration canonicalization to algorithm steps w3c/vc-di-eddsa#31, by @Wind4Greg.
-
Update test vectors based on new example document w3c/vc-di-eddsa#29, by @Wind4Greg.
-
Additional Test vectors and Separation of Files w3c/vc-di-eddsa#28, by @Wind4Greg.
-
-
1 pull request merged.
-
Revised Test vectors text w3c/vc-di-eddsa#24.
-
-
1 pull request closed.
-
Additional Test vectors and Separation of Files w3c/vc-di-eddsa#28.
-
-
5 pull requests received 74 new comments.
-
Update test vectors based on new example document w3c/vc-di-eddsa#29 (39 comments by @brentzundel, @dlongley, @msporny, @OR13, @TallTed, @Wind4Greg)
-
Add json-eddsa-2022 cryptosuite. w3c/vc-di-eddsa#26 (15 comments by @iherman, @msporny, @OR13, @silverpill)
-
Additional Test vectors and Separation of Files w3c/vc-di-eddsa#28 (8 comments by @msporny, @Wind4Greg)
-
Add proof configuration canonicalization to algorithm steps w3c/vc-di-eddsa#31 (3 comments by @msporny, @w3cbot, @Wind4Greg)
-
w3c/vc-extensions
-
4 issues opened.
-
Define all schema validation fields in respec w3c/vc-extensions#12, by @OR13.
-
Multiple Maintainers w3c/vc-extensions#9, by @David-Chadwick.
-
Do we add a media types section? w3c/vc-extensions#7, by @OR13.
-
Add an example JSON file the "how to register" section w3c/vc-extensions#3, by @jandrieu.
-
-
2 issues received 6 new comments.
-
Add an example JSON file the "how to register" section w3c/vc-extensions#3 (5 comments by @jandrieu, @OR13)
-
-
7 pull requests opened.
-
Add TRAIN ToU w3c/vc-extensions#11, by @David-Chadwick.
-
Add registration example to respec w3c/vc-extensions#10, by @OR13.
-
Add OIDF IDA Evidence w3c/vc-extensions#8, by @David-Chadwick.
-
Add traceability w3c/vc-extensions#6, by @OR13.
-
Add OAS / YAML credentialSchema validator w3c/vc-extensions#5, by @OR13.
-
add credential schema 2022 w3c/vc-extensions#4, by @thereisnogabe.
-
Add 1edtech specs w3c/vc-extensions#2, by @xaviaracil.
-
-
7 pull requests merged.
-
Add TRAIN ToU w3c/vc-extensions#11.
-
Add OIDF IDA Evidence w3c/vc-extensions#8.
-
Add traceability w3c/vc-extensions#6.
-
Add OAS / YAML credentialSchema validator w3c/vc-extensions#5.
-
add credential schema 2022 w3c/vc-extensions#4.
-
Add 1edtech specs w3c/vc-extensions#2.
-
Add VC Status List 2021. w3c/vc-extensions#1.
-
-
4 pull requests received 8 new comments.
-
Add registration example to respec w3c/vc-extensions#10 (3 comments by @David-Chadwick, @msporny, @OR13)
-
w3c/vc-di-bbs
-
1 issue opened.
-
bbs/v1 schema returned 404 w3c/vc-di-bbs#71, by @suutaku.
-
-
1 issue closed.
-
bbs/v1 schema returned 404 w3c/vc-di-bbs#71.
-
-
1 issue received 9 new comments.
-
bbs/v1 schema returned 404 w3c/vc-di-bbs#71 (9 comments by @geel9, @swcurran, @tplooker, @vongohren)
-
-
1 pull request opened.
-
Update specification structure to align with latest Data Integrity specification w3c/vc-di-bbs#70, by @msporny.
-
-
1 pull request merged.
-
1 pull request received 20 new comments.
-
Update specification structure to align with latest Data Integrity specification w3c/vc-di-bbs#70 (20 comments by @David-Chadwick, @dlongley, @msporny, @OR13, @swcurran, @TallTed, @tplooker)
-
w3c/vc-data-integrity
-
2 issues opened.
-
Specify a default context if JSON-LD processing is required w3c/vc-data-integrity#88, by @msporny.
-
Potential attacks on `previousProof` and algorithmic mitigations w3c/vc-data-integrity#87, by @msporny.
-
-
3 issues received 5 new comments.
-
Potential attacks on `previousProof` and algorithmic mitigations w3c/vc-data-integrity#87 (1 comment by @msporny)
-
1 pull request opened.
-
Comments use HTML in the vocabulary.yml file w3c/vc-data-integrity#89, by @iherman.
-
-
3 pull requests merged.
-
Comments use HTML in the vocabulary.yml file w3c/vc-data-integrity#89.
-
Add algorithm for retrieving a Verification Method. w3c/vc-data-integrity#86.
-
Replace `proofChain` property with `previousProof` property. w3c/vc-data-integrity#85.
-
-
3 pull requests received 23 new comments.
-
Add algorithm for retrieving a Verification Method. w3c/vc-data-integrity#86 (17 comments by @iherman, @msporny, @OR13, @peacekeeper, @TallTed)
-
Replace `proofChain` property with `previousProof` property. w3c/vc-data-integrity#85 (5 comments by @msporny, @OR13)
-
w3c/vc-recognized-entities
-
2 issues opened.
-
Size of the lists. w3c/vc-recognized-entities#5, by @hendersonweb.
-
Outline considerations that are out of scope w3c/vc-recognized-entities#4, by @msporny.
-
-
1 issue received 3 new comments.
-
Outline considerations that are out of scope w3c/vc-recognized-entities#4 (3 comments by @bobwyman, @msporny, @RieksJ)
-
w3c/vc-di-ecdsa
-
1 issue opened.
-
Initial Review, Suggestions, Test Vectors... w3c/vc-di-ecdsa#4, by @Wind4Greg.
-
w3c/vc-jws-2020
-
1 pull request opened.
-
Withdraw work item w3c/vc-jws-2020#33, by @OR13.
-
-
1 pull request received 10 new comments.
w3c/vc-bitstring-status-list-test-suite
-
1 issue closed.
-
Update tests to support StatusList2021 type as soon as implementation is ready. w3c/vc-bitstring-status-list-test-suite#8.
-
-
1 issue received 1 new comment.
-
Update tests to support StatusList2021 type as soon as implementation is ready. w3c/vc-bitstring-status-list-test-suite#8 (1 comment by @JSAssassin)
-
w3c/vc-bitstring-status-list
-
3 pull requests merged.
-
Propose text for malicious issuers w3c/vc-bitstring-status-list#57.
-
Add validity/caching period to status list credentials. w3c/vc-bitstring-status-list#53.
-
Add section about bitstring encoding. w3c/vc-bitstring-status-list#45.
-
-
4 pull requests received 4 new comments.
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (1 comment by @msporny)
-
Add validity/caching period to status list credentials. w3c/vc-bitstring-status-list#53 (1 comment by @msporny)
-
w3c/vc-json-schema
-
1 issue received 3 new comments.
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122 (3 comments by @andresuribe87, @msporny)
-
-
1 pull request merged.
-
validity text fix w3c/vc-json-schema#124.
-
TR publications
-
5 documents published.
-
Verifiable Credential Data Integrity 1.0 published 3 times as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published twice as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Past meetings
Participants
-
5 participants joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
Devin Rousso (Block, Inc.) joined.
-
Mircea Nistor (Consensys) joined.
-
Paul Dietrich (GS1) joined.
-
Todd Snyder (GS1) joined.
-
-
6 participants left.
-
Joe Andrieu (Legendary Requirements) left.
-
Sarven Capadisli (Inrupt Inc.) left.
-
Shenole Latimer (MFX Worldwide, Inc.) left.
-
Frank Corsi (MFX Worldwide, Inc.) left.
-
Sheri Smith (MFX Worldwide, Inc.) left.
-
Aanchal Malhotra (Ripple) left.
-
-
2 organizations joined.
-
Legendary Requirements joined.
-
Consensys joined.
-
-
1 organization left.
-
Ripple left.
-
GitHub
w3c/vc-data-model
-
14 issues opened.
-
Fix media type registration language w3c/vc-data-model#1052, by @msporny.
-
Media types other than vc+ld+json w3c/vc-data-model#1048, by @Sakurann.
-
NIST defines "credential" differently w3c/vc-data-model#1047, by @OR13.
-
Add a unique version property to the core data model w3c/vc-data-model#1046, by @thereisnogabe.
-
Do we have to introduce the `Credential` class in the VCDM vocabulary? w3c/vc-data-model#1044, by @iherman.
-
Add "Relay Attacks" to security considerations w3c/vc-data-model#1041, by @OR13.
-
Guidance on `application/ld+json` w3c/vc-data-model#1040, by @OR13.
-
Query on HashLinks w3c/vc-data-model#1038, by @sumanair.
-
`nonTransferable` property in v2.0? w3c/vc-data-model#1037, by @Sakurann.
-
Broken link in 1.0 data integrity section w3c/vc-data-model#1036, by @vongohren.
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031, by @OR13.
-
Add guidance on ignoring optional fields w3c/vc-data-model#1027, by @OR13.
-
Replace e.g. and i.e. with internationalization friendly text w3c/vc-data-model#1025, by @thereisnogabe.
-
Forbid expanded JSON-LD in `application/credential+ld+json` w3c/vc-data-model#1024, by @OR13.
-
-
10 issues closed.
-
ACDC (Authentic Chained Data Containers) in VC DM 2.0 w3c/vc-data-model#895.
-
Strawman for Increasing Interop w3c/vc-data-model#972.
-
Make the usage of `@context` optional w3c/vc-data-model#947.
-
Evidence as a Related Credential w3c/vc-data-model#919.
-
Section 3.2 Credentials makes confusing statements about what a "credential" is w3c/vc-data-model#989.
-
`notTransferable` property not defined in `@context` w3c/vc-data-model#731.
-
Terminology needs to be revised w3c/vc-data-model#983.
-
Typos in v.1.1 w3c/vc-data-model#1021.
-
Clarification of the type of the "verifiableCredential" field in a VP w3c/vc-data-model#958.
-
-
51 issues received 196 new comments.
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932 (22 comments by @agropper, @dlongley, @dwaite, @iherman, @msporny, @OR13, @peacekeeper, @Sakurann, @SmithSamuelM, @thereisnogabe)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (19 comments by @agropper, @David-Chadwick, @iherman, @mwherman2000, @OR13, @RieksJ, @Sakurann)
-
Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. w3c/vc-data-model#1031 (10 comments by @brentzundel, @David-Chadwick, @mkhraisha, @OR13, @vongohren)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (10 comments by @aljones15, @brianorwhatever, @dlongley, @OR13, @TallTed)
-
Do we have to introduce the `Credential` class in the VCDM vocabulary? w3c/vc-data-model#1044 (8 comments by @andresuribe87, @dlongley, @iherman, @OR13, @TallTed)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (6 comments by @iherman, @OR13, @TallTed)
-
Define policies for directory of related work w3c/vc-data-model#909 (6 comments by @iherman, @msporny, @TallTed, @thereisnogabe)
-
Add guidance on ignoring optional fields w3c/vc-data-model#1027 (6 comments by @David-Chadwick, @dlongley, @OR13, @Sakurann)
-
Make the usage of `@context` optional w3c/vc-data-model#947 (5 comments by @iherman, @melvincarvalho, @Sakurann, @TallTed)
-
NIST defines "credential" differently w3c/vc-data-model#1047 (5 comments by @mwherman2000, @PatStLouis, @RieksJ)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (5 comments by @brownoxford, @iherman, @kimdhamilton, @msporny, @PatStLouis)
-
[Terminology] claim w3c/vc-data-model#995 (5 comments by @David-Chadwick, @jandrieu, @RieksJ, @Sakurann)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (5 comments by @David-Chadwick, @RieksJ, @Sakurann, @TallTed)
-
ACDC (Authentic Chained Data Containers) in VC DM 2.0 w3c/vc-data-model#895 (4 comments by @bumblefudge, @iherman, @jandrieu, @Sakurann)
-
Protecting integrity of `@context` w3c/vc-data-model#956 (3 comments by @iherman, @mark-moir, @msporny)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (3 comments by @RieksJ, @Sakurann)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (3 comments by @iherman, @msporny, @OR13)
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946 (3 comments by @iherman, @msporny, @OR13)
-
Evidence as a Related Credential w3c/vc-data-model#919 (3 comments by @David-Chadwick, @iherman, @thereisnogabe)
-
Clarification on when a credentialRefresh service should be used w3c/vc-data-model#1020 (3 comments by @David-Chadwick, @Sakurann, @TallTed)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (3 comments by @iherman, @Sakurann, @TallTed)
-
Define one or more media types for VCs w3c/vc-data-model#421 (3 comments by @msporny, @OR13, @StEvUgnIn)
-
Forbid expanded JSON-LD in `application/credential+ld+json` w3c/vc-data-model#1024 (3 comments by @bumblefudge, @OR13)
-
Verification of multiple credential schemas w3c/vc-data-model#950 (2 comments by @iherman, @thereisnogabe)
-
W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec w3c/vc-data-model#982 (2 comments by @Sakurann, @TallTed)
-
Add a unique version property to the core data model w3c/vc-data-model#1046 (2 comments by @bumblefudge, @thereisnogabe)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (2 comments by @David-Chadwick, @iherman)
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985 (2 comments by @iherman, @OR13)
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948 (1 comment by @msporny)
-
Is a verifiable credential in JSON-LD expand form valid? w3c/vc-data-model#779 (1 comment by @msporny)
-
Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" w3c/vc-data-model#1012 (1 comment by @paulfdietrich)
-
Specify allowed Verifier interactions with Verifiable Data Registries w3c/vc-data-model#1016 (1 comment by @Sakurann)
-
"bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders w3c/vc-data-model#821 (1 comment by @Sakurann)
-
Section 3.2 Credentials makes confusing statements about what a "credential" is w3c/vc-data-model#989 (1 comment by @Sakurann)
-
Separation of Cryptographic Verification from Business Process (and Semantic) Validation w3c/vc-data-model#986 (1 comment by @Sakurann)
-
Remove 3-party Issuer-Holder-Verifier diagram and replace with 2-party Raw Credential Sender-Receiver Model w3c/vc-data-model#1008 (1 comment by @mwherman2000)
-
Add spec text around utilizing JSON Schemas for VCDM objects w3c/vc-data-model#997 (1 comment by @thereisnogabe)
-
Clarification of the type of the "verifiableCredential" field in a VP w3c/vc-data-model#958 (1 comment by @brentzundel)
-
-
16 pull requests opened.
-
Add confidence method to VCDM w3c/vc-data-model#1054, by @awoie.
-
VC.name term definition w3c/vc-data-model#1053, by @nissimsan.
-
Add warning related to protecting integrity of @context w3c/vc-data-model#1051, by @msporny.
-
Restrict JSON-LD expression to compact document form. w3c/vc-data-model#1050, by @msporny.
-
Setting up a user dependent namespace document w3c/vc-data-model#1049, by @iherman.
-
Remove eg and ie w3c/vc-data-model#1045, by @thereisnogabe.
-
s/`MIME Media Type`/`Media Type`/ w3c/vc-data-model#1043, by @TallTed.
-
Replace JsonSchemaValidator2018 (undefined) with CredentialSchema2022 w3c/vc-data-model#1042, by @thereisnogabe.
-
Add rendering property to VC Data Model w3c/vc-data-model#1035, by @msporny.
-
Propose `verifiable-credential+ld+json` media type w3c/vc-data-model#1034, by @OR13.
-
Add guidance for `credential+ld+json` for `external`proof w3c/vc-data-model#1033, by @OR13.
-
Add presentation media type w3c/vc-data-model#1032, by @OR13.
-
change ZKP section w3c/vc-data-model#1030, by @brentzundel.
-
ignore gitignore file w3c/vc-data-model#1028, by @brentzundel.
-
Add issue to zkp section w3c/vc-data-model#1026, by @OR13.
-
Add language clarifying multiple data schemas w3c/vc-data-model#1023, by @thereisnogabe.
-
-
4 pull requests merged.
-
s/`MIME Media Type`/`Media Type`/ w3c/vc-data-model#1043.
-
ignore gitignore file w3c/vc-data-model#1028.
-
Add issue to zkp section w3c/vc-data-model#1026.
-
Typos pointed out in issue 1021 w3c/vc-data-model#1022.
-
-
1 pull request closed.
-
Remove ZKP Section w3c/vc-data-model#999.
-
-
21 pull requests received 273 new comments.
-
Add normative requirements regarding media type and proof w3c/vc-data-model#1014 (45 comments by @andresuribe87, @dlongley, @iherman, @jandrieu, @mprorock, @msporny, @mwherman2000, @OR13, @paulfdietrich, @quartzjer, @selfissued, @TallTed, @thereisnogabe)
-
Add language clarifying multiple data schemas w3c/vc-data-model#1023 (45 comments by @aphillips, @brianorwhatever, @David-Chadwick, @iherman, @msporny, @OR13, @TallTed, @thereisnogabe)
-
Add rendering property to VC Data Model w3c/vc-data-model#1035 (29 comments by @dcrousso, @dlongley, @iherman, @lemoustachiste, @msporny, @OR13, @TallTed)
-
Add confidence method to VCDM w3c/vc-data-model#1054 (20 comments by @awoie, @dlongley, @OR13, @Sakurann, @TallTed, @thereisnogabe)
-
Add presentation media type w3c/vc-data-model#1032 (17 comments by @iherman, @msporny, @OR13, @Sakurann, @selfissued, @TallTed)
-
change ZKP section w3c/vc-data-model#1030 (16 comments by @brentzundel, @dlongley, @iherman, @msporny, @quartzjer, @Sakurann, @TallTed)
-
Remove eg and ie w3c/vc-data-model#1045 (14 comments by @aphillips, @iherman, @msporny, @peacekeeper, @TallTed, @thereisnogabe)
-
Propose `verifiable-credential+ld+json` media type w3c/vc-data-model#1034 (11 comments by @iherman, @msporny, @OR13, @TallTed)
-
Restrict JSON-LD expression to compact document form. w3c/vc-data-model#1050 (11 comments by @msporny, @OR13, @TallTed)
-
Add warning related to protecting integrity of @context w3c/vc-data-model#1051 (9 comments by @dlongley, @mark-moir, @OR13, @TallTed)
-
Add issue to zkp section w3c/vc-data-model#1026 (8 comments by @brentzundel, @iherman, @msporny, @OR13, @Sakurann)
-
Added presentationSchema w3c/vc-data-model#987 (7 comments by @David-Chadwick, @iherman, @msporny, @OR13)
-
VC.name term definition w3c/vc-data-model#1053 (4 comments by @jandrieu, @nissimsan, @OR13, @w3cbot)
-
Setting up a user dependent namespace document w3c/vc-data-model#1049 (4 comments by @iherman, @TallTed)
-
Typos pointed out in issue 1021 w3c/vc-data-model#1022 (4 comments by @bumblefudge, @iherman, @msporny)
-
Replace JsonSchemaValidator2018 (undefined) with CredentialSchema2022 w3c/vc-data-model#1042 (3 comments by @msporny, @thereisnogabe)
-
w3c/vc-data-integrity
-
5 issues opened.
-
How to use cryptographic suites w3c/vc-data-integrity#84, by @silverpill.
-
NIST defines data integrity differently w3c/vc-data-integrity#83, by @OR13.
-
Add at least one unsigned properties w3c/vc-data-integrity#90, by @jandrieu.
-
Apply guidance from RCH WG on processing poisoned graphs w3c/vc-data-integrity#82, by @OR13.
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107, by @OR13.
-
-
13 issues closed.
-
Ambiguity resulting from signature -> proof rename w3c/vc-data-integrity#2.
-
Add language about verificationMethod representation w3c/vc-data-integrity#25.
-
Link of ZCAP is 404 w3c/vc-data-integrity#31.
-
Proof Type w3c/vc-data-integrity#28.
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#12.
-
[Terminology] Definition of a linked data document is not discernable w3c/vc-data-integrity#13.
-
LD-Proofs v LD-Signatures w3c/vc-data-integrity#5.
-
Examples of the "domain" field in use? w3c/vc-data-integrity#15.
-
Use cases for RsaSignatureAuthentication2018 / authentication suites w3c/vc-data-integrity#17.
-
Specifying that input document must be framed or compacted in algorithm? w3c/vc-data-integrity#20.
-
Should the verification algorithm recursively check embedded objects? w3c/vc-data-integrity#21.
-
Storing information on whether a child object is referenced by id or included recursively w3c/vc-data-integrity#22.
-
Mark as Deprecated or Move to CCG w3c/vc-data-integrity#9.
-
-
2 issues reopened.
-
either nonce or challenge is redundant w3c/vc-data-integrity#30, by @awoie.
-
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? w3c/vc-data-integrity#14, by @msporny.
-
-
29 issues received 53 new comments.
-
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? w3c/vc-data-integrity#14 (6 comments by @msporny, @mwherman2000)
-
Apply guidance from RCH WG on processing poisoned graphs w3c/vc-data-integrity#82 (5 comments by @dlongley, @OR13, @quartzjer)
-
Add at least one unsigned properties w3c/vc-data-integrity#90 (4 comments by @dlongley, @jandrieu, @RieksJ)
-
Ambiguity resulting from signature -> proof rename w3c/vc-data-integrity#2 (2 comments by @kimdhamilton, @msporny)
-
Add language about verificationMethod representation w3c/vc-data-integrity#25 (2 comments by @msporny, @OR13)
-
Describe how JSON-LD framing is used with Selective Disclosure w3c/vc-data-integrity#107 (2 comments by @OR13, @Sakurann)
-
serialization, canonicalized values and normalized datasets w3c/vc-data-integrity#11 (2 comments by @gkellogg, @msporny)
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (1 comment by @dlongley)
-
URLs in current editors draft all seem to be invalid w3c/vc-data-integrity#37 (1 comment by @msporny)
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#12 (1 comment by @msporny)
-
[Terminology] Definition of a linked data document is not discernable w3c/vc-data-integrity#13 (1 comment by @msporny)
-
Example that demonstrates input(s) and what gets fed to the signature algorithms? w3c/vc-data-integrity#19 (1 comment by @msporny)
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18 (1 comment by @msporny)
-
Use cases for RsaSignatureAuthentication2018 / authentication suites w3c/vc-data-integrity#17 (1 comment by @msporny)
-
Specifying that input document must be framed or compacted in algorithm? w3c/vc-data-integrity#20 (1 comment by @msporny)
-
Should the verification algorithm recursively check embedded objects? w3c/vc-data-integrity#21 (1 comment by @msporny)
-
Storing information on whether a child object is referenced by id or included recursively w3c/vc-data-integrity#22 (1 comment by @msporny)
-
2 pull requests opened.
-
Add algorithm for retrieving a Verification Method. w3c/vc-data-integrity#86, by @msporny.
-
Replace `proofChain` property with `previousProof` property. w3c/vc-data-integrity#85, by @msporny.
-
-
2 pull requests received 21 new comments.
-
Add algorithm for retrieving a Verification Method. w3c/vc-data-integrity#86 (8 comments by @dlongley, @msporny, @OR13, @peacekeeper, @TallTed)
w3c/vc-di-eddsa
-
2 issues opened.
-
Examples for Test Vector Generation w3c/vc-di-eddsa#27, by @Wind4Greg.
-
Add JCS as canonicalization scheme w3c/vc-di-eddsa#25, by @msporny.
-
-
1 issue closed.
-
Review on 2023-01-26 by Greg Bernstein, Test Vector Suggestions w3c/vc-di-eddsa#22.
-
-
2 issues received 6 new comments.
-
How is `proofConfig` meant to be serialized? w3c/vc-di-eddsa#21 (4 comments by @msporny, @olivereanderson, @Wind4Greg)
-
-
1 pull request opened.
-
Add json-eddsa-2022 cryptosuite. w3c/vc-di-eddsa#26, by @msporny.
-
-
2 pull requests received 14 new comments.
-
Revised Test vectors text w3c/vc-di-eddsa#24 (12 comments by @dlongley, @iherman, @msporny, @TallTed, @Wind4Greg)
-
w3c/vc-jose-cose
-
7 issues opened.
-
Change `typ` values for JSON-LD claim sets? w3c/vc-jose-cose#57, by @OR13.
-
F2F mapping converstation w3c/vc-jose-cose#53, by @OR13.
-
Describe how `cnf` is allowed to be used for "binding" w3c/vc-jose-cose#52, by @OR13.
-
Change spec name? w3c/vc-jose-cose#49, by @OR13.
-
Provide guidance on use of `cty` in JOSE / COSE w3c/vc-jose-cose#47, by @OR13.
-
Replace reference to jwt.io with embedded example w3c/vc-jose-cose#46, by @OR13.
-
Should we shorten `verifiable-credential+jwt` to `vc+jwt`? w3c/vc-jose-cose#45, by @OR13.
-
-
1 issue closed.
-
Looser restrictions on the JOSE header `typ` w3c/vc-jose-cose#5.
-
-
8 issues received 29 new comments.
-
Should we shorten `verifiable-credential+jwt` to `vc+jwt`? w3c/vc-jose-cose#45 (13 comments by @dlongley, @OR13, @selfissued, @TallTed)
-
Provide guidance on use of `cty` in JOSE / COSE w3c/vc-jose-cose#47 (7 comments by @dlongley, @OR13)
-
-
7 pull requests opened.
-
Feature/ld examples w3c/vc-jose-cose#58, by @mprorock.
-
Add example mapping w3c/vc-jose-cose#56, by @OR13.
-
Editorial cleanup w3c/vc-jose-cose#55, by @OR13.
-
Feature: vc-jwt context w3c/vc-jose-cose#54, by @mprorock.
-
Shorten media type closes #45 w3c/vc-jose-cose#50, by @OR13.
-
Refine vp-jwt-1.1 production rules w3c/vc-jose-cose#48, by @OR13.
-
-
5 pull requests merged.
-
Editorial cleanup w3c/vc-jose-cose#55.
-
Shorten media type closes #45 w3c/vc-jose-cose#50.
-
Refine vp-jwt-1.1 production rules w3c/vc-jose-cose#48.
-
Add version 2 w3c/vc-jose-cose#44.
-
-
1 pull request closed.
-
Feature: vc-jwt context w3c/vc-jose-cose#54.
-
-
8 pull requests received 91 new comments.
-
Add version 2 w3c/vc-jose-cose#44 (29 comments by @bc-pi, @dhh1128, @dlongley, @iherman, @letmaik, @msporny, @OR13, @SmithSamuelM, @TallTed)
-
Feature: vc-jwt context w3c/vc-jose-cose#54 (15 comments by @bumblefudge, @mkhraisha, @mprorock, @OR13, @TallTed)
-
Shorten media type closes #45 w3c/vc-jose-cose#50 (6 comments by @dlongley, @iherman, @mkhraisha, @OR13, @TallTed)
-
w3c/vc-json-schema
-
3 issues opened.
-
Update storage guidelines w3c/vc-json-schema#126, by @andresuribe87.
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122, by @thereisnogabe.
-
Support multiple schemas applying to different portions of a VC w3c/vc-json-schema#121, by @thereisnogabe.
-
-
7 issues closed.
-
Document usage flows w3c/vc-json-schema#14.
-
Why do we need two schema system/languages? w3c/vc-json-schema#16.
-
JSON-LD cannot validate, only JSON Schema can w3c/vc-json-schema#88.
-
Support multiple schemas applying to different portions of a VC w3c/vc-json-schema#121.
-
Summary of "forks" from VC spec w3c/vc-json-schema#18.
-
Should bikeshed be used to define industry specific contexts w3c/vc-json-schema#21.
-
How to use Credential Schemas in the VCDM? w3c/vc-json-schema#104.
-
-
13 issues received 26 new comments.
-
Support multiple schemas applying to different portions of a VC w3c/vc-json-schema#121 (11 comments by @andresuribe87, @David-Chadwick, @thereisnogabe)
-
How can JSON Schemas be used with JSON-LD? Why is this useful? w3c/vc-json-schema#122 (2 comments by @andresuribe87, @thereisnogabe)
-
Should the non json-ld version have an `@context` w3c/vc-json-schema#7 (1 comment by @thereisnogabe)
-
Example of the credentialSchema.id resolution to schema w3c/vc-json-schema#19 (1 comment by @thereisnogabe)
-
Add examples for JSON-LD and JOSE Signed Schema w3c/vc-json-schema#103 (1 comment by @thereisnogabe)
-
Consider adding language on schema immutability w3c/vc-json-schema#120 (1 comment by @thereisnogabe)
-
-
3 pull requests opened.
-
Remove version from spec w3c/vc-json-schema#125, by @andresuribe87.
-
validity text fix w3c/vc-json-schema#124, by @thereisnogabe.
-
add multiple schema examples; tag issues w3c/vc-json-schema#123, by @thereisnogabe.
-
-
1 pull request merged.
-
add multiple schema examples; tag issues w3c/vc-json-schema#123.
-
-
4 pull requests received 27 new comments.
-
add multiple schema examples; tag issues w3c/vc-json-schema#123 (15 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
Remove version from spec w3c/vc-json-schema#125 (7 comments by @andresuribe87, @TallTed, @thereisnogabe)
-
w3c/vcalm
-
1 issue opened.
-
Can issue credential request credential proof property w3c/vcalm#337, by @acarnagey.
-
-
1 issue closed.
-
404 HTTP error response status w3c/vcalm#305.
-
-
3 issues received 13 new comments.
-
Can issue credential request credential proof property w3c/vcalm#337 (8 comments by @dlongley, @OR13)
-
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.) w3c/vcalm#285 (4 comments by @kezike, @msporny, @PatStLouis)
-
-
1 pull request opened.
-
Remove me from CODEOWNERS w3c/vcalm#336, by @peacekeeper.
-
-
1 pull request received 2 new comments.
w3c/vc-use-cases
-
3 issues opened.
-
Consider "dispute" as an action w3c/vc-use-cases#134, by @jandrieu.
-
Add language around "Amend" actions w3c/vc-use-cases#133, by @msporny.
-
Repo needs CODEOWNERs w3c/vc-use-cases#132, by @OR13.
-
-
7 issues received 19 new comments.
-
Expand on Use Cases for Multi Party Credentials w3c/vc-use-cases#126 (3 comments by @iherman, @jandrieu, @thereisnogabe)
-
Section 4 diagram includes "amend claim" w3c/vc-use-cases#124 (3 comments by @iherman, @OR13, @Sakurann)
-
2 pull requests received 34 new comments.
-
Use case for Holder Binding w3c/vc-use-cases#129 (33 comments by @ghost, @justAnIdentity, @Sakurann, @TallTed, @vongohren)
-
w3c/vc-bitstring-status-list
-
6 issues opened.
-
Encoded list in Base64 or Base64Url? w3c/vc-bitstring-status-list#58, by @amondit.
-
Implementation Considerations w3c/vc-bitstring-status-list#56, by @shigeya.
-
Add guidance on rfc3642 w3c/vc-bitstring-status-list#55, by @OR13.
-
How to understand herd privacy in using bit string? w3c/vc-bitstring-status-list#54, by @echenknox.
-
Implementation guidelines around how StatusList2021Credential is secured/encoded. w3c/vc-bitstring-status-list#52, by @Sakurann.
-
Clarify that `StatusList2021Credential` must be VC-DATA-MODEL (v1.1) w3c/vc-bitstring-status-list#51, by @Sakurann.
-
-
11 issues received 26 new comments.
-
Define priority for a single credential with multiple statuses w3c/vc-bitstring-status-list#37 (13 comments by @dlongley, @echenknox, @OR13)
-
RevocationList2021 or RevocationList2021Status w3c/vc-bitstring-status-list#11 (2 comments by @iherman, @Sakurann)
-
Preventing multiple single-credential status lists per issuer w3c/vc-bitstring-status-list#6 (1 comment by @iherman)
-
Is it possible to support multiple purposes? w3c/vc-bitstring-status-list#47 (1 comment by @dlongley)
-
Would like multiple status to be capable of representation in a status list w3c/vc-bitstring-status-list#42 (1 comment by @dlongley)
-
Document design characteristics why "StatusList2021Credential" is a VC w3c/vc-bitstring-status-list#48 (1 comment by @dlongley)
-
-
2 pull requests opened.
-
Propose text for malicious issuers w3c/vc-bitstring-status-list#57, by @OR13.
-
Add validity/caching period to status list credentials. w3c/vc-bitstring-status-list#53, by @msporny.
-
-
4 pull requests received 36 new comments.
-
Add section about bitstring encoding. w3c/vc-bitstring-status-list#45 (22 comments by @dlongley, @dwight-holman, @iherman, @msporny, @OR13, @TallTed)
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (7 comments by @dlongley, @iherman, @msporny)
-
Add validity/caching period to status list credentials. w3c/vc-bitstring-status-list#53 (2 comments by @iherman, @TallTed)
-
w3c/vc-di-bbs
-
2 issues received 3 new comments.
-
Should we switch signature format to base64url without padding? w3c/vc-di-bbs#16 (2 comments by @kdenhartog, @thereisnogabe)
-
w3c/vc-extensions
-
1 pull request opened.
-
Add VC Status List 2021. w3c/vc-extensions#1, by @msporny.
-
w3c/vc-di-ed25519signature2020-test-suite
-
2 pull requests opened.
-
Lint vc generator w3c/vc-di-ed25519signature2020-test-suite#32, by @aljones15.
-
Test Fixes: throw on issuer error, Remove extraneous VC type, swap env variables. w3c/vc-di-ed25519signature2020-test-suite#31, by @aljones15.
-
-
2 pull requests merged.
-
Lint vc generator w3c/vc-di-ed25519signature2020-test-suite#32.
-
Test Fixes: throw on issuer error, Remove extraneous VC type, swap env variables. w3c/vc-di-ed25519signature2020-test-suite#31.
-
-
2 pull requests received 6 new comments.
-
Lint vc generator w3c/vc-di-ed25519signature2020-test-suite#32 (5 comments by @aljones15, @dlongley)
-
Test Fixes: throw on issuer error, Remove extraneous VC type, swap env variables. w3c/vc-di-ed25519signature2020-test-suite#31 (1 comment by @aljones15)
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request opened.
-
Use latest `@digitalbazaar/vc-status-list@7.0` w3c/vc-bitstring-status-list-test-suite#22, by @JSAssassin.
-
-
1 pull request merged.
-
Use latest `@digitalbazaar/vc-status-list@7.0` w3c/vc-bitstring-status-list-test-suite#22.
-
-
1 pull request received 1 new comment.
-
Use latest `@digitalbazaar/vc-status-list@7.0` w3c/vc-bitstring-status-list-test-suite#22 (1 comment by @JSAssassin)
-
w3c/vc-imp-guide
-
4 issues received 11 new comments.
-
Verifiers MUST NOT trust visual indicators on apps they do not control w3c/vc-imp-guide#66 (6 comments by @agropper, @iherman, @OR13, @TallTed)
-
Be suspicious of QR Code flows that don't also check digital signatures at some point w3c/vc-imp-guide#67 (2 comments by @iherman, @Sakurann)
-
Clarification needed regarding "the subject of a VC" w3c/vc-imp-guide#70 (2 comments by @awoie, @OR13)
-
Ensure that credential storage should be encrypted using strong entropy sources w3c/vc-imp-guide#65 (1 comment by @iherman)
-
-
1 pull request merged.
-
Fix a broken link to a paper w3c/vc-imp-guide#60.
-
-
2 pull requests received 2 new comments.
-
[WIP] added example schema.json for vc (resolves #1) w3c/vc-imp-guide#17 (1 comment by @brentzundel)
-
TR publications
-
8 documents published.
-
Verifiable Credential Data Integrity 1.0 published as a Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Verifiable Credentials Data Model v2.0 published 5 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
JSON Web Signatures for Data Integrity Proofs published twice as a Working Draft. History of JSON Web Signatures for Data Integrity Proofs
-
Past meetings
Participants
-
2 participants joined.
-
Arjen van Veen (Spruce Systems, Inc.) joined.
-
Kerri Lemoie (W3C Invited Experts) joined.
-
-
1 participant left.
-
Robin Berjon (The New York Times) left.
-
GitHub
w3c/vc-bitstring-status-list
-
13 issues opened.
-
Versioning w3c/vc-bitstring-status-list#50, by @Sakurann.
-
Document design characteristics why "StatusList2021Entry" is signed. w3c/vc-bitstring-status-list#49, by @Sakurann.
-
Document design characteristics why "StatusList2021Credential" is a VC w3c/vc-bitstring-status-list#48, by @Sakurann.
-
Is it possible to support multiple purposes? w3c/vc-bitstring-status-list#47, by @echenknox.
-
clarify protocol for retrieval of a status list w3c/vc-bitstring-status-list#44, by @mprorock.
-
Trusted origins, list issuers vs hosts w3c/vc-bitstring-status-list#43, by @OR13.
-
Would like multiple status to be capable of representation in a status list w3c/vc-bitstring-status-list#42, by @mprorock.
-
Randomization w3c/vc-bitstring-status-list#41, by @OR13.
-
Should "noise" be added during "updates" w3c/vc-bitstring-status-list#40, by @OR13.
-
Verification should fail for revocable credentials for status list that cannot be deferenced w3c/vc-bitstring-status-list#39, by @BenjaminMoe.
-
Define TTL and caching behavior for lists w3c/vc-bitstring-status-list#38, by @OR13.
-
Define priority for a single credential with multiple statuses w3c/vc-bitstring-status-list#37, by @OR13.
-
Specify bit order for status list w3c/vc-bitstring-status-list#36, by @msporny.
-
-
5 issues closed.
-
RevocationList2021 or RevocationList2021Status w3c/vc-bitstring-status-list#11.
-
Context about how this differs from 2020-rl w3c/vc-bitstring-status-list#3.
-
Bitstring endianness w3c/vc-bitstring-status-list#8.
-
Context URL resolves to 404 w3c/vc-bitstring-status-list#21.
-
Validate Algorithm Step (6) has an error w3c/vc-bitstring-status-list#27.
-
-
18 issues received 60 new comments.
-
Define priority for a single credential with multiple statuses w3c/vc-bitstring-status-list#37 (8 comments by @andresuribe87, @dlongley, @iherman, @msporny, @OR13, @Sakurann)
-
RevocationList2021 or RevocationList2021Status w3c/vc-bitstring-status-list#11 (7 comments by @brentzundel, @mprorock, @msporny, @Sakurann)
-
Verification should fail for revocable credentials for status list that cannot be deferenced w3c/vc-bitstring-status-list#39 (7 comments by @dlongley, @iherman, @morgatron, @msporny, @OR13)
-
Status list credential issuer validation w3c/vc-bitstring-status-list#7 (5 comments by @longpd, @mprorock, @Sakurann)
-
Should "noise" be added during "updates" w3c/vc-bitstring-status-list#40 (4 comments by @dlongley, @msporny, @OR13)
-
Is it possible to support multiple purposes? w3c/vc-bitstring-status-list#47 (2 comments by @echenknox)
-
Context about how this differs from 2020-rl w3c/vc-bitstring-status-list#3 (2 comments by @msporny, @Sakurann)
-
Context URL resolves to 404 w3c/vc-bitstring-status-list#21 (2 comments by @msporny, @rolsonquadras)
-
Would like multiple status to be capable of representation in a status list w3c/vc-bitstring-status-list#42 (1 comment by @dlongley)
-
Handling Right to Erasure in encodedList and Validate Algorithm w3c/vc-bitstring-status-list#23 (1 comment by @iherman)
-
-
2 pull requests opened.
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46, by @msporny.
-
Add section about bitstring encoding. w3c/vc-bitstring-status-list#45, by @msporny.
-
-
2 pull requests merged.
-
fix: credentialStatus w3c/vc-bitstring-status-list#34.
-
validation alg fix w3c/vc-bitstring-status-list#28.
-
-
2 pull requests received 11 new comments.
-
Add section about bitstring encoding. w3c/vc-bitstring-status-list#45 (6 comments by @dlongley, @OR13, @TallTed)
-
Ensure that statusListCredential can be dereferenced. w3c/vc-bitstring-status-list#46 (5 comments by @mprorock, @TallTed)
-
w3c/vc-jose-cose
-
2 issues opened.
-
clearer wording for step 2 w3c/vc-jose-cose#43, by @TallTed.
-
Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. w3c/vc-jose-cose#42, by @OR13.
-
-
19 issues received 41 new comments.
-
Confusing text about "If no JWS is present" w3c/vc-jose-cose#23 (5 comments by @mprorock, @OR13, @Sakurann)
-
clarify that `vc` `vp` claims do not include entire VC/VPs w3c/vc-jose-cose#4 (5 comments by @David-Chadwick, @OR13, @Sakurann)
-
Address the `alg` language per the comment here w3c/vc-jose-cose#37 (4 comments by @OR13, @Sakurann)
-
Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. w3c/vc-jose-cose#42 (3 comments by @dlongley, @TallTed)
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-jose-cose#31 (3 comments by @OR13, @Sakurann)
-
No normative statement wrt. JWT encoding of `verifiableCredential` as base64url w3c/vc-jose-cose#3 (2 comments by @David-Chadwick, @Sakurann)
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9 (2 comments by @David-Chadwick, @Sakurann)
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (1 comment by @David-Chadwick)
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30 (1 comment by @OR13)
-
Determine whether to include content from Verifiable Credentials Implementation Guidelines w3c/vc-jose-cose#28 (1 comment by @Sakurann)
-
-
3 pull requests opened.
-
Add version 2 w3c/vc-jose-cose#44, by @OR13.
-
Propose "instead of" in terms of media type w3c/vc-jose-cose#41, by @OR13.
-
Request media type for 1.1 vc-jwt claim set w3c/vc-jose-cose#40, by @OR13.
-
-
3 pull requests merged.
-
Propose "instead of" in terms of media type w3c/vc-jose-cose#41.
-
Request media type for 1.1 vc-jwt claim set w3c/vc-jose-cose#40.
-
Begin production rule definition w3c/vc-jose-cose#11.
-
-
4 pull requests received 63 new comments.
-
Request media type for 1.1 vc-jwt claim set w3c/vc-jose-cose#40 (47 comments by @bc-pi, @brentzundel, @dlongley, @iherman, @jandrieu, @mprorock, @msporny, @OR13, @quartzjer, @Sakurann, @selfissued, @TallTed, @thereisnogabe)
-
w3c/vc-data-model
-
12 issues opened.
-
Typos in v.1.1 w3c/vc-data-model#1021, by @shujikamitsuna.
-
Clarification on when a credentialRefresh service should be used w3c/vc-data-model#1020, by @morgatron.
-
Support for SD-JWT w3c/vc-data-model#1019, by @David-Chadwick.
-
Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data w3c/vc-data-model#1018, by @ChristopherA.
-
Requesting content type for presentation w3c/vc-data-model#1017, by @andresuribe87.
-
Specify allowed Verifier interactions with Verifiable Data Registries w3c/vc-data-model#1016, by @msporny.
-
Provide guidance when media type is incorrect w3c/vc-data-model#1015, by @msporny.
-
Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" w3c/vc-data-model#1012, by @OR13.
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010, by @msporny.
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009, by @David-Chadwick.
-
Breaking changes to IRIs in JSON-LD Context w3c/vc-data-model#1007, by @OR13.
-
-
21 issues closed.
-
Change vocabulary base URL for v2 context w3c/vc-data-model#1002.
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#923.
-
Resolve discrepancies between specifications, vocabularies, schemas w3c/vc-data-model#979.
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913.
-
Add normative reference to Data Integrity w3c/vc-data-model#912.
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953.
-
clarify what an "appropriate VC/VP" is w3c/vc-data-model#848.
-
Change the target file for "https://www.w3.org/2018/credentials/" (at some point...) w3c/vc-data-model#944.
-
Update termsOfUse in context and remove note about bug w3c/vc-data-model#810.
-
Add display hints to data model, for example: information to use a Web Component w3c/vc-data-model#42.
-
Add DataIntegritySignature to v2 context? w3c/vc-data-model#901.
-
EU Label joint degree and multiple issuers for the same VC w3c/vc-data-model#940.
-
Define one or more media types for VCs w3c/vc-data-model#421.
-
Requesting content type for `credential` (without proof). w3c/vc-data-model#978.
-
Define SHACL constraints w3c/vc-data-model#76.
-
Automate generation of JSON-LD Context, Vocabulary, JSON Schema w3c/vc-data-model#998.
-
Adopt and publish StatusList2021 as an `credentialStatus` extension w3c/vc-data-model#974.
-
Have fields for locale-specific information (names, addresses, etc.) been checked? w3c/vc-data-model#734.
-
Redirect the vocabulary to v2 w3c/vc-data-model#966.
-
issuer IRI should be anchored to term definition, page should scroll to definition w3c/vc-data-model#990.
-
URI dereferencing w3c/vc-data-model#764.
-
-
1 issue reopened.
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009, by @David-Chadwick.
-
-
63 issues received 147 new comments.
-
Clarifying credential from verifiable credential w3c/vc-data-model#1009 (7 comments by @awoie, @David-Chadwick, @Sakurann, @TallTed, @thereisnogabe)
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967 (6 comments by @msporny, @OR13, @pchampin)
-
Remove requirement for JWT (etc.) support from VC 2.0 & only support Linked Data w3c/vc-data-model#1018 (6 comments by @ChristopherA, @mwherman2000, @OR13, @peacekeeper, @TallTed)
-
W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec w3c/vc-data-model#982 (5 comments by @brentzundel, @mwherman2000)
-
Remove 3-party Issuer-Holder-Verifier diagram and replace with 2-party Raw Credential Sender-Receiver Model w3c/vc-data-model#1008 (5 comments by @brentzundel, @mwherman2000, @TallTed)
-
Indicating Encrypted VCs in VPs w3c/vc-data-model#938 (5 comments by @David-Chadwick, @dlongley, @OR13, @Sakurann)
-
Some questions about implementation: URIs and verificationMethod w3c/vc-data-model#945 (4 comments by @fabrii, @OR13)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (4 comments by @brentzundel, @mprorock, @OR13, @SmithSamuelM)
-
Update termsOfUse in context and remove note about bug w3c/vc-data-model#810 (4 comments by @msporny, @Sakurann, @TallTed)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (4 comments by @David-Chadwick, @msporny, @Sakurann, @TallTed)
-
Change vocabulary base URL for v2 context w3c/vc-data-model#1002 (3 comments by @brentzundel, @msporny, @OR13)
-
Define policies for directory of related work w3c/vc-data-model#909 (3 comments by @iherman, @TallTed)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (3 comments by @iherman, @Sakurann, @TallTed)
-
Move the VC Extension Registry to this Working Group w3c/vc-data-model#975 (3 comments by @jandrieu, @thereisnogabe)
-
Add `render` property to a core VC data model w3c/vc-data-model#928 (3 comments by @OR13, @Sakurann, @thereisnogabe)
-
Define one or more media types for VCs w3c/vc-data-model#421 (3 comments by @brentzundel, @iherman, @OR13)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (3 comments by @brentzundel, @iherman)
-
Adopt and publish StatusList2021 as an `credentialStatus` extension w3c/vc-data-model#974 (3 comments by @iherman, @msporny)
-
Resolve discrepancies between specifications, vocabularies, schemas w3c/vc-data-model#979 (2 comments by @TallTed, @thereisnogabe)
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896 (2 comments by @msporny, @OR13)
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946 (2 comments by @msporny, @OR13)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (2 comments by @iherman, @msporny)
-
`termsOfUse` is insufficiently specified w3c/vc-data-model#1010 (2 comments by @David-Chadwick, @msporny)
-
Breaking changes to IRIs in JSON-LD Context w3c/vc-data-model#1007 (2 comments by @Sakurann, @TallTed)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (1 comment by @awoie)
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933 (1 comment by @OR13)
-
Clarification of the type of the "verifiableCredential" field in a VP w3c/vc-data-model#958 (1 comment by @OR13)
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913 (1 comment by @msporny)
-
w3c/vc-data-model#862 (1 comment by @msporny)
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953 (1 comment by @msporny)
-
Specify allowed Verifier interactions with Verifiable Data Registries w3c/vc-data-model#1016 (1 comment by @David-Chadwick)
-
Change the target file for "https://www.w3.org/2018/credentials/" (at some point...) w3c/vc-data-model#944 (1 comment by @iherman)
-
Need to clarify the nature of the media type in relationship to "credential" vs "verifiable-credential" w3c/vc-data-model#1012 (1 comment by @TallTed)
-
w3c/vc-data-model#42 (1 comment by @Sakurann)
-
Potential improvements to section "5.8 Zero-Knowledge Proofs" w3c/vc-data-model#939 (1 comment by @Sakurann)
-
EU Label joint degree and multiple issuers for the same VC w3c/vc-data-model#940 (1 comment by @Sakurann)
-
Automate generation of JSON-LD Context, Vocabulary, JSON Schema w3c/vc-data-model#998 (1 comment by @msporny)
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948 (1 comment by @iherman)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (1 comment by @iherman)
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709 (1 comment by @iherman)
-
Have fields for locale-specific information (names, addresses, etc.) been checked? w3c/vc-data-model#734 (1 comment by @msporny)
-
issuer IRI should be anchored to term definition, page should scroll to definition w3c/vc-data-model#990 (1 comment by @msporny)
-
-
8 pull requests opened.
-
Typos pointed out in issue 1021 w3c/vc-data-model#1022, by @bumblefudge.
-
Add normative requirements regarding media type and proof w3c/vc-data-model#1014, by @OR13.
-
Added Presentation as a possible domain for termsOfUse to the formal vocabulary w3c/vc-data-model#1013, by @iherman.
-
Change the reference URL in the vocabulary template file w3c/vc-data-model#1011, by @iherman.
-
Automatic generation of the vocab files via github actions w3c/vc-data-model#1006, by @iherman.
-
Clarify appropriate usage of type information during validation. w3c/vc-data-model#1005, by @msporny.
-
Add termsOfUse to presentations in v2 context. w3c/vc-data-model#1004, by @msporny.
-
Update all examples to use new v2 JSON-LD Context w3c/vc-data-model#1003, by @msporny.
-
-
9 pull requests merged.
-
Added Presentation as a possible domain for termsOfUse to the formal vocabulary w3c/vc-data-model#1013.
-
Change the reference URL in the vocabulary template file w3c/vc-data-model#1011.
-
Clarify appropriate usage of type information during validation. w3c/vc-data-model#1005.
-
Add `@vocab` to v2 context w3c/vc-data-model#1001.
-
Add media type registration request w3c/vc-data-model#1000.
-
Automatic generation of the vocab files via github actions w3c/vc-data-model#1006.
-
Add termsOfUse to presentations in v2 context. w3c/vc-data-model#1004.
-
Update all examples to use new v2 JSON-LD Context w3c/vc-data-model#1003.
-
Change reference to URI/IRI to use WHATWG URL specification. w3c/vc-data-model#994.
-
-
1 pull request closed.
-
Add nonTransferable property to credentials vocab w3c/vc-data-model#969.
-
-
15 pull requests received 196 new comments.
-
Add media type registration request w3c/vc-data-model#1000 (56 comments by @brentzundel, @dlongley, @iherman, @mprorock, @msporny, @OR13, @quartzjer, @Sakurann, @selfissued, @TallTed)
-
Added presentationSchema w3c/vc-data-model#987 (17 comments by @David-Chadwick, @iherman, @msporny, @OR13)
-
Add `@vocab` to v2 context w3c/vc-data-model#1001 (16 comments by @iherman, @msporny, @OR13, @vongohren)
-
Added Presentation as a possible domain for termsOfUse to the formal vocabulary w3c/vc-data-model#1013 (14 comments by @iherman, @jandrieu, @msporny, @TallTed)
-
Remove ZKP Section w3c/vc-data-model#999 (12 comments by @brentzundel, @iherman, @jandrieu, @msporny, @OR13, @Sebastian-Elfors-IDnow, @TallTed, @thereisnogabe)
-
Clarify appropriate usage of type information during validation. w3c/vc-data-model#1005 (10 comments by @David-Chadwick, @iherman, @msporny, @TallTed)
-
Change the reference URL in the vocabulary template file w3c/vc-data-model#1011 (8 comments by @dlongley, @iherman, @msporny)
-
Update all examples to use new v2 JSON-LD Context w3c/vc-data-model#1003 (8 comments by @dlongley, @iherman, @msporny)
-
Add termsOfUse to presentations in v2 context. w3c/vc-data-model#1004 (6 comments by @brentzundel, @iherman, @jandrieu, @msporny, @TallTed)
-
Automatic generation of the vocab files via github actions w3c/vc-data-model#1006 (4 comments by @iherman, @msporny)
-
Change reference to URI/IRI to use WHATWG URL specification. w3c/vc-data-model#994 (2 comments by @msporny)
-
Add DataIntegrityProof to credentials/v2 JSON-LD Context. w3c/vc-data-model#943 (1 comment by @TallTed)
-
w3c/vc-di-eddsa
-
2 issues opened.
-
Review on 2023-01-26 by Greg Bernstein, Test Vector Suggestions w3c/vc-di-eddsa#22, by @Wind4Greg.
-
How is `proofConfig` meant to be serialized? w3c/vc-di-eddsa#21, by @olivereanderson.
-
-
2 issues closed.
-
Review multibase vs base58 key representation w3c/vc-di-eddsa#3.
-
Add CODEOWNERS as spec editors w3c/vc-di-eddsa#2.
-
-
4 issues received 4 new comments.
-
Review on 2023-01-26 by Greg Bernstein, Test Vector Suggestions w3c/vc-di-eddsa#22 (1 comment by @msporny)
-
-
2 pull requests opened.
-
Revised Test vectors text w3c/vc-di-eddsa#24, by @Wind4Greg.
-
Added test vectors for the Ed25519Signature2020 case. w3c/vc-di-eddsa#23, by @Wind4Greg.
-
-
1 pull request merged.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15.
-
-
1 pull request closed.
-
Added test vectors for the Ed25519Signature2020 case. w3c/vc-di-eddsa#23.
-
-
2 pull requests received 7 new comments.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15 (4 comments by @matthieubosquet, @msporny)
-
Added test vectors for the Ed25519Signature2020 case. w3c/vc-di-eddsa#23 (3 comments by @msporny, @OR13, @Wind4Greg)
-
w3c/vcalm
-
5 issues opened.
-
Define extensibility rules for VC API endpoint options w3c/vcalm#335, by @msporny.
-
Production utilities endpoints w3c/vcalm#333, by @PatStLouis.
-
Multi-format credential support w3c/vcalm#332, by @PatStLouis.
-
Specify how error details are returned w3c/vcalm#331, by @msporny.
-
Clarify expected use of "description" in "Initiate Exchange" w3c/vcalm#330, by @jrhender.
-
-
4 issues closed.
-
Should URL options be terms or absolute URLs? w3c/vcalm#198.
-
10 issues received 14 new comments.
-
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.) w3c/vcalm#285 (1 comment by @msporny)
-
What are the reasons that a JSON registry shouldn't be used for term extensibility in the VC API? w3c/vcalm#288 (1 comment by @msporny)
-
What are the reasons that JSON-LD shouldn't be used for term extensibility in the VC API? w3c/vcalm#287 (1 comment by @msporny)
-
PROPOSAL: Restrict conformance and interop test suites to did:key only. w3c/vcalm#184 (1 comment by @msporny)
-
4 pull requests opened.
-
Fix linting errors in OAS files. w3c/vcalm#334, by @msporny.
-
Add Design Goals and Rationale w3c/vcalm#329, by @msporny.
-
Expand introductory section to include purpose of spec. w3c/vcalm#328, by @msporny.
-
Fix roles/components to use "Coordinator" and migrate to SVG files. w3c/vcalm#327, by @msporny.
-
-
7 pull requests merged.
-
Add Design Goals and Rationale w3c/vcalm#329.
-
Expand introductory section to include purpose of spec. w3c/vcalm#328.
-
Adds a description to issuer.id & the error response. w3c/vcalm#324.
-
Add verifiablePresentation to exchanges examples. w3c/vcalm#322.
-
-
1 pull request closed.
-
Prepare document for publication as VCWG Draft NOTE. w3c/vcalm#320.
-
-
9 pull requests received 30 new comments.
-
Expand introductory section to include purpose of spec. w3c/vcalm#328 (10 comments by @dlongley, @msporny, @TallTed)
-
Reference error schema on error endpoints w3c/vcalm#326 (8 comments by @aljones15, @msporny, @nissimsan, @OR13, @ottonomy)
-
Prepare document for publication as VCWG Draft NOTE. w3c/vcalm#320 (3 comments by @aljones15, @msporny)
-
Fix roles/components to use "Coordinator" and migrate to SVG files. w3c/vcalm#327 (1 comment by @msporny)
-
Add 404 as a response for GET/DELETE credentials/{id} and same for VPs w3c/vcalm#321 (1 comment by @msporny)
-
Exchanges Continue response can be anyOf VPResponse or VPRequest. w3c/vcalm#325 (1 comment by @msporny)
-
Add verifiablePresentationRequest property to exchange initiate. w3c/vcalm#323 (1 comment by @mkhraisha)
-
w3c/vc-json-schema
-
1 issue opened.
-
Consider adding language on schema immutability w3c/vc-json-schema#120, by @andresuribe87.
-
-
1 issue received 3 new comments.
-
Consider adding language on schema immutability w3c/vc-json-schema#120 (3 comments by @andresuribe87, @OR13, @thereisnogabe)
-
-
1 pull request opened.
-
Included drawback section on validation w3c/vc-json-schema#119, by @andresuribe87.
-
-
1 pull request merged.
-
Included drawback section on validation w3c/vc-json-schema#119.
-
-
1 pull request received 11 new comments.
-
Included drawback section on validation w3c/vc-json-schema#119 (11 comments by @andresuribe87, @OR13, @TallTed)
-
w3c/vc-use-cases
-
1 issue opened.
-
Define use case(s) that requires holder binding w3c/vc-use-cases#128, by @awoie.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Use case for Holder Binding w3c/vc-use-cases#129, by @justAnIdentity.
-
-
2 pull requests received 4 new comments.
w3c/vc-data-integrity
-
3 issues opened.
-
Review on 2023-01-26 by Greg Bernstein w3c/vc-data-integrity#81, by @Wind4Greg.
-
Expiration Date w3c/vc-data-integrity#78, by @David-Chadwick.
-
Specify how relative URLs should be processed w3c/vc-data-integrity#77, by @msporny.
-
-
3 issues received 6 new comments.
-
4 pull requests opened.
-
Add section on Proof Purpose Validation. w3c/vc-data-integrity#80, by @msporny.
-
Attempt to synchronize the security vocabulary with the FPWD spec w3c/vc-data-integrity#79, by @iherman.
-
Add section on Canonicalization Method Correctness. w3c/vc-data-integrity#76, by @msporny.
-
Add note on verification relationships to Security Considerations. w3c/vc-data-integrity#75, by @msporny.
-
-
4 pull requests merged.
-
Attempt to synchronize the security vocabulary with the FPWD spec w3c/vc-data-integrity#79.
-
Add section on Proof Purpose Validation. w3c/vc-data-integrity#80.
-
Add section on Canonicalization Method Correctness. w3c/vc-data-integrity#76.
-
Add note on verification relationships to Security Considerations. w3c/vc-data-integrity#75.
-
-
4 pull requests received 55 new comments.
-
Add section on Canonicalization Method Correctness. w3c/vc-data-integrity#76 (12 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add note on verification relationships to Security Considerations. w3c/vc-data-integrity#75 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add section on Proof Purpose Validation. w3c/vc-data-integrity#80 (3 comments by @iherman, @msporny)
w3c/vc-jws-2020
-
1 issue opened.
-
Naming of work w3c/vc-jws-2020#31, by @martinthomson.
-
-
1 issue received 7 new comments.
-
Naming of work w3c/vc-jws-2020#31 (7 comments by @brentzundel, @brianorwhatever, @mprorock, @OR13, @peacekeeper, @Sakurann)
-
-
1 pull request opened.
-
Change spec title w3c/vc-jws-2020#32, by @OR13.
-
-
2 pull requests merged.
-
Change spec title w3c/vc-jws-2020#32.
-
Fix typos w3c/vc-jws-2020#30.
-
-
1 pull request received 5 new comments.
w3c/vc-test-suite
-
1 issue received 1 new comment.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (1 comment by @brentzundel)
-
w3c/vc-di-bbs
-
1 issue received 1 new comment.
-
1 pull request opened.
-
add a new pure golang implementation w3c/vc-di-bbs#68, by @suutaku.
-
-
1 pull request merged.
-
add a new pure golang implementation w3c/vc-di-bbs#68.
-
w3c/vc-jose-cose-test-suite
-
1 issue received 1 new comment.
-
Proposal: use did:jwk for testing dids and vc-jwt in the vc-jwt-test-suite w3c/vc-jose-cose-test-suite#10 (1 comment by @Sakurann)
-