Verifiable Credentials Working Group - Activity
No matches.
VC Render Method
Participants
-
1 participant joined the VC Render Method.
-
Patrick St-Louis joined.
-
GitHub
w3c/vc-render-method
-
8 issues opened in the VC Render Method.
-
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.
-
-
9 issues closed in the VC Render Method.
-
(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.
-
-
17 issues in the VC Render Method received 23 new comments.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93 (3 comments by @aphillips, @iherman)
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96 (2 comments by @iherman, @msporny)
-
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)
-
`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)
-
-
4 pull requests opened in the VC Render Method.
-
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.
-
-
4 pull requests in the VC Render Method received 20 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)
-
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)
-
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
-
5 participants 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/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 57 new comments.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144 (7 comments by @iherman, @msporny)
-
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/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.
-
-
13 issues received 33 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)
-
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)
-
-
7 pull requests opened.
-
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 26 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-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-render-method
-
8 issues opened.
-
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.
-
-
9 issues closed.
-
(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.
-
-
17 issues received 23 new comments.
-
`name` and `descriptions` should be Localizables w3c/vc-render-method#93 (3 comments by @aphillips, @iherman)
-
`validFrom` and `validUntil` might be underspecified w3c/vc-render-method#96 (2 comments by @iherman, @msporny)
-
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)
-
`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)
-
-
4 pull requests opened.
-
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.
-
-
4 pull requests received 20 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)
-
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-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 Recognized Entities
Past meetings
-
2 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 57 new comments.
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144 (7 comments by @iherman, @msporny)
-
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
-
2 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.
-
-
13 issues in the VC API for Lifecycle Management received 33 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)
-
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)
-
-
7 pull requests opened in the VC API for Lifecycle Management.
-
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 26 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.
-
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.