- From: W3C Webmaster via GitHub API <sysbot+gh@w3.org>
- Date: Mon, 03 Jul 2023 17:01:19 +0000
- To: public-credentials@w3.org
- Message-Id: <E1qGMvP-0016QU-H3@uranus.w3.org>
Issues
------
* w3c/vc-data-model (+3/-15/💬96)
3 issues created:
- Provide guidance for when hash values do not match specification text (by msporny)
https://github.com/w3c/vc-data-model/issues/1177
- Define what a credential validity does mean (by filip26)
https://github.com/w3c/vc-data-model/issues/1176
- Ensure the base context doesn't constrain lower-maturity specifications (by jyasskin)
https://github.com/w3c/vc-data-model/issues/1175
38 issues received 96 new comments:
- #1176 Define what a credential validity does mean (10 by OR13, andresuribe87, brentzundel, filip26, jandrieu)
https://github.com/w3c/vc-data-model/issues/1176
- #1175 Ensure the base context doesn't constrain lower-maturity specifications (4 by OR13, mprorock, selfissued)
https://github.com/w3c/vc-data-model/issues/1175
- #1173 Entities and Parties (4 by OR13, RieksJ, TallTed)
https://github.com/w3c/vc-data-model/issues/1173
- #1169 Consider removing Use Cases summary from core DM (4 by OR13, brentzundel, msporny)
https://github.com/w3c/vc-data-model/issues/1169
- #1165 Add language that there is generally no relationship between a VP and their VCs other than integrity protection (2 by awoie, brentzundel)
https://github.com/w3c/vc-data-model/issues/1165
- #1162 consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` (4 by OR13, TallTed, awoie)
https://github.com/w3c/vc-data-model/issues/1162
- #1150 Protected term errors when supporting v1 and v2 (5 by OR13, TallTed, iherman)
https://github.com/w3c/vc-data-model/issues/1150 [before-CR]
- #1148 Check status privacy (3 by OR13, brentzundel, iherman)
https://github.com/w3c/vc-data-model/issues/1148 [post-CR]
- #1145 Respec VC plugin is breaking the build (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1145 [pending close]
- #1136 Collusion, i.e. collaboration, between Alice and Bob (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1136 [pending close]
- #1135 Add VC-JWT diagrams to core specification (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/1135 [post-CR]
- #1134 Should we bundle contexts for credentialSchema and credentialStatus int he v2 core context? (5 by OR13, decentralgabe, iherman)
https://github.com/w3c/vc-data-model/issues/1134 [before-CR]
- #1126 Address "Credential" vs "VerifiableCredential" (2 by OR13, brentzundel)
https://github.com/w3c/vc-data-model/issues/1126
- #1125 Remove reference toCredentialManagerPresentation (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1125 [pr exists] [before-CR]
- #1123 Remove reference to OdrlPolicy2017 (2 by iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1123 [pr exists] [before-CR]
- #1117 VC Vocabulary v2.0 does not have any term definitions (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1117 [before-CR]
- #1103 Vocabulary normative, context isn't? (2 by brentzundel, msporny)
https://github.com/w3c/vc-data-model/issues/1103 [discuss]
- #1089 Why does the Data Model context file define a DataIntegrityProof RDF class? (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/1089 [before-CR]
- #1077 Remove normative statements from vocab (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1077 [pending close]
- #1048 Media types other than vc+ld+json (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1048 [ready for PR] [media-type] [before-CR]
- #1040 Guidance on `application/ld+json` (2 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/1040 [ready for PR] [media-type] [priority] [before-CR]
- #1031 Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/1031 [pending close] [discuss]
- #1029 Describe how JSON-LD framing is used with Selective Disclosure (8 by OR13, dlongley, iherman, msporny)
https://github.com/w3c/vc-data-model/issues/1029 [discuss] [before-CR]
- #1027 Add guidance on ignoring optional fields (4 by OR13, awoie, brentzundel, dlongley)
https://github.com/w3c/vc-data-model/issues/1027 [ready for PR] [before-CR]
- #1010 `termsOfUse` is insufficiently specified (1 by iherman)
https://github.com/w3c/vc-data-model/issues/1010 [conversation] [directory] [before-CR]
- #1009 Clarifying credential from verifiable credential (1 by OR13)
https://github.com/w3c/vc-data-model/issues/1009 [editorial] [ready for PR] [terminology] [before-CR]
- #991 Clarify credentialStatus (3 by David-Chadwick, OR13, iherman)
https://github.com/w3c/vc-data-model/issues/991 [discuss] [status] [before-CR]
- #988 Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/988 [pending close] [discuss] [holder-binding] [blocked]
- #984 Verifier Role Confusion (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/984 [question] [pending close] [terminology]
- #965 'issued' vs. 'validFrom' (formerly 'issuanceDate') (1 by filip26)
https://github.com/w3c/vc-data-model/issues/965 [ready for PR] [before-CR]
- #950 Verification of multiple credential schemas (2 by OR13, decentralgabe)
https://github.com/w3c/vc-data-model/issues/950 [discuss] [schema]
- #942 Create the new role of issuee (4 by David-Chadwick, OR13, TallTed, brentzundel)
https://github.com/w3c/vc-data-model/issues/942 [discuss] [terminology]
- #938 Indicating Encrypted VCs in VPs (1 by OR13)
https://github.com/w3c/vc-data-model/issues/938 [ready for PR] [discuss] [before-CR]
- #908 Describe SD-JWT as an alternative for selective disclosure (1 by Sakurann)
https://github.com/w3c/vc-data-model/issues/908 [pending close]
- #902 Define "prover" in addition to "holder". (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/902 [pending close] [discuss] [terminology]
- #887 What is the action associated with issuing/creating a Verifiable Presentation? (2 by OR13, awoie)
https://github.com/w3c/vc-data-model/issues/887 [ready for PR] [post-CR]
- #881 `proof` in `@context` and the use of `@container` (3 by OR13, iherman)
https://github.com/w3c/vc-data-model/issues/881 [before-CR]
- #821 "bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders (1 by brentzundel)
https://github.com/w3c/vc-data-model/issues/821 [clarification] [pending close] [holder-binding] [terminology]
15 issues closed:
- Add language that there is generally no relationship between a VP and their VCs other than integrity protection https://github.com/w3c/vc-data-model/issues/1165
- Remove reference to OdrlPolicy2017 https://github.com/w3c/vc-data-model/issues/1123 [pr exists] [before-CR]
- Remove reference to DocumentVerification2018 https://github.com/w3c/vc-data-model/issues/1124 [pr exists]
- Remove reference toCredentialManagerPresentation https://github.com/w3c/vc-data-model/issues/1125 [pr exists] [before-CR]
- consider changing all mentions of misnamed `holder binding` to something like `authorized presenter list` https://github.com/w3c/vc-data-model/issues/1162
- Presentations SHOULD expire https://github.com/w3c/vc-data-model/issues/937 [pr exists]
- Remove normative statements from vocab https://github.com/w3c/vc-data-model/issues/1077 [pending close]
- Collusion, i.e. collaboration, between Alice and Bob https://github.com/w3c/vc-data-model/issues/1136 [pending close]
- Respec VC plugin is breaking the build https://github.com/w3c/vc-data-model/issues/1145 [pending close]
- "bound"/"binding" terminology is a significantly stronger relationship than is actually present between VCs and their Subjects *or* Holders https://github.com/w3c/vc-data-model/issues/821 [clarification] [pending close] [holder-binding] [terminology]
- Define "prover" in addition to "holder". https://github.com/w3c/vc-data-model/issues/902 [pending close] [discuss] [terminology]
- Verifier Role Confusion https://github.com/w3c/vc-data-model/issues/984 [question] [pending close] [terminology]
- Holder-Binding: Needs Privacy & Correlation, Centralization/Lock-in Considerations https://github.com/w3c/vc-data-model/issues/988 [pending close] [discuss] [holder-binding] [blocked]
- Make `verifiable-credential.id` & `verifiable-presentation.id` REQUIRED. https://github.com/w3c/vc-data-model/issues/1031 [pending close] [discuss]
- Respec VC plugin is breaking the build https://github.com/w3c/vc-data-model/issues/1145
* w3c/vc-use-cases (+0/-0/💬1)
1 issues received 1 new comments:
- #146 Chain of GS1 credentials to identify a trade item (1 by jandrieu)
https://github.com/w3c/vc-use-cases/issues/146
* w3c/vc-data-integrity (+0/-1/💬12)
11 issues received 12 new comments:
- #37 URLs in current editors draft all seem to be invalid (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/37
- #34 nonce property (2 by msporny)
https://github.com/w3c/vc-data-integrity/issues/34 [question]
- #30 either nonce or challenge is redundant (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/30
- #29 domain should be a string or array (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/29
- #27 What attributes are included in proof options? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/27
- #26 proofChain property violates VC data model requirement (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/26
- #24 Mentioning how to retrieve the public key (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/24
- #16 Which options are "input options"? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/16
- #14 [EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/14
- #11 serialization, canonicalized values and normalized datasets (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/11
- #3 Authenticity checks (1 by msporny)
https://github.com/w3c/vc-data-integrity/issues/3
1 issues closed:
- Mentioning how to retrieve the public key https://github.com/w3c/vc-data-integrity/issues/24
* w3c/vc-jws-2020 (+0/-11/💬0)
11 issues closed:
- Naming of work https://github.com/w3c/vc-jws-2020/issues/31
- Move conformance section https://github.com/w3c/vc-jws-2020/issues/27
- Re-use `proofValue` from DataIntegrityProof instead of `jws` https://github.com/w3c/vc-jws-2020/issues/25 [blocked-by-data-integrity]
- Ensure all IRIs for terms are resolvable https://github.com/w3c/vc-jws-2020/issues/23
- Anti-pattern: Excessive algorithm agility https://github.com/w3c/vc-jws-2020/issues/20 [pending-close]
- Add links to testsuite https://github.com/w3c/vc-jws-2020/issues/18 [help wanted]
- Restrict secp*r1 curves https://github.com/w3c/vc-jws-2020/issues/16 [pending-close]
- Rename to `di-jws-2020` ? https://github.com/w3c/vc-jws-2020/issues/5
- Add `@vocab` to the context https://github.com/w3c/vc-jws-2020/issues/4
- Define all fields of `publicKeyJwk` https://github.com/w3c/vc-jws-2020/issues/3
- PROPOSAL: Host test vectors as a single json file in this repo https://github.com/w3c/vc-jws-2020/issues/2
* w3c/vc-jwt (+3/-7/💬48)
3 issues created:
- Deprecate `vc` & `vp` ? (by OR13)
https://github.com/w3c/vc-jwt/issues/119
- Describe SD-JWT as an alternative for selective disclosure (by Sebastian-Elfors-IDnow)
https://github.com/w3c/vc-jwt/issues/118
- how is `kid` to be `useful to distinguish the specific key used`? (by TallTed)
https://github.com/w3c/vc-jwt/issues/117
36 issues received 48 new comments:
- #117 how is `kid` to be `useful to distinguish the specific key used`? (1 by OR13)
https://github.com/w3c/vc-jwt/issues/117
- #110 Address VP Token interop (8 by OR13, Sakurann, TallTed, andresuribe87, mprorock)
https://github.com/w3c/vc-jwt/issues/110
- #99 consider adding registered claims VC-JWT to explainer (1 by OR13)
https://github.com/w3c/vc-jwt/issues/99
- #71 Update `application/vc+ld+jwt` (1 by OR13)
https://github.com/w3c/vc-jwt/issues/71
- #69 Add guidance on mapping to the core data model (1 by OR13)
https://github.com/w3c/vc-jwt/issues/69 [pending-close]
- #66 (English) references to the VCDM spec are wrong in the 1.1 section (1 by OR13)
https://github.com/w3c/vc-jwt/issues/66
- #65 Why do we have a v1.1 in this specification? (1 by OR13)
https://github.com/w3c/vc-jwt/issues/65 [pending-close]
- #64 How to include credential metadata in vc + jwt encoding (2 by David-Chadwick, OR13)
https://github.com/w3c/vc-jwt/issues/64 [pending-close]
- #62 Add guidance on what to do id `proof` is present in VC-JWT (1 by OR13)
https://github.com/w3c/vc-jwt/issues/62
- #57 Change `typ` values for JSON-LD claim sets? (2 by OR13)
https://github.com/w3c/vc-jwt/issues/57
- #53 F2F mapping converstation (1 by OR13)
https://github.com/w3c/vc-jwt/issues/53
- #49 Change spec name? (1 by OR13)
https://github.com/w3c/vc-jwt/issues/49
- #47 Provide guidance on use of `cty` in JOSE / COSE (1 by OR13)
https://github.com/w3c/vc-jwt/issues/47
- #46 Replace reference to jwt.io with embedded example (1 by OR13)
https://github.com/w3c/vc-jwt/issues/46
- #43 clearer wording for step 2 (1 by OR13)
https://github.com/w3c/vc-jwt/issues/43
- #42 Bikeshedding the name for the `vc-jwt` 1.1 `cty` value. (2 by OR13, dlongley)
https://github.com/w3c/vc-jwt/issues/42 [pending-close]
- #39 JWT exp claim (1 by OR13)
https://github.com/w3c/vc-jwt/issues/39
- #38 Update language to align with v2 resolutions (1 by OR13)
https://github.com/w3c/vc-jwt/issues/38
- #37 Address the `alg` language per the comment here (2 by OR13)
https://github.com/w3c/vc-jwt/issues/37 [pending-close]
- #36 How best to describe the VC-JWT Production Rules (1 by OR13)
https://github.com/w3c/vc-jwt/issues/36
- #35 Should we comment on "principle"? (1 by OR13)
https://github.com/w3c/vc-jwt/issues/35
- #28 Determine whether to include content from Verifiable Credentials Implementation Guidelines (1 by OR13)
https://github.com/w3c/vc-jwt/issues/28
- #27 Respec warnings and errors (1 by OR13)
https://github.com/w3c/vc-jwt/issues/27
- #26 Security Considerations section empty (1 by OR13)
https://github.com/w3c/vc-jwt/issues/26
- #25 Privacy Considerations section empty (1 by OR13)
https://github.com/w3c/vc-jwt/issues/25
- #23 Confusing text about "If no JWS is present" (1 by OR13)
https://github.com/w3c/vc-jwt/issues/23
- #22 Clarify relationship between "iss" and "issuer" (1 by OR13)
https://github.com/w3c/vc-jwt/issues/22
- #15 Describe why core data model members are translated to JWT claims (1 by OR13)
https://github.com/w3c/vc-jwt/issues/15
- #14 Various discussion points for VC-JWT Specification (1 by OR13)
https://github.com/w3c/vc-jwt/issues/14
- #13 Proposal: use did:jwk for testing dids and vc-jwt in the vc-jwt-test-suite (2 by OR13)
https://github.com/w3c/vc-jwt/issues/13
- #12 vc-jws (1 by OR13)
https://github.com/w3c/vc-jwt/issues/12
- #9 Represent issuance time with "iat" rather than "nbf" (1 by OR13)
https://github.com/w3c/vc-jwt/issues/9
- #7 JWT Decoding: expirationDate (1 by OR13)
https://github.com/w3c/vc-jwt/issues/7
- #6 Support for multiple signatures (1 by OR13)
https://github.com/w3c/vc-jwt/issues/6
- #4 clarify that `vc` `vp` claims do not include entire VC/VPs (1 by OR13)
https://github.com/w3c/vc-jwt/issues/4 [discuss]
- #3 No normative statement wrt. JWT encoding of `verifiableCredential` as base64url (1 by OR13)
https://github.com/w3c/vc-jwt/issues/3
7 issues closed:
- JWT Decoding: expirationDate https://github.com/w3c/vc-jwt/issues/7
- Privacy Considerations section empty https://github.com/w3c/vc-jwt/issues/25
- Security Considerations section empty https://github.com/w3c/vc-jwt/issues/26
- Respec warnings and errors https://github.com/w3c/vc-jwt/issues/27
- Update language to align with v2 resolutions https://github.com/w3c/vc-jwt/issues/38
- Replace reference to jwt.io with embedded example https://github.com/w3c/vc-jwt/issues/46
- consider adding registered claims VC-JWT to explainer https://github.com/w3c/vc-jwt/issues/99
* w3c/vc-status-list-2021 (+1/-1/💬1)
1 issues created:
- Security and Privacy Questionnaire (by mkhraisha)
https://github.com/w3c/vc-status-list-2021/issues/77
1 issues received 1 new comments:
- #73 Unify design of status lists to support multi-bit values (1 by dlongley)
https://github.com/w3c/vc-status-list-2021/issues/73
1 issues closed:
- Need examples for how to handle multiple status messages https://github.com/w3c/vc-status-list-2021/issues/66
Pull requests
-------------
* w3c/vc-data-model (+6/-6/💬25)
6 pull requests submitted:
- removing remaining references to JSON (by Sakurann)
https://github.com/w3c/vc-data-model/pull/1182
- Presentations (by brentzundel)
https://github.com/w3c/vc-data-model/pull/1181
- fix typo in vp+ld+json IANA considerations (by brentzundel)
https://github.com/w3c/vc-data-model/pull/1180
- remove 'credential' and 'presentation' from 'type' examples table (by brentzundel)
https://github.com/w3c/vc-data-model/pull/1179
- add vc-json-schema to vocab and context (by decentralgabe)
https://github.com/w3c/vc-data-model/pull/1178
- Updated privacy language in diagram (by andresuribe87)
https://github.com/w3c/vc-data-model/pull/1174
13 pull requests received 25 new comments:
- #1181 Presentations (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1181
- #1180 fix typo in vp+ld+json IANA considerations (1 by davidlehn)
https://github.com/w3c/vc-data-model/pull/1180
- #1174 Updated privacy language in diagram (3 by TallTed, andresuribe87)
https://github.com/w3c/vc-data-model/pull/1174
- #1172 Add "author" and "party" to terminology, rewrite "claim" terminology (4 by OR13, RieksJ, dlongley)
https://github.com/w3c/vc-data-model/pull/1172
- #1171 add issue numbers to at risk extension points (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1171
- #1170 Update example types (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1170
- #1168 made validFrom optional, fixes #1133 (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1168
- #1166 Clean up use-cases summary (2 by brentzundel, msporny)
https://github.com/w3c/vc-data-model/pull/1166
- #1164 Add language clarifying VP is short-lived (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1164
- #1159 Make the vocabulary URLs and values normative (2 by msporny)
https://github.com/w3c/vc-data-model/pull/1159
- #1158 Make the value of the base context normative. (1 by msporny)
https://github.com/w3c/vc-data-model/pull/1158
- #1149 Add graph node identifiers for registered claims (6 by OR13, dlongley)
https://github.com/w3c/vc-data-model/pull/1149
- #1054 Add confidence method to VCDM (1 by awoie)
https://github.com/w3c/vc-data-model/pull/1054 [pending close]
6 pull requests merged:
- add issue numbers to at risk extension points
https://github.com/w3c/vc-data-model/pull/1171
- Update example types
https://github.com/w3c/vc-data-model/pull/1170
- Make the vocabulary URLs and values normative
https://github.com/w3c/vc-data-model/pull/1159
- Clean up use-cases summary
https://github.com/w3c/vc-data-model/pull/1166
- Add language clarifying VP is short-lived
https://github.com/w3c/vc-data-model/pull/1164
- Make the value of the base context normative.
https://github.com/w3c/vc-data-model/pull/1158
* w3c/vc-use-cases (+0/-0/💬3)
2 pull requests received 3 new comments:
- #145 Bona fide shopper (2 by David-Chadwick, TallTed)
https://github.com/w3c/vc-use-cases/pull/145
- #127 Non-transferable use case (1 by David-Chadwick)
https://github.com/w3c/vc-use-cases/pull/127
* w3c/vc-data-integrity (+6/-1/💬2)
6 pull requests submitted:
- Remove outdated issues that have been addressed. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/106
- Fix examples and point to specifications (by msporny)
https://github.com/w3c/vc-data-integrity/pull/105
- Add related links to other specifications. Fix references. (by msporny)
https://github.com/w3c/vc-data-integrity/pull/104
- Update CODEOWNERS to remove myself as I am not an editor on this item (by mprorock)
https://github.com/w3c/vc-data-integrity/pull/103
- Cite Multibase normatively (by jyasskin)
https://github.com/w3c/vc-data-integrity/pull/102
- Update MULTIBASE Reference (by OR13)
https://github.com/w3c/vc-data-integrity/pull/101
2 pull requests received 2 new comments:
- #102 Cite Multibase normatively (1 by msporny)
https://github.com/w3c/vc-data-integrity/pull/102
- #99 Update controller document reference (1 by OR13)
https://github.com/w3c/vc-data-integrity/pull/99
1 pull requests merged:
- Update CODEOWNERS to remove myself as I am not an editor on this item
https://github.com/w3c/vc-data-integrity/pull/103
* w3c/vc-jws-2020 (+0/-1/💬5)
1 pull requests received 5 new comments:
- #33 Withdraw work item (5 by OR13, iherman)
https://github.com/w3c/vc-jws-2020/pull/33
1 pull requests merged:
- Withdraw work item
https://github.com/w3c/vc-jws-2020/pull/33
* w3c/vc-jwt (+5/-3/💬22)
5 pull requests submitted:
- Clarify json ld is not a cwt claimset (by OR13)
https://github.com/w3c/vc-jwt/pull/120
- chore: adjust example titles, nesting, and indents (by mprorock)
https://github.com/w3c/vc-jwt/pull/116
- Change short name to vc-jose-cose (by mprorock)
https://github.com/w3c/vc-jwt/pull/115
- Add sd-jwt example (by OR13)
https://github.com/w3c/vc-jwt/pull/114
- chore: update pre tag indents and lack thereof (by mprorock)
https://github.com/w3c/vc-jwt/pull/113
6 pull requests received 22 new comments:
- #120 Clarify json ld is not a cwt claimset (1 by OR13)
https://github.com/w3c/vc-jwt/pull/120
- #114 Add sd-jwt example (1 by OR13)
https://github.com/w3c/vc-jwt/pull/114
- #113 chore: update pre tag indents and lack thereof (2 by OR13, mprorock)
https://github.com/w3c/vc-jwt/pull/113 [editorial]
- #112 Feature/editorial intro and format (5 by OR13, mprorock)
https://github.com/w3c/vc-jwt/pull/112
- #111 Add comments on key discovery (9 by OR13, TallTed, mprorock)
https://github.com/w3c/vc-jwt/pull/111
- #88 remove securing json (4 by OR13, Sakurann, brentzundel, mprorock)
https://github.com/w3c/vc-jwt/pull/88 [tag-needs-resolution] [pending-wg-review]
3 pull requests merged:
- chore: adjust example titles, nesting, and indents
https://github.com/w3c/vc-jwt/pull/116
- chore: update pre tag indents and lack thereof
https://github.com/w3c/vc-jwt/pull/113 [editorial]
- Feature/editorial intro and format
https://github.com/w3c/vc-jwt/pull/112
* w3c/vc-status-list-2021 (+3/-1/💬4)
3 pull requests submitted:
- fixes example JSON (by mkhraisha)
https://github.com/w3c/vc-status-list-2021/pull/76
- add explainer (by mkhraisha)
https://github.com/w3c/vc-status-list-2021/pull/75
- update contexts in examples to point to v2 (by mprorock)
https://github.com/w3c/vc-status-list-2021/pull/74
3 pull requests received 4 new comments:
- #75 add explainer (1 by mkhraisha)
https://github.com/w3c/vc-status-list-2021/pull/75
- #69 chore: update title and urls to contexts (2 by dlongley, mprorock)
https://github.com/w3c/vc-status-list-2021/pull/69
- #65 Support for multiple status codes (1 by msporny)
https://github.com/w3c/vc-status-list-2021/pull/65
1 pull requests merged:
- Support for multiple status codes
https://github.com/w3c/vc-status-list-2021/pull/65
Repositories tracked by this digest:
-----------------------------------
* https://github.com/w3c/vc-data-model
* https://github.com/w3c/vc-test-suite
* https://github.com/w3c/vc-imp-guide
* https://github.com/w3c/vc-use-cases
* https://github.com/w3c/vc-data-integrity
* https://github.com/w3c/vc-jws-2020
* https://github.com/w3c/vc-jwt
* https://github.com/w3c/vc-status-list-2021
--
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Monday, 3 July 2023 17:01:22 UTC