VC Recognized Entities - Activity
No matches.
Past meetings
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)
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)
Past meetings
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)
-