VC Recognized Entities - Activity
No matches.
GitHub
w3c/vc-recognized-entities
-
1 pull request merged.
-
Draft vocabulary definition w3c/vc-recognized-entities#122.
-
-
1 pull request received 5 new comments.
Past meetings
Participants
-
1 participant left.
-
Sin Yong Loh left.
-
GitHub
w3c/vc-recognized-entities
-
3 issues opened.
-
Can we add a name to recognizedAction w3c/vc-recognized-entities#145, by @paulfdietrich.
-
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.
-
-
5 issues closed.
-
Internationalization Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#98.
-
Can we add a name to recognizedAction w3c/vc-recognized-entities#145.
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140.
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131.
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130.
-
-
12 issues received 48 new comments.
-
Add support for FieldMatch (transitive output validations) w3c/vc-recognized-entities#121 (20 comments by @dlongley, @msporny, @onthebreeze, @paulfdietrich, @philarcher)
-
revisit the data model w3c/vc-recognized-entities#135 (8 comments by @dlongley, @msporny, @onthebreeze, @philarcher)
-
back to basics - what is recognized-entity for? w3c/vc-recognized-entities#140 (7 comments by @iherman, @msporny, @onthebreeze)
-
Global Quality Infrastructure use case for Recognized Entities w3c/vc-recognized-entities#139 (5 comments by @msporny, @philarcher)
-
Internationalization Self-Review Questionnaire for VC Recognized Entities v1.0 w3c/vc-recognized-entities#98 (1 comment by @msporny)
-
Create Vocabulary and JSON-LD Context for recognized entities credential w3c/vc-recognized-entities#73 (1 comment by @msporny)
-
add the registered / recognised entity ID to the Data model w3c/vc-recognized-entities#132 (1 comment by @msporny)
-
recommendations for distributing recognized entities credentials to avoid privacy leakage? w3c/vc-recognized-entities#131 (1 comment by @msporny)
-
threat model is not a sufficient replacement for privacy considerations and security considerations w3c/vc-recognized-entities#130 (1 comment by @msporny)
-
-
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.
-
-
5 pull requests merged.
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142.
-
Add SSRF threat and mitigation. w3c/vc-recognized-entities#137.
-
Add maxDuration to limit DoS attacks. w3c/vc-recognized-entities#136.
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134.
-
Specify how to properly use digestMultibase. w3c/vc-recognized-entities#133.
-
-
1 pull request closed.
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108.
-
-
11 pull requests received 74 new comments.
-
Add `registration` property. Update UNTP example to use it. w3c/vc-recognized-entities#142 (14 comments by @dlongley, @msporny, @onthebreeze, @TallTed)
-
Issue #121 update output validation with jsonata w3c/vc-recognized-entities#144 (10 comments by @iherman, @msporny, @paulfdietrich, @TallTed)
-
Add currentDateTime during validity window check. w3c/vc-recognized-entities#134 (3 comments by @msporny, @simoneonofri)
-
added a >CE Marking Product Conformity Example< in appendix D w3c/vc-recognized-entities#141 (3 comments by @msporny, @ngwlf, @TallTed)
-
Aligning the GS1 appendix w3c/vc-recognized-entities#108 (3 comments by @msporny, @paulfdietrich, @philarcher)
-
Ensure intermediate authority is asserted. w3c/vc-recognized-entities#138 (2 comments by @iherman, @TallTed)
Past meetings
Participants
-
2 participants joined.
-
Nate Otto joined.
-
James Richards joined.
-
GitHub
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)