Verifiable Credentials Working Group - Activity in 2022
No matches.
TR publications
-
3 documents published.
-
Verifiable Credentials Data Model v2.0 published twice as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
JSON Web Signature 2020 published as a First Public Working Draft. History of JSON Web Signature 2020
-
Past meetings
Participants
-
1 participant joined.
-
Brian Campbell (Ping Identity) joined.
-
GitHub
w3c/vcalm
-
1 issue closed.
-
5 issues received 10 new comments.
-
credentialId in updateCredentialStatus may not fit all use cases w3c/vcalm#126 (6 comments by @brownoxford, @dlongley, @msporny, @nissimsan)
-
BbsBls sig test fixtures (valid by various W3C docs) not permitted by current OpenAPI spec w3c/vcalm#194 (1 comment by @msporny)
-
-
1 pull request opened.
-
Reference error schema on error endpoints w3c/vcalm#326, by @ottonomy.
-
-
1 pull request received 1 new comment.
w3c/vc-jws-2020
-
2 pull requests opened.
-
Setting up echidna w3c/vc-jws-2020#29, by @iherman.
-
1 pull request merged.
-
Setting up echidna w3c/vc-jws-2020#29.
-
-
1 pull request closed.
-
Add IANA to context w3c/vc-jws-2020#24.
-
-
2 pull requests received 2 new comments.
w3c/vc-data-integrity
-
3 issues opened.
-
Domain and range of sec:publicKey w3c/vc-data-integrity#74, by @csarven.
-
domain of publicKeyJWK should be rdf:JSON w3c/vc-data-integrity#73, by @bblfish.
-
Is the sec entry in vocab/security/vocabulary.jsonld and vocab/security/vocabulary.ttl wrong? w3c/vc-data-integrity#72, by @Daniel-Abrecht.
-
-
1 issue received 2 new comments.
w3c/vc-data-model
-
8 issues opened.
-
Change vocabulary base URL for v2 context w3c/vc-data-model#1002, by @OR13.
-
Automate generation of JSON-LD Context, Vocabulary, JSON Schema w3c/vc-data-model#998, by @msporny.
-
Add spec text around utilizing JSON Schemas for VCDM objects w3c/vc-data-model#997, by @thereisnogabe.
-
Question about verifiable presentations w3c/vc-data-model#996, by @RieksJ.
-
[Terminology] claim w3c/vc-data-model#995, by @RieksJ.
-
Clarify credentialStatus w3c/vc-data-model#991, by @David-Chadwick.
-
issuer IRI should be anchored to term definition, page should scroll to definition w3c/vc-data-model#990, by @BenjaminMoe.
-
Section 3.2 Credentials makes confusing statements about what a "credential" is w3c/vc-data-model#989, by @mwherman2000.
-
-
8 issues closed.
-
issue in the example EXAMPLE 4: Usage of the id property w3c/vc-data-model#903.
-
Explain relationship between Presentations and Verifiable Credentials w3c/vc-data-model#910.
-
Make images consistent w3c/vc-data-model#865.
-
More implementation issues w3c/vc-data-model#712.
-
Representing Delegated Credentials in the VCDM w3c/vc-data-model#930.
-
Missing context in an example? w3c/vc-data-model#871.
-
Define JSON Schemas for all objects in the VCDM w3c/vc-data-model#934.
-
-
46 issues received 220 new comments.
-
W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec w3c/vc-data-model#982 (52 comments by @ChristopherA, @David-Chadwick, @mwherman2000, @OR13, @SmithSamuelM, @TallTed)
-
more clarity around the `id` field in the VC data model w3c/vc-data-model#973 (28 comments by @AFlowOfCode, @andrewhughes3000, @bumblefudge, @David-Chadwick, @dlongley, @jandrieu, @mwherman2000, @TallTed)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (17 comments by @agropper, @andrewhughes3000, @bumblefudge, @David-Chadwick, @RieksJ, @TallTed)
-
Redirect the vocabulary to v2 w3c/vc-data-model#966 (12 comments by @dlongley, @iherman, @kdenhartog, @msporny, @OR13, @selfissued)
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988 (12 comments by @bumblefudge, @dlongley, @jandrieu, @nadalin, @TallTed, @vongohren)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (9 comments by @awoie, @dlongley, @jandrieu, @mwherman2000, @OR13, @paulbastian, @RieksJ)
-
Update termsOfUse in context and remove note about bug w3c/vc-data-model#810 (7 comments by @iherman, @OR13, @TallTed)
-
Adopt and publish StatusList2021 as an `credentialStatus` extension w3c/vc-data-model#974 (7 comments by @brentzundel, @David-Chadwick, @iherman, @msporny)
-
Section 3.2 Credentials makes confusing statements about what a "credential" is w3c/vc-data-model#989 (6 comments by @David-Chadwick, @mwherman2000, @RieksJ, @TallTed)
-
Make the usage of `@context` optional w3c/vc-data-model#947 (5 comments by @dlongley, @jandrieu, @OR13, @TallTed)
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963 (4 comments by @Fak3, @jimschoening1, @mwherman2000)
-
issuer IRI should be anchored to term definition, page should scroll to definition w3c/vc-data-model#990 (4 comments by @iherman, @OR13)
-
Have fields for locale-specific information (names, addresses, etc.) been checked? w3c/vc-data-model#734 (4 comments by @iherman, @msporny, @OR13, @pchampin)
-
Change vocabulary base URL for v2 context w3c/vc-data-model#1002 (3 comments by @mprorock, @msporny, @OR13)
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953 (3 comments by @OR13)
-
Requesting content type for `credential` (without proof). w3c/vc-data-model#978 (3 comments by @brentzundel, @OR13)
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931 (3 comments by @dmitrizagidulin, @iherman, @OR13)
-
Add "credential boilerplates" as examples w3c/vc-data-model#935 (2 comments by @David-Chadwick, @OR13)
-
w3c/vc-data-model#863 (2 comments by @brentzundel)
-
Representing Delegated Credentials in the VCDM w3c/vc-data-model#930 (2 comments by @iherman, @thereisnogabe)
-
ManualRefreshService2018 - what exactly is it? w3c/vc-data-model#981 (2 comments by @msporny, @OR13)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (1 comment by @amiller-ims)
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965 (1 comment by @brentzundel)
-
issue in the example EXAMPLE 4: Usage of the id property w3c/vc-data-model#903 (1 comment by @msporny)
-
Explain relationship between Presentations and Verifiable Credentials w3c/vc-data-model#910 (1 comment by @brentzundel)
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875 (1 comment by @brentzundel)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (1 comment by @iherman)
-
w3c/vc-data-model#862 (1 comment by @msporny)
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913 (1 comment by @msporny)
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932 (1 comment by @theblockstalk)
-
-
6 pull requests opened.
-
Add `@vocab` to v2 context w3c/vc-data-model#1001, by @OR13.
-
Add media type registration request w3c/vc-data-model#1000, by @OR13.
-
Remove ZKP Section w3c/vc-data-model#999, by @OR13.
-
Change reference to URI/IRI to use WHATWG URL specification. w3c/vc-data-model#994, by @msporny.
-
Add normative dependency on VC Data Integrity. w3c/vc-data-model#993, by @msporny.
-
Rename issuanceDate/expirationDate to validFrom/validUntil. w3c/vc-data-model#992, by @msporny.
-
-
2 pull requests merged.
-
Add normative dependency on VC Data Integrity. w3c/vc-data-model#993.
-
Rename issuanceDate/expirationDate to validFrom/validUntil. w3c/vc-data-model#992.
-
-
8 pull requests received 62 new comments.
-
Change reference to URI/IRI to use WHATWG URL specification. w3c/vc-data-model#994 (15 comments by @brentzundel, @csarven, @dlongley, @iherman, @msporny, @OR13)
-
Add nonTransferable property to credentials vocab w3c/vc-data-model#969 (13 comments by @awoie, @David-Chadwick, @iherman, @jandrieu, @matthieubosquet, @mccown, @mprorock, @msporny, @TallTed)
-
Add media type registration request w3c/vc-data-model#1000 (10 comments by @msporny, @OR13, @Sakurann, @TallTed)
-
Rename issuanceDate/expirationDate to validFrom/validUntil. w3c/vc-data-model#992 (8 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add normative dependency on VC Data Integrity. w3c/vc-data-model#993 (2 comments by @iherman, @msporny)
-
w3c/vc-use-cases
-
1 pull request opened.
-
Non-transferable use case w3c/vc-use-cases#127, by @David-Chadwick.
-
-
1 pull request received 2 new comments.
w3c/vc-jose-cose
-
1 issue received 3 new comments.
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (3 comments by @David-Chadwick, @Sebastian-Elfors-IDnow, @selfissued)
-
-
1 pull request reopened.
-
Begin production rule definition w3c/vc-jose-cose#11, by @OR13.
-
-
1 pull request received 1 new comment.
w3c/vc-recognized-entities
-
3 issues opened.
-
Document risk surface of peer sharing w3c/vc-recognized-entities#3, by @msporny.
-
Document danger of first mover advantages w3c/vc-recognized-entities#2, by @msporny.
-
Consider hierarchical/chained lists w3c/vc-recognized-entities#1, by @msporny.
-
w3c/vc-json-schema
-
1 pull request opened.
-
update json schema w3c/vc-json-schema#112, by @thereisnogabe.
-
-
1 pull request merged.
-
update json schema w3c/vc-json-schema#112.
-
w3c/vc-bitstring-status-list
-
1 issue opened.
-
Status of what? w3c/vc-bitstring-status-list#35, by @David-Chadwick.
-
w3c/vc-di-eddsa
-
1 pull request opened.
-
Add Dmitri Zagidulin as editor. w3c/vc-di-eddsa#20, by @dmitrizagidulin.
-
-
4 pull requests merged.
-
Add Dmitri Zagidulin as editor. w3c/vc-di-eddsa#20.
-
Removing as inactive editor w3c/vc-di-eddsa#19.
-
Remove Codeowner w3c/vc-di-eddsa#18.
-
Remove inactive editor w3c/vc-di-eddsa#17.
-
-
1 pull request received 4 new comments.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15 (4 comments by @dlongley, @matthieubosquet, @msporny)
-
TR publications
-
5 documents published.
-
Verifiable Credentials Data Model v2.0 published 4 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Verifiable Credential Data Integrity 1.0 published as a First Public Working Draft. History of Verifiable Credential Data Integrity 1.0
-
Past meetings
-
7 meetings.
Participants
-
5 participants joined.
-
Brian Richter (W3C Invited Experts) joined.
-
Andres Uribe (Block, Inc.) joined.
-
Sten Reijers (Ver.iD) joined.
-
Matthieu Bosquet (Inrupt Inc.) joined.
-
Daniel Hardman (W3C Invited Experts) joined.
-
GitHub
w3c/vc-data-model
-
15 issues opened.
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988, by @ChristopherA.
-
Separation of Cryptographic Verification from Business Process (and Semantic) Validation w3c/vc-data-model#986, by @ChristopherA.
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985, by @selfissued.
-
Verifier Role Confusion w3c/vc-data-model#984, by @mwherman2000.
-
Terminology needs to be revised w3c/vc-data-model#983, by @RieksJ.
-
ManualRefreshService2018 - what exactly is it? w3c/vc-data-model#981, by @AFlowOfCode.
-
Error in the JSON schema for `proof` w3c/vc-data-model#980, by @iherman.
-
Resolve discrepancies between specifications, vocabularies, schemas w3c/vc-data-model#979, by @thereisnogabe.
-
Requesting content type for `credential` (without proof). w3c/vc-data-model#978, by @OR13.
-
Move the VC Extension Registry to this Working Group w3c/vc-data-model#975, by @thereisnogabe.
-
Adopt and publish StatusList2021 as an `credentialStatus` extension w3c/vc-data-model#974, by @msporny.
-
more clarity around the `id` field in the VC data model w3c/vc-data-model#973, by @andorsk.
-
Strawman for Increasing Interop w3c/vc-data-model#972, by @David-Chadwick.
-
Securing the VC Data Model with JOSE w3c/vc-data-model#971, by @OR13.
-
-
4 issues closed.
-
Can a credentialSubject be only a string value? w3c/vc-data-model#762.
-
Error in the JSON schema for `proof` w3c/vc-data-model#980.
-
Base context v1 missing `sec:` mapping in RsaSignature2018 "@context" w3c/vc-data-model#778.
-
Definition of issuanceDate property (and its mapping to JWT claims) w3c/vc-data-model#844.
-
-
34 issues received 355 new comments.
-
Make the usage of `@context` optional w3c/vc-data-model#947 (160 comments by @csuwildcat, @danbri, @David-Chadwick, @dhh1128, @dlongley, @gannan08, @gkellogg, @handrews, @iherman, @jandrieu, @mark-moir, @melvincarvalho, @mprorock, @msporny, @nadalin, @OR13, @peacekeeper, @selfissued, @SmithSamuelM, @TallTed, @talltree, @thereisnogabe, @tlodderstedt, @tplooker, @vongohren)
-
more clarity around the `id` field in the VC data model w3c/vc-data-model#973 (19 comments by @aljones15, @andorsk, @bumblefudge, @David-Chadwick, @jandrieu, @melvincarvalho, @mwherman2000, @RieksJ, @TallTed)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (19 comments by @David-Chadwick, @jandrieu, @RieksJ, @TallTed)
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963 (16 comments by @jimschoening1, @OR13, @TallTed)
-
Securing the VC Data Model with JOSE w3c/vc-data-model#971 (13 comments by @David-Chadwick, @letmaik, @mprorock, @msporny, @OR13, @TallTed)
-
Move the VC Extension Registry to this Working Group w3c/vc-data-model#975 (11 comments by @awoie, @msporny, @nadalin, @Sakurann, @selfissued, @TallTed, @thereisnogabe)
-
PresentationSchema for VPs w3c/vc-data-model#839 (10 comments by @awoie, @David-Chadwick, @iherman, @thereisnogabe)
-
Enable CBOR Representation(s) of Verifiable Credentials w3c/vc-data-model#985 (9 comments by @ChristopherA, @David-Chadwick, @dlongley, @mprorock, @mwherman2000, @OR13, @selfissued, @TallTed)
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933 (8 comments by @David-Chadwick, @iherman, @sbutterfield, @thereisnogabe)
-
Strawman for Increasing Interop w3c/vc-data-model#972 (8 comments by @David-Chadwick, @melvincarvalho, @selfissued, @TallTed, @talltree, @thereisnogabe)
-
W3C VC-LD Specification and Layered VC Specification: = interoperability at the application layer of layered spec w3c/vc-data-model#982 (7 comments by @mwherman2000, @SmithSamuelM, @TallTed, @thereisnogabe)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (7 comments by @iherman, @longpd, @mccown, @mprorock, @OR13, @selfissued, @shigeya)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (6 comments by @awoie, @David-Chadwick, @iherman, @msporny, @OR13)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (6 comments by @awoie, @dlongley, @OR13, @TallTed)
-
Create the new role of issuee w3c/vc-data-model#942 (6 comments by @awoie, @David-Chadwick, @SmithSamuelM, @TallTed)
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953 (5 comments by @OR13, @TallTed, @tplooker, @vongohren)
-
Requesting content type for `credential` (without proof). w3c/vc-data-model#978 (5 comments by @letmaik, @mprorock, @OR13)
-
Evidence as a Related Credential w3c/vc-data-model#919 (5 comments by @iherman, @jandrieu, @longpd, @RieksJ, @thereisnogabe)
-
Define JSON Schemas for all objects in the VCDM w3c/vc-data-model#934 (4 comments by @iherman, @sbutterfield, @thereisnogabe)
-
Can a credentialSubject be only a string value? w3c/vc-data-model#762 (3 comments by @awoie, @kdenhartog, @msporny)
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#923 (3 comments by @awoie, @iherman)
-
Proposal: Chaining VCs via links and digests w3c/vc-data-model#952 (3 comments by @dmitrizagidulin, @gobengo, @OR13)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (3 comments by @iherman, @Sakurann, @TallTed)
-
Define policies for directory of related work w3c/vc-data-model#909 (2 comments by @iherman, @mprorock)
-
Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations w3c/vc-data-model#988 (1 comment by @nadalin)
-
Should `validFrom` and `validUntil` change to ISO8601 or Unix Time Stamp, or remain XML Date Time Strings? w3c/vc-data-model#962 (1 comment by @TallTed)
-
Base context v1 missing `sec:` mapping in RsaSignature2018 "@context" w3c/vc-data-model#778 (1 comment by @brentzundel)
-
Definition of issuanceDate property (and its mapping to JWT claims) w3c/vc-data-model#844 (1 comment by @Sakurann)
-
-
4 pull requests opened.
-
Added presentationSchema w3c/vc-data-model#987, by @David-Chadwick.
-
Add JSON Schema for Verifiable Credentials w3c/vc-data-model#977, by @thereisnogabe.
-
credentialSubject's range is an IRI w3c/vc-data-model#976, by @iherman.
-
Forbids credentialSubject objects represented as string values, also fixes #762 w3c/vc-data-model#970, by @awoie.
-
-
4 pull requests merged.
-
credentialSubject's range is an IRI w3c/vc-data-model#976.
-
Forbids credentialSubject objects represented as string values, also fixes #762 w3c/vc-data-model#970.
-
Add JSON Schema for Verifiable Credentials w3c/vc-data-model#977.
-
Upgrade to YAML vocabulary w3c/vc-data-model#968.
-
-
1 pull request closed.
-
IssuanceDate and ExpirationDate w3c/vc-data-model#964.
-
-
7 pull requests received 69 new comments.
-
Add nonTransferable property to credentials vocab w3c/vc-data-model#969 (18 comments by @csarven, @David-Chadwick, @iherman, @jandrieu, @logpo, @matthieubosquet, @msporny, @TallTed)
-
Forbids credentialSubject objects represented as string values, also fixes #762 w3c/vc-data-model#970 (17 comments by @awoie, @David-Chadwick, @iherman, @mprorock, @msporny, @OR13, @TallTed)
-
Add JSON Schema for Verifiable Credentials w3c/vc-data-model#977 (15 comments by @dlongley, @iherman, @msporny, @TallTed, @thereisnogabe)
-
Added presentationSchema w3c/vc-data-model#987 (9 comments by @David-Chadwick, @iherman, @TallTed, @thereisnogabe)
-
IssuanceDate and ExpirationDate w3c/vc-data-model#964 (4 comments by @iherman, @mkhraisha, @msporny)
-
w3c/vc-jose-cose
-
3 issues opened.
-
JWT exp claim w3c/vc-jose-cose#39, by @David-Chadwick.
-
Update language to align with v2 resolutions w3c/vc-jose-cose#38, by @OR13.
-
Address the `alg` language per the comment here w3c/vc-jose-cose#37, by @OR13.
-
-
3 issues received 8 new comments.
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30 (3 comments by @OR13)
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (1 comment by @OR13)
-
1 pull request received 12 new comments.
w3c/vc-jws-2020
-
1 issue opened.
-
Move conformance section w3c/vc-jws-2020#27, by @OR13.
-
-
1 pull request opened.
-
Changed a link for FPWD publication w3c/vc-jws-2020#28, by @iherman.
-
-
2 pull requests merged.
-
Changed a link for FPWD publication w3c/vc-jws-2020#28.
-
Create a First Public Working Draft for Json Web Signature Data Integrity. w3c/vc-jws-2020#26.
-
-
3 pull requests received 17 new comments.
-
Create a First Public Working Draft for Json Web Signature Data Integrity. w3c/vc-jws-2020#26 (12 comments by @iherman, @mprorock, @OR13, @TallTed)
-
w3c/vc-imp-guide
-
1 issue received 4 new comments.
-
Clarification needed regarding "the subject of a VC" w3c/vc-imp-guide#70 (4 comments by @awoie, @David-Chadwick, @RieksJ, @TallTed)
-
w3c/vc-di-eddsa
-
3 pull requests opened.
-
Removing as inactive editor w3c/vc-di-eddsa#19, by @tplooker.
-
Remove Codeowner w3c/vc-di-eddsa#18, by @OR13.
-
Remove inactive editor w3c/vc-di-eddsa#17, by @OR13.
-
-
1 pull request received 2 new comments.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15 (2 comments by @matthieubosquet, @OR13)
-
w3c/vc-data-integrity
-
2 issues opened.
-
Broken link to CAIP-10Account ID Specification w3c/vc-data-integrity#71, by @orblivion.
-
JWS proof least significant bit change w3c/vc-data-integrity#68, by @mkhraisha.
-
-
2 issues received 4 new comments.
-
JWS proof least significant bit change w3c/vc-data-integrity#68 (2 comments by @dlongley, @mkhraisha)
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66 (2 comments by @mprorock, @msporny)
-
-
1 pull request opened.
-
Set up auto-publish.yml w3c/vc-data-integrity#69, by @iherman.
-
-
2 pull requests merged.
-
Set up auto-publish.yml w3c/vc-data-integrity#69.
-
Create a First Public Working Draft for Data Integrity. w3c/vc-data-integrity#67.
-
-
2 pull requests received 4 new comments.
-
Create a First Public Working Draft for Data Integrity. w3c/vc-data-integrity#67 (3 comments by @iherman, @msporny)
-
w3c/vc-bitstring-status-list
-
1 issue opened.
-
Are suppension and revocation mutially exclusive? w3c/vc-bitstring-status-list#33, by @BenjaminMoe.
-
-
1 issue closed.
-
Are suppension and revocation mutially exclusive? w3c/vc-bitstring-status-list#33.
-
-
2 issues received 7 new comments.
-
Are suppension and revocation mutially exclusive? w3c/vc-bitstring-status-list#33 (4 comments by @BenjaminMoe, @dlongley)
-
-
1 pull request opened.
-
fix: credentialStatus w3c/vc-bitstring-status-list#34, by @nissimsan.
-
-
1 pull request received 1 new comment.
w3c/cid
-
1 issue opened.
-
X25519KeyAgreementKey2019 has wrong property w3c/cid#34, by @brianorwhatever.
-
w3c/vc-json-schema
-
6 issues opened.
-
Update Drawbacks Section w3c/vc-json-schema#108, by @thereisnogabe.
-
Add to section on extensibility w3c/vc-json-schema#107, by @thereisnogabe.
-
How does using JSON Schemas enable interoperability? w3c/vc-json-schema#106, by @thereisnogabe.
-
Add language on which version(s) of JSON Schema are supported w3c/vc-json-schema#105, by @thereisnogabe.
-
How to use Credential Schemas in the VCDM? w3c/vc-json-schema#104, by @thereisnogabe.
-
Add examples for JSON-LD and JOSE Signed Schema w3c/vc-json-schema#103, by @thereisnogabe.
-
-
3 issues closed.
-
Matrix parameters :D w3c/vc-json-schema#80.
-
Move JoseNonLinkedDataSignature2020 to a seperate repo w3c/vc-json-schema#6.
-
JSON Schema Canonicalization w3c/vc-json-schema#20.
-
-
9 issues received 10 new comments.
-
Add language on which version(s) of JSON Schema are supported w3c/vc-json-schema#105 (2 comments by @thereisnogabe)
-
Add examples for JSON-LD and JOSE Signed Schema w3c/vc-json-schema#103 (1 comment by @thereisnogabe)
-
Should bikeshed be used to define industry specific contexts w3c/vc-json-schema#21 (1 comment by @thereisnogabe)
-
Move JoseNonLinkedDataSignature2020 to a seperate repo w3c/vc-json-schema#6 (1 comment by @thereisnogabe)
-
-
2 pull requests opened.
-
Substantial changes for v2 w3c/vc-json-schema#102, by @thereisnogabe.
-
Update v2 w3c/vc-json-schema#101, by @thereisnogabe.
-
-
2 pull requests merged.
-
Substantial changes for v2 w3c/vc-json-schema#102.
-
Update v2 w3c/vc-json-schema#101.
-
-
2 pull requests received 7 new comments.
w3c/vc-di-eddsa-test-suite
-
1 pull request opened.
-
Use @digitalbazaar/mocha-w3c-interop-reporter 1.3. w3c/vc-di-eddsa-test-suite#7, by @aljones15.
-
-
1 pull request merged.
-
Use @digitalbazaar/mocha-w3c-interop-reporter 1.3. w3c/vc-di-eddsa-test-suite#7.
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request opened.
-
Use @digitalbazaar/mocha-w3c-interop-reporter 1.3. w3c/vc-bitstring-status-list-test-suite#21, by @aljones15.
-
-
1 pull request merged.
-
Use @digitalbazaar/mocha-w3c-interop-reporter 1.3. w3c/vc-bitstring-status-list-test-suite#21.
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
Use @digitalbazaar/mocha-w3c-interop-reporter ^1.3. w3c/vc-di-ed25519signature2020-test-suite#30, by @aljones15.
-
-
1 pull request merged.
-
Use @digitalbazaar/mocha-w3c-interop-reporter ^1.3. w3c/vc-di-ed25519signature2020-test-suite#30.
-
w3c/vcalm
-
5 issues received 8 new comments.
-
PROPOSAL: verifiers MUST cryptographically sign their challenges w3c/vcalm#188 (2 comments by @msporny, @OR13)
-
How are client features requested by the server during exchanges using VPR? w3c/vcalm#280 (2 comments by @msporny)
-
credentialId in updateCredentialStatus may not fit all use cases w3c/vcalm#126 (1 comment by @msporny)
-
-
2 pull requests opened.
-
Exchanges Continue response can be anyOf VPResponse or VPRequest. w3c/vcalm#325, by @aljones15.
-
Adds a description to issuer.id & the error response. w3c/vcalm#324, by @aljones15.
-
-
3 pull requests received 5 new comments.
-
Add verifiablePresentationRequest property to exchange initiate. w3c/vcalm#323 (3 comments by @aljones15, @dlongley)
-
Exchanges Continue response can be anyOf VPResponse or VPRequest. w3c/vcalm#325 (1 comment by @dlongley)
-
TR publications
-
4 documents published.
-
Verifiable Credentials Data Model v2.0 published 4 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Past meetings
Participants
-
3 participants joined.
-
Brandon Baraban (Koodos Labs) joined.
-
Phillip Long (Arizona State University) joined.
-
Timothy Summers (Arizona State University) joined.
-
-
3 participants left.
-
Rachel Dvorak (MFX Worldwide, Inc.) left.
-
Alyssa Oconnor (MFX Worldwide, Inc.) left.
-
Timothy Summers (Arizona State University) left.
-
-
2 organizations joined.
-
Koodos Labs joined.
-
Arizona State University joined.
-
GitHub
w3c/vc-data-model
-
23 issues opened.
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967, by @pchampin.
-
Redirect the vocabulary to v2 w3c/vc-data-model#966, by @iherman.
-
'issued' vs. 'validFrom' (formerly 'issuanceDate') w3c/vc-data-model#965, by @iherman.
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963, by @OR13.
-
Should `validFrom` and `validUntil` change to ISO8601 or Unix Time Stamp, or remain XML Date Time Strings? w3c/vc-data-model#962, by @OR13.
-
nonTransferable Property questions w3c/vc-data-model#960, by @RieksJ.
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959, by @RieksJ.
-
Clarification of the type of the "verifiableCredential" field in a VP w3c/vc-data-model#958, by @vdods.
-
Protecting integrity of `@context` w3c/vc-data-model#956, by @mark-moir.
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953, by @OR13.
-
Proposal: Chaining VCs via links and digests w3c/vc-data-model#952, by @dmitrizagidulin.
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-data-model#951, by @vdods.
-
Verification of multiple credential schemas w3c/vc-data-model#950, by @matthieubosquet.
-
Zero-knowledge packed binary data format w3c/vc-data-model#949, by @stenreijers.
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948, by @msporny.
-
Make the usage of `@context` optional w3c/vc-data-model#947, by @msporny.
-
Change the target file for "https://www.w3.org/2018/credentials/" (at some point...) w3c/vc-data-model#944, by @iherman.
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946, by @Muthurajj.
-
Some questions about implementation: URIs and verificationMethod w3c/vc-data-model#945, by @fabrii.
-
Create the new role of issuee w3c/vc-data-model#942, by @David-Chadwick.
-
Updated schema definition (JSON Shema, SHACL etc) w3c/vc-data-model#941, by @jan-forster-cognizone.
-
EU Label joint degree and multiple issuers for the same VC w3c/vc-data-model#940, by @paulojorgeqferreira.
-
Potential improvements to section "5.8 Zero-Knowledge Proofs" w3c/vc-data-model#939, by @Sebastian-Elfors-IDnow.
-
-
11 issues closed.
-
Minor edit: correction to out of sync link titles in section 4.3 to JSON-LD spec w3c/vc-data-model#925.
-
credentials/v2 should allow additional proof purposes w3c/vc-data-model#756.
-
Default vocab for credentials context v2 w3c/vc-data-model#753.
-
Add a summary text as meta information w3c/vc-data-model#248.
-
Remove `@version` from v2 context w3c/vc-data-model#843.
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-data-model#951.
-
Tracking Issue from TPAC: What does JSON-LD compatible JSON mean? w3c/vc-data-model#929.
-
Modify the .htaccess file for https://www.w3.org/2018/credentials w3c/vc-data-model#921.
-
Migrate Appendix C. "Subject-Holder Relationships" to VC Implementation Guide w3c/vc-data-model#879.
-
Updated schema definition (JSON Shema, SHACL etc) w3c/vc-data-model#941.
-
57 issues received 446 new comments.
-
Make the usage of `@context` optional w3c/vc-data-model#947 (125 comments by @David-Chadwick, @dhh1128, @dlongley, @dmitrizagidulin, @gannan08, @iherman, @jandrieu, @jyasskin, @lrosenthol, @melvincarvalho, @mprorock, @msporny, @nadalin, @OR13, @peacekeeper, @selfissued, @stenreijers, @TallTed, @talltree, @thereisnogabe)
-
Tracking Issue from TPAC: What does JSON-LD compatible JSON mean? w3c/vc-data-model#929 (77 comments by @David-Chadwick, @dlongley, @dwaite, @gkellogg, @iherman, @jandrieu, @melvincarvalho, @msporny, @nadalin, @OR13, @pchampin, @selfissued, @TallTed, @thereisnogabe)
-
Add `@vocab` for `private claims` in `/credentials/v2` `@context` w3c/vc-data-model#953 (56 comments by @bumblefudge, @David-Chadwick, @dlongley, @dmitrizagidulin, @gkellogg, @jandrieu, @jimschoening1, @melvincarvalho, @mfosterio, @mkhraisha, @mprorock, @msporny, @nadalin, @OR13, @peacekeeper, @selfissued, @TallTed, @thereisnogabe, @tplooker, @vongohren)
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932 (31 comments by @agropper, @David-Chadwick, @dwaite, @RieksJ, @Sakurann, @SmithSamuelM, @TallTed, @thereisnogabe)
-
Create the new role of issuee w3c/vc-data-model#942 (17 comments by @agropper, @David-Chadwick, @dwaite, @msporny, @RieksJ, @SmithSamuelM, @TallTed)
-
Limit JSON-LD optionality to enhance developer experience w3c/vc-data-model#948 (16 comments by @David-Chadwick, @dlongley, @gvelez17, @iherman, @msporny, @nadalin, @OR13, @selfissued, @vongohren)
-
Clarification needed on the ease of deducing that a subject is the holder. w3c/vc-data-model#959 (11 comments by @David-Chadwick, @dlongley, @jandrieu, @RieksJ, @TallTed)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (10 comments by @AlexAndrei98, @David-Chadwick, @mark-moir, @Sakurann, @SmithSamuelM, @TallTed)
-
Should `validFrom` and `validUntil` change to ISO8601 or Unix Time Stamp, or remain XML Date Time Strings? w3c/vc-data-model#962 (8 comments by @BenjaminMoe, @dlongley, @msporny, @nissimsan, @OR13, @TallTed)
-
IEEE Ontology Standards Working Group Credential Example w3c/vc-data-model#963 (8 comments by @jimschoening1, @OR13)
-
EU Label joint degree and multiple issuers for the same VC w3c/vc-data-model#940 (7 comments by @dlongley, @paulojorgeqferreira, @RieksJ, @vongohren)
-
Protecting integrity of `@context` w3c/vc-data-model#956 (4 comments by @dlongley, @mark-moir, @msporny)
-
`notTransferable` property not defined in `@context` w3c/vc-data-model#731 (4 comments by @David-Chadwick, @msporny, @TallTed, @thereisnogabe)
-
Can a credentialSubject be only a string value? w3c/vc-data-model#762 (4 comments by @iherman, @kdenhartog, @msporny, @OR13)
-
Minor edit: correction to out of sync link titles in section 4.3 to JSON-LD spec w3c/vc-data-model#925 (3 comments by @msporny, @richardbergquist, @thereisnogabe)
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709 (3 comments by @iherman, @msporny, @nadalin)
-
Define JSON Schemas for all objects in the VCDM w3c/vc-data-model#934 (3 comments by @aljones15, @jan-forster-cognizone)
-
Modify the .htaccess file for https://www.w3.org/2018/credentials w3c/vc-data-model#921 (3 comments by @dlongley, @iherman, @msporny)
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913 (2 comments by @iherman, @msporny)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (2 comments by @msporny, @TallTed)
-
credentials/v2 should allow additional proof purposes w3c/vc-data-model#756 (2 comments by @msporny, @OR13)
-
Change the target file for "https://www.w3.org/2018/credentials/" (at some point...) w3c/vc-data-model#944 (2 comments by @iherman, @msporny)
-
ACDC (Authentic Chained Data Containers) in VC DM 2.0 w3c/vc-data-model#895 (2 comments by @brentzundel, @mark-moir)
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-data-model#951 (2 comments by @David-Chadwick, @vdods)
-
Some questions about implementation: URIs and verificationMethod w3c/vc-data-model#945 (2 comments by @brentzundel, @TallTed)
-
In Example 1, `value` and `lang` are not aliased to `@value` and `@language` w3c/vc-data-model#967 (1 comment by @msporny)
-
Clarification of the type of the "verifiableCredential" field in a VP w3c/vc-data-model#958 (1 comment by @TallTed)
-
Is a verifiable credential in JSON-LD expand form valid? w3c/vc-data-model#779 (1 comment by @msporny)
-
Base context v1 missing `sec:` mapping in RsaSignature2018 "@context" w3c/vc-data-model#778 (1 comment by @msporny)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (1 comment by @dmitrizagidulin)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (1 comment by @OR13)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (1 comment by @Sakurann)
-
what is attribute ID in the verifiable credential? w3c/vc-data-model#946 (1 comment by @brentzundel)
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#923 (1 comment by @David-Chadwick)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (1 comment by @agropper)
-
w3c/vc-data-model#42 (1 comment by @msporny)
-
Migrate Appendix C. "Subject-Holder Relationships" to VC Implementation Guide w3c/vc-data-model#879 (1 comment by @msporny)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (1 comment by @David-Chadwick)
-
-
6 pull requests opened.
-
Add nonTransferable property to credentials vocab w3c/vc-data-model#969, by @matthieubosquet.
-
Upgrade to YAML vocabulary w3c/vc-data-model#968, by @msporny.
-
IssuanceDate and ExpirationDate w3c/vc-data-model#964, by @mkhraisha.
-
Corrects out of sync link titles in section 4.3 to json-ld spec w3c/vc-data-model#955, by @richardbergquist.
-
Switched to YAML for the vocab definition w3c/vc-data-model#954, by @iherman.
-
Add DataIntegrityProof to credentials/v2 JSON-LD Context. w3c/vc-data-model#943, by @msporny.
-
-
4 pull requests merged.
-
Switched to YAML for the vocab definition w3c/vc-data-model#954.
-
Corrects out of sync link titles in section 4.3 to json-ld spec w3c/vc-data-model#955.
-
Add DataIntegrityProof to credentials/v2 JSON-LD Context. w3c/vc-data-model#943.
-
New script for the vocabulary generation w3c/vc-data-model#936.
-
-
2 pull requests closed.
-
Remove proof from v2 context w3c/vc-data-model#924.
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#795.
-
-
7 pull requests received 68 new comments.
-
Remove proof from v2 context w3c/vc-data-model#924 (14 comments by @David-Chadwick, @iherman, @msporny, @OR13, @peacekeeper, @thereisnogabe)
-
IssuanceDate and ExpirationDate w3c/vc-data-model#964 (4 comments by @dlongley, @mkhraisha, @msporny)
-
Corrects out of sync link titles in section 4.3 to json-ld spec w3c/vc-data-model#955 (2 comments by @iherman, @w3cbot)
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#795 (2 comments by @David-Chadwick, @msporny)
w3c/vcalm
-
3 issues opened.
-
Question about IssueCredentialOptions and VerifyOptions w3c/vcalm#318, by @tsnyder-gs1us.
-
Add challenge management endpoint to verifying APIs w3c/vcalm#310, by @dlongley.
-
-
3 issues closed.
-
"App" terminology creating confusion w3c/vcalm#297.
-
Linting CI/CD w3c/vcalm#221.
-
Need to address CI w3c/vcalm#277.
-
-
7 issues received 27 new comments.
-
Snapshot VC Issuer/Verifier API for VCWG? w3c/vcalm#304 (8 comments by @mavarley, @msporny, @OR13, @peacekeeper)
-
There should be a test for issue credential with a default issuer provided w3c/vcalm#274 (6 comments by @dlongley, @mkhraisha, @msporny, @OR13, @TallTed)
-
Why don't we just say this API is external and start designing it as such? w3c/vcalm#282 (6 comments by @David-Chadwick, @dlongley, @jandrieu, @msporny)
-
Add challenge management endpoint to verifying APIs w3c/vcalm#310 (3 comments by @dlongley, @msporny)
-
Ensure exchanges payloads use top-level JSON properties and use POST method w3c/vcalm#311 (2 comments by @dlongley, @msporny)
-
-
13 pull requests opened.
-
Add verifiablePresentationRequest property to exchange initiate. w3c/vcalm#323, by @aljones15.
-
Add verifiablePresentation to exchanges examples. w3c/vcalm#322, by @aljones15.
-
Add 404 as a response for GET/DELETE credentials/{id} and same for VPs w3c/vcalm#321, by @aljones15.
-
Prepare document for publication as VCWG Draft NOTE. w3c/vcalm#320, by @msporny.
-
Fix bug: continue should use POST not PUT in index.html. w3c/vcalm#319, by @aljones15.
-
Change DIDAuth to DIDAuthentication. w3c/vcalm#317, by @aljones15.
-
Add OAuth2 to securitySchemes for holder, issuer, & verifier. w3c/vcalm#316, by @aljones15.
-
Add 404 to exchanges/exchange-id/transaction-id responses. w3c/vcalm#315, by @aljones15.
-
Add serveIndex & docs on serving the index.html. w3c/vcalm#312, by @aljones15.
-
Fix Presentation endpoints w3c/vcalm#309, by @matthieubosquet.
-
Rename "App" to "Coordinator". w3c/vcalm#308, by @msporny.
-
-
11 pull requests merged.
-
Fix bug: continue should use POST not PUT in index.html. w3c/vcalm#319.
-
Add 404 to exchanges/exchange-id/transaction-id responses. w3c/vcalm#315.
-
Add serveIndex & docs on serving the index.html. w3c/vcalm#312.
-
Fix Presentation endpoints w3c/vcalm#309.
-
Rename "App" to "Coordinator". w3c/vcalm#308.
-
Change DIDAuth to DIDAuthentication. w3c/vcalm#317.
-
Fix existing CI/CD pipeline and add linting w3c/vcalm#294.
-
Typo w3c/vcalm#307.
-
Typo in VC API spec w3c/vcalm#303.
-
-
3 pull requests closed.
-
Security Framework w3c/vcalm#226.
-
Add section on authorization delegation. w3c/vcalm#230.
-
-
8 pull requests received 11 new comments.
-
Add VerifiablePresentationResponse with property verifiablePresentation w3c/vcalm#314 (3 comments by @aljones15, @TallTed)
-
Add verifiablePresentationRequest property to exchange initiate. w3c/vcalm#323 (1 comment by @dlongley)
-
Add OAuth2 to securitySchemes for holder, issuer, & verifier. w3c/vcalm#316 (1 comment by @dlongley)
-
w3c/vc-jws-2020
-
1 issue opened.
-
Re-use `proofValue` from DataIntegrityProof instead of `jws` w3c/vc-jws-2020#25, by @msporny.
-
-
1 issue received 4 new comments.
-
Re-use `proofValue` from DataIntegrityProof instead of `jws` w3c/vc-jws-2020#25 (4 comments by @mprorock, @msporny, @OR13)
-
-
1 pull request opened.
-
Create a First Public Working Draft for Json Web Signature Data Integrity. w3c/vc-jws-2020#26, by @OR13.
-
-
2 pull requests received 17 new comments.
-
Add IANA to context w3c/vc-jws-2020#24 (10 comments by @dlongley, @iherman, @mprorock, @msporny, @peacekeeper)
-
Create a First Public Working Draft for Json Web Signature Data Integrity. w3c/vc-jws-2020#26 (7 comments by @iherman, @OR13)
-
w3c/vc-imp-guide
-
2 issues opened.
-
Verifier perspective needed on subject-holder relationships w3c/vc-imp-guide#69, by @RieksJ.
-
Clarification needed regarding "the subject of a VC" w3c/vc-imp-guide#70, by @RieksJ.
-
-
1 issue received 3 new comments.
-
Clarification needed regarding "the subject of a VC" w3c/vc-imp-guide#70 (3 comments by @awoie, @RieksJ)
-
w3c/vc-data-integrity
-
2 issues opened.
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66, by @msporny.
-
Explain how proof types are mapped to URLs w3c/vc-data-integrity#60, by @msporny.
-
-
1 issue closed.
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#8.
-
-
3 issues received 4 new comments.
-
Cleanly separate cryptosuite verification and purpose verification algorithms w3c/vc-data-integrity#66 (1 comment by @TallTed)
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#8 (1 comment by @msporny)
-
9 pull requests opened.
-
Create a First Public Working Draft for Data Integrity. w3c/vc-data-integrity#67, by @msporny.
-
Create formal version of the security vocabulary w3c/vc-data-integrity#65, by @iherman.
-
Update algorithm for Verify Proof w3c/vc-data-integrity#64, by @msporny.
-
Remove the unnecessary Create Verify Hash Algorithm. w3c/vc-data-integrity#63, by @msporny.
-
Refactor Generate Proof algorithm. w3c/vc-data-integrity#62, by @msporny.
-
Add initial JSON-LD Context for Data Integrity. w3c/vc-data-integrity#61, by @msporny.
-
Refactor examples to use DataIntegrityProof w3c/vc-data-integrity#59, by @msporny.
-
Add section on DataIntegrityProof. w3c/vc-data-integrity#58, by @msporny.
-
Refactor the cryptosuite section. w3c/vc-data-integrity#57, by @msporny.
-
-
10 pull requests merged.
-
Create formal version of the security vocabulary w3c/vc-data-integrity#65.
-
Update algorithm for Verify Proof w3c/vc-data-integrity#64.
-
Remove the unnecessary Create Verify Hash Algorithm. w3c/vc-data-integrity#63.
-
Refactor Generate Proof algorithm. w3c/vc-data-integrity#62.
-
Add initial JSON-LD Context for Data Integrity. w3c/vc-data-integrity#61.
-
Refactor examples to use DataIntegrityProof w3c/vc-data-integrity#59.
-
Add section on DataIntegrityProof. w3c/vc-data-integrity#58.
-
Refactor the cryptosuite section. w3c/vc-data-integrity#57.
-
Add normative text to proofs section. w3c/vc-data-integrity#56.
-
Add content to section on selective disclosure w3c/vc-data-integrity#53.
-
-
1 pull request closed.
-
Add content to section on unlinkability w3c/vc-data-integrity#52.
-
-
12 pull requests received 98 new comments.
-
Update algorithm for Verify Proof w3c/vc-data-integrity#64 (24 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Add normative text to proofs section. w3c/vc-data-integrity#56 (11 comments by @msporny, @TallTed, @thereisnogabe)
-
Create a First Public Working Draft for Data Integrity. w3c/vc-data-integrity#67 (10 comments by @iherman, @msporny)
-
Create formal version of the security vocabulary w3c/vc-data-integrity#65 (10 comments by @iherman, @msporny, @OR13, @TallTed)
-
Refactor Generate Proof algorithm. w3c/vc-data-integrity#62 (10 comments by @dlongley, @iherman, @msporny, @TallTed)
-
Refactor examples to use DataIntegrityProof w3c/vc-data-integrity#59 (10 comments by @dlongley, @msporny, @TallTed)
-
Refactor the cryptosuite section. w3c/vc-data-integrity#57 (8 comments by @dlongley, @mprorock, @msporny, @TallTed)
-
Remove the unnecessary Create Verify Hash Algorithm. w3c/vc-data-integrity#63 (7 comments by @dlongley, @iherman, @msporny, @TallTed)
-
w3c/vc-jose-cose
-
5 issues opened.
-
How best to describe the VC-JWT Production Rules w3c/vc-jose-cose#36, by @OR13.
-
Should we comment on "principle"? w3c/vc-jose-cose#35, by @OR13.
-
Add Privacy and Security Considerations w3c/vc-jose-cose#34, by @OR13.
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-jose-cose#31, by @vdods.
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30, by @OR13.
-
-
5 issues closed.
-
Speculations about future JWT extensions w3c/vc-jose-cose#24.
-
Write meaningful Introduction w3c/vc-jose-cose#21.
-
Delete "still" in description of JWT w3c/vc-jose-cose#18.
-
Write meaningful Abstract w3c/vc-jose-cose#17.
-
Adopt a more meaningful VC-JWT specification title w3c/vc-jose-cose#16.
-
-
16 issues received 31 new comments.
-
Accept or Dismiss the guidance provided by DIF on `kid` / `iss` w3c/vc-jose-cose#30 (10 comments by @David-Chadwick, @OR13, @Sakurann, @selfissued)
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#22 (2 comments by @selfissued, @TallTed)
-
Various discussion points for VC-JWT Specification w3c/vc-jose-cose#14 (2 comments by @mprorock, @OR13)
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15 (2 comments by @OR13, @selfissued)
-
About the optionality of the "kid" field in JWT-formatted VCs/VPs w3c/vc-jose-cose#31 (1 comment by @selfissued)
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (1 comment by @selfissued)
-
No normative statement wrt. JWT encoding of `verifiableCredential` as base64url w3c/vc-jose-cose#3 (1 comment by @selfissued)
-
-
2 pull requests opened.
-
Multiple subjects note w3c/vc-jose-cose#33, by @selfissued.
-
Excise vacuous introduction w3c/vc-jose-cose#32, by @selfissued.
-
-
6 pull requests merged.
-
Multiple subjects note w3c/vc-jose-cose#33.
-
Excise vacuous introduction w3c/vc-jose-cose#32.
-
Initial VC-JWT Editorial Corrections w3c/vc-jose-cose#29.
-
Write meaningful Abstract w3c/vc-jose-cose#19.
-
Update spec title w3c/vc-jose-cose#20.
-
Remove typ requirement w3c/vc-jose-cose#10.
-
-
4 pull requests received 45 new comments.
-
Begin production rule definition w3c/vc-jose-cose#11 (35 comments by @David-Chadwick, @iherman, @OR13, @Sakurann, @selfissued, @TallTed)
-
w3c/vc-di-eddsa
-
1 pull request opened.
-
DID document public keys are verification methods w3c/vc-di-eddsa#16, by @matthieubosquet.
-
-
1 pull request merged.
-
DID document public keys are verification methods w3c/vc-di-eddsa#16.
-
-
1 pull request received 1 new comment.
w3c/cid
-
1 issue received 1 new comment.
w3c/vc-bitstring-status-list-test-suite
-
1 pull request opened.
-
Add key seed db to github action reporter generator. w3c/vc-bitstring-status-list-test-suite#20, by @aljones15.
-
-
1 pull request merged.
-
Add key seed db to github action reporter generator. w3c/vc-bitstring-status-list-test-suite#20.
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
Add key seed GitHub actions w3c/vc-di-ed25519signature2020-test-suite#29, by @aljones15.
-
-
1 pull request merged.
-
Add key seed GitHub actions w3c/vc-di-ed25519signature2020-test-suite#29.
-
-
1 pull request received 1 new comment.
w3c/vc-di-eddsa-test-suite
-
1 pull request opened.
-
Separate not present or invalid w3c/vc-di-eddsa-test-suite#6, by @aljones15.
-
-
2 pull requests merged.
-
Add verifier tests w3c/vc-di-eddsa-test-suite#4.
-
Separate not present or invalid w3c/vc-di-eddsa-test-suite#6.
-
-
2 pull requests received 10 new comments.
TR publications
-
3 documents published.
-
Verifiable Credentials Data Model v2.0 published 3 times as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Past meetings
-
4 meetings.
Participants
-
13 participants joined.
-
Przemek Praszczalek (Mastercard Incorporated) joined.
-
Geunhyung Kim (Sharing Economy Association of Korea (SEAK)) joined.
-
Cosma Alex Vergari (Institut Mines-Télécom) joined.
-
Charles Lehner (W3C Invited Experts) joined.
-
Paul Ashley (Anonyome Labs, Inc.) joined.
-
Yan Zhang (DappWorks Technology Inc.) joined.
-
Yi Shi (DappWorks Technology Inc.) joined.
-
Scott Heger (Identity Fusion Inc) joined.
-
Steve McCown (Anonyome Labs, Inc.) joined.
-
Dmitri Zagidulin (W3C Invited Experts) joined.
-
Benjamin Goering (Protocol Labs) joined.
-
Allison Shaw (Trinsic) joined.
-
Tomislav Markovski (Trinsic) joined.
-
-
1 participant left.
-
Charles Lehner (W3C Invited Experts) left.
-
-
8 organizations joined.
-
Mastercard Incorporated joined.
-
Gooroomee Inc. joined.
-
Institut Mines-Télécom joined.
-
DappWorks Technology Inc. joined.
-
Identity Fusion Inc joined.
-
Anonyome Labs, Inc. joined.
-
Protocol Labs joined.
-
Trinsic joined.
-
GitHub
w3c/vcalm
-
3 issues opened.
-
How does the issuer know what crypto suite to use? w3c/vcalm#306, by @brianorwhatever.
-
404 HTTP error response status w3c/vcalm#305, by @artursudnik.
-
Snapshot VC Issuer/Verifier API for VCWG? w3c/vcalm#304, by @msporny.
-
-
3 issues closed.
-
How does the issuer know what crypto suite to use? w3c/vcalm#306.
-
Name change in the repo broke the links to the OpenAPI pages w3c/vcalm#238.
-
-
6 issues received 7 new comments.
-
Should the Issuer API allow authorization on a per credential subject granularity? w3c/vcalm#223 (1 comment by @msporny)
-
2 pull requests opened.
-
Typo w3c/vcalm#307, by @matthieubosquet.
-
Typo in VC API spec w3c/vcalm#303, by @matthieubosquet.
-
w3c/vc-di-eddsa-test-suite
-
5 pull requests opened.
-
Add github workflow. w3c/vc-di-eddsa-test-suite#5, by @aljones15.
-
Add verifier tests w3c/vc-di-eddsa-test-suite#4, by @aljones15.
-
Add abstract w3c/vc-di-eddsa-test-suite#3, by @aljones15.
-
Add interop tests for eddsa-2022. w3c/vc-di-eddsa-test-suite#2, by @aljones15.
-
Initial w3c/vc-di-eddsa-test-suite#1, by @aljones15.
-
-
4 pull requests merged.
-
Add github workflow. w3c/vc-di-eddsa-test-suite#5.
-
Add interop tests for eddsa-2022. w3c/vc-di-eddsa-test-suite#2.
-
Initial w3c/vc-di-eddsa-test-suite#1.
-
Add abstract w3c/vc-di-eddsa-test-suite#3.
-
-
3 pull requests received 10 new comments.
w3c/vc-di-eddsa
-
1 pull request opened.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15, by @matthieubosquet.
-
-
1 pull request received 2 new comments.
-
Add missing context for Ed25519VerificationKey2020 w3c/vc-di-eddsa#15 (2 comments by @matthieubosquet, @OR13)
-
w3c/vc-di-ed25519signature2020-test-suite
-
3 pull requests opened.
-
Correct report subtitle w3c/vc-di-ed25519signature2020-test-suite#28, by @aljones15.
-
Remove credentials generator w3c/vc-di-ed25519signature2020-test-suite#27, by @aljones15.
-
Add more verbose author to package.json. w3c/vc-di-ed25519signature2020-test-suite#26, by @aljones15.
-
-
3 pull requests merged.
-
Correct report subtitle w3c/vc-di-ed25519signature2020-test-suite#28.
-
Add more verbose author to package.json. w3c/vc-di-ed25519signature2020-test-suite#26.
-
Remove credentials generator w3c/vc-di-ed25519signature2020-test-suite#27.
-
-
1 pull request received 4 new comments.
-
Remove credentials generator w3c/vc-di-ed25519signature2020-test-suite#27 (4 comments by @aljones15, @msporny)
-
w3c/vc-jose-cose
-
14 issues opened.
-
Determine whether to include content from Verifiable Credentials Implementation Guidelines w3c/vc-jose-cose#28, by @selfissued.
-
Respec warnings and errors w3c/vc-jose-cose#27, by @OR13.
-
Security Considerations section empty w3c/vc-jose-cose#26, by @selfissued.
-
Privacy Considerations section empty w3c/vc-jose-cose#25, by @selfissued.
-
Speculations about future JWT extensions w3c/vc-jose-cose#24, by @selfissued.
-
Confusing text about "If no JWS is present" w3c/vc-jose-cose#23, by @selfissued.
-
Clarify relationship between "iss" and "issuer" w3c/vc-jose-cose#22, by @selfissued.
-
Write meaningful Introduction w3c/vc-jose-cose#21, by @selfissued.
-
Delete "still" in description of JWT w3c/vc-jose-cose#18, by @selfissued.
-
Write meaningful Abstract w3c/vc-jose-cose#17, by @selfissued.
-
Adopt a more meaningful VC-JWT specification title w3c/vc-jose-cose#16, by @selfissued.
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15, by @OR13.
-
Various discussion points for VC-JWT Specification w3c/vc-jose-cose#14, by @nadalin.
-
-
12 issues received 40 new comments.
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (10 comments by @bellebaum, @OR13, @TallTed)
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (8 comments by @nadalin, @Sakurann, @Sebastian-Elfors-IDnow, @selfissued, @thereisnogabe)
-
Support for multiple signatures w3c/vc-jose-cose#6 (5 comments by @David-Chadwick, @TallTed, @theblockstalk)
-
clarify that `vc` `vp` claims do not include entire VC/VPs w3c/vc-jose-cose#4 (3 comments by @OR13, @TallTed)
-
Adopt a more meaningful VC-JWT specification title w3c/vc-jose-cose#16 (3 comments by @OR13, @Sakurann)
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9 (3 comments by @bellebaum, @David-Chadwick, @TallTed)
-
Describe why core data model members are translated to JWT claims w3c/vc-jose-cose#15 (1 comment by @TallTed)
-
-
3 pull requests opened.
-
Initial VC-JWT Editorial Corrections w3c/vc-jose-cose#29, by @selfissued.
-
Update spec title w3c/vc-jose-cose#20, by @OR13.
-
Write meaningful Abstract w3c/vc-jose-cose#19, by @OR13.
-
-
4 pull requests received 12 new comments.
w3c/vc-data-model
-
12 issues opened.
-
Indicating Encrypted VCs in VPs w3c/vc-data-model#938, by @David-Chadwick.
-
Presentations SHOULD expire w3c/vc-data-model#937, by @OR13.
-
Add "credential boilerplates" as examples w3c/vc-data-model#935, by @OR13.
-
Define JSON Schemas for all objects in the VCDM w3c/vc-data-model#934, by @thereisnogabe.
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933, by @thereisnogabe.
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932, by @thereisnogabe.
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931, by @thereisnogabe.
-
Representing Delegated Credentials in the VCDM w3c/vc-data-model#930, by @thereisnogabe.
-
Tracking Issue from TPAC: What does JSON-LD compatible JSON mean? w3c/vc-data-model#929, by @brentzundel.
-
Add `render` property to a core VC data model w3c/vc-data-model#928, by @philarcher.
-
Definition of evidence should align with NIST w3c/vc-data-model#926, by @OR13.
-
Minor edit: correction to out of sync link titles in section 4.3 to JSON-LD spec w3c/vc-data-model#925, by @richardbergquist.
-
-
5 issues closed.
-
Migrate Section 6.3.1 JSON Web Token to separate normative specification w3c/vc-data-model#880.
-
Condense editors list to set of current editors w3c/vc-data-model#917.
-
Bug in the credential vocabulary specification w3c/vc-data-model#770.
-
Data Model Vocabulary versioning questions w3c/vc-data-model#916.
-
VPs and timestamps? w3c/vc-data-model#877.
-
-
29 issues received 151 new comments.
-
Representing Delegated Credentials in the VCDM w3c/vc-data-model#930 (36 comments by @agropper, @awoie, @jandrieu, @kdenhartog, @msporny, @RieksJ, @swcurran, @TallTed, @thereisnogabe, @vongohren)
-
Define policies for directory of related work w3c/vc-data-model#909 (16 comments by @iherman, @lrosenthol, @msporny, @OR13, @Sakurann, @selfissued, @TallTed, @thereisnogabe)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (14 comments by @agropper, @brentzundel, @David-Chadwick, @iherman, @jandrieu, @logpo, @OR13, @RieksJ, @TallTed, @thereisnogabe)
-
Define JSON Schemas for all objects in the VCDM w3c/vc-data-model#934 (14 comments by @dezell, @iherman, @OR13, @SmithSamuelM)
-
Representing Multi Issuer Credentials in the VCDM w3c/vc-data-model#932 (9 comments by @David-Chadwick, @OR13, @RieksJ, @SmithSamuelM, @thereisnogabe)
-
"bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders w3c/vc-data-model#821 (8 comments by @agropper, @jandrieu, @RieksJ, @TallTed)
-
Evidence as a Related Credential w3c/vc-data-model#919 (5 comments by @jandrieu, @nadalin, @OR13, @thereisnogabe)
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890 (5 comments by @David-Chadwick, @iherman, @TallTed)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (3 comments by @brentzundel, @iherman, @Sakurann)
-
Representing Mutli Subject Credentials in the VCDM w3c/vc-data-model#931 (3 comments by @SmithSamuelM, @TallTed, @thereisnogabe)
-
Define a standard way to use Credential Schemas for Credential Subjects w3c/vc-data-model#933 (3 comments by @darrellodonnell, @thereisnogabe, @vongohren)
-
Tracking Issue from TPAC: What does JSON-LD compatible JSON mean? w3c/vc-data-model#929 (3 comments by @dlongley, @nadalin)
-
Definition of evidence should align with NIST w3c/vc-data-model#926 (3 comments by @awoie, @kdenhartog, @OR13)
-
`notTransferable` property not defined in `@context` w3c/vc-data-model#731 (3 comments by @iherman, @jandrieu, @thereisnogabe)
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913 (3 comments by @iherman, @OR13, @RieksJ)
-
Fix the vc-data-model namespace with https://www.w3.org/ns/vc/v2 w3c/vc-data-model#758 (3 comments by @iherman, @OR13)
-
Migrate Section 6.3.1 JSON Web Token to separate normative specification w3c/vc-data-model#880 (2 comments by @brentzundel, @OR13)
-
Modify the .htaccess file for https://www.w3.org/2018/credentials w3c/vc-data-model#921 (2 comments by @iherman, @msporny)
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#923 (2 comments by @RieksJ, @thereisnogabe)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (2 comments by @iherman, @TallTed)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (1 comment by @pchampin)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (1 comment by @agropper)
-
-
3 pull requests opened.
-
New script for the vocabulary generation w3c/vc-data-model#936, by @iherman.
-
Vocabulary synced with v2 context w3c/vc-data-model#927, by @iherman.
-
Remove proof from v2 context w3c/vc-data-model#924, by @OR13.
-
-
3 pull requests merged.
-
Vocabulary synced with v2 context w3c/vc-data-model#927.
-
modify editors list w3c/vc-data-model#922.
-
Update the formal vocabulary files w3c/vc-data-model#920.
-
-
6 pull requests received 68 new comments.
-
Update the formal vocabulary files w3c/vc-data-model#920 (20 comments by @dlongley, @iherman, @msporny, @OR13)
-
Vocabulary synced with v2 context w3c/vc-data-model#927 (13 comments by @iherman, @msporny, @pchampin, @thereisnogabe)
-
Remove proof from v2 context w3c/vc-data-model#924 (10 comments by @iherman, @jandrieu, @OR13, @selfissued, @TallTed, @thereisnogabe)
-
modify editors list w3c/vc-data-model#922 (5 comments by @brentzundel, @iherman, @kdenhartog, @msporny)
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#795 (3 comments by @iherman, @thereisnogabe)
-
w3c/vc-data-integrity
-
1 issue opened.
-
Schema.org namespace typos (hash should be a slash!) w3c/vc-data-integrity#50, by @pmcb55.
-
-
1 issue closed.
-
Schema.org namespace typos (hash should be a slash!) w3c/vc-data-integrity#50.
-
-
2 issues received 3 new comments.
-
URLs in current editors draft all seem to be invalid w3c/vc-data-integrity#37 (2 comments by @msporny, @thereisnogabe)
-
Schema.org namespace typos (hash should be a slash!) w3c/vc-data-integrity#50 (1 comment by @msporny)
-
-
7 pull requests opened.
-
Add normative text to proofs section. w3c/vc-data-integrity#56, by @msporny.
-
Fix link to zcap spec. w3c/vc-data-integrity#55, by @aljones15.
-
fix `schema.org#` to `schema.org/` in index.html w3c/vc-data-integrity#54, by @TallTed.
-
Add content to section on selective disclosure w3c/vc-data-integrity#53, by @msporny.
-
Add content to section on unlinkability w3c/vc-data-integrity#52, by @msporny.
-
Rename cryptographic hardening to cryptographic layering. w3c/vc-data-integrity#51, by @msporny.
-
Remove `suites` namespace from Multikey context url. w3c/vc-data-integrity#49, by @gannan08.
-
-
7 pull requests merged.
-
Fix link to zcap spec. w3c/vc-data-integrity#55.
-
Rename cryptographic hardening to cryptographic layering. w3c/vc-data-integrity#51.
-
fix `schema.org#` to `schema.org/` in index.html w3c/vc-data-integrity#54.
-
Adjusting some language for clarity and consistency w3c/vc-data-integrity#35.
-
Remove `suites` namespace from Multikey context url. w3c/vc-data-integrity#49.
-
Add "How it Works" section w3c/vc-data-integrity#47.
-
Revise Design Goals and Rationale w3c/vc-data-integrity#46.
-
-
10 pull requests received 80 new comments.
-
Add content to section on unlinkability w3c/vc-data-integrity#52 (24 comments by @brentzundel, @dlongley, @mkhraisha, @msporny, @TallTed, @thereisnogabe)
-
Add content to section on selective disclosure w3c/vc-data-integrity#53 (23 comments by @brentzundel, @dlongley, @mkhraisha, @mprorock, @msporny, @TallTed, @thereisnogabe)
-
Adjusting some language for clarity and consistency w3c/vc-data-integrity#35 (10 comments by @iherman, @mprorock, @msporny, @thereisnogabe)
-
Rename cryptographic hardening to cryptographic layering. w3c/vc-data-integrity#51 (6 comments by @mkhraisha, @msporny, @TallTed)
-
Remove `suites` namespace from Multikey context url. w3c/vc-data-integrity#49 (2 comments by @iherman, @msporny)
-
w3c/vc-use-cases
-
1 issue opened.
-
Expand on Use Cases for Multi Party Credentials w3c/vc-use-cases#126, by @thereisnogabe.
-
-
1 issue received 1 new comment.
w3c/vc-jose-cose-test-suite
-
1 issue opened.
-
Proposal: use did:jwk for testing dids and vc-jwt in the vc-jwt-test-suite w3c/vc-jose-cose-test-suite#10, by @OR13.
-
-
1 issue received 4 new comments.
-
Proposal: use did:jwk for testing dids and vc-jwt in the vc-jwt-test-suite w3c/vc-jose-cose-test-suite#10 (4 comments by @bellebaum, @David-Chadwick, @OR13)
-
w3c/vc-jws-2020
-
1 pull request received 3 new comments.
TR publications
-
2 documents published.
-
Verifiable Credentials Data Model v2.0 published as a Working Draft. History of Verifiable Credentials Data Model v2.0
-
Verifiable Credentials Data Model v2.0 published as a First Public Working Draft. History of Verifiable Credentials Data Model v2.0
-
Past meetings
Participants
-
12 participants joined.
-
David Ellis (Becker-Carroll) joined.
-
David Chadwick (W3C Invited Experts) joined.
-
Xiaoyu YOU (China Academy of Information and Communications Technology (CAICT)) joined.
-
Haihua Li (China Academy of Information and Communications Technology (CAICT)) joined.
-
Yue Jing (China Academy of Information and Communications Technology (CAICT)) joined.
-
Jian Jin (China Academy of Information and Communications Technology (CAICT)) joined.
-
Chris Abernethy (Tradeverifyd) joined.
-
Edward Curran (Jolocom GmbH) joined.
-
Exe Zulliger (Jolocom GmbH) joined.
-
Marie Jordan (Visa) joined.
-
Mary Dwyer (Dfinity Stiftung) joined.
-
Sebastian Elfors (IDnow GmbH) joined.
-
-
1 participant left.
-
David Chadwick (W3C Invited Experts) left.
-
-
4 organizations joined.
-
Crossword Cybersecurity joined.
-
Visa joined.
-
Dfinity Stiftung joined.
-
IDnow GmbH joined.
-
GitHub
w3c/vc-data-model
-
16 issues opened.
-
Making explicit the binding of the holder to a VC w3c/vc-data-model#923, by @OR13.
-
Modify the .htaccess file for https://www.w3.org/2018/credentials w3c/vc-data-model#921, by @iherman.
-
Evidence as a Related Credential w3c/vc-data-model#919, by @thereisnogabe.
-
Retain issuanceDate and don't introduce validFrom w3c/vc-data-model#918, by @selfissued.
-
Condense editors list to set of current editors w3c/vc-data-model#917, by @brentzundel.
-
Data Model Vocabulary versioning questions w3c/vc-data-model#916, by @iherman.
-
Address `controller` ambiguity w3c/vc-data-model#915, by @OR13.
-
Dereferencing relative to `issuer` w3c/vc-data-model#914, by @OR13.
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913, by @msporny.
-
Add normative reference to Data Integrity w3c/vc-data-model#912, by @Sebastian-Elfors-IDnow.
-
Explain relationship between Presentations and Verifiable Credentials w3c/vc-data-model#910, by @msporny.
-
Define policies for directory of related work w3c/vc-data-model#909, by @msporny.
-
Error in the (RDF) vocabulary of the VC Data Model? w3c/vc-data-model#907, by @iherman.
-
Define v2 context w3c/vc-data-model#904, by @OR13.
-
issue in the example EXAMPLE 4: Usage of the id property w3c/vc-data-model#903, by @SamerW.
-
Define "prover" in addition to "holder". w3c/vc-data-model#902, by @OR13.
-
-
20 issues closed.
-
Retain issuanceDate and don't introduce validFrom w3c/vc-data-model#918.
-
Define v2 context w3c/vc-data-model#904.
-
Authenticators for nodes w3c/vc-data-model#760.
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480.
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164.
-
Bootstrapping Simple WoT Verifiable Claims w3c/vc-data-model#32.
-
Error in the (RDF) vocabulary of the VC Data Model? w3c/vc-data-model#907.
-
The explanation about `credentialStatus.type` is broken. w3c/vc-data-model#891.
-
Defining a V2 context here will require an update to normative statements w3c/vc-data-model#755.
-
example 2 > sec: prefix w3c/vc-data-model#884.
-
Remove proof property from most examples w3c/vc-data-model#811.
-
Are Persistent URI's with https an implementation of VC? w3c/vc-data-model#889.
-
vc:credentialSubject semantics w3c/vc-data-model#885.
-
VC-DATA-MODEL: adding more examples of non json-ld credentials w3c/vc-data-model#815.
-
JWT encoding w3c/vc-data-model#809.
-
Bound Credentials and Unbound Credentials w3c/vc-data-model#799.
-
-
60 issues received 160 new comments.
-
`issuanceDate/expirationDate` and `validFrom/validUntil` w3c/vc-data-model#913 (10 comments by @awoie, @David-Chadwick, @selfissued, @TallTed)
-
Is a verifiable credential in JSON-LD expand form valid? w3c/vc-data-model#779 (9 comments by @agropper, @dlongley, @iherman, @jandrieu, @kdenhartog, @TallTed, @vongohren)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (7 comments by @David-Chadwick, @logpo, @TallTed, @vongohren)
-
Retain issuanceDate and don't introduce validFrom w3c/vc-data-model#918 (7 comments by @awoie, @brentzundel, @David-Chadwick, @OR13, @selfissued, @TallTed)
-
PresentationSchema for VPs w3c/vc-data-model#839 (7 comments by @awoie, @David-Chadwick, @iherman, @OR13)
-
Include a regex for XML Date Time in the next version of the standard. w3c/vc-data-model#846 (7 comments by @brentzundel, @iherman, @mprorock, @OR13, @TallTed)
-
Define "prover" in addition to "holder". w3c/vc-data-model#902 (7 comments by @agropper, @brentzundel, @dlongley, @OR13, @TallTed, @vongohren)
-
Can a credentialSubject be only a string value? w3c/vc-data-model#762 (6 comments by @davux, @dlongley, @iherman, @OR13)
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896 (5 comments by @bumblefudge, @jandrieu, @logpo, @selfissued)
-
Error in the (RDF) vocabulary of the VC Data Model? w3c/vc-data-model#907 (4 comments by @iherman, @OR13)
-
Explicit reference should be added about binding the VC to the holder w3c/vc-data-model#789 (4 comments by @iherman, @kdenhartog, @OR13, @peacekeeper)
-
Define one or more media types for VCs w3c/vc-data-model#421 (4 comments by @iherman, @msporny, @Sakurann)
-
Defining a V2 context here will require an update to normative statements w3c/vc-data-model#755 (3 comments by @iherman, @kdenhartog, @OR13)
-
Condense editors list to set of current editors w3c/vc-data-model#917 (2 comments by @2byrds, @Sakurann)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (2 comments by @iherman, @TallTed)
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709 (2 comments by @iherman, @OR13)
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480 (2 comments by @brentzundel, @iherman)
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164 (2 comments by @brentzundel, @iherman)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (1 comment by @nadalin)
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860 (1 comment by @jandrieu)
-
Explain relationship between Presentations and Verifiable Credentials w3c/vc-data-model#910 (1 comment by @TallTed)
-
issue in the example EXAMPLE 4: Usage of the id property w3c/vc-data-model#903 (1 comment by @TallTed)
-
Are Persistent URI's with https an implementation of VC? w3c/vc-data-model#889 (1 comment by @Sakurann)
-
VC-DATA-MODEL: adding more examples of non json-ld credentials w3c/vc-data-model#815 (1 comment by @brentzundel)
-
Migrate Section 6.3.1 JSON Web Token to separate normative specification w3c/vc-data-model#880 (1 comment by @iherman)
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875 (1 comment by @iherman)
-
Definition of issuanceDate property (and its mapping to JWT claims) w3c/vc-data-model#844 (1 comment by @iherman)
-
Base context v1 missing `sec:` mapping in RsaSignature2018 "@context" w3c/vc-data-model#778 (1 comment by @iherman)
-
[VC-DATA-MODEL] This recommendation has no stated purpose, goals, or intended audience statements. w3c/vc-data-model#813 (1 comment by @brentzundel)
-
V1 specification doesn't definitively state that the credentialSubject.id, if specified, is always the id of the Subject of the Credential w3c/vc-data-model#792 (1 comment by @brentzundel)
-
[PROPOSAL] Spec needs to include a non-JSON/non-JSON-LD example VC binding e.g. JPEG EXIF/XMP w3c/vc-data-model#796 (1 comment by @brentzundel)
-
"Individual claims can be merged together to express a graph of information about a subject." is not a true statement, in general w3c/vc-data-model#790 (1 comment by @brentzundel)
-
-
5 pull requests opened.
-
modify editors list w3c/vc-data-model#922, by @brentzundel.
-
Update the formal vocabulary files w3c/vc-data-model#920, by @iherman.
-
added awoie to editor's list w3c/vc-data-model#911, by @awoie.
-
Setting-up-echidna w3c/vc-data-model#906, by @iherman.
-
Specify the draft Verifiable Credentials v2.0 context. w3c/vc-data-model#905, by @msporny.
-
-
9 pull requests merged.
-
added awoie to editor's list w3c/vc-data-model#911.
-
Specify the draft Verifiable Credentials v2.0 context. w3c/vc-data-model#905.
-
Setting-up-echidna w3c/vc-data-model#906.
-
Migrate Data Integrity section to dedicated specification. w3c/vc-data-model#900.
-
Migrate VC-JWT section to dedicated specification. w3c/vc-data-model#899.
-
Update README to reflect v2.0 work. w3c/vc-data-model#898.
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-data-model#897.
-
Fix the `credentialStatus.type` description w3c/vc-data-model#892.
-
Fixes example signature name typo w3c/vc-data-model#876.
-
-
3 pull requests closed.
-
feat: add name and description w3c/vc-data-model#752.
-
Fix bug in `rdfs:range` of `verifiableCredential` property. w3c/vc-data-model#771.
-
feat: adds 2020 v1 VC context and v3 security context w3c/vc-data-model#759.
-
-
14 pull requests received 99 new comments.
-
Specify the draft Verifiable Credentials v2.0 context. w3c/vc-data-model#905 (39 comments by @dlongley, @iherman, @msporny, @OR13, @Sakurann, @TallTed, @wip-abramson)
-
Setting-up-echidna w3c/vc-data-model#906 (6 comments by @brentzundel, @iherman, @msporny, @Sakurann)
-
Fix bug in `rdfs:range` of `verifiableCredential` property. w3c/vc-data-model#771 (3 comments by @iherman, @msporny)
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-data-model#897 (2 comments by @awoie, @msporny)
-
feat: adds 2020 v1 VC context and v3 security context w3c/vc-data-model#759 (1 comment by @brentzundel)
-
Migrate Data Integrity section to dedicated specification. w3c/vc-data-model#900 (1 comment by @msporny)
-
w3c/vc-jws-2020
-
3 issues opened.
-
Ensure all IRIs for terms are resolvable w3c/vc-jws-2020#23, by @OR13.
-
Fix w3id.org redirects w3c/vc-jws-2020#21, by @OR13.
-
Unable to transfer issues from ccg w3c/vc-jws-2020#8, by @OR13.
-
-
13 issues closed.
-
Publish lates version of lds-jws2020 w3c/vc-jws-2020#14.
-
Web Browser issues with latest version w3c/vc-jws-2020#13.
-
JEST / JOSE compatability w3c/vc-jws-2020#12.
-
jsonld version peer dependency w3c/vc-jws-2020#11.
-
Need another spec author w3c/vc-jws-2020#10.
-
Add definitions for w3id.org/security w3c/vc-jws-2020#15.
-
JsonWebKeyLinkedDataKeyClass2020 should be deprecated, examples updated w3c/vc-jws-2020#17.
-
PublicKeyJWK and PrivateKeyJWK are il-defined w3c/vc-jws-2020#9.
-
PROPOSAL: Merge GitHistory from lds-jws2020 w3c/vc-jws-2020#1.
-
Unable to transfer issues from ccg w3c/vc-jws-2020#8.
-
Rename "VerificationKey" to "JsonWebKey2020" w3c/vc-jws-2020#19.
-
Fix w3id.org redirects w3c/vc-jws-2020#21.
-
`CG-Final` required w3c/vc-jws-2020#6.
-
-
12 issues received 25 new comments.
-
Anti-pattern: Excessive algorithm agility w3c/vc-jws-2020#20 (3 comments by @msporny, @OR13, @selfissued)
-
JsonWebKeyLinkedDataKeyClass2020 should be deprecated, examples updated w3c/vc-jws-2020#17 (1 comment by @OR13)
-
PROPOSAL: Host test vectors as a single json file in this repo w3c/vc-jws-2020#2 (1 comment by @OR13)
-
3 pull requests opened.
-
Add IANA to context w3c/vc-jws-2020#24, by @OR13.
-
Merge ccg history w3c/vc-jws-2020#22, by @OR13.
-
Prepare for Editors Draft revisions w3c/vc-jws-2020#7, by @OR13.
-
-
2 pull requests merged.
-
Merge ccg history w3c/vc-jws-2020#22.
-
Prepare for Editors Draft revisions w3c/vc-jws-2020#7.
-
-
2 pull requests received 10 new comments.
w3c/vc-data-integrity
-
4 issues opened.
-
Add requirements on cryptosuite contexts such as `@protected` w3c/vc-data-integrity#48, by @dlongley.
-
Enable GitHub Pages so we can use it to serve old URLs like https://w3c-ccg.github.io/ld-proofs w3c/vc-data-integrity#39, by @gobengo.
-
Determine how cryptographic suites are named and versioned w3c/vc-data-integrity#38, by @msporny.
-
URLs in current editors draft all seem to be invalid w3c/vc-data-integrity#37, by @wip-abramson.
-
-
1 issue closed.
-
Enable GitHub Pages so we can use it to serve old URLs like https://w3c-ccg.github.io/ld-proofs w3c/vc-data-integrity#39.
-
-
4 issues received 13 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (5 comments by @georgepadayatti, @lemoustachiste, @msporny, @vongohren)
-
Enable GitHub Pages so we can use it to serve old URLs like https://w3c-ccg.github.io/ld-proofs w3c/vc-data-integrity#39 (4 comments by @gobengo, @iherman, @msporny, @OR13)
-
-
11 pull requests opened.
-
Add "How it Works" section w3c/vc-data-integrity#47, by @msporny.
-
Revise Design Goals and Rationale w3c/vc-data-integrity#46, by @msporny.
-
add a few missing words w3c/vc-data-integrity#45, by @TallTed.
-
fix README.md link to editor's draft w3c/vc-data-integrity#44, by @TallTed.
-
Add Security Considerations regarding Data Opacity. w3c/vc-data-integrity#43, by @msporny.
-
Add security considerations section on data transformations. w3c/vc-data-integrity#42, by @msporny.
-
Add section on cryptographic agility and cryptographic hardening. w3c/vc-data-integrity#41, by @msporny.
-
Add Security Considerations for appropriate layering of cryptographic options/parameters. w3c/vc-data-integrity#40, by @msporny.
-
Add Security Considerations section on Versioning Cryptography Suites. w3c/vc-data-integrity#36, by @msporny.
-
Adjusting some language for clarity and consistency w3c/vc-data-integrity#35, by @mprorock.
-
De-scope the Data Integrity specification to focus on Verifiable Credentials. w3c/vc-data-integrity#32, by @msporny.
-
-
8 pull requests merged.
-
add a few missing words w3c/vc-data-integrity#45.
-
Add Security Considerations regarding Data Opacity. w3c/vc-data-integrity#43.
-
Add security considerations section on data transformations. w3c/vc-data-integrity#42.
-
Add section on cryptographic agility and cryptographic hardening. w3c/vc-data-integrity#41.
-
Add Security Considerations for appropriate layering of cryptographic options/parameters. w3c/vc-data-integrity#40.
-
Add Security Considerations section on Versioning Cryptography Suites. w3c/vc-data-integrity#36.
-
fix README.md link to editor's draft w3c/vc-data-integrity#44.
-
De-scope the Data Integrity specification to focus on Verifiable Credentials. w3c/vc-data-integrity#32.
-
-
11 pull requests received 152 new comments.
-
Add Security Considerations section on Versioning Cryptography Suites. w3c/vc-data-integrity#36 (37 comments by @dlongley, @mprorock, @msporny, @OR13)
-
Add section on cryptographic agility and cryptographic hardening. w3c/vc-data-integrity#41 (27 comments by @msporny, @peacekeeper, @TallTed, @thereisnogabe)
-
Add Security Considerations for appropriate layering of cryptographic options/parameters. w3c/vc-data-integrity#40 (26 comments by @dlongley, @msporny, @TallTed, @thereisnogabe)
-
Add security considerations section on data transformations. w3c/vc-data-integrity#42 (15 comments by @dlongley, @msporny, @TallTed)
-
Adjusting some language for clarity and consistency w3c/vc-data-integrity#35 (11 comments by @mprorock, @msporny, @OR13)
-
Add Security Considerations regarding Data Opacity. w3c/vc-data-integrity#43 (7 comments by @dlongley, @msporny, @TallTed)
-
De-scope the Data Integrity specification to focus on Verifiable Credentials. w3c/vc-data-integrity#32 (7 comments by @mprorock, @msporny, @peacekeeper)
-
w3c/vc-jose-cose
-
2 issues opened.
-
Represent issuance time with "iat" rather than "nbf" w3c/vc-jose-cose#9, by @selfissued.
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118, by @Sebastian-Elfors-IDnow.
-
-
1 issue closed.
-
Bad website link in Github repo w3c/vc-jose-cose#2.
-
-
4 issues received 8 new comments.
-
Describe SD-JWT as an alternative for selective disclosure w3c/vc-jose-cose#118 (4 comments by @mprorock, @Sakurann, @Sebastian-Elfors-IDnow)
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (1 comment by @OR13)
-
-
2 pull requests opened.
-
Begin production rule definition w3c/vc-jose-cose#11, by @OR13.
-
Remove typ requirement w3c/vc-jose-cose#10, by @OR13.
-
-
1 pull request merged.
-
Copy JWT section w3c/vc-jose-cose#1.
-
-
2 pull requests received 12 new comments.
w3c/vcalm
-
3 issues opened.
-
Clarification of `GET /credentials` endpoint w3c/vcalm#302, by @kezike.
-
Define OAuth2 authorization mechanism w3c/vcalm#301, by @msporny.
-
-
1 issue closed.
-
Specify DIDAuthentication protocol in more detail w3c/vcalm#296.
-
-
6 issues received 17 new comments.
-
"App" terminology creating confusion w3c/vcalm#297 (8 comments by @ChristopherA, @dlongley, @jandrieu, @kezike, @msporny, @PatStLouis)
-
Add language clarifying the security implications of the 'domain' property in DID Authentication w3c/vcalm#300 (1 comment by @dlongley)
-
-
1 pull request opened.
-
2 pull requests merged.
-
Initial PR for exchange discovery. w3c/vcalm#268.
-
-
2 pull requests received 7 new comments.
-
Replace all references/occurences of the term 'VC HTTP API' with 'VC API' w3c/vcalm#299 (3 comments by @msporny, @PatStLouis)
w3c/cid
-
1 issue received 21 new comments.
w3c/vc-di-eddsa
-
1 issue opened.
-
Test Vectors Don't Verify w3c/vc-di-eddsa#14, by @Wind4Greg.
-
w3c/vc-imp-guide
-
1 pull request merged.
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-imp-guide#68.
-
-
1 pull request received 1 new comment.
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-imp-guide#68 (1 comment by @msporny)
-
w3c/vc-bitstring-status-list
-
1 issue received 3 new comments.
-
Versioning of a specific commit of the specification as a predraft w3c/vc-bitstring-status-list#32 (3 comments by @msporny, @Sakurann, @yanicakj)
-
w3c/vc-di-bbs
-
1 issue received 1 new comment.
Past meetings
Participants
-
7 participants joined.
-
Frans Ward (SURF bv) joined.
-
Alyssa Oconnor (MFX Worldwide, Inc.) joined.
-
Shenole Latimer (MFX Worldwide, Inc.) joined.
-
Rachel Dvorak (MFX Worldwide, Inc.) joined.
-
Frank Corsi (MFX Worldwide, Inc.) joined.
-
Sheri Smith (MFX Worldwide, Inc.) joined.
-
Samuel Smith (W3C Invited Experts) joined.
-
-
22 participants left.
-
JungSoo Park (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Marie Jordan (Visa) left.
-
Sebastian Elfors (IDnow GmbH) left.
-
Scott Heger (Identity Fusion Inc) left.
-
Juan Carlos Cruellas (Universitat Politècnica de Catalunya) left.
-
Yuriy Yuzifovich (Alibaba Group) left.
-
Julien Rossi (CANTON CONSULTING) left.
-
Carlos Pastor Matut (W3C Invited Experts) left.
-
Geunhyung Kim (Sharing Economy Association of Korea (SEAK)) left.
-
Namseok Ko (Electronics and Telecommunications Research Institute (ETRI)) left.
-
Duy-Tung LUU (CANTON CONSULTING) left.
-
Frans Ward (SURF bv) left.
-
Chris Winczewski (Learning Machine, Inc.) left.
-
Troy Ronda (SecureKey) left.
-
Dudley Collinson (Universities Admissions Centre) left.
-
Dmitry Barinov (SecureKey) left.
-
Naomi Yoshizawa (W3C) left.
-
Daniel Burnett (W3C Invited Experts) left.
-
Rouven Heck (Consensys) left.
-
Jean-Yves ROSSI (CANTON CONSULTING) left.
-
Michel Foucault (CANTON CONSULTING) left.
-
Dmitri Zagidulin (W3C Invited Experts) left.
-
-
5 organizations joined.
-
SURF bv joined.
-
Sony Group Corporation joined.
-
MFX Worldwide, Inc. joined.
-
Entersekt joined.
-
Mattr Limited joined.
-
GitHub
w3c/vc-di-bbs
-
1 issue received 1 new comment.
w3c/vc-data-model
-
6 issues opened.
-
Add DataIntegritySignature to v2 context? w3c/vc-data-model#901, by @msporny.
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896, by @jandrieu.
-
ACDC (Authentic Chained Data Containers) in VC DM 2.0 w3c/vc-data-model#895, by @SmithSamuelM.
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893, by @Sakurann.
-
The explanation about `credentialStatus.type` is broken. w3c/vc-data-model#891, by @mirceanis.
-
credentialSchema and Selective Disclosure w3c/vc-data-model#890, by @David-Chadwick.
-
-
3 issues closed.
-
Diagram issues w3c/vc-data-model#873.
-
Cover "authenticatability" of credential w3c/vc-data-model#751.
-
26 issues received 49 new comments.
-
ACDC (Authentic Chained Data Containers) in VC DM 2.0 w3c/vc-data-model#895 (6 comments by @SmithSamuelM, @TallTed, @talltree)
-
Add a summary text as meta information w3c/vc-data-model#248 (5 comments by @brentzundel, @iherman, @jandrieu, @RieksJ, @TallTed)
-
[PROPOSAL] New specification document title: W3C Consensus-based Data Model Specification for Verifiable Credentials w3c/vc-data-model#791 (3 comments by @brentzundel, @iherman)
-
add claims metadata (how the identity claims were assured and how they are maintained) w3c/vc-data-model#893 (3 comments by @RieksJ, @TallTed)
-
Standardize recording a pre-issuance DID Auth VP as evidence property w3c/vc-data-model#896 (2 comments by @msporny, @peacekeeper)
-
Migrate Section 6.3.1 JSON Web Token to separate normative specification w3c/vc-data-model#880 (2 comments by @OR13, @Sakurann)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (2 comments by @andrewwhitehead, @brentzundel)
-
[PROPOSAL] Spec needs to include a non-JSON/non-JSON-LD example VC binding e.g. JPEG EXIF/XMP w3c/vc-data-model#796 (2 comments by @brentzundel, @Sakurann)
-
Are Persistent URI's with https an implementation of VC? w3c/vc-data-model#889 (1 comment by @brentzundel)
-
VC-DATA-MODEL: adding more examples of non json-ld credentials w3c/vc-data-model#815 (1 comment by @Sakurann)
-
[VC-DATA-MODEL] This recommendation has no stated purpose, goals, or intended audience statements. w3c/vc-data-model#813 (1 comment by @brentzundel)
-
V1 specification doesn't definitively state that the credentialSubject.id, if specified, is always the id of the Subject of the Credential w3c/vc-data-model#792 (1 comment by @brentzundel)
-
"bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders w3c/vc-data-model#821 (1 comment by @brentzundel)
-
"Individual claims can be merged together to express a graph of information about a subject." is not a true statement, in general w3c/vc-data-model#790 (1 comment by @brentzundel)
-
Proposal: Anchored Resources and Hashlinks for VCs w3c/vc-data-model#831 (1 comment by @peacekeeper)
-
-
6 pull requests opened.
-
Migrate Data Integrity section to dedicated specification. w3c/vc-data-model#900, by @msporny.
-
Migrate VC-JWT section to dedicated specification. w3c/vc-data-model#899, by @msporny.
-
Update README to reflect v2.0 work. w3c/vc-data-model#898, by @msporny.
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-data-model#897, by @msporny.
-
Prepare the VC Data Model v2.0 FPWD publication w3c/vc-data-model#894, by @msporny.
-
Fix the `credentialStatus.type` description w3c/vc-data-model#892, by @mirceanis.
-
-
1 pull request merged.
-
Prepare the VC Data Model v2.0 FPWD publication w3c/vc-data-model#894.
-
-
7 pull requests received 44 new comments.
-
Prepare the VC Data Model v2.0 FPWD publication w3c/vc-data-model#894 (18 comments by @caribouW3, @deniak, @iherman, @msporny, @thereisnogabe)
-
feat: adds 2020 v1 VC context and v3 security context w3c/vc-data-model#759 (9 comments by @brentzundel, @iherman, @kdenhartog, @msporny)
-
feat: add name and description w3c/vc-data-model#752 (6 comments by @iherman, @msporny, @peacekeeper, @RieksJ)
-
Migrate VC-JWT section to dedicated specification. w3c/vc-data-model#899 (2 comments by @msporny, @peacekeeper)
-
Migrate Data Integrity section to dedicated specification. w3c/vc-data-model#900 (2 comments by @iherman, @msporny)
-
Fix the `credentialStatus.type` description w3c/vc-data-model#892 (2 comments by @mirceanis, @w3cbot)
-
w3c/vc-jose-cose
-
1 issue opened.
-
Bad website link in Github repo w3c/vc-jose-cose#2, by @peacekeeper.
-
-
1 issue received 6 new comments.
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (6 comments by @David-Chadwick, @msporny, @TallTed)
-
-
1 pull request opened.
-
Copy JWT section w3c/vc-jose-cose#1, by @OR13.
-
-
1 pull request received 5 new comments.
w3c/vc-imp-guide
-
1 pull request opened.
-
Migrate Subject-Holder Relationships to VC Implementation Guide. w3c/vc-imp-guide#68, by @msporny.
-
w3c/vc-data-integrity
-
1 issue opened.
-
Link of ZCAP is 404 w3c/vc-data-integrity#31, by @SatoshiSakamori.
-
-
1 issue received 3 new comments.
w3c/vcalm
-
4 issues opened.
-
What does the Exchanger Service do and who uses it? w3c/vcalm#298, by @msporny.
-
"App" terminology creating confusion w3c/vcalm#297, by @msporny.
-
Specify DIDAuthentication protocol in more detail w3c/vcalm#296, by @msporny.
-
Should the VC API support callbacks? w3c/vcalm#295, by @msporny.
-
-
3 issues received 8 new comments.
w3c/vc-jws-2020
-
6 issues opened.
-
`CG-Final` required w3c/vc-jws-2020#6, by @OR13.
-
Rename to `di-jws-2020` ? w3c/vc-jws-2020#5, by @OR13.
-
Add `@vocab` to the context w3c/vc-jws-2020#4, by @OR13.
-
Define all fields of `publicKeyJwk` w3c/vc-jws-2020#3, by @OR13.
-
PROPOSAL: Host test vectors as a single json file in this repo w3c/vc-jws-2020#2, by @OR13.
-
PROPOSAL: Merge GitHistory from lds-jws2020 w3c/vc-jws-2020#1, by @OR13.
-
-
2 issues received 6 new comments.
w3c/vc-bitstring-status-list
-
1 issue opened.
-
Versioning of a specific commit of the specification as a predraft w3c/vc-bitstring-status-list#32, by @Sakurann.
-
-
1 issue closed.
-
Versioning of a specific commit of the specification as a predraft w3c/vc-bitstring-status-list#32.
-
-
1 issue received 3 new comments.
-
Versioning of a specific commit of the specification as a predraft w3c/vc-bitstring-status-list#32 (3 comments by @msporny, @yanicakj)
-
w3c/vc-use-cases
-
1 pull request closed.
-
Adds User Task for "Trust Claim" w3c/vc-use-cases#103.
-
w3c/vc-bitstring-status-list-test-suite
-
1 issue opened.
-
Make issuer configurable w3c/vc-bitstring-status-list-test-suite#19, by @JSAssassin.
-
-
1 pull request opened.
-
Use next implementations w3c/vc-bitstring-status-list-test-suite#18, by @aljones15.
-
-
2 pull requests merged.
-
Refactor tests to support StatusList2021 type w3c/vc-bitstring-status-list-test-suite#13.
-
Use next implementations w3c/vc-bitstring-status-list-test-suite#18.
-
-
1 pull request received 4 new comments.
-
Refactor tests to support StatusList2021 type w3c/vc-bitstring-status-list-test-suite#13 (4 comments by @aljones15, @JSAssassin)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 issue received 3 new comments.
-
Syntactic comparison of expected and actual result w3c/vc-di-ed25519signature2020-test-suite#22 (3 comments by @dlongley, @filip26)
-
-
1 pull request opened.
-
Use post over class specific properties. w3c/vc-di-ed25519signature2020-test-suite#25, by @aljones15.
-
-
2 pull requests merged.
-
Convert to module. w3c/vc-di-ed25519signature2020-test-suite#21.
-
Use post over class specific properties. w3c/vc-di-ed25519signature2020-test-suite#25.
-
Lifecycle
-
1 charter started.
-
Chartered until 30 June 2024. Participants had to rejoin under this charter.
-
Past meetings
-
1 meeting.
Participants
-
3 chairs appointed.
-
Brent Zundel became a chair.
-
Kristina Yasuda became a chair.
-
Kristina Yasuda became a chair.
-
-
3 chairs stepped down.
-
Wayne Chang stepped down as a chair.
-
Kristina Yasuda stepped down as a chair.
-
Brent Zundel stepped down as a chair.
-
-
21 participants joined.
-
Timothée Haudebourg (Spruce Systems, Inc.) joined.
-
Christopher Allen (W3C Invited Experts) joined.
-
Sarven Capadisli (Inrupt Inc.) joined.
-
Justin Richer (Gen) joined.
-
Will Abramson (Legendary Requirements) joined.
-
Snorre Lothar von Gohren Edwin (W3C Invited Experts) joined.
-
Anthony Nadalin (W3C Invited Experts) joined.
-
Gabe Cohen (W3C Invited Experts) joined.
-
Daniel Buchner (Block, Inc.) joined.
-
Eugeniu Rusu (Jolocom GmbH) joined.
-
Aanchal Malhotra (Ripple) joined.
-
Andrew Whitehead (Becker-Carroll) joined.
-
Leonard Rosenthol (Adobe) joined.
-
Robin Berjon (The New York Times) joined.
-
Cihan Saglam (Danube Tech GmbH) joined.
-
Bernhard Fuchs (Danube Tech GmbH) joined.
-
Ahamed Azeem (Danube Tech GmbH) joined.
-
Andrew Jones (Digital Bazaar) joined.
-
Mike Varley (Gen) joined.
-
Brent Zundel (Yubico) joined.
-
Drummond Reed (Gen) joined.
-
-
9 participants left.
-
Justin Richer (Gen) left.
-
Michael Klein (Spruce Systems, Inc.) left.
-
Juan Caballero (Spruce Systems, Inc.) left.
-
Mina Soliman (Jolocom GmbH) left.
-
Karyl Fowler (Transmute) left.
-
Sercan Kum (Becker-Carroll) left.
-
Mike Varley (Gen) left.
-
Drummond Reed (Gen) left.
-
Brent Zundel (Yubico) left.
-
-
29 organizations joined.
-
MITRE Corporation joined.
-
Wiley joined.
-
Kaiser Permanente joined.
-
Inrupt Inc. joined.
-
RANDA Solutions joined.
-
Google LLC joined.
-
Digital Contract Design joined.
-
Block, Inc. joined.
-
Spruce Systems, Inc. joined.
-
Jolocom GmbH joined.
-
GS1 joined.
-
Ripple joined.
-
Merchant Advisory Group joined.
-
China Academy of Information and Communications Technology (CAICT) joined.
-
OpenLink Software Inc. joined.
-
Adobe joined.
-
The New York Times joined.
-
Danube Tech GmbH joined.
-
Keio University joined.
-
Salesforce joined.
-
Transmute joined.
-
Mavennet Systems Inc. joined.
-
Digital Bazaar joined.
-
Ping Identity joined.
-
Microsoft Corporation joined.
-
Gen joined.
-
Becker-Carroll joined.
-
Conexxus joined.
-
Tradeverifyd joined.
-
-
42 organizations left.
-
Visa left.
-
Merchant Advisory Group left.
-
Salesforce left.
-
Google LLC left.
-
China Academy of Information and Communications Technology (CAICT) left.
-
IDnow GmbH left.
-
Identity Fusion Inc left.
-
RANDA Solutions left.
-
Common Approach to Impact Measurement left.
-
Inrupt Inc. left.
-
Universitat Politècnica de Catalunya left.
-
Mavennet Systems Inc. left.
-
Microsoft Corporation left.
-
Alibaba Group left.
-
Sony Group Corporation left.
-
Keio University left.
-
GS1 left.
-
Digital Contract Design left.
-
Tradeverifyd left.
-
Gooroomee Inc. left.
-
Consensys left.
-
Ping Identity left.
-
MITRE Corporation left.
-
Becker-Carroll left.
-
CANTON CONSULTING left.
-
SecureKey left.
-
Universities Admissions Centre left.
-
Conexxus left.
-
Entersekt left.
-
Transmute left.
-
Learning Machine, Inc. left.
-
SURF bv left.
-
Kaiser Permanente left.
-
Wiley left.
-
OpenLink Software Inc. left.
-
Electronics and Telecommunications Research Institute (ETRI) left.
-
Digital Bazaar left.
-
Jolocom GmbH left.
-
Mattr Limited left.
-
Spruce Systems, Inc. left.
-
Danube Tech GmbH left.
-
Evernym left.
-
GitHub
w3c/vc-di-ed25519signature2020-test-suite
-
3 issues opened.
-
Ed25519Signature2020 - Issuer: proofValue length test always fails w3c/vc-di-ed25519signature2020-test-suite#24, by @filip26.
-
Test suite does not deference verificationMethod w3c/vc-di-ed25519signature2020-test-suite#23, by @filip26.
-
Syntactic comparison of expected and actual result w3c/vc-di-ed25519signature2020-test-suite#22, by @filip26.
-
-
2 issues closed.
-
Syntactic comparison of expected and actual result w3c/vc-di-ed25519signature2020-test-suite#22.
-
Ed25519Signature2020 - Issuer: proofValue length test always fails w3c/vc-di-ed25519signature2020-test-suite#24.
-
-
4 issues received 12 new comments.
-
Syntactic comparison of expected and actual result w3c/vc-di-ed25519signature2020-test-suite#22 (7 comments by @aljones15, @dlongley, @filip26)
-
Ed25519Signature2020 - Issuer: proofValue length test always fails w3c/vc-di-ed25519signature2020-test-suite#24 (2 comments by @aljones15, @filip26)
-
Test suite does not deference verificationMethod w3c/vc-di-ed25519signature2020-test-suite#23 (2 comments by @aljones15, @msporny)
-
Shouldn't this be part of the VC API test suite? w3c/vc-di-ed25519signature2020-test-suite#2 (1 comment by @aljones15)
-
-
1 pull request opened.
-
Convert to module. w3c/vc-di-ed25519signature2020-test-suite#21, by @JSAssassin.
-
w3c/vcalm
-
4 issues received 12 new comments.
-
Should issuer be optional when requesting a credential be issued. w3c/vcalm#265 (1 comment by @msporny)
-
1 pull request opened.
-
Fix existing CI/CD pipeline and add linting w3c/vcalm#294, by @brownoxford.
-
-
1 pull request merged.
-
Add general exchange sequence diagram using respec-mermaid. w3c/vcalm#286.
-
-
2 pull requests received 5 new comments.
w3c/vc-data-model
-
10 issues opened.
-
Are Persistent URI's with https an implementation of VC? w3c/vc-data-model#889, by @bertvannuffelen.
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887, by @msporny.
-
id property optional w3c/vc-data-model#886, by @martyr280.
-
vc:credentialSubject semantics w3c/vc-data-model#885, by @bertvannuffelen.
-
example 2 > sec: prefix w3c/vc-data-model#884, by @bertvannuffelen.
-
usage of json-ld to connect json with RDF w3c/vc-data-model#883, by @bertvannuffelen.
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881, by @OR13.
-
Migrate Section 6.3.1 JSON Web Token to separate normative specification w3c/vc-data-model#880, by @msporny.
-
Migrate Appendix C. "Subject-Holder Relationships" to VC Implementation Guide w3c/vc-data-model#879, by @msporny.
-
-
2 issues closed.
-
id property optional w3c/vc-data-model#886.
-
usage of json-ld to connect json with RDF w3c/vc-data-model#883.
-
-
7 issues received 65 new comments.
-
`proof` in `@context` and the use of `@container` w3c/vc-data-model#881 (29 comments by @dlongley, @msporny, @OR13, @peacekeeper, @sbutterfield, @TallTed, @VladimirAlexiev)
-
Add extension mechanism to allow different methods for VP-to-VC / holder binding to next version of standard to allow verification of rightfulness of presentation w3c/vc-data-model#882 (23 comments by @awoie, @bertvannuffelen, @bumblefudge, @jose-gataca, @OR13, @peacekeeper, @samu-gataca, @thereisnogabe)
-
vc:credentialSubject semantics w3c/vc-data-model#885 (8 comments by @awoie, @bertvannuffelen, @lemoustachiste, @mkhraisha)
-
What is the action associated with issuing/creating a Verifiable Presentation? w3c/vc-data-model#887 (2 comments by @andrewhughes3000, @brentzundel)
-
w3c/vc-data-integrity
-
1 issue opened.
-
vc:proof scope w3c/vc-data-integrity#33, by @bertvannuffelen.
-
-
2 issues received 3 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (1 comment by @lemoustachiste)
w3c/vc-bitstring-status-list
-
3 issues opened.
-
Purpose of `id` field in `StatusList2021Entry` w3c/vc-bitstring-status-list#31, by @PhilippGackstatter.
-
StatusList2021Entry example should include "id" field w3c/vc-bitstring-status-list#29, by @yanicakj.
-
Validate Algorithm Step (6) has an error w3c/vc-bitstring-status-list#27, by @thereisnogabe.
-
-
2 issues closed.
-
Purpose of `id` field in `StatusList2021Entry` w3c/vc-bitstring-status-list#31.
-
StatusList2021Entry example should include "id" field w3c/vc-bitstring-status-list#29.
-
-
2 issues received 3 new comments.
-
Purpose of `id` field in `StatusList2021Entry` w3c/vc-bitstring-status-list#31 (2 comments by @dlongley, @PhilippGackstatter)
-
Validate Algorithm Step (6) has an error w3c/vc-bitstring-status-list#27 (1 comment by @thereisnogabe)
-
-
2 pull requests opened.
-
Per issue #29 - Adding "id" field to credentialStatus in example w3c/vc-bitstring-status-list#30, by @yanicakj.
-
validation alg fix w3c/vc-bitstring-status-list#28, by @thereisnogabe.
-
-
1 pull request merged.
-
Per issue #29 - Adding "id" field to credentialStatus in example w3c/vc-bitstring-status-list#30.
-
-
2 pull requests received 8 new comments.
-
Per issue #29 - Adding "id" field to credentialStatus in example w3c/vc-bitstring-status-list#30 (7 comments by @dlongley, @msporny, @OR13, @yanicakj)
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request closed.
-
Convert to module. w3c/vc-bitstring-status-list-test-suite#17.
-
-
1 pull request received 1 new comment.
w3c/vc-jose-cose
-
1 issue opened.
-
1 issue received 3 new comments.
-
[JWT encoding] JWT claim names `instead of` or `in addition to` their verifiable credential counterparts w3c/vc-jose-cose#8 (3 comments by @msporny, @Sakurann, @TallTed)
-
w3c/vc-wg-charter
-
1 pull request opened.
-
Request for Explicit Interop Test Suites from Mozilla w3c/vc-wg-charter#111, by @mprorock.
-
-
1 pull request merged.
-
Request for Explicit Interop Test Suites from Mozilla w3c/vc-wg-charter#111.
-
-
1 pull request received 18 new comments.
-
Request for Explicit Interop Test Suites from Mozilla w3c/vc-wg-charter#111 (18 comments by @brentzundel, @clehner, @iherman, @mprorock, @msporny, @Sakurann)
-
w3c/vc-imp-guide
-
1 issue received 1 new comment.
-
Verifiers MUST NOT trust visual indicators on apps they do not control w3c/vc-imp-guide#66 (1 comment by @chongkan)
-
Lifecycle
GitHub
w3c/vc-bitstring-status-list-test-suite
-
1 issue opened.
-
Update tests to support StatusList2021 type as soon as implementation is ready. w3c/vc-bitstring-status-list-test-suite#8, by @JSAssassin.
-
-
1 issue received 1 new comment.
-
Shouldn't this be part of the VC API test suite? w3c/vc-bitstring-status-list-test-suite#4 (1 comment by @msporny)
-
-
9 pull requests opened.
-
Convert to module. w3c/vc-bitstring-status-list-test-suite#17, by @JSAssassin.
-
Remove `body.hbs` and add `abstract.hbs` w3c/vc-bitstring-status-list-test-suite#16, by @JSAssassin.
-
Explicitly set `force` option to `true` for testing. w3c/vc-bitstring-status-list-test-suite#15, by @JSAssassin.
-
Update to use `RevocationList2020` tag. w3c/vc-bitstring-status-list-test-suite#14, by @JSAssassin.
-
Refactor tests to support StatusList2021 type w3c/vc-bitstring-status-list-test-suite#13, by @JSAssassin.
-
Update if conditional. w3c/vc-bitstring-status-list-test-suite#12, by @JSAssassin.
-
Update gh actions. w3c/vc-bitstring-status-list-test-suite#11, by @JSAssassin.
-
Update to use master branch for `mocha-w3c-interop-reporter`. w3c/vc-bitstring-status-list-test-suite#10, by @JSAssassin.
-
Update `this.columns` to `this.implemented`. w3c/vc-bitstring-status-list-test-suite#9, by @JSAssassin.
-
-
9 pull requests merged.
-
Remove `body.hbs` and add `abstract.hbs` w3c/vc-bitstring-status-list-test-suite#16.
-
Explicitly set `force` option to `true` for testing. w3c/vc-bitstring-status-list-test-suite#15.
-
Update to use `RevocationList2020` tag. w3c/vc-bitstring-status-list-test-suite#14.
-
Update `this.columns` to `this.implemented`. w3c/vc-bitstring-status-list-test-suite#9.
-
Update if conditional. w3c/vc-bitstring-status-list-test-suite#12.
-
Update gh actions. w3c/vc-bitstring-status-list-test-suite#11.
-
Update to use master branch for `mocha-w3c-interop-reporter`. w3c/vc-bitstring-status-list-test-suite#10.
-
Initial w3c/vc-bitstring-status-list-test-suite#1.
-
Use `notImplemented` to populate tables. w3c/vc-bitstring-status-list-test-suite#7.
-
-
1 pull request received 1 new comment.
-
Use `notImplemented` to populate tables. w3c/vc-bitstring-status-list-test-suite#7 (1 comment by @aljones15)
-
w3c/vc-imp-guide
-
4 issues opened.
-
Be suspicious of QR Code flows that don't also check digital signatures at some point w3c/vc-imp-guide#67, by @msporny.
-
Verifiers MUST NOT trust visual indicators on apps they do not control w3c/vc-imp-guide#66, by @msporny.
-
Ensure that credential storage should be encrypted using strong entropy sources w3c/vc-imp-guide#65, by @msporny.
-
Specify that VCs that are not signed are not VCs w3c/vc-imp-guide#64, by @msporny.
-
-
2 issues received 3 new comments.
-
Specify that VCs that are not signed are not VCs w3c/vc-imp-guide#64 (2 comments by @msporny, @peacekeeper)
-
Verifiers MUST NOT trust visual indicators on apps they do not control w3c/vc-imp-guide#66 (1 comment by @RieksJ)
-
w3c/vc-di-ed25519signature2020-test-suite
-
10 pull requests opened.
-
Fix max-len issues and copyright year w3c/vc-di-ed25519signature2020-test-suite#20, by @JSAssassin.
-
Remove unused deps and add missing jsonld dep. w3c/vc-di-ed25519signature2020-test-suite#19, by @JSAssassin.
-
Use abstract.hbs over body.hbs. w3c/vc-di-ed25519signature2020-test-suite#18, by @aljones15.
-
Use add-publish-date-respec w3c/vc-di-ed25519signature2020-test-suite#17, by @aljones15.
-
Allow issuer options w3c/vc-di-ed25519signature2020-test-suite#16, by @aljones15.
-
Use node 16.x in gh workflows. w3c/vc-di-ed25519signature2020-test-suite#15, by @JSAssassin.
-
Add conditional to trigger jobs on different events. w3c/vc-di-ed25519signature2020-test-suite#14, by @JSAssassin.
-
Use master branch for `mocha-w3c-interop-reporter`. w3c/vc-di-ed25519signature2020-test-suite#13, by @JSAssassin.
-
Switch from columns to implemented, notImplemented. w3c/vc-di-ed25519signature2020-test-suite#12, by @aljones15.
-
Refactor create tests to prevent duplicate test creation. w3c/vc-di-ed25519signature2020-test-suite#11, by @aljones15.
-
-
10 pull requests merged.
-
Fix max-len issues and copyright year w3c/vc-di-ed25519signature2020-test-suite#20.
-
Use abstract.hbs over body.hbs. w3c/vc-di-ed25519signature2020-test-suite#18.
-
Remove unused deps and add missing jsonld dep. w3c/vc-di-ed25519signature2020-test-suite#19.
-
Use add-publish-date-respec w3c/vc-di-ed25519signature2020-test-suite#17.
-
Allow issuer options w3c/vc-di-ed25519signature2020-test-suite#16.
-
Use node 16.x in gh workflows. w3c/vc-di-ed25519signature2020-test-suite#15.
-
Switch from columns to implemented, notImplemented. w3c/vc-di-ed25519signature2020-test-suite#12.
-
Add conditional to trigger jobs on different events. w3c/vc-di-ed25519signature2020-test-suite#14.
-
Use master branch for `mocha-w3c-interop-reporter`. w3c/vc-di-ed25519signature2020-test-suite#13.
-
Refactor create tests to prevent duplicate test creation. w3c/vc-di-ed25519signature2020-test-suite#11.
-
-
1 pull request received 2 new comments.
-
Refactor create tests to prevent duplicate test creation. w3c/vc-di-ed25519signature2020-test-suite#11 (2 comments by @JSAssassin)
-
w3c/vcalm
-
4 issues opened.
-
npm run build fails without dependency w3c/vcalm#293, by @paulfdietrich.
-
Which options are required? w3c/vcalm#292, by @aljones15.
-
IssueCredentialResponse does not allow for metadata w3c/vcalm#291, by @msporny.
-
-
1 issue closed.
-
9 issues received 18 new comments.
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266 (4 comments by @dlongley, @jandrieu, @jricher, @msporny)
-
Does verifying a presentation include verifying its VCs? w3c/vcalm#284 (4 comments by @clehner, @jandrieu, @mkhraisha)
-
IssueCredentialResponse does not allow for metadata w3c/vcalm#291 (3 comments by @mavarley, @msporny, @peacekeeper)
-
-
1 pull request received 3 new comments.
w3c/vc-test-suite
-
1 issue opened.
-
The current Process delegates full authority to the Director in making decision to sign Memoranda of Understanding; the only option for the Membership to disagree is through the appeal process. In particular, the process doesn't call for any prior engagement from the Team with the Membership prior to signing such an MoU. w3c/vc-test-suite#129, by @lamjay2704.
-
-
1 issue closed.
w3c/vc-data-model
-
2 issues opened.
-
VPs and timestamps? w3c/vc-data-model#877, by @vdods.
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875, by @nissimsan.
-
-
2 issues received 27 new comments.
-
Normative definition of credentialSubject including legal types w3c/vc-data-model#875 (25 comments by @brentzundel, @csuwildcat, @David-Chadwick, @dwaite, @kdenhartog, @logpo, @msporny, @mwherman2000, @OR13, @selfissued, @TallTed, @thereisnogabe, @tplooker)
-
-
1 pull request opened.
-
Fixes example signature name typo w3c/vc-data-model#876, by @kushaldas.
-
-
1 pull request received 4 new comments.
w3c/vc-di-ecdsa
-
1 issue opened.
-
Excelsior Pass divergence w3c/vc-di-ecdsa#3, by @clehner.
-
-
1 issue closed.
-
Was this really created in 2019? w3c/vc-di-ecdsa#1.
-
-
1 issue received 2 new comments.
w3c/vc-data-integrity
-
1 issue received 3 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (3 comments by @lemoustachiste, @vongohren)
-
w3c/vc-jose-cose
-
1 issue received 1 new comment.
w3c/vc-wg-charter
-
1 issue closed.
-
APA would like a liaison statement w3c/vc-wg-charter#108.
-
-
1 issue received 4 new comments.
-
APA would like a liaison statement w3c/vc-wg-charter#108 (4 comments by @iherman, @michael-n-cooper, @Sakurann)
-
-
2 pull requests merged.
-
Adding registry content reference w3c/vc-wg-charter#109.
-
Added coordination with APA w3c/vc-wg-charter#110.
-
w3c/vc-di-bbs
-
1 pull request opened.
-
Change Linked Data Proofs -> Data Integrity. w3c/vc-di-bbs#66, by @peacekeeper.
-
-
1 pull request merged.
-
Change Linked Data Proofs -> Data Integrity. w3c/vc-di-bbs#66.
-
-
1 pull request received 1 new comment.
Participants
-
5 participants joined.
-
JungSoo Park (Electronics and Telecommunications Research Institute (ETRI)) joined.
-
Marie Jordan (Visa) joined.
-
Kyle Den Hartog (W3C Invited Experts) joined.
-
Steve Cole (Merchant Advisory Group) joined.
-
Kaliya Young (W3C Invited Experts) joined.
-
-
2 organizations joined.
-
Visa joined.
-
Merchant Advisory Group joined.
-
-
1 organization left.
-
AKASHA Foundation left.
-
GitHub
w3c/vc-wg-charter
-
1 issue opened.
-
APA would like a liaison statement w3c/vc-wg-charter#108, by @iherman.
-
-
2 pull requests opened.
-
Added coordination with APA w3c/vc-wg-charter#110, by @iherman.
-
Adding registry content reference w3c/vc-wg-charter#109, by @iherman.
-
-
1 pull request received 1 new comment.
w3c/vc-jose-cose
-
1 issue opened.
-
JWT Decoding: expirationDate w3c/vc-jose-cose#7, by @vpapanchev.
-
w3c/vc-bitstring-status-list-test-suite
-
2 pull requests opened.
-
Use `notImplemented` to populate tables. w3c/vc-bitstring-status-list-test-suite#7, by @JSAssassin.
-
Update to use `vc-api-test-suite-implementations` w3c/vc-bitstring-status-list-test-suite#6, by @JSAssassin.
-
-
1 pull request merged.
-
Update to use `vc-api-test-suite-implementations` w3c/vc-bitstring-status-list-test-suite#6.
-
-
1 pull request received 1 new comment.
-
Use `notImplemented` to populate tables. w3c/vc-bitstring-status-list-test-suite#7 (1 comment by @JSAssassin)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 issue opened.
-
Lint credential generator w3c/vc-di-ed25519signature2020-test-suite#10, by @aljones15.
-
-
1 issue closed.
-
This should explicitly request a "Ed25519Signature2020" proof w3c/vc-di-ed25519signature2020-test-suite#4.
-
-
1 issue received 1 new comment.
-
This should explicitly request a "Ed25519Signature2020" proof w3c/vc-di-ed25519signature2020-test-suite#4 (1 comment by @aljones15)
-
-
3 pull requests opened.
-
Add not implemented w3c/vc-di-ed25519signature2020-test-suite#9, by @aljones15.
-
Correct issuer tests w3c/vc-di-ed25519signature2020-test-suite#8, by @aljones15.
-
Change to msporny di proof w3c/vc-di-ed25519signature2020-test-suite#7, by @aljones15.
-
-
5 pull requests merged.
-
Add not implemented w3c/vc-di-ed25519signature2020-test-suite#9.
-
Correct issuer tests w3c/vc-di-ed25519signature2020-test-suite#8.
-
Change to msporny di proof w3c/vc-di-ed25519signature2020-test-suite#7.
-
Initial w3c/vc-di-ed25519signature2020-test-suite#1.
-
Add issuer test w3c/vc-di-ed25519signature2020-test-suite#6.
-
-
2 pull requests received 14 new comments.
-
Change to msporny di proof w3c/vc-di-ed25519signature2020-test-suite#7 (11 comments by @aljones15, @msporny)
-
w3c/vc-data-integrity
-
1 issue received 1 new comment.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (1 comment by @lemoustachiste)
-
w3c/vc-di-bbs
-
1 issue opened.
-
Believe it is a typo in chapter 6.1.1 step 1 w3c/vc-di-bbs#65, by @echenknox.
-
w3c/vcalm
-
7 issues opened.
-
Does verifying a presentation include verifying its VCs? w3c/vcalm#284, by @jandrieu.
-
Reminder to spot-check broken links in README w3c/vcalm#283, by @kezike.
-
9 issues closed.
-
The link to Figure 1 is broken w3c/vcalm#217.
-
The link to Figure 2 is broken w3c/vcalm#216.
-
Broken paths for test reports caused by changes to this repo w3c/vcalm#193.
-
did:web issuer uses publicKey instead of verificationMethod w3c/vcalm#175.
-
PROPOSAL: delete verifyCredential operation w3c/vcalm#123.
-
-
28 issues received 109 new comments.
-
Do the `/exchanges/*` endpoints need authz? w3c/vcalm#279 (56 comments by @dlongley, @mavarley, @msporny, @tplooker)
-
Should vc http api use PE Spec for query format? w3c/vcalm#174 (6 comments by @csuwildcat, @jrhender, @mavarley, @msporny, @OR13)
-
PROPOSAL: Spec will recommend AGAINST Issuer <> Verifier flows over https w3c/vcalm#186 (5 comments by @jandrieu, @mavarley, @msporny)
-
Ensure that GNAP can be an Authorization protocol extension w3c/vcalm#181 (5 comments by @mavarley, @msporny, @TallTed)
-
API endpoints MUST specify the component (Issuer App, Issuer Service, etc.) w3c/vcalm#285 (4 comments by @dlongley, @jandrieu)
-
Why don't we just say this API is external and start designing it as such? w3c/vcalm#282 (4 comments by @mavarley, @TallTed, @tplooker)
-
Retro-documentation efforts towards UCR documentation w3c/vcalm#180 (3 comments by @jandrieu, @msporny)
-
How are client features requested by the server during exchanges using VPR? w3c/vcalm#280 (3 comments by @msporny, @tplooker)
-
PROPOSAL: Restrict conformance and interop test suites to did:key only. w3c/vcalm#184 (2 comments by @mavarley, @msporny)
-
Proposal: The WG needs to agree to an interoperability profile that covers the suites w3c/vcalm#130 (2 comments by @mavarley, @msporny)
-
Support BitstringStatusList (was: StatusList2021, was: RevocationStatus2020) w3c/vcalm#214 (1 comment by @msporny)
-
Verifiable Presentation should be an object that supports both JWTs and JSON-LD Proofs w3c/vcalm#209 (1 comment by @mavarley)
-
Establish and document permanent URLs for specification and resources by version w3c/vcalm#196 (1 comment by @msporny)
-
BbsBls sig test fixtures (valid by various W3C docs) not permitted by current OpenAPI spec w3c/vcalm#194 (1 comment by @msporny)
-
PROPOSAL: verifiers MUST cryptographically sign their challenges w3c/vcalm#188 (1 comment by @msporny)
-
OpenAPI generators produce non-compiling code from verifier.yml w3c/vcalm#192 (1 comment by @mkhraisha)
-
PROPOSAL: Move DID Resolution Interoperability testing to the did-resolution spec and work item w3c/vcalm#185 (1 comment by @mkhraisha)
-
-
2 pull requests opened.
-
Add general exchange sequence diagram using respec-mermaid. w3c/vcalm#286, by @msporny.
-
Update CODEOWNERS w3c/vcalm#281, by @OR13.
-
-
1 pull request merged.
-
Update CODEOWNERS w3c/vcalm#281.
-
w3c/vc-data-model
-
1 issue closed.
-
Is there a solution of zero knowledge proof for secp256k1 curve? w3c/vc-data-model#861.
-
w3c/vc-bitstring-status-list
-
2 issues closed.
-
Add status list type field w3c/vc-bitstring-status-list#2.
-
StatusList2021Credential or RevovationList2021 Credential w3c/vc-bitstring-status-list#26.
-
-
2 issues received 2 new comments.
-
StatusList2021Credential or RevovationList2021 Credential w3c/vc-bitstring-status-list#26 (1 comment by @msporny)
-
1 pull request merged.
-
Rework the data model to support `statusPurpose` field. w3c/vc-bitstring-status-list#24.
-
-
1 pull request received 4 new comments.
-
Rework the data model to support `statusPurpose` field. w3c/vc-bitstring-status-list#24 (4 comments by @msporny)
-
TR publications
-
1 document published.
-
Verifiable Credentials Data Model v1.1 published as a Recommendation. History of Verifiable Credentials Data Model v1.1
-
Past meetings
Participants
-
7 participants joined.
-
Shawn Butterfield (Salesforce) joined.
-
Sid Mishra (Google LLC) joined.
-
Jeremie Miller (Ping Identity) joined.
-
Songpu Ai (China Academy of Information and Communications Technology (CAICT)) joined.
-
Sebastian Elfors (IDnow GmbH) joined.
-
Kyle Den Hartog (W3C Invited Experts) joined.
-
Scott Heger (Identity Fusion Inc) joined.
-
-
1 participant left.
-
Kyle Den Hartog (W3C Invited Experts) left.
-
-
5 organizations joined.
-
Salesforce joined.
-
Google LLC joined.
-
China Academy of Information and Communications Technology (CAICT) joined.
-
IDnow GmbH joined.
-
Identity Fusion Inc joined.
-
GitHub
w3c/vcalm
-
8 issues opened.
-
Do the `/exchanges/*` endpoints need authz? w3c/vcalm#279, by @msporny.
-
List of VC API implementations? w3c/vcalm#278, by @dmitrizagidulin.
-
Need to address CI w3c/vcalm#277, by @mprorock.
-
What happens when you delete a revocable credential? w3c/vcalm#276, by @OR13.
-
There should be a test for issue credential with a default issuer provided w3c/vcalm#274, by @OR13.
-
There should be a test for issue credential with a default issuer provided> w3c/vcalm#273, by @OR13.
-
Mediated Presentation clarification w3c/vcalm#536, by @jrhender.
-
-
38 issues closed.
-
No authorization mechanism testable in test suite w3c/vcalm#234.
-
Atomicity of credential issuance and reference creation w3c/vcalm#34.
-
confusion around endpoint naming w3c/vcalm#97.
-
Get credentials issued by query w3c/vcalm#114.
-
Allow additionalProperties for options w3c/vcalm#160.
-
No meeting details from Readme w3c/vcalm#235.
-
Endpoint to fetch workflow type w3c/vcalm#259.
-
Need to define "verify" w3c/vcalm#59.
-
Holder: store <credential> w3c/vcalm#71.
-
Checks in verify options w3c/vcalm#74.
-
Consider state proofs when trust boundaries are crossed w3c/vcalm#58.
-
Audit trails for Issuers and Verifiers w3c/vcalm#189.
-
Beware of broken revocation list urls w3c/vcalm#236.
-
Nit: no default file for test suite w3c/vcalm#251.
-
Question on the Presenting APIs w3c/vcalm#260.
-
__fixture__ credential naming format w3c/vcalm#161.
-
nonce option for DeriveCredential w3c/vcalm#136.
-
Add traceability credential to vc-http-api fixtures w3c/vcalm#131.
-
CD for test reports w3c/vcalm#121.
-
Define type of Oauth2 bearer token for plugfest 2021? w3c/vcalm#113.
-
Add Program Completion example credential w3c/vcalm#107.
-
Add CourseCompletion example to test vectors w3c/vcalm#106.
-
Default verificationMethod option w3c/vcalm#67.
-
Arbitrary validation of business rules w3c/vcalm#55.
-
Add proof request as option w3c/vcalm#56.
-
Architectural Model Discussion w3c/vcalm#54.
-
Publish test suite under w3c-ccg w3c/vcalm#79.
-
API does not meet the needs of our customers w3c/vcalm#108.
-
Example API using node.js, express and swagger w3c/vcalm#60.
-
Consider downsides of RESTful APIs w3c/vcalm#50.
-
Remove public-facing API calls w3c/vcalm#40.
-
-
1 issue reopened.
-
VC API should not squat on domain root URL namespace w3c/vcalm#244, by @msporny.
-
-
48 issues received 93 new comments.
-
Do the `/exchanges/*` endpoints need authz? w3c/vcalm#279 (11 comments by @dlongley, @msporny, @tplooker)
-
Should issuer be optional when requesting a credential be issued. w3c/vcalm#265 (8 comments by @dlongley, @OR13)
-
Why do we believe it's a good idea to return an issued credential to an internal caller? w3c/vcalm#48 (6 comments by @msporny, @tplooker)
-
There should be a test that confirms a 4xx error when a credential issuance is requested with an unsupported issuer w3c/vcalm#275 (2 comments by @OR13, @TallTed)
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266 (2 comments by @OR13)
-
credentialId in updateCredentialStatus may not fit all use cases w3c/vcalm#126 (1 comment by @msporny)
-
There should be a test for issue credential with a default issuer provided> w3c/vcalm#273 (1 comment by @OR13)
-
There should be a test for issue credential with a default issuer provided w3c/vcalm#274 (1 comment by @OR13)
-
Define /.well-known endpoint for an API to advertise optional features supported w3c/vcalm#91 (1 comment by @OR13)
-
The Verification Method of a Revocation List Credential MUST match the issuer of a Revocable Verifiable Credential w3c/vcalm#264 (1 comment by @OR13)
-
allow setting credential status before issuance to allow 'pre-registration' of credentials w3c/vcalm#52 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Add JSON Schema renderer for ReSpec w3c/vcalm#272, by @msporny.
-
Initial GET and DELETE Operations w3c/vcalm#271, by @mprorock.
-
Bundle VC-API and provide UX on API Docs w3c/vcalm#270, by @mprorock.
-
Clarify that exchange-id/transaction-id are opaque to client. w3c/vcalm#269, by @msporny.
-
-
5 pull requests merged.
-
Initial GET and DELETE Operations w3c/vcalm#271.
-
Add JSON Schema renderer for ReSpec w3c/vcalm#272.
-
Bundle VC-API and provide UX on API Docs w3c/vcalm#270.
-
Remove issue VC option to change verification method. w3c/vcalm#263.
-
-
5 pull requests received 64 new comments.
-
Initial GET and DELETE Operations w3c/vcalm#271 (34 comments by @dlongley, @mprorock, @msporny, @OR13, @peacekeeper)
-
Remove issue VC option to change verification method. w3c/vcalm#263 (9 comments by @dlongley, @mkhraisha, @OR13)
-
Bundle VC-API and provide UX on API Docs w3c/vcalm#270 (5 comments by @mprorock, @msporny, @TallTed)
-
w3c/vc-wg-charter
-
5 issues opened.
-
Definition of all key formats are left out of scope of the VC data model and crypto suites w3c/vc-wg-charter#97, by @kdenhartog.
-
conditional deliverables section should have an input documents section w3c/vc-wg-charter#90, by @brentzundel.
-
Environmental, Ethical and Social Implications of the Work w3c/vc-wg-charter#89, by @OR13.
-
algorithms-related input documents for all proofs of integrity types w3c/vc-wg-charter#88, by @Sakurann.
-
rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0" w3c/vc-wg-charter#87, by @Sakurann.
-
-
23 issues closed.
-
algorithms-related input documents for all proofs of integrity types w3c/vc-wg-charter#88.
-
New PR needed if did:key/multibase is going to be in scope w3c/vc-wg-charter#83.
-
Each registry should include at least one standardized entry w3c/vc-wg-charter#67.
-
Some of the "other deliverables" raise patent concerns w3c/vc-wg-charter#72.
-
Environmental, Ethical and Social Implications of the Work w3c/vc-wg-charter#89.
-
Add JwtProof2020 to the charter w3c/vc-wg-charter#84.
-
Be clear that defining some fields means defining the ceremonies they point to w3c/vc-wg-charter#68.
-
Clarification on supported proof types w3c/vc-wg-charter#78.
-
rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0" w3c/vc-wg-charter#87.
-
Data Integrity Crypto Suite Registry w3c/vc-wg-charter#62.
-
This should be LEVEL 2 not VERSION 2 w3c/vc-wg-charter#81.
-
v2 Test Suite w3c/vc-wg-charter#64.
-
Update the Verifiable Credential Data Integrity 1.0 section w3c/vc-wg-charter#54.
-
Standardizing PGP for Linked Data Integrity w3c/vc-wg-charter#48.
-
Standardizing MultiKey2021 w3c/vc-wg-charter#46.
-
conditional deliverables section should have an input documents section w3c/vc-wg-charter#90.
-
Draft state for Verifiable Credential Data Integrity 1.0? w3c/vc-wg-charter#56.
-
Data model or models w3c/vc-wg-charter#57.
-
More narrative description/ background w3c/vc-wg-charter#59.
-
clarify IETF liaison w3c/vc-wg-charter#52.
-
expand acronyms on first use w3c/vc-wg-charter#53.
-
-
20 issues received 128 new comments.
-
Normatively defined crypto suites MUST fully define both public and private key representations w3c/vc-wg-charter#82 (36 comments by @brentzundel, @bshambaugh, @dlongley, @iherman, @jyasskin, @kdenhartog, @mprorock, @msporny, @OR13, @quartzjer, @selfissued, @thereisnogabe)
-
algorithms-related input documents for all proofs of integrity types w3c/vc-wg-charter#88 (12 comments by @brentzundel, @iherman, @msporny, @OR13, @Sakurann)
-
Add JwtProof2020 to the charter w3c/vc-wg-charter#84 (11 comments by @brentzundel, @bumblefudge, @iherman, @msporny, @OR13, @Sakurann, @selfissued)
-
This should be LEVEL 2 not VERSION 2 w3c/vc-wg-charter#81 (10 comments by @brentzundel, @iherman, @nadalin, @OR13, @peacekeeper, @Sakurann)
-
Environmental, Ethical and Social Implications of the Work w3c/vc-wg-charter#89 (7 comments by @brentzundel, @iherman, @jandrieu, @msporny, @OR13, @rxgrant)
-
Each registry should include at least one standardized entry w3c/vc-wg-charter#67 (7 comments by @brentzundel, @iherman, @jyasskin, @kdenhartog, @OR13)
-
Be clear that defining some fields means defining the ceremonies they point to w3c/vc-wg-charter#68 (7 comments by @brentzundel, @iherman, @jyasskin, @kdenhartog, @msporny)
-
New PR needed if did:key/multibase is going to be in scope w3c/vc-wg-charter#83 (6 comments by @brentzundel, @iherman, @kdenhartog, @msporny, @quartzjer)
-
rename a deliverable to "Verifiable Credential Proofs of Integrity 1.0" w3c/vc-wg-charter#87 (6 comments by @brentzundel, @msporny, @OR13, @quartzjer, @Sakurann)
-
Some of the "other deliverables" raise patent concerns w3c/vc-wg-charter#72 (5 comments by @brentzundel, @iherman, @jyasskin, @kdenhartog)
-
Definition of all key formats are left out of scope of the VC data model and crypto suites w3c/vc-wg-charter#97 (4 comments by @brentzundel, @iherman, @kdenhartog)
-
Clarification on supported proof types w3c/vc-wg-charter#78 (4 comments by @awoie, @brentzundel, @Sakurann)
-
Update the Verifiable Credential Data Integrity 1.0 section w3c/vc-wg-charter#54 (2 comments by @brentzundel)
-
Draft state for Verifiable Credential Data Integrity 1.0? w3c/vc-wg-charter#56 (1 comment by @brentzundel)
-
-
18 pull requests opened.
-
updating algorithms-related reference documents for jwt-vcs w3c/vc-wg-charter#107, by @Sakurann.
-
Editorial fix: Remove an unnecessary period w3c/vc-wg-charter#106, by @shigeya.
-
Add Koblitz ECDSA Recovery Cryptosuite w3c/vc-wg-charter#105, by @clehner.
-
Clean up capitalization. w3c/vc-wg-charter#104, by @msporny.
-
remove redundant registry section w3c/vc-wg-charter#103, by @brentzundel.
-
renaming a deliverable to "Securing Verifiable Credentials 1.0" w3c/vc-wg-charter#102, by @Sakurann.
-
Registries and standardized entries w3c/vc-wg-charter#101, by @brentzundel.
-
A non-exhaustive set of possible input documents for registries w3c/vc-wg-charter#100, by @brentzundel.
-
A non-exhaustive set of possible registries w3c/vc-wg-charter#99, by @brentzundel.
-
The WG may produce registries w3c/vc-wg-charter#98, by @brentzundel.
-
Clarify that DI should focus on VCs but ensure generality. w3c/vc-wg-charter#96, by @msporny.
-
Rename a duplicated id w3c/vc-wg-charter#94, by @jyasskin.
-
Complete the list of known cryptosuites of interest for standardization. w3c/vc-wg-charter#93, by @msporny.
-
Add input documents column to conditional deliverables w3c/vc-wg-charter#92, by @brentzundel.
-
Fix botched merge to main for "Other Deliverables" section. w3c/vc-wg-charter#91, by @msporny.
-
Refactor "Other Deliverables" section w3c/vc-wg-charter#86, by @msporny.
-
Add Deliverables section on Registries w3c/vc-wg-charter#85, by @msporny.
-
-
18 pull requests merged.
-
updating algorithms-related reference documents for jwt-vcs w3c/vc-wg-charter#107.
-
Add Koblitz ECDSA Recovery Cryptosuite w3c/vc-wg-charter#105.
-
Clean up capitalization. w3c/vc-wg-charter#104.
-
Editorial fix: Remove an unnecessary period w3c/vc-wg-charter#106.
-
Clarify that DI should focus on VCs but ensure generality. w3c/vc-wg-charter#96.
-
remove redundant registry section w3c/vc-wg-charter#103.
-
Registries and standardized entries w3c/vc-wg-charter#101.
-
renaming a deliverable to "Securing Verifiable Credentials 1.0" w3c/vc-wg-charter#102.
-
The WG may produce registries w3c/vc-wg-charter#98.
-
Add input documents column to conditional deliverables w3c/vc-wg-charter#92.
-
Rename a duplicated id w3c/vc-wg-charter#94.
-
Complete the list of known cryptosuites of interest for standardization. w3c/vc-wg-charter#93.
-
Fix botched merge to main for "Other Deliverables" section. w3c/vc-wg-charter#91.
-
Clarify IETF liaison w3c/vc-wg-charter#80.
-
Refactor "Other Deliverables" section w3c/vc-wg-charter#86.
-
Refactor WG inputs and outputs to follow (approved) WebApps Charter style w3c/vc-wg-charter#77.
-
Clarify Acronyms w3c/vc-wg-charter#79.
-
-
5 pull requests closed.
-
Add Deliverables section on Registries w3c/vc-wg-charter#85.
-
A non-exhaustive set of possible input documents for registries w3c/vc-wg-charter#100.
-
A non-exhaustive set of possible registries w3c/vc-wg-charter#99.
-
Add a possible reference for pgp as a cryptosuite w3c/vc-wg-charter#50.
-
Add ECDSA secpr1 cryptosuite to VCWG input documents. w3c/vc-wg-charter#63.
-
-
22 pull requests received 172 new comments.
-
Add Deliverables section on Registries w3c/vc-wg-charter#85 (41 comments by @brentzundel, @iherman, @jandrieu, @jyasskin, @msporny, @Sakurann, @selfissued, @TallTed, @tplooker)
-
Clarify that DI should focus on VCs but ensure generality. w3c/vc-wg-charter#96 (34 comments by @brentzundel, @dlongley, @iherman, @kdenhartog, @msporny, @OR13, @pchampin, @peacekeeper, @Sakurann)
-
Refactor WG inputs and outputs to follow (approved) WebApps Charter style w3c/vc-wg-charter#77 (14 comments by @brentzundel, @msporny, @Sakurann, @tplooker)
-
Registries and standardized entries w3c/vc-wg-charter#101 (11 comments by @brentzundel, @iherman, @jyasskin, @kdenhartog, @msporny)
-
Refactor "Other Deliverables" section w3c/vc-wg-charter#86 (9 comments by @brentzundel, @msporny, @Sakurann, @TallTed)
-
to allow for multibase support in the VCDI spec w3c/vc-wg-charter#51 (7 comments by @kdenhartog, @msporny)
-
updating algorithms-related reference documents for jwt-vcs w3c/vc-wg-charter#107 (6 comments by @iherman, @msporny, @Sakurann, @selfissued)
-
Add input documents column to conditional deliverables w3c/vc-wg-charter#92 (6 comments by @brentzundel, @iherman, @msporny)
-
Fix botched merge to main for "Other Deliverables" section. w3c/vc-wg-charter#91 (6 comments by @brentzundel, @msporny, @TallTed)
-
Add Koblitz ECDSA Recovery Cryptosuite w3c/vc-wg-charter#105 (5 comments by @brianorwhatever, @iherman, @mirceanis, @mprorock, @OR13)
-
A non-exhaustive set of possible registries w3c/vc-wg-charter#99 (5 comments by @brentzundel, @iherman, @kdenhartog)
-
A non-exhaustive set of possible input documents for registries w3c/vc-wg-charter#100 (3 comments by @brentzundel, @iherman)
-
Complete the list of known cryptosuites of interest for standardization. w3c/vc-wg-charter#93 (2 comments by @iherman, @TallTed)
-
renaming a deliverable to "Securing Verifiable Credentials 1.0" w3c/vc-wg-charter#102 (1 comment by @iherman)
-
Add conditional normative deliverables for post-quantum crypto and other externally standardized primitives w3c/vc-wg-charter#95 (1 comment by @brentzundel)
-
w3c/vc-bitstring-status-list
-
4 issues opened.
-
StatusList2021Credential or RevovationList2021 Credential w3c/vc-bitstring-status-list#26, by @paulfdietrich.
-
Revocation or Suspension Date w3c/vc-bitstring-status-list#25, by @paulfdietrich.
-
Handling Right to Erasure in encodedList and Validate Algorithm w3c/vc-bitstring-status-list#23, by @sbutterfield.
-
Context URL resolves to 404 w3c/vc-bitstring-status-list#21, by @nikosft.
-
-
5 issues received 25 new comments.
-
Context about how this differs from 2020-rl w3c/vc-bitstring-status-list#3 (17 comments by @csuwildcat, @dlongley, @msporny, @sbutterfield)
-
Handling Right to Erasure in encodedList and Validate Algorithm w3c/vc-bitstring-status-list#23 (4 comments by @msporny, @sbutterfield)
-
-
2 pull requests opened.
-
Rework the data model to support `statusPurpose` field. w3c/vc-bitstring-status-list#24, by @msporny.
-
Update context file URL w3c/vc-bitstring-status-list#22, by @clehner.
-
-
1 pull request closed.
-
Update context file URL w3c/vc-bitstring-status-list#22.
-
-
2 pull requests received 32 new comments.
-
Rework the data model to support `statusPurpose` field. w3c/vc-bitstring-status-list#24 (27 comments by @aljones15, @dlongley, @msporny, @OR13, @sbutterfield, @TallTed)
-
w3c/vc-bitstring-status-list-test-suite
-
1 pull request opened.
-
Use new DB issuer and verifier endpoints w3c/vc-bitstring-status-list-test-suite#5, by @JSAssassin.
-
-
1 pull request merged.
-
Use new DB issuer and verifier endpoints w3c/vc-bitstring-status-list-test-suite#5.
-
w3c/vc-di-ed25519signature2020-test-suite
-
2 pull requests opened.
-
Add issuer test w3c/vc-di-ed25519signature2020-test-suite#6, by @aljones15.
-
Add zcap auth headers w3c/vc-di-ed25519signature2020-test-suite#5, by @aljones15.
-
-
1 pull request merged.
-
Add zcap auth headers w3c/vc-di-ed25519signature2020-test-suite#5.
-
-
1 pull request received 2 new comments.
w3c/vc-data-integrity
-
1 issue received 2 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (2 comments by @Exulansis, @msporny)
-
Past meetings
Participants
-
7 participants joined.
-
Kimberly Linson (RANDA Solutions) joined.
-
Martin Reed (RANDA Solutions) joined.
-
Oliver Terbu (Mattr Limited) joined.
-
Patrick Mandic (Mavennet Systems Inc.) joined.
-
Aaron Coburn (Inrupt Inc.) joined.
-
Juan Carlos Cruellas (Universitat Politècnica de Catalunya) joined.
-
Mahmoud Alkhraishi (Mavennet Systems Inc.) joined.
-
-
1 participant left.
-
Kyle Den Hartog (W3C Invited Experts) left.
-
-
5 organizations joined.
-
RANDA Solutions joined.
-
Common Approach to Impact Measurement joined.
-
Inrupt Inc. joined.
-
Universitat Politècnica de Catalunya joined.
-
Mavennet Systems Inc. joined.
-
GitHub
w3c/vc-wg-charter
-
10 issues opened.
-
Add JwtProof2020 to the charter w3c/vc-wg-charter#84, by @OR13.
-
New PR needed if did:key/multibase is going to be in scope w3c/vc-wg-charter#83, by @bumblefudge.
-
Normatively defined crypto suites MUST fully define both public and private key representations w3c/vc-wg-charter#82, by @OR13.
-
This should be LEVEL 2 not VERSION 2 w3c/vc-wg-charter#81, by @nadalin.
-
Clarification on supported proof types w3c/vc-wg-charter#78, by @awoie.
-
Some of the "other deliverables" raise patent concerns w3c/vc-wg-charter#72, by @jyasskin.
-
Add a link to the test suite for VC-JWT & JsonWebSignature2020 w3c/vc-wg-charter#71, by @OR13.
-
Be clear that defining some fields means defining the ceremonies they point to w3c/vc-wg-charter#68, by @jyasskin.
-
Each registry should include at least one standardized entry w3c/vc-wg-charter#67, by @jyasskin.
-
Meta issue on the VCDI deliverable w3c/vc-wg-charter#65, by @iherman.
-
-
7 issues closed.
-
Meta issue on the VCDI deliverable w3c/vc-wg-charter#65.
-
Protocols and APIs should remain out of scope w3c/vc-wg-charter#24.
-
Multilingual support for selecting a image file w3c/vc-wg-charter#38.
-
Add a link to the test suite for VC-JWT & JsonWebSignature2020 w3c/vc-wg-charter#71.
-
Standardizing JsonWebSignature2020 / JsonWebKey2020 w3c/vc-wg-charter#45.
-
Add charter history w3c/vc-wg-charter#55.
-
Success criteria ??? w3c/vc-wg-charter#58.
-
-
21 issues received 75 new comments.
-
Each registry should include at least one standardized entry w3c/vc-wg-charter#67 (18 comments by @brentzundel, @iherman, @jyasskin, @kdenhartog, @msporny, @OR13, @selfissued)
-
clarify IETF liaison w3c/vc-wg-charter#52 (8 comments by @brentzundel, @kdenhartog, @mnot, @msporny, @samuelweiler, @selfissued)
-
Protocols and APIs should remain out of scope w3c/vc-wg-charter#24 (7 comments by @brentzundel, @iherman, @jandrieu, @mprorock, @Sakurann, @selfissued)
-
Be clear that defining some fields means defining the ceremonies they point to w3c/vc-wg-charter#68 (7 comments by @jyasskin, @mprorock, @msporny, @selfissued)
-
Data Integrity Crypto Suite Registry w3c/vc-wg-charter#62 (5 comments by @iherman, @jandrieu, @OR13, @selfissued)
-
Draft state for Verifiable Credential Data Integrity 1.0? w3c/vc-wg-charter#56 (4 comments by @brentzundel, @OR13)
-
Meta issue on the VCDI deliverable w3c/vc-wg-charter#65 (3 comments by @brentzundel, @iherman, @OR13)
-
Some of the "other deliverables" raise patent concerns w3c/vc-wg-charter#72 (3 comments by @brentzundel, @kdenhartog, @nadalin)
-
Normatively defined crypto suites MUST fully define both public and private key representations w3c/vc-wg-charter#82 (2 comments by @dlongley, @thereisnogabe)
-
Clarification on supported proof types w3c/vc-wg-charter#78 (2 comments by @brentzundel, @kdenhartog)
-
Multilingual support for selecting a image file w3c/vc-wg-charter#38 (2 comments by @brentzundel, @shigeya)
-
Update the Verifiable Credential Data Integrity 1.0 section w3c/vc-wg-charter#54 (1 comment by @brentzundel)
-
Add a link to the test suite for VC-JWT & JsonWebSignature2020 w3c/vc-wg-charter#71 (1 comment by @OR13)
-
-
10 pull requests opened.
-
Clarify IETF liaison w3c/vc-wg-charter#80, by @brentzundel.
-
Clarify Acronyms w3c/vc-wg-charter#79, by @brentzundel.
-
Refactor WG inputs and outputs to follow (approved) WebApps Charter style w3c/vc-wg-charter#77, by @msporny.
-
Simplify VCDI deliverable w3c/vc-wg-charter#76, by @brentzundel.
-
Add links to VC Data Model for intro w3c/vc-wg-charter#75, by @brentzundel.
-
Add clarification to description of non-normative deliverables w3c/vc-wg-charter#74, by @brentzundel.
-
Add links from stalled prs w3c/vc-wg-charter#73, by @OR13.
-
Normative specification of APIs or protocols is out of scope w3c/vc-wg-charter#70, by @selfissued.
-
Add ACLU as liaison. w3c/vc-wg-charter#69, by @msporny.
-
Clarify some non-normative deliverables, as well as explicit not in scope items w3c/vc-wg-charter#66, by @mprorock.
-
-
11 pull requests merged.
-
Simplify VCDI deliverable w3c/vc-wg-charter#76.
-
Add links to VC Data Model for intro w3c/vc-wg-charter#75.
-
Clarify some non-normative deliverables, as well as explicit not in scope items w3c/vc-wg-charter#66.
-
Add clarification to description of non-normative deliverables w3c/vc-wg-charter#74.
-
Clarified data model and sub parts w3c/vc-wg-charter#60.
-
Extending support for resources in general w3c/vc-wg-charter#44.
-
Normative specification of APIs or protocols is out of scope w3c/vc-wg-charter#70.
-
Add ACLU as liaison. w3c/vc-wg-charter#69.
-
Linked Data Signatures for JWS w3c/vc-wg-charter#47.
-
Proposed work mode for charter development w3c/vc-wg-charter#61.
-
Align with the latest W3C charter template w3c/vc-wg-charter#49.
-
-
3 pull requests closed.
-
to allow for multibase support in the VCDI spec w3c/vc-wg-charter#51.
-
Add links from stalled prs w3c/vc-wg-charter#73.
-
Specification of APIs or protocols is out of scope w3c/vc-wg-charter#43.
-
-
19 pull requests received 235 new comments.
-
Clarify some non-normative deliverables, as well as explicit not in scope items w3c/vc-wg-charter#66 (51 comments by @brentzundel, @bumblefudge, @dlongley, @iherman, @jricher, @mavarley, @mkhraisha, @mprorock, @msporny, @nadalin, @OR13, @peacekeeper, @Sakurann, @selfissued)
-
Refactor WG inputs and outputs to follow (approved) WebApps Charter style w3c/vc-wg-charter#77 (44 comments by @iherman, @kdenhartog, @msporny, @nadalin, @OR13, @Sakurann)
-
Specification of APIs or protocols is out of scope w3c/vc-wg-charter#43 (22 comments by @brentzundel, @bumblefudge, @iherman, @mprorock, @msporny, @nadalin, @OR13, @peacekeeper)
-
Simplify VCDI deliverable w3c/vc-wg-charter#76 (18 comments by @brentzundel, @iherman, @kdenhartog-mattr, @msporny, @OR13, @Sakurann)
-
Add ECDSA secpr1 cryptosuite to VCWG input documents. w3c/vc-wg-charter#63 (17 comments by @brentzundel, @kdenhartog, @msporny, @OR13)
-
to allow for multibase support in the VCDI spec w3c/vc-wg-charter#51 (15 comments by @brentzundel, @bumblefudge, @kdenhartog, @msporny, @OR13)
-
Add a possible reference for pgp as a cryptosuite w3c/vc-wg-charter#50 (12 comments by @brentzundel, @iherman, @kdenhartog, @msporny, @OR13)
-
Add links to VC Data Model for intro w3c/vc-wg-charter#75 (10 comments by @brentzundel, @iherman, @msporny, @OR13, @Sakurann)
-
Clarified data model and sub parts w3c/vc-wg-charter#60 (9 comments by @brentzundel, @msporny, @OR13, @Sakurann)
-
Add clarification to description of non-normative deliverables w3c/vc-wg-charter#74 (6 comments by @iherman, @Sakurann)
-
Add ACLU as liaison. w3c/vc-wg-charter#69 (5 comments by @brentzundel, @iherman, @msporny, @Sakurann)
-
Extending support for resources in general w3c/vc-wg-charter#44 (4 comments by @brentzundel, @shigeya)
-
Normative specification of APIs or protocols is out of scope w3c/vc-wg-charter#70 (2 comments by @iherman, @selfissued)
-
w3c/vc-jws-2020
-
1 issue opened.
-
PublicKeyJWK and PrivateKeyJWK are il-defined w3c/vc-jws-2020#9, by @thereisnogabe.
-
-
1 issue received 10 new comments.
-
PublicKeyJWK and PrivateKeyJWK are il-defined w3c/vc-jws-2020#9 (10 comments by @kdenhartog, @OR13, @thereisnogabe)
-
w3c/vcalm
-
6 issues opened.
-
Document Instance Configuration in the VC API w3c/vcalm#267, by @OR13.
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266, by @OR13.
-
Should issuer be optional when requesting a credential be issued. w3c/vcalm#265, by @OR13.
-
Question on the Presenting APIs w3c/vcalm#260, by @xtrycatchx.
-
Endpoint to fetch workflow type w3c/vcalm#259, by @mkhraisha.
-
-
4 issues closed.
-
Intro/discussion of VC-HTTP-API to the CCG w3c/vcalm#172.
-
PROPOSAL: Interactive Issue and Re-Issue VC API flow w3c/vcalm#245.
-
-
9 issues received 45 new comments.
-
Should workflow `id`s and `name`s be provided in the URL or POST body? w3c/vcalm#256 (23 comments by @agropper, @mkhraisha, @mprorock, @msporny, @OR13, @TallTed)
-
The Verification Method of a Revocation List Credential MUST match the issuer of a Revocable Verifiable Credential w3c/vcalm#264 (5 comments by @OR13, @peacekeeper, @TallTed)
-
Should issuer be optional when requesting a credential be issued. w3c/vcalm#265 (3 comments by @dlongley, @OR13, @peacekeeper)
-
Issuer API does not expose issuer identifiers and supported crypto suites w3c/vcalm#266 (3 comments by @dlongley, @OR13, @peacekeeper)
-
Given implementation experience, was choosing the "controller style endpoint" pattern the right decision? w3c/vcalm#257 (1 comment by @msporny)
-
-
5 pull requests opened.
-
Initial PR for exchange discovery. w3c/vcalm#268, by @mavarley.
-
Remove issue VC option to change verification method. w3c/vcalm#263, by @dlongley.
-
Enable transaction identifiers to be multibase encoded 128-bit numbers. w3c/vcalm#262, by @msporny.
-
Refactor non-normative workflow explanation to "exchange" explanation. w3c/vcalm#261, by @msporny.
-
Refactor presentation endpoints into exchange endpoints w3c/vcalm#258, by @msporny.
-
-
3 pull requests merged.
-
Refactor presentation endpoints into exchange endpoints w3c/vcalm#258.
-
4 pull requests received 83 new comments.
-
Refactor presentation endpoints into exchange endpoints w3c/vcalm#258 (56 comments by @mkhraisha, @mprorock, @msporny, @OR13)
-
Enable transaction identifiers to be multibase encoded 128-bit numbers. w3c/vcalm#262 (19 comments by @mavarley, @msporny, @OR13, @peacekeeper)
-
Remove issue VC option to change verification method. w3c/vcalm#263 (6 comments by @dlongley, @OR13, @peacekeeper)
-
w3c/vc-data-model
-
3 issues opened.
-
Diagram issues w3c/vc-data-model#873, by @davidlehn.
-
Missing context in an example? w3c/vc-data-model#871, by @iherman.
-
Update LD-PROOF link to point to DATA-INTEGRITY w3c/vc-data-model#869, by @msporny.
-
-
2 issues closed.
-
Add details about difference between contexts and credentialSchemas property w3c/vc-data-model#781.
-
Update LD-PROOF link to point to DATA-INTEGRITY w3c/vc-data-model#869.
-
-
2 issues reopened.
-
Make images consistent w3c/vc-data-model#865, by @davidlehn.
-
[Tracking Issue - Proposed Corrections Feedback] URL to URI w3c/vc-data-model#862, by @kdenhartog.
-
-
6 issues received 18 new comments.
-
Default vocab for credentials context v2 w3c/vc-data-model#753 (7 comments by @dlongley, @mavarley, @mprorock, @selfissued, @TallTed, @tplooker)
-
Update LD-PROOF link to point to DATA-INTEGRITY w3c/vc-data-model#869 (3 comments by @kdenhartog, @msporny)
-
w3c/vc-data-model#863 (1 comment by @iherman)
-
Is there a solution of zero knowledge proof for secp256k1 curve? w3c/vc-data-model#861 (1 comment by @msporny)
-
-
2 pull requests opened.
-
Update example 20 w3c/vc-data-model#872, by @David-Chadwick.
-
Updating References in the note on transitive trust w3c/vc-data-model#868, by @shigeya.
-
-
4 pull requests merged.
-
Update example 20 w3c/vc-data-model#872.
-
add section to differentiate between contexts and credential Schemas w3c/vc-data-model#847.
-
Updating References in the note on transitive trust w3c/vc-data-model#868.
-
address clarification that the URI can be used to retrieve data w3c/vc-data-model#866.
-
-
1 pull request closed.
-
Create SECURITY.md w3c/vc-data-model#854.
-
-
5 pull requests received 80 new comments.
-
add section to differentiate between contexts and credential Schemas w3c/vc-data-model#847 (69 comments by @David-Chadwick, @iherman, @kdenhartog, @msporny, @TallTed)
-
address clarification that the URI can be used to retrieve data w3c/vc-data-model#866 (7 comments by @brentzundel, @iherman, @jyasskin, @msporny)
-
Updating References in the note on transitive trust w3c/vc-data-model#868 (2 comments by @iherman, @msporny)
-
w3c/vc-test-suite
-
1 issue opened.
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134, by @OR13.
-
-
2 issues received 13 new comments.
-
[Tracking Issue - Proposed Corrections Feedback] Test suite improvements are needed w3c/vc-test-suite#126 (8 comments by @brentzundel, @bumblefudge, @clehner, @iherman, @jyasskin)
-
Evidence extension point (was: Improve tests for Evidence) w3c/vc-test-suite#134 (5 comments by @jandrieu, @OR13)
-
-
1 pull request opened.
-
Update ZKP tests for changes in VC Data Model v1.1 w3c/vc-test-suite#127, by @clehner.
-
-
2 pull requests received 15 new comments.
-
Update ZKP tests for changes in VC Data Model v1.1 w3c/vc-test-suite#127 (4 comments by @clehner, @iherman, @TallTed)
w3c/vc-di-ed25519signature2020-test-suite
-
3 issues opened.
-
This should explicitly request a "Ed25519Signature2020" proof w3c/vc-di-ed25519signature2020-test-suite#4, by @peacekeeper.
-
"checks" option isn't supported by VC API w3c/vc-di-ed25519signature2020-test-suite#3, by @peacekeeper.
-
Shouldn't this be part of the VC API test suite? w3c/vc-di-ed25519signature2020-test-suite#2, by @peacekeeper.
-
-
3 issues received 7 new comments.
-
This should explicitly request a "Ed25519Signature2020" proof w3c/vc-di-ed25519signature2020-test-suite#4 (3 comments by @aljones15, @msporny, @OR13)
-
Shouldn't this be part of the VC API test suite? w3c/vc-di-ed25519signature2020-test-suite#2 (3 comments by @msporny, @OR13)
-
"checks" option isn't supported by VC API w3c/vc-di-ed25519signature2020-test-suite#3 (1 comment by @msporny)
-
w3c/vc-di-ecdsa
-
1 issue opened.
-
Was this really created in 2019? w3c/vc-di-ecdsa#1, by @peacekeeper.
-
-
1 pull request opened.
-
Fix encoding of P-384 public key w3c/vc-di-ecdsa#2, by @peacekeeper.
-
-
1 pull request merged.
-
Fix encoding of P-384 public key w3c/vc-di-ecdsa#2.
-
-
1 pull request received 3 new comments.
w3c/vc-bitstring-status-list-test-suite
-
1 issue opened.
-
Shouldn't this be part of the VC API test suite? w3c/vc-bitstring-status-list-test-suite#4, by @peacekeeper.
-
-
3 pull requests opened.
-
Revoke credential test w3c/vc-bitstring-status-list-test-suite#3, by @JSAssassin.
-
Add static test credentials w3c/vc-bitstring-status-list-test-suite#2, by @JSAssassin.
-
Initial w3c/vc-bitstring-status-list-test-suite#1, by @JSAssassin.
-
-
2 pull requests merged.
-
Revoke credential test w3c/vc-bitstring-status-list-test-suite#3.
-
Add static test credentials w3c/vc-bitstring-status-list-test-suite#2.
-
-
1 pull request received 1 new comment.
w3c/vc-bitstring-status-list
-
1 issue closed.
-
Need clarification on compression algorithm & container used w3c/vc-bitstring-status-list#13.
-
-
1 issue received 1 new comment.
-
Need clarification on compression algorithm & container used w3c/vc-bitstring-status-list#13 (1 comment by @thehenrytsai)
-
-
3 pull requests opened.
-
add mkhraisha as codeowner/editor w3c/vc-bitstring-status-list#20, by @mkhraisha.
-
add mprorock as an editor w3c/vc-bitstring-status-list#19, by @mprorock.
-
Update index.html w3c/vc-bitstring-status-list#18, by @OR13.
-
-
3 pull requests merged.
-
add mkhraisha as codeowner/editor w3c/vc-bitstring-status-list#20.
-
add mprorock as an editor w3c/vc-bitstring-status-list#19.
-
Update index.html w3c/vc-bitstring-status-list#18.
-
w3c/vc-imp-guide
-
1 issue opened.
-
Are there any open-source reference implementations of this spec? w3c/vc-imp-guide#63, by @ravi-prakash-v.
-
w3c/vc-data-integrity
-
1 issue received 2 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (2 comments by @lemoustachiste, @msporny)
-
w3c/vc-di-bbs
-
1 issue received 1 new comment.
Past meetings
Participants
-
4 participants joined.
-
David Waite (Ping Identity) joined.
-
Michael Klein (Spruce Systems, Inc.) joined.
-
Michael Jones (W3C Invited Experts) joined.
-
Kristina Yasuda (Microsoft Corporation) joined.
-
-
1 participant left.
-
Michael Herman (W3C Invited Experts) left.
-
-
1 organization joined.
-
Microsoft Corporation joined.
-
GitHub
w3c/vc-wg-charter
-
14 issues opened.
-
v2 Test Suite w3c/vc-wg-charter#64, by @OR13.
-
Data Integrity Crypto Suite Registry w3c/vc-wg-charter#62, by @OR13.
-
More narrative description/ background w3c/vc-wg-charter#59, by @samuelweiler.
-
Success criteria ??? w3c/vc-wg-charter#58, by @samuelweiler.
-
Data model or models w3c/vc-wg-charter#57, by @samuelweiler.
-
Draft state for Verifiable Credential Data Integrity 1.0? w3c/vc-wg-charter#56, by @samuelweiler.
-
Add charter history w3c/vc-wg-charter#55, by @samuelweiler.
-
Update the Verifiable Credential Data Integrity 1.0 section w3c/vc-wg-charter#54, by @OR13.
-
expand acronyms on first use w3c/vc-wg-charter#53, by @samuelweiler.
-
clarify IETF liaison w3c/vc-wg-charter#52, by @samuelweiler.
-
Standardizing PGP for Linked Data Integrity w3c/vc-wg-charter#48, by @OR13.
-
Standardizing MultiKey2021 w3c/vc-wg-charter#46, by @OR13.
-
Standardizing JsonWebSignature2020 / JsonWebKey2020 w3c/vc-wg-charter#45, by @OR13.
-
Multilingual support for selecting a image file w3c/vc-wg-charter#38, by @shigeya.
-
-
2 issues closed.
-
Fixing problems identified through using the 1.0 and 1.1 specs must be in scope w3c/vc-wg-charter#22.
-
-
2 issues reopened.
-
Protocols and APIs should remain out of scope w3c/vc-wg-charter#24, by @brentzundel.
-
Fixing problems identified through using the 1.0 and 1.1 specs must be in scope w3c/vc-wg-charter#22, by @brentzundel.
-
-
16 issues received 49 new comments.
-
Protocols and APIs should remain out of scope w3c/vc-wg-charter#24 (9 comments by @brentzundel, @iherman, @OR13, @Sakurann)
-
Multilingual support for selecting a image file w3c/vc-wg-charter#38 (6 comments by @iherman, @shigeya)
-
Draft state for Verifiable Credential Data Integrity 1.0? w3c/vc-wg-charter#56 (4 comments by @iherman, @samuelweiler)
-
Standardizing PGP for Linked Data Integrity w3c/vc-wg-charter#48 (4 comments by @mprorock, @OR13, @wyc)
-
Standardizing JsonWebSignature2020 / JsonWebKey2020 w3c/vc-wg-charter#45 (3 comments by @iherman, @mprorock, @selfissued)
-
Update the Verifiable Credential Data Integrity 1.0 section w3c/vc-wg-charter#54 (2 comments by @bumblefudge, @selfissued)
-
Verifiable Credential Linked Data Integrity work should happen in a Linked Data working group w3c/vc-wg-charter#21 (2 comments by @brentzundel, @iherman)
-
Fixing problems identified through using the 1.0 and 1.1 specs must be in scope w3c/vc-wg-charter#22 (1 comment by @brentzundel)
-
-
14 pull requests opened.
-
Add ECDSA secpr1 cryptosuite to VCWG input documents. w3c/vc-wg-charter#63, by @msporny.
-
Proposed work mode for charter development w3c/vc-wg-charter#61, by @brentzundel.
-
Clarified data model and sub parts w3c/vc-wg-charter#60, by @brentzundel.
-
to allow for multibase support in the VCDI spec w3c/vc-wg-charter#51, by @bumblefudge.
-
Add a possible reference for pgp as a cryptosuite w3c/vc-wg-charter#50, by @mprorock.
-
Align with the latest W3C charter template w3c/vc-wg-charter#49, by @iherman.
-
Linked Data Signatures for JWS w3c/vc-wg-charter#47, by @mprorock.
-
Extending support for resources in general w3c/vc-wg-charter#44, by @shigeya.
-
Specification of APIs or protocols is out of scope w3c/vc-wg-charter#43, by @selfissued.
-
Unambiguously state that fixing problems is in scope w3c/vc-wg-charter#42, by @selfissued.
-
Add second chair information w3c/vc-wg-charter#41, by @brentzundel.
-
re-tweaked cryptosuite deliverables w3c/vc-wg-charter#40, by @TallTed.
-
Update link to Data Integrity draft CCG spec w3c/vc-wg-charter#39, by @peacekeeper.
-
Add concrete cryptosuites to deliverables. w3c/vc-wg-charter#37, by @msporny.
-
-
5 pull requests merged.
-
Unambiguously state that fixing problems is in scope w3c/vc-wg-charter#42.
-
Add second chair information w3c/vc-wg-charter#41.
-
re-tweaked cryptosuite deliverables w3c/vc-wg-charter#40.
-
Add concrete cryptosuites to deliverables. w3c/vc-wg-charter#37.
-
Update link to Data Integrity draft CCG spec w3c/vc-wg-charter#39.
-
-
12 pull requests received 129 new comments.
-
Specification of APIs or protocols is out of scope w3c/vc-wg-charter#43 (36 comments by @brentzundel, @iherman, @kdenhartog, @msporny, @nadalin, @OR13, @Sakurann, @selfissued)
-
Add concrete cryptosuites to deliverables. w3c/vc-wg-charter#37 (24 comments by @iherman, @msporny, @peacekeeper, @TallTed)
-
Linked Data Signatures for JWS w3c/vc-wg-charter#47 (23 comments by @brentzundel, @csuwildcat, @iherman, @kdenhartog, @kdenhartog-mattr, @mprorock, @msporny, @OR13, @quartzjer, @selfissued)
-
Extending support for resources in general w3c/vc-wg-charter#44 (16 comments by @David-Chadwick, @iherman, @msporny, @Sakurann, @shigeya)
-
Add a possible reference for pgp as a cryptosuite w3c/vc-wg-charter#50 (9 comments by @mprorock, @msporny, @OR13)
-
Align with the latest W3C charter template w3c/vc-wg-charter#49 (9 comments by @iherman, @Sakurann, @samuelweiler)
-
Add second chair information w3c/vc-wg-charter#41 (3 comments by @brentzundel, @David-Chadwick, @iherman)
-
Add ECDSA secpr1 cryptosuite to VCWG input documents. w3c/vc-wg-charter#63 (2 comments by @msporny, @OR13)
-
Proposed work mode for charter development w3c/vc-wg-charter#61 (2 comments by @brentzundel, @msporny)
-
w3c/vcalm
-
2 issues opened.
-
Should workflow `id`s and `name`s be provided in the URL or POST body? w3c/vcalm#256, by @msporny.
-
5 issues closed.
-
readme not clear on purpose or contribution guidelines w3c/vcalm#101.
-
Plugfest March 2021 Feature freeze date w3c/vcalm#93.
-
Enable HTTP requests to specify optional verification checks w3c/vcalm#104.
-
11 issues received 24 new comments.
-
Should workflow `id`s and `name`s be provided in the URL or POST body? w3c/vcalm#256 (5 comments by @msporny, @OR13)
-
PROPOSAL: Interactive Issue and Re-Issue VC API flow w3c/vcalm#245 (4 comments by @msporny, @OR13, @peacekeeper)
-
case 2 verifiable presentation has id IRI with two hash marks w3c/vcalm#155 (2 comments by @clehner, @peacekeeper)
-
Define /.well-known endpoint for an API to advertise optional features supported w3c/vcalm#91 (2 comments by @bumblefudge, @msporny)
-
Enable HTTP requests to specify optional verification checks w3c/vcalm#104 (2 comments by @msporny, @peacekeeper)
-
with the latest test additions it is not clear how to add a test w3c/vcalm#105 (1 comment by @msporny)
-
-
2 pull requests opened.
-
Define Workflow APIs w3c/vcalm#255, by @msporny.
-
Add section on automation via workflows. w3c/vcalm#254, by @msporny.
-
-
3 pull requests merged.
-
Define Workflow APIs w3c/vcalm#255.
-
Add section on automation via workflows. w3c/vcalm#254.
-
Remove verificationMethod from VerifyOptions w3c/vcalm#253.
-
-
3 pull requests received 64 new comments.
-
Add section on automation via workflows. w3c/vcalm#254 (30 comments by @msporny, @OR13, @peacekeeper, @TallTed)
w3c/vc-data-model
-
5 issues opened.
-
example.edu is not a reserved name w3c/vc-data-model#867, by @mcr.
-
Make images consistent w3c/vc-data-model#865, by @chaals.
-
Is there a solution of zero knowledge proof for secp256k1 curve? w3c/vc-data-model#861, by @picardcapt1212.
-
Determine interoperable way for Holder to make claims directly in VPs w3c/vc-data-model#860, by @jandrieu.
-
Missing Referenced ld-proofs : https://w3c-ccg.github.io/ld-proofs/ w3c/vc-data-model#858, by @jaroslavsaxa.
-
-
6 issues closed.
-
example.edu is not a reserved name w3c/vc-data-model#867.
-
Missing Referenced ld-proofs : https://w3c-ccg.github.io/ld-proofs/ w3c/vc-data-model#858.
-
Fix the JWT encoding in the examples w3c/vc-data-model#838.
-
Update github link to use TR instead of github.io w3c/vc-data-model#852.
-
Optimized SVG diagrams w3c/vc-data-model#721.
-
-
13 issues received 50 new comments.
-
Default vocab for credentials context v2 w3c/vc-data-model#753 (18 comments by @dlongley, @mprorock, @msporny, @OR13, @peacekeeper, @TallTed, @tplooker, @VladimirAlexiev)
-
Remove `@version` from v2 context w3c/vc-data-model#843 (7 comments by @dlongley, @OR13, @VladimirAlexiev)
-
Question: Using Refresh Service Property to update a credential when Credential Subject has a new field w3c/vc-data-model#820 (4 comments by @alenhorvat, @msporny, @TallTed)
-
Can a credentialSubject be only a string value? w3c/vc-data-model#762 (3 comments by @mwherman2000, @peacekeeper)
-
Update github link to use TR instead of github.io w3c/vc-data-model#852 (2 comments by @iherman, @kdenhartog)
-
Definition of issuanceDate property (and its mapping to JWT claims) w3c/vc-data-model#844 (1 comment by @alenhorvat)
-
Determine if JWT pre-signed intermediate-mode output should be in every example in the specification. w3c/vc-data-model#836 (1 comment by @msporny)
-
-
3 pull requests opened.
-
address clarification that the URI can be used to retrieve data w3c/vc-data-model#866, by @kdenhartog.
-
Rename "Linked Data Proofs" to "Data Integrity". w3c/vc-data-model#859, by @peacekeeper.
-
Edit of Proof Format section w3c/vc-data-model#857, by @David-Chadwick.
-
-
3 pull requests merged.
-
Edit of Proof Format section w3c/vc-data-model#857.
-
Rename "Linked Data Proofs" to "Data Integrity". w3c/vc-data-model#859.
-
Chaals more diagrams w3c/vc-data-model#855.
-
-
1 pull request closed.
-
Optimize diagrams. w3c/vc-data-model#851.
-
-
6 pull requests received 77 new comments.
-
Chaals more diagrams w3c/vc-data-model#855 (45 comments by @brentzundel, @chaals, @davidlehn, @dlongley, @iherman, @kdenhartog)
-
add section to differentiate between contexts and credential Schemas w3c/vc-data-model#847 (19 comments by @David-Chadwick, @iherman, @kdenhartog, @kdenhartog-mattr, @msporny, @TallTed)
-
address clarification that the URI can be used to retrieve data w3c/vc-data-model#866 (4 comments by @brentzundel, @kdenhartog, @msporny)
-
Edit of Proof Format section w3c/vc-data-model#857 (4 comments by @David-Chadwick, @dlongley, @iherman, @kdenhartog)
-
Rename "Linked Data Proofs" to "Data Integrity". w3c/vc-data-model#859 (4 comments by @iherman, @kdenhartog, @nikosft, @peacekeeper)
-
w3c/vc-jws-2020
-
1 issue received 1 new comment.
w3c/vc-bitstring-status-list
-
4 issues opened.
-
Add vocabulary document w3c/vc-bitstring-status-list#17, by @msporny.
-
Need examples in the specification w3c/vc-bitstring-status-list#16, by @msporny.
-
Can the spec relax/remove the requirement on minimal bit length? w3c/vc-bitstring-status-list#14, by @thehenrytsai.
-
Need clarification on compression algorithm & container used w3c/vc-bitstring-status-list#13, by @thehenrytsai.
-
-
1 issue closed.
-
Context file/URL w3c/vc-bitstring-status-list#10.
-
-
3 issues received 4 new comments.
-
Need clarification on compression algorithm & container used w3c/vc-bitstring-status-list#13 (1 comment by @clehner)
-
1 pull request opened.
-
Update context w3c/vc-bitstring-status-list#15, by @JSAssassin.
-
-
1 pull request merged.
-
Update context w3c/vc-bitstring-status-list#15.
-
-
1 pull request received 26 new comments.
-
Update context w3c/vc-bitstring-status-list#15 (26 comments by @dlongley, @dmitrizagidulin, @JSAssassin, @msporny, @OR13)
-
w3c/vc-test-suite
-
1 issue opened.
-
[Tracking Issue - Proposed Corrections Feedback] Test suite improvements are needed w3c/vc-test-suite#126, by @brentzundel.
-
-
1 issue closed.
-
New w3c/vc-test-suite#124.
-
-
2 issues received 2 new comments.
-
[Tracking Issue - Proposed Corrections Feedback] Test suite improvements are needed w3c/vc-test-suite#126 (1 comment by @iherman)
-
-
1 pull request opened.
-
Fix link to VC Data Model w3c/vc-test-suite#125, by @clehner.
-
-
1 pull request received 1 new comment.
w3c/vc-data-integrity
-
2 issues received 3 new comments.
-
proofChain property violates VC data model requirement w3c/vc-data-integrity#26 (2 comments by @Exulansis, @lemoustachiste)
-
Example that demonstrates input(s) and what gets fed to the signature algorithms? w3c/vc-data-integrity#19 (1 comment by @DePasqualeOrg)
-
w3c/vc-json-schema
-
1 issue opened.
-
JSON-LD cannot validate, only JSON Schema can w3c/vc-json-schema#88, by @VladimirAlexiev.
-
-
2 issues received 5 new comments.
-
JSON-LD cannot validate, only JSON Schema can w3c/vc-json-schema#88 (3 comments by @thereisnogabe, @VladimirAlexiev)
-
Why do we need two schema system/languages? w3c/vc-json-schema#16 (2 comments by @TallTed, @VladimirAlexiev)
-
w3c/vc-di-ed25519signature2020-test-suite
-
1 pull request opened.
-
Initial w3c/vc-di-ed25519signature2020-test-suite#1, by @aljones15.
-
w3c/vc-jose-cose
-
1 issue opened.
-
Support for multiple signatures w3c/vc-jose-cose#6, by @David-Chadwick.
-
-
1 issue received 1 new comment.
w3c/vc-di-bbs
-
1 issue opened.
-
Cross linked to ZKP-LD Playground w3c/vc-di-bbs#64, by @OR13.
-