Verifiable Credentials Working Group - Activity in 2026
No matches.
VC Recognized Entities
Past meetings
-
3 meetings of the VC Recognized Entities.
GitHub
w3c/vc-recognized-entities
-
2 issues opened in the VC Recognized Entities.
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140, by @onthebreeze.
-
Global Quality Infrastructure use case for Recognized Entities w3c/vc-recognized-entities#139, by @onthebreeze.
-
-
4 issues in the VC Recognized Entities received 36 new comments.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (19 comments by @dlongley, @msporny, @onthebreeze, @paulfdietrich, @philarcher)
-
revisit the data model w3c/vc-recognized-entities#135 (7 comments by @dlongley, @msporny, @onthebreeze, @philarcher)
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140 (6 comments by @iherman, @msporny, @onthebreeze)
-
Global Quality Infrastructure use case for Recognized Entities w3c/vc-recognized-entities#139 (4 comments by @msporny, @philarcher)
-
-
4 pull requests opened in the VC Recognized Entities.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144, by @paulfdietrich.
-
Add metrology calibration example w3c/vc-recognized-entities#143, by @msporny.
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142, by @msporny.
-
added a >CE Marking Product Conformity Example< in appendix D w3c/vc-recognized-entities#141, by @ngwlf.
-
-
1 pull request closed in the VC Recognized Entities.
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108.
-
-
7 pull requests in the VC Recognized Entities received 58 new comments.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144 (8 comments by @iherman, @msporny, @paulfdietrich)
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142 (7 comments by @msporny, @onthebreeze)
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108 (3 comments by @msporny, @paulfdietrich, @philarcher)
-
added a >CE Marking Product Conformity Example< in appendix D w3c/vc-recognized-entities#141 (2 comments by @msporny, @TallTed)
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138 (2 comments by @iherman, @TallTed)
VC API for Lifecycle Management
Past meetings
-
3 meetings of the VC API for Lifecycle Management.
GitHub
w3c/vcalm
-
4 issues opened in the VC API for Lifecycle Management.
-
2 issues closed in the VC API for Lifecycle Management.
-
Create Threat Model for VCALM w3c/vcalm#628.
-
Add QR Code shoulder surfing to threat model w3c/vcalm#719.
-
-
14 issues in the VC API for Lifecycle Management received 34 new comments.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686 (19 comments by @donaldzitzer406-lang, @iherman, @kezike)
-
Allow an application-defined payload in the final exchange message after a successful DIDAuthentication w3c/vcalm#733 (2 comments by @donaldzitzer406-lang)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @ottonomy)
-
Component Overview missing all endpoints, probably due to a respec error w3c/vcalm#738 (1 comment by @PatStLouis)
-
BUGFIX - Spec isn't rendering properly, endpoints sections are missing content w3c/vcalm#732 (1 comment by @donaldzitzer406-lang)
-
Consider including `recipientPublicJwk` (or similarly named) property in VPR for encrypted responses w3c/vcalm#693 (1 comment by @dlongley)
-
Add a multistep workflow example with branching steps generated from step templates w3c/vcalm#600 (1 comment by @PatStLouis)
-
-
8 pull requests opened in the VC API for Lifecycle Management.
-
Document cryptosuite-specific exchangeData with a BBS example w3c/vcalm#742, by @PatStLouis.
-
Add explicit exchange termination signal w3c/vcalm#741, by @kezike.
-
Fix mixed LF/CRLF state in index.html. w3c/vcalm#739, by @kezike.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#737, by @PatStLouis.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#736, by @PatStLouis.
-
Revert "Fix empty endpoint tables and broken deletion xref. (#734)" w3c/vcalm#735, by @PatStLouis.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#734, by @PatStLouis.
-
Adding threat model snapshot to transitions folder w3c/vcalm#731, by @eric-schuh.
-
-
3 pull requests merged in the VC API for Lifecycle Management.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#734.
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720.
-
3 pull requests closed in the VC API for Lifecycle Management.
-
Fix mixed LF/CRLF state in index.html. w3c/vcalm#739.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#737.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#736.
-
-
11 pull requests in the VC API for Lifecycle Management received 28 new comments.
-
Adding threat model snapshot to transitions folder w3c/vcalm#731 (5 comments by @eric-schuh, @iherman)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (4 comments by @PatStLouis)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (4 comments by @PatStLouis)
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728 (2 comments by @eric-schuh)
-
w3c/vcalm-test-suite
-
4 pull requests opened in the VC API for Lifecycle Management.
-
Test the workflow interfaces required by section 3.6 w3c/vcalm-test-suite#9, by @PatStLouis.
-
Lay skipped normative statements under the spec contents w3c/vcalm-test-suite#8, by @PatStLouis.
-
Scaffold the remaining required statements as skipped rows w3c/vcalm-test-suite#7, by @PatStLouis.
-
Cover required conformance endpoints and OpenAPI checks w3c/vcalm-test-suite#6, by @PatStLouis.
-
-
2 pull requests merged in the VC API for Lifecycle Management.
-
Scaffold the remaining required statements as skipped rows w3c/vcalm-test-suite#7.
-
Cover required conformance endpoints and OpenAPI checks w3c/vcalm-test-suite#6.
-
TR publications
-
10 documents published.
-
Securing Verifiable Credentials using JOSE and COSE published as a Recommendation. History of Securing Verifiable Credentials using JOSE and COSE
-
VCALM v1.0 published twice as a Working Draft. History of VCALM v1.0
-
Verifiable Credential Rendering Methods v1.0 published twice as a Working Draft. History of Verifiable Credential Rendering Methods v1.0
-
Data Integrity Threat Model v1.1 published as a Draft Note. History of Data Integrity Threat Model v1.1
-
Recognized Entities Threat Model v1.0 published as a Draft Note. History of Recognized Entities Threat Model v1.0
-
VCALM Threat Model v1.0 published as a Draft Note. History of VCALM Threat Model v1.0
-
Verifiable Credential Barcodes Threat Model v1.0 published as a Draft Note. History of Verifiable Credential Barcodes Threat Model v1.0
-
Past meetings
-
2 meetings.
Participants
-
6 participants joined.
-
Artiom Casapu (Google LLC) joined.
-
Devin Zeng (Tencent) joined.
-
Juan Caballero (Decentralized Identity Foundation (DIF)) joined.
-
Kevin Druff (Capital One Discover Network) joined.
-
Daniel Pelegero (Capital One Discover Network) joined.
-
George McEwan (W3C Invited Experts) joined.
-
-
1 participant left.
-
Rob De Feo (Vidos) left.
-
-
2 organizations joined.
-
Tencent joined.
-
Decentralized Identity Foundation (DIF) joined.
-
-
1 organization left.
-
Vidos left.
-
GitHub
w3c/vcalm
-
4 issues opened.
-
2 issues closed.
-
Create Threat Model for VCALM w3c/vcalm#628.
-
Add QR Code shoulder surfing to threat model w3c/vcalm#719.
-
-
14 issues received 34 new comments.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686 (19 comments by @donaldzitzer406-lang, @iherman, @kezike)
-
Allow an application-defined payload in the final exchange message after a successful DIDAuthentication w3c/vcalm#733 (2 comments by @donaldzitzer406-lang)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @ottonomy)
-
Component Overview missing all endpoints, probably due to a respec error w3c/vcalm#738 (1 comment by @PatStLouis)
-
BUGFIX - Spec isn't rendering properly, endpoints sections are missing content w3c/vcalm#732 (1 comment by @donaldzitzer406-lang)
-
Consider including `recipientPublicJwk` (or similarly named) property in VPR for encrypted responses w3c/vcalm#693 (1 comment by @dlongley)
-
Add a multistep workflow example with branching steps generated from step templates w3c/vcalm#600 (1 comment by @PatStLouis)
-
-
8 pull requests opened.
-
Document cryptosuite-specific exchangeData with a BBS example w3c/vcalm#742, by @PatStLouis.
-
Add explicit exchange termination signal w3c/vcalm#741, by @kezike.
-
Fix mixed LF/CRLF state in index.html. w3c/vcalm#739, by @kezike.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#737, by @PatStLouis.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#736, by @PatStLouis.
-
Revert "Fix empty endpoint tables and broken deletion xref. (#734)" w3c/vcalm#735, by @PatStLouis.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#734, by @PatStLouis.
-
Adding threat model snapshot to transitions folder w3c/vcalm#731, by @eric-schuh.
-
-
3 pull requests merged.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#734.
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720.
-
3 pull requests closed.
-
Fix mixed LF/CRLF state in index.html. w3c/vcalm#739.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#737.
-
Fix empty endpoint tables and broken deletion xref w3c/vcalm#736.
-
-
11 pull requests received 28 new comments.
-
Adding threat model snapshot to transitions folder w3c/vcalm#731 (5 comments by @eric-schuh, @iherman)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (4 comments by @PatStLouis)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (4 comments by @PatStLouis)
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728 (2 comments by @eric-schuh)
-
w3c/vc-render-method
-
9 issues opened.
-
Support following related credentials from html suite templates (host-mediated links) w3c/vc-render-method#99, by @PatStLouis.
-
Language negotiation of `static` render suite w3c/vc-render-method#98, by @aphillips.
-
`html` method has no localization model w3c/vc-render-method#97, by @aphillips.
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96, by @aphillips.
-
language and direction for `name`, `direction`, `icon`, and theme colors w3c/vc-render-method#95, by @aphillips.
-
`summary` method has no localization model w3c/vc-render-method#94, by @aphillips.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93, by @aphillips.
-
Considerations for static render method w3c/vc-render-method#92, by @dlongley.
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90, by @iherman.
-
-
10 issues closed.
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27.
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90.
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69.
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71.
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84.
-
Specify a usage type / display preference for List view credential w3c/vc-render-method#18.
-
Add web-based `renderSuite` w3c/vc-render-method#23.
-
Editorial comments on (JSON) cards w3c/vc-render-method#61.
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77.
-
-
20 issues received 29 new comments.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93 (4 comments by @aphillips, @dmitrizagidulin, @iherman)
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96 (3 comments by @dmitrizagidulin, @iherman, @msporny)
-
Support following related credentials from html suite templates (host-mediated links) w3c/vc-render-method#99 (2 comments by @dlongley, @dmitrizagidulin)
-
Considerations for static render method w3c/vc-render-method#92 (2 comments by @aphillips, @dlongley)
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71 (2 comments by @dmitrizagidulin)
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84 (2 comments by @dmitrizagidulin)
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27 (1 comment by @dmitrizagidulin)
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69 (1 comment by @dmitrizagidulin)
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90 (1 comment by @dmitrizagidulin)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
Specify a usage type / display preference for List view credential w3c/vc-render-method#18 (1 comment by @dmitrizagidulin)
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (1 comment by @dmitrizagidulin)
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77 (1 comment by @dmitrizagidulin)
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86 (1 comment by @PatStLouis)
-
-
7 pull requests opened.
-
Allow language value objects for name, description, and fields. w3c/vc-render-method#102, by @dmitrizagidulin.
-
Allow language value objects for render method name/description. w3c/vc-render-method#101, by @dmitrizagidulin.
-
Reference VCDM for validFrom/validUntil instead of redefining. w3c/vc-render-method#100, by @dmitrizagidulin.
-
Convert direct links to ReSpec citations. w3c/vc-render-method#91, by @dmitrizagidulin.
-
Add a Selecting on Language section, 'targetLanguage' property. w3c/vc-render-method#89, by @dmitrizagidulin.
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88, by @dmitrizagidulin.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87, by @dmitrizagidulin.
-
-
4 pull requests merged.
-
Convert direct links to ReSpec citations. w3c/vc-render-method#91.
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87.
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85.
-
-
1 pull request closed.
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30.
-
-
5 pull requests received 22 new comments.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87 (11 comments by @dmitrizagidulin, @iherman, @msporny)
-
Add a Selecting on Language section, 'targetLanguage' property. w3c/vc-render-method#89 (7 comments by @dlongley, @dmitrizagidulin, @TallTed)
-
Reference VCDM for validFrom/validUntil instead of redefining. w3c/vc-render-method#100 (2 comments by @dmitrizagidulin)
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88 (1 comment by @dmitrizagidulin)
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (1 comment by @PatStLouis)
-
w3c/vc-recognized-entities
-
2 issues opened.
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140, by @onthebreeze.
-
Global Quality Infrastructure use case for Recognized Entities w3c/vc-recognized-entities#139, by @onthebreeze.
-
-
4 issues received 36 new comments.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (19 comments by @dlongley, @msporny, @onthebreeze, @paulfdietrich, @philarcher)
-
revisit the data model w3c/vc-recognized-entities#135 (7 comments by @dlongley, @msporny, @onthebreeze, @philarcher)
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140 (6 comments by @iherman, @msporny, @onthebreeze)
-
Global Quality Infrastructure use case for Recognized Entities w3c/vc-recognized-entities#139 (4 comments by @msporny, @philarcher)
-
-
4 pull requests opened.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144, by @paulfdietrich.
-
Add metrology calibration example w3c/vc-recognized-entities#143, by @msporny.
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142, by @msporny.
-
added a >CE Marking Product Conformity Example< in appendix D w3c/vc-recognized-entities#141, by @ngwlf.
-
-
1 pull request closed.
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108.
-
-
7 pull requests received 58 new comments.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144 (8 comments by @iherman, @msporny, @paulfdietrich)
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142 (7 comments by @msporny, @onthebreeze)
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108 (3 comments by @msporny, @paulfdietrich, @philarcher)
-
added a >CE Marking Product Conformity Example< in appendix D w3c/vc-recognized-entities#141 (2 comments by @msporny, @TallTed)
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138 (2 comments by @iherman, @TallTed)
w3c/vc-data-model
-
3 issues opened.
-
Discussion of privacy mitigations when fetching resources over the web. w3c/vc-data-model#1660, by @wes-smith.
-
Which bytes of a related resource are hashed for digestMultibase and digestSRI? w3c/vc-data-model#1657, by @shigeya.
-
Document how preferred language is passed when fetching resources w3c/vc-data-model#1653, by @msporny.
-
-
1 issue closed.
-
CSOAI — Verifiable Credentials for AI governance w3c/vc-data-model#1650.
-
-
6 issues received 13 new comments.
-
Document how preferred language is passed when fetching resources w3c/vc-data-model#1653 (4 comments by @aphillips, @iherman, @msporny)
-
Which bytes of a related resource are hashed for digestMultibase and digestSRI? w3c/vc-data-model#1657 (2 comments by @astrogilda, @shigeya)
-
Add `exchangeData` to `VerifiablePresentation` datatype w3c/vc-data-model#1649 (2 comments by @dmitrizagidulin, @iherman)
-
Threat Model: Improve Bearer Credential Reuse and Correlation description w3c/vc-data-model#1640 (2 comments by @dmitrizagidulin, @iherman)
-
Update references to confidence and render methods. w3c/vc-data-model#1632 (2 comments by @dmitrizagidulin, @iherman)
-
-
5 pull requests opened.
-
Add a note describing digestMultibase and digestSRI (#1628) w3c/vc-data-model#1659, by @shigeya.
-
Pin digestSRI to SRI 1.0 and define its processing rules (#1628) w3c/vc-data-model#1658, by @shigeya.
-
Add exchangeData property to verifiable presentations. w3c/vc-data-model#1656, by @dmitrizagidulin.
-
Add format fields to VC and VP JSON Schemas. w3c/vc-data-model#1655, by @dmitrizagidulin.
-
Point reserved extension points at their defining specs. w3c/vc-data-model#1654, by @dmitrizagidulin.
-
-
5 pull requests received 26 new comments.
-
First version of the 2.1 version of the vocabulary. w3c/vc-data-model#1652 (14 comments by @dlongley, @iherman, @msporny)
-
Add a note describing digestMultibase and digestSRI (#1628) w3c/vc-data-model#1659 (4 comments by @shigeya, @TallTed)
-
Point reserved extension points at their defining specs. w3c/vc-data-model#1654 (3 comments by @TallTed)
-
Add exchangeData property to verifiable presentations. w3c/vc-data-model#1656 (3 comments by @kezike)
-
Add format fields to VC and VP JSON Schemas. w3c/vc-data-model#1655 (2 comments by @Oran-Dan, @TallTed)
-
w3c/vc-bitstring-status-list
-
3 issues opened.
-
ReSpec failure on latest PRs w3c/vc-bitstring-status-list#221, by @KDean-Dolphin.
-
Clarify producer conformance for reserved decoy positions and their lifecycle privacy limits w3c/vc-bitstring-status-list#218, by @cstoecker.
-
Tradeoffs in mixing credential types on individual lists. w3c/vc-bitstring-status-list#217, by @wes-smith.
-
-
6 issues received 7 new comments.
-
Add table for mitigations that increase privacy when using revocation lists w3c/vc-bitstring-status-list#207 (2 comments by @wes-smith)
-
Add privacy consideration regarding k-anonymity degradation over time w3c/vc-bitstring-status-list#206 (1 comment by @wes-smith)
-
The explainer needs more clarity around example bitstring list I am unable to decode the example bitstring status list w3c/vc-bitstring-status-list#201 (1 comment by @KDean-Dolphin)
-
information that gets embedded in the compressed bitstring (GZIP) w3c/vc-bitstring-status-list#209 (1 comment by @KDean-Dolphin)
-
Broken links in Bitstring Status List v1.1 w3c/vc-bitstring-status-list#210 (1 comment by @KDean-Dolphin)
-
Clarify bit-to-byte ordering in bitstring serialization w3c/vc-bitstring-status-list#211 (1 comment by @KDean-Dolphin)
-
-
2 pull requests opened.
-
Refined bitstring compression and encoding steps w3c/vc-bitstring-status-list#220, by @KDean-Dolphin.
-
Expanded Bitstring Generation Algorithm per #211 w3c/vc-bitstring-status-list#219, by @KDean-Dolphin.
-
w3c/vc-data-integrity
-
3 issues received 19 new comments.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369 (12 comments by @studyzy, @Wind4Greg)
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363 (5 comments by @antonymott, @msporny, @Wind4Greg)
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373 (2 comments by @filip26, @swcurran)
-
-
1 pull request opened.
-
Aggregate SHoC salted hashes with a Merkle tree w3c/vc-data-integrity#377, by @studyzy.
-
-
1 pull request received 7 new comments.
-
Aggregate SHoC salted hashes with a Merkle tree w3c/vc-data-integrity#377 (7 comments by @iherman, @studyzy, @Wind4Greg)
-
w3c/vc-confidence-method
-
2 issues opened.
-
Update "at risk" narrative on ZKP biometrics w3c/vc-confidence-method#53, by @jandrieu.
-
Broken links in Verifiable Credential Confidence Methods v1.0 w3c/vc-confidence-method#52, by @dontcallmedom-bot.
-
-
3 issues received 4 new comments.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (2 comments by @iherman, @jandrieu)
-
Biometric model and vector data might be combined since they are associated with one another w3c/vc-confidence-method#50 (1 comment by @jandrieu)
-
-
1 pull request opened.
-
Update Assurance Levels description w3c/vc-confidence-method#54, by @denkeni.
-
w3c/vc-use-cases
-
1 pull request opened.
-
updated user tasks to say credential instead of claim w3c/vc-use-cases#172, by @jandrieu.
-
-
1 pull request received 1 new comment.
w3c/vcalm-test-suite
-
4 pull requests opened.
-
Test the workflow interfaces required by section 3.6 w3c/vcalm-test-suite#9, by @PatStLouis.
-
Lay skipped normative statements under the spec contents w3c/vcalm-test-suite#8, by @PatStLouis.
-
Scaffold the remaining required statements as skipped rows w3c/vcalm-test-suite#7, by @PatStLouis.
-
Cover required conformance endpoints and OpenAPI checks w3c/vcalm-test-suite#6, by @PatStLouis.
-
-
2 pull requests merged.
-
Scaffold the remaining required statements as skipped rows w3c/vcalm-test-suite#7.
-
Cover required conformance endpoints and OpenAPI checks w3c/vcalm-test-suite#6.
-
w3c/vc-test-suite-implementations
-
1 pull request opened.
-
Add RWAIX implementation w3c/vc-test-suite-implementations#128, by @hw7325391218-create.
-
w3c/vc-jose-cose
-
1 issue closed.
-
CR leftover text in the status section w3c/vc-jose-cose#345.
-
-
1 pull request opened.
-
Removing old CR text. Will Fix #345 w3c/vc-jose-cose#346, by @philarcher.
-
-
1 pull request merged.
-
Removing old CR text. Will Fix #345 w3c/vc-jose-cose#346.
-
-
1 pull request received 2 new comments.
w3c/vc-barcodes
-
1 pull request opened.
-
Prepare threat model for DNOTE publication. w3c/vc-barcodes#74, by @wes-smith.
-
-
1 pull request received 4 new comments.
VC Render Method
Participants
-
1 participant joined the VC Render Method.
-
Patrick St-Louis joined.
-
GitHub
w3c/vc-render-method
-
9 issues opened in the VC Render Method.
-
Support following related credentials from html suite templates (host-mediated links) w3c/vc-render-method#99, by @PatStLouis.
-
Language negotiation of `static` render suite w3c/vc-render-method#98, by @aphillips.
-
`html` method has no localization model w3c/vc-render-method#97, by @aphillips.
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96, by @aphillips.
-
language and direction for `name`, `direction`, `icon`, and theme colors w3c/vc-render-method#95, by @aphillips.
-
`summary` method has no localization model w3c/vc-render-method#94, by @aphillips.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93, by @aphillips.
-
Considerations for static render method w3c/vc-render-method#92, by @dlongley.
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90, by @iherman.
-
-
10 issues closed in the VC Render Method.
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27.
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90.
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69.
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71.
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84.
-
Specify a usage type / display preference for List view credential w3c/vc-render-method#18.
-
Add web-based `renderSuite` w3c/vc-render-method#23.
-
Editorial comments on (JSON) cards w3c/vc-render-method#61.
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77.
-
-
20 issues in the VC Render Method received 29 new comments.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93 (4 comments by @aphillips, @dmitrizagidulin, @iherman)
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96 (3 comments by @dmitrizagidulin, @iherman, @msporny)
-
Support following related credentials from html suite templates (host-mediated links) w3c/vc-render-method#99 (2 comments by @dlongley, @dmitrizagidulin)
-
Considerations for static render method w3c/vc-render-method#92 (2 comments by @aphillips, @dlongley)
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71 (2 comments by @dmitrizagidulin)
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84 (2 comments by @dmitrizagidulin)
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27 (1 comment by @dmitrizagidulin)
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69 (1 comment by @dmitrizagidulin)
-
(Editorial) Use "indirect" references instead of direct ones w3c/vc-render-method#90 (1 comment by @dmitrizagidulin)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
Specify a usage type / display preference for List view credential w3c/vc-render-method#18 (1 comment by @dmitrizagidulin)
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (1 comment by @dmitrizagidulin)
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77 (1 comment by @dmitrizagidulin)
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86 (1 comment by @PatStLouis)
-
-
7 pull requests opened in the VC Render Method.
-
Allow language value objects for name, description, and fields. w3c/vc-render-method#102, by @dmitrizagidulin.
-
Allow language value objects for render method name/description. w3c/vc-render-method#101, by @dmitrizagidulin.
-
Reference VCDM for validFrom/validUntil instead of redefining. w3c/vc-render-method#100, by @dmitrizagidulin.
-
Convert direct links to ReSpec citations. w3c/vc-render-method#91, by @dmitrizagidulin.
-
Add a Selecting on Language section, 'targetLanguage' property. w3c/vc-render-method#89, by @dmitrizagidulin.
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88, by @dmitrizagidulin.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87, by @dmitrizagidulin.
-
-
4 pull requests merged in the VC Render Method.
-
Convert direct links to ReSpec citations. w3c/vc-render-method#91.
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87.
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85.
-
-
1 pull request closed in the VC Render Method.
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30.
-
-
5 pull requests in the VC Render Method received 22 new comments.
-
Prep threat model for DNOTE publication. w3c/vc-render-method#87 (11 comments by @dmitrizagidulin, @iherman, @msporny)
-
Add a Selecting on Language section, 'targetLanguage' property. w3c/vc-render-method#89 (7 comments by @dlongley, @dmitrizagidulin, @TallTed)
-
Reference VCDM for validFrom/validUntil instead of redefining. w3c/vc-render-method#100 (2 comments by @dmitrizagidulin)
-
Rename 'template' field to 'payload' for all suites. w3c/vc-render-method#88 (1 comment by @dmitrizagidulin)
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (1 comment by @PatStLouis)
-
VC Barcodes and Data Integrity
Past meetings
-
3 meetings of the VC Barcodes and Data Integrity.
GitHub
w3c/vc-data-integrity
-
3 issues in the VC Barcodes and Data Integrity received 19 new comments.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369 (12 comments by @studyzy, @Wind4Greg)
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363 (5 comments by @antonymott, @msporny, @Wind4Greg)
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373 (2 comments by @filip26, @swcurran)
-
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Aggregate SHoC salted hashes with a Merkle tree w3c/vc-data-integrity#377, by @studyzy.
-
-
1 pull request in the VC Barcodes and Data Integrity received 7 new comments.
-
Aggregate SHoC salted hashes with a Merkle tree w3c/vc-data-integrity#377 (7 comments by @iherman, @studyzy, @Wind4Greg)
-
w3c/vc-barcodes
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Prepare threat model for DNOTE publication. w3c/vc-barcodes#74, by @wes-smith.
-
-
1 pull request in the VC Barcodes and Data Integrity received 4 new comments.
VC Confidence Method
GitHub
w3c/vc-confidence-method
-
2 issues opened in the VC Confidence Method.
-
Update "at risk" narrative on ZKP biometrics w3c/vc-confidence-method#53, by @jandrieu.
-
Broken links in Verifiable Credential Confidence Methods v1.0 w3c/vc-confidence-method#52, by @dontcallmedom-bot.
-
-
3 issues in the VC Confidence Method received 4 new comments.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (2 comments by @iherman, @jandrieu)
-
Biometric model and vector data might be combined since they are associated with one another w3c/vc-confidence-method#50 (1 comment by @jandrieu)
-
-
1 pull request opened in the VC Confidence Method.
-
Update Assurance Levels description w3c/vc-confidence-method#54, by @denkeni.
-
TR publications
-
25 documents published.
-
Data Integrity BBS Cryptosuites v1.0 published twice as a Candidate Recommendation Draft. History of Data Integrity BBS Cryptosuites v1.0
-
Verifiable Credential Data Integrity 1.1 published 3 times as a Working Draft. History of Verifiable Credential Data Integrity 1.1
-
Verifiable Credentials Data Model v2.1 published 6 times as a Working Draft. History of Verifiable Credentials Data Model v2.1
-
Verifiable Credential Rendering Methods v1.0 published twice as a Working Draft. History of Verifiable Credential Rendering Methods v1.0
-
Data Integrity ECDSA Cryptosuites v1.1 published as a Working Draft. History of Data Integrity ECDSA Cryptosuites v1.1
-
Verifiable Credential Confidence Methods v1.0 published twice as a Working Draft. History of Verifiable Credential Confidence Methods v1.0
-
Recognized Entities v1.0 published twice as a Working Draft. History of Recognized Entities v1.0
-
Bitstring Status List v1.1 published as a First Public Working Draft. History of Bitstring Status List v1.1
-
Verifiable Credentials Data Model Threat Model v2.1 published 3 times as a Draft Note. History of Verifiable Credentials Data Model Threat Model v2.1
-
Verifiable Credentials Overview v1.1 published 3 times as a Draft Note. History of Verifiable Credentials Overview v1.1
-
Past meetings
Participants
-
1 participant joined.
-
Lucy (Qixue) Yang (W3C Invited Experts) joined.
-
-
2 participants left.
-
Ramprasad Gaddam (UnitedHealth Group) left.
-
Olvis Enrique Gil Ríos (W3C Invited Experts) left.
-
-
1 organization joined.
-
Capital One Discover Network joined.
-
-
1 organization left.
-
UnitedHealth Group left.
-
GitHub
w3c/vc-data-integrity
-
6 issues opened.
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373, by @swcurran.
-
SHoC: derive salts in the holder from `saltSeed` instead of carrying the full salts array in the base proof w3c/vc-data-integrity#372, by @studyzy.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369, by @studyzy.
-
Missing Step in Selective Disclosure (SIC approach serialize derive) w3c/vc-data-integrity#367, by @Wind4Greg.
-
RDFC-based cryptosuites do not specify `rdfDirection`; implementations already diverge on documents with `@direction` w3c/vc-data-integrity#366, by @shigeya.
-
-
7 issues received 64 new comments.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369 (18 comments by @filip26, @studyzy, @Wind4Greg)
-
SHoC: derive salts in the holder from `saltSeed` instead of carrying the full salts array in the base proof w3c/vc-data-integrity#372 (17 comments by @dlongley, @filip26, @studyzy, @Wind4Greg)
-
Technical Decisions and Options w3c/vc-data-integrity#362 (17 comments by @dlongley, @filip26, @msporny, @Wind4Greg)
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363 (6 comments by @antonymott, @Wind4Greg)
-
Bug: SHoC: derived proof reveals salts of non-disclosed claims, enabling offline guessing attacks (+ 2 algorithm inconsistencies) w3c/vc-data-integrity#370 (3 comments by @studyzy, @Wind4Greg)
-
RDFC-based cryptosuites do not specify `rdfDirection`; implementations already diverge on documents with `@direction` w3c/vc-data-integrity#366 (2 comments by @dlongley, @shigeya)
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373 (1 comment by @antonymott)
-
-
6 pull requests opened.
-
removed the postprocess block in TM w3c/vc-data-integrity#376, by @iherman.
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375, by @antonymott.
-
Fix SIC Approach Signature Filtering (attempt 2) w3c/vc-data-integrity#374, by @msporny.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371, by @Wind4Greg.
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368, by @Wind4Greg.
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365, by @Wind4Greg.
-
-
6 pull requests merged.
-
removed the postprocess block in TM w3c/vc-data-integrity#376.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371.
-
Fix SIC Approach Signature Filtering (attempt 2) w3c/vc-data-integrity#374.
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375.
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365.
-
Attempts to get rid of the js issues w3c/vc-data-integrity#364.
-
-
1 pull request closed.
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368.
-
-
5 pull requests received 25 new comments.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371 (10 comments by @dlongley, @TallTed, @Wind4Greg)
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368 (5 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375 (4 comments by @iherman, @msporny)
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365 (3 comments by @dlongley, @TallTed)
-
w3c/vc-data-model
-
3 issues opened.
-
domain of the validFrom and validUntil must be changed in the vocabulary w3c/vc-data-model#1651, by @iherman.
-
CSOAI — Verifiable Credentials for AI governance w3c/vc-data-model#1650, by @CSOAI-ORG.
-
Add `exchangeData` to `VerifiablePresentation` datatype w3c/vc-data-model#1649, by @msporny.
-
-
6 issues closed.
-
Structuring the security considerations section w3c/vc-data-model#1583.
-
Add a "localizeable value" term to address i18n concerns w3c/vc-data-model#1641.
-
Suggestion: Show mixed localized/non-localized arrays in i18n examples w3c/vc-data-model#1643.
-
https://www.w3.org/2018/credentials redirect missing Access-Control-Allow-Origin w3c/vc-data-model#1644.
-
Invalid JSON and @context in Example #31 w3c/vc-data-model#1642.
-
multiple comments on the introduction section w3c/vc-data-model#1592.
-
-
8 issues received 18 new comments.
-
domain of the validFrom and validUntil must be changed in the vocabulary w3c/vc-data-model#1651 (5 comments by @dlongley, @iherman, @msporny)
-
https://www.w3.org/2018/credentials redirect missing Access-Control-Allow-Origin w3c/vc-data-model#1644 (4 comments by @iherman, @msporny, @nissimsan)
-
Structuring the security considerations section w3c/vc-data-model#1583 (2 comments by @iherman, @msporny)
-
Add a "localizeable value" term to address i18n concerns w3c/vc-data-model#1641 (2 comments by @msporny)
-
Suggestion: Show mixed localized/non-localized arrays in i18n examples w3c/vc-data-model#1643 (2 comments by @msporny)
-
-
3 pull requests opened.
-
First version of the 2.1 version of the vocabulary. w3c/vc-data-model#1652, by @iherman.
-
Add an example of a mixed array of strings and language value objects w3c/vc-data-model#1647, by @msporny.
-
Export definition of language value object; revise prose. w3c/vc-data-model#1646, by @msporny.
-
-
4 pull requests merged.
-
Rephrase securing requirement as constraint on securing (vs conformance). w3c/vc-data-model#1645.
-
Add an example of a mixed array of strings and language value objects w3c/vc-data-model#1647.
-
Export definition of language value object; revise prose. w3c/vc-data-model#1646.
-
Update introduction sections for clarity. w3c/vc-data-model#1636.
-
-
5 pull requests received 41 new comments.
-
First version of the 2.1 version of the vocabulary. w3c/vc-data-model#1652 (15 comments by @dmitrizagidulin, @iherman, @TallTed)
-
Add an example of a mixed array of strings and language value objects w3c/vc-data-model#1647 (10 comments by @aphillips, @filip26, @iherman, @msporny)
-
Export definition of language value object; revise prose. w3c/vc-data-model#1646 (8 comments by @aphillips, @filip26, @iherman, @msporny)
-
Rephrase securing requirement as constraint on securing (vs conformance). w3c/vc-data-model#1645 (6 comments by @dmitrizagidulin, @iherman, @jandrieu, @msporny, @TallTed)
-
w3c/vc-render-method
-
5 issues opened.
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86, by @PatStLouis.
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84, by @TallTed.
-
Compare "output_descriptors" from DIF's Credential Manifest to the "card" render method approach w3c/vc-render-method#83, by @BigBlueHat.
-
Compare "card" stuff to `cardDesigns.js` JSON from Bedrock Vue Wallet. w3c/vc-render-method#82, by @BigBlueHat.
-
Consider combining `renderProperty` and `fields` from the fka `cards` render method. w3c/vc-render-method#81, by @BigBlueHat.
-
-
1 issue closed.
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70.
-
-
6 issues received 18 new comments.
-
Consider combining `renderProperty` and `fields` from the fka `cards` render method. w3c/vc-render-method#81 (10 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman)
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86 (2 comments by @dmitrizagidulin, @ottonomy)
-
Compare "card" stuff to `cardDesigns.js` JSON from Bedrock Vue Wallet. w3c/vc-render-method#82 (2 comments by @BigBlueHat, @dlongley)
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77 (2 comments by @dlongley, @dmitrizagidulin)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70 (1 comment by @dmitrizagidulin)
-
-
2 pull requests opened.
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85, by @dmitrizagidulin.
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80, by @alexfigtree.
-
-
3 pull requests merged.
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76.
-
Address editorial comments on JSON cards. w3c/vc-render-method#73.
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72.
-
-
2 pull requests closed.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74.
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80.
-
-
5 pull requests received 22 new comments.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74 (8 comments by @BigBlueHat, @dmitrizagidulin, @TallTed)
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76 (6 comments by @dlongley, @dmitrizagidulin, @TallTed)
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80 (6 comments by @alexfigtree, @davidlehn, @iherman, @TallTed, @w3cbot)
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85 (1 comment by @dmitrizagidulin)
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72 (1 comment by @dmitrizagidulin)
-
w3c/vc-jose-cose
-
1 issue received 1 new comment.
w3c/cid
-
3 pull requests received 6 new comments.
-
Allow for fragment identifier in document.id w3c/cid#168 (4 comments by @elf-pavlik, @filip26, @msporny, @uvdsl)
-
w3c/vc-recognized-entities
-
5 issues opened.
-
revisit the data model w3c/vc-recognized-entities#135, by @onthebreeze.
-
add the registered / recognised entity ID to the Data model w3c/vc-recognized-entities#132, by @onthebreeze.
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131, by @npdoty.
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130, by @npdoty.
-
`RecognizedEntityCredential` type used at two separate layers w3c/vc-recognized-entities#125, by @kezike.
-
-
9 issues closed.
-
Add Privacy Considerations on Verifiable Recognition Credential delivery mechanisms w3c/vc-recognized-entities#56.
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105.
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91.
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50.
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112.
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111.
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115.
-
Examples are USA-centric? w3c/vc-recognized-entities#110.
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71.
-
-
20 issues received 64 new comments.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (16 comments by @dlongley, @iherman, @msporny, @paulfdietrich, @philarcher)
-
revisit the data model w3c/vc-recognized-entities#135 (9 comments by @dlongley, @onthebreeze, @philarcher)
-
Create vocabulary term definitions and anchors in spec w3c/vc-recognized-entities#92 (7 comments by @iherman, @msporny)
-
Rethinking verifying recognition chains w3c/vc-recognized-entities#85 (5 comments by @dlongley, @iherman, @msporny, @onthebreeze)
-
`RecognizedEntityCredential` type used at two separate layers w3c/vc-recognized-entities#125 (3 comments by @Giampieroz, @kezike, @msporny)
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131 (2 comments by @msporny)
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130 (2 comments by @msporny)
-
add the registered / recognised entity ID to the Data model w3c/vc-recognized-entities#132 (2 comments by @dlongley, @Fak3)
-
Add Privacy Considerations on Verifiable Recognition Credential delivery mechanisms w3c/vc-recognized-entities#56 (2 comments by @msporny)
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105 (2 comments by @msporny)
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91 (2 comments by @msporny)
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50 (2 comments by @msporny)
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112 (2 comments by @msporny)
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111 (2 comments by @msporny)
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117 (1 comment by @ottonomy)
-
Security and Privacy Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#96 (1 comment by @msporny)
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46 (1 comment by @msporny)
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115 (1 comment by @msporny)
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71 (1 comment by @msporny)
-
-
12 pull requests opened.
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138, by @msporny.
-
Add SSRF threat and mitigation. w3c/vc-recognized-entities#137, by @msporny.
-
Add maxDuration to limit DoS attacks. w3c/vc-recognized-entities#136, by @msporny.
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134, by @msporny.
-
Specify how to properly use digestMultibase. w3c/vc-recognized-entities#133, by @msporny.
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129, by @msporny.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128, by @msporny.
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127, by @msporny.
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126, by @msporny.
-
Add example that includes different languages. w3c/vc-recognized-entities#124, by @msporny.
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123, by @msporny.
-
Draft vocabulary definition w3c/vc-recognized-entities#122, by @iherman.
-
-
7 pull requests merged.
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128.
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127.
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126.
-
Add example that includes different languages. w3c/vc-recognized-entities#124.
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123.
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119.
-
-
11 pull requests received 98 new comments.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128 (16 comments by @dlongley, @iherman, @msporny, @TallTed, @vnlemanhthanh)
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138 (10 comments by @onthebreeze, @TallTed)
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129 (9 comments by @dlongley, @iherman, @kezike, @msporny)
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123 (8 comments by @aphillips, @iherman, @msporny, @TallTed)
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add example that includes different languages. w3c/vc-recognized-entities#124 (7 comments by @iherman, @msporny, @shigeya)
-
Add maxDuration to limit DoS attacks. w3c/vc-recognized-entities#136 (5 comments by @dlongley, @msporny)
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134 (4 comments by @dlongley)
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126 (4 comments by @iherman, @msporny, @shigeya)
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119 (1 comment by @msporny)
w3c/vcalm
-
11 issues opened.
-
Sync threat file names with changes to threat names w3c/vcalm#726, by @eric-schuh.
-
`created` field is defined as a string? w3c/vcalm#725, by @aphillips.
-
Use more globally correct example; editorial nit w3c/vcalm#724, by @aphillips.
-
Documenting localizable text in examples w3c/vcalm#723, by @aphillips.
-
Review R41 on T38 w3c/vcalm#722, by @eric-schuh.
-
Add QR Code shoulder surfing to threat model w3c/vcalm#719, by @msporny.
-
Question: should we add ipex to protocols list for KERI/ACDC ecosystem? w3c/vcalm#718, by @ottonomy.
-
Add example VPR that would be used with credentialOffer w3c/vcalm#717, by @eric-schuh.
-
Handle property duplication problem from oneOf pattern w3c/vcalm#715, by @eric-schuh.
-
Update threat-model/README.md to be VCALM specific w3c/vcalm#714, by @jandrieu.
-
1 issue closed.
-
5 issues received 13 new comments.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686 (8 comments by @BigBlueHat, @iherman, @TallTed)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @dmitrizagidulin)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @kezike)
-
Consider to introduce a manifest describing entry points ('static' endpoints) w3c/vcalm#433 (1 comment by @filip26)
-
-
7 pull requests opened.
-
Specify proper format for date/time properties w3c/vcalm#729, by @kezike.
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728, by @eric-schuh.
-
Replace `firstName` with i18n appropriate `givenName` in VPR example w3c/vcalm#727, by @kezike.
-
Apply git renormalize to mixed line ending files w3c/vcalm#721, by @ottonomy.
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720, by @msporny.
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716, by @eric-schuh.
-
-
9 pull requests merged.
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716.
-
Apply git renormalize to mixed line ending files w3c/vcalm#721.
-
Fix broken link for "transformation" w3c/vcalm#708.
-
Fix oneOf + required rendering issues w3c/vcalm#692.
-
Updated respec-oas to version 1.0.2 w3c/vcalm#706.
-
-
3 pull requests closed.
-
Adding `credentialOffer` to VPR w3c/vcalm#705.
-
-
12 pull requests received 99 new comments.
-
Resolve tension between Threat Model and Privacy & Security Considerations w3c/vcalm#711 (41 comments by @eric-schuh, @kezike, @PatStLouis, @TallTed)
-
Add ExchangeVerifiablePresentation option to support exchange specific data w3c/vcalm#713 (16 comments by @dlongley, @eric-schuh, @kezike, @msporny, @ottonomy, @TallTed)
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720 (14 comments by @dlongley, @eric-schuh, @msporny, @ottonomy, @TallTed)
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716 (11 comments by @dlongley, @eric-schuh, @kezike, @TallTed)
-
Adding `credentialOffer` to VPR w3c/vcalm#705 (6 comments by @dlongley, @eric-schuh, @ottonomy, @PatStLouis, @TallTed)
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728 (2 comments by @dlongley, @PatStLouis)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (2 comments by @eric-schuh, @TallTed)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (2 comments by @PatStLouis, @TallTed)
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691 (2 comments by @kezike, @PatStLouis)
-
Replace `firstName` with i18n appropriate `givenName` in VPR example w3c/vcalm#727 (1 comment by @ottonomy)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (1 comment by @PatStLouis)
-
w3c/vc-bitstring-status-list
-
2 issues received 2 new comments.
-
The explainer needs more clarity around example bitstring list I am unable to decode the example bitstring status list w3c/vc-bitstring-status-list#201 (1 comment by @wes-smith)
-
5 pull requests opened.
-
Post FPWD Publication setup w3c/vc-bitstring-status-list#216, by @iherman.
-
Updated respecConfig for former editors w3c/vc-bitstring-status-list#215, by @iherman.
-
FPWD publish date set to Sept 24 w3c/vc-bitstring-status-list#214, by @iherman.
-
added authors'/editors' version notes and copied the diagrams w3c/vc-bitstring-status-list#213, by @iherman.
-
Prepare document for FPWD, add Terse content, administrative changes. w3c/vc-bitstring-status-list#212, by @wes-smith.
-
-
4 pull requests merged.
-
Updated respecConfig for former editors w3c/vc-bitstring-status-list#215.
-
FPWD publish date set to Sept 24 w3c/vc-bitstring-status-list#214.
-
Prepare document for FPWD, add Terse content, administrative changes. w3c/vc-bitstring-status-list#212.
-
added authors'/editors' version notes and copied the diagrams w3c/vc-bitstring-status-list#213.
-
-
4 pull requests received 15 new comments.
-
Prepare document for FPWD, add Terse content, administrative changes. w3c/vc-bitstring-status-list#212 (7 comments by @iherman, @msporny, @wes-smith)
-
Updated respecConfig for former editors w3c/vc-bitstring-status-list#215 (6 comments by @dlongley, @iherman, @wes-smith)
-
added authors'/editors' version notes and copied the diagrams w3c/vc-bitstring-status-list#213 (1 comment by @wes-smith)
-
w3c/vc-test-suite-implementations
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Bring in latest ZCAP expiration monitoring. w3c/vc-test-suite-implementations#127, by @BigBlueHat.
-
-
1 pull request merged.
-
Add jose-cose tags to Trential w3c/vc-test-suite-implementations#124.
-
-
1 pull request received 1 new comment.
w3c/vc-barcodes
-
3 issues opened.
-
Improve examples (state => region, use metric units?) w3c/vc-barcodes#73, by @aphillips.
-
VCB example and non-ASCII w3c/vc-barcodes#72, by @aphillips.
-
newline reference could use character template w3c/vc-barcodes#71, by @aphillips.
-
-
1 issue received 1 new comment.
w3c/vc-di-quantum-resistant
-
1 issue opened.
-
Consistency of cryptosuite tables (editorial) w3c/vc-di-quantum-resistant#44, by @iherman.
-
-
1 pull request opened.
-
Refactor to Use Common Selective Disclosure Algorithms w3c/vc-di-quantum-resistant#43, by @Wind4Greg.
-
-
2 pull requests merged.
-
Refactor to Use Common Selective Disclosure Algorithms w3c/vc-di-quantum-resistant#43.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42.
-
-
1 pull request received 3 new comments.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42 (3 comments by @iherman, @TallTed)
-
w3c/vc-di-bbs
-
1 issue opened.
-
Generalize and Modularize Optional Features w3c/vc-di-bbs#207, by @Wind4Greg.
-
-
1 pull request opened.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206, by @Wind4Greg.
-
-
2 pull requests merged.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206.
-
Editorial: Fix href for Blind BBS Signatures w3c/vc-di-bbs#205.
-
-
1 pull request received 3 new comments.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206 (3 comments by @dlongley, @msporny, @TallTed)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 issue opened.
-
Status of Docker Integration (TODO in README) w3c/vc-di-ed25519signature2020-test-suite#66, by @Olvisgil.
-
w3c/vc-confidence-method
-
4 issues opened.
-
Add expectation that confidence methods SHOULD be selectively disclosable w3c/vc-confidence-method#51, by @jandrieu.
-
Biometric model and vector data might be combined since they are associated with one another w3c/vc-confidence-method#50, by @denkeni.
-
Explain how ids/types are used to fetch external documents w3c/vc-confidence-method#49, by @msporny.
-
Add example of cryptographic-key-based confidenceMethod that does not depend on a VerifiablePresentation w3c/vc-confidence-method#48, by @msporny.
-
-
2 issues closed.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37.
-
Add did-auth as initial confidence method w3c/vc-confidence-method#20.
-
-
4 issues received 4 new comments.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37 (1 comment by @jandrieu)
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (1 comment by @denkeni)
-
-
1 pull request merged.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43.
-
-
1 pull request received 12 new comments.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43 (12 comments by @denkeni, @iherman, @jandrieu, @msporny)
-
w3c/vc-di-ecdsa
-
1 pull request opened.
-
Selective Disclosure Algorithms and Functions Refactoring w3c/vc-di-ecdsa#107, by @Wind4Greg.
-
-
2 pull requests merged.
-
Selective Disclosure Algorithms and Functions Refactoring w3c/vc-di-ecdsa#107.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106.
-
-
1 pull request received 1 new comment.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106 (1 comment by @Wind4Greg)
-
w3c/vc-overview
-
1 pull request opened.
-
Incorporating Pierre-Antoine's comments w3c/vc-overview#46, by @iherman.
-
-
1 pull request merged.
-
Incorporating Pierre-Antoine's comments w3c/vc-overview#46.
-
-
2 pull requests received 4 new comments.
w3c/vcalm-test-suite
-
1 issue opened.
-
LICENSE.md points at the wrong license w3c/vcalm-test-suite#5, by @tidoust.
-
-
1 issue received 1 new comment.
w3c/vc-use-cases
-
2 issues closed.
-
New user/holder task - Receive and process claim request w3c/vc-use-cases#140.
-
Request for new section 6.3 How a Verifiable Credential may be issued within a process w3c/vc-use-cases#144.
-
-
1 issue received 2 new comments.
-
Pull request preview images are missing (links are broken) w3c/vc-use-cases#170 (2 comments by @jandrieu, @KDean-Dolphin)
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request merged.
-
Add config directory w3c/vc-bitstring-status-list-test-suite#68.
-
-
1 pull request received 2 new comments.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-bitstring-status-list-test-suite#76 (2 comments by @BigBlueHat, @PatStLouis)
-
w3c/vc-data-model-2.0-test-suite
-
1 pull request merged.
-
Fix enveloped proof existence assertion w3c/vc-data-model-2.0-test-suite#174.
-
w3c/vc-di-eddsa
-
1 pull request merged.
-
Reuse Common Algorithms from VC-DI-1.1 w3c/vc-di-eddsa#118.
-
-
1 pull request received 2 new comments.
w3c/vc-jose-cose-test-suite
-
1 pull request opened.
-
update ci node 24 w3c/vc-jose-cose-test-suite#36, by @BigBlueHat.
-
-
2 pull requests merged.
-
Add trential test config w3c/vc-jose-cose-test-suite#34.
-
Add CODEOWNERS file. w3c/vc-jose-cose-test-suite#35.
-
-
1 pull request received 1 new comment.
VC Barcodes and Data Integrity
Past meetings
-
4 meetings of the VC Barcodes and Data Integrity.
GitHub
w3c/vc-data-integrity
-
6 issues opened in the VC Barcodes and Data Integrity.
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373, by @swcurran.
-
SHoC: derive salts in the holder from `saltSeed` instead of carrying the full salts array in the base proof w3c/vc-data-integrity#372, by @studyzy.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369, by @studyzy.
-
Missing Step in Selective Disclosure (SIC approach serialize derive) w3c/vc-data-integrity#367, by @Wind4Greg.
-
RDFC-based cryptosuites do not specify `rdfDirection`; implementations already diverge on documents with `@direction` w3c/vc-data-integrity#366, by @shigeya.
-
-
7 issues in the VC Barcodes and Data Integrity received 64 new comments.
-
Idea: Merkle-tree aggregation mode for SHoC to reduce derived proof size from O(N) to O(k log N) w3c/vc-data-integrity#369 (18 comments by @filip26, @studyzy, @Wind4Greg)
-
SHoC: derive salts in the holder from `saltSeed` instead of carrying the full salts array in the base proof w3c/vc-data-integrity#372 (17 comments by @dlongley, @filip26, @studyzy, @Wind4Greg)
-
Technical Decisions and Options w3c/vc-data-integrity#362 (17 comments by @dlongley, @filip26, @msporny, @Wind4Greg)
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363 (6 comments by @antonymott, @Wind4Greg)
-
Bug: SHoC: derived proof reveals salts of non-disclosed claims, enabling offline guessing attacks (+ 2 algorithm inconsistencies) w3c/vc-data-integrity#370 (3 comments by @studyzy, @Wind4Greg)
-
RDFC-based cryptosuites do not specify `rdfDirection`; implementations already diverge on documents with `@direction` w3c/vc-data-integrity#366 (2 comments by @dlongley, @shigeya)
-
Using key pre-rotation in Data Integrity to enable quantum resistance with current cryptography for certain use cases w3c/vc-data-integrity#373 (1 comment by @antonymott)
-
-
6 pull requests opened in the VC Barcodes and Data Integrity.
-
removed the postprocess block in TM w3c/vc-data-integrity#376, by @iherman.
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375, by @antonymott.
-
Fix SIC Approach Signature Filtering (attempt 2) w3c/vc-data-integrity#374, by @msporny.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371, by @Wind4Greg.
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368, by @Wind4Greg.
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365, by @Wind4Greg.
-
-
6 pull requests merged in the VC Barcodes and Data Integrity.
-
removed the postprocess block in TM w3c/vc-data-integrity#376.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371.
-
Fix SIC Approach Signature Filtering (attempt 2) w3c/vc-data-integrity#374.
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375.
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365.
-
Attempts to get rid of the js issues w3c/vc-data-integrity#364.
-
-
1 pull request closed in the VC Barcodes and Data Integrity.
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368.
-
-
5 pull requests in the VC Barcodes and Data Integrity received 25 new comments.
-
Fix Salted Hash of Claims Algorithms w3c/vc-data-integrity#371 (10 comments by @dlongley, @TallTed, @Wind4Greg)
-
Fix SIC Approach Signature Filtering w3c/vc-data-integrity#368 (5 comments by @dlongley, @msporny, @TallTed, @Wind4Greg)
-
chore: transition Threat Model to DNOTE on 2026-10-08 w3c/vc-data-integrity#375 (4 comments by @iherman, @msporny)
-
Update to define the SIC proof header bytes w3c/vc-data-integrity#365 (3 comments by @dlongley, @TallTed)
-
w3c/vc-barcodes
-
3 issues opened in the VC Barcodes and Data Integrity.
-
Improve examples (state => region, use metric units?) w3c/vc-barcodes#73, by @aphillips.
-
VCB example and non-ASCII w3c/vc-barcodes#72, by @aphillips.
-
newline reference could use character template w3c/vc-barcodes#71, by @aphillips.
-
-
1 issue in the VC Barcodes and Data Integrity received 1 new comment.
w3c/vc-di-quantum-resistant
-
1 issue opened in the VC Barcodes and Data Integrity.
-
Consistency of cryptosuite tables (editorial) w3c/vc-di-quantum-resistant#44, by @iherman.
-
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Refactor to Use Common Selective Disclosure Algorithms w3c/vc-di-quantum-resistant#43, by @Wind4Greg.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Refactor to Use Common Selective Disclosure Algorithms w3c/vc-di-quantum-resistant#43.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42.
-
-
1 pull request in the VC Barcodes and Data Integrity received 3 new comments.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42 (3 comments by @iherman, @TallTed)
-
w3c/vc-di-bbs
-
1 issue opened in the VC Barcodes and Data Integrity.
-
Generalize and Modularize Optional Features w3c/vc-di-bbs#207, by @Wind4Greg.
-
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206, by @Wind4Greg.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206.
-
Editorial: Fix href for Blind BBS Signatures w3c/vc-di-bbs#205.
-
-
1 pull request in the VC Barcodes and Data Integrity received 3 new comments.
-
Refactor to use Common SD Algorithms w3c/vc-di-bbs#206 (3 comments by @dlongley, @msporny, @TallTed)
-
w3c/vc-di-ecdsa
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Selective Disclosure Algorithms and Functions Refactoring w3c/vc-di-ecdsa#107, by @Wind4Greg.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Selective Disclosure Algorithms and Functions Refactoring w3c/vc-di-ecdsa#107.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106.
-
-
1 pull request in the VC Barcodes and Data Integrity received 1 new comment.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106 (1 comment by @Wind4Greg)
-
w3c/vc-di-eddsa
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Reuse Common Algorithms from VC-DI-1.1 w3c/vc-di-eddsa#118.
-
-
1 pull request in the VC Barcodes and Data Integrity received 2 new comments.
VC Render Method
GitHub
w3c/vc-render-method
-
5 issues opened in the VC Render Method.
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86, by @PatStLouis.
-
there are some bad links in and to the Threat Model w3c/vc-render-method#84, by @TallTed.
-
Compare "output_descriptors" from DIF's Credential Manifest to the "card" render method approach w3c/vc-render-method#83, by @BigBlueHat.
-
Compare "card" stuff to `cardDesigns.js` JSON from Bedrock Vue Wallet. w3c/vc-render-method#82, by @BigBlueHat.
-
Consider combining `renderProperty` and `fields` from the fka `cards` render method. w3c/vc-render-method#81, by @BigBlueHat.
-
-
1 issue closed in the VC Render Method.
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70.
-
-
6 issues in the VC Render Method received 18 new comments.
-
Consider combining `renderProperty` and `fields` from the fka `cards` render method. w3c/vc-render-method#81 (10 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman)
-
Rendering behavior when verification fails (revoked/suspended status, invalid proof, expired validity) w3c/vc-render-method#86 (2 comments by @dmitrizagidulin, @ottonomy)
-
Compare "card" stuff to `cardDesigns.js` JSON from Bedrock Vue Wallet. w3c/vc-render-method#82 (2 comments by @BigBlueHat, @dlongley)
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77 (2 comments by @dlongley, @dmitrizagidulin)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70 (1 comment by @dmitrizagidulin)
-
-
2 pull requests opened in the VC Render Method.
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85, by @dmitrizagidulin.
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80, by @alexfigtree.
-
-
3 pull requests merged in the VC Render Method.
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76.
-
Address editorial comments on JSON cards. w3c/vc-render-method#73.
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72.
-
-
2 pull requests closed in the VC Render Method.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74.
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80.
-
-
5 pull requests in the VC Render Method received 22 new comments.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74 (8 comments by @BigBlueHat, @dmitrizagidulin, @TallTed)
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76 (6 comments by @dlongley, @dmitrizagidulin, @TallTed)
-
Fix broken data-cite link to VC-DATA-MODEL-2.1 threat model w3c/vc-render-method#80 (6 comments by @alexfigtree, @davidlehn, @iherman, @TallTed, @w3cbot)
-
Rename 'nfc' to 'static', add 'deliveryMethod' property. w3c/vc-render-method#85 (1 comment by @dmitrizagidulin)
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72 (1 comment by @dmitrizagidulin)
-
VC Recognized Entities
Past meetings
-
4 meetings of the VC Recognized Entities.
Participants
-
2 participants joined the VC Recognized Entities.
-
Nate Otto joined.
-
James Richards joined.
-
GitHub
w3c/vc-recognized-entities
-
5 issues opened in the VC Recognized Entities.
-
revisit the data model w3c/vc-recognized-entities#135, by @onthebreeze.
-
add the registered / recognised entity ID to the Data model w3c/vc-recognized-entities#132, by @onthebreeze.
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131, by @npdoty.
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130, by @npdoty.
-
`RecognizedEntityCredential` type used at two separate layers w3c/vc-recognized-entities#125, by @kezike.
-
-
9 issues closed in the VC Recognized Entities.
-
Add Privacy Considerations on Verifiable Recognition Credential delivery mechanisms w3c/vc-recognized-entities#56.
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105.
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91.
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50.
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112.
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111.
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115.
-
Examples are USA-centric? w3c/vc-recognized-entities#110.
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71.
-
-
20 issues in the VC Recognized Entities received 64 new comments.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (16 comments by @dlongley, @iherman, @msporny, @paulfdietrich, @philarcher)
-
revisit the data model w3c/vc-recognized-entities#135 (9 comments by @dlongley, @onthebreeze, @philarcher)
-
Create vocabulary term definitions and anchors in spec w3c/vc-recognized-entities#92 (7 comments by @iherman, @msporny)
-
Rethinking verifying recognition chains w3c/vc-recognized-entities#85 (5 comments by @dlongley, @iherman, @msporny, @onthebreeze)
-
`RecognizedEntityCredential` type used at two separate layers w3c/vc-recognized-entities#125 (3 comments by @Giampieroz, @kezike, @msporny)
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131 (2 comments by @msporny)
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130 (2 comments by @msporny)
-
add the registered / recognised entity ID to the Data model w3c/vc-recognized-entities#132 (2 comments by @dlongley, @Fak3)
-
Add Privacy Considerations on Verifiable Recognition Credential delivery mechanisms w3c/vc-recognized-entities#56 (2 comments by @msporny)
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105 (2 comments by @msporny)
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91 (2 comments by @msporny)
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50 (2 comments by @msporny)
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112 (2 comments by @msporny)
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111 (2 comments by @msporny)
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117 (1 comment by @ottonomy)
-
Security and Privacy Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#96 (1 comment by @msporny)
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46 (1 comment by @msporny)
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115 (1 comment by @msporny)
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71 (1 comment by @msporny)
-
-
12 pull requests opened in the VC Recognized Entities.
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138, by @msporny.
-
Add SSRF threat and mitigation. w3c/vc-recognized-entities#137, by @msporny.
-
Add maxDuration to limit DoS attacks. w3c/vc-recognized-entities#136, by @msporny.
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134, by @msporny.
-
Specify how to properly use digestMultibase. w3c/vc-recognized-entities#133, by @msporny.
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129, by @msporny.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128, by @msporny.
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127, by @msporny.
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126, by @msporny.
-
Add example that includes different languages. w3c/vc-recognized-entities#124, by @msporny.
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123, by @msporny.
-
Draft vocabulary definition w3c/vc-recognized-entities#122, by @iherman.
-
-
7 pull requests merged in the VC Recognized Entities.
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128.
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127.
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126.
-
Add example that includes different languages. w3c/vc-recognized-entities#124.
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123.
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119.
-
-
11 pull requests in the VC Recognized Entities received 98 new comments.
-
Refactor Algorithms to extract Recognition Validation algorithm. w3c/vc-recognized-entities#128 (16 comments by @dlongley, @iherman, @msporny, @TallTed, @vnlemanhthanh)
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138 (10 comments by @onthebreeze, @TallTed)
-
Explain most-to-least privacy preserving way to fetch a recognized entity credential w3c/vc-recognized-entities#129 (9 comments by @dlongley, @iherman, @kezike, @msporny)
-
Allow legalName to be a language value object. w3c/vc-recognized-entities#123 (8 comments by @aphillips, @iherman, @msporny, @TallTed)
-
Add Holder-based Delivery section. w3c/vc-recognized-entities#127 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add example that includes different languages. w3c/vc-recognized-entities#124 (7 comments by @iherman, @msporny, @shigeya)
-
Add maxDuration to limit DoS attacks. w3c/vc-recognized-entities#136 (5 comments by @dlongley, @msporny)
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134 (4 comments by @dlongley)
-
Remove Use Cases document, revise editors/authors w3c/vc-recognized-entities#126 (4 comments by @iherman, @msporny, @shigeya)
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119 (1 comment by @msporny)
VC API for Lifecycle Management
Past meetings
-
5 meetings of the VC API for Lifecycle Management.
Participants
-
1 participant left the VC API for Lifecycle Management.
-
Olvis Enrique Gil Ríos left.
-
GitHub
w3c/vcalm
-
11 issues opened in the VC API for Lifecycle Management.
-
Sync threat file names with changes to threat names w3c/vcalm#726, by @eric-schuh.
-
`created` field is defined as a string? w3c/vcalm#725, by @aphillips.
-
Use more globally correct example; editorial nit w3c/vcalm#724, by @aphillips.
-
Documenting localizable text in examples w3c/vcalm#723, by @aphillips.
-
Review R41 on T38 w3c/vcalm#722, by @eric-schuh.
-
Add QR Code shoulder surfing to threat model w3c/vcalm#719, by @msporny.
-
Question: should we add ipex to protocols list for KERI/ACDC ecosystem? w3c/vcalm#718, by @ottonomy.
-
Add example VPR that would be used with credentialOffer w3c/vcalm#717, by @eric-schuh.
-
Handle property duplication problem from oneOf pattern w3c/vcalm#715, by @eric-schuh.
-
Update threat-model/README.md to be VCALM specific w3c/vcalm#714, by @jandrieu.
-
1 issue closed in the VC API for Lifecycle Management.
-
5 issues in the VC API for Lifecycle Management received 13 new comments.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686 (8 comments by @BigBlueHat, @iherman, @TallTed)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @dmitrizagidulin)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @kezike)
-
Consider to introduce a manifest describing entry points ('static' endpoints) w3c/vcalm#433 (1 comment by @filip26)
-
-
7 pull requests opened in the VC API for Lifecycle Management.
-
Specify proper format for date/time properties w3c/vcalm#729, by @kezike.
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728, by @eric-schuh.
-
Replace `firstName` with i18n appropriate `givenName` in VPR example w3c/vcalm#727, by @kezike.
-
Apply git renormalize to mixed line ending files w3c/vcalm#721, by @ottonomy.
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720, by @msporny.
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716, by @eric-schuh.
-
-
9 pull requests merged in the VC API for Lifecycle Management.
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716.
-
Apply git renormalize to mixed line ending files w3c/vcalm#721.
-
Fix broken link for "transformation" w3c/vcalm#708.
-
Fix oneOf + required rendering issues w3c/vcalm#692.
-
Updated respec-oas to version 1.0.2 w3c/vcalm#706.
-
-
3 pull requests closed in the VC API for Lifecycle Management.
-
Adding `credentialOffer` to VPR w3c/vcalm#705.
-
-
12 pull requests in the VC API for Lifecycle Management received 99 new comments.
-
Resolve tension between Threat Model and Privacy & Security Considerations w3c/vcalm#711 (41 comments by @eric-schuh, @kezike, @PatStLouis, @TallTed)
-
Add ExchangeVerifiablePresentation option to support exchange specific data w3c/vcalm#713 (16 comments by @dlongley, @eric-schuh, @kezike, @msporny, @ottonomy, @TallTed)
-
Document QR Code shoulder surfing threat and mitigations w3c/vcalm#720 (14 comments by @dlongley, @eric-schuh, @msporny, @ottonomy, @TallTed)
-
Adding appendix with swimlane examples (#2) w3c/vcalm#716 (11 comments by @dlongley, @eric-schuh, @kezike, @TallTed)
-
Adding `credentialOffer` to VPR w3c/vcalm#705 (6 comments by @dlongley, @eric-schuh, @ottonomy, @PatStLouis, @TallTed)
-
Adding credentialOffer parameter to the VerifiablePresenationRequest w3c/vcalm#728 (2 comments by @dlongley, @PatStLouis)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (2 comments by @eric-schuh, @TallTed)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (2 comments by @PatStLouis, @TallTed)
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691 (2 comments by @kezike, @PatStLouis)
-
Replace `firstName` with i18n appropriate `givenName` in VPR example w3c/vcalm#727 (1 comment by @ottonomy)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (1 comment by @PatStLouis)
-
w3c/vcalm-test-suite
-
1 issue opened in the VC API for Lifecycle Management.
-
LICENSE.md points at the wrong license w3c/vcalm-test-suite#5, by @tidoust.
-
-
1 issue in the VC API for Lifecycle Management received 1 new comment.
VC Confidence Method
GitHub
w3c/vc-confidence-method
-
4 issues opened in the VC Confidence Method.
-
Add expectation that confidence methods SHOULD be selectively disclosable w3c/vc-confidence-method#51, by @jandrieu.
-
Biometric model and vector data might be combined since they are associated with one another w3c/vc-confidence-method#50, by @denkeni.
-
Explain how ids/types are used to fetch external documents w3c/vc-confidence-method#49, by @msporny.
-
Add example of cryptographic-key-based confidenceMethod that does not depend on a VerifiablePresentation w3c/vc-confidence-method#48, by @msporny.
-
-
2 issues closed in the VC Confidence Method.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37.
-
Add did-auth as initial confidence method w3c/vc-confidence-method#20.
-
-
4 issues in the VC Confidence Method received 4 new comments.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37 (1 comment by @jandrieu)
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (1 comment by @denkeni)
-
-
1 pull request merged in the VC Confidence Method.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43.
-
-
1 pull request in the VC Confidence Method received 12 new comments.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43 (12 comments by @denkeni, @iherman, @jandrieu, @msporny)
-
TR publications
-
22 documents published.
-
Verifiable Credential Forgery Defense v1.0 published twice as a Working Draft. History of Verifiable Credential Forgery Defense v1.0
-
Recognized Entities v1.0 published 4 times as a Working Draft. History of Recognized Entities v1.0
-
Verifiable Credential Barcodes v1.0 published twice as a Working Draft. History of Verifiable Credential Barcodes v1.0
-
Verifiable Credential Rendering Methods v1.0 published twice as a Working Draft. History of Verifiable Credential Rendering Methods v1.0
-
VCALM v1.0 published 5 times as a Working Draft. History of VCALM v1.0
-
Verifiable Credential Confidence Methods v1.0 published as a Working Draft. History of Verifiable Credential Confidence Methods v1.0
-
Verifiable Credentials Data Model v2.1 published twice as a Working Draft. History of Verifiable Credentials Data Model v2.1
-
Verifiable Credentials Overview v1.1 published 4 times as a Draft Note. History of Verifiable Credentials Overview v1.1
-
Past meetings
Participants
-
3 participants joined.
-
Antony Mott (W3C Invited Experts) joined.
-
Brandon Maslen (Microsoft Corporation) joined.
-
James Richards (W3C Invited Experts) joined.
-
GitHub
w3c/vc-recognized-entities
-
11 issues opened.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121, by @philarcher.
-
Create test suite for VC Recognized Entities w3c/vc-recognized-entities#120, by @msporny.
-
Provide guidance related to data URLs when used with outputValidation and other object types w3c/vc-recognized-entities#118, by @msporny.
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117, by @iherman.
-
Determine alignment with OpenID Federation w3c/vc-recognized-entities#116, by @msporny.
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115, by @TallTed.
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112, by @aphillips.
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111, by @aphillips.
-
Examples are USA-centric? w3c/vc-recognized-entities#110, by @aphillips.
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109, by @tsnyder-gs1us.
-
Refine UNGRID / UNTP / UNVTD Example w3c/vc-recognized-entities#107, by @msporny.
-
-
13 issues closed.
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49.
-
Federated Identifier use case w3c/vc-recognized-entities#74.
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66.
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86.
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63.
-
Add ref to Forgery Defense to threat model w3c/vc-recognized-entities#100.
-
Threat Model: diagram box type cues w3c/vc-recognized-entities#87.
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109.
-
Use Cases and Applications for this data model w3c/vc-recognized-entities#51.
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48.
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88.
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77.
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89.
-
-
25 issues received 67 new comments.
-
Refine UNGRID / UNTP / UNVTD Example w3c/vc-recognized-entities#107 (11 comments by @iherman, @JohnOnGH, @msporny, @TallTed)
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117 (10 comments by @iherman, @msporny, @ottomorac, @peacekeeper, @swcurran)
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71 (5 comments by @iherman, @kezike, @msporny)
-
Provide guidance related to data URLs when used with outputValidation and other object types w3c/vc-recognized-entities#118 (4 comments by @iherman, @paulfdietrich, @philarcher)
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111 (4 comments by @aphillips, @iherman, @msporny)
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112 (3 comments by @iherman, @msporny, @TallTed)
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46 (2 comments by @paulfdietrich)
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86 (2 comments by @msporny)
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109 (2 comments by @iherman, @msporny)
-
Use Cases and Applications for this data model w3c/vc-recognized-entities#51 (2 comments by @iherman, @msporny)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (2 comments by @iherman, @msporny)
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91 (2 comments by @iherman, @msporny)
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89 (2 comments by @iherman, @onthebreeze)
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (1 comment by @paulfdietrich)
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115 (1 comment by @iherman)
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49 (1 comment by @msporny)
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @msporny)
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88 (1 comment by @msporny)
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119, by @kezike.
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114, by @msporny.
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113, by @msporny.
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108, by @philarcher.
-
-
4 pull requests merged.
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114.
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113.
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104.
-
-
7 pull requests received 36 new comments.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104 (13 comments by @JohnOnGH, @msporny, @TallTed)
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114 (5 comments by @iherman, @msporny, @philarcher, @TallTed)
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113 (5 comments by @iherman, @msporny, @TallTed, @wes-smith)
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119 (4 comments by @iherman, @kezike, @TallTed)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (4 comments by @filip26, @msporny, @shigeya)
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106 (3 comments by @dlongley, @msporny)
-
w3c/vc-data-integrity
-
2 issues opened.
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363, by @Wind4Greg.
-
Technical Decisions and Options w3c/vc-data-integrity#362, by @Wind4Greg.
-
-
3 issues received 13 new comments.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352 (9 comments by @msporny, @TallTed, @Wind4Greg)
-
Technical Decisions and Options w3c/vc-data-integrity#362 (3 comments by @dlongley, @TallTed, @Wind4Greg)
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354 (1 comment by @Wind4Greg)
-
-
5 pull requests opened.
-
Attempts to get rid of the js issues w3c/vc-data-integrity#364, by @iherman.
-
Respec dfn issues w3c/vc-data-integrity#361, by @iherman.
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359, by @iherman.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358, by @Wind4Greg.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357, by @Wind4Greg.
-
-
6 pull requests merged.
-
Respec dfn issues w3c/vc-data-integrity#361.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358.
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357.
-
Add copyright notice and license information w3c/vc-data-integrity#355.
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353.
-
-
1 pull request closed.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356.
-
-
3 pull requests reopened.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358, by @iherman.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357, by @Wind4Greg.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356, by @Wind4Greg.
-
-
4 pull requests received 86 new comments.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358 (46 comments by @dlongley, @iherman, @TallTed, @Wind4Greg)
-
Explaining Selective Disclosure w3c/vc-data-integrity#356 (21 comments by @iherman, @TallTed, @Wind4Greg)
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359 (11 comments by @dlongley, @iherman, @Wind4Greg)
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357 (8 comments by @iherman, @msporny, @TallTed, @Wind4Greg)
-
w3c/vc-render-method
-
14 issues opened.
-
Security and Privacy Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#79, by @msporny.
-
Non-Issuer provided Render Methods. w3c/vc-render-method#78, by @BigBlueHat.
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77, by @dmitrizagidulin.
-
Registry for renderSuite values w3c/vc-render-method#75, by @dmitrizagidulin.
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71, by @dontcallmedom-bot.
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70, by @msporny.
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69, by @TallTed.
-
Accessibility Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#68, by @msporny.
-
Internationalization Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#67, by @msporny.
-
Horizontal Reviews for VC Rendering Methods v1.0 w3c/vc-render-method#66, by @msporny.
-
Add Relationship to Other Technologies section w3c/vc-render-method#64, by @msporny.
-
Internationalization is broken for card method w3c/vc-render-method#63, by @msporny.
-
Dynamic update-ability of Render Methods. w3c/vc-render-method#62, by @BigBlueHat.
-
Editorial comments on (JSON) cards w3c/vc-render-method#61, by @iherman.
-
-
2 issues closed.
-
We should note that, in general, all fetches SHOULD be performed over OHTTP or similar w3c/vc-render-method#47.
-
Add Relationship to Other Technologies section w3c/vc-render-method#64.
-
-
11 issues received 19 new comments.
-
Finalize names for render method categories w3c/vc-render-method#55 (5 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman)
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70 (3 comments by @dlongley, @dmitrizagidulin, @msporny)
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (2 comments by @dmitrizagidulin, @iherman)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
We should note that, in general, all fetches SHOULD be performed over OHTTP or similar w3c/vc-render-method#47 (1 comment by @dmitrizagidulin)
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27 (1 comment by @dmitrizagidulin)
-
-
7 pull requests opened.
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76, by @dmitrizagidulin.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74, by @BigBlueHat.
-
Address editorial comments on JSON cards. w3c/vc-render-method#73, by @dmitrizagidulin.
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72, by @dmitrizagidulin.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65, by @msporny.
-
Add Rendering Methods threat model w3c/vc-render-method#60, by @msporny.
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59, by @msporny.
-
-
4 pull requests merged.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65.
-
Add Rendering Methods threat model w3c/vc-render-method#60.
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59.
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58.
-
-
7 pull requests received 47 new comments.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65 (17 comments by @iherman, @msporny, @TallTed)
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59 (9 comments by @dmitrizagidulin, @iherman, @kezike, @msporny, @TallTed)
-
Add Rendering Methods threat model w3c/vc-render-method#60 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58 (6 comments by @dmitrizagidulin, @iherman, @isaackps, @msporny)
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74 (5 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman, @TallTed)
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72 (2 comments by @dmitrizagidulin, @msporny)
-
w3c/vcalm
-
11 issues opened.
-
Handling the unregistered `application/mdoc` media type. w3c/vcalm#712, by @BigBlueHat.
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710, by @dmitrizagidulin.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#703, by @kezike.
-
Provide a mermaid diagram that illustrates interaction chaining w3c/vcalm#702, by @kezike.
-
Design Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#699, by @kezike.
-
Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#698, by @kezike.
-
Internationalization Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#697, by @kezike.
-
Accessibility Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#696, by @kezike.
-
Security and Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#695, by @kezike.
-
-
13 issues closed.
-
Add link to threat model document in main spec w3c/vcalm#683.
-
Update threat_model folder name to threat-model w3c/vcalm#682.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#703.
-
Add `protocols` object key table w3c/vcalm#642.
-
Interaction scheme registration w3c/vcalm#579.
-
Design Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#699.
-
Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#698.
-
Mermaid diagrams for interactions are incorrect w3c/vcalm#631.
-
-
19 issues received 25 new comments.
-
Add support for advanced BBS features like pseudonyms w3c/vcalm#396 (3 comments by @dlongley, @eric-schuh)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @kezike)
-
Consider using `web+interaction:` scheme to allow web apps to register to receive interaction URLs w3c/vcalm#634 (2 comments by @kezike)
-
Split T25 "Failure to Validate Verifier Results and Semantic Contexts" into two threats w3c/vcalm#671 (1 comment by @kezike)
-
Should the information here reflect aspirational state (`WD`) instead of current state (`FPWD`)? w3c/vcalm#654 (1 comment by @kezike)
-
Consider adding `<exchangeId>/request` endpoint to serve current VPR/request for DC API protocol w3c/vcalm#633 (1 comment by @kezike)
-
Provide example of using `redirectUrl` with an interaction URL (`?iuv=1`) to demonstrate exchange "chaining" w3c/vcalm#619 (1 comment by @kezike)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @eric-schuh)
-
Allow multiple presentations to be sent in a response via an array value for `verifiablePresentation` w3c/vcalm#649 (1 comment by @kezike)
-
Include optional `credentialOffer` property in a VPR that announces VCs to be issued in step w3c/vcalm#689 (1 comment by @dlongley)
-
-
13 pull requests opened.
-
Add inline references and security/privacy tags to each threat. w3c/vcalm#709, by @kezike.
-
Fix broken link for "transformation" w3c/vcalm#708, by @tidoust.
-
Fix threat model folder and landing page w3c/vcalm#707, by @kezike.
-
Updated respec-oas to version 1.0.2 w3c/vcalm#706, by @eric-schuh.
-
Adding `credentialOffer` to VPR w3c/vcalm#705, by @eric-schuh.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704, by @kezike.
-
Add informative reference workflow step processing appendix w3c/vcalm#701, by @PatStLouis.
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700, by @PatStLouis.
-
Register interaction protocol schemes w3c/vcalm#694, by @kezike.
-
Fix oneOf + required rendering issues w3c/vcalm#692, by @eric-schuh.
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691, by @PatStLouis.
-
Fix oneOf+required respec render issue w3c/vcalm#690, by @eric-schuh.
-
8 pull requests merged.
-
Fix threat model folder and landing page w3c/vcalm#707.
-
Add threat model section to security considerations w3c/vcalm#685.
-
Update local bibliography refs w3c/vcalm#681.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704.
-
Add interaction protocol table w3c/vcalm#680.
-
Add support for retrieving current exchange VPR w3c/vcalm#663.
-
Register interaction protocol schemes w3c/vcalm#694.
-
-
3 pull requests closed.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624.
-
Fix oneOf+required respec render issue w3c/vcalm#690.
-
20 pull requests received 138 new comments.
-
Resolve tension between Threat Model and Privacy & Security Considerations w3c/vcalm#711 (59 comments by @eric-schuh, @kezike, @msporny)
-
Register interaction protocol schemes w3c/vcalm#694 (12 comments by @iherman, @kezike, @msporny, @TallTed)
-
Add threat model section to security considerations w3c/vcalm#685 (8 comments by @dlongley, @kezike, @msporny, @PatStLouis)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (5 comments by @ottonomy, @PatStLouis, @TallTed)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (3 comments by @dlongley, @PatStLouis, @TallTed)
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679 (3 comments by @TallTed)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (3 comments by @dlongley)
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704 (2 comments by @kezike, @TallTed)
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691 (2 comments by @eric-schuh, @PatStLouis)
-
Add inline references and security/privacy tags to each threat. w3c/vcalm#709 (1 comment by @msporny)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @PatStLouis)
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624 (1 comment by @PatStLouis)
-
w3c/vc-overview
-
3 issues opened.
-
Consistency of V|verifiable C|credential w3c/vc-overview#44, by @philarcher.
-
"Alumnus" is used throughout. Consider "Alum" or "Matriculation" instead. w3c/vc-overview#41, by @TallTed.
-
Reorganization of the embedded proof section w3c/vc-overview#40, by @iherman.
-
-
5 issues closed.
-
SD and Quantum with regard jose cose? w3c/vc-overview#31.
-
Review of the SD description w3c/vc-overview#32.
-
Reorganization of the embedded proof section w3c/vc-overview#40.
-
"Alumnus" is used throughout. Consider "Alum" or "Matriculation" instead. w3c/vc-overview#41.
-
Linked resources example json schemas? w3c/vc-overview#30.
-
-
6 issues received 18 new comments.
-
Linked resources example json schemas? w3c/vc-overview#30 (11 comments by @iherman, @msporny, @philarcher)
-
"Alumnus" is used throughout. Consider "Alum" or "Matriculation" instead. w3c/vc-overview#41 (3 comments by @iherman, @TallTed)
-
-
5 pull requests opened.
-
Reorganize sd w3c/vc-overview#45, by @iherman.
-
Typo in the abstract w3c/vc-overview#43, by @philarcher.
-
Alumnus -> Alumni w3c/vc-overview#42, by @iherman.
-
added a note on credential data usage w3c/vc-overview#39, by @iherman.
-
Emphasize the generic use of digestMultibase w3c/vc-overview#38, by @iherman.
-
-
5 pull requests merged.
-
Reorganize sd w3c/vc-overview#45.
-
Alumnus -> Alumni w3c/vc-overview#42.
-
Typo in the abstract w3c/vc-overview#43.
-
added a note on credential data usage w3c/vc-overview#39.
-
Emphasize the generic use of digestMultibase w3c/vc-overview#38.
-
-
3 pull requests received 11 new comments.
-
added a note on credential data usage w3c/vc-overview#39 (7 comments by @iherman, @msporny, @TallTed)
-
w3c/vc-di-ecdsa
-
1 pull request opened.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106, by @Wind4Greg.
-
-
2 pull requests merged.
-
Update echidna w3c/vc-di-ecdsa#104.
-
-
2 pull requests received 8 new comments.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106 (7 comments by @dlongley, @TallTed)
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103 (1 comment by @Wind4Greg)
-
w3c/vc-data-model
-
6 issues opened.
-
https://www.w3.org/2018/credentials redirect missing Access-Control-Allow-Origin w3c/vc-data-model#1644, by @nissimsan.
-
Suggestion: Show mixed localized/non-localized arrays in i18n examples w3c/vc-data-model#1643, by @filip26.
-
Invalid JSON and @context in Example #31 w3c/vc-data-model#1642, by @filip26.
-
Add a "localizeable value" term to address i18n concerns w3c/vc-data-model#1641, by @msporny.
-
Threat Model: Improve Bearer Credential Reuse and Correlation description w3c/vc-data-model#1640, by @msporny.
-
Add new W3C Threat Model to specification w3c/vc-data-model#1637, by @msporny.
-
-
1 issue closed.
-
Add new W3C Threat Model to specification w3c/vc-data-model#1637.
-
-
8 issues received 16 new comments.
-
Deprecate `digestSRI` in v2.1 w3c/vc-data-model#1628 (6 comments by @dlongley, @iherman, @philarcher, @shigeya)
-
Terminology for processing modes w3c/vc-data-model#1634 (3 comments by @dmitrizagidulin, @filip26, @iherman)
-
https://www.w3.org/2018/credentials redirect missing Access-Control-Allow-Origin w3c/vc-data-model#1644 (1 comment by @nissimsan)
-
Add a "localizeable value" term to address i18n concerns w3c/vc-data-model#1641 (1 comment by @iherman)
-
Threat Model: Improve Bearer Credential Reuse and Correlation description w3c/vc-data-model#1640 (1 comment by @msporny)
-
-
3 pull requests opened.
-
Rephrase securing requirement as constraint on securing (vs conformance). w3c/vc-data-model#1645, by @dmitrizagidulin.
-
Migrate Security/Privacy Considerations to Threat Model w3c/vc-data-model#1639, by @msporny.
-
Add basic threat model. w3c/vc-data-model#1638, by @msporny.
-
-
2 pull requests merged.
-
Migrate Security/Privacy Considerations to Threat Model w3c/vc-data-model#1639.
-
Add basic threat model. w3c/vc-data-model#1638.
-
-
4 pull requests received 50 new comments.
-
Update introduction sections for clarity. w3c/vc-data-model#1636 (21 comments by @dlongley, @dmitrizagidulin, @iherman, @msporny, @TallTed)
-
Migrate Security/Privacy Considerations to Threat Model w3c/vc-data-model#1639 (7 comments by @dlongley, @iherman, @msporny)
-
w3c/vc-wg
-
1 issue opened.
-
The infamous LF vs CRLF problem on GitHub w3c/vc-wg#16, by @iherman.
-
-
1 issue received 13 new comments.
-
The infamous LF vs CRLF problem on GitHub w3c/vc-wg#16 (13 comments by @iherman, @kezike, @msporny, @pchampin, @TallTed, @Wind4Greg)
-
-
1 pull request merged.
-
Placing the new terms in vocabularies and context files w3c/vc-wg#15.
-
w3c/vc-data-model-2.0-test-suite
-
3 pull requests opened.
-
Fix main GitHub Actions permissions. w3c/vc-data-model-2.0-test-suite#178, by @BigBlueHat.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-data-model-2.0-test-suite#177, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-data-model-2.0-test-suite#176, by @BigBlueHat.
-
-
5 pull requests merged.
-
Fix main GitHub Actions permissions. w3c/vc-data-model-2.0-test-suite#178.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-data-model-2.0-test-suite#177.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-data-model-2.0-test-suite#176.
-
Set permissions; do not persist credentials. w3c/vc-data-model-2.0-test-suite#162.
-
Update vc-test-suite-implementations at runtime. w3c/vc-data-model-2.0-test-suite#175.
-
-
1 pull request closed.
-
Unignore package-lock.json. w3c/vc-data-model-2.0-test-suite#173.
-
-
2 pull requests received 2 new comments.
-
Update vc-test-suite-implementations at runtime. w3c/vc-data-model-2.0-test-suite#175 (1 comment by @BigBlueHat)
w3c/vc-di-ecdsa-test-suite
-
3 pull requests opened.
-
Update CI to Node.js 24 w3c/vc-di-ecdsa-test-suite#125, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-ecdsa-test-suite#124, by @BigBlueHat.
-
Add CODEOWNERS file. w3c/vc-di-ecdsa-test-suite#123, by @BigBlueHat.
-
-
2 pull requests merged.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-ecdsa-test-suite#124.
-
Add CODEOWNERS file. w3c/vc-di-ecdsa-test-suite#123.
-
w3c/vc-di-ed25519signature2020-test-suite
-
3 pull requests opened.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-di-ed25519signature2020-test-suite#65, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-ed25519signature2020-test-suite#64, by @BigBlueHat.
-
Add CODEOWNERS file. w3c/vc-di-ed25519signature2020-test-suite#63, by @BigBlueHat.
-
-
3 pull requests merged.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-ed25519signature2020-test-suite#64.
-
fix abstract link w3c/vc-di-ed25519signature2020-test-suite#60.
-
Add CODEOWNERS file. w3c/vc-di-ed25519signature2020-test-suite#63.
-
w3c/vc-di-eddsa-test-suite
-
3 pull requests opened.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-di-eddsa-test-suite#74, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-eddsa-test-suite#73, by @BigBlueHat.
-
Add CODEOWNERS file. w3c/vc-di-eddsa-test-suite#72, by @BigBlueHat.
-
-
3 pull requests merged.
-
Use vc2 credential in issue/verify rdfc tests w3c/vc-di-eddsa-test-suite#69.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-eddsa-test-suite#73.
-
Add CODEOWNERS file. w3c/vc-di-eddsa-test-suite#72.
-
w3c/vc-di-bbs-test-suite
-
3 pull requests opened.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-di-bbs-test-suite#84, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-bbs-test-suite#83, by @BigBlueHat.
-
Add CODEOWNERS file. w3c/vc-di-bbs-test-suite#82, by @BigBlueHat.
-
-
3 pull requests merged.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-di-bbs-test-suite#83.
-
Use Issuer instead of Implementation for issuer tests. w3c/vc-di-bbs-test-suite#79.
-
Add CODEOWNERS file. w3c/vc-di-bbs-test-suite#82.
-
w3c/vc-bitstring-status-list-test-suite
-
4 pull requests opened.
-
Update CI to Node.js 24 and pin github-pages-deploy-action w3c/vc-bitstring-status-list-test-suite#76, by @BigBlueHat.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-bitstring-status-list-test-suite#75, by @BigBlueHat.
-
Add CODEOWNERS file. w3c/vc-bitstring-status-list-test-suite#74, by @BigBlueHat.
-
Fix test case if condition w3c/vc-bitstring-status-list-test-suite#73, by @ashushukla0412.
-
-
3 pull requests merged.
-
Add CODEOWNERS file. w3c/vc-bitstring-status-list-test-suite#74.
-
Fix test case if condition w3c/vc-bitstring-status-list-test-suite#73.
-
Always float vc-test-suite-implementations to main in pretest w3c/vc-bitstring-status-list-test-suite#75.
-
-
1 pull request received 1 new comment.
-
Fix test case if condition w3c/vc-bitstring-status-list-test-suite#73 (1 comment by @ashushukla0412)
-
w3c/vc-confidence-method
-
2 issues closed.
-
Change the short name w3c/vc-confidence-method#46.
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33.
-
-
2 issues received 4 new comments.
-
1 pull request opened.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47, by @denkeni.
-
-
3 pull requests merged.
-
Add biometric image section w3c/vc-confidence-method#44.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47.
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45.
-
-
4 pull requests received 27 new comments.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47 (4 comments by @denkeni, @dlongley, @iherman, @msporny)
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45 (2 comments by @denkeni, @iherman)
w3c/vc-test-suite-implementations
-
3 pull requests opened.
-
Update DigitalBazaar config. w3c/vc-test-suite-implementations#126, by @BigBlueHat.
-
Update LearnCard: new endpoint, new DID, register eddsa-rdfc-2022 w3c/vc-test-suite-implementations#125, by @Custard7.
-
Add jose-cose tags to Trential w3c/vc-test-suite-implementations#124, by @ashushukla0412.
-
-
3 pull requests merged.
-
Update DigitalBazaar config. w3c/vc-test-suite-implementations#126.
-
Update LearnCard: new endpoint, new DID, register eddsa-rdfc-2022 w3c/vc-test-suite-implementations#125.
-
Add TrustVC to implementations w3c/vc-test-suite-implementations#115.
-
-
2 pull requests received 3 new comments.
-
Add jose-cose tags to Trential w3c/vc-test-suite-implementations#124 (2 comments by @ashushukla0412)
-
w3c/vc-di-quantum-resistant
-
2 pull requests opened.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42, by @Wind4Greg.
-
Patch Selective Disclosure for sqisign1-sd-2024: new Cryptosuite table row, minimal examples w3c/vc-di-quantum-resistant#41, by @antonymott.
-
-
1 pull request merged.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40.
-
-
2 pull requests received 24 new comments.
-
Patch Selective Disclosure for sqisign1-sd-2024: new Cryptosuite table row, minimal examples w3c/vc-di-quantum-resistant#41 (21 comments by @antonymott, @dlongley, @iherman, @msporny, @w3cbot, @Wind4Greg)
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42 (3 comments by @dlongley)
-
w3c/vc-forgery-defense
-
3 issues opened.
-
Fort apps w3c/vc-forgery-defense#8, by @shanmohd44494-oss.
-
Connect security/privacy considerations to existing threat models. w3c/vc-forgery-defense#7, by @wes-smith.
-
Consider making witnessSeed an optional property w3c/vc-forgery-defense#6, by @wes-smith.
-
-
1 issue closed.
-
Fort apps w3c/vc-forgery-defense#8.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
Generalize witness seed format. w3c/vc-forgery-defense#5.
-
-
1 pull request received 7 new comments.
-
Generalize witness seed format. w3c/vc-forgery-defense#5 (7 comments by @dlongley, @msporny, @wes-smith)
-
w3c/vc-di-eddsa
-
1 pull request opened.
-
Reuse Common Algorithms from VC-DI-1.1 w3c/vc-di-eddsa#118, by @Wind4Greg.
-
-
1 pull request merged.
-
Update echidna w3c/vc-di-eddsa#116.
-
-
1 pull request received 5 new comments.
w3c/vc-dpp-bw
-
2 issues opened.
-
Add explanation of confidence method and threat modelling etc. w3c/vc-dpp-bw#16, by @philarcher.
-
Explain how VCs go beyond normal digitally signed documents w3c/vc-dpp-bw#15, by @philarcher.
-
-
4 pull requests opened.
-
- added UC scenario file for BW w3c/vc-dpp-bw#18, by @ngwlf.
-
Raising and linking to issues w3c/vc-dpp-bw#17, by @philarcher.
-
Update index.md w3c/vc-dpp-bw#14, by @susanne-guth-orlowski.
-
Digital twin rash w3c/vc-dpp-bw#13, by @philarcher.
-
-
6 pull requests merged.
-
Raising and linking to issues w3c/vc-dpp-bw#17.
-
Digital Links as credentialSubject.id w3c/vc-dpp-bw#10.
-
Update index.md w3c/vc-dpp-bw#14.
-
- added UC scenario file for BW w3c/vc-dpp-bw#18.
-
SGO Update index.md w3c/vc-dpp-bw#12.
-
Digital twin rash w3c/vc-dpp-bw#13.
-
-
1 pull request received 11 new comments.
w3c/vc-jose-cose-test-suite
-
2 pull requests opened.
-
Add CODEOWNERS file. w3c/vc-jose-cose-test-suite#35, by @BigBlueHat.
-
Add trential test config w3c/vc-jose-cose-test-suite#34, by @ashushukla0412.
-
-
1 pull request received 2 new comments.
w3c/vc-use-cases
-
5 issues closed.
-
typo in section "L.4 Refugee crisis" w3c/vc-use-cases#120.
-
Review Editor/Author section w3c/vc-use-cases#107.
-
New user/verifier task - Request Claim w3c/vc-use-cases#139.
-
New user/issuer task - Provide Claim w3c/vc-use-cases#141.
-
Update requested for section 6.2 (VC usage) w3c/vc-use-cases#143.
-
-
9 issues received 13 new comments.
-
Pull request preview images are missing (links are broken) w3c/vc-use-cases#170 (5 comments by @deniak, @iherman, @jandrieu, @kfranqueiro, @tobie)
-
New user/holder task - Receive and process claim request w3c/vc-use-cases#140 (1 comment by @jandrieu)
-
Request for new section 6.3 How a Verifiable Credential may be issued within a process w3c/vc-use-cases#144 (1 comment by @KDean-Dolphin)
-
w3c/cid
-
5 issues received 7 new comments.
-
In examples, avoid HTTPS URIs that are not dereferenced during dereferencing w3c/cid#165 (1 comment by @iherman)
-
1 pull request opened.
-
Update index.html #167 w3c/cid#178, by @mxshea.
-
-
1 pull request closed.
-
2 pull requests received 2 new comments.
w3c/vc-barcodes
-
3 issues opened.
-
Accessibility Self-Review Questionnaire for Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#70, by @wes-smith.
-
Internationalization Self-Review Questionnaire for VC Barcodes v1.0 w3c/vc-barcodes#69, by @wes-smith.
-
Security and Privacy Self-Review Questionnaire for VC Barcodes 1.0 w3c/vc-barcodes#68, by @wes-smith.
-
-
1 issue closed.
-
"Secure barcodes" w3c/vc-barcodes#58.
-
-
2 issues received 2 new comments.
-
1 pull request merged.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62.
-
-
1 pull request received 6 new comments.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62 (6 comments by @philarcher, @TallTed, @wes-smith)
-
w3c/vcalm-test-suite
-
1 pull request opened.
-
Add VCALM TR normative statements scrape and HTML report w3c/vcalm-test-suite#4, by @PatStLouis.
-
-
1 pull request merged.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#3.
-
VC Recognized Entities
Past meetings
GitHub
w3c/vc-recognized-entities
-
11 issues opened in the VC Recognized Entities.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121, by @philarcher.
-
Create test suite for VC Recognized Entities w3c/vc-recognized-entities#120, by @msporny.
-
Provide guidance related to data URLs when used with outputValidation and other object types w3c/vc-recognized-entities#118, by @msporny.
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117, by @iherman.
-
Determine alignment with OpenID Federation w3c/vc-recognized-entities#116, by @msporny.
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115, by @TallTed.
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112, by @aphillips.
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111, by @aphillips.
-
Examples are USA-centric? w3c/vc-recognized-entities#110, by @aphillips.
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109, by @tsnyder-gs1us.
-
Refine UNGRID / UNTP / UNVTD Example w3c/vc-recognized-entities#107, by @msporny.
-
-
13 issues closed in the VC Recognized Entities.
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49.
-
Federated Identifier use case w3c/vc-recognized-entities#74.
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66.
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86.
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63.
-
Add ref to Forgery Defense to threat model w3c/vc-recognized-entities#100.
-
Threat Model: diagram box type cues w3c/vc-recognized-entities#87.
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109.
-
Use Cases and Applications for this data model w3c/vc-recognized-entities#51.
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48.
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88.
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77.
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89.
-
-
25 issues in the VC Recognized Entities received 67 new comments.
-
Refine UNGRID / UNTP / UNVTD Example w3c/vc-recognized-entities#107 (11 comments by @iherman, @JohnOnGH, @msporny, @TallTed)
-
Normative references to WhoisService and PathService w3c/vc-recognized-entities#117 (10 comments by @iherman, @msporny, @ottomorac, @peacekeeper, @swcurran)
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71 (5 comments by @iherman, @kezike, @msporny)
-
Provide guidance related to data URLs when used with outputValidation and other object types w3c/vc-recognized-entities#118 (4 comments by @iherman, @paulfdietrich, @philarcher)
-
`legalName` does not permit a "language value object" w3c/vc-recognized-entities#111 (4 comments by @aphillips, @iherman, @msporny)
-
Show some non-ASCII/non-English examples and label the English w3c/vc-recognized-entities#112 (3 comments by @iherman, @msporny, @TallTed)
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46 (2 comments by @paulfdietrich)
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86 (2 comments by @msporny)
-
Recognized Entities and Transfer of Ownership w3c/vc-recognized-entities#109 (2 comments by @iherman, @msporny)
-
Use Cases and Applications for this data model w3c/vc-recognized-entities#51 (2 comments by @iherman, @msporny)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (2 comments by @iherman, @msporny)
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91 (2 comments by @iherman, @msporny)
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89 (2 comments by @iherman, @onthebreeze)
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (1 comment by @paulfdietrich)
-
CRQC is not in general nor wide use (yet) and should be included in each document w3c/vc-recognized-entities#115 (1 comment by @iherman)
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49 (1 comment by @msporny)
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @msporny)
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88 (1 comment by @msporny)
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77 (1 comment by @msporny)
-
-
4 pull requests opened in the VC Recognized Entities.
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119, by @kezike.
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114, by @msporny.
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113, by @msporny.
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108, by @philarcher.
-
-
4 pull requests merged in the VC Recognized Entities.
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114.
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113.
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104.
-
-
7 pull requests in the VC Recognized Entities received 36 new comments.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104 (13 comments by @JohnOnGH, @msporny, @TallTed)
-
Note that the spec is an application of the VC data model. w3c/vc-recognized-entities#114 (5 comments by @iherman, @msporny, @philarcher, @TallTed)
-
Add reference to VC Forgery Defense in CRQC threat response. w3c/vc-recognized-entities#113 (5 comments by @iherman, @msporny, @TallTed, @wes-smith)
-
Add support for arbitrary external entity registry lists w3c/vc-recognized-entities#119 (4 comments by @iherman, @kezike, @TallTed)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (4 comments by @filip26, @msporny, @shigeya)
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106 (3 comments by @dlongley, @msporny)
-
VC Barcodes and Data Integrity
Past meetings
-
4 meetings of the VC Barcodes and Data Integrity.
Participants
-
1 participant joined the VC Barcodes and Data Integrity.
-
Antony Mott joined.
-
GitHub
w3c/vc-data-integrity
-
2 issues opened in the VC Barcodes and Data Integrity.
-
Add Definition of Unlinkable Disclosure w3c/vc-data-integrity#363, by @Wind4Greg.
-
Technical Decisions and Options w3c/vc-data-integrity#362, by @Wind4Greg.
-
-
3 issues in the VC Barcodes and Data Integrity received 13 new comments.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352 (9 comments by @msporny, @TallTed, @Wind4Greg)
-
Technical Decisions and Options w3c/vc-data-integrity#362 (3 comments by @dlongley, @TallTed, @Wind4Greg)
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354 (1 comment by @Wind4Greg)
-
-
5 pull requests opened in the VC Barcodes and Data Integrity.
-
Attempts to get rid of the js issues w3c/vc-data-integrity#364, by @iherman.
-
Respec dfn issues w3c/vc-data-integrity#361, by @iherman.
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359, by @iherman.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358, by @Wind4Greg.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357, by @Wind4Greg.
-
-
6 pull requests merged in the VC Barcodes and Data Integrity.
-
Respec dfn issues w3c/vc-data-integrity#361.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358.
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357.
-
Add copyright notice and license information w3c/vc-data-integrity#355.
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353.
-
-
1 pull request closed in the VC Barcodes and Data Integrity.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356.
-
-
3 pull requests reopened in the VC Barcodes and Data Integrity.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358, by @iherman.
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357, by @Wind4Greg.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356, by @Wind4Greg.
-
-
4 pull requests in the VC Barcodes and Data Integrity received 86 new comments.
-
Selective Disclosure Refactored w3c/vc-data-integrity#358 (46 comments by @dlongley, @iherman, @TallTed, @Wind4Greg)
-
Explaining Selective Disclosure w3c/vc-data-integrity#356 (21 comments by @iherman, @TallTed, @Wind4Greg)
-
Adding to the SD Explanation (PR 357) w3c/vc-data-integrity#359 (11 comments by @dlongley, @iherman, @Wind4Greg)
-
Definition of selected disclosure and explanation of "how it works". w3c/vc-data-integrity#357 (8 comments by @iherman, @msporny, @TallTed, @Wind4Greg)
-
w3c/vc-di-ecdsa
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106, by @Wind4Greg.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Update echidna w3c/vc-di-ecdsa#104.
-
-
2 pull requests in the VC Barcodes and Data Integrity received 8 new comments.
-
Update to Use Crytposuite Common Algorithms from DI-1.1 w3c/vc-di-ecdsa#106 (7 comments by @dlongley, @TallTed)
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103 (1 comment by @Wind4Greg)
-
w3c/vc-di-quantum-resistant
-
2 pull requests opened in the VC Barcodes and Data Integrity.
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42, by @Wind4Greg.
-
Patch Selective Disclosure for sqisign1-sd-2024: new Cryptosuite table row, minimal examples w3c/vc-di-quantum-resistant#41, by @antonymott.
-
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40.
-
-
2 pull requests in the VC Barcodes and Data Integrity received 24 new comments.
-
Patch Selective Disclosure for sqisign1-sd-2024: new Cryptosuite table row, minimal examples w3c/vc-di-quantum-resistant#41 (21 comments by @antonymott, @dlongley, @iherman, @msporny, @w3cbot, @Wind4Greg)
-
Reuse Common Algorithms from VC-Data-Integrity 1.1 w3c/vc-di-quantum-resistant#42 (3 comments by @dlongley)
-
w3c/vc-forgery-defense
-
3 issues opened in the VC Barcodes and Data Integrity.
-
Fort apps w3c/vc-forgery-defense#8, by @shanmohd44494-oss.
-
Connect security/privacy considerations to existing threat models. w3c/vc-forgery-defense#7, by @wes-smith.
-
Consider making witnessSeed an optional property w3c/vc-forgery-defense#6, by @wes-smith.
-
-
1 issue closed in the VC Barcodes and Data Integrity.
-
Fort apps w3c/vc-forgery-defense#8.
-
-
2 issues in the VC Barcodes and Data Integrity received 2 new comments.
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Generalize witness seed format. w3c/vc-forgery-defense#5.
-
-
1 pull request in the VC Barcodes and Data Integrity received 7 new comments.
-
Generalize witness seed format. w3c/vc-forgery-defense#5 (7 comments by @dlongley, @msporny, @wes-smith)
-
w3c/vc-di-eddsa
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Reuse Common Algorithms from VC-DI-1.1 w3c/vc-di-eddsa#118, by @Wind4Greg.
-
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Update echidna w3c/vc-di-eddsa#116.
-
-
1 pull request in the VC Barcodes and Data Integrity received 5 new comments.
w3c/vc-barcodes
-
3 issues opened in the VC Barcodes and Data Integrity.
-
Accessibility Self-Review Questionnaire for Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#70, by @wes-smith.
-
Internationalization Self-Review Questionnaire for VC Barcodes v1.0 w3c/vc-barcodes#69, by @wes-smith.
-
Security and Privacy Self-Review Questionnaire for VC Barcodes 1.0 w3c/vc-barcodes#68, by @wes-smith.
-
-
1 issue closed in the VC Barcodes and Data Integrity.
-
"Secure barcodes" w3c/vc-barcodes#58.
-
-
2 issues in the VC Barcodes and Data Integrity received 2 new comments.
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62.
-
-
1 pull request in the VC Barcodes and Data Integrity received 6 new comments.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62 (6 comments by @philarcher, @TallTed, @wes-smith)
-
VC Render Method
GitHub
w3c/vc-render-method
-
14 issues opened in the VC Render Method.
-
Security and Privacy Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#79, by @msporny.
-
Non-Issuer provided Render Methods. w3c/vc-render-method#78, by @BigBlueHat.
-
Folding `nfc` into a `static` render suite needs a dispatch mechanism w3c/vc-render-method#77, by @dmitrizagidulin.
-
Registry for renderSuite values w3c/vc-render-method#75, by @dmitrizagidulin.
-
Broken links in Verifiable Credential Rendering Methods v1.0 w3c/vc-render-method#71, by @dontcallmedom-bot.
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70, by @msporny.
-
`t19` and threat-related numbering are made permanent by current tooling w3c/vc-render-method#69, by @TallTed.
-
Accessibility Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#68, by @msporny.
-
Internationalization Self-Review Questionnaire for VC Rendering Methods v1.0 w3c/vc-render-method#67, by @msporny.
-
Horizontal Reviews for VC Rendering Methods v1.0 w3c/vc-render-method#66, by @msporny.
-
Add Relationship to Other Technologies section w3c/vc-render-method#64, by @msporny.
-
Internationalization is broken for card method w3c/vc-render-method#63, by @msporny.
-
Dynamic update-ability of Render Methods. w3c/vc-render-method#62, by @BigBlueHat.
-
Editorial comments on (JSON) cards w3c/vc-render-method#61, by @iherman.
-
-
2 issues closed in the VC Render Method.
-
We should note that, in general, all fetches SHOULD be performed over OHTTP or similar w3c/vc-render-method#47.
-
Add Relationship to Other Technologies section w3c/vc-render-method#64.
-
-
11 issues in the VC Render Method received 19 new comments.
-
Finalize names for render method categories w3c/vc-render-method#55 (5 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman)
-
Internationalization and Accessibility support in `html` render method w3c/vc-render-method#70 (3 comments by @dlongley, @dmitrizagidulin, @msporny)
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (2 comments by @dmitrizagidulin, @iherman)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @dmitrizagidulin)
-
We should note that, in general, all fetches SHOULD be performed over OHTTP or similar w3c/vc-render-method#47 (1 comment by @dmitrizagidulin)
-
Make the spec clear about it being an extension mechanism w3c/vc-render-method#27 (1 comment by @dmitrizagidulin)
-
-
7 pull requests opened in the VC Render Method.
-
Dispatch render suites on renderSuite, not type. w3c/vc-render-method#76, by @dmitrizagidulin.
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74, by @BigBlueHat.
-
Address editorial comments on JSON cards. w3c/vc-render-method#73, by @dmitrizagidulin.
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72, by @dmitrizagidulin.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65, by @msporny.
-
Add Rendering Methods threat model w3c/vc-render-method#60, by @msporny.
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59, by @msporny.
-
-
4 pull requests merged in the VC Render Method.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65.
-
Add Rendering Methods threat model w3c/vc-render-method#60.
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59.
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58.
-
-
7 pull requests in the VC Render Method received 47 new comments.
-
Add content to Relationship to Other Technologies section. w3c/vc-render-method#65 (17 comments by @iherman, @msporny, @TallTed)
-
Remove "JSON" language from card render suite. w3c/vc-render-method#59 (9 comments by @dmitrizagidulin, @iherman, @kezike, @msporny, @TallTed)
-
Add Rendering Methods threat model w3c/vc-render-method#60 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58 (6 comments by @dmitrizagidulin, @iherman, @isaackps, @msporny)
-
Reworking `card` to be `highlights`. w3c/vc-render-method#74 (5 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman, @TallTed)
-
Require i18n and a11y settings exposure in html render suite. w3c/vc-render-method#72 (2 comments by @dmitrizagidulin, @msporny)
-
VC API for Lifecycle Management
Past meetings
-
4 meetings of the VC API for Lifecycle Management.
GitHub
w3c/vcalm
-
11 issues opened in the VC API for Lifecycle Management.
-
Handling the unregistered `application/mdoc` media type. w3c/vcalm#712, by @BigBlueHat.
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710, by @dmitrizagidulin.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#703, by @kezike.
-
Provide a mermaid diagram that illustrates interaction chaining w3c/vcalm#702, by @kezike.
-
Design Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#699, by @kezike.
-
Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#698, by @kezike.
-
Internationalization Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#697, by @kezike.
-
Accessibility Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#696, by @kezike.
-
Security and Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#695, by @kezike.
-
-
13 issues closed in the VC API for Lifecycle Management.
-
Add link to threat model document in main spec w3c/vcalm#683.
-
Update threat_model folder name to threat-model w3c/vcalm#682.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#703.
-
Add `protocols` object key table w3c/vcalm#642.
-
Interaction scheme registration w3c/vcalm#579.
-
Design Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#699.
-
Privacy Self-Review Questionnaire for VCALM v1.0 w3c/vcalm#698.
-
Mermaid diagrams for interactions are incorrect w3c/vcalm#631.
-
-
19 issues in the VC API for Lifecycle Management received 25 new comments.
-
Add support for advanced BBS features like pseudonyms w3c/vcalm#396 (3 comments by @dlongley, @eric-schuh)
-
Add ephemeral requester-initiated exchanges profile w3c/vcalm#710 (2 comments by @dlongley, @kezike)
-
Consider using `web+interaction:` scheme to allow web apps to register to receive interaction URLs w3c/vcalm#634 (2 comments by @kezike)
-
Split T25 "Failure to Validate Verifier Results and Semantic Contexts" into two threats w3c/vcalm#671 (1 comment by @kezike)
-
Should the information here reflect aspirational state (`WD`) instead of current state (`FPWD`)? w3c/vcalm#654 (1 comment by @kezike)
-
Consider adding `<exchangeId>/request` endpoint to serve current VPR/request for DC API protocol w3c/vcalm#633 (1 comment by @kezike)
-
Provide example of using `redirectUrl` with an interaction URL (`?iuv=1`) to demonstrate exchange "chaining" w3c/vcalm#619 (1 comment by @kezike)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @eric-schuh)
-
Allow multiple presentations to be sent in a response via an array value for `verifiablePresentation` w3c/vcalm#649 (1 comment by @kezike)
-
Include optional `credentialOffer` property in a VPR that announces VCs to be issued in step w3c/vcalm#689 (1 comment by @dlongley)
-
-
13 pull requests opened in the VC API for Lifecycle Management.
-
Add inline references and security/privacy tags to each threat. w3c/vcalm#709, by @kezike.
-
Fix broken link for "transformation" w3c/vcalm#708, by @tidoust.
-
Fix threat model folder and landing page w3c/vcalm#707, by @kezike.
-
Updated respec-oas to version 1.0.2 w3c/vcalm#706, by @eric-schuh.
-
Adding `credentialOffer` to VPR w3c/vcalm#705, by @eric-schuh.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704, by @kezike.
-
Add informative reference workflow step processing appendix w3c/vcalm#701, by @PatStLouis.
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700, by @PatStLouis.
-
Register interaction protocol schemes w3c/vcalm#694, by @kezike.
-
Fix oneOf + required rendering issues w3c/vcalm#692, by @eric-schuh.
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691, by @PatStLouis.
-
Fix oneOf+required respec render issue w3c/vcalm#690, by @eric-schuh.
-
8 pull requests merged in the VC API for Lifecycle Management.
-
Fix threat model folder and landing page w3c/vcalm#707.
-
Add threat model section to security considerations w3c/vcalm#685.
-
Update local bibliography refs w3c/vcalm#681.
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704.
-
Add interaction protocol table w3c/vcalm#680.
-
Add support for retrieving current exchange VPR w3c/vcalm#663.
-
Register interaction protocol schemes w3c/vcalm#694.
-
-
3 pull requests closed in the VC API for Lifecycle Management.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624.
-
Fix oneOf+required respec render issue w3c/vcalm#690.
-
20 pull requests in the VC API for Lifecycle Management received 138 new comments.
-
Resolve tension between Threat Model and Privacy & Security Considerations w3c/vcalm#711 (59 comments by @eric-schuh, @kezike, @msporny)
-
Register interaction protocol schemes w3c/vcalm#694 (12 comments by @iherman, @kezike, @msporny, @TallTed)
-
Add threat model section to security considerations w3c/vcalm#685 (8 comments by @dlongley, @kezike, @msporny, @PatStLouis)
-
Add informative reference workflow step processing appendix w3c/vcalm#701 (5 comments by @ottonomy, @PatStLouis, @TallTed)
-
Add QueryByExample matching and JSON pointer conversion algorithms w3c/vcalm#700 (3 comments by @dlongley, @PatStLouis, @TallTed)
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679 (3 comments by @TallTed)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (3 comments by @dlongley)
-
Replace `trustedIssuer` with `acceptedIssuers` in VPR w3c/vcalm#704 (2 comments by @kezike, @TallTed)
-
Fix respec-oas RENDER ERROR on Credential/Presentation schemas w3c/vcalm#691 (2 comments by @eric-schuh, @PatStLouis)
-
Add inline references and security/privacy tags to each threat. w3c/vcalm#709 (1 comment by @msporny)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @PatStLouis)
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624 (1 comment by @PatStLouis)
-
w3c/vcalm-test-suite
-
1 pull request opened in the VC API for Lifecycle Management.
-
Add VCALM TR normative statements scrape and HTML report w3c/vcalm-test-suite#4, by @PatStLouis.
-
-
1 pull request merged in the VC API for Lifecycle Management.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#3.
-
VC Confidence Method
GitHub
w3c/vc-confidence-method
-
2 issues closed in the VC Confidence Method.
-
Change the short name w3c/vc-confidence-method#46.
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33.
-
-
2 issues in the VC Confidence Method received 4 new comments.
-
1 pull request opened in the VC Confidence Method.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47, by @denkeni.
-
-
3 pull requests merged in the VC Confidence Method.
-
Add biometric image section w3c/vc-confidence-method#44.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47.
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45.
-
-
4 pull requests in the VC Confidence Method received 27 new comments.
-
Editorial cleanup: sections, title, tooling w3c/vc-confidence-method#47 (4 comments by @denkeni, @dlongley, @iherman, @msporny)
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45 (2 comments by @denkeni, @iherman)
VC DPP & Business Wallet
GitHub
w3c/vc-dpp-bw
-
2 issues opened in the VC DPP & Business Wallet.
-
Add explanation of confidence method and threat modelling etc. w3c/vc-dpp-bw#16, by @philarcher.
-
Explain how VCs go beyond normal digitally signed documents w3c/vc-dpp-bw#15, by @philarcher.
-
-
4 pull requests opened in the VC DPP & Business Wallet.
-
- added UC scenario file for BW w3c/vc-dpp-bw#18, by @ngwlf.
-
Raising and linking to issues w3c/vc-dpp-bw#17, by @philarcher.
-
Update index.md w3c/vc-dpp-bw#14, by @susanne-guth-orlowski.
-
Digital twin rash w3c/vc-dpp-bw#13, by @philarcher.
-
-
6 pull requests merged in the VC DPP & Business Wallet.
-
Raising and linking to issues w3c/vc-dpp-bw#17.
-
Digital Links as credentialSubject.id w3c/vc-dpp-bw#10.
-
Update index.md w3c/vc-dpp-bw#14.
-
- added UC scenario file for BW w3c/vc-dpp-bw#18.
-
SGO Update index.md w3c/vc-dpp-bw#12.
-
Digital twin rash w3c/vc-dpp-bw#13.
-
-
1 pull request in the VC DPP & Business Wallet received 11 new comments.
TR publications
-
11 documents published.
-
Confidence Method v1.0 published twice as a Working Draft. History of Confidence Method v1.0
-
Verifiable Credential Barcodes v1.0 published twice as a Working Draft. History of Verifiable Credential Barcodes v1.0
-
Recognized Entities v1.0 published as a Working Draft. History of Recognized Entities v1.0
-
VCALM v1.0 published twice as a Working Draft. History of VCALM v1.0
-
Verifiable Credential Forgery Defense v1.0 published as a Working Draft. History of Verifiable Credential Forgery Defense v1.0
-
Verifiable Credentials Overview v1.0 published as a Note. History of Verifiable Credentials Overview v1.0
-
Verifiable Credentials Overview v1.1 published twice as a Draft Note. History of Verifiable Credentials Overview v1.1
-
Past meetings
Participants
-
4 participants joined.
-
Niranjana Subrahmanyam (Siemens AG) joined.
-
Saad Bin Shams (Siemens AG) joined.
-
Rodrigo Menéndez (Universidad Politécnica de Madrid) joined.
-
Michael Linck (Google LLC) joined.
-
-
1 participant left.
-
Poh Hendry (W3C Invited Experts) left.
-
-
2 organizations joined.
-
Microsoft Corporation joined.
-
Google LLC joined.
-
GitHub
w3c/vc-recognized-entities
-
7 issues opened.
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105, by @onthebreeze.
-
Add ref to Forgery Defense to threat model w3c/vc-recognized-entities#100, by @philarcher.
-
Internationalization Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#98, by @msporny.
-
Accessibility Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#97, by @msporny.
-
Security and Privacy Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#96, by @msporny.
-
Horizontal Reviews for VC Recognized Entities v1.0 w3c/vc-recognized-entities#95, by @msporny.
-
Create vocabulary term definitions and anchors in spec w3c/vc-recognized-entities#92, by @iherman.
-
-
9 issues closed.
-
validation rules for chained credentials w3c/vc-recognized-entities#90.
-
Broken links in Recognized Entities v1.0 w3c/vc-recognized-entities#78.
-
Reorder forward references w3c/vc-recognized-entities#84.
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44.
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43.
-
Explain that `outputValidation` requires governance w3c/vc-recognized-entities#41.
-
Outline considerations that are out of scope w3c/vc-recognized-entities#4.
-
Document risk surface of peer sharing w3c/vc-recognized-entities#3.
-
Document danger of first mover advantages w3c/vc-recognized-entities#2.
-
-
16 issues received 28 new comments.
-
validation rules for chained credentials w3c/vc-recognized-entities#90 (6 comments by @iherman, @msporny, @onthebreeze)
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105 (4 comments by @msporny, @onthebreeze, @sankarshanmukhopadhyay)
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89 (3 comments by @iherman, @msporny, @swcurran)
-
Horizontal Reviews for VC Recognized Entities v1.0 w3c/vc-recognized-entities#95 (2 comments by @iherman)
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49 (1 comment by @msporny)
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44 (1 comment by @msporny)
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43 (1 comment by @msporny)
-
Explain that `outputValidation` requires governance w3c/vc-recognized-entities#41 (1 comment by @msporny)
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @iherman)
-
-
8 pull requests opened.
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106, by @msporny.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104, by @msporny.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103, by @msporny.
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102, by @BigBlueHat.
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101, by @philarcher.
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99, by @msporny.
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94, by @msporny.
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93, by @msporny.
-
-
7 pull requests merged.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103.
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102.
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99.
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101.
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94.
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93.
-
Add initial attempt at threat model. w3c/vc-recognized-entities#82.
-
-
10 pull requests received 81 new comments.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103 (29 comments by @dlongley, @Fak3, @iherman, @msporny, @philarcher, @TallTed, @tsnyder-gs1us)
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104 (20 comments by @iherman, @JohnOnGH, @msporny, @onthebreeze, @TallTed)
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99 (11 comments by @BigBlueHat, @dlongley, @iherman, @longpd, @msporny, @PatStLouis, @philarcher, @swcurran)
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102 (8 comments by @BigBlueHat, @msporny, @philarcher, @TallTed)
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94 (6 comments by @dlongley, @iherman, @msporny, @onthebreeze, @philarcher)
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106 (3 comments by @iherman, @msporny, @TallTed)
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101 (1 comment by @dlongley)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (1 comment by @shigeya)
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93 (1 comment by @iherman)
-
w3c/vc-data-integrity
-
3 issues opened.
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354, by @jandrieu.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352, by @Wind4Greg.
-
Additional considerations for compound documents (merging secured documents) w3c/vc-data-integrity#350, by @trwnh.
-
-
6 issues received 15 new comments.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352 (4 comments by @dlongley, @Wind4Greg)
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348 (4 comments by @dlongley, @filip26, @TallTed, @Wind4Greg)
-
Additional considerations for compound documents (merging secured documents) w3c/vc-data-integrity#350 (3 comments by @filip26, @trwnh)
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354 (2 comments by @dlongley, @jandrieu)
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @Wind4Greg)
-
Potential internal contradiction around verificationMethod w3c/vc-data-integrity#349 (1 comment by @filip26)
-
-
4 pull requests opened.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356, by @Wind4Greg.
-
Add copyright notice and license information w3c/vc-data-integrity#355, by @jandrieu.
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353, by @Wind4Greg.
-
Add basic threat model to specification w3c/vc-data-integrity#351, by @msporny.
-
-
2 pull requests merged.
-
Add basic threat model to specification w3c/vc-data-integrity#351.
-
Update echidna w3c/vc-data-integrity#347.
-
-
3 pull requests received 57 new comments.
-
Add basic threat model to specification w3c/vc-data-integrity#351 (11 comments by @dlongley, @iherman, @msporny, @TallTed, @wes-smith, @Wind4Greg)
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353 (4 comments by @dlongley, @iherman, @Wind4Greg)
w3c/vcalm
-
20 issues opened.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686, by @BigBlueHat.
-
Add link to threat model document in main spec w3c/vcalm#683, by @eric-schuh.
-
Update threat_model folder name to threat-model w3c/vcalm#682, by @eric-schuh.
-
Unify "protocol objects" language across threat model w3c/vcalm#678, by @eric-schuh.
-
Add dfn links for DC API and VC API references in threat model w3c/vcalm#676, by @eric-schuh.
-
Add DFD description w3c/vcalm#675, by @eric-schuh.
-
Add W3C license to threat model copyright.txt and LICENSE files w3c/vcalm#674, by @eric-schuh.
-
Add response(s) to T28 w3c/vcalm#673, by @eric-schuh.
-
Review T29 and potential responses w3c/vcalm#672, by @eric-schuh.
-
Refactor text for R21 to give more precise advice w3c/vcalm#670, by @eric-schuh.
-
Unify "Misconfigured <Component> instance" threats w3c/vcalm#669, by @eric-schuh.
-
Add tags to threats w3c/vcalm#668, by @eric-schuh.
-
Define a query type for confidence methods in general w3c/vcalm#660, by @dlongley.
-
6 issues closed.
-
Mediated Presentation definition w3c/vcalm#541.
-
Simplify OAS file for Presentations/Credentials w3c/vcalm#653.
-
Define zcap actions w3c/vcalm#644.
-
Add detail to OAuth 2.0 scopes w3c/vcalm#643.
-
-
28 issues received 50 new comments.
-
Add sequence diagrams for issuance, presentation, and verification w3c/vcalm#561 (7 comments by @bparth24, @eric-schuh, @kezike, @msporny, @TallTed)
-
Consider using `web+interaction:` scheme to allow web apps to register to receive interaction URLs w3c/vcalm#634 (4 comments by @dlongley, @kezike)
-
No way for an exchange participant to decline/terminate an exchange w3c/vcalm#664 (3 comments by @dlongley, @kezike)
-
Should the information here reflect aspirational state (`WD`) instead of current state (`FPWD`)? w3c/vcalm#654 (3 comments by @kezike, @msporny, @TallTed)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (3 comments by @kezike, @PatStLouis, @tidoust)
-
Define a query type for confidence methods in general w3c/vcalm#660 (2 comments by @dlongley, @kezike)
-
Add normative algorithm for QueryByExample matching w3c/vcalm#574 (2 comments by @bparth24, @kezike)
-
Add W3C license to threat model copyright.txt and LICENSE files w3c/vcalm#674 (2 comments by @BigBlueHat, @eric-schuh)
-
Unspecified enumeration of accepted values for template properties w3c/vcalm#449 (1 comment by @kezike)
-
Add workflow step property to indicate whether a domain should be included w3c/vcalm#460 (1 comment by @kezike)
-
`acceptedIssuers` examples incorrect (need to be updated to match definition) w3c/vcalm#658 (1 comment by @PatStLouis)
-
-
11 pull requests opened.
-
Add threat model section to security considerations w3c/vcalm#685, by @eric-schuh.
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684, by @eric-schuh.
-
Update local bibliography refs w3c/vcalm#681, by @kezike.
-
Add interaction protocol table w3c/vcalm#680, by @kezike.
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679, by @kezike.
-
Add support for multiple VPs in exchange participation messages w3c/vcalm#666, by @kezike.
-
Fix exchange interaction diagrams w3c/vcalm#665, by @kezike.
-
Add support for retrieving current exchange VPR w3c/vcalm#663, by @kezike.
-
Simplify credential and presentation OAS schemas w3c/vcalm#661, by @PatStLouis.
-
Add two variants to `acceptedIssuers` example. w3c/vcalm#659, by @BigBlueHat.
-
-
8 pull requests merged.
-
Fix exchange interaction diagrams w3c/vcalm#665.
-
Simplify credential and presentation OAS schemas w3c/vcalm#661.
-
Add two variants to `acceptedIssuers` example. w3c/vcalm#659.
-
Define valid ZCAP actions w3c/vcalm#657.
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656.
-
Adding VCALM Threat Model w3c/vcalm#655.
-
13 pull requests received 166 new comments.
-
Adding VCALM Threat Model w3c/vcalm#655 (77 comments by @BigBlueHat, @dlongley, @eric-schuh, @jandrieu, @PatStLouis, @TallTed)
-
Simplify credential and presentation OAS schemas w3c/vcalm#661 (18 comments by @kezike, @PatStLouis, @TallTed)
-
Add support for retrieving current exchange VPR w3c/vcalm#663 (17 comments by @dlongley, @kezike, @PatStLouis, @TallTed)
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656 (14 comments by @dlongley, @kezike, @TallTed)
-
Add interaction protocol table w3c/vcalm#680 (7 comments by @dlongley, @jandrieu, @kezike, @PatStLouis)
-
Add support for multiple VPs in exchange participation messages w3c/vcalm#666 (6 comments by @dlongley, @kezike)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (4 comments by @TallTed)
-
Add threat model section to security considerations w3c/vcalm#685 (3 comments by @dlongley, @TallTed)
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679 (2 comments by @kezike, @PatStLouis)
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651 (1 comment by @TallTed)
-
w3c/vc-dpp-bw
-
2 issues opened.
-
Clarify credential subject and unique product identifier w3c/vc-dpp-bw#11, by @carolynnbernier.
-
Clarify Credential Subject / Holder Binding for DPP VCs w3c/vc-dpp-bw#9, by @Echsecutor.
-
-
1 issue received 1 new comment.
-
Clarify credential subject and unique product identifier w3c/vc-dpp-bw#11 (1 comment by @susanne-guth-orlowski)
-
-
3 pull requests opened.
-
SGO Update index.md w3c/vc-dpp-bw#12, by @susanne-guth-orlowski.
-
Digital Links as credentialSubject.id w3c/vc-dpp-bw#10, by @Echsecutor.
-
Missed a replace data- attribute w3c/vc-dpp-bw#8, by @iherman.
-
-
1 pull request closed.
-
Missed a replace data- attribute w3c/vc-dpp-bw#8.
-
-
2 pull requests received 2 new comments.
w3c/vc-overview
-
7 issues opened.
-
Section on WG notes? w3c/vc-overview#35, by @iherman.
-
Lifecycle details from version 1.0? w3c/vc-overview#34, by @iherman.
-
Barcode processing plugin did not seem to work... w3c/vc-overview#33, by @iherman.
-
Review of the SD description w3c/vc-overview#32, by @iherman.
-
SD and Quantum with regard jose cose? w3c/vc-overview#31, by @iherman.
-
Linked resources example json schemas? w3c/vc-overview#30, by @iherman.
-
Render method examples w3c/vc-overview#29, by @iherman.
-
-
3 issues received 5 new comments.
-
2 pull requests opened.
-
Removed qr generation and unknown context files w3c/vc-overview#37, by @iherman.
-
Added issue references w3c/vc-overview#36, by @iherman.
-
-
2 pull requests merged.
-
Removed qr generation and unknown context files w3c/vc-overview#37.
-
Added issue references w3c/vc-overview#36.
-
w3c/vc-barcodes
-
6 issues opened.
-
Threat model: add section to track improvements needed. w3c/vc-barcodes#67, by @wes-smith.
-
Threat model: display ERTA types and link to specification w3c/vc-barcodes#66, by @wes-smith.
-
Missing documentation for opticalDataBytes generation in Examples 8 and 15 w3c/vc-barcodes#64, by @filip26.
-
Improve clarity when discussing credentialSubject.type values w3c/vc-barcodes#63, by @wes-smith.
-
Proper class and property specifications, please w3c/vc-barcodes#61, by @iherman.
-
Terse bitstringStatusListEntry only in barcode? w3c/vc-barcodes#60, by @iherman.
-
-
5 issues closed.
-
Create a Threat Model for VC Barcodes w3c/vc-barcodes#41.
-
The introductory examples may need some care... w3c/vc-barcodes#49.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34.
-
Allow PDF417 barcode types beyond AAMVA Driver's License w3c/vc-barcodes#22.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33.
-
-
4 issues received 5 new comments.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34 (2 comments by @TallTed, @wes-smith)
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @wes-smith)
-
-
3 pull requests opened.
-
Add threat model. w3c/vc-barcodes#65, by @wes-smith.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62, by @philarcher.
-
Generalize "augment an existing barcode" feature, refactor algorithms, clean up cruft. w3c/vc-barcodes#59, by @wes-smith.
-
-
3 pull requests merged.
-
Add threat model. w3c/vc-barcodes#65.
-
Update introductory examples. w3c/vc-barcodes#52.
-
-
4 pull requests received 89 new comments.
-
Add threat model. w3c/vc-barcodes#65 (57 comments by @dlongley, @iherman, @jandrieu, @simoneonofri, @TallTed, @wes-smith)
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62 (15 comments by @ewoogit, @philarcher, @TallTed, @wes-smith)
-
Generalize "augment an existing barcode" feature, refactor algorithms, clean up cruft. w3c/vc-barcodes#59 (12 comments by @ewoogit, @iherman, @wes-smith)
-
w3c/vc-confidence-method
-
3 issues opened.
-
Change the short name w3c/vc-confidence-method#46, by @denkeni.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41, by @jandrieu.
-
-
5 issues received 11 new comments.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (4 comments by @amir-hameed-mir, @dlongley)
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33 (3 comments by @denkeni, @jandrieu, @TallTed)
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45, by @denkeni.
-
Add biometric image section w3c/vc-confidence-method#44, by @denkeni.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43, by @msporny.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42, by @ScottJeezey.
-
-
1 pull request merged.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42.
-
-
3 pull requests received 20 new comments.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42 (12 comments by @dlongley, @TallTed)
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45 (5 comments by @dlongley, @msporny)
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43 (3 comments by @dlongley, @iherman, @TallTed)
-
w3c/vc-wg
-
1 issue opened.
-
Progress Tracker w3c/vc-wg#14, by @philarcher.
-
-
2 issues received 2 new comments.
-
1 pull request opened.
-
Placing the new terms in vocabularies and context files w3c/vc-wg#15, by @iherman.
-
w3c/vc-bitstring-status-list-test-suite
-
2 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-bitstring-status-list-test-suite#72, by @BigBlueHat.
-
upgrade deps w3c/vc-bitstring-status-list-test-suite#71, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update vc-test-suite-implementations at runtime. w3c/vc-bitstring-status-list-test-suite#72.
-
upgrade deps w3c/vc-bitstring-status-list-test-suite#71.
-
w3c/vc-di-bbs-test-suite
-
2 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-bbs-test-suite#81, by @BigBlueHat.
-
upgrade deps w3c/vc-di-bbs-test-suite#80, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-bbs-test-suite#81.
-
upgrade deps w3c/vc-di-bbs-test-suite#80.
-
w3c/vc-di-ed25519signature2020-test-suite
-
2 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-ed25519signature2020-test-suite#62, by @BigBlueHat.
-
upgrade deps w3c/vc-di-ed25519signature2020-test-suite#61, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-ed25519signature2020-test-suite#62.
-
upgrade deps w3c/vc-di-ed25519signature2020-test-suite#61.
-
w3c/vc-di-ecdsa-test-suite
-
2 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-ecdsa-test-suite#122, by @BigBlueHat.
-
upgrade deps w3c/vc-di-ecdsa-test-suite#121, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-ecdsa-test-suite#122.
-
upgrade deps w3c/vc-di-ecdsa-test-suite#121.
-
w3c/vc-di-eddsa-test-suite
-
2 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-eddsa-test-suite#71, by @BigBlueHat.
-
upgrade deps w3c/vc-di-eddsa-test-suite#70, by @BigBlueHat.
-
-
2 pull requests merged.
-
Update vc-test-suite-implementations at runtime. w3c/vc-di-eddsa-test-suite#71.
-
upgrade deps w3c/vc-di-eddsa-test-suite#70.
-
w3c/vc-data-model-2.0-test-suite
-
3 pull requests opened.
-
Update vc-test-suite-implementations at runtime. w3c/vc-data-model-2.0-test-suite#175, by @BigBlueHat.
-
Fix enveloped proof existence assertion w3c/vc-data-model-2.0-test-suite#174, by @burdettadam.
-
Unignore package-lock.json. w3c/vc-data-model-2.0-test-suite#173, by @BigBlueHat.
-
-
1 pull request merged.
-
Add CODEOWNERS with initial owners. w3c/vc-data-model-2.0-test-suite#171.
-
-
1 pull request closed.
-
Override uuid to ^11.1.1 to clear npm audit findings w3c/vc-data-model-2.0-test-suite#170.
-
-
2 pull requests received 3 new comments.
-
Fix enveloped proof existence assertion w3c/vc-data-model-2.0-test-suite#174 (2 comments by @burdettadam)
-
Override uuid to ^11.1.1 to clear npm audit findings w3c/vc-data-model-2.0-test-suite#170 (1 comment by @BigBlueHat)
-
w3c/vc-forgery-defense
-
2 pull requests opened.
-
Generalize witness seed format. w3c/vc-forgery-defense#5, by @wes-smith.
-
update ED URL w3c/vc-forgery-defense#4, by @deniak.
-
-
2 pull requests merged.
-
Added echidna script w3c/vc-forgery-defense#3.
-
update ED URL w3c/vc-forgery-defense#4.
-
-
2 pull requests received 2 new comments.
w3c/vc-render-method
-
2 issues opened.
-
Finalize names for render method categories w3c/vc-render-method#55, by @kezike.
-
-
2 issues received 4 new comments.
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (2 comments by @dlongley, @iherman)
-
Finalize names for render method categories w3c/vc-render-method#55 (2 comments by @iherman, @TallTed)
-
-
3 pull requests opened.
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58, by @dmitrizagidulin.
-
Remove leftover template/mustache mentions. w3c/vc-render-method#57, by @dmitrizagidulin.
-
Restore json-card section formatting. w3c/vc-render-method#56, by @dmitrizagidulin.
-
-
4 pull requests merged.
-
Remove leftover template/mustache mentions. w3c/vc-render-method#57.
-
Restore json-card section formatting. w3c/vc-render-method#56.
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49.
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39.
-
-
3 pull requests received 4 new comments.
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49 (1 comment by @dmitrizagidulin)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (1 comment by @iherman)
w3c/vc-test-suite-implementations
-
2 pull requests opened.
-
Update ZCAPs for DigitalBazaar config. w3c/vc-test-suite-implementations#123, by @BigBlueHat.
-
upgrade deps w3c/vc-test-suite-implementations#122, by @BigBlueHat.
-
-
2 pull requests merged.
-
upgrade deps w3c/vc-test-suite-implementations#122.
-
Update ZCAPs for DigitalBazaar config. w3c/vc-test-suite-implementations#123.
-
w3c/vc-data-model
-
1 issue opened.
-
Terminology for processing modes w3c/vc-data-model#1634, by @filip26.
-
-
6 issues received 10 new comments.
-
Schema lacking `format` field w3c/vc-data-model#1619 (3 comments by @brentzundel, @iherman, @Oran-Dan)
-
multiple comments on the introduction section w3c/vc-data-model#1592 (2 comments by @dmitrizagidulin, @iherman)
-
-
1 pull request opened.
-
Update introduction sections for clarity. w3c/vc-data-model#1636, by @dmitrizagidulin.
-
-
2 pull requests received 5 new comments.
w3c/vc-di-eddsa
-
1 issue opened.
-
1 issue received 10 new comments.
-
[3.2.2 Verify Proof (eddsa-rdfc-2022)] makes reference to "proof value" (instead of "proof graph"?) w3c/vc-di-eddsa#117 (10 comments by @iherman, @trwnh, @Wind4Greg)
-
w3c/vcalm-test-suite
-
2 pull requests opened.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#3, by @PatStLouis.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#2, by @PatStLouis.
-
-
1 pull request closed.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#2.
-
-
1 pull request received 1 new comment.
w3c/cid
-
2 issues received 7 new comments.
-
6 pull requests opened.
-
update echidna file w3c/cid#177, by @brentzundel.
-
Revert "Revert "make common.js match vcdm repo"" w3c/cid#176, by @brentzundel.
-
Revert "make common.js match vcdm repo" w3c/cid#175, by @brentzundel.
-
make common.js match vcdm repo w3c/cid#174, by @brentzundel.
-
remove duplicate definition w3c/cid#173, by @brentzundel.
-
Update controlled identifier definition in index.html w3c/cid#172, by @jandrieu.
-
-
6 pull requests merged.
-
update echidna file w3c/cid#177.
-
Revert "Revert "make common.js match vcdm repo"" w3c/cid#176.
-
Revert "make common.js match vcdm repo" w3c/cid#175.
-
make common.js match vcdm repo w3c/cid#174.
-
remove duplicate definition w3c/cid#173.
-
-
3 pull requests received 5 new comments.
-
Add CID alias for controlled identifier document term w3c/cid#171 (3 comments by @brentzundel, @jandrieu)
-
w3c/vc-di-quantum-resistant
-
1 issue opened.
-
Use deterministic signatures in test vectors w3c/vc-di-quantum-resistant#39, by @Wind4Greg.
-
-
1 issue closed.
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33.
-
-
1 pull request opened.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40, by @Wind4Greg.
-
-
1 pull request merged.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37.
-
-
1 pull request received 16 new comments.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40 (16 comments by @dlongley)
-
w3c/vc-di-ecdsa
-
1 issue opened.
-
Incorrect C14N in test vectors (A.4) w3c/vc-di-ecdsa#105, by @filip26.
-
-
1 issue received 1 new comment.
VC Recognized Entities
Past meetings
GitHub
w3c/vc-recognized-entities
-
7 issues opened in the VC Recognized Entities.
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105, by @onthebreeze.
-
Add ref to Forgery Defense to threat model w3c/vc-recognized-entities#100, by @philarcher.
-
Internationalization Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#98, by @msporny.
-
Accessibility Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#97, by @msporny.
-
Security and Privacy Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#96, by @msporny.
-
Horizontal Reviews for VC Recognized Entities v1.0 w3c/vc-recognized-entities#95, by @msporny.
-
Create vocabulary term definitions and anchors in spec w3c/vc-recognized-entities#92, by @iherman.
-
-
9 issues closed in the VC Recognized Entities.
-
validation rules for chained credentials w3c/vc-recognized-entities#90.
-
Broken links in Recognized Entities v1.0 w3c/vc-recognized-entities#78.
-
Reorder forward references w3c/vc-recognized-entities#84.
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44.
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43.
-
Explain that `outputValidation` requires governance w3c/vc-recognized-entities#41.
-
Outline considerations that are out of scope w3c/vc-recognized-entities#4.
-
Document risk surface of peer sharing w3c/vc-recognized-entities#3.
-
Document danger of first mover advantages w3c/vc-recognized-entities#2.
-
-
16 issues in the VC Recognized Entities received 28 new comments.
-
validation rules for chained credentials w3c/vc-recognized-entities#90 (6 comments by @iherman, @msporny, @onthebreeze)
-
Separate discovery from verification in the Algorithms section w3c/vc-recognized-entities#105 (4 comments by @msporny, @onthebreeze, @sankarshanmukhopadhyay)
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89 (3 comments by @iherman, @msporny, @swcurran)
-
Horizontal Reviews for VC Recognized Entities v1.0 w3c/vc-recognized-entities#95 (2 comments by @iherman)
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49 (1 comment by @msporny)
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44 (1 comment by @msporny)
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43 (1 comment by @msporny)
-
Explain that `outputValidation` requires governance w3c/vc-recognized-entities#41 (1 comment by @msporny)
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @iherman)
-
-
8 pull requests opened in the VC Recognized Entities.
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106, by @msporny.
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104, by @msporny.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103, by @msporny.
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102, by @BigBlueHat.
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101, by @philarcher.
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99, by @msporny.
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94, by @msporny.
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93, by @msporny.
-
-
7 pull requests merged in the VC Recognized Entities.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103.
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102.
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99.
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101.
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94.
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93.
-
Add initial attempt at threat model. w3c/vc-recognized-entities#82.
-
-
10 pull requests in the VC Recognized Entities received 81 new comments.
-
Add complete GS1 Federated Identifier example. w3c/vc-recognized-entities#103 (29 comments by @dlongley, @Fak3, @iherman, @msporny, @philarcher, @TallTed, @tsnyder-gs1us)
-
Add complete UN GRID example to appendix w3c/vc-recognized-entities#104 (20 comments by @iherman, @JohnOnGH, @msporny, @onthebreeze, @TallTed)
-
Add section on identifier-based discovery w3c/vc-recognized-entities#99 (11 comments by @BigBlueHat, @dlongley, @iherman, @longpd, @msporny, @PatStLouis, @philarcher, @swcurran)
-
Reapply change request from earlier PR #101 w3c/vc-recognized-entities#102 (8 comments by @BigBlueHat, @msporny, @philarcher, @TallTed)
-
Add section on credential-based discovery. w3c/vc-recognized-entities#94 (6 comments by @dlongley, @iherman, @msporny, @onthebreeze, @philarcher)
-
Add validFrom/validUntil to recognized actions. w3c/vc-recognized-entities#106 (3 comments by @iherman, @msporny, @TallTed)
-
Adding the GS1 use case by ref to main VC-Use-Cases w3c/vc-recognized-entities#101 (1 comment by @dlongley)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (1 comment by @shigeya)
-
Add "display information" and "credential type" use cases. w3c/vc-recognized-entities#93 (1 comment by @iherman)
-
VC Barcodes and Data Integrity
Past meetings
-
4 meetings of the VC Barcodes and Data Integrity.
GitHub
w3c/vc-data-integrity
-
3 issues opened in the VC Barcodes and Data Integrity.
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354, by @jandrieu.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352, by @Wind4Greg.
-
Additional considerations for compound documents (merging secured documents) w3c/vc-data-integrity#350, by @trwnh.
-
-
6 issues in the VC Barcodes and Data Integrity received 15 new comments.
-
Add High Level Definition of Selective Disclosure w3c/vc-data-integrity#352 (4 comments by @dlongley, @Wind4Greg)
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348 (4 comments by @dlongley, @filip26, @TallTed, @Wind4Greg)
-
Additional considerations for compound documents (merging secured documents) w3c/vc-data-integrity#350 (3 comments by @filip26, @trwnh)
-
Copyrigh notice on threat-model.js needs to be restored w3c/vc-data-integrity#354 (2 comments by @dlongley, @jandrieu)
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @Wind4Greg)
-
Potential internal contradiction around verificationMethod w3c/vc-data-integrity#349 (1 comment by @filip26)
-
-
4 pull requests opened in the VC Barcodes and Data Integrity.
-
Explaining Selective Disclosure w3c/vc-data-integrity#356, by @Wind4Greg.
-
Add copyright notice and license information w3c/vc-data-integrity#355, by @jandrieu.
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353, by @Wind4Greg.
-
Add basic threat model to specification w3c/vc-data-integrity#351, by @msporny.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Add basic threat model to specification w3c/vc-data-integrity#351.
-
Update echidna w3c/vc-data-integrity#347.
-
-
3 pull requests in the VC Barcodes and Data Integrity received 57 new comments.
-
Add basic threat model to specification w3c/vc-data-integrity#351 (11 comments by @dlongley, @iherman, @msporny, @TallTed, @wes-smith, @Wind4Greg)
-
Add Cryptosuite Common Algorithms w3c/vc-data-integrity#353 (4 comments by @dlongley, @iherman, @Wind4Greg)
w3c/vc-barcodes
-
6 issues opened in the VC Barcodes and Data Integrity.
-
Threat model: add section to track improvements needed. w3c/vc-barcodes#67, by @wes-smith.
-
Threat model: display ERTA types and link to specification w3c/vc-barcodes#66, by @wes-smith.
-
Missing documentation for opticalDataBytes generation in Examples 8 and 15 w3c/vc-barcodes#64, by @filip26.
-
Improve clarity when discussing credentialSubject.type values w3c/vc-barcodes#63, by @wes-smith.
-
Proper class and property specifications, please w3c/vc-barcodes#61, by @iherman.
-
Terse bitstringStatusListEntry only in barcode? w3c/vc-barcodes#60, by @iherman.
-
-
5 issues closed in the VC Barcodes and Data Integrity.
-
Create a Threat Model for VC Barcodes w3c/vc-barcodes#41.
-
The introductory examples may need some care... w3c/vc-barcodes#49.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34.
-
Allow PDF417 barcode types beyond AAMVA Driver's License w3c/vc-barcodes#22.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33.
-
-
4 issues in the VC Barcodes and Data Integrity received 5 new comments.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34 (2 comments by @TallTed, @wes-smith)
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @wes-smith)
-
-
3 pull requests opened in the VC Barcodes and Data Integrity.
-
Add threat model. w3c/vc-barcodes#65, by @wes-smith.
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62, by @philarcher.
-
Generalize "augment an existing barcode" feature, refactor algorithms, clean up cruft. w3c/vc-barcodes#59, by @wes-smith.
-
-
3 pull requests merged in the VC Barcodes and Data Integrity.
-
Add threat model. w3c/vc-barcodes#65.
-
Update introductory examples. w3c/vc-barcodes#52.
-
-
4 pull requests in the VC Barcodes and Data Integrity received 89 new comments.
-
Add threat model. w3c/vc-barcodes#65 (57 comments by @dlongley, @iherman, @jandrieu, @simoneonofri, @TallTed, @wes-smith)
-
Secure content, not secure barcode Will fix #58 w3c/vc-barcodes#62 (15 comments by @ewoogit, @philarcher, @TallTed, @wes-smith)
-
Generalize "augment an existing barcode" feature, refactor algorithms, clean up cruft. w3c/vc-barcodes#59 (12 comments by @ewoogit, @iherman, @wes-smith)
-
w3c/vc-forgery-defense
-
2 pull requests opened in the VC Barcodes and Data Integrity.
-
Generalize witness seed format. w3c/vc-forgery-defense#5, by @wes-smith.
-
update ED URL w3c/vc-forgery-defense#4, by @deniak.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Added echidna script w3c/vc-forgery-defense#3.
-
update ED URL w3c/vc-forgery-defense#4.
-
-
2 pull requests in the VC Barcodes and Data Integrity received 2 new comments.
w3c/vc-di-eddsa
-
1 issue opened in the VC Barcodes and Data Integrity.
-
1 issue in the VC Barcodes and Data Integrity received 10 new comments.
-
[3.2.2 Verify Proof (eddsa-rdfc-2022)] makes reference to "proof value" (instead of "proof graph"?) w3c/vc-di-eddsa#117 (10 comments by @iherman, @trwnh, @Wind4Greg)
-
w3c/vc-di-quantum-resistant
-
1 issue opened in the VC Barcodes and Data Integrity.
-
Use deterministic signatures in test vectors w3c/vc-di-quantum-resistant#39, by @Wind4Greg.
-
-
1 issue closed in the VC Barcodes and Data Integrity.
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33.
-
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40, by @Wind4Greg.
-
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37.
-
-
1 pull request in the VC Barcodes and Data Integrity received 16 new comments.
-
Replace "cypher" term with "crypto" throughout the document w3c/vc-di-quantum-resistant#40 (16 comments by @dlongley)
-
w3c/vc-di-ecdsa
-
1 issue opened in the VC Barcodes and Data Integrity.
-
Incorrect C14N in test vectors (A.4) w3c/vc-di-ecdsa#105, by @filip26.
-
-
1 issue in the VC Barcodes and Data Integrity received 1 new comment.
VC API for Lifecycle Management
Past meetings
-
4 meetings of the VC API for Lifecycle Management.
GitHub
w3c/vcalm
-
20 issues opened in the VC API for Lifecycle Management.
-
Add normative reference to `jsonata` definition. w3c/vcalm#686, by @BigBlueHat.
-
Add link to threat model document in main spec w3c/vcalm#683, by @eric-schuh.
-
Update threat_model folder name to threat-model w3c/vcalm#682, by @eric-schuh.
-
Unify "protocol objects" language across threat model w3c/vcalm#678, by @eric-schuh.
-
Add dfn links for DC API and VC API references in threat model w3c/vcalm#676, by @eric-schuh.
-
Add DFD description w3c/vcalm#675, by @eric-schuh.
-
Add W3C license to threat model copyright.txt and LICENSE files w3c/vcalm#674, by @eric-schuh.
-
Add response(s) to T28 w3c/vcalm#673, by @eric-schuh.
-
Review T29 and potential responses w3c/vcalm#672, by @eric-schuh.
-
Refactor text for R21 to give more precise advice w3c/vcalm#670, by @eric-schuh.
-
Unify "Misconfigured <Component> instance" threats w3c/vcalm#669, by @eric-schuh.
-
Add tags to threats w3c/vcalm#668, by @eric-schuh.
-
Define a query type for confidence methods in general w3c/vcalm#660, by @dlongley.
-
6 issues closed in the VC API for Lifecycle Management.
-
Mediated Presentation definition w3c/vcalm#541.
-
Simplify OAS file for Presentations/Credentials w3c/vcalm#653.
-
Define zcap actions w3c/vcalm#644.
-
Add detail to OAuth 2.0 scopes w3c/vcalm#643.
-
-
28 issues in the VC API for Lifecycle Management received 50 new comments.
-
Add sequence diagrams for issuance, presentation, and verification w3c/vcalm#561 (7 comments by @bparth24, @eric-schuh, @kezike, @msporny, @TallTed)
-
Consider using `web+interaction:` scheme to allow web apps to register to receive interaction URLs w3c/vcalm#634 (4 comments by @dlongley, @kezike)
-
No way for an exchange participant to decline/terminate an exchange w3c/vcalm#664 (3 comments by @dlongley, @kezike)
-
Should the information here reflect aspirational state (`WD`) instead of current state (`FPWD`)? w3c/vcalm#654 (3 comments by @kezike, @msporny, @TallTed)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (3 comments by @kezike, @PatStLouis, @tidoust)
-
Define a query type for confidence methods in general w3c/vcalm#660 (2 comments by @dlongley, @kezike)
-
Add normative algorithm for QueryByExample matching w3c/vcalm#574 (2 comments by @bparth24, @kezike)
-
Add W3C license to threat model copyright.txt and LICENSE files w3c/vcalm#674 (2 comments by @BigBlueHat, @eric-schuh)
-
Unspecified enumeration of accepted values for template properties w3c/vcalm#449 (1 comment by @kezike)
-
Add workflow step property to indicate whether a domain should be included w3c/vcalm#460 (1 comment by @kezike)
-
`acceptedIssuers` examples incorrect (need to be updated to match definition) w3c/vcalm#658 (1 comment by @PatStLouis)
-
-
11 pull requests opened in the VC API for Lifecycle Management.
-
Add threat model section to security considerations w3c/vcalm#685, by @eric-schuh.
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684, by @eric-schuh.
-
Update local bibliography refs w3c/vcalm#681, by @kezike.
-
Add interaction protocol table w3c/vcalm#680, by @kezike.
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679, by @kezike.
-
Add support for multiple VPs in exchange participation messages w3c/vcalm#666, by @kezike.
-
Fix exchange interaction diagrams w3c/vcalm#665, by @kezike.
-
Add support for retrieving current exchange VPR w3c/vcalm#663, by @kezike.
-
Simplify credential and presentation OAS schemas w3c/vcalm#661, by @PatStLouis.
-
Add two variants to `acceptedIssuers` example. w3c/vcalm#659, by @BigBlueHat.
-
-
8 pull requests merged in the VC API for Lifecycle Management.
-
Fix exchange interaction diagrams w3c/vcalm#665.
-
Simplify credential and presentation OAS schemas w3c/vcalm#661.
-
Add two variants to `acceptedIssuers` example. w3c/vcalm#659.
-
Define valid ZCAP actions w3c/vcalm#657.
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656.
-
Adding VCALM Threat Model w3c/vcalm#655.
-
13 pull requests in the VC API for Lifecycle Management received 166 new comments.
-
Adding VCALM Threat Model w3c/vcalm#655 (77 comments by @BigBlueHat, @dlongley, @eric-schuh, @jandrieu, @PatStLouis, @TallTed)
-
Simplify credential and presentation OAS schemas w3c/vcalm#661 (18 comments by @kezike, @PatStLouis, @TallTed)
-
Add support for retrieving current exchange VPR w3c/vcalm#663 (17 comments by @dlongley, @kezike, @PatStLouis, @TallTed)
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656 (14 comments by @dlongley, @kezike, @TallTed)
-
Add interaction protocol table w3c/vcalm#680 (7 comments by @dlongley, @jandrieu, @kezike, @PatStLouis)
-
Add support for multiple VPs in exchange participation messages w3c/vcalm#666 (6 comments by @dlongley, @kezike)
-
Add appendix with issuance, verification, and presentation examples w3c/vcalm#684 (4 comments by @TallTed)
-
Add threat model section to security considerations w3c/vcalm#685 (3 comments by @dlongley, @TallTed)
-
Add extra hints about using interaction URL as `redirectUrl` value w3c/vcalm#679 (2 comments by @kezike, @PatStLouis)
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651 (1 comment by @TallTed)
-
w3c/vcalm-test-suite
-
2 pull requests opened in the VC API for Lifecycle Management.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#3, by @PatStLouis.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#2, by @PatStLouis.
-
-
1 pull request closed in the VC API for Lifecycle Management.
-
Scaffold VCALM interop test suite w3c/vcalm-test-suite#2.
-
-
1 pull request in the VC API for Lifecycle Management received 1 new comment.
VC DPP & Business Wallet
Participants
-
3 participants joined the VC DPP & Business Wallet.
-
Saad Bin Shams joined.
-
Ingo Wolf joined.
-
Michael Linck joined.
-
-
1 participant left the VC DPP & Business Wallet.
-
Ingo Wolf left.
-
GitHub
w3c/vc-dpp-bw
-
2 issues opened in the VC DPP & Business Wallet.
-
Clarify credential subject and unique product identifier w3c/vc-dpp-bw#11, by @carolynnbernier.
-
Clarify Credential Subject / Holder Binding for DPP VCs w3c/vc-dpp-bw#9, by @Echsecutor.
-
-
1 issue in the VC DPP & Business Wallet received 1 new comment.
-
Clarify credential subject and unique product identifier w3c/vc-dpp-bw#11 (1 comment by @susanne-guth-orlowski)
-
-
3 pull requests opened in the VC DPP & Business Wallet.
-
SGO Update index.md w3c/vc-dpp-bw#12, by @susanne-guth-orlowski.
-
Digital Links as credentialSubject.id w3c/vc-dpp-bw#10, by @Echsecutor.
-
Missed a replace data- attribute w3c/vc-dpp-bw#8, by @iherman.
-
-
1 pull request closed in the VC DPP & Business Wallet.
-
Missed a replace data- attribute w3c/vc-dpp-bw#8.
-
-
2 pull requests in the VC DPP & Business Wallet received 2 new comments.
VC Confidence Method
GitHub
w3c/vc-confidence-method
-
3 issues opened in the VC Confidence Method.
-
Change the short name w3c/vc-confidence-method#46, by @denkeni.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41, by @jandrieu.
-
-
5 issues in the VC Confidence Method received 11 new comments.
-
Evaluate constraints that verifiers might request for biometrics w3c/vc-confidence-method#41 (4 comments by @amir-hameed-mir, @dlongley)
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33 (3 comments by @denkeni, @jandrieu, @TallTed)
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37 (1 comment by @msporny)
-
-
4 pull requests opened in the VC Confidence Method.
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45, by @denkeni.
-
Add biometric image section w3c/vc-confidence-method#44, by @denkeni.
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43, by @msporny.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42, by @ScottJeezey.
-
-
1 pull request merged in the VC Confidence Method.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42.
-
-
3 pull requests in the VC Confidence Method received 20 new comments.
-
Update BiometricVectorConfidenceMethod: field renames, vendor-neutral examples, use cases w3c/vc-confidence-method#42 (12 comments by @dlongley, @TallTed)
-
Align with the original VCDM 2.0 definition w3c/vc-confidence-method#45 (5 comments by @dlongley, @msporny)
-
Add sections on cryptographic keys and controlled identifiers w3c/vc-confidence-method#43 (3 comments by @dlongley, @iherman, @TallTed)
-
VC Render Method
Participants
-
2 participants joined the VC Render Method.
-
Kayode Ezike joined.
-
Nate Otto joined.
-
GitHub
w3c/vc-render-method
-
2 issues opened in the VC Render Method.
-
Finalize names for render method categories w3c/vc-render-method#55, by @kezike.
-
-
2 issues in the VC Render Method received 4 new comments.
-
Should we try to use a single type, e.g., "RenderSuiteRenderMethod", or multiple types for the known render methods of interest? w3c/vc-render-method#54 (2 comments by @dlongley, @iherman)
-
Finalize names for render method categories w3c/vc-render-method#55 (2 comments by @iherman, @TallTed)
-
-
3 pull requests opened in the VC Render Method.
-
Remove EmbeddedRenderer section. w3c/vc-render-method#58, by @dmitrizagidulin.
-
Remove leftover template/mustache mentions. w3c/vc-render-method#57, by @dmitrizagidulin.
-
Restore json-card section formatting. w3c/vc-render-method#56, by @dmitrizagidulin.
-
-
4 pull requests merged in the VC Render Method.
-
Remove leftover template/mustache mentions. w3c/vc-render-method#57.
-
Restore json-card section formatting. w3c/vc-render-method#56.
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49.
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39.
-
-
3 pull requests in the VC Render Method received 4 new comments.
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49 (1 comment by @dmitrizagidulin)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (1 comment by @iherman)
TR publications
-
9 documents published.
-
VCALM v1.0 published twice as a Working Draft. History of VCALM v1.0
-
Verifiable Credential Barcodes v1.0 published as a Working Draft. History of Verifiable Credential Barcodes v1.0
-
Confidence Method v1.0 published as a Working Draft. History of Confidence Method v1.0
-
Verifiable Credential Forgery Defense v1.0 published as a First Public Working Draft. History of Verifiable Credential Forgery Defense v1.0
-
Quantum-Resistant Cryptosuites v1.0 published as a First Public Working Draft. History of Quantum-Resistant Cryptosuites v1.0
-
Verifiable Credentials Overview published 3 times as a Note. History of Verifiable Credentials Overview
-
Past meetings
Participants
-
6 participants joined.
-
Eric Schuh (Legendary Requirements) joined.
-
Tony Choi (W3C Invited Experts) joined.
-
Marc-Andree Wolf (W3C Invited Experts) joined.
-
Seth van Hooland (W3C Invited Experts) joined.
-
Michael Shea (W3C Invited Experts) joined.
-
Tomasz Blachowicz (Mastercard Incorporated) joined.
-
-
3 participants left.
-
David Trang (Universities Admissions Centre) left.
-
Nick Clark (Universities Admissions Centre) left.
-
Dudley Collinson (Universities Admissions Centre) left.
-
-
2 organizations joined.
-
Siemens AG joined.
-
Mastercard Incorporated joined.
-
-
1 organization left.
-
Universities Admissions Centre left.
-
GitHub
w3c/vcalm
-
9 issues opened.
-
Simplify OAS file for Presentations/Credentials w3c/vcalm#653, by @PatStLouis.
-
Remote credential renderer use case w3c/vcalm#648, by @kezike.
-
Refine credential lifecycle diagram w3c/vcalm#647, by @kezike.
-
Refine all diagrams in the spec w3c/vcalm#646, by @kezike.
-
Address all oustanding issues in the spec text w3c/vcalm#645, by @kezike.
-
Define zcap actions w3c/vcalm#644, by @kezike.
-
Add detail to OAuth 2.0 scopes w3c/vcalm#643, by @kezike.
-
6 issues closed.
-
Address all oustanding issues in the spec text w3c/vcalm#645.
-
Refine all diagrams in the spec w3c/vcalm#646.
-
Fix URLs in the spec w3c/vcalm#640.
-
15 issues received 25 new comments.
-
Allow multiple presentations to be sent in a response via an array value for `verifiablePresentation` w3c/vcalm#649 (4 comments by @dlongley, @kezike)
-
Align examples and schemas with VC Data Model 2.0 (context + validFrom/validUntil) w3c/vcalm#635 (1 comment by @kezike)
-
Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage w3c/vcalm#629 (1 comment by @kezike)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (1 comment by @kezike)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @kezike)
-
-
6 pull requests opened.
-
Define valid ZCAP actions w3c/vcalm#657, by @kezike.
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656, by @kezike.
-
Adding VCALM Threat Model w3c/vcalm#655, by @eric-schuh.
-
Fix broken URL standard reference w3c/vcalm#652, by @kezike.
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651, by @kezike.
-
Update name for Recognized Entities spec w3c/vcalm#650, by @kezike.
-
-
5 pull requests merged.
-
Update name for Recognized Entities spec w3c/vcalm#650.
-
Fix broken URL standard reference w3c/vcalm#652.
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641.
-
8 pull requests received 108 new comments.
-
Adding VCALM Threat Model w3c/vcalm#655 (90 comments by @dlongley, @eric-schuh, @iherman, @jandrieu, @kezike, @msporny, @TallTed)
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641 (3 comments by @bparth24, @kezike, @TallTed)
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651 (2 comments by @kezike)
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636 (1 comment by @PatStLouis)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @TallTed)
-
w3c/vc-recognized-entities
-
8 issues opened.
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91, by @BigBlueHat.
-
validation rules for chained credentials w3c/vc-recognized-entities#90, by @onthebreeze.
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89, by @onthebreeze.
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88, by @TallTed.
-
Threat Model: diagram box type cues w3c/vc-recognized-entities#87, by @TallTed.
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86, by @iherman.
-
Rethinking verifying recognition chains w3c/vc-recognized-entities#85, by @KDean-Dolphin.
-
Reorder forward references w3c/vc-recognized-entities#84, by @KDean-Dolphin.
-
-
4 issues received 4 new comments.
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @BigBlueHat)
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66 (1 comment by @BigBlueHat)
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73 (1 comment by @iherman)
-
-
1 pull request opened.
-
Update threat model based on VCWG F2F feedback w3c/vc-recognized-entities#83, by @msporny.
-
-
1 pull request merged.
-
Update threat model based on VCWG F2F feedback w3c/vc-recognized-entities#83.
-
-
1 pull request received 8 new comments.
w3c/vc-data-integrity
-
2 issues opened.
-
Potential internal contradiction around verificationMethod w3c/vc-data-integrity#349, by @rmlearney-digicatapult.
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348, by @Wind4Greg.
-
-
1 issue received 3 new comments.
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348 (3 comments by @dlongley, @Wind4Greg)
-
w3c/vc-forgery-defense
-
3 pull requests opened.
-
Added echidna script w3c/vc-forgery-defense#3, by @iherman.
-
Prepare document for FPWD. w3c/vc-forgery-defense#2, by @wes-smith.
-
Add initial specification text. w3c/vc-forgery-defense#1, by @wes-smith.
-
-
2 pull requests merged.
-
Prepare document for FPWD. w3c/vc-forgery-defense#2.
-
Add initial specification text. w3c/vc-forgery-defense#1.
-
-
1 pull request received 1 new comment.
w3c/vc-di-quantum-resistant
-
5 issues opened.
-
Remove internal use of Cipher/Cypher wording w3c/vc-di-quantum-resistant#38, by @Wind4Greg.
-
Strengthen Section 4.1 — ML-DSA BUFF security properties need mechanistic rationale, implementation boundary, and updated citations w3c/vc-di-quantum-resistant#34, by @amir-hameed-mir.
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33, by @amir-hameed-mir.
-
Add `mldsa65-jcs-2024` Cryptosuite w3c/vc-di-quantum-resistant#31, by @amir-hameed-mir.
-
-
1 issue closed.
-
Support for Selective Disclosure w3c/vc-di-quantum-resistant#22.
-
-
6 issues received 25 new comments.
-
Add `mldsa65-jcs-2024` Cryptosuite w3c/vc-di-quantum-resistant#31 (13 comments by @amir-hameed-mir, @msporny, @Wind4Greg)
-
Strengthen Section 4.1 — ML-DSA BUFF security properties need mechanistic rationale, implementation boundary, and updated citations w3c/vc-di-quantum-resistant#34 (5 comments by @amir-hameed-mir, @TallTed, @Wind4Greg)
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33 (3 comments by @amir-hameed-mir, @Wind4Greg)
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17 (2 comments by @amir-hameed-mir, @Wind4Greg)
-
Offer: independent pure-Rust cross-validation of the Appendix A test vectors (Falcon-512 / SLH-DSA), + Falcon signature-length clarification w3c/vc-di-quantum-resistant#35 (1 comment by @Wind4Greg)
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19 (1 comment by @amir-hameed-mir)
-
-
4 pull requests opened.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37, by @Wind4Greg.
-
Add echidna action script w3c/vc-di-quantum-resistant#36, by @iherman.
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32, by @amir-hameed-mir.
-
Update FPWD with corrected short name and updated references. w3c/vc-di-quantum-resistant#30, by @Wind4Greg.
-
-
3 pull requests merged.
-
Add echidna action script w3c/vc-di-quantum-resistant#36.
-
Update FPWD with corrected short name and updated references. w3c/vc-di-quantum-resistant#30.
-
Removing errors before FPWD w3c/vc-di-quantum-resistant#29.
-
-
1 pull request closed.
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32.
-
-
4 pull requests received 14 new comments.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37 (8 comments by @davidlehn, @dlongley, @TallTed, @Wind4Greg)
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32 (4 comments by @amir-hameed-mir, @Wind4Greg)
-
w3c/vcalm-test-suite
-
1 pull request opened.
-
Adjust repo-type in w3c.json w3c/vcalm-test-suite#1, by @tidoust.
-
-
1 pull request merged.
-
Adjust repo-type in w3c.json w3c/vcalm-test-suite#1.
-
w3c/vc-data-model
-
1 issue opened.
-
Normative text on VP-within-VP w3c/vc-data-model#1633, by @rmlearney-digicatapult.
-
-
3 issues received 3 new comments.
w3c/vc-barcodes
-
1 issue opened.
-
"Secure barcodes" w3c/vc-barcodes#58, by @philarcher.
-
-
2 issues closed.
-
Broken links in Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#54.
-
4 issues received 6 new comments.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @msporny)
-
2 pull requests merged.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57.
-
Fix CBOR-LD algorithm links. w3c/vc-barcodes#56.
-
-
3 pull requests received 3 new comments.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57 (1 comment by @wes-smith)
-
w3c/vc-confidence-method
-
1 issue opened.
-
Another possible biometric example. w3c/vc-confidence-method#39, by @ewoogit.
-
-
1 issue received 3 new comments.
-
Isn't example 1 incomplete? w3c/vc-confidence-method#32 (3 comments by @dlongley, @iherman, @jandrieu)
-
-
1 pull request merged.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38.
-
-
1 pull request received 7 new comments.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38 (7 comments by @iherman, @jandrieu, @msporny, @TallTed, @wip-abramson)
-
w3c/vc-render-method
-
2 pull requests received 9 new comments.
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (7 comments by @TallTed)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (2 comments by @BigBlueHat, @ottonomy)
-
w3c/vc-use-cases
-
3 issues closed.
-
Add user task 'Trust claim' w3c/vc-use-cases#95.
-
New user/issuer task - Offer Claim w3c/vc-use-cases#138.
-
Do we need distinct use-cases for verification and validation? w3c/vc-use-cases#125.
-
-
8 issues received 8 new comments.
-
Replace "claim" with "credential" in user task diagram w3c/vc-use-cases#153 (1 comment by @KDean-Dolphin)
-
Do we need distinct use-cases for verification and validation? w3c/vc-use-cases#125 (1 comment by @KDean-Dolphin)
w3c/vc-data-model-2.0-test-suite
-
3 pull requests opened.
-
chore: bump dependency floors to latest minors w3c/vc-data-model-2.0-test-suite#172, by @djscruggs.
-
Add CODEOWNERS with initial owners. w3c/vc-data-model-2.0-test-suite#171, by @BigBlueHat.
-
Override uuid to ^11.1.1 to clear npm audit findings w3c/vc-data-model-2.0-test-suite#170, by @djscruggs.
-
-
1 pull request closed.
-
chore: bump dependency floors to latest minors w3c/vc-data-model-2.0-test-suite#172.
-
-
3 pull requests received 7 new comments.
-
Override uuid to ^11.1.1 to clear npm audit findings w3c/vc-data-model-2.0-test-suite#170 (4 comments by @BigBlueHat, @davidlehn, @djscruggs)
-
chore: bump dependency floors to latest minors w3c/vc-data-model-2.0-test-suite#172 (2 comments by @davidlehn, @djscruggs)
-
w3c/cid
-
1 issue received 1 new comment.
VC API for Lifecycle Management
Past meetings
-
3 meetings of the VC API for Lifecycle Management.
GitHub
w3c/vcalm
-
9 issues opened in the VC API for Lifecycle Management.
-
Simplify OAS file for Presentations/Credentials w3c/vcalm#653, by @PatStLouis.
-
Remote credential renderer use case w3c/vcalm#648, by @kezike.
-
Refine credential lifecycle diagram w3c/vcalm#647, by @kezike.
-
Refine all diagrams in the spec w3c/vcalm#646, by @kezike.
-
Address all oustanding issues in the spec text w3c/vcalm#645, by @kezike.
-
Define zcap actions w3c/vcalm#644, by @kezike.
-
Add detail to OAuth 2.0 scopes w3c/vcalm#643, by @kezike.
-
6 issues closed in the VC API for Lifecycle Management.
-
Address all oustanding issues in the spec text w3c/vcalm#645.
-
Refine all diagrams in the spec w3c/vcalm#646.
-
Fix URLs in the spec w3c/vcalm#640.
-
15 issues in the VC API for Lifecycle Management received 25 new comments.
-
Allow multiple presentations to be sent in a response via an array value for `verifiablePresentation` w3c/vcalm#649 (4 comments by @dlongley, @kezike)
-
Align examples and schemas with VC Data Model 2.0 (context + validFrom/validUntil) w3c/vcalm#635 (1 comment by @kezike)
-
Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage w3c/vcalm#629 (1 comment by @kezike)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (1 comment by @kezike)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @kezike)
-
-
6 pull requests opened in the VC API for Lifecycle Management.
-
Define valid ZCAP actions w3c/vcalm#657, by @kezike.
-
Add detail to OAuth 2.0 scope requiremements w3c/vcalm#656, by @kezike.
-
Adding VCALM Threat Model w3c/vcalm#655, by @eric-schuh.
-
Fix broken URL standard reference w3c/vcalm#652, by @kezike.
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651, by @kezike.
-
Update name for Recognized Entities spec w3c/vcalm#650, by @kezike.
-
-
5 pull requests merged in the VC API for Lifecycle Management.
-
Update name for Recognized Entities spec w3c/vcalm#650.
-
Fix broken URL standard reference w3c/vcalm#652.
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641.
-
8 pull requests in the VC API for Lifecycle Management received 108 new comments.
-
Adding VCALM Threat Model w3c/vcalm#655 (90 comments by @dlongley, @eric-schuh, @iherman, @jandrieu, @kezike, @msporny, @TallTed)
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641 (3 comments by @bparth24, @kezike, @TallTed)
-
Clarify when to use `acceptedEnvelopes` and `acceptedCryptosuites` w3c/vcalm#651 (2 comments by @kezike)
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636 (1 comment by @PatStLouis)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @TallTed)
-
w3c/vcalm-test-suite
-
1 pull request opened in the VC API for Lifecycle Management.
-
Adjust repo-type in w3c.json w3c/vcalm-test-suite#1, by @tidoust.
-
-
1 pull request merged in the VC API for Lifecycle Management.
-
Adjust repo-type in w3c.json w3c/vcalm-test-suite#1.
-
VC Recognized Entities
Past meetings
-
3 meetings of the VC Recognized Entities.
Participants
-
2 participants joined the VC Recognized Entities.
-
Todd Snyder joined.
-
Paul Dietrich joined.
-
GitHub
w3c/vc-recognized-entities
-
8 issues opened in the VC Recognized Entities.
-
Deprecate/remove `use-cases.html` replace with inline use cases section. w3c/vc-recognized-entities#91, by @BigBlueHat.
-
validation rules for chained credentials w3c/vc-recognized-entities#90, by @onthebreeze.
-
Discovery model for recognised entity VCs w3c/vc-recognized-entities#89, by @onthebreeze.
-
Threat Model: diagram color contrasts need tweak w3c/vc-recognized-entities#88, by @TallTed.
-
Threat Model: diagram box type cues w3c/vc-recognized-entities#87, by @TallTed.
-
(Editorial) Emphasize the "VC application" aspect of the spec w3c/vc-recognized-entities#86, by @iherman.
-
Rethinking verifying recognition chains w3c/vc-recognized-entities#85, by @KDean-Dolphin.
-
Reorder forward references w3c/vc-recognized-entities#84, by @KDean-Dolphin.
-
-
4 issues in the VC Recognized Entities received 4 new comments.
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63 (1 comment by @BigBlueHat)
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66 (1 comment by @BigBlueHat)
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73 (1 comment by @iherman)
-
-
1 pull request opened in the VC Recognized Entities.
-
Update threat model based on VCWG F2F feedback w3c/vc-recognized-entities#83, by @msporny.
-
-
1 pull request merged in the VC Recognized Entities.
-
Update threat model based on VCWG F2F feedback w3c/vc-recognized-entities#83.
-
-
1 pull request in the VC Recognized Entities received 8 new comments.
VC Barcodes and Data Integrity
Past meetings
-
3 meetings of the VC Barcodes and Data Integrity.
GitHub
w3c/vc-data-integrity
-
2 issues opened in the VC Barcodes and Data Integrity.
-
Potential internal contradiction around verificationMethod w3c/vc-data-integrity#349, by @rmlearney-digicatapult.
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348, by @Wind4Greg.
-
-
1 issue in the VC Barcodes and Data Integrity received 3 new comments.
-
Move Common Algorthms from vc-di-quantum-resistant to vc-data-integrity and update vc-di-ecdsa and vc-di-eddsa w3c/vc-data-integrity#348 (3 comments by @dlongley, @Wind4Greg)
-
w3c/vc-forgery-defense
-
3 pull requests opened in the VC Barcodes and Data Integrity.
-
Added echidna script w3c/vc-forgery-defense#3, by @iherman.
-
Prepare document for FPWD. w3c/vc-forgery-defense#2, by @wes-smith.
-
Add initial specification text. w3c/vc-forgery-defense#1, by @wes-smith.
-
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Prepare document for FPWD. w3c/vc-forgery-defense#2.
-
Add initial specification text. w3c/vc-forgery-defense#1.
-
-
1 pull request in the VC Barcodes and Data Integrity received 1 new comment.
w3c/vc-di-quantum-resistant
-
5 issues opened in the VC Barcodes and Data Integrity.
-
Remove internal use of Cipher/Cypher wording w3c/vc-di-quantum-resistant#38, by @Wind4Greg.
-
Strengthen Section 4.1 — ML-DSA BUFF security properties need mechanistic rationale, implementation boundary, and updated citations w3c/vc-di-quantum-resistant#34, by @amir-hameed-mir.
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33, by @amir-hameed-mir.
-
Add `mldsa65-jcs-2024` Cryptosuite w3c/vc-di-quantum-resistant#31, by @amir-hameed-mir.
-
-
1 issue closed in the VC Barcodes and Data Integrity.
-
Support for Selective Disclosure w3c/vc-di-quantum-resistant#22.
-
-
6 issues in the VC Barcodes and Data Integrity received 25 new comments.
-
Add `mldsa65-jcs-2024` Cryptosuite w3c/vc-di-quantum-resistant#31 (13 comments by @amir-hameed-mir, @msporny, @Wind4Greg)
-
Strengthen Section 4.1 — ML-DSA BUFF security properties need mechanistic rationale, implementation boundary, and updated citations w3c/vc-di-quantum-resistant#34 (5 comments by @amir-hameed-mir, @TallTed, @Wind4Greg)
-
ML-DSA-44 Test Vector Successfully Verified — @context Injection Required for proofConfig w3c/vc-di-quantum-resistant#33 (3 comments by @amir-hameed-mir, @Wind4Greg)
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17 (2 comments by @amir-hameed-mir, @Wind4Greg)
-
Offer: independent pure-Rust cross-validation of the Appendix A test vectors (Falcon-512 / SLH-DSA), + Falcon signature-length clarification w3c/vc-di-quantum-resistant#35 (1 comment by @Wind4Greg)
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19 (1 comment by @amir-hameed-mir)
-
-
4 pull requests opened in the VC Barcodes and Data Integrity.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37, by @Wind4Greg.
-
Add echidna action script w3c/vc-di-quantum-resistant#36, by @iherman.
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32, by @amir-hameed-mir.
-
Update FPWD with corrected short name and updated references. w3c/vc-di-quantum-resistant#30, by @Wind4Greg.
-
-
3 pull requests merged in the VC Barcodes and Data Integrity.
-
Add echidna action script w3c/vc-di-quantum-resistant#36.
-
Update FPWD with corrected short name and updated references. w3c/vc-di-quantum-resistant#30.
-
Removing errors before FPWD w3c/vc-di-quantum-resistant#29.
-
-
1 pull request closed in the VC Barcodes and Data Integrity.
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32.
-
-
4 pull requests in the VC Barcodes and Data Integrity received 14 new comments.
-
Add table and text for secretKeyMultibase information w3c/vc-di-quantum-resistant#37 (8 comments by @davidlehn, @dlongley, @TallTed, @Wind4Greg)
-
added mldsa65-test-vectors w3c/vc-di-quantum-resistant#32 (4 comments by @amir-hameed-mir, @Wind4Greg)
-
w3c/vc-barcodes
-
1 issue opened in the VC Barcodes and Data Integrity.
-
"Secure barcodes" w3c/vc-barcodes#58, by @philarcher.
-
-
2 issues closed in the VC Barcodes and Data Integrity.
-
Broken links in Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#54.
-
4 issues in the VC Barcodes and Data Integrity received 6 new comments.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @msporny)
-
2 pull requests merged in the VC Barcodes and Data Integrity.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57.
-
Fix CBOR-LD algorithm links. w3c/vc-barcodes#56.
-
-
3 pull requests in the VC Barcodes and Data Integrity received 3 new comments.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57 (1 comment by @wes-smith)
-
VC Confidence Method
Participants
-
2 participants joined the VC Confidence Method.
-
Amir Hameed Mir joined.
-
Scott Jones joined.
-
GitHub
w3c/vc-confidence-method
-
1 issue opened in the VC Confidence Method.
-
Another possible biometric example. w3c/vc-confidence-method#39, by @ewoogit.
-
-
1 issue in the VC Confidence Method received 3 new comments.
-
Isn't example 1 incomplete? w3c/vc-confidence-method#32 (3 comments by @dlongley, @iherman, @jandrieu)
-
-
1 pull request merged in the VC Confidence Method.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38.
-
-
1 pull request in the VC Confidence Method received 7 new comments.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38 (7 comments by @iherman, @jandrieu, @msporny, @TallTed, @wip-abramson)
-
VC DPP & Business Wallet
Participants
-
3 participants joined the VC DPP & Business Wallet.
-
Tony Choi joined.
-
Marc-Andree Wolf joined.
-
Michael Shea joined.
-
VC Render Method
GitHub
w3c/vc-render-method
-
2 pull requests in the VC Render Method received 9 new comments.
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (7 comments by @TallTed)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (2 comments by @BigBlueHat, @ottonomy)
-
TR publications
-
7 documents published.
-
VCALM v1.0 published twice as a Working Draft. History of VCALM v1.0
-
Confidence Method v1.0 published as a Working Draft. History of Confidence Method v1.0
-
Verifiable Credential Barcodes v1.0 published twice as a Working Draft. History of Verifiable Credential Barcodes v1.0
-
Verifiable Credentials Data Model v2.1 published as a Working Draft. History of Verifiable Credentials Data Model v2.1
-
Recognized Entities v1.0 published as a First Public Working Draft. History of Recognized Entities v1.0
-
Past meetings
Participants
-
7 participants joined.
-
Priyanka Dubbaka (W3C Invited Experts) joined.
-
Emanuel Silva (HM Government) joined.
-
Ted Guild (W3C Invited Experts) joined.
-
Ronald Koenig (Spherity GmbH) joined.
-
Ingo Wolf (Spherity GmbH) joined.
-
Carsten Stöcker (Spherity GmbH) joined.
-
Punith Durga Prasad Arumilli (W3C Invited Experts) joined.
-
-
1 participant left.
-
Emanuel Silva (HM Government) left.
-
-
1 organization joined.
-
Spherity GmbH joined.
-
GitHub
w3c/vc-recognized-entities
-
3 issues opened.
-
Broken links in Recognized Entities v1.0 w3c/vc-recognized-entities#78, by @dontcallmedom-bot.
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77, by @TallTed.
-
Federated Identifier use case w3c/vc-recognized-entities#74, by @philarcher.
-
-
1 issue closed.
-
Change document title w3c/vc-recognized-entities#30.
-
-
3 issues received 4 new comments.
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73 (2 comments by @iherman, @msporny)
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66 (1 comment by @onthebreeze)
-
-
6 pull requests opened.
-
Add initial attempt at threat model. w3c/vc-recognized-entities#82, by @msporny.
-
add trade and conformity use cases w3c/vc-recognized-entities#81, by @onthebreeze.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80, by @onthebreeze.
-
Adding echidna workflow script w3c/vc-recognized-entities#79, by @iherman.
-
Handled a link checker issue w3c/vc-recognized-entities#76, by @iherman.
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75, by @msporny.
-
-
6 pull requests merged.
-
add trade and conformity use cases w3c/vc-recognized-entities#81.
-
Adding echidna workflow script w3c/vc-recognized-entities#79.
-
Handled a link checker issue w3c/vc-recognized-entities#76.
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65.
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75.
-
Adjust URL of live version in README w3c/vc-recognized-entities#72.
-
-
1 pull request closed.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80.
-
-
8 pull requests received 17 new comments.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80 (4 comments by @iherman, @msporny, @onthebreeze)
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75 (4 comments by @msporny, @philarcher, @TallTed)
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65 (3 comments by @BigBlueHat, @msporny)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (2 comments by @shigeya)
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61 (1 comment by @TallTed)
-
w3c/vc-confidence-method
-
1 issue opened.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37, by @msporny.
-
-
1 issue closed.
-
One confidence method on several subjects? w3c/vc-confidence-method#34.
-
-
2 issues received 5 new comments.
-
One confidence method on several subjects? w3c/vc-confidence-method#34 (4 comments by @iherman, @jandrieu)
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31 (1 comment by @ScottJeezey)
-
-
1 pull request opened.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38, by @ScottJeezey.
-
-
1 pull request merged.
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29.
-
-
2 pull requests received 44 new comments.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38 (34 comments by @amir-hameed-mir, @denkeni, @jandrieu, @msporny, @ScottJeezey, @TallTed)
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29 (10 comments by @jandrieu, @TallTed)
-
w3c/vc-data-model
-
1 issue opened.
-
Update references to confidence and render methods. w3c/vc-data-model#1632, by @iherman.
-
-
2 issues closed.
-
digestSRI example does not conform with SRI spec w3c/vc-data-model#1603.
-
Use case: post-hoc integrity attestations for user-generated content w3c/vc-data-model#1627.
-
-
3 issues received 16 new comments.
-
Deprecate `digestSRI` in v2.1 w3c/vc-data-model#1628 (13 comments by @brentzundel, @filip26, @iherman, @msporny, @shigeya)
-
Use case: post-hoc integrity attestations for user-generated content w3c/vc-data-model#1627 (2 comments by @brentzundel, @iherman)
-
-
2 pull requests opened.
-
Deprecate digest sri datatype vocab item w3c/vc-data-model#1630, by @iherman.
-
Deprecate `digestSri`. w3c/vc-data-model#1629, by @msporny.
-
-
1 pull request merged.
-
Deprecate digest sri datatype vocab item w3c/vc-data-model#1630.
-
-
1 pull request received 3 new comments.
w3c/vcalm
-
6 issues opened.
-
Add `protocols` object key table w3c/vcalm#642, by @BigBlueHat.
-
Fix URLs in the spec w3c/vcalm#640, by @bparth24.
-
Update README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#638, by @bparth24.
-
Expand error handling to workflows w3c/vcalm#637, by @PatStLouis.
-
-
1 issue closed.
-
6 issues received 16 new comments.
-
Create Threat Model for VCALM w3c/vcalm#628 (11 comments by @eric-schuh, @iherman, @kezike, @msporny)
-
Update README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#638 (1 comment by @bparth24)
-
Consider adding `<exchangeId>/request` endpoint to serve current VPR/request for DC API protocol w3c/vcalm#633 (1 comment by @dlongley)
-
-
3 pull requests opened.
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641, by @bparth24.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639, by @bparth24.
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636, by @PatStLouis.
-
-
3 pull requests merged.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639.
-
Remove outdated issue about DataIntegrityProof. w3c/vcalm#632.
-
Added echidna workflow script w3c/vcalm#630.
-
-
4 pull requests received 7 new comments.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639 (3 comments by @iherman, @kezike, @PatStLouis)
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636 (2 comments by @iherman, @PatStLouis)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @iherman)
-
w3c/vc-di-quantum-resistant
-
7 issues closed.
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9.
-
ML-DSA-44 encoding (base58 or Url64)? w3c/vc-di-quantum-resistant#8.
-
experimental-mldsa44-2024 vs mldsa-rdfc-2025 w3c/vc-di-quantum-resistant#7.
-
Modularize algorithm text to keep it DRY w3c/vc-di-quantum-resistant#6.
-
Pick and use Multikey names and prefix values w3c/vc-di-quantum-resistant#5.
-
SLH-DSA w3c/vc-di-quantum-resistant#3.
-
Register multibase values to identify ML-DSA-44 keys w3c/vc-di-quantum-resistant#2.
-
-
9 issues received 9 new comments.
-
Register multibase values to identify ML-DSA-44 keys w3c/vc-di-quantum-resistant#2 (1 comment by @Wind4Greg)
-
Pick and use Multikey names and prefix values w3c/vc-di-quantum-resistant#5 (1 comment by @Wind4Greg)
-
experimental-mldsa44-2024 vs mldsa-rdfc-2025 w3c/vc-di-quantum-resistant#7 (1 comment by @Wind4Greg)
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9 (1 comment by @Wind4Greg)
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17 (1 comment by @Wind4Greg)
-
6 pull requests opened.
-
Removing errors before FPWD w3c/vc-di-quantum-resistant#29, by @iherman.
-
Update FPWD. w3c/vc-di-quantum-resistant#28, by @Wind4Greg.
-
Fix short name and GitHub links. w3c/vc-di-quantum-resistant#27, by @Wind4Greg.
-
Creating FPWD. w3c/vc-di-quantum-resistant#26, by @Wind4Greg.
-
Selective Disclosure Test Vectors w3c/vc-di-quantum-resistant#25, by @Wind4Greg.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24, by @Wind4Greg.
-
-
5 pull requests merged.
-
Update FPWD. w3c/vc-di-quantum-resistant#28.
-
Fix short name and GitHub links. w3c/vc-di-quantum-resistant#27.
-
Creating FPWD. w3c/vc-di-quantum-resistant#26.
-
Selective Disclosure Test Vectors w3c/vc-di-quantum-resistant#25.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24.
-
-
2 pull requests received 2 new comments.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24 (1 comment by @msporny)
w3c/vc-imp-guide
-
1 issue opened.
-
1 issue received 1 new comment.
-
Deployment-pattern guidance: principal-authority pre-layer for credentials consumed by autonomous agents w3c/vc-imp-guide#75 (1 comment by @chopmob-cloud)
-
w3c/cid
-
1 issue opened.
-
Add "CID" as definition for XREF w3c/cid#170, by @jandrieu.
-
-
3 issues received 4 new comments.
-
1 pull request opened.
-
Add CID alias for controlled identifier document term w3c/cid#171, by @jandrieu.
-
-
1 pull request received 2 new comments.
w3c/vc-di-eddsa-test-suite
-
1 pull request opened.
-
Use vc2 credential in issue/verify rdfc tests w3c/vc-di-eddsa-test-suite#69, by @PatStLouis.
-
w3c/vc-render-method
-
1 issue opened.
-
Discuss PDF rendering expectations. w3c/vc-render-method#53, by @BigBlueHat.
-
-
1 issue received 1 new comment.
-
2 pull requests merged.
-
Add outputPreference terms section. w3c/vc-render-method#51.
-
Add info about Oblivious HTTP. w3c/vc-render-method#48.
-
-
5 pull requests received 15 new comments.
-
Add outputPreference terms section. w3c/vc-render-method#51 (8 comments by @BigBlueHat, @iherman, @msporny, @TallTed)
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49 (3 comments by @BigBlueHat, @iherman, @msporny)
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (2 comments by @iherman, @PatStLouis)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (1 comment by @iherman)
-
w3c/vc-data-model-2.0-test-suite
-
1 issue opened.
-
relatedResource fixture hashes are stale after Feb 2025 context update w3c/vc-data-model-2.0-test-suite#166, by @PatStLouis.
-
-
1 issue closed.
-
relatedResource fixture hashes are stale after Feb 2025 context update w3c/vc-data-model-2.0-test-suite#166.
-
-
1 issue received 1 new comment.
-
3 pull requests opened.
-
feat: accept credential or verifiableCredential in issue responses w3c/vc-data-model-2.0-test-suite#169, by @PatStLouis.
-
fix: refresh relatedResource digests for credentials/v2 context w3c/vc-data-model-2.0-test-suite#168, by @PatStLouis.
-
chore: update deps for Node 20 and resolve npm audit findings w3c/vc-data-model-2.0-test-suite#167, by @PatStLouis.
-
-
3 pull requests merged.
-
chore: update deps for Node 20 and resolve npm audit findings w3c/vc-data-model-2.0-test-suite#167.
-
feat: accept credential or verifiableCredential in issue responses w3c/vc-data-model-2.0-test-suite#169.
-
fix: refresh relatedResource digests for credentials/v2 context w3c/vc-data-model-2.0-test-suite#168.
-
-
1 pull request closed.
-
Update digest and vc api w3c/vc-data-model-2.0-test-suite#161.
-
-
4 pull requests received 7 new comments.
-
chore: update deps for Node 20 and resolve npm audit findings w3c/vc-data-model-2.0-test-suite#167 (3 comments by @dlongley, @PatStLouis)
-
Update digest and vc api w3c/vc-data-model-2.0-test-suite#161 (2 comments by @lemoustachiste, @PatStLouis)
-
feat: accept credential or verifiableCredential in issue responses w3c/vc-data-model-2.0-test-suite#169 (1 comment by @PatStLouis)
-
fix: refresh relatedResource digests for credentials/v2 context w3c/vc-data-model-2.0-test-suite#168 (1 comment by @PatStLouis)
-
w3c/vc-barcodes
-
3 issues opened.
-
Broken links in Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#54, by @dontcallmedom-bot.
-
Location of VCB in PDF417 w3c/vc-barcodes#53, by @wes-smith.
-
3 issues closed.
-
"Original" barcode? (Section §2.1) w3c/vc-barcodes#38.
-
Allow multibase encoding for driver's license VCBs. w3c/vc-barcodes#20.
-
Update verification examples in test vectors section to use modern CBOR-LD tag. w3c/vc-barcodes#25.
-
-
4 issues received 5 new comments.
-
Allow PDF417 barcode types beyond AAMVA Driver's License w3c/vc-barcodes#22 (2 comments by @iherman, @wes-smith)
-
Example 8 in §6.1.1.1: `canonicalizedData` is missing the `F` prefix on the license number (`DAQ`) field w3c/vc-barcodes#55 (1 comment by @wes-smith)
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @wes-smith)
-
Outdated `TerseBitstringStatusListEntry` to `BitstringStatusListEntry` conversion w3c/vc-barcodes#19 (1 comment by @TallTed)
-
-
4 pull requests opened.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57, by @wes-smith.
-
Fix CBOR-LD algorithm links. w3c/vc-barcodes#56, by @wes-smith.
-
Update introductory examples. w3c/vc-barcodes#52, by @wes-smith.
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51, by @wes-smith.
-
-
3 pull requests merged.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44.
-
Add discussion of multibase header in PDF417 VCBs. w3c/vc-barcodes#50.
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51.
-
-
1 pull request closed.
-
Update verification examples. w3c/vc-barcodes#48.
-
-
4 pull requests received 78 new comments.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44 (72 comments by @dlongley, @TallTed, @wes-smith)
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51 (3 comments by @iherman, @wes-smith)
-
w3c/vc-dpp-bw
-
1 issue opened.
-
UCR and VC-s in general w3c/vc-dpp-bw#5, by @iherman.
-
-
6 pull requests opened.
-
ucr_webuild w3c/vc-dpp-bw#7, by @ngwlf.
-
- switched the use case about trusted fashion imagery for a Digital C… w3c/vc-dpp-bw#6, by @ngwlf.
-
Remove Ivan from the editors' list. w3c/vc-dpp-bw#4, by @iherman.
-
Ucr webuild w3c/vc-dpp-bw#3, by @ngwlf.
-
Ucr webuild w3c/vc-dpp-bw#2, by @ngwlf.
-
ucr_webuild w3c/vc-dpp-bw#1, by @ngwlf.
-
-
6 pull requests merged.
-
ucr_webuild w3c/vc-dpp-bw#7.
-
Remove Ivan from the editors' list. w3c/vc-dpp-bw#4.
-
Ucr webuild w3c/vc-dpp-bw#3.
-
Ucr webuild w3c/vc-dpp-bw#2.
-
ucr_webuild w3c/vc-dpp-bw#1.
-
-
2 pull requests received 3 new comments.
w3c/vc-wg
-
1 issue received 4 new comments.
-
1 pull request opened.
-
Current overview of Vocabularies and Contexts w3c/vc-wg#13, by @iherman.
-
-
1 pull request merged.
-
Current overview of Vocabularies and Contexts w3c/vc-wg#13.
-
-
1 pull request received 22 new comments.
-
Current overview of Vocabularies and Contexts w3c/vc-wg#13 (22 comments by @dlongley, @iherman, @msporny, @TallTed)
-
w3c/vc-data-integrity
-
1 issue closed.
-
Latest published version is 404. w3c/vc-data-integrity#345.
-
-
3 issues received 4 new comments.
-
Cryptographic primitives supported by current smart phones w3c/vc-data-integrity#340 (2 comments by @iherman, @msporny)
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @iherman)
-
VC Recognized Entities
Past meetings
Participants
-
1 participant joined the VC Recognized Entities.
-
Sin Yong Loh joined.
-
GitHub
w3c/vc-recognized-entities
-
3 issues opened in the VC Recognized Entities.
-
Broken links in Recognized Entities v1.0 w3c/vc-recognized-entities#78, by @dontcallmedom-bot.
-
broken English in `Issuer Impersonation` section w3c/vc-recognized-entities#77, by @TallTed.
-
Federated Identifier use case w3c/vc-recognized-entities#74, by @philarcher.
-
-
1 issue closed in the VC Recognized Entities.
-
Change document title w3c/vc-recognized-entities#30.
-
-
3 issues in the VC Recognized Entities received 4 new comments.
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73 (2 comments by @iherman, @msporny)
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66 (1 comment by @onthebreeze)
-
-
6 pull requests opened in the VC Recognized Entities.
-
Add initial attempt at threat model. w3c/vc-recognized-entities#82, by @msporny.
-
add trade and conformity use cases w3c/vc-recognized-entities#81, by @onthebreeze.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80, by @onthebreeze.
-
Adding echidna workflow script w3c/vc-recognized-entities#79, by @iherman.
-
Handled a link checker issue w3c/vc-recognized-entities#76, by @iherman.
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75, by @msporny.
-
-
6 pull requests merged in the VC Recognized Entities.
-
add trade and conformity use cases w3c/vc-recognized-entities#81.
-
Adding echidna workflow script w3c/vc-recognized-entities#79.
-
Handled a link checker issue w3c/vc-recognized-entities#76.
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65.
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75.
-
Adjust URL of live version in README w3c/vc-recognized-entities#72.
-
-
1 pull request closed in the VC Recognized Entities.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80.
-
-
8 pull requests in the VC Recognized Entities received 17 new comments.
-
Add discoverable chain pattern and cross-border trade use cases w3c/vc-recognized-entities#80 (4 comments by @iherman, @msporny, @onthebreeze)
-
Rename to "recognized entity credential" w3c/vc-recognized-entities#75 (4 comments by @msporny, @philarcher, @TallTed)
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65 (3 comments by @BigBlueHat, @msporny)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (2 comments by @shigeya)
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61 (1 comment by @TallTed)
-
VC Confidence Method
Participants
-
2 participants joined the VC Confidence Method.
-
Sin Yong Loh joined.
-
Will Abramson joined.
-
GitHub
w3c/vc-confidence-method
-
1 issue opened in the VC Confidence Method.
-
Add DID-based verification method approaches to the spec w3c/vc-confidence-method#37, by @msporny.
-
-
1 issue closed in the VC Confidence Method.
-
One confidence method on several subjects? w3c/vc-confidence-method#34.
-
-
2 issues in the VC Confidence Method received 5 new comments.
-
One confidence method on several subjects? w3c/vc-confidence-method#34 (4 comments by @iherman, @jandrieu)
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31 (1 comment by @ScottJeezey)
-
-
1 pull request opened in the VC Confidence Method.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38, by @ScottJeezey.
-
-
1 pull request merged in the VC Confidence Method.
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29.
-
-
2 pull requests in the VC Confidence Method received 44 new comments.
-
Add BiometricVectorConfidenceMethod to Data Model w3c/vc-confidence-method#38 (34 comments by @amir-hameed-mir, @denkeni, @jandrieu, @msporny, @ScottJeezey, @TallTed)
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29 (10 comments by @jandrieu, @TallTed)
-
VC API for Lifecycle Management
Past meetings
-
4 meetings of the VC API for Lifecycle Management.
Participants
-
1 participant joined the VC API for Lifecycle Management.
-
Olvis Enrique Gil Ríos joined.
-
GitHub
w3c/vcalm
-
6 issues opened in the VC API for Lifecycle Management.
-
Add `protocols` object key table w3c/vcalm#642, by @BigBlueHat.
-
Fix URLs in the spec w3c/vcalm#640, by @bparth24.
-
Update README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#638, by @bparth24.
-
Expand error handling to workflows w3c/vcalm#637, by @PatStLouis.
-
-
1 issue closed in the VC API for Lifecycle Management.
-
6 issues in the VC API for Lifecycle Management received 16 new comments.
-
Create Threat Model for VCALM w3c/vcalm#628 (11 comments by @eric-schuh, @iherman, @kezike, @msporny)
-
Update README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#638 (1 comment by @bparth24)
-
Consider adding `<exchangeId>/request` endpoint to serve current VPR/request for DC API protocol w3c/vcalm#633 (1 comment by @dlongley)
-
-
3 pull requests opened in the VC API for Lifecycle Management.
-
Fix URLs - from w3c-ccg to w3c; vc-api to vcalm; w3c/vcalm#641, by @bparth24.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639, by @bparth24.
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636, by @PatStLouis.
-
-
3 pull requests merged in the VC API for Lifecycle Management.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639.
-
Remove outdated issue about DataIntegrityProof. w3c/vcalm#632.
-
Added echidna workflow script w3c/vcalm#630.
-
-
4 pull requests in the VC API for Lifecycle Management received 7 new comments.
-
Fix README.md URLs from w3c-ccg.github.io to w3c.github.io w3c/vcalm#639 (3 comments by @iherman, @kezike, @PatStLouis)
-
Align with VC Data Model 2.0 (context URLs + validFrom/validUntil) w3c/vcalm#636 (2 comments by @iherman, @PatStLouis)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @iherman)
-
VC Barcodes and Data Integrity
Past meetings
-
4 meetings of the VC Barcodes and Data Integrity.
Participants
-
1 participant joined the VC Barcodes and Data Integrity.
-
Will Abramson joined.
-
GitHub
w3c/vc-di-quantum-resistant
-
7 issues closed in the VC Barcodes and Data Integrity.
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9.
-
ML-DSA-44 encoding (base58 or Url64)? w3c/vc-di-quantum-resistant#8.
-
experimental-mldsa44-2024 vs mldsa-rdfc-2025 w3c/vc-di-quantum-resistant#7.
-
Modularize algorithm text to keep it DRY w3c/vc-di-quantum-resistant#6.
-
Pick and use Multikey names and prefix values w3c/vc-di-quantum-resistant#5.
-
SLH-DSA w3c/vc-di-quantum-resistant#3.
-
Register multibase values to identify ML-DSA-44 keys w3c/vc-di-quantum-resistant#2.
-
-
9 issues in the VC Barcodes and Data Integrity received 9 new comments.
-
Register multibase values to identify ML-DSA-44 keys w3c/vc-di-quantum-resistant#2 (1 comment by @Wind4Greg)
-
Pick and use Multikey names and prefix values w3c/vc-di-quantum-resistant#5 (1 comment by @Wind4Greg)
-
experimental-mldsa44-2024 vs mldsa-rdfc-2025 w3c/vc-di-quantum-resistant#7 (1 comment by @Wind4Greg)
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9 (1 comment by @Wind4Greg)
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17 (1 comment by @Wind4Greg)
-
6 pull requests opened in the VC Barcodes and Data Integrity.
-
Removing errors before FPWD w3c/vc-di-quantum-resistant#29, by @iherman.
-
Update FPWD. w3c/vc-di-quantum-resistant#28, by @Wind4Greg.
-
Fix short name and GitHub links. w3c/vc-di-quantum-resistant#27, by @Wind4Greg.
-
Creating FPWD. w3c/vc-di-quantum-resistant#26, by @Wind4Greg.
-
Selective Disclosure Test Vectors w3c/vc-di-quantum-resistant#25, by @Wind4Greg.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24, by @Wind4Greg.
-
-
5 pull requests merged in the VC Barcodes and Data Integrity.
-
Update FPWD. w3c/vc-di-quantum-resistant#28.
-
Fix short name and GitHub links. w3c/vc-di-quantum-resistant#27.
-
Creating FPWD. w3c/vc-di-quantum-resistant#26.
-
Selective Disclosure Test Vectors w3c/vc-di-quantum-resistant#25.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24.
-
-
2 pull requests in the VC Barcodes and Data Integrity received 2 new comments.
-
Support for Efficient PQC Selective disclosure w3c/vc-di-quantum-resistant#24 (1 comment by @msporny)
w3c/vc-barcodes
-
3 issues opened in the VC Barcodes and Data Integrity.
-
Broken links in Verifiable Credential Barcodes v1.0 w3c/vc-barcodes#54, by @dontcallmedom-bot.
-
Location of VCB in PDF417 w3c/vc-barcodes#53, by @wes-smith.
-
3 issues closed in the VC Barcodes and Data Integrity.
-
"Original" barcode? (Section §2.1) w3c/vc-barcodes#38.
-
Allow multibase encoding for driver's license VCBs. w3c/vc-barcodes#20.
-
Update verification examples in test vectors section to use modern CBOR-LD tag. w3c/vc-barcodes#25.
-
-
4 issues in the VC Barcodes and Data Integrity received 5 new comments.
-
Allow PDF417 barcode types beyond AAMVA Driver's License w3c/vc-barcodes#22 (2 comments by @iherman, @wes-smith)
-
Example 8 in §6.1.1.1: `canonicalizedData` is missing the `F` prefix on the license number (`DAQ`) field w3c/vc-barcodes#55 (1 comment by @wes-smith)
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33 (1 comment by @wes-smith)
-
Outdated `TerseBitstringStatusListEntry` to `BitstringStatusListEntry` conversion w3c/vc-barcodes#19 (1 comment by @TallTed)
-
-
4 pull requests opened in the VC Barcodes and Data Integrity.
-
Add missing character to test vector canonicalized data string. w3c/vc-barcodes#57, by @wes-smith.
-
Fix CBOR-LD algorithm links. w3c/vc-barcodes#56, by @wes-smith.
-
Update introductory examples. w3c/vc-barcodes#52, by @wes-smith.
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51, by @wes-smith.
-
-
3 pull requests merged in the VC Barcodes and Data Integrity.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44.
-
Add discussion of multibase header in PDF417 VCBs. w3c/vc-barcodes#50.
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51.
-
-
1 pull request closed in the VC Barcodes and Data Integrity.
-
Update verification examples. w3c/vc-barcodes#48.
-
-
4 pull requests in the VC Barcodes and Data Integrity received 78 new comments.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44 (72 comments by @dlongley, @TallTed, @wes-smith)
-
Update CBOR tag in verification test vectors. w3c/vc-barcodes#51 (3 comments by @iherman, @wes-smith)
-
w3c/vc-data-integrity
-
1 issue closed in the VC Barcodes and Data Integrity.
-
Latest published version is 404. w3c/vc-data-integrity#345.
-
-
3 issues in the VC Barcodes and Data Integrity received 4 new comments.
-
Cryptographic primitives supported by current smart phones w3c/vc-data-integrity#340 (2 comments by @iherman, @msporny)
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @iherman)
-
VC Render Method
GitHub
w3c/vc-render-method
-
1 issue opened in the VC Render Method.
-
Discuss PDF rendering expectations. w3c/vc-render-method#53, by @BigBlueHat.
-
-
1 issue in the VC Render Method received 1 new comment.
-
2 pull requests merged in the VC Render Method.
-
Add outputPreference terms section. w3c/vc-render-method#51.
-
Add info about Oblivious HTTP. w3c/vc-render-method#48.
-
-
5 pull requests in the VC Render Method received 15 new comments.
-
Add outputPreference terms section. w3c/vc-render-method#51 (8 comments by @BigBlueHat, @iherman, @msporny, @TallTed)
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49 (3 comments by @BigBlueHat, @iherman, @msporny)
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (2 comments by @iherman, @PatStLouis)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (1 comment by @iherman)
-
VC DPP & Business Wallet
Participants
-
1 chair appointed in the VC DPP & Business Wallet.
-
Carsten Stöcker became a chair.
-
-
5 participants joined the VC DPP & Business Wallet.
-
Phillip Long joined.
-
Ted Guild joined.
-
Ronald Koenig joined.
-
Ingo Wolf joined.
-
Carsten Stöcker joined.
-
GitHub
w3c/vc-dpp-bw
-
1 issue opened in the VC DPP & Business Wallet.
-
UCR and VC-s in general w3c/vc-dpp-bw#5, by @iherman.
-
-
6 pull requests opened in the VC DPP & Business Wallet.
-
ucr_webuild w3c/vc-dpp-bw#7, by @ngwlf.
-
- switched the use case about trusted fashion imagery for a Digital C… w3c/vc-dpp-bw#6, by @ngwlf.
-
Remove Ivan from the editors' list. w3c/vc-dpp-bw#4, by @iherman.
-
Ucr webuild w3c/vc-dpp-bw#3, by @ngwlf.
-
Ucr webuild w3c/vc-dpp-bw#2, by @ngwlf.
-
ucr_webuild w3c/vc-dpp-bw#1, by @ngwlf.
-
-
6 pull requests merged in the VC DPP & Business Wallet.
-
ucr_webuild w3c/vc-dpp-bw#7.
-
Remove Ivan from the editors' list. w3c/vc-dpp-bw#4.
-
Ucr webuild w3c/vc-dpp-bw#3.
-
Ucr webuild w3c/vc-dpp-bw#2.
-
ucr_webuild w3c/vc-dpp-bw#1.
-
-
2 pull requests in the VC DPP & Business Wallet received 3 new comments.
TR publications
-
11 documents published.
-
Data Integrity BBS Cryptosuites v1.0 published as a Candidate Recommendation Draft. History of Data Integrity BBS Cryptosuites v1.0
-
Verifiable Credentials Data Model v2.1 published as a Working Draft. History of Verifiable Credentials Data Model v2.1
-
Verifiable Credential Barcodes v1.0 published as a Working Draft. History of Verifiable Credential Barcodes v1.0
-
Verifiable Credential Rendering Methods v1.0 published as a Working Draft. History of Verifiable Credential Rendering Methods v1.0
-
Confidence Method v1.0 published as a Working Draft. History of Confidence Method v1.0
-
Data Integrity ECDSA Cryptosuites v1.1 published as a First Public Working Draft. History of Data Integrity ECDSA Cryptosuites v1.1
-
Data Integrity EdDSA Cryptosuites v1.1 published as a First Public Working Draft. History of Data Integrity EdDSA Cryptosuites v1.1
-
VCALM v1.0 published as a First Public Working Draft. History of VCALM v1.0
-
Verifiable Credential Barcodes v1.0 published as a First Public Working Draft. History of Verifiable Credential Barcodes v1.0
-
Verifiable Credential Data Integrity 1.1 published as a First Public Working Draft. History of Verifiable Credential Data Integrity 1.1
-
Verifiable Credentials Data Model v2.1 published as a First Public Working Draft. History of Verifiable Credentials Data Model v2.1
-
Past meetings
Participants
-
20 participants joined.
-
Klaeri Schelhowe (GS1) joined.
-
Johan de Swardt (Entersekt) joined.
-
Gerhard Oosthuizen (Entersekt) joined.
-
Wonsuk Lee (Electronics and Telecommunications Research Institute (ETRI)) joined.
-
Nate Otto (Skybridge Skills) joined.
-
Olvis Enrique Gil Ríos (W3C Invited Experts) joined.
-
Carolynn Bernier (W3C Invited Experts) joined.
-
Robert David (Graphwise) joined.
-
Wajih Rehman (W3C Invited Experts) joined.
-
Ivo Ladenius (GS1) joined.
-
Jiwoong YOO (Sharing Economy Association of Korea (SEAK)) joined.
-
Geunhyung Kim (Sharing Economy Association of Korea (SEAK)) joined.
-
Jon St John (Anonyome Labs, Inc.) joined.
-
John Mumford (Anonyome Labs, Inc.) joined.
-
Rebecca Christman (Anonyome Labs, Inc.) joined.
-
Bianca Arocho (Anonyome Labs, Inc.) joined.
-
Sin Yong Loh (W3C Invited Experts) joined.
-
Elnar Hajiyev (W3C Invited Experts) joined.
-
Pierre-Antoine Champin (W3C) joined.
-
Scott Jones (W3C Invited Experts) joined.
-
-
61 participants left.
-
Jonathan Prisby (Department of Homeland Security) left.
-
Christine Runnegar (W3C Invited Experts) left.
-
Ugur Acar (Depixen) left.
-
Isaiah Inuwa (Bitwarden) left.
-
Siddhartha Pandey (Microsoft Corporation) left.
-
Ruoxi Ran (W3C) left.
-
ChangYun LEE (CREATIVECODE) left.
-
Daehyun Kim (CREATIVECODE) left.
-
Hyeri Kim (CREATIVECODE) left.
-
Adam Bradley (Mastercard Incorporated) left.
-
Junichi Yoshii (Kodansha, Publishers, Ltd.) left.
-
Savita Farooqui (W3C Invited Experts) left.
-
Wonsuk Lee (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Joshua Thomas (Ignite Retail Technology) left.
-
Zane Durkin (Ignite Retail Technology) left.
-
Brian McManus (Ignite Retail Technology) left.
-
Carl Prosack (Department of Homeland Security) left.
-
Hu Liu (Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司）) left.
-
Dan Stewart (Autodesk) left.
-
Won Choe (Department of Homeland Security) left.
-
Vincent Annunziato (Department of Homeland Security) left.
-
Waheed Ashraf (INSIGHT - The Centre for Data Analytics) left.
-
Johan de Swardt (Entersekt) left.
-
Sebastian Crane (W3C Invited Experts) left.
-
Hyojin Song (LG Electronics) left.
-
Bruno Vavala (W3C Invited Experts) left.
-
stephan baur (Kaiser Permanente) left.
-
zhilei zhang (360) left.
-
Luis Meijueiro (Fundacion CTIC) left.
-
Pablo COCA (Fundacion CTIC) left.
-
Brian Campbell (Ping Identity) left.
-
Brian Richter (W3C Invited Experts) left.
-
Sten Reijers (Ver.iD) left.
-
Cosma Alex Vergari (Institut Mines-Télécom) left.
-
Yan Zhang (DappWorks Technology Inc.) left.
-
Yi Shi (DappWorks Technology Inc.) left.
-
Chris Abernethy (Tradeverifyd) left.
-
Samuel Smith (W3C Invited Experts) left.
-
Marie Jordan (Visa) left.
-
Kaliya Young (W3C Invited Experts) left.
-
Shawn Butterfield (Salesforce) left.
-
Kimberly Linson (RANDA Solutions) left.
-
Martin Reed (RANDA Solutions) left.
-
Aaron Coburn (Inrupt Inc.) left.
-
Michael Prorock (Tradeverifyd) left.
-
Jaco Myburg (Entersekt) left.
-
Gerhard Oosthuizen (Entersekt) left.
-
Tobias Looker (Mattr Limited) left.
-
Chris Buchanan (MITRE Corporation) left.
-
David Waite (Ping Identity) left.
-
Oliver Terbu (Mattr Limited) left.
-
David Chadwick (W3C Invited Experts) left.
-
Arjen van Veen (Spruce Systems, Inc.) left.
-
Tommaso De Orchi (Futurae Technologies AG) left.
-
Jon St John (Anonyome Labs, Inc.) left.
-
John Mumford (Anonyome Labs, Inc.) left.
-
Rebecca Christman (Anonyome Labs, Inc.) left.
-
Bianca Arocho (Anonyome Labs, Inc.) left.
-
Geunhyung Kim (Sharing Economy Association of Korea (SEAK)) left.
-
Duy-Tung LUU (CANTON CONSULTING) left.
-
Jean-Yves ROSSI (CANTON CONSULTING) left.
-
-
15 organizations joined.
-
Entersekt joined.
-
Electronics and Telecommunications Research Institute (ETRI) joined.
-
Digital Contract Design joined.
-
Sony Group Corporation joined.
-
Skybridge Skills joined.
-
Graphwise joined.
-
China Academy of Information and Communications Technology (CAICT) joined.
-
Spruce Systems, Inc. joined.
-
Universities Admissions Centre joined.
-
Ant Group Co., Ltd. joined.
-
Sharing Economy Association of Korea (SEAK) joined.
-
Futurae Technologies AG joined.
-
Anonyome Labs, Inc. joined.
-
University of Oxford joined.
-
Conexxus joined.
-
GitHub
w3c/vcalm
-
7 issues opened.
-
Mermaid diagrams for interactions are incorrect w3c/vcalm#631, by @dlongley.
-
Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage w3c/vcalm#629, by @kezike.
-
Create Threat Model for VCALM w3c/vcalm#628, by @msporny.
-
Horizontal reviews for VCALM v1.0 w3c/vcalm#627, by @msporny.
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621, by @tidoust.
-
5 issues closed.
-
Add clarification of OAuth scope where needed w3c/vcalm#521.
-
5 issues received 8 new comments.
-
Add `redirectUrl` to step options to specify a `redirectUrl` to send to the client w3c/vcalm#590 (2 comments by @dlongley, @PatStLouis)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (1 comment by @tidoust)
-
Add optional `result` property to issue request element in `issueRequests` w3c/vcalm#583 (1 comment by @PatStLouis)
-
Specify optional "clientProfiles" in "openId" workflow step to support OID4VP multiplexing w3c/vcalm#527 (1 comment by @msporny)
-
8 pull requests opened.
-
Remove outdated issue about DataIntegrityProof. w3c/vcalm#632, by @BigBlueHat.
-
Added echidna workflow script w3c/vcalm#630, by @iherman.
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626, by @PatStLouis.
-
docs: explain indexAllocator for status updates w3c/vcalm#625, by @PatStLouis.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624, by @PatStLouis.
-
Fix links for FPWD transition. w3c/vcalm#623, by @kezike.
-
Prepare for FPWD transition. w3c/vcalm#622, by @kezike.
-
Add redirectUrl to step options in StepData. w3c/vcalm#620, by @bparth24.
-
-
4 pull requests merged.
-
Add redirectUrl to step options in StepData. w3c/vcalm#620.
-
Fix links for FPWD transition. w3c/vcalm#623.
-
Prepare for FPWD transition. w3c/vcalm#622.
-
-
1 pull request closed.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#572.
-
-
6 pull requests received 21 new comments.
-
docs: explain indexAllocator for status updates w3c/vcalm#625 (6 comments by @dlongley, @msporny, @TallTed)
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624 (5 comments by @PatStLouis, @TallTed, @w3cbot)
-
Add redirectUrl to step options in StepData. w3c/vcalm#620 (4 comments by @bparth24, @dlongley, @TallTed)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @TallTed)
-
Add optional result property to issueRequests and clarify variable name string format. w3c/vcalm#618 (1 comment by @ottonomy)
-
w3c/vc-data-model
-
2 issues opened.
-
Deprecate `digestSRI` in v2.1 w3c/vc-data-model#1628, by @msporny.
-
Use case: post-hoc integrity attestations for user-generated content w3c/vc-data-model#1627, by @onderl.
-
-
3 issues closed.
-
Clean up identifier definition w3c/vc-data-model#1624.
-
Revise language around dependent claims w3c/vc-data-model#1617.
-
Add SD-JWT-VC to Ecosystem Compatibility section w3c/vc-data-model#1593.
-
-
6 issues received 10 new comments.
-
1 pull request opened.
-
Fix citation `href` value for ETSI doc. w3c/vc-data-model#1626, by @BigBlueHat.
-
-
4 pull requests merged.
-
Fix citation `href` value for ETSI doc. w3c/vc-data-model#1626.
-
Update URL definition to clarify dereferencing w3c/vc-data-model#1625.
-
Remove guidance around bundling dependent claims. w3c/vc-data-model#1623.
-
Clarify that SD-JWT-VC is incompatible with W3C VCs. w3c/vc-data-model#1622.
-
-
4 pull requests received 4 new comments.
w3c/vc-wg
-
6 issues opened.
-
Vocabularies as notes? w3c/vc-wg#12, by @iherman.
-
Setting up Rendering method TF w3c/vc-wg#9, by @iherman.
-
Create VC Barcodes and Data Integrity w3c/vc-wg#8, by @msporny.
-
Create VCs for Entity Recognition Task Force w3c/vc-wg#7, by @msporny.
-
Create VCALM Task Force w3c/vc-wg#6, by @msporny.
-
Confidence Method task force w3c/vc-wg#5, by @jandrieu.
-
-
6 issues closed.
-
Create VCs for Entity Recognition Task Force w3c/vc-wg#7.
-
Create VCALM Task Force w3c/vc-wg#6.
-
Confidence Method task force w3c/vc-wg#5.
-
Create VC Barcodes and Data Integrity w3c/vc-wg#8.
-
Setting up Rendering method TF w3c/vc-wg#9.
-
Priorities for next W3C VCWG charter w3c/vc-wg#1.
-
-
6 issues received 27 new comments.
-
Create VCs for Entity Recognition Task Force w3c/vc-wg#7 (11 comments by @BigBlueHat, @iherman, @msporny, @shigeya, @TallTed)
-
Confidence Method task force w3c/vc-wg#5 (10 comments by @brentzundel, @iherman, @jandrieu, @TallTed)
-
-
2 pull requests opened.
-
Fix typos and improve wording in README.md w3c/vc-wg#11, by @TallTed.
-
Added TF infos to readme w3c/vc-wg#10, by @iherman.
-
-
2 pull requests merged.
-
Fix typos and improve wording in README.md w3c/vc-wg#11.
-
Added TF infos to readme w3c/vc-wg#10.
-
w3c/vc-recognized-entities
-
4 issues opened.
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73, by @iherman.
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71, by @msporny.
-
digestSRI missing? w3c/vc-recognized-entities#68, by @shigeya.
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66, by @onthebreeze.
-
-
3 issues received 5 new comments.
-
Change document title w3c/vc-recognized-entities#30 (3 comments by @BigBlueHat, @onthebreeze, @TallTed)
-
Create an example showing both `recognizedTo` and `recognizedIn` used concurrently. w3c/vc-recognized-entities#52 (1 comment by @iherman)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (1 comment by @iherman)
-
-
6 pull requests opened.
-
Adjust URL of live version in README w3c/vc-recognized-entities#72, by @tidoust.
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70, by @msporny.
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69, by @shigeya.
-
Remove version numbers from people names. w3c/vc-recognized-entities#67, by @BigBlueHat.
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65, by @BigBlueHat.
-
Update group and contacts in w3c.json. w3c/vc-recognized-entities#64, by @BigBlueHat.
-
-
4 pull requests merged.
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70.
-
Add Relationship to Other Technologies section. w3c/vc-recognized-entities#62.
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61.
-
Remove version numbers from people names. w3c/vc-recognized-entities#67.
-
-
1 pull request closed.
-
Update group and contacts in w3c.json. w3c/vc-recognized-entities#64.
-
-
5 pull requests received 29 new comments.
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61 (12 comments by @shigeya, @TallTed)
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (6 comments by @iherman, @msporny, @shigeya, @TallTed)
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70 (5 comments by @msporny, @onthebreeze)
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65 (3 comments by @BigBlueHat, @iherman)
-
Update group and contacts in w3c.json. w3c/vc-recognized-entities#64 (3 comments by @BigBlueHat, @iherman, @pchampin)
-
w3c/vc-barcodes
-
12 issues opened.
-
The introductory examples may need some care... w3c/vc-barcodes#49, by @iherman.
-
Is "xi" a general feature, not bound to barcodes? w3c/vc-barcodes#47, by @iherman.
-
Why ecdsa only in xi? w3c/vc-barcodes#45, by @iherman.
-
AIDC considerations w3c/vc-barcodes#43, by @philarcher.
-
(Editorial) §2.1 should be consistent with other class definitions w3c/vc-barcodes#42, by @iherman.
-
Create a Threat Model for VC Barcodes w3c/vc-barcodes#41, by @msporny.
-
Horizontal Review for VC Barcodes v1.0 w3c/vc-barcodes#40, by @msporny.
-
Very long respec loading... w3c/vc-barcodes#39, by @iherman.
-
"Original" barcode? (Section §2.1) w3c/vc-barcodes#38, by @iherman.
-
Editorial comments w3c/vc-barcodes#37, by @iherman.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34, by @ewoogit.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33, by @ewoogit.
-
-
2 issues closed.
-
Add "bare" VCs in QR Codes to spec w3c/vc-barcodes#21.
-
Very long respec loading... w3c/vc-barcodes#39.
-
-
5 issues received 5 new comments.
-
Outdated `TerseBitstringStatusListEntry` to `BitstringStatusListEntry` conversion w3c/vc-barcodes#19 (1 comment by @wes-smith)
-
Update examples to use proper `TerseBitstringStatusList` entry definition from vc-barcodes context w3c/vc-barcodes#17 (1 comment by @wes-smith)
-
6 pull requests opened.
-
Add discussion of multibase header in PDF417 VCBs. w3c/vc-barcodes#50, by @wes-smith.
-
Update verification examples. w3c/vc-barcodes#48, by @wes-smith.
-
Added echidna workflow script w3c/vc-barcodes#46, by @iherman.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44, by @wes-smith.
-
Updated the short name w3c/vc-barcodes#36, by @iherman.
-
Prepare for FPWD publication. w3c/vc-barcodes#35, by @wes-smith.
-
-
3 pull requests merged.
-
Updated the short name w3c/vc-barcodes#36.
-
Added echidna workflow script w3c/vc-barcodes#46.
-
Prepare for FPWD publication. w3c/vc-barcodes#35.
-
-
5 pull requests received 17 new comments.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44 (13 comments by @dlongley, @iherman, @msporny, @TallTed, @wes-smith)
-
w3c/cid
-
1 issue opened.
-
Should application/cid define a profile= parameter? w3c/cid#169, by @trwnh.
-
-
1 pull request opened.
-
Allow for fragment identifier in document.id w3c/cid#168, by @pchampin.
-
-
1 pull request received 5 new comments.
-
Allow for fragment identifier in document.id w3c/cid#168 (5 comments by @iherman, @TallTed, @uvdsl, @w3cbot)
-
w3c/vc-di-quantum-resistant
-
5 issues opened.
-
Support for Selective Disclosure w3c/vc-di-quantum-resistant#22, by @Wind4Greg.
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19, by @msporny.
-
Horizontal Review for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#18, by @msporny.
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17, by @msporny.
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15, by @amir-hameed-mir.
-
-
1 issue closed.
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15.
-
-
2 issues received 4 new comments.
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19 (2 comments by @msporny, @Wind4Greg)
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15 (2 comments by @amir-hameed-mir, @Wind4Greg)
-
-
4 pull requests opened.
-
Add CG Report; set base to `CG-FINAL`. w3c/vc-di-quantum-resistant#23, by @BigBlueHat.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21, by @Wind4Greg.
-
Update Security Considerations Section w3c/vc-di-quantum-resistant#20, by @Wind4Greg.
-
Update Multikey and Test Vectors for FALCON-512 and SQIsign-I w3c/vc-di-quantum-resistant#16, by @Wind4Greg.
-
-
5 pull requests merged.
-
Add CG Report; set base to `CG-FINAL`. w3c/vc-di-quantum-resistant#23.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21.
-
Update Security Considerations Section w3c/vc-di-quantum-resistant#20.
-
Update Multikey and Test Vectors for FALCON-512 and SQIsign-I w3c/vc-di-quantum-resistant#16.
-
FALCON and SQIsign Updates w3c/vc-di-quantum-resistant#14.
-
-
1 pull request received 2 new comments.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21 (2 comments by @dlongley, @TallTed)
-
w3c/vc-data-integrity
-
1 issue received 1 new comment.
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @iherman)
-
-
1 pull request opened.
-
Update echidna w3c/vc-data-integrity#347, by @iherman.
-
w3c/vc-confidence-method
-
3 issues received 19 new comments.
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31 (14 comments by @amir-hameed-mir, @dlongley, @jandrieu, @msporny, @ScottJeezey)
-
Isn't example 1 incomplete? w3c/vc-confidence-method#32 (3 comments by @amir-hameed-mir, @dlongley, @iherman)
-
One confidence method on several subjects? w3c/vc-confidence-method#34 (2 comments by @amir-hameed-mir, @TallTed)
-
-
2 pull requests opened.
-
Change specStatus from FPWD to ED w3c/vc-confidence-method#36, by @jandrieu.
-
Minor change to test echidna w3c/vc-confidence-method#35, by @jandrieu.
-
-
2 pull requests merged.
-
Change specStatus from FPWD to ED w3c/vc-confidence-method#36.
-
Minor change to test echidna w3c/vc-confidence-method#35.
-
-
1 pull request received 2 new comments.
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29 (2 comments by @jandrieu, @TallTed)
-
w3c/vc-di-ecdsa
-
2 pull requests opened.
-
Update echidna w3c/vc-di-ecdsa#104, by @iherman.
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103, by @scouttyg.
-
-
1 pull request received 1 new comment.
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103 (1 comment by @w3cbot)
-
w3c/vc-di-eddsa
-
2 pull requests opened.
-
Update echidna w3c/vc-di-eddsa#116, by @iherman.
-
Create transitions/2026/FPWD. w3c/vc-di-eddsa#115, by @Wind4Greg.
-
-
1 pull request merged.
-
Create transitions/2026/FPWD. w3c/vc-di-eddsa#115.
-
w3c/vc-render-method
-
1 issue closed.
-
Re-enable markup validation for WD publication w3c/vc-render-method#50.
-
-
1 issue received 6 new comments.
-
Re-enable markup validation for WD publication w3c/vc-render-method#50 (6 comments by @deniak, @iherman, @jandrieu, @msporny)
-
VC API for Lifecycle Management
Past meetings
-
1 meeting of the VC API for Lifecycle Management.
Participants
-
2 chairs appointed in the VC API for Lifecycle Management.
-
Kayode Ezike became a chair.
-
Patrick St-Louis became a chair.
-
-
1 Team contact appointed in the VC API for Lifecycle Management.
-
Ivan Herman became a Team contact.
-
-
15 participants joined the VC API for Lifecycle Management.
-
Parth Bhatt joined.
-
Kevin Dean joined.
-
Joe Andrieu joined.
-
Henrique Xavier joined.
-
Elaine Wooton joined.
-
Dmitri Zagidulin joined.
-
Benjamin Young joined.
-
Dave Longley joined.
-
Phil Archer joined.
-
Brent Zundel joined.
-
Ted Thibodeau Jr joined.
-
Manu Sporny joined.
-
Kayode Ezike joined.
-
Patrick St-Louis joined.
-
Ivan Herman joined.
-
GitHub
w3c/vcalm
-
7 issues opened in the VC API for Lifecycle Management.
-
Mermaid diagrams for interactions are incorrect w3c/vcalm#631, by @dlongley.
-
Add clarity around `acceptedEnvelopes` vs. `acceptedCryptosuites` usage w3c/vcalm#629, by @kezike.
-
Create Threat Model for VCALM w3c/vcalm#628, by @msporny.
-
Horizontal reviews for VCALM v1.0 w3c/vcalm#627, by @msporny.
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621, by @tidoust.
-
5 issues closed in the VC API for Lifecycle Management.
-
Add clarification of OAuth scope where needed w3c/vcalm#521.
-
5 issues in the VC API for Lifecycle Management received 8 new comments.
-
Add `redirectUrl` to step options to specify a `redirectUrl` to send to the client w3c/vcalm#590 (2 comments by @dlongley, @PatStLouis)
-
Scope definition of "domain" to "verifiable presentation request"? w3c/vcalm#621 (1 comment by @tidoust)
-
Add optional `result` property to issue request element in `issueRequests` w3c/vcalm#583 (1 comment by @PatStLouis)
-
Specify optional "clientProfiles" in "openId" workflow step to support OID4VP multiplexing w3c/vcalm#527 (1 comment by @msporny)
-
8 pull requests opened in the VC API for Lifecycle Management.
-
Remove outdated issue about DataIntegrityProof. w3c/vcalm#632, by @BigBlueHat.
-
Added echidna workflow script w3c/vcalm#630, by @iherman.
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626, by @PatStLouis.
-
docs: explain indexAllocator for status updates w3c/vcalm#625, by @PatStLouis.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624, by @PatStLouis.
-
Fix links for FPWD transition. w3c/vcalm#623, by @kezike.
-
Prepare for FPWD transition. w3c/vcalm#622, by @kezike.
-
Add redirectUrl to step options in StepData. w3c/vcalm#620, by @bparth24.
-
-
4 pull requests merged in the VC API for Lifecycle Management.
-
Add redirectUrl to step options in StepData. w3c/vcalm#620.
-
Fix links for FPWD transition. w3c/vcalm#623.
-
Prepare for FPWD transition. w3c/vcalm#622.
-
-
1 pull request closed in the VC API for Lifecycle Management.
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#572.
-
-
5 pull requests in the VC API for Lifecycle Management received 20 new comments.
-
docs: explain indexAllocator for status updates w3c/vcalm#625 (6 comments by @dlongley, @msporny, @TallTed)
-
Add selective disclosure example and conversion pseudo code w3c/vcalm#624 (5 comments by @PatStLouis, @TallTed, @w3cbot)
-
Add redirectUrl to step options in StepData. w3c/vcalm#620 (4 comments by @bparth24, @dlongley, @TallTed)
-
docs: add informative reference workflow step processing algorithm w3c/vcalm#626 (1 comment by @TallTed)
-
VC Recognized Entities
Past meetings
-
3 meetings of the VC Recognized Entities.
Participants
-
2 chairs appointed in the VC Recognized Entities.
-
Manu Sporny became a chair.
-
Benjamin Young became a chair.
-
-
1 Team contact appointed in the VC Recognized Entities.
-
Ivan Herman became a Team contact.
-
-
14 participants joined the VC Recognized Entities.
-
Elaine Wooton joined.
-
Steven Capell joined.
-
Parth Bhatt joined.
-
Kevin Dean joined.
-
Kayode Ezike joined.
-
Dmitri Zagidulin joined.
-
Dave Longley joined.
-
Ted Thibodeau Jr joined.
-
Shigeya Suzuki joined.
-
Brent Zundel joined.
-
Phil Archer joined.
-
Manu Sporny joined.
-
Benjamin Young joined.
-
Ivan Herman joined.
-
GitHub
w3c/vc-recognized-entities
-
4 issues opened in the VC Recognized Entities.
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73, by @iherman.
-
How are different `type`s supported for `recognizedIn`? w3c/vc-recognized-entities#71, by @msporny.
-
digestSRI missing? w3c/vc-recognized-entities#68, by @shigeya.
-
UNTP / UNGRID / DIA Identity Anchor use case w3c/vc-recognized-entities#66, by @onthebreeze.
-
-
3 issues in the VC Recognized Entities received 5 new comments.
-
Change document title w3c/vc-recognized-entities#30 (3 comments by @BigBlueHat, @onthebreeze, @TallTed)
-
Create an example showing both `recognizedTo` and `recognizedIn` used concurrently. w3c/vc-recognized-entities#52 (1 comment by @iherman)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (1 comment by @iherman)
-
-
5 pull requests opened in the VC Recognized Entities.
-
Adjust URL of live version in README w3c/vc-recognized-entities#72, by @tidoust.
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70, by @msporny.
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69, by @shigeya.
-
Remove version numbers from people names. w3c/vc-recognized-entities#67, by @BigBlueHat.
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65, by @BigBlueHat.
-
-
4 pull requests merged in the VC Recognized Entities.
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70.
-
Add Relationship to Other Technologies section. w3c/vc-recognized-entities#62.
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61.
-
Remove version numbers from people names. w3c/vc-recognized-entities#67.
-
-
1 pull request closed in the VC Recognized Entities.
-
Update group and contacts in w3c.json. w3c/vc-recognized-entities#64.
-
-
5 pull requests in the VC Recognized Entities received 17 new comments.
-
Add `digestSRI` property to General Properties w3c/vc-recognized-entities#69 (6 comments by @iherman, @msporny, @shigeya, @TallTed)
-
Applies the result of the spec renaming poll w3c/vc-recognized-entities#70 (5 comments by @msporny, @onthebreeze)
-
Revise README to new name: Recognized Entities. w3c/vc-recognized-entities#65 (3 comments by @BigBlueHat, @iherman)
-
Update group and contacts in w3c.json. w3c/vc-recognized-entities#64 (2 comments by @iherman, @pchampin)
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61 (1 comment by @shigeya)
-
VC Confidence Method
Participants
-
2 chairs appointed in the VC Confidence Method.
-
Denken Chen became a chair.
-
Joe Andrieu became a chair.
-
-
1 Team contact appointed in the VC Confidence Method.
-
Ivan Herman became a Team contact.
-
-
13 participants joined the VC Confidence Method.
-
Elaine Wooton joined.
-
Ted Thibodeau Jr joined.
-
Phillip Long joined.
-
Manu Sporny joined.
-
Henrique Xavier joined.
-
Dmitri Zagidulin joined.
-
Dave Longley joined.
-
Benjamin Young joined.
-
Denken Chen joined.
-
Joe Andrieu joined.
-
Phil Archer joined.
-
Brent Zundel joined.
-
Ivan Herman joined.
-
GitHub
w3c/vc-confidence-method
-
2 issues in the VC Confidence Method received 16 new comments.
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31 (14 comments by @amir-hameed-mir, @dlongley, @jandrieu, @msporny, @ScottJeezey)
-
One confidence method on several subjects? w3c/vc-confidence-method#34 (2 comments by @amir-hameed-mir, @TallTed)
-
-
1 pull request in the VC Confidence Method received 2 new comments.
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29 (2 comments by @jandrieu, @TallTed)
-
VC Render Method
Participants
-
1 chair appointed in the VC Render Method.
-
Dmitri Zagidulin became a chair.
-
-
1 Team contact appointed in the VC Render Method.
-
Ivan Herman became a Team contact.
-
-
14 participants joined the VC Render Method.
-
Elaine Wooton joined.
-
Will Abramson joined.
-
Ted Thibodeau Jr joined.
-
Parth Bhatt joined.
-
Manu Sporny joined.
-
Kevin Dean joined.
-
Henrique Xavier joined.
-
Dave Longley joined.
-
Benjamin Young joined.
-
Amir Hameed Mir joined.
-
Dmitri Zagidulin joined.
-
Phil Archer joined.
-
Brent Zundel joined.
-
Ivan Herman joined.
-
GitHub
w3c/vc-render-method
-
1 issue closed in the VC Render Method.
-
Re-enable markup validation for WD publication w3c/vc-render-method#50.
-
-
1 issue in the VC Render Method received 1 new comment.
VC Barcodes and Data Integrity
Past meetings
-
3 meetings of the VC Barcodes and Data Integrity.
Participants
-
3 chairs appointed in the VC Barcodes and Data Integrity.
-
Greg Bernstein became a chair.
-
Wesley Smith became a chair.
-
Elaine Wooton became a chair.
-
-
1 Team contact appointed in the VC Barcodes and Data Integrity.
-
Ivan Herman became a Team contact.
-
-
14 participants joined the VC Barcodes and Data Integrity.
-
David Lehn joined.
-
Phillip Long joined.
-
Kevin Dean joined.
-
Parth Bhatt joined.
-
Benjamin Young joined.
-
Dave Longley joined.
-
Ted Thibodeau Jr joined.
-
Brent Zundel joined.
-
Phil Archer joined.
-
Manu Sporny joined.
-
Greg Bernstein joined.
-
Wesley Smith joined.
-
Elaine Wooton joined.
-
Ivan Herman joined.
-
GitHub
w3c/vc-barcodes
-
12 issues opened in the VC Barcodes and Data Integrity.
-
The introductory examples may need some care... w3c/vc-barcodes#49, by @iherman.
-
Is "xi" a general feature, not bound to barcodes? w3c/vc-barcodes#47, by @iherman.
-
Why ecdsa only in xi? w3c/vc-barcodes#45, by @iherman.
-
AIDC considerations w3c/vc-barcodes#43, by @philarcher.
-
(Editorial) §2.1 should be consistent with other class definitions w3c/vc-barcodes#42, by @iherman.
-
Create a Threat Model for VC Barcodes w3c/vc-barcodes#41, by @msporny.
-
Horizontal Review for VC Barcodes v1.0 w3c/vc-barcodes#40, by @msporny.
-
Very long respec loading... w3c/vc-barcodes#39, by @iherman.
-
"Original" barcode? (Section §2.1) w3c/vc-barcodes#38, by @iherman.
-
Editorial comments w3c/vc-barcodes#37, by @iherman.
-
Add privacy considerations discussion to the spec. w3c/vc-barcodes#34, by @ewoogit.
-
Add mechanism to protect VC Barcodes from insider threats and quantum computers w3c/vc-barcodes#33, by @ewoogit.
-
-
2 issues closed in the VC Barcodes and Data Integrity.
-
Add "bare" VCs in QR Codes to spec w3c/vc-barcodes#21.
-
Very long respec loading... w3c/vc-barcodes#39.
-
-
5 issues in the VC Barcodes and Data Integrity received 5 new comments.
-
Outdated `TerseBitstringStatusListEntry` to `BitstringStatusListEntry` conversion w3c/vc-barcodes#19 (1 comment by @wes-smith)
-
Update examples to use proper `TerseBitstringStatusList` entry definition from vc-barcodes context w3c/vc-barcodes#17 (1 comment by @wes-smith)
-
6 pull requests opened in the VC Barcodes and Data Integrity.
-
Add discussion of multibase header in PDF417 VCBs. w3c/vc-barcodes#50, by @wes-smith.
-
Update verification examples. w3c/vc-barcodes#48, by @wes-smith.
-
Added echidna workflow script w3c/vc-barcodes#46, by @iherman.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44, by @wes-smith.
-
Updated the short name w3c/vc-barcodes#36, by @iherman.
-
Prepare for FPWD publication. w3c/vc-barcodes#35, by @wes-smith.
-
-
3 pull requests merged in the VC Barcodes and Data Integrity.
-
Updated the short name w3c/vc-barcodes#36.
-
Added echidna workflow script w3c/vc-barcodes#46.
-
Prepare for FPWD publication. w3c/vc-barcodes#35.
-
-
5 pull requests in the VC Barcodes and Data Integrity received 17 new comments.
-
Clarify the two major VC Barcode use cases. w3c/vc-barcodes#44 (13 comments by @dlongley, @iherman, @msporny, @TallTed, @wes-smith)
-
w3c/vc-di-quantum-resistant
-
5 issues opened in the VC Barcodes and Data Integrity.
-
Support for Selective Disclosure w3c/vc-di-quantum-resistant#22, by @Wind4Greg.
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19, by @msporny.
-
Horizontal Review for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#18, by @msporny.
-
ML-DSA 44 Secret Key varint / hex values not defined w3c/vc-di-quantum-resistant#17, by @msporny.
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15, by @amir-hameed-mir.
-
-
1 issue closed in the VC Barcodes and Data Integrity.
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15.
-
-
2 issues in the VC Barcodes and Data Integrity received 4 new comments.
-
Create a Threat Model for Quantum Safe Data Integrity Cryptosuites w3c/vc-di-quantum-resistant#19 (2 comments by @msporny, @Wind4Greg)
-
Test Vector: ML-DSA-87 with SUCRE Masking (146ms sign / 34ms verify) w3c/vc-di-quantum-resistant#15 (2 comments by @amir-hameed-mir, @Wind4Greg)
-
-
4 pull requests opened in the VC Barcodes and Data Integrity.
-
Add CG Report; set base to `CG-FINAL`. w3c/vc-di-quantum-resistant#23, by @BigBlueHat.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21, by @Wind4Greg.
-
Update Security Considerations Section w3c/vc-di-quantum-resistant#20, by @Wind4Greg.
-
Update Multikey and Test Vectors for FALCON-512 and SQIsign-I w3c/vc-di-quantum-resistant#16, by @Wind4Greg.
-
-
5 pull requests merged in the VC Barcodes and Data Integrity.
-
Add CG Report; set base to `CG-FINAL`. w3c/vc-di-quantum-resistant#23.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21.
-
Update Security Considerations Section w3c/vc-di-quantum-resistant#20.
-
Update Multikey and Test Vectors for FALCON-512 and SQIsign-I w3c/vc-di-quantum-resistant#16.
-
FALCON and SQIsign Updates w3c/vc-di-quantum-resistant#14.
-
-
1 pull request in the VC Barcodes and Data Integrity received 2 new comments.
-
Editorial Cleanup and Privacy Update w3c/vc-di-quantum-resistant#21 (2 comments by @dlongley, @TallTed)
-
w3c/vc-data-integrity
-
1 issue in the VC Barcodes and Data Integrity received 1 new comment.
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344 (1 comment by @iherman)
-
-
1 pull request opened in the VC Barcodes and Data Integrity.
-
Update echidna w3c/vc-data-integrity#347, by @iherman.
-
w3c/vc-di-ecdsa
-
2 pull requests opened in the VC Barcodes and Data Integrity.
-
Update echidna w3c/vc-di-ecdsa#104, by @iherman.
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103, by @scouttyg.
-
-
1 pull request in the VC Barcodes and Data Integrity received 1 new comment.
-
Fix mismatched prCredUnsigned.json description compared to data from ecdsa-sd-2023/prc/ w3c/vc-di-ecdsa#103 (1 comment by @w3cbot)
-
w3c/vc-di-eddsa
-
2 pull requests opened in the VC Barcodes and Data Integrity.
-
Update echidna w3c/vc-di-eddsa#116, by @iherman.
-
Create transitions/2026/FPWD. w3c/vc-di-eddsa#115, by @Wind4Greg.
-
-
1 pull request merged in the VC Barcodes and Data Integrity.
-
Create transitions/2026/FPWD. w3c/vc-di-eddsa#115.
-
VC DPP & Business Wallet
Participants
-
1 chair appointed in the VC DPP & Business Wallet.
-
Carolynn Bernier became a chair.
-
-
1 Team contact appointed in the VC DPP & Business Wallet.
-
Ivan Herman became a Team contact.
-
-
7 participants joined the VC DPP & Business Wallet.
-
Carolynn Bernier joined.
-
Susanne Guth-Orlowski joined.
-
Ivo Ladenius joined.
-
Brent Zundel joined.
-
Ivan Herman joined.
-
Phil Archer joined.
-
Eva Blomqvist joined.
-
Lifecycle
-
1 charter started.
-
Chartered until 31 March 2028. Participants had to rejoin under this charter.
-
TR publications
-
1 document published.
-
Verifiable Credentials Use Cases published as a Note. History of Verifiable Credentials Use Cases
-
Past meetings
Participants
-
12 participants joined.
-
Zachary Zeus (Pyx Industries) joined.
-
Steven Capell (Pyx Industries) joined.
-
Sebastian Schmittner (W3C Invited Experts) joined.
-
Kayode Ezike (W3C Invited Experts) joined.
-
Eva Blomqvist (W3C Invited Experts) joined.
-
Susanne Guth-Orlowski (W3C Invited Experts) joined.
-
Yuqiang Wang (Beijing Cognitive Emergence Technology Co., Ltd) joined.
-
Raja Rakshit Varanasi (Stony Brook University) joined.
-
Henrique Xavier (NIC.br - Brazilian Network Information Center) joined.
-
Paul Dietrich (GS1) joined.
-
Todd Snyder (GS1) joined.
-
Rob De Feo (Vidos) joined.
-
-
9 participants left.
-
Nicholas Steele (1Password) left.
-
Yen-Lin Huang (Ministry of Digital Affairs, Taiwan) left.
-
Tyler Minard (Digital Bazaar) left.
-
Mandy Venables (Digital Bazaar) left.
-
Amy Guy (Digital Bazaar) left.
-
Ganesh Annan (Digital Bazaar) left.
-
Nicholas Lansley (GS1) left.
-
Paul Dietrich (GS1) left.
-
Todd Snyder (GS1) left.
-
-
24 organizations joined.
-
Switchchord joined.
-
Pyx Industries joined.
-
Arizona State University joined.
-
UnitedHealth Group joined.
-
OpenLink Software Inc. joined.
-
Web Consortium Asia Pacific (WCAP) joined.
-
HM Government joined.
-
Universidad Politécnica de Madrid joined.
-
OISTE Foundation joined.
-
Adobe joined.
-
SURF bv joined.
-
1Password joined.
-
Beijing Cognitive Emergence Technology Co., Ltd joined.
-
Ministry of Digital Affairs, Taiwan joined.
-
Mavennet Systems Inc. joined.
-
Yubico joined.
-
Stony Brook University joined.
-
NIC.br - Brazilian Network Information Center joined.
-
Originator Profile CIP joined.
-
Keio University joined.
-
Legendary Requirements joined.
-
Vidos joined.
-
GS1 joined.
-
Digital Bazaar joined.
-
-
69 organizations left.
-
Stony Brook University left.
-
NIC.br - Brazilian Network Information Center left.
-
HM Government left.
-
UnitedHealth Group left.
-
Futurae Technologies AG left.
-
Yubico left.
-
Depixen left.
-
Bitwarden left.
-
University of Oxford left.
-
Web Consortium Asia Pacific (WCAP) left.
-
Ant Group Co., Ltd. left.
-
Holopin left.
-
Originator Profile CIP left.
-
CREATIVECODE left.
-
1Password left.
-
Kodansha, Publishers, Ltd. left.
-
Electronics and Telecommunications Research Institute (ETRI) left.
-
Vidos left.
-
Ignite Retail Technology left.
-
Jiangsu TPBlock Technology Co., Ltd. （江苏第三极区块链科技有限公司） left.
-
OISTE Foundation left.
-
Department of Homeland Security left.
-
INSIGHT - The Centre for Data Analytics left.
-
Autodesk left.
-
Switchchord left.
-
Akamai Technologies left.
-
Ver.iD left.
-
Universidad Politécnica de Madrid left.
-
CANTON CONSULTING left.
-
Universities Admissions Centre left.
-
LG Electronics left.
-
Intel Corporation left.
-
Ministry of Digital Affairs, Taiwan left.
-
Keio University left.
-
360 left.
-
Fundacion CTIC left.
-
Legendary Requirements left.
-
Arizona State University left.
-
Mastercard Incorporated left.
-
Gooroomee Inc. left.
-
Institut Mines-Télécom left.
-
DappWorks Technology Inc. left.
-
Anonyome Labs, Inc. left.
-
Visa left.
-
Dfinity Stiftung left.
-
SURF bv left.
-
Sony Group Corporation left.
-
Entersekt left.
-
Mattr Limited left.
-
MITRE Corporation left.
-
Kaiser Permanente left.
-
Inrupt Inc. left.
-
RANDA Solutions left.
-
Google LLC left.
-
Digital Contract Design left.
-
Spruce Systems, Inc. left.
-
GS1 left.
-
Merchant Advisory Group left.
-
China Academy of Information and Communications Technology (CAICT) left.
-
OpenLink Software Inc. left.
-
Adobe left.
-
The New York Times left.
-
Salesforce left.
-
Mavennet Systems Inc. left.
-
Digital Bazaar left.
-
Ping Identity left.
-
Microsoft Corporation left.
-
Conexxus left.
-
Tradeverifyd left.
-
GitHub
w3c/vc-confidence-method
-
5 issues opened.
-
One confidence method on several subjects? w3c/vc-confidence-method#34, by @iherman.
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33, by @iherman.
-
Isn't example 1 incomplete? w3c/vc-confidence-method#32, by @iherman.
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31, by @msporny.
-
Consider ISO IEC 29115:2013 w3c/vc-confidence-method#30, by @jandrieu.
-
-
4 issues received 7 new comments.
-
Determine if a privacy-preserving client-side biometric is possible w3c/vc-confidence-method#31 (4 comments by @msporny, @ScottJeezey)
-
Definitions of `confidenceMethod` in this spec and VCDM are not consistent w3c/vc-confidence-method#33 (1 comment by @TallTed)
-
-
1 pull request opened.
-
first pass at integrated confidence and assurance methods w3c/vc-confidence-method#29, by @jandrieu.
-
w3c/vcalm
-
7 issues opened.
-
Improve UX around OAS output in the main specification w3c/vcalm#606, by @BigBlueHat.
-
Add an `interaction:` scheme interaction URL example in its section w3c/vcalm#601, by @dlongley.
-
Nonsensical display for "variables" on create exchange endpoint w3c/vcalm#599, by @ottonomy.
-
6 issues closed.
-
Questions regarding `QueryByExample` structure and handling w3c/vcalm#538.
-
13 issues received 22 new comments.
-
Add a multistep workflow example with branching steps generated from step templates w3c/vcalm#600 (3 comments by @dlongley, @msporny)
-
Add optional `result` property to issue request element in `issueRequests` w3c/vcalm#583 (2 comments by @dlongley, @ottonomy)
-
Add support for `VerifiableRecognitionCredential`s to be used in `acceptedIssuers` field w3c/vcalm#598 (2 comments by @msporny)
-
Improve UX around OAS output in the main specification w3c/vcalm#606 (2 comments by @msporny, @ottonomy)
-
Consider adding optional `referenceId` as a top-level property in exchange messages w3c/vcalm#604 (2 comments by @BigBlueHat, @msporny)
-
Add `step.verifiablePresentation` option to explicitly express VP to be used in a step w3c/vcalm#575 (1 comment by @msporny)
-
Consider defining normative/non-normative workflow processing algorithm w3c/vcalm#596 (1 comment by @msporny)
-
Nonsensical display for "variables" on create exchange endpoint w3c/vcalm#599 (1 comment by @BigBlueHat)
-
Fix rendering issues that occur whenever `oneOf` is used with `required` constraint w3c/vcalm#605 (1 comment by @kezike)
-
13 pull requests opened.
-
Add ability for acceptedIssuers to include VRCs. w3c/vcalm#615, by @msporny.
-
Update guidance on OAuth 2.0 scopes. w3c/vcalm#614, by @msporny.
-
Comment out `publishDate`. w3c/vcalm#613, by @BigBlueHat.
-
Set publication date to 2026-03-20. w3c/vcalm#612, by @BigBlueHat.
-
fix(oas): Explicitly declare empty properties for empty object w3c/vcalm#611, by @ottonomy.
-
Add optional referenceId to exchange participation messages w3c/vcalm#610, by @ottonomy.
-
Add CG Report; configure respec to match future. w3c/vcalm#609, by @BigBlueHat.
-
Add Editors and Authors. w3c/vcalm#608, by @BigBlueHat.
-
Fix misspelling of the word `Coordinator`. w3c/vcalm#607, by @jameseaster.
-
Use generic object without results for create exchange variables. w3c/vcalm#603, by @kezike.
-
Add an example interaction scheme format URL w3c/vcalm#602, by @ottonomy.
-
13 pull requests merged.
-
Add ability for acceptedIssuers to include VRCs. w3c/vcalm#615.
-
Update guidance on OAuth 2.0 scopes. w3c/vcalm#614.
-
Comment out `publishDate`. w3c/vcalm#613.
-
Set publication date to 2026-03-20. w3c/vcalm#612.
-
Add CG Report; configure respec to match future. w3c/vcalm#609.
-
Add Editors and Authors. w3c/vcalm#608.
-
Fix misspelling of the word `Coordinator`. w3c/vcalm#607.
-
Add optional referenceId to exchange participation messages w3c/vcalm#610.
-
Add JSON Schema for QueryByExample w3c/vcalm#593.
-
Add an example interaction scheme format URL w3c/vcalm#602.
-
9 pull requests received 43 new comments.
-
Add Editors and Authors. w3c/vcalm#608 (5 comments by @eric-schuh, @jandrieu, @kezike, @ottonomy, @PatStLouis)
-
Add CG Report; configure respec to match future. w3c/vcalm#609 (2 comments by @BigBlueHat, @msporny)
-
Add step.verifiablePresentation option to explicitly express VP to be used in a step w3c/vcalm#617 (1 comment by @TallTed)
-
Add optional referenceId to exchange participation messages w3c/vcalm#610 (1 comment by @PatStLouis)
-
Use generic object without results for create exchange variables. w3c/vcalm#603 (1 comment by @msporny)
w3c/vc-di-quantum-resistant
-
4 pull requests opened.
-
FALCON and SQIsign Updates w3c/vc-di-quantum-resistant#14, by @Wind4Greg.
-
Editorial fixes and Updates and Add Greg as Editor/Author w3c/vc-di-quantum-resistant#13, by @Wind4Greg.
-
Test vectors and Explanatory Text w3c/vc-di-quantum-resistant#12, by @Wind4Greg.
-
Multikey, cryptosuites, proof representation updates w3c/vc-di-quantum-resistant#11, by @Wind4Greg.
-
-
4 pull requests merged.
-
Editorial fixes and Updates and Add Greg as Editor/Author w3c/vc-di-quantum-resistant#13.
-
Test vectors and Explanatory Text w3c/vc-di-quantum-resistant#12.
-
Multikey, cryptosuites, proof representation updates w3c/vc-di-quantum-resistant#11.
-
Update/Refactor Common Algorithms, ML-DSA, SLH-DSA, Outline Test Vector sections w3c/vc-di-quantum-resistant#10.
-
-
3 pull requests received 25 new comments.
-
Multikey, cryptosuites, proof representation updates w3c/vc-di-quantum-resistant#11 (14 comments by @msporny, @TallTed, @Wind4Greg)
-
Test vectors and Explanatory Text w3c/vc-di-quantum-resistant#12 (6 comments by @msporny, @Wind4Greg)
-
Editorial fixes and Updates and Add Greg as Editor/Author w3c/vc-di-quantum-resistant#13 (5 comments by @dlongley, @TallTed, @Wind4Greg)
-
w3c/vc-barcodes
-
1 issue opened.
-
Fix link link in the compression tables section. w3c/vc-barcodes#28, by @davidlehn.
-
-
1 issue closed.
-
Fix link link in the compression tables section. w3c/vc-barcodes#28.
-
-
5 pull requests opened.
-
Add devcontainer.json for preview in codespaces. w3c/vc-barcodes#32, by @BigBlueHat.
-
Remove `publishDate`. w3c/vc-barcodes#31, by @BigBlueHat.
-
Set publication date to 2026-03-20. w3c/vc-barcodes#30, by @BigBlueHat.
-
Various updates. w3c/vc-barcodes#29, by @davidlehn.
-
Add CG Report; configure respec to match future. w3c/vc-barcodes#27, by @BigBlueHat.
-
-
5 pull requests merged.
-
Remove `publishDate`. w3c/vc-barcodes#31.
-
Set publication date to 2026-03-20. w3c/vc-barcodes#30.
-
Add CG Report; configure respec to match future. w3c/vc-barcodes#27.
-
Various updates. w3c/vc-barcodes#29.
-
Fix link to github repository w3c/vc-barcodes#26.
-
-
1 pull request closed.
-
fix grammar, punctuation, some whitespace w3c/vc-barcodes#10.
-
-
4 pull requests received 11 new comments.
-
fix grammar, punctuation, some whitespace w3c/vc-barcodes#10 (5 comments by @BigBlueHat, @davidlehn, @TallTed)
-
Add CG Report; configure respec to match future. w3c/vc-barcodes#27 (2 comments by @BigBlueHat, @ewoogit)
-
w3c/vc-render-method
-
1 issue opened.
-
Re-enable markup validation for WD publication w3c/vc-render-method#50, by @msporny.
-
-
1 issue closed.
-
Mustache Template Rendering Algorithm w3c/vc-render-method#40.
-
-
4 pull requests opened.
-
Update publish-wd.yaml to allow manual start w3c/vc-render-method#52, by @iherman.
-
Add outputPreference terms section. w3c/vc-render-method#51, by @BigBlueHat.
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49, by @msporny.
-
Add info about Oblivious HTTP. w3c/vc-render-method#48, by @BigBlueHat.
-
-
3 pull requests merged.
-
Update publish-wd.yaml to allow manual start w3c/vc-render-method#52.
-
fix: update OpenAttestationEmbeddedRenderer to EmbeddedRenderer w3c/vc-render-method#25.
-
Refer to mustache templating algorithm instead of reproducing a partial w3c/vc-render-method#41.
-
-
1 pull request closed.
-
Introduce `RenderMethod` for untemplated renderings. w3c/vc-render-method#38.
-
-
8 pull requests received 12 new comments.
-
Introduce `RenderMethod` for untemplated renderings. w3c/vc-render-method#38 (3 comments by @BigBlueHat, @msporny)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (3 comments by @BigBlueHat, @ottonomy)
-
Remove pdf-mustache render suite and svg-mustache render suite. w3c/vc-render-method#49 (1 comment by @msporny)
-
Add OverlayRenderMethod with oca-bundle-v2 render suite w3c/vc-render-method#30 (1 comment by @msporny)
-
fix: update OpenAttestationEmbeddedRenderer to EmbeddedRenderer w3c/vc-render-method#25 (1 comment by @msporny)
-
w3c/vc-recognized-entities
-
4 issues opened.
-
How do you state a historical recognized action is valid between two dates? w3c/vc-recognized-entities#63, by @msporny.
-
Add Privacy Considerations on Verifiable Recognition Credential delivery mechanisms w3c/vc-recognized-entities#56, by @msporny.
-
Create an example showing both `recognizedTo` and `recognizedIn` used concurrently. w3c/vc-recognized-entities#52, by @BigBlueHat.
-
Use Cases and Applications for this data model w3c/vc-recognized-entities#51, by @BigBlueHat.
-
-
1 issue closed.
-
Add 'List of Known/KYC'd Entities' use case w3c/vc-recognized-entities#38.
-
-
8 issues received 17 new comments.
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46 (4 comments by @BigBlueHat, @msporny, @TallTed)
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50 (4 comments by @BigBlueHat, @dlongley, @msporny, @swcurran)
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49 (4 comments by @BigBlueHat, @msporny, @swcurran)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (1 comment by @msporny)
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44 (1 comment by @BigBlueHat)
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43 (1 comment by @BigBlueHat)
-
-
9 pull requests opened.
-
Add Relationship to Other Technologies section. w3c/vc-recognized-entities#62, by @msporny.
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61, by @msporny.
-
Comment out `publishDate`. w3c/vc-recognized-entities#60, by @BigBlueHat.
-
Set publication date to 2026-03-20. w3c/vc-recognized-entities#59, by @BigBlueHat.
-
Rename the specification to be more accurate. w3c/vc-recognized-entities#58, by @msporny.
-
Add CG Report; configure respec to match future. w3c/vc-recognized-entities#57, by @BigBlueHat.
-
Add section on validating before sharing. w3c/vc-recognized-entities#55, by @msporny.
-
Update introduction to better align with updated specification. w3c/vc-recognized-entities#54, by @msporny.
-
Update the abstract to better align with the updated spec. w3c/vc-recognized-entities#53, by @msporny.
-
-
7 pull requests merged.
-
Comment out `publishDate`. w3c/vc-recognized-entities#60.
-
Set publication date to 2026-03-20. w3c/vc-recognized-entities#59.
-
Add CG Report; configure respec to match future. w3c/vc-recognized-entities#57.
-
Rename the specification to be more accurate. w3c/vc-recognized-entities#58.
-
Update introduction to better align with updated specification. w3c/vc-recognized-entities#54.
-
Add section on validating before sharing. w3c/vc-recognized-entities#55.
-
Update the abstract to better align with the updated spec. w3c/vc-recognized-entities#53.
-
-
1 pull request closed.
-
Use Cases Updates w3c/vc-recognized-entities#39.
-
-
7 pull requests received 29 new comments.
-
Add Relationship to Other Technologies section. w3c/vc-recognized-entities#62 (14 comments by @TallTed)
-
Update introduction to better align with updated specification. w3c/vc-recognized-entities#54 (5 comments by @msporny, @TallTed)
-
Add broad topics for privacy and security considerations. w3c/vc-recognized-entities#61 (4 comments by @dlongley, @msporny)
-
Update the abstract to better align with the updated spec. w3c/vc-recognized-entities#53 (2 comments by @TallTed)
-
Rename the specification to be more accurate. w3c/vc-recognized-entities#58 (2 comments by @dlongley, @msporny)
-
w3c/vc-data-integrity
-
1 issue opened.
-
Add mandatory checking of digestMultibase if resource is "made use of" w3c/vc-data-integrity#346, by @msporny.
-
w3c/cid
-
5 issues opened.
-
canonical mapping of the multibase datatype is ill-defined w3c/cid#167, by @pchampin.
-
checksum of vocabulary do not match w3c/cid#166, by @pchampin.
-
Base identifier including a fragment w3c/cid#164, by @pchampin.
-
Clarification about canonical URL dereferencing w3c/cid#163, by @pchampin.
-
-
3 issues received 13 new comments.
-
Base identifier including a fragment w3c/cid#164 (11 comments by @iherman, @kaefer3000, @mwherman2000, @pchampin, @TallTed)
-
w3c/vc-data-model
-
1 issue opened.
-
Clean up identifier definition w3c/vc-data-model#1624, by @jandrieu.
-
-
2 issues closed.
-
Example of Use of renderMethod w3c/vc-data-model#1480.
-
-
5 issues received 10 new comments.
-
Managing Verifiable Presentations with Mixed W3C Verifiable Credentials Data Models (1.1 and 2.0) w3c/vc-data-model#1621 (5 comments by @dlongley, @KiruthikaJeyashankar, @msporny)
-
-
3 pull requests opened.
-
Update URL definition to clarify dereferencing w3c/vc-data-model#1625, by @jandrieu.
-
Remove guidance around bundling dependent claims. w3c/vc-data-model#1623, by @msporny.
-
Clarify that SD-JWT-VC is incompatible with W3C VCs. w3c/vc-data-model#1622, by @msporny.
-
-
1 pull request merged.
-
Add reference to confidence method and render method w3c/vc-data-model#1620.
-
-
2 pull requests received 2 new comments.
w3c/vc-use-cases
-
1 issue received 1 new comment.
-
Pull request preview images are missing (links are broken) w3c/vc-use-cases#170 (1 comment by @rjpadula)
-
-
1 pull request opened.
-
2026-03-Editorial w3c/vc-use-cases#171, by @KDean-Dolphin.
-
-
1 pull request merged.
-
2026-03-Editorial w3c/vc-use-cases#171.
-
w3c/vc-imp-guide
-
1 issue opened.
-
Create full working examples of JSON-LD resolution to standard OOP language formats w3c/vc-imp-guide#74, by @andrew-mitt-docu.
-
Past meetings
Participants
-
3 participants joined.
-
Beatriz Rocha (NIC.br - Brazilian Network Information Center) joined.
-
Jonathan Prisby (Department of Homeland Security) joined.
-
Isaac Koh (W3C Invited Experts) joined.
-
-
1 participant left.
-
Anil John (Department of Homeland Security) left.
-
-
2 organizations joined.
-
Stony Brook University joined.
-
NIC.br - Brazilian Network Information Center joined.
-
-
1 organization left.
-
Government Technology Agency left.
-
GitHub
w3c/vc-recognized-entities
-
8 issues opened.
-
Create example demonstrating holder-based delivery of a `VerifiableRecognitionCredential` w3c/vc-recognized-entities#50, by @msporny.
-
Ensure that a `VerifiableRecognitionCredential` be published through a DID `/whois` endpoint w3c/vc-recognized-entities#49, by @msporny.
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48, by @msporny.
-
Potentially multi-valued attributes need more explicit definitions w3c/vc-recognized-entities#46, by @TallTed.
-
Extract use cases into separate document. w3c/vc-recognized-entities#45, by @BigBlueHat.
-
Is it `the value MUST be a URL`, or `URL or image data`? w3c/vc-recognized-entities#44, by @TallTed.
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43, by @filip26.
-
Explain that `outputValidation` requires governance w3c/vc-recognized-entities#41, by @msporny.
-
-
12 issues closed.
-
Extract use cases into separate document. w3c/vc-recognized-entities#45.
-
Naming convention is not aligned with other vocabularies w3c/vc-recognized-entities#36.
-
Data model conflates list operators with lists w3c/vc-recognized-entities#35.
-
should `Attributes of List Operator` be an alphanumerically ordered list of `dfn`? w3c/vc-recognized-entities#26.
-
Size of the lists. w3c/vc-recognized-entities#5.
-
Consider hierarchical/chained lists w3c/vc-recognized-entities#1.
-
Add fully decentralized verifiable issuer use case w3c/vc-recognized-entities#37.
-
Provide minimal viable examples w3c/vc-recognized-entities#34.
-
Demonstrate usage of data model in a VC w3c/vc-recognized-entities#33.
-
Role-based grants are too coarse w3c/vc-recognized-entities#32.
-
Shift language to align more with accreditation rather than valid claims w3c/vc-recognized-entities#31.
-
About wallet issuer / verifier verification w3c/vc-recognized-entities#7.
-
-
1 issue reopened.
-
Change document title w3c/vc-recognized-entities#30, by @msporny.
-
-
18 issues received 35 new comments.
-
Comic-style images are misleading and inappropriate for a spec w3c/vc-recognized-entities#43 (4 comments by @BigBlueHat, @msporny, @TallTed)
-
Extract use cases into separate document. w3c/vc-recognized-entities#45 (3 comments by @msporny, @TallTed)
-
Data model conflates list operators with lists w3c/vc-recognized-entities#35 (3 comments by @BigBlueHat, @msporny, @TallTed)
-
Consider hierarchical/chained lists w3c/vc-recognized-entities#1 (3 comments by @BigBlueHat, @msporny)
-
Naming convention is not aligned with other vocabularies w3c/vc-recognized-entities#36 (2 comments by @BigBlueHat, @msporny)
-
should `Attributes of List Operator` be an alphanumerically ordered list of `dfn`? w3c/vc-recognized-entities#26 (2 comments by @BigBlueHat, @msporny)
-
About wallet issuer / verifier verification w3c/vc-recognized-entities#7 (2 comments by @dlongley, @patatoid)
-
Ensure compatibility with UNTP Digital Identity Anchor work w3c/vc-recognized-entities#48 (1 comment by @msporny)
-
Add fully decentralized verifiable issuer use case w3c/vc-recognized-entities#37 (1 comment by @msporny)
-
Shift language to align more with accreditation rather than valid claims w3c/vc-recognized-entities#31 (1 comment by @msporny)
-
Outline considerations that are out of scope w3c/vc-recognized-entities#4 (1 comment by @BigBlueHat)
-
2 pull requests opened.
-
Separate use cases and requirements from main specification. w3c/vc-recognized-entities#47, by @msporny.
-
Add EU ETSI Trust Services support to data model w3c/vc-recognized-entities#42, by @msporny.
-
-
3 pull requests merged.
-
Separate use cases and requirements from main specification. w3c/vc-recognized-entities#47.
-
Add EU ETSI Trust Services support to data model w3c/vc-recognized-entities#42.
-
Add VerifibleRecognitionCredential section to Data Model. w3c/vc-recognized-entities#40.
-
-
1 pull request closed.
-
Add first cut at verifiable accreditation section. w3c/vc-recognized-entities#29.
-
-
4 pull requests received 65 new comments.
-
Separate use cases and requirements from main specification. w3c/vc-recognized-entities#47 (31 comments by @dlongley, @msporny, @TallTed)
-
Add EU ETSI Trust Services support to data model w3c/vc-recognized-entities#42 (25 comments by @dlongley, @msporny, @TallTed)
-
Add VerifibleRecognitionCredential section to Data Model. w3c/vc-recognized-entities#40 (6 comments by @BigBlueHat, @David-Chadwick, @msporny)
-
Add first cut at verifiable accreditation section. w3c/vc-recognized-entities#29 (3 comments by @BigBlueHat, @msporny, @TallTed)
-
w3c/vc-confidence-method
-
4 issues opened.
-
Invocation section: Should “previousCapability” be “parentCapability”? w3c/vc-confidence-method#28, by @nobby-e.
-
Adaptive Hierarchical Classification with Multi-Dimensional Decay and Privacy-Preserving Risk Federation w3c/vc-confidence-method#27, by @amir-hameed-mir.
-
Start a Threat Model w3c/vc-confidence-method#26, by @jandrieu.
-
Add section on Holder Binding w3c/vc-confidence-method#25, by @jandrieu.
-
-
1 issue closed.
-
Invocation section: Should “previousCapability” be “parentCapability”? w3c/vc-confidence-method#28.
-
-
5 issues received 14 new comments.
-
Add section on Holder Binding w3c/vc-confidence-method#25 (5 comments by @denkeni, @jandrieu, @TallTed)
-
Start a Threat Model w3c/vc-confidence-method#26 (5 comments by @amir-hameed-mir, @ewoogit, @hychen, @msporny)
-
Adaptive Hierarchical Classification with Multi-Dimensional Decay and Privacy-Preserving Risk Federation w3c/vc-confidence-method#27 (2 comments by @amir-hameed-mir, @jandrieu)
-
Invocation section: Should “previousCapability” be “parentCapability”? w3c/vc-confidence-method#28 (1 comment by @nobby-e)
-
w3c/vcalm
-
9 issues opened.
-
Consider defining normative/non-normative workflow processing algorithm w3c/vcalm#596, by @dlongley.
-
Document `indexAllocator` in more detail w3c/vcalm#594, by @msporny.
-
DELETE /presentations/{id} missing section in the specification w3c/vcalm#588, by @eric-schuh.
-
Should /callbacks/{localCallbackId} have expected callers? w3c/vcalm#587, by @eric-schuh.
-
Remove `Exchange Discovery` section w3c/vcalm#586, by @eric-schuh.
-
Annotate example workflows in appendix w3c/vcalm#585, by @eric-schuh.
-
7 issues closed.
-
Add links to endpoint definitions in the component tables w3c/vcalm#560.
-
Should /callbacks/{localCallbackId} have expected callers? w3c/vcalm#587.
-
Remove `Exchange Discovery` section w3c/vcalm#586.
-
Should this API define how to host revocation lists? w3c/vcalm#232.
-
Discuss `acceptedIssuers` property naming and behavior w3c/vcalm#582.
-
14 issues received 19 new comments.
-
Should /callbacks/{localCallbackId} have expected callers? w3c/vcalm#587 (3 comments by @dlongley, @eric-schuh, @TallTed)
-
Discuss `acceptedIssuers` property naming and behavior w3c/vcalm#582 (2 comments by @bparth24, @dlongley)
-
Consider defining normative/non-normative workflow processing algorithm w3c/vcalm#596 (1 comment by @TallTed)
-
Add workflow step property to indicate whether a domain should be included w3c/vcalm#460 (1 comment by @PatStLouis)
-
DELETE /presentations/{id} missing section in the specification w3c/vcalm#588 (1 comment by @PatStLouis)
-
Add `redirectUrl` to step options to specify a `redirectUrl` to send to the client w3c/vcalm#590 (1 comment by @PatStLouis)
-
Add optional `result` property to issue request element in `issueRequests` w3c/vcalm#583 (1 comment by @dlongley)
-
Add `acceptedEnvelopes` and `acceptedCryptosuites` examples for `QueryByExample` w3c/vcalm#542 (1 comment by @bparth24)
-
-
7 pull requests opened.
-
Fix DELETE /presentations/{id} component table link w3c/vcalm#597, by @eric-schuh.
-
Add delete presentation by id endpoint section. w3c/vcalm#595, by @bparth24.
-
Add JSON Schema for QueryByExample w3c/vcalm#593, by @msporny.
-
Delete old exchange discovery endpoint w3c/vcalm#592, by @eric-schuh.
-
Add /callbacks/{localCallbackId} to component tables w3c/vcalm#591, by @eric-schuh.
-
Add client-initiated VPR examples to Exchange Examples section. w3c/vcalm#589, by @bparth24.
-
Add links to component tables w3c/vcalm#584, by @eric-schuh.
-
-
9 pull requests merged.
-
Fix DELETE /presentations/{id} component table link w3c/vcalm#597.
-
Add links to component tables w3c/vcalm#584.
-
Add delete presentation by id endpoint section. w3c/vcalm#595.
-
Add /callbacks/{localCallbackId} to component tables w3c/vcalm#591.
-
Delete old exchange discovery endpoint w3c/vcalm#592.
-
OpenID client profile exchange configuration w3c/vcalm#581.
-
Add non normative section about managing status list w3c/vcalm#573.
-
-
8 pull requests received 58 new comments.
-
Add non normative section about managing status list w3c/vcalm#573 (11 comments by @dlongley, @PatStLouis, @TallTed)
-
Add client-initiated VPR examples to Exchange Examples section. w3c/vcalm#589 (4 comments by @bparth24, @dlongley)
w3c/vc-data-model
-
2 issues opened.
-
Schema lacking `format` field w3c/vc-data-model#1619, by @Oran-Dan.
-
7 issues received 12 new comments.
-
Managing Verifiable Presentations with Mixed W3C Verifiable Credentials Data Models (1.1 and 2.0) w3c/vc-data-model#1621 (2 comments by @dlongley, @KiruthikaJeyashankar)
-
1 pull request opened.
-
Add reference to confidence method and render method w3c/vc-data-model#1620, by @ewoogit.
-
-
1 pull request received 3 new comments.
-
Add reference to confidence method and render method w3c/vc-data-model#1620 (3 comments by @iherman, @TallTed)
-
w3c/vc-data-integrity
-
1 issue opened.
-
Latest published version is 404. w3c/vc-data-integrity#345, by @BigBlueHat.
-
w3c/vc-use-cases
-
1 issue opened.
-
Pull request preview images are missing (links are broken) w3c/vc-use-cases#170, by @rjpadula.
-
-
3 issues closed.
-
Exchange of Electronic Certificate of Origin to facilitate Cross Border Trade w3c/vc-use-cases#157.
-
Update toolchain to use latest validator w3c/vc-use-cases#168.
-
Change Kevin Dean's representation in the repository w3c/vc-use-cases#169.
-
-
4 issues received 15 new comments.
-
Pull request preview images are missing (links are broken) w3c/vc-use-cases#170 (12 comments by @iherman, @jandrieu, @rjpadula, @tobie)
-
Exchange of Electronic Certificate of Origin to facilitate Cross Border Trade w3c/vc-use-cases#157 (1 comment by @jandrieu)
-
-
1 pull request merged.
-
Added Exchange of Electronic Certificate of Origin focal use case w3c/vc-use-cases#167.
-
-
1 pull request received 2 new comments.
-
Added Exchange of Electronic Certificate of Origin focal use case w3c/vc-use-cases#167 (2 comments by @jandrieu, @KDean-Dolphin)
-
w3c/vc-render-method
-
2 issues opened.
-
We should note that, in general, all fetches SHOULD be performed over OHTTP or similar w3c/vc-render-method#47, by @BigBlueHat.
-
Bookmarking some a11y related references.... w3c/vc-render-method#45, by @iherman.
-
-
2 issues received 4 new comments.
-
Bookmarking some a11y related references.... w3c/vc-render-method#45 (2 comments by @iherman, @TallTed)
-
❓ Clarification: Handling multiple renderMethod entries from multiple issuers w3c/vc-render-method#43 (2 comments by @aamirmir001, @dlongley)
-
-
2 pull requests opened.
-
Add devcontainer.json for preview in codespaces. w3c/vc-render-method#46, by @BigBlueHat.
-
Clarify that `template` may be a `data:` URL. w3c/vc-render-method#44, by @BigBlueHat.
-
-
3 pull requests merged.
-
First draft of HTML Render Method. w3c/vc-render-method#42.
-
Add devcontainer.json for preview in codespaces. w3c/vc-render-method#46.
-
Clarify that `template` may be a `data:` URL. w3c/vc-render-method#44.
-
-
4 pull requests received 45 new comments.
-
First draft of HTML Render Method. w3c/vc-render-method#42 (41 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @iherman, @msporny, @simoneonofri, @TallTed)
-
Refer to mustache templating algorithm instead of reproducing a partial w3c/vc-render-method#41 (2 comments by @dmitrizagidulin, @Echsecutor)
-
Add devcontainer.json for preview in codespaces. w3c/vc-render-method#46 (1 comment by @dmitrizagidulin)
-
w3c/vc-test-suite-implementations
-
2 issues received 2 new comments.
-
1 pull request received 1 new comment.
w3c/vc-di-quantum-resistant
-
1 issue received 1 new comment.
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9 (1 comment by @Wind4Greg)
-
-
1 pull request opened.
-
Update/Refactor Common Algorithms, ML-DSA, SLH-DSA, Outline Test Vector sections w3c/vc-di-quantum-resistant#10, by @Wind4Greg.
-
-
1 pull request received 48 new comments.
-
Update/Refactor Common Algorithms, ML-DSA, SLH-DSA, Outline Test Vector sections w3c/vc-di-quantum-resistant#10 (48 comments by @dlongley, @TallTed, @Wind4Greg)
-
w3c/vc-json-schema
-
1 issue received 1 new comment.
-
Example of JsonSchemaCredential v2 has incorrect digestSRI w3c/vc-json-schema#257 (1 comment by @genaris)
-
w3c/vc-di-bbs
-
1 pull request opened.
-
Editorial: Fix href for Blind BBS Signatures w3c/vc-di-bbs#205, by @plehegar.
-
w3c/vc-bitstring-status-list
-
1 issue received 1 new comment.
-
Clarify bit-to-byte ordering in bitstring serialization w3c/vc-bitstring-status-list#211 (1 comment by @oriolcanades)
-
Past meetings
Participants
-
3 participants joined.
-
Amir Hameed Mir (W3C Invited Experts) joined.
-
Michael Animashaun (HM Government) joined.
-
Ramprasad Gaddam (UnitedHealth Group) joined.
-
-
2 organizations joined.
-
HM Government joined.
-
UnitedHealth Group joined.
-
GitHub
w3c/vc-render-method
-
2 issues opened.
-
❓ Clarification: Handling multiple renderMethod entries from multiple issuers w3c/vc-render-method#43, by @amir-hameed-mir.
-
Mustache Template Rendering Algorithm w3c/vc-render-method#40, by @Echsecutor.
-
-
7 issues received 11 new comments.
-
publish context file for renderMethod w3c/vc-render-method#16 (2 comments by @dlongley, @Echsecutor)
-
Create a data model level distinction between templated and untemplated render methods. w3c/vc-render-method#37 (1 comment by @msporny)
-
2 pull requests opened.
-
First draft of HTML Render Method. w3c/vc-render-method#42, by @BigBlueHat.
-
Refer to mustache templating algorithm instead of reproducing a partial w3c/vc-render-method#41, by @Echsecutor.
-
-
3 pull requests received 27 new comments.
-
First draft of HTML Render Method. w3c/vc-render-method#42 (22 comments by @BigBlueHat, @dlongley, @dmitrizagidulin, @msporny)
-
Render method to enable card-like displays in wallets and displayers w3c/vc-render-method#39 (3 comments by @dlongley, @msporny)
-
Refer to mustache templating algorithm instead of reproducing a partial w3c/vc-render-method#41 (2 comments by @dmitrizagidulin, @TallTed)
-
w3c/vc-bitstring-status-list
-
1 issue opened.
-
Clarify bit-to-byte ordering in bitstring serialization w3c/vc-bitstring-status-list#211, by @oriolcanades.
-
-
1 issue received 2 new comments.
-
Clarify bit-to-byte ordering in bitstring serialization w3c/vc-bitstring-status-list#211 (2 comments by @dlongley)
-
w3c/vcalm
-
4 issues opened.
-
Discuss `acceptedIssuers` property naming and behavior w3c/vcalm#582, by @bparth24.
-
Interaction scheme registration w3c/vcalm#579, by @PatStLouis.
-
Expressing predicates in presentation request w3c/vcalm#578, by @PatStLouis.
-
-
2 issues received 5 new comments.
-
4 pull requests opened.
-
OpenID client profile exchange configuration w3c/vcalm#581, by @kezike.
-
Add new appendix for minimum and other workflow examples w3c/vcalm#577, by @eric-schuh.
-
Add section about interaction schemes w3c/vcalm#576, by @msporny.
-
-
2 pull requests merged.
-
Add new appendix for minimum and other workflow examples w3c/vcalm#577.
-
Add section about interaction schemes w3c/vcalm#576.
-
-
5 pull requests received 50 new comments.
-
Add acceptedCryptosuites and acceptedEnvelopes examples for QueryByExample w3c/vcalm#580 (33 comments by @bparth24, @dlongley, @PatStLouis, @TallTed)
-
Add non normative section about managing status list w3c/vcalm#573 (6 comments by @dlongley, @msporny)
-
w3c/vc-test-suite-implementations
-
5 issues opened.
-
Trinsic endpoints are timing out w3c/vc-test-suite-implementations#120, by @BigBlueHat.
-
Mavennet endpoints are 404 w3c/vc-test-suite-implementations#119, by @BigBlueHat.
-
Gen Digital endpoint is ENOTFOUND w3c/vc-test-suite-implementations#118, by @BigBlueHat.
-
Procivis One Core is 404 w3c/vc-test-suite-implementations#117, by @BigBlueHat.
-
Aviary Tech endpoints are 404 w3c/vc-test-suite-implementations#116, by @BigBlueHat.
-
-
1 issue received 2 new comments.
-
Gen Digital endpoint is ENOTFOUND w3c/vc-test-suite-implementations#118 (2 comments by @BigBlueHat, @skynet2)
-
-
1 pull request opened.
-
Remove Aviary Tech implementation w3c/vc-test-suite-implementations#121, by @brianorwhatever.
-
-
1 pull request merged.
-
Remove Aviary Tech implementation w3c/vc-test-suite-implementations#121.
-
-
2 pull requests received 4 new comments.
-
Add TrustVC to implementations w3c/vc-test-suite-implementations#115 (3 comments by @BigBlueHat, @RishabhS7)
-
w3c/vc-di-quantum-resistant
-
1 issue opened.
-
Updating Draft: Refactoring, MultiKeys/Proofs, and Test Vectors w3c/vc-di-quantum-resistant#9, by @Wind4Greg.
-
w3c/vc-use-cases
-
2 issues opened.
-
Change Kevin Dean's representation in the repository w3c/vc-use-cases#169, by @ghost.
-
Update toolchain to use latest validator w3c/vc-use-cases#168, by @ghost.
-
-
2 issues received 8 new comments.
-
Update toolchain to use latest validator w3c/vc-use-cases#168 (7 comments by @deniak, @iherman, @jandrieu)
-
-
1 pull request received 1 new comment.
-
Added Exchange of Electronic Certificate of Origin focal use case w3c/vc-use-cases#167 (1 comment by @ghost)
-
w3c/vc-confidence-method
-
1 issue opened.
-
Seek Accessibility input w3c/vc-confidence-method#24, by @jandrieu.
-
-
7 issues received 12 new comments.
-
Address privacy concerns of using biometrics w3c/vc-confidence-method#21 (3 comments by @denkeni, @jandrieu)
-
Adding more confidence method types based on Multi-Factor Authentication w3c/vc-confidence-method#17 (2 comments by @denkeni, @msporny)
w3c/vc-data-integrity
-
1 issue opened.
-
Move General Selective Disclosure Functions from VC-DI-ECDSA to VC-Data-Integrity w3c/vc-data-integrity#344, by @Wind4Greg.
-
-
1 pull request closed.
-
Appendix on Proof Sets/Chains: Clarity improvements w3c/vc-data-integrity#335.
-
-
1 pull request received 1 new comment.
-
Appendix on Proof Sets/Chains: Clarity improvements w3c/vc-data-integrity#335 (1 comment by @TallTed)
-
w3c/vc-recognized-entities
-
1 pull request opened.
-
Add VerifibleRecognitionCredential section to Data Model. w3c/vc-recognized-entities#40, by @msporny.
-
-
1 pull request received 8 new comments.
-
Add VerifibleRecognitionCredential section to Data Model. w3c/vc-recognized-entities#40 (8 comments by @David-Chadwick, @dlongley, @msporny, @TallTed)
-
w3c/vc-json-schema
-
1 issue opened.
-
Example of JsonSchemaCredential v2 has incorrect digestSRI w3c/vc-json-schema#257, by @lotharking.
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
fix abstract link w3c/vc-di-ed25519signature2020-test-suite#60, by @BigBlueHat.
-
w3c/vc-data-model
-
1 issue opened.
-
Typos, Chapter 3.1 VC Data Model w3c/vc-data-model#1618, by @RenatoasMedeiros.
-
-
1 issue closed.
-
Typos, Chapter 3.1 VC Data Model w3c/vc-data-model#1618.
-
-
1 issue received 1 new comment.
w3c/vc-di-eddsa-test-suite
-
1 pull request opened.
-
Set all column labels to Issuer. w3c/vc-di-eddsa-test-suite#68, by @BigBlueHat.
-
-
1 pull request merged.
-
Set all column labels to Issuer. w3c/vc-di-eddsa-test-suite#68.
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request opened.
-
Set column labels; comment on interop test labels. w3c/vc-bitstring-status-list-test-suite#70, by @BigBlueHat.
-
-
1 pull request merged.
-
Set column labels; comment on interop test labels. w3c/vc-bitstring-status-list-test-suite#70.
-
w3c/vc-data-model-2.0-test-suite
-
1 pull request opened.
-
Add column labels where possible. w3c/vc-data-model-2.0-test-suite#165, by @BigBlueHat.
-
-
1 pull request merged.
-
Add column labels where possible. w3c/vc-data-model-2.0-test-suite#165.
-
w3c/vc-di-ecdsa-test-suite
-
1 pull request opened.
-
Add missing column labels. w3c/vc-di-ecdsa-test-suite#120, by @BigBlueHat.
-
-
1 pull request merged.
-
Add missing column labels. w3c/vc-di-ecdsa-test-suite#120.
-
w3c/vc-imp-guide
-
1 pull request closed.
-
Improve grammar for clarity in Update terms.html w3c/vc-imp-guide#73.
-