Verifiable Credentials Working Group - Activity in 2019
No matches.
Participants
-
1 participant left.
-
Daniel Burnett (W3C Invited Experts) left.
-
-
1 organization joined.
-
The Scottish Government joined.
-
GitHub
w3c/vc-data-model
-
2 issues opened.
-
`notTransferable` property not defined in `@context` w3c/vc-data-model#731, by @David-Chadwick.
-
Missing "issuer" property in examples w3c/vc-data-model#729, by @peacekeeper.
-
-
1 pull request opened.
-
fix: Represent "True" as JSON boolean instead w3c/vc-data-model#730, by @confiks.
-
-
1 pull request received 1 new comment.
w3c/vc-test-suite
-
1 issue opened.
-
Invalid base context in example-016-jwt.jwt w3c/vc-test-suite#103, by @kdimak.
-
-
2 issues received 10 new comments.
-
Correct JWK for decoding JWTs tests w3c/vc-test-suite#101 (9 comments by @awoie, @kdimak, @troyronda)
-
-
1 pull request opened.
-
Use Verifiable Credential JWS signed using known JSON WEB Key. w3c/vc-test-suite#102, by @kdimak.
-
w3c/vc-json-schema
-
12 issues opened.
-
Should bikeshed be used to define industry specific contexts w3c/vc-json-schema#21, by @OR13.
-
JSON Schema Canonicalization w3c/vc-json-schema#20, by @thereisnogabe.
-
Example of the credentialSchema.id resolution to schema w3c/vc-json-schema#19, by @troyronda.
-
Summary of "forks" from VC spec w3c/vc-json-schema#18, by @troyronda.
-
Drop `id` DID URI restriction w3c/vc-json-schema#17, by @OR13.
-
Why do we need two schema system/languages? w3c/vc-json-schema#16, by @OR13.
-
Document usage flows w3c/vc-json-schema#14, by @OR13.
-
Fix credential-schema links w3c/vc-json-schema#13, by @OR13.
-
Section on Validation w3c/vc-json-schema#11, by @thereisnogabe.
-
Example verifiable credential w3c/vc-json-schema#9, by @troyronda.
-
Should the non json-ld version have an `@context` w3c/vc-json-schema#7, by @OR13.
-
Move JoseNonLinkedDataSignature2020 to a seperate repo w3c/vc-json-schema#6, by @OR13.
-
-
4 issues closed.
-
Fix credential-schema links w3c/vc-json-schema#13.
-
Example verifiable credential w3c/vc-json-schema#9.
-
fix spec hosting w3c/vc-json-schema#3.
-
Fix proof / JSON-LD compatibility issues w3c/vc-json-schema#2.
-
-
1 issue reopened.
-
fix spec hosting w3c/vc-json-schema#3, by @kimdhamilton.
-
-
13 issues received 43 new comments.
-
Should the non json-ld version have an `@context` w3c/vc-json-schema#7 (4 comments by @OR13, @thereisnogabe)
-
Example of the credentialSchema.id resolution to schema w3c/vc-json-schema#19 (3 comments by @thereisnogabe, @troyronda)
-
Should bikeshed be used to define industry specific contexts w3c/vc-json-schema#21 (1 comment by @msporny)
-
6 pull requests opened.
-
fix cred schema links w3c/vc-json-schema#15, by @thereisnogabe.
-
Add mill cert example w3c/vc-json-schema#12, by @OR13.
-
add vc example + minor fixes w3c/vc-json-schema#10, by @thereisnogabe.
-
bug in create script caused me to miss these files w3c/vc-json-schema#8, by @kimdhamilton.
-
Bikeshed draft w3c/vc-json-schema#5, by @thereisnogabe.
-
Add dockerized bikeshed example w3c/vc-json-schema#4, by @OR13.
-
-
5 pull requests merged.
-
Add mill cert example w3c/vc-json-schema#12.
-
fix cred schema links w3c/vc-json-schema#15.
-
add vc example + minor fixes w3c/vc-json-schema#10.
-
bug in create script caused me to miss these files w3c/vc-json-schema#8.
-
Bikeshed draft w3c/vc-json-schema#5.
-
-
1 pull request closed.
-
Add dockerized bikeshed example w3c/vc-json-schema#4.
-
-
3 pull requests received 31 new comments.
TR publications
-
1 document published.
-
Verifiable Credentials Data Model 1.0 published as a Recommendation. History of Verifiable Credentials Data Model 1.0
-
Participants
-
1 participant joined.
-
Ivan Herman (W3C) joined.
-
GitHub
w3c/vc-data-integrity
-
1 issue opened.
-
serialization, canonicalized values and normalized datasets w3c/vc-data-integrity#11, by @nightpool.
-
-
1 issue received 7 new comments.
-
serialization, canonicalized values and normalized datasets w3c/vc-data-integrity#11 (7 comments by @dlongley, @gkellogg, @grishka, @nightpool)
-
w3c/vc-test-suite
-
1 issue opened.
-
Correct JWK for decoding JWTs tests w3c/vc-test-suite#101, by @kdimak.
-
-
1 pull request merged.
-
Adds Factom-Harmony-Integrate-report w3c/vc-test-suite#100.
-
w3c/vc-data-model
-
1 issue opened.
-
Inconsistencies between Figures and examples w3c/vc-data-model#727, by @mxshea.
-
-
1 pull request opened.
-
Initial revision for errata page w3c/vc-data-model#728, by @plehegar.
-
-
1 pull request merged.
-
Initial revision for errata page w3c/vc-data-model#728.
-
w3c/vc-json-schema
-
2 issues opened.
-
fix spec hosting w3c/vc-json-schema#3, by @OR13.
-
Fix proof / JSON-LD compatibility issues w3c/vc-json-schema#2, by @OR13.
-
-
1 issue received 3 new comments.
-
1 pull request opened.
-
Initial draft w3c/vc-json-schema#1, by @thereisnogabe.
-
-
1 pull request merged.
-
Initial draft w3c/vc-json-schema#1.
-
-
1 pull request received 7 new comments.
Participants
-
4 organizations joined.
-
Jolocom GmbH joined.
-
MITRE Corporation joined.
-
Mattr Limited joined.
-
globaliD joined.
-
-
2 organizations left.
-
Best Innovation Group left.
-
Blockstream left.
-
GitHub
w3c/vc-test-suite
-
4 issues opened.
-
any tests show interop between implementations? w3c/vc-test-suite#99, by @dckc.
-
jwt test generator options are applied to the following zkp ones w3c/vc-test-suite#98, by @kdimak.
-
"bad type cardinality" test w3c/vc-test-suite#97, by @kdimak.
-
"bad @context cardinality" test w3c/vc-test-suite#96, by @kdimak.
-
-
1 issue closed.
-
any tests show interop between implementations? w3c/vc-test-suite#99.
-
-
4 issues received 15 new comments.
-
any tests show interop between implementations? w3c/vc-test-suite#99 (6 comments by @brentzundel, @dckc, @msporny)
-
"bad @context cardinality" test w3c/vc-test-suite#96 (6 comments by @dlongley, @llorllale, @TallTed)
-
-
1 pull request opened.
-
Adds Factom-Harmony-Integrate-report w3c/vc-test-suite#100, by @danielRicaud.
-
w3c/vc-data-integrity
-
2 issues opened.
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#8, by @msporny.
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#12, by @msporny.
-
-
1 issue received 1 new comment.
-
Need a way to specify multi-factor key/proof relationships w3c/vc-data-integrity#12 (1 comment by @ChristopherA)
-
-
1 pull request opened.
-
Expand intro, add sections on methods, purposes, controllers; refactor. w3c/vc-data-integrity#7, by @dmitrizagidulin.
-
-
2 pull requests merged.
-
Expand intro, add sections on methods, purposes, controllers; refactor. w3c/vc-data-integrity#7.
-
Update LD Proofs spec to match latest DID and VC spec examples w3c/vc-data-integrity#6.
-
-
2 pull requests received 38 new comments.
-
Expand intro, add sections on methods, purposes, controllers; refactor. w3c/vc-data-integrity#7 (35 comments by @dlongley, @dmitrizagidulin, @msporny)
-
Update LD Proofs spec to match latest DID and VC spec examples w3c/vc-data-integrity#6 (3 comments by @dmitrizagidulin)
-
w3c/vc-data-model
-
1 issue opened.
-
ZKP implementation - why proof and schema mandatory within derived VC? w3c/vc-data-model#726, by @Iso5786.
-
-
1 issue received 4 new comments.
-
ZKP implementation - why proof and schema mandatory within derived VC? w3c/vc-data-model#726 (4 comments by @brentzundel, @Iso5786)
-
w3c/vc-use-cases
-
1 issue opened.
-
typo in section "L.4 Refugee crisis" w3c/vc-use-cases#120, by @Toni100.
-
TR publications
-
3 documents published.
-
Verifiable Credentials Data Model 1.0 published as a Proposed Recommendation. History of Verifiable Credentials Data Model 1.0
-
Verifiable Credentials Use Cases published as a Note. History of Verifiable Credentials Use Cases
-
GitHub
w3c/vc-data-integrity
-
1 pull request received 4 new comments.
-
Update LD Proofs spec to match latest DID and VC spec examples w3c/vc-data-integrity#6 (4 comments by @dlongley, @dmitrizagidulin)
-
w3c/vc-data-model
-
2 issues opened.
-
openid implementations w3c/vc-data-model#725, by @victorherraiz-santander.
-
Expressing which credentials are acceptable w3c/vc-data-model#724, by @rceleste125.
-
-
2 issues received 6 new comments.
-
Expressing which credentials are acceptable w3c/vc-data-model#724 (4 comments by @ChristopherA, @David-Chadwick, @dlongley, @dmitrizagidulin)
-
openid implementations w3c/vc-data-model#725 (2 comments by @dmitrizagidulin, @victorherraiz-santander)
-
w3c/vc-use-cases
-
5 pull requests opened.
-
Prepare for NOTE publication w3c/vc-use-cases#119, by @rhiaro.
-
remove duplicate figure 2, Amanda->Anand w3c/vc-use-cases#118, by @ken-ebert.
-
Prepare for NOTE publication w3c/vc-use-cases#117, by @rhiaro.
-
does this result in fewer conflicts? w3c/vc-use-cases#116, by @TallTed.
-
Cleanup index.html v2 w3c/vc-use-cases#115, by @stonematt.
-
-
4 pull requests merged.
-
Prepare for NOTE publication w3c/vc-use-cases#119.
-
remove duplicate figure 2, Amanda->Anand w3c/vc-use-cases#118.
-
cleanup of index.html w3c/vc-use-cases#111.
-
Update Editor/Author sections w3c/vc-use-cases#113.
-
-
3 pull requests closed.
-
Cleanup index.html v2 w3c/vc-use-cases#115.
-
does this result in fewer conflicts? w3c/vc-use-cases#116.
-
Prepare for NOTE publication w3c/vc-use-cases#117.
-
-
7 pull requests received 35 new comments.
-
Cleanup index.html v2 w3c/vc-use-cases#115 (15 comments by @brentzundel, @ken-ebert, @stonematt, @TallTed)
-
w3c/vc-imp-guide
-
1 issue closed.
-
add caveats about impacts of group deadlines w3c/vc-imp-guide#46.
-
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Prepare NOTE for publication w3c/vc-imp-guide#58, by @rhiaro.
-
-
2 pull requests merged.
-
Prepare NOTE for publication w3c/vc-imp-guide#58.
-
Extending JWTs w3c/vc-imp-guide#41.
-
-
2 pull requests received 22 new comments.
Participants
-
1 participant joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
-
1 organization joined.
-
Danube Tech GmbH joined.
-
GitHub
w3c/vc-use-cases
-
3 issues opened.
-
update diagrams w3c/vc-use-cases#109, by @stonematt.
-
review document for glossary/terms w3c/vc-use-cases#108, by @stonematt.
-
Review Editor/Author section w3c/vc-use-cases#107, by @stonematt.
-
-
20 issues closed.
-
Add a Threat Model section w3c/vc-use-cases#90.
-
Add Accessibility Use Case for under 3.3 Healthcare w3c/vc-use-cases#74.
-
Can I verifify/validate/understand who the issuer is w3c/vc-use-cases#89.
-
review document for glossary/terms w3c/vc-use-cases#108.
-
Is storage out of scope? w3c/vc-use-cases#49.
-
preservation (inc. version control?) w3c/vc-use-cases#36.
-
Establish criteria for use cases, provide outlet for examples w3c/vc-use-cases#35.
-
Add lifecycle engagement models w3c/vc-use-cases#34.
-
Privacy / Dignity w3c/vc-use-cases#32.
-
WoT Use Case w3c/vc-use-cases#31.
-
Requirements should be derived from use cases w3c/vc-use-cases#30.
-
RDF based spec w3c/vc-use-cases#25.
-
old use-cases? w3c/vc-use-cases#24.
-
5. 1 Expansion 4. Italicized word ‘credential’ Overlooked link? w3c/vc-use-cases#13.
-
Sec 4.2 ‘Needs’ example: reference and link to C.5 Social Authority, Freedonia w3c/vc-use-cases#10.
-
Update Needs Map and Task Map [was core v additional use cases] w3c/vc-use-cases#19.
-
Amend task can be assigned to holder w3c/vc-use-cases#92.
-
Sec 2. “Holder” is a confusing name w3c/vc-use-cases#18.
-
Dead link w3c/vc-use-cases#85.
-
Add retail use cases w3c/vc-use-cases#48.
-
-
21 issues received 27 new comments.
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (1 comment by @jandrieu)
-
w3c/vc-use-cases#36 (1 comment by @jandrieu)
-
w3c/vc-use-cases#35 (1 comment by @jandrieu)
-
w3c/vc-use-cases#32 (1 comment by @jandrieu)
-
w3c/vc-use-cases#31 (1 comment by @jandrieu)
-
w3c/vc-use-cases#30 (1 comment by @jandrieu)
-
w3c/vc-use-cases#25 (1 comment by @jandrieu)
-
w3c/vc-use-cases#24 (1 comment by @jandrieu)
-
w3c/vc-use-cases#19 (1 comment by @stonematt)
-
w3c/vc-use-cases#18 (1 comment by @stonematt)
-
6 pull requests opened.
-
Cleanup Issue Notes w3c/vc-use-cases#114, by @stonematt.
-
Update Editor/Author sections w3c/vc-use-cases#113, by @stonematt.
-
Define terms w3c/vc-use-cases#112, by @stonematt.
-
cleanup of index.html w3c/vc-use-cases#111, by @TallTed.
-
editorial w3c/vc-use-cases#110, by @stonematt.
-
fix roles diagram to show verifier instead of inspector w3c/vc-use-cases#106, by @ken-ebert.
-
-
6 pull requests merged.
-
Cleanup Issue Notes w3c/vc-use-cases#114.
-
Define terms w3c/vc-use-cases#112.
-
Add device use cases w3c/vc-use-cases#105.
-
added PADI focal use case w3c/vc-use-cases#100.
-
editorial w3c/vc-use-cases#110.
-
fix roles diagram to show verifier instead of inspector w3c/vc-use-cases#106.
-
-
5 pull requests received 40 new comments.
-
Add device use cases w3c/vc-use-cases#105 (18 comments by @jandrieu, @ken-ebert, @nedmsmith, @TallTed)
-
Adds User Task for "Trust Claim" w3c/vc-use-cases#103 (6 comments by @jandrieu, @RieksJ, @stonematt)
-
fix roles diagram to show verifier instead of inspector w3c/vc-use-cases#106 (1 comment by @stonematt)
-
w3c/vc-imp-guide
-
12 issues opened.
-
all vocab links should be versioned w3c/vc-imp-guide#55, by @TallTed.
-
add caveats about impacts of group deadlines w3c/vc-imp-guide#46, by @TallTed.
-
Section 7.2 Issues w3c/vc-imp-guide#45, by @nadalin.
-
Multiple times w3c/vc-imp-guide#44, by @David-Chadwick.
-
Selective Disclosure w3c/vc-imp-guide#42, by @David-Chadwick.
-
preview/diff magic isn't active on vc-imp-guide w3c/vc-imp-guide#35, by @TallTed.
-
Verification section is incomplete w3c/vc-imp-guide#31, by @brentzundel.
-
examples allow copying non-JSON elements w3c/vc-imp-guide#29, by @brentzundel.
-
Add section on ZKPs and where to find more information w3c/vc-imp-guide#25, by @msporny.
-
Add section on ZKPs and where to find more information w3c/vc-imp-guide#24, by @deiu.
-
Add section on related work w3c/vc-imp-guide#23, by @msporny.
-
variable vocab is being discussed as if invariable w3c/vc-imp-guide#22, by @TallTed.
-
-
12 issues closed.
-
Selective Disclosure w3c/vc-imp-guide#42.
-
Section 7.2 Issues w3c/vc-imp-guide#45.
-
Add guidance to prevent unauthorized credential reuse by verifiers w3c/vc-imp-guide#2.
-
Reference or attach credential in another credentials w3c/vc-imp-guide#4.
-
Add section on ZKPs and where to find more information w3c/vc-imp-guide#24.
-
Determine how/if WebAuthn will work with VCs w3c/vc-imp-guide#3.
-
examples allow copying non-JSON elements w3c/vc-imp-guide#29.
-
variable vocab is being discussed as if invariable w3c/vc-imp-guide#22.
-
preview/diff magic isn't active on vc-imp-guide w3c/vc-imp-guide#35.
-
Add section on ZKPs and where to find more information w3c/vc-imp-guide#25.
-
Add sections outlining benefits of different syntax + proof formats w3c/vc-imp-guide#8.
-
Add section detailing how to author a new VC (semantics and schema) w3c/vc-imp-guide#16.
-
-
15 issues received 44 new comments.
-
variable vocab is being discussed as if invariable w3c/vc-imp-guide#22 (6 comments by @brentzundel, @deiu, @dmitrizagidulin, @TallTed)
-
Reference or attach credential in another credentials w3c/vc-imp-guide#4 (5 comments by @David-Chadwick, @dlongley, @dmitrizagidulin, @TallTed)
-
Add guidance to prevent unauthorized credential reuse by verifiers w3c/vc-imp-guide#2 (5 comments by @David-Chadwick, @deiu, @TallTed)
-
Determine how/if WebAuthn will work with VCs w3c/vc-imp-guide#3 (3 comments by @David-Chadwick, @deiu, @dlongley)
-
Verification section is incomplete w3c/vc-imp-guide#31 (3 comments by @brentzundel, @deiu, @dmitrizagidulin)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials (see pending PR #17) w3c/vc-imp-guide#1 (2 comments by @jonnycrunch)
-
Add section on ZKPs and where to find more information w3c/vc-imp-guide#24 (1 comment by @brentzundel)
-
Add section detailing how to author a new VC (semantics and schema) w3c/vc-imp-guide#16 (1 comment by @deiu)
-
24 pull requests opened.
-
(editorial) capitalization and minor grammar w3c/vc-imp-guide#57, by @TallTed.
-
Add note about referencing CCG for future versions. w3c/vc-imp-guide#56, by @dlongley.
-
resolves #22; re. risks of evolving schema.org vocab w3c/vc-imp-guide#54, by @deiu.
-
fixes #29; do not copy non-JSON elements w3c/vc-imp-guide#53, by @deiu.
-
Add section on Web Authentication. w3c/vc-imp-guide#52, by @dmitrizagidulin.
-
Add a section on referencing or embedding external credentials. w3c/vc-imp-guide#51, by @dmitrizagidulin.
-
Added ZKP-section text w3c/vc-imp-guide#50, by @brentzundel.
-
Added content verifiable data registries section w3c/vc-imp-guide#49, by @brentzundel.
-
Additional date/times w3c/vc-imp-guide#48, by @David-Chadwick.
-
Hashed claim values w3c/vc-imp-guide#47, by @David-Chadwick.
-
Jwt aud claim w3c/vc-imp-guide#43, by @David-Chadwick.
-
Extending JWTs w3c/vc-imp-guide#41, by @David-Chadwick.
-
Add text to verification section w3c/vc-imp-guide#40, by @brentzundel.
-
Add targeted vp example. w3c/vc-imp-guide#39, by @dlongley.
-
Fix context URL typos. w3c/vc-imp-guide#38, by @dlongley.
-
Preview test w3c/vc-imp-guide#37, by @burnburn.
-
Test preview w3c/vc-imp-guide#36, by @burnburn.
-
moved hashlinks to new content integrity subsection of verification w3c/vc-imp-guide#34, by @brentzundel.
-
removed COSE sections w3c/vc-imp-guide#33, by @brentzundel.
-
ZKP section w3c/vc-imp-guide#32, by @brentzundel.
-
made Disputes its own section w3c/vc-imp-guide#30, by @brentzundel.
-
Proof formats - edits w3c/vc-imp-guide#28, by @brentzundel.
-
Identifiers - edits w3c/vc-imp-guide#27, by @brentzundel.
-
Introduction - edits w3c/vc-imp-guide#26, by @brentzundel.
-
-
22 pull requests merged.
-
(editorial) capitalization and minor grammar w3c/vc-imp-guide#57.
-
Hashed claim values w3c/vc-imp-guide#47.
-
Jwt aud claim w3c/vc-imp-guide#43.
-
Add note about referencing CCG for future versions. w3c/vc-imp-guide#56.
-
Add a section on referencing or embedding external credentials. w3c/vc-imp-guide#51.
-
Added content verifiable data registries section w3c/vc-imp-guide#49.
-
Added ZKP-section text w3c/vc-imp-guide#50.
-
Add section on Web Authentication. w3c/vc-imp-guide#52.
-
fixes #29; do not copy non-JSON elements w3c/vc-imp-guide#53.
-
resolves #22; re. risks of evolving schema.org vocab w3c/vc-imp-guide#54.
-
Add text to verification section w3c/vc-imp-guide#40.
-
Add targeted vp example. w3c/vc-imp-guide#39.
-
Introduction - edits w3c/vc-imp-guide#26.
-
made Disputes its own section w3c/vc-imp-guide#30.
-
Fix context URL typos. w3c/vc-imp-guide#38.
-
moved hashlinks to new content integrity subsection of verification w3c/vc-imp-guide#34.
-
removed COSE sections w3c/vc-imp-guide#33.
-
Proof formats - edits w3c/vc-imp-guide#28.
-
ZKP section w3c/vc-imp-guide#32.
-
Identifiers - edits w3c/vc-imp-guide#27.
-
Jwt tradeoff section (resolves #8) w3c/vc-imp-guide#19.
-
Start new extension section (resolves #16) w3c/vc-imp-guide#18.
-
-
2 pull requests closed.
-
Preview test w3c/vc-imp-guide#37.
-
Test preview w3c/vc-imp-guide#36.
-
-
19 pull requests received 184 new comments.
-
Hashed claim values w3c/vc-imp-guide#47 (23 comments by @David-Chadwick, @deiu, @dlongley, @TallTed)
-
Add a section on referencing or embedding external credentials. w3c/vc-imp-guide#51 (9 comments by @David-Chadwick, @dmitrizagidulin)
-
Additional date/times w3c/vc-imp-guide#48 (9 comments by @David-Chadwick, @deiu, @dlongley, @TallTed)
-
resolves #22; re. risks of evolving schema.org vocab w3c/vc-imp-guide#54 (8 comments by @David-Chadwick, @deiu, @TallTed)
-
[WIP] added example schema.json for vc (resolves #1) w3c/vc-imp-guide#17 (3 comments by @deiu, @jonnycrunch)
w3c/vc-data-model
-
4 issues opened.
-
Optimized SVG diagrams w3c/vc-data-model#721, by @davidlehn.
-
Verifiable Credentials Implementation Guidelines 1.0 w3c/vc-data-model#714, by @nadalin.
-
More implementation issues w3c/vc-data-model#712, by @nadalin.
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709, by @nadalin.
-
-
3 issues closed.
-
Verifiable Credentials Implementation Guidelines 1.0 w3c/vc-data-model#714.
-
(editorial) inline comments make JSON invalid w3c/vc-data-model#704.
-
Verification definition incorrect w3c/vc-data-model#705.
-
-
6 issues received 37 new comments.
-
Underspecification of issuer object format and document obtained if issuer id is dereferenced w3c/vc-data-model#709 (18 comments by @brentzundel, @burnburn, @csuwildcat, @jandrieu, @msporny, @nadalin, @stonematt)
-
More implementation issues w3c/vc-data-model#712 (14 comments by @aljones15, @brentzundel, @burnburn, @David-Chadwick, @nadalin)
-
-
11 pull requests opened.
-
(editorial) various clarified phrasings w3c/vc-data-model#723, by @TallTed.
-
making a note, a note w3c/vc-data-model#722, by @TallTed.
-
Other JWT claims w3c/vc-data-model#720, by @David-Chadwick.
-
JWT exp w3c/vc-data-model#719, by @David-Chadwick.
-
JWT property to claim w3c/vc-data-model#718, by @David-Chadwick.
-
JWT - aud w3c/vc-data-model#717, by @David-Chadwick.
-
Proposed Recommendation for 2019-08-18. w3c/vc-data-model#716, by @msporny.
-
Add example of expanded issuer property. Related to issue #709. w3c/vc-data-model#715, by @msporny.
-
Fix typos in JWT encoding decoding w3c/vc-data-model#711, by @David-Chadwick.
-
added example of issuer with object as value w3c/vc-data-model#710, by @brentzundel.
-
Prevent copying of comments in examples. Use a11y friendly colors. w3c/vc-data-model#708, by @msporny.
-
-
6 pull requests merged.
-
JWT property to claim w3c/vc-data-model#718.
-
JWT - aud w3c/vc-data-model#717.
-
Proposed Recommendation for 2019-08-18. w3c/vc-data-model#716.
-
Add example of expanded issuer property. Related to issue #709. w3c/vc-data-model#715.
-
Prevent copying of comments in examples. Use a11y friendly colors. w3c/vc-data-model#708.
-
Update terms.html w3c/vc-data-model#706.
-
-
4 pull requests closed.
-
Other JWT claims w3c/vc-data-model#720.
-
JWT exp w3c/vc-data-model#719.
-
Fix typos in JWT encoding decoding w3c/vc-data-model#711.
-
added example of issuer with object as value w3c/vc-data-model#710.
-
-
10 pull requests received 62 new comments.
-
Fix typos in JWT encoding decoding w3c/vc-data-model#711 (40 comments by @awoie, @David-Chadwick, @davidlehn, @msporny, @TallTed)
-
added example of issuer with object as value w3c/vc-data-model#710 (6 comments by @brentzundel, @msporny, @TallTed)
-
Other JWT claims w3c/vc-data-model#720 (5 comments by @burnburn, @David-Chadwick, @msporny, @TallTed)
-
Add example of expanded issuer property. Related to issue #709. w3c/vc-data-model#715 (1 comment by @msporny)
-
w3c/vc-test-suite
-
1 issue opened.
-
vc-test-suite w3c/vc-test-suite#95, by @nadalin.
-
-
4 issues closed.
-
Add key/legend for test statuses w3c/vc-test-suite#70.
-
JSON-LD context is Invalid JSON w3c/vc-test-suite#19.
-
Wrong content type w3c/vc-test-suite#18.
-
Wrong content type and CORS headers not set w3c/vc-test-suite#9.
-
-
6 issues received 19 new comments.
-
vc-test-suite w3c/vc-test-suite#95 (13 comments by @brentzundel, @burnburn, @David-Chadwick, @dmitrizagidulin, @nadalin, @TallTed)
-
Add feature sections to report's Table of Contents w3c/vc-test-suite#69 (1 comment by @dmitrizagidulin)
-
-
7 pull requests opened.
-
Update impl. report Table of Contents. w3c/vc-test-suite#94, by @dmitrizagidulin.
-
removed redundant file w3c/vc-test-suite#93, by @awoie.
-
added additional uport kotlin test report w3c/vc-test-suite#92, by @awoie.
-
updated uport w3c test report w3c/vc-test-suite#91, by @awoie.
-
Add table key to test results. w3c/vc-test-suite#90, by @dmitrizagidulin.
-
Updated report w3c/vc-test-suite#89, by @dmitrizagidulin.
-
updated uport test report w3c/vc-test-suite#88, by @awoie.
-
-
7 pull requests merged.
-
Update impl. report Table of Contents. w3c/vc-test-suite#94.
-
removed redundant file w3c/vc-test-suite#93.
-
added additional uport kotlin test report w3c/vc-test-suite#92.
-
updated uport w3c test report w3c/vc-test-suite#91.
-
Add table key to test results. w3c/vc-test-suite#90.
-
Updated report w3c/vc-test-suite#89.
-
updated uport test report w3c/vc-test-suite#88.
-
-
1 pull request closed.
-
Create Toulouse-Kent-report.json w3c/vc-test-suite#62.
-
-
1 pull request reopened.
-
Create Toulouse-Kent-report.json w3c/vc-test-suite#62, by @David-Chadwick.
-
-
5 pull requests received 10 new comments.
-
Create Toulouse-Kent-report.json w3c/vc-test-suite#62 (5 comments by @David-Chadwick, @dmitrizagidulin, @TallTed)
-
w3c/vc-data-integrity
-
1 pull request opened.
-
Update LD Proofs spec to match latest DID and VC spec examples w3c/vc-data-integrity#6, by @dmitrizagidulin.
-
TR publications
-
1 document published.
-
Verifiable Credentials Data Model 1.0 published as a Candidate Recommendation Snapshot. History of Verifiable Credentials Data Model 1.0
-
Participants
-
1 participant joined.
-
Alan Bird (W3C) joined.
-
-
1 organization joined.
-
Universities Admissions Centre joined.
-
-
1 organization left.
-
VitalSource | Ingram Content Group left.
-
GitHub
w3c/vc-use-cases
-
1 issue received 4 new comments.
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (4 comments by @jandrieu, @RieksJ, @stonematt)
-
-
3 pull requests opened.
-
Add device use cases w3c/vc-use-cases#105, by @ken-ebert.
-
update of PADI, includes suggestions of issue #96 w3c/vc-use-cases#104, by @RieksJ.
-
Adds User Task for "Trust Claim" w3c/vc-use-cases#103, by @RieksJ.
-
-
1 pull request merged.
-
Update order of User Needs w3c/vc-use-cases#102.
-
-
1 pull request closed.
-
update of PADI, includes suggestions of issue #96 w3c/vc-use-cases#104.
-
-
4 pull requests received 7 new comments.
-
update of PADI, includes suggestions of issue #96 w3c/vc-use-cases#104 (2 comments by @RieksJ, @stonematt)
w3c/vc-imp-guide
-
1 issue opened.
-
Add section pointing to the test suite and implementation report. w3c/vc-imp-guide#20, by @deiu.
-
-
2 issues closed.
-
Add section pointing to the test suite and implementation report. w3c/vc-imp-guide#20.
-
Suggestions on how to do progressive trust or graceful degredation w3c/vc-imp-guide#6.
-
-
3 issues received 7 new comments.
-
Add section detailing how to author a new VC (semantics and schema) w3c/vc-imp-guide#16 (3 comments by @dlongley, @TallTed)
-
Suggestions on how to do progressive trust or graceful degredation w3c/vc-imp-guide#6 (3 comments by @brentzundel, @deiu)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials (see pending PR #17) w3c/vc-imp-guide#1 (1 comment by @jonnycrunch)
-
-
4 pull requests opened.
-
Add section for test suite and implementation report w3c/vc-imp-guide#21, by @deiu.
-
Jwt tradeoff section (resolves #8) w3c/vc-imp-guide#19, by @awoie.
-
Start new extension section (resolves #16) w3c/vc-imp-guide#18, by @dlongley.
-
[WIP] added example schema.json for vc (resolves #1) w3c/vc-imp-guide#17, by @jonnycrunch.
-
-
4 pull requests merged.
-
Add section for test suite and implementation report w3c/vc-imp-guide#21.
-
Progressive Trust w3c/vc-imp-guide#14.
-
Editorial: Indentation fix w3c/vc-imp-guide#13.
-
Added sections on identifiers and proofs w3c/vc-imp-guide#7.
-
-
6 pull requests received 65 new comments.
-
Start new extension section (resolves #16) w3c/vc-imp-guide#18 (25 comments by @brentzundel, @deiu, @dlongley, @TallTed)
-
Add section for test suite and implementation report w3c/vc-imp-guide#21 (9 comments by @brentzundel, @deiu, @TallTed)
-
Jwt tradeoff section (resolves #8) w3c/vc-imp-guide#19 (9 comments by @brentzundel, @dlongley, @TallTed)
-
w3c/vc-test-suite
-
4 issues opened.
-
Add links to repos for public implementations w3c/vc-test-suite#86, by @deiu.
-
Indicating 'refresh' not-supported in config.json causes 'status' tests to not run. w3c/vc-test-suite#73, by @ken-ebert.
-
Add key/legend for test statuses w3c/vc-test-suite#70, by @dmitrizagidulin.
-
Add feature sections to report's Table of Contents w3c/vc-test-suite#69, by @dmitrizagidulin.
-
-
7 issues closed.
-
Indicating 'refresh' not-supported in config.json causes 'status' tests to not run. w3c/vc-test-suite#73.
-
An example to follow would be really nice w3c/vc-test-suite#14.
-
Timeout w3c/vc-test-suite#21.
-
Report generation fails w3c/vc-test-suite#28.
-
Tests are checking for ISO8601 w3c/vc-test-suite#22.
-
Report is non-specific in its categorization of tests w3c/vc-test-suite#30.
-
Passing tests against the testsuite are not correctly summarized in the report w3c/vc-test-suite#59.
-
-
8 issues received 8 new comments.
-
Indicating 'refresh' not-supported in config.json causes 'status' tests to not run. w3c/vc-test-suite#73 (1 comment by @dmitrizagidulin)
-
Report is non-specific in its categorization of tests w3c/vc-test-suite#30 (1 comment by @dmitrizagidulin)
-
Passing tests against the testsuite are not correctly summarized in the report w3c/vc-test-suite#59 (1 comment by @dmitrizagidulin)
-
18 pull requests opened.
-
Added tests for holder/iss in presentation w3c/vc-test-suite#87, by @awoie.
-
Rebased Ken Ebert's Sovrin PR w3c/vc-test-suite#85, by @dmitrizagidulin.
-
Evernym test update w3c/vc-test-suite#84, by @brentzundel.
-
Update Sovrin test report w3c/vc-test-suite#83, by @ken-ebert.
-
Update Credly implementation report w3c/vc-test-suite#82, by @yancyribbens.
-
add Brightlink implementation report w3c/vc-test-suite#81, by @stonematt.
-
Updated Evernym test report w3c/vc-test-suite#80, by @brentzundel.
-
fixed error in status test w3c/vc-test-suite#79, by @brentzundel.
-
Updated Evernym test report w3c/vc-test-suite#78, by @brentzundel.
-
(editorial) change "Linked Data" to "LD" w3c/vc-test-suite#77, by @TallTed.
-
Update DanubeTech report, re-run with latest tests. w3c/vc-test-suite#76, by @peacekeeper.
-
Fix "status" value in "sectionsNotSupported" w3c/vc-test-suite#75, by @peacekeeper.
-
Fixes Indicating 'refresh' not-supported in config.json causes 'status' tests to not run. #73 w3c/vc-test-suite#74, by @ken-ebert.
-
regenerated uPort report using latest test suite filter options w3c/vc-test-suite#72, by @mirceanis.
-
Add aria-label for failure/status marks w3c/vc-test-suite#71, by @BigBlueHat.
-
Add example config file, troubleshooting section. w3c/vc-test-suite#68, by @dmitrizagidulin.
-
Add timeout troubleshooting instructions to README. w3c/vc-test-suite#67, by @dmitrizagidulin.
-
Fix report generation instructions. w3c/vc-test-suite#66, by @dmitrizagidulin.
-
-
14 pull requests merged.
-
Added tests for holder/iss in presentation w3c/vc-test-suite#87.
-
Rebased Ken Ebert's Sovrin PR w3c/vc-test-suite#85.
-
Evernym test update w3c/vc-test-suite#84.
-
Update Credly implementation report w3c/vc-test-suite#82.
-
add Brightlink implementation report w3c/vc-test-suite#81.
-
regenerated uPort report using latest test suite filter options w3c/vc-test-suite#72.
-
Updated Evernym test report w3c/vc-test-suite#80.
-
Update DanubeTech report, re-run with latest tests. w3c/vc-test-suite#76.
-
fixed error in status test w3c/vc-test-suite#79.
-
Add aria-label for failure/status marks w3c/vc-test-suite#71.
-
Add example config file, troubleshooting section. w3c/vc-test-suite#68.
-
Add timeout troubleshooting instructions to README. w3c/vc-test-suite#67.
-
Fix report generation instructions. w3c/vc-test-suite#66.
-
Refactor conformance results tables w3c/vc-test-suite#64.
-
-
5 pull requests closed.
-
Update Sovrin test report w3c/vc-test-suite#83.
-
Updated Evernym test report w3c/vc-test-suite#78.
-
Fix "status" value in "sectionsNotSupported" w3c/vc-test-suite#75.
-
Change to rfc3339 date times w3c/vc-test-suite#65.
-
-
14 pull requests received 26 new comments.
-
(editorial) change "Linked Data" to "LD" w3c/vc-test-suite#77 (7 comments by @dmitrizagidulin, @TallTed)
-
Added tests for holder/iss in presentation w3c/vc-test-suite#87 (5 comments by @awoie, @brentzundel, @dmitrizagidulin)
-
regenerated uPort report using latest test suite filter options w3c/vc-test-suite#72 (2 comments by @dmitrizagidulin)
-
Create Toulouse-Kent-report.json w3c/vc-test-suite#62 (2 comments by @David-Chadwick, @dmitrizagidulin)
-
Update DanubeTech report, re-run with latest tests. w3c/vc-test-suite#76 (1 comment by @dmitrizagidulin)
-
Fixes Indicating 'refresh' not-supported in config.json causes 'status' tests to not run. #73 w3c/vc-test-suite#74 (1 comment by @dmitrizagidulin)
-
w3c/vc-data-model
-
5 issues opened.
-
Verification definition incorrect w3c/vc-data-model#705, by @jandrieu.
-
(editorial) inline comments make JSON invalid w3c/vc-data-model#704, by @TallTed.
-
Implicit Types Insertion w3c/vc-data-model#682, by @David-Chadwick.
-
Update feature at risk section w3c/vc-data-model#681, by @awoie.
-
Update list of Editors/Authors for spec. w3c/vc-data-model#675, by @msporny.
-
-
22 issues closed.
-
Change W3C TR link to vc-data-model w3c/vc-data-model#526.
-
tracking issue for iat → nbf related changes w3c/vc-data-model#667.
-
Implicit Types Insertion w3c/vc-data-model#682.
-
Tracking Issue: JWT-only support w3c/vc-data-model#634.
-
Tracking Issue: JSON-LD concerns w3c/vc-data-model#633.
-
Coordinate with PING during review process w3c/vc-data-model#222.
-
Update feature at risk section w3c/vc-data-model#681.
-
JSON-LD Reference w3c/vc-data-model#537.
-
The confusing nature of type and presentation w3c/vc-data-model#653.
-
Clarification on JSON types w3c/vc-data-model#621.
-
Protocol buffer support w3c/vc-data-model#642.
-
Consolidate all Verifiable Credential Registries to a single registry w3c/vc-data-model#530.
-
Update list of Editors/Authors for spec. w3c/vc-data-model#675.
-
Proofs Note w3c/vc-data-model#612.
-
Conformance w3c/vc-data-model#609.
-
Section 4.2 w3c/vc-data-model#606.
-
Example URI w3c/vc-data-model#605.
-
Recommend adding `holder` to non-ZKP VPs in implementation guide w3c/vc-data-model#596.
-
JSON schema reference w3c/vc-data-model#589.
-
misleadingly and confusingly named issuanceDate w3c/vc-data-model#584.
-
@Context Processing w3c/vc-data-model#558.
-
-
22 issues received 44 new comments.
-
Implicit Types Insertion w3c/vc-data-model#682 (11 comments by @brentzundel, @burnburn, @David-Chadwick, @dlongley, @msporny, @TallTed)
-
(editorial) inline comments make JSON invalid w3c/vc-data-model#704 (4 comments by @brentzundel, @ken-ebert, @peacekeeper)
-
Tracking Issue: JWT-only support w3c/vc-data-model#634 (4 comments by @burnburn, @David-Chadwick, @nadalin, @TallTed)
-
Update list of Editors/Authors for spec. w3c/vc-data-model#675 (4 comments by @ChristopherA, @msporny)
-
tracking issue for iat → nbf related changes w3c/vc-data-model#667 (2 comments by @burnburn, @msporny)
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436 (1 comment by @burnburn)
-
Consolidate all Verifiable Credential Registries to a single registry w3c/vc-data-model#530 (1 comment by @msporny)
-
Recommend adding `holder` to non-ZKP VPs in implementation guide w3c/vc-data-model#596 (1 comment by @burnburn)
-
-
28 pull requests opened.
-
Update iss of JWT w3c/vc-data-model#707, by @David-Chadwick.
-
Update terms.html w3c/vc-data-model#706, by @jandrieu.
-
Draft of potential CR2 for 2019-07-25 publication w3c/vc-data-model#703, by @msporny.
-
Implement VCWG Resolution wrt. implicit types. Related to #682. w3c/vc-data-model#702, by @msporny.
-
(editorial) change such to showing w3c/vc-data-model#701, by @TallTed.
-
grammar fix and example clarification rewording w3c/vc-data-model#700, by @TallTed.
-
minor grammar and punctuation w3c/vc-data-model#699, by @TallTed.
-
small grammar and other corrections w3c/vc-data-model#698, by @TallTed.
-
fix punctuation and minor reword w3c/vc-data-model#697, by @TallTed.
-
fixed typo (URI is Uniform, not Universal) w3c/vc-data-model#696, by @TallTed.
-
Appendix C Subject Holder suggested editorial updates w3c/vc-data-model#695, by @grantnoble.
-
Appendix B Base Context suggested editorial updates w3c/vc-data-model#694, by @grantnoble.
-
Appendix A Validation suggested editorial updates w3c/vc-data-model#693, by @grantnoble.
-
Internationalization Considerations suggested editorial updates w3c/vc-data-model#692, by @grantnoble.
-
Clarify implicit typing. Related to #682. w3c/vc-data-model#691, by @msporny.
-
Added myself to RWOT facilitators w3c/vc-data-model#690, by @kimdhamilton.
-
Suggested updates for Security Considerations section w3c/vc-data-model#689, by @grantnoble.
-
Suggested updates for Privacy Considerations section w3c/vc-data-model#688, by @grantnoble.
-
Suggested updates for Syntaxes section w3c/vc-data-model#687, by @grantnoble.
-
Suggested updates for Advanced Concepts section w3c/vc-data-model#686, by @grantnoble.
-
fix subclass/superclass typing requirement mismatch w3c/vc-data-model#685, by @TallTed.
-
Suggested updates for the Basic Concepts section w3c/vc-data-model#684, by @grantnoble.
-
Suggested updates for the Core Data Model section w3c/vc-data-model#683, by @grantnoble.
-
Suggested updates for Terminology section w3c/vc-data-model#680, by @grantnoble.
-
Suggested updates for Abstract and Intro sections w3c/vc-data-model#679, by @grantnoble.
-
(editorial) small language adjustment w3c/vc-data-model#678, by @TallTed.
-
Update JSON-LD 1.0 references to JSON-LD 1.1. w3c/vc-data-model#677, by @msporny.
-
Update Editors, Authors, contributors and acknowledgements. w3c/vc-data-model#676, by @msporny.
-
-
27 pull requests merged.
-
Update iss of JWT w3c/vc-data-model#707.
-
Draft of potential CR2 for 2019-07-25 publication w3c/vc-data-model#703.
-
fixed issue 667 -- renamed iat in nbf w3c/vc-data-model#668.
-
Implement VCWG Resolution wrt. implicit types. Related to #682. w3c/vc-data-model#702.
-
minor grammar and punctuation w3c/vc-data-model#699.
-
(editorial) change such to showing w3c/vc-data-model#701.
-
grammar fix and example clarification rewording w3c/vc-data-model#700.
-
small grammar and other corrections w3c/vc-data-model#698.
-
fix punctuation and minor reword w3c/vc-data-model#697.
-
fixed typo (URI is Uniform, not Universal) w3c/vc-data-model#696.
-
Appendix C Subject Holder suggested editorial updates w3c/vc-data-model#695.
-
Appendix B Base Context suggested editorial updates w3c/vc-data-model#694.
-
Appendix A Validation suggested editorial updates w3c/vc-data-model#693.
-
Internationalization Considerations suggested editorial updates w3c/vc-data-model#692.
-
Suggested updates for Security Considerations section w3c/vc-data-model#689.
-
Suggested updates for Privacy Considerations section w3c/vc-data-model#688.
-
Suggested updates for Syntaxes section w3c/vc-data-model#687.
-
Suggested updates for Advanced Concepts section w3c/vc-data-model#686.
-
fix subclass/superclass typing requirement mismatch w3c/vc-data-model#685.
-
Suggested updates for the Basic Concepts section w3c/vc-data-model#684.
-
Suggested updates for the Core Data Model section w3c/vc-data-model#683.
-
Suggested updates for Terminology section w3c/vc-data-model#680.
-
Suggested updates for Abstract and Intro sections w3c/vc-data-model#679.
-
Added myself to RWOT facilitators w3c/vc-data-model#690.
-
(editorial) small language adjustment w3c/vc-data-model#678.
-
Update JSON-LD 1.0 references to JSON-LD 1.1. w3c/vc-data-model#677.
-
Update Editors, Authors, contributors and acknowledgements. w3c/vc-data-model#676.
-
-
3 pull requests closed.
-
Clarify implicit typing. Related to #682. w3c/vc-data-model#691.
-
Add further explanation of types. w3c/vc-data-model#674.
-
Update index.html w3c/vc-data-model#672.
-
-
23 pull requests received 131 new comments.
-
Clarify implicit typing. Related to #682. w3c/vc-data-model#691 (16 comments by @brentzundel, @David-Chadwick, @msporny)
-
Appendix A Validation suggested editorial updates w3c/vc-data-model#693 (15 comments by @brentzundel, @grantnoble, @TallTed)
-
Add further explanation of types. w3c/vc-data-model#674 (14 comments by @David-Chadwick, @dlongley, @msporny, @TallTed)
-
Suggested updates for the Basic Concepts section w3c/vc-data-model#684 (12 comments by @grantnoble, @TallTed)
-
Internationalization Considerations suggested editorial updates w3c/vc-data-model#692 (10 comments by @grantnoble, @TallTed)
-
Update terms.html w3c/vc-data-model#706 (9 comments by @brentzundel, @jandrieu, @msporny, @stonematt, @TallTed)
-
Suggested updates for Advanced Concepts section w3c/vc-data-model#686 (8 comments by @dlongley, @grantnoble)
-
fix subclass/superclass typing requirement mismatch w3c/vc-data-model#685 (7 comments by @brentzundel, @David-Chadwick, @msporny, @TallTed)
-
Appendix C Subject Holder suggested editorial updates w3c/vc-data-model#695 (6 comments by @grantnoble, @TallTed)
-
fixed issue 667 -- renamed iat in nbf w3c/vc-data-model#668 (5 comments by @awoie, @David-Chadwick, @msporny, @peacekeeper)
-
Update Editors, Authors, contributors and acknowledgements. w3c/vc-data-model#676 (5 comments by @msporny, @TallTed)
-
Implement VCWG Resolution wrt. implicit types. Related to #682. w3c/vc-data-model#702 (3 comments by @msporny, @TallTed)
-
Appendix B Base Context suggested editorial updates w3c/vc-data-model#694 (2 comments by @grantnoble, @TallTed)
-
Suggested updates for the Core Data Model section w3c/vc-data-model#683 (2 comments by @dlongley, @grantnoble)
-
Participants
-
1 participant joined.
-
Jonathan Holt (Consensys) joined.
-
-
1 organization joined.
-
IBM Corporation joined.
-
GitHub
w3c/vc-data-model
-
4 issues opened.
-
Remove unnecessary limitation for alg JWT attribute w3c/vc-data-model#669, by @awoie.
-
tracking issue for iat → nbf related changes w3c/vc-data-model#667, by @TallTed.
-
Issue 6 and 8 (ZKP and JWT) implementers w3c/vc-data-model#662, by @Iso5786.
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c/vc-data-model#659, by @enuoCM.
-
-
15 issues closed.
-
Remove unnecessary limitation for alg JWT attribute w3c/vc-data-model#669.
-
Issue 6 and 8 (ZKP and JWT) implementers w3c/vc-data-model#662.
-
JSON-LD verifiable credential with multiple subjects w3c/vc-data-model#518.
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c/vc-data-model#659.
-
Terms of Use for credentials should not be at risk, but requires better purposes w3c/vc-data-model#479.
-
"@context" missing in verifiable credentials embedded in verifiable presentation examples w3c/vc-data-model#654.
-
Remove reliance on external URL by allowing primary context to be a JSON Object w3c/vc-data-model#549.
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363.
-
TITLE- Verifiable Credentials Data Model 1.0 w3c/vc-data-model#498.
-
Non-normative sections contain musts w3c/vc-data-model#602.
-
@Context w3c/vc-data-model#604.
-
Section 4.3 w3c/vc-data-model#608.
-
decentralized identifier document w3c/vc-data-model#610.
-
Human readable @context w3c/vc-data-model#585.
-
Using JWT with presentations w3c/vc-data-model#586.
-
-
16 issues received 38 new comments.
-
Issue 6 and 8 (ZKP and JWT) implementers w3c/vc-data-model#662 (8 comments by @brentzundel, @burnburn, @Iso5786)
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c/vc-data-model#659 (6 comments by @brentzundel, @burnburn, @enuoCM)
-
Remove unnecessary limitation for alg JWT attribute w3c/vc-data-model#669 (3 comments by @nadalin, @TallTed)
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436 (1 comment by @msporny)
-
Terms of Use for credentials should not be at risk, but requires better purposes w3c/vc-data-model#479 (1 comment by @burnburn)
-
"@context" missing in verifiable credentials embedded in verifiable presentation examples w3c/vc-data-model#654 (1 comment by @burnburn)
-
Remove reliance on external URL by allowing primary context to be a JSON Object w3c/vc-data-model#549 (1 comment by @burnburn)
-
-
15 pull requests opened.
-
Add further explanation of types. w3c/vc-data-model#674, by @msporny.
-
Update context and associated hash to latest. w3c/vc-data-model#673, by @dlongley.
-
Update index.html w3c/vc-data-model#672, by @TallTed.
-
Update index.html w3c/vc-data-model#671, by @David-Chadwick.
-
fixed #669 -- removed redundant and misleading statement w3c/vc-data-model#670, by @awoie.
-
fixed issue 667 -- renamed iat in nbf w3c/vc-data-model#668, by @awoie.
-
Small typo w3c/vc-data-model#666, by @peacekeeper.
-
Added text clarifying singleton properties w3c/vc-data-model#665, by @brentzundel.
-
Update index.html w3c/vc-data-model#664, by @TallTed.
-
accessibility implementation language tweak w3c/vc-data-model#663, by @TallTed.
-
Expand example context to use terms from ZKP test suite examples. w3c/vc-data-model#661, by @dmitrizagidulin.
-
Property-scope schema and refresh types. w3c/vc-data-model#660, by @dlongley.
-
Clarify type description w3c/vc-data-model#658, by @brentzundel.
-
Update index.html w3c/vc-data-model#657, by @TallTed.
-
language massage around aggregation w3c/vc-data-model#656, by @TallTed.
-
-
21 pull requests merged.
-
Update context and associated hash to latest. w3c/vc-data-model#673.
-
fixed #669 -- removed redundant and misleading statement w3c/vc-data-model#670.
-
Small typo w3c/vc-data-model#666.
-
Added text clarifying singleton properties w3c/vc-data-model#665.
-
Clarify type description w3c/vc-data-model#658.
-
Change proof reference from JWT to JWS. w3c/vc-data-model#652.
-
Rewrite Internationalization section. w3c/vc-data-model#641.
-
Add notes for validFrom and validUntil. w3c/vc-data-model#646.
-
Expand example context to use terms from ZKP test suite examples. w3c/vc-data-model#661.
-
Property-scope schema and refresh types. w3c/vc-data-model#660.
-
Update index.html w3c/vc-data-model#657.
-
language massage around aggregation w3c/vc-data-model#656.
-
Add "@context" in verifiable credentials embedded in verifiable presentation examples w3c/vc-data-model#655.
-
Highlight correlation concerns wrt. identifiers. w3c/vc-data-model#651.
-
Non-substantive guidance for example context URL. w3c/vc-data-model#650.
-
Replace non-normative 'must' with 'is expected to'. w3c/vc-data-model#649.
-
Add holder to presentation in a non-normative way. w3c/vc-data-model#648.
-
Add latest reference to JSON Schema at IETF. w3c/vc-data-model#647.
-
Fix TR links to point to new vc-data-model URL. w3c/vc-data-model#645.
-
Add multiple subjects example. w3c/vc-data-model#644.
-
Add mentions of ToS usage based on feedback from @RieksJ. w3c/vc-data-model#643.
-
-
3 pull requests closed.
-
accessibility implementation language tweak w3c/vc-data-model#663.
-
Update index.html w3c/vc-data-model#671.
-
Update index.html w3c/vc-data-model#664.
-
-
15 pull requests received 134 new comments.
-
Rewrite Internationalization section. w3c/vc-data-model#641 (44 comments by @aphillips, @brentzundel, @chaals, @dlongley, @msporny, @r12a, @TallTed)
-
Clarify type description w3c/vc-data-model#658 (43 comments by @brentzundel, @burnburn, @David-Chadwick, @dlongley, @msporny, @TallTed)
-
Change proof reference from JWT to JWS. w3c/vc-data-model#652 (12 comments by @burnburn, @msporny, @nadalin, @TallTed)
-
Add notes for validFrom and validUntil. w3c/vc-data-model#646 (9 comments by @dlongley, @msporny, @stonematt, @TallTed)
-
Added text clarifying singleton properties w3c/vc-data-model#665 (6 comments by @dmitrizagidulin, @msporny)
-
fixed #669 -- removed redundant and misleading statement w3c/vc-data-model#670 (3 comments by @dlongley, @mirceanis, @TallTed)
-
Add latest reference to JSON Schema at IETF. w3c/vc-data-model#647 (3 comments by @burnburn, @msporny, @TallTed)
-
w3c/vc-use-cases
-
8 issues closed.
-
Law-Enforcement Process w3c/vc-use-cases#23.
-
Digital Wallet Portability w3c/vc-use-cases#26.
-
Pseudo-anonymity w3c/vc-use-cases#27.
-
Digital Receipts w3c/vc-use-cases#28.
-
Clothing w3c/vc-use-cases#29.
-
Add use-case 'Fraud Detection' in retail section w3c/vc-use-cases#94.
-
Questions on sub-credentials w3c/vc-use-cases#99.
-
-
7 issues received 9 new comments.
-
w3c/vc-use-cases#23 (1 comment by @jandrieu)
-
w3c/vc-use-cases#26 (1 comment by @jandrieu)
-
w3c/vc-use-cases#27 (1 comment by @jandrieu)
-
w3c/vc-use-cases#29 (1 comment by @jandrieu)
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (1 comment by @stonematt)
-
3 pull requests opened.
-
Update order of User Needs w3c/vc-use-cases#102, by @stonematt.
-
adds use case from RieksJ, fixes terminology w3c/vc-use-cases#101, by @TallTed.
-
added PADI focal use case w3c/vc-use-cases#100, by @jandrieu.
-
-
5 pull requests merged.
-
adds use case from RieksJ, fixes terminology w3c/vc-use-cases#101.
-
fixes #94 - Added use case R.3 Fraud detection w3c/vc-use-cases#98.
-
Update link to common glossary w3c/vc-use-cases#87.
-
Add example for International Travel with Minor w3c/vc-use-cases#86.
-
Update README.md w3c/vc-use-cases#93.
-
-
6 pull requests received 8 new comments.
-
Add example for International Travel with Minor w3c/vc-use-cases#86 (2 comments by @jandrieu, @stonematt)
w3c/vc-test-suite
-
6 issues opened.
-
Passing tests against the testsuite are not correctly summarized in the report w3c/vc-test-suite#59, by @ken-ebert.
-
`proof` field in JWT encoding test is expected in wrong location when no-JWS is requested w3c/vc-test-suite#54, by @mirceanis.
-
Example input files contain embedded html for international language examples. w3c/vc-test-suite#47, by @ken-ebert.
-
"node generate.js" results in "TypeError: Cannot convert undefined or null to object" w3c/vc-test-suite#45, by @brentzundel.
-
ZKP verifiable credential w3c/vc-test-suite#44, by @yancyribbens.
-
test-suit should remain implementation agnostic w3c/vc-test-suite#43, by @yancyribbens.
-
-
8 issues closed.
-
Missing copyright w3c/vc-test-suite#23.
-
Should we pass resources to issuers / verifiers? w3c/vc-test-suite#2.
-
"node generate.js" results in "TypeError: Cannot convert undefined or null to object" w3c/vc-test-suite#45.
-
Example input files contain embedded html for international language examples. w3c/vc-test-suite#47.
-
ZKP verifiable credential w3c/vc-test-suite#44.
-
test-suit should remain implementation agnostic w3c/vc-test-suite#43.
-
Contained verifiable credential in a verifiable presentation is missing context. w3c/vc-test-suite#31.
-
-
15 issues received 22 new comments.
-
"node generate.js" results in "TypeError: Cannot convert undefined or null to object" w3c/vc-test-suite#45 (3 comments by @brentzundel, @dmitrizagidulin, @TallTed)
-
Passing tests against the testsuite are not correctly summarized in the report w3c/vc-test-suite#59 (2 comments by @dmitrizagidulin)
-
Report is non-specific in its categorization of tests w3c/vc-test-suite#30 (2 comments by @dmitrizagidulin)
-
Should we pass resources to issuers / verifiers? w3c/vc-test-suite#2 (1 comment by @dmitrizagidulin)
-
Example input files contain embedded html for international language examples. w3c/vc-test-suite#47 (1 comment by @dmitrizagidulin)
-
Contained verifiable credential in a verifiable presentation is missing context. w3c/vc-test-suite#31 (1 comment by @dmitrizagidulin)
-
-
20 pull requests opened.
-
Change to rfc3339 date times w3c/vc-test-suite#65, by @aljones15.
-
Refactor conformance results tables w3c/vc-test-suite#64, by @dmitrizagidulin.
-
Remove negative proof test. w3c/vc-test-suite#63, by @dmitrizagidulin.
-
Create Toulouse-Kent-report.json w3c/vc-test-suite#62, by @David-Chadwick.
-
Update to RFC3339. w3c/vc-test-suite#61, by @aljones15.
-
Add copyright, license. w3c/vc-test-suite#60, by @dmitrizagidulin.
-
Re-run implementations UI based on latest versions. w3c/vc-test-suite#58, by @dmitrizagidulin.
-
Fix generation w3c/vc-test-suite#57, by @dmitrizagidulin.
-
Fix -report filename in README w3c/vc-test-suite#56, by @peacekeeper.
-
Fix no jws test w3c/vc-test-suite#55, by @mirceanis.
-
added uport test report w3c/vc-test-suite#53, by @awoie.
-
Preliminary DanubeTech implementation report. w3c/vc-test-suite#52, by @peacekeeper.
-
add link to draft implementation report w3c/vc-test-suite#51, by @TallTed.
-
added support for JWT test cases support w3c/vc-test-suite#50, by @awoie.
-
add Credly implementation report w3c/vc-test-suite#49, by @yancyribbens.
-
Remove html from attribute values in example files. w3c/vc-test-suite#48, by @ken-ebert.
-
Evernym test suite report, first submission w3c/vc-test-suite#46, by @brentzundel.
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#42, by @ken-ebert.
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#41, by @ken-ebert.
-
Update README.md w3c/vc-test-suite#40, by @TallTed.
-
-
20 pull requests merged.
-
Remove negative proof test. w3c/vc-test-suite#63.
-
Update to RFC3339. w3c/vc-test-suite#61.
-
Add copyright, license. w3c/vc-test-suite#60.
-
Re-run implementations UI based on latest versions. w3c/vc-test-suite#58.
-
Fix no jws test w3c/vc-test-suite#55.
-
added uport test report w3c/vc-test-suite#53.
-
Preliminary DanubeTech implementation report. w3c/vc-test-suite#52.
-
Fix generation w3c/vc-test-suite#57.
-
add link to draft implementation report w3c/vc-test-suite#51.
-
Fix -report filename in README w3c/vc-test-suite#56.
-
added support for JWT test cases support w3c/vc-test-suite#50.
-
add Credly implementation report w3c/vc-test-suite#49.
-
Remove html from attribute values in example files. w3c/vc-test-suite#48.
-
Test suite sequence diagram w3c/vc-test-suite#36.
-
Evernym test suite report, first submission w3c/vc-test-suite#46.
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#42.
-
Update zkp examples w3c/vc-test-suite#39.
-
ZKP tests for verifiable presentations w3c/vc-test-suite#38.
-
Update README.md w3c/vc-test-suite#40.
-
Add @context to embedded verifiable credentials within verifiable presentations w3c/vc-test-suite#37.
-
-
1 pull request closed.
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#41.
-
-
13 pull requests received 25 new comments.
-
added support for JWT test cases support w3c/vc-test-suite#50 (6 comments by @awoie, @dmitrizagidulin, @stonematt, @TallTed)
-
ZKP tests for verifiable presentations w3c/vc-test-suite#38 (4 comments by @brentzundel, @dlongley, @dmitrizagidulin)
-
Preliminary DanubeTech implementation report. w3c/vc-test-suite#52 (2 comments by @peacekeeper, @TallTed)
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#41 (2 comments by @ken-ebert)
-
Preliminary test result for Sovrin implementation of VC Data Model test suite. w3c/vc-test-suite#42 (1 comment by @ken-ebert)
-
Add @context to embedded verifiable credentials within verifiable presentations w3c/vc-test-suite#37 (1 comment by @brentzundel)
-
w3c/vc-imp-guide
-
1 issue opened.
-
Add section detailing how to author a new VC (semantics and schema) w3c/vc-imp-guide#16, by @dlongley.
-
-
3 issues closed.
-
Use of aliases and extending VCs w3c/vc-imp-guide#10.
-
@context value ordering w3c/vc-imp-guide#9.
-
Reference or attach generic (not-credential) data in credential w3c/vc-imp-guide#5.
-
-
9 issues received 13 new comments.
-
Add sections outlining benefits of different syntax + proof formats w3c/vc-imp-guide#8 (2 comments by @burnburn)
-
Determine how/if WebAuthn will work with VCs w3c/vc-imp-guide#3 (2 comments by @David-Chadwick, @msporny)
-
Add section detailing how to author a new VC (semantics and schema) w3c/vc-imp-guide#16 (1 comment by @dlongley)
-
Suggestions on how to do progressive trust or graceful degredation w3c/vc-imp-guide#6 (1 comment by @burnburn)
-
Reference or attach generic (not-credential) data in credential w3c/vc-imp-guide#5 (1 comment by @burnburn)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials (see pending PR #17) w3c/vc-imp-guide#1 (1 comment by @burnburn)
-
3 pull requests merged.
-
(editorial) fix typos and punctuation w3c/vc-imp-guide#15.
-
Added section on benefits of ZKP proofs w3c/vc-imp-guide#12.
-
Update README.md w3c/vc-imp-guide#11.
-
-
2 pull requests received 4 new comments.
-
Added sections on identifiers and proofs w3c/vc-imp-guide#7 (3 comments by @burnburn, @deiu, @TallTed)
-
Participants
-
1 participant joined.
-
Jack Busa (W3C) joined.
-
-
1 organization joined.
-
Kaiser Permanente joined.
-
GitHub
w3c/vc-test-suite
-
12 issues opened.
-
Contained verifiable credential in a verifiable presentation is missing context. w3c/vc-test-suite#31, by @ken-ebert.
-
Report is non-specific in its categorization of tests w3c/vc-test-suite#30, by @brentzundel.
-
README directions are incorrect w3c/vc-test-suite#29, by @brentzundel.
-
Report generation fails w3c/vc-test-suite#28, by @brentzundel.
-
example input proof objects need type fields w3c/vc-test-suite#26, by @brentzundel.
-
example-5-bad-proof w3c/vc-test-suite#24, by @brentzundel.
-
Missing copyright w3c/vc-test-suite#23, by @aljones15.
-
Tests are checking for ISO8601 w3c/vc-test-suite#22, by @brentzundel.
-
Timeout w3c/vc-test-suite#21, by @brentzundel.
-
Test - @context MUST be one or more URIs (negative) w3c/vc-test-suite#20, by @brentzundel.
-
JSON-LD context is Invalid JSON w3c/vc-test-suite#19, by @yancyribbens.
-
Wrong content type w3c/vc-test-suite#18, by @yancyribbens.
-
-
4 issues closed.
-
README directions are incorrect w3c/vc-test-suite#29.
-
example input proof objects need type fields w3c/vc-test-suite#26.
-
example-5-bad-proof w3c/vc-test-suite#24.
-
Test - @context MUST be one or more URIs (negative) w3c/vc-test-suite#20.
-
-
12 issues received 29 new comments.
-
Test - @context MUST be one or more URIs (negative) w3c/vc-test-suite#20 (5 comments by @brentzundel, @dmitrizagidulin, @msporny)
-
Report generation fails w3c/vc-test-suite#28 (3 comments by @brentzundel, @dmitrizagidulin, @yancyribbens)
-
Contained verifiable credential in a verifiable presentation is missing context. w3c/vc-test-suite#31 (3 comments by @dlongley, @dmitrizagidulin)
-
JSON-LD context is Invalid JSON w3c/vc-test-suite#19 (3 comments by @dmitrizagidulin, @yancyribbens)
-
Report is non-specific in its categorization of tests w3c/vc-test-suite#30 (2 comments by @dmitrizagidulin, @ken-ebert)
-
11 pull requests opened.
-
Update zkp examples w3c/vc-test-suite#39, by @brentzundel.
-
ZKP tests for verifiable presentations w3c/vc-test-suite#38, by @brentzundel.
-
Add @context to embedded verifiable credentials within verifiable presentations w3c/vc-test-suite#37, by @ken-ebert.
-
Test suite sequence diagram w3c/vc-test-suite#36, by @awoie.
-
Add tests for ZKP Verifiable Credentials w3c/vc-test-suite#35, by @brentzundel.
-
Replace nonce with challenge, add jws and proofPurpose. w3c/vc-test-suite#34, by @dmitrizagidulin.
-
Fix implementations/ dir typo. w3c/vc-test-suite#33, by @dmitrizagidulin.
-
Change example type to resolving RsaSignature2018. w3c/vc-test-suite#32, by @dmitrizagidulin.
-
added type to proofs w3c/vc-test-suite#27, by @brentzundel.
-
fixed proof JSON-LD for test input w3c/vc-test-suite#25, by @brentzundel.
-
Update vc.js implementation report to show optional skipped. w3c/vc-test-suite#17, by @dmitrizagidulin.
-
-
10 pull requests merged.
-
Add tests for ZKP Verifiable Credentials w3c/vc-test-suite#35.
-
Fix implementations/ dir typo. w3c/vc-test-suite#33.
-
Change example type to resolving RsaSignature2018. w3c/vc-test-suite#32.
-
Replace nonce with challenge, add jws and proofPurpose. w3c/vc-test-suite#34.
-
fixed proof JSON-LD for test input w3c/vc-test-suite#25.
-
added type to proofs w3c/vc-test-suite#27.
-
Update vc.js implementation report to show optional skipped. w3c/vc-test-suite#17.
-
Update README.md w3c/vc-test-suite#13.
-
Add additional tests required by CR 1. w3c/vc-test-suite#15.
-
Add implementation report for vc-js lib. w3c/vc-test-suite#16.
-
-
8 pull requests received 26 new comments.
-
Add additional tests required by CR 1. w3c/vc-test-suite#15 (8 comments by @brentzundel, @dmitrizagidulin, @msporny)
-
Replace nonce with challenge, add jws and proofPurpose. w3c/vc-test-suite#34 (7 comments by @dlongley, @dmitrizagidulin)
-
Add tests for ZKP Verifiable Credentials w3c/vc-test-suite#35 (4 comments by @brentzundel, @dmitrizagidulin)
-
Update vc.js implementation report to show optional skipped. w3c/vc-test-suite#17 (1 comment by @dmitrizagidulin)
-
w3c/vc-data-model
-
26 issues opened.
-
"@context" missing in verifiable credentials embedded in verifiable presentation examples w3c/vc-data-model#654, by @ken-ebert.
-
The confusing nature of type and presentation w3c/vc-data-model#653, by @brentzundel.
-
Protocol buffer support w3c/vc-data-model#642, by @richburdon.
-
ZKP section seems un-testable w3c/vc-data-model#639, by @brentzundel.
-
JWT examples use strings instead of NumericDate for iat, exp w3c/vc-data-model#637, by @awoie.
-
Minor jti inconsistency/typo w3c/vc-data-model#635, by @awoie.
-
Tracking Issue: JWT-only support w3c/vc-data-model#634, by @burnburn.
-
Tracking Issue: JSON-LD concerns w3c/vc-data-model#633, by @burnburn.
-
Tracking Issue: Interoperability w3c/vc-data-model#632, by @burnburn.
-
Example context needs updating w3c/vc-data-model#622, by @dmitrizagidulin.
-
Clarification on JSON types w3c/vc-data-model#621, by @awoie.
-
Expiration w3c/vc-data-model#613, by @nadalin.
-
Proofs Note w3c/vc-data-model#612, by @nadalin.
-
decentralized identifier document w3c/vc-data-model#610, by @nadalin.
-
Conformance w3c/vc-data-model#609, by @nadalin.
-
Section 4.3 w3c/vc-data-model#608, by @nadalin.
-
Section 4.2 w3c/vc-data-model#606, by @nadalin.
-
Example URI w3c/vc-data-model#605, by @nadalin.
-
Patent Policy w3c/vc-data-model#603, by @nadalin.
-
Non-normative sections contain musts w3c/vc-data-model#602, by @nadalin.
-
Example VerifiablePresentation types need updating w3c/vc-data-model#600, by @dmitrizagidulin.
-
Recommend adding `holder` to non-ZKP VPs in implementation guide w3c/vc-data-model#596, by @dlongley.
-
JSON schema reference w3c/vc-data-model#589, by @David-Chadwick.
-
Using JWT with presentations w3c/vc-data-model#586, by @David-Chadwick.
-
-
31 issues closed.
-
Example VerifiablePresentation types need updating w3c/vc-data-model#600.
-
Disputes w3c/vc-data-model#545.
-
Example context needs updating w3c/vc-data-model#622.
-
Expiration w3c/vc-data-model#613.
-
Proofs w3c/vc-data-model#611.
-
ZKP section seems un-testable w3c/vc-data-model#639.
-
JWT examples use strings instead of NumericDate for iat, exp w3c/vc-data-model#637.
-
Minor jti inconsistency/typo w3c/vc-data-model#635.
-
verifiable presentation w3c/vc-data-model#559.
-
4.9 Status w3c/vc-data-model#500.
-
4.10 Presentations w3c/vc-data-model#488.
-
5.3.1 Semantic Interoperability w3c/vc-data-model#525.
-
4.7 Proofs w3c/vc-data-model#489.
-
4.7 Proofs w3c/vc-data-model#487.
-
4.7 Proofs w3c/vc-data-model#486.
-
4.3 Types w3c/vc-data-model#484.
-
@Context w3c/vc-data-model#557.
-
Make a JWT a VC and not to encapsulate the VC inside a JWT w3c/vc-data-model#520.
-
4.8 Expiration w3c/vc-data-model#496.
-
8.2 Content Integrity Protection w3c/vc-data-model#494.
-
8. Security Considerations w3c/vc-data-model#493.
-
problematic phrasing in 4.2 https://w3c.github.io/vc-data-model/#identifiers w3c/vc-data-model#556.
-
unclear bit of text in "JWT Encoding" section w3c/vc-data-model#552.
-
Add informative references to LD Proofs, LD Signatures, detached JWS, and RsaSignature2018 w3c/vc-data-model#543.
-
Can JWT represent a verifiable credential with multiple subjects w3c/vc-data-model#511.
-
Schema vs @context w3c/vc-data-model#474.
-
JWS Examples and JOSE Consistency w3c/vc-data-model#470.
-
Refreshing questions w3c/vc-data-model#458.
-
Patent Policy w3c/vc-data-model#603.
-
Appendix examples not complete w3c/vc-data-model#551.
-
Section 5 normative and non-normative parts w3c/vc-data-model#524.
-
-
1 issue reopened.
-
JWS Examples and JOSE Consistency w3c/vc-data-model#470, by @burnburn.
-
-
55 issues received 172 new comments.
-
Clarification on JSON types w3c/vc-data-model#621 (15 comments by @awoie, @dlongley, @mirceanis, @msporny, @RorschachRev)
-
decentralized identifier document w3c/vc-data-model#610 (10 comments by @brentzundel, @burnburn, @nadalin, @TallTed)
-
Human readable @context w3c/vc-data-model#585 (10 comments by @burnburn, @David-Chadwick, @gkellogg, @msporny)
-
misleadingly and confusingly named issuanceDate w3c/vc-data-model#584 (8 comments by @burnburn, @David-Chadwick, @msporny, @TallTed)
-
Non-normative sections contain musts w3c/vc-data-model#602 (7 comments by @burnburn, @msporny, @nadalin, @TallTed)
-
Using JWT with presentations w3c/vc-data-model#586 (7 comments by @awoie, @burnburn, @David-Chadwick, @msporny)
-
Section 4.3 w3c/vc-data-model#608 (6 comments by @burnburn, @David-Chadwick, @msporny, @nadalin, @TallTed)
-
Recommend adding `holder` to non-ZKP VPs in implementation guide w3c/vc-data-model#596 (5 comments by @burnburn, @David-Chadwick, @msporny)
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436 (4 comments by @BigBlueHat, @msporny)
-
Example context needs updating w3c/vc-data-model#622 (3 comments by @burnburn, @dmitrizagidulin, @msporny)
-
Make a JWT a VC and not to encapsulate the VC inside a JWT w3c/vc-data-model#520 (3 comments by @burnburn, @msporny)
-
Remove reliance on external URL by allowing primary context to be a JSON Object w3c/vc-data-model#549 (3 comments by @msporny, @yancyribbens)
-
Example VerifiablePresentation types need updating w3c/vc-data-model#600 (2 comments by @burnburn, @dmitrizagidulin)
-
JSON-LD verifiable credential with multiple subjects w3c/vc-data-model#518 (2 comments by @burnburn, @msporny)
-
Terms of Use for credentials should not be at risk, but requires better purposes w3c/vc-data-model#479 (2 comments by @msporny, @RieksJ)
-
Add informative references to LD Proofs, LD Signatures, detached JWS, and RsaSignature2018 w3c/vc-data-model#543 (2 comments by @burnburn, @msporny)
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480 (2 comments by @burnburn, @RieksJ)
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363 (1 comment by @brentzundel)
-
Can JWT represent a verifiable credential with multiple subjects w3c/vc-data-model#511 (1 comment by @burnburn)
-
Consolidate all Verifiable Credential Registries to a single registry w3c/vc-data-model#530 (1 comment by @msporny)
-
-
44 pull requests opened.
-
Add "@context" in verifiable credentials embedded in verifiable presentation examples w3c/vc-data-model#655, by @ken-ebert.
-
Change proof reference from JWT to JWS. w3c/vc-data-model#652, by @msporny.
-
Highlight correlation concerns wrt. identifiers. w3c/vc-data-model#651, by @msporny.
-
Non-substantive guidance for example context URL. w3c/vc-data-model#650, by @msporny.
-
Replace non-normative 'must' with 'is expected to'. w3c/vc-data-model#649, by @msporny.
-
Add holder to presentation in a non-normative way. w3c/vc-data-model#648, by @msporny.
-
Add latest reference to JSON Schema at IETF. w3c/vc-data-model#647, by @msporny.
-
Add notes for validFrom and validUntil. w3c/vc-data-model#646, by @msporny.
-
Fix TR links to point to new vc-data-model URL. w3c/vc-data-model#645, by @msporny.
-
Add multiple subjects example. w3c/vc-data-model#644, by @msporny.
-
Add mentions of ToS usage based on feedback from @RieksJ. w3c/vc-data-model#643, by @msporny.
-
Rewrite Internationalization section. w3c/vc-data-model#641, by @msporny.
-
Zkp section clarifying language w3c/vc-data-model#640, by @brentzundel.
-
Fixes #637 -- JWT examples now using NumericDate instead of String w3c/vc-data-model#638, by @awoie.
-
Fixes #635 -- minor jti inconsistency/typo w3c/vc-data-model#636, by @awoie.
-
clarify when type property is required w3c/vc-data-model#631, by @TallTed.
-
clarified @context processing w3c/vc-data-model#630, by @brentzundel.
-
Alt Disputes w3c/vc-data-model#629, by @David-Chadwick.
-
even less @id optionality ambiguity w3c/vc-data-model#628, by @TallTed.
-
Addition to Presentation Proofs and JWT w3c/vc-data-model#627, by @David-Chadwick.
-
Update index.html w3c/vc-data-model#626, by @TallTed.
-
Update index.html w3c/vc-data-model#625, by @TallTed.
-
Added detailed lifecycle diagram and revised explanatory text details w3c/vc-data-model#624, by @ken-ebert.
-
Fix invalid context entries, add required fields. w3c/vc-data-model#623, by @dmitrizagidulin.
-
Update definition of issuance date w3c/vc-data-model#620, by @David-Chadwick.
-
Update LD proof examples. w3c/vc-data-model#619, by @dlongley.
-
name DID document in terminology section w3c/vc-data-model#618, by @TallTed.
-
require proof details as well as mechanism w3c/vc-data-model#617, by @TallTed.
-
Made optional nature of id more explicit w3c/vc-data-model#616, by @brentzundel.
-
clarify that expirationDate is optional w3c/vc-data-model#615, by @TallTed.
-
rephrasing of proof mechanism note w3c/vc-data-model#614, by @TallTed.
-
adjust example context text w3c/vc-data-model#607, by @TallTed.
-
Update VerifiablePresentation types in examples. w3c/vc-data-model#601, by @dmitrizagidulin.
-
Move Disputes section to Implementation Guidance. w3c/vc-data-model#599, by @msporny.
-
Note difference between data schemas and @context. w3c/vc-data-model#598, by @msporny.
-
Note the end of Candidate Recommendation comment period. w3c/vc-data-model#597, by @msporny.
-
Update @context definition w3c/vc-data-model#595, by @David-Chadwick.
-
Add warning related to multiple subjects and JWTs. w3c/vc-data-model#594, by @msporny.
-
Explain and link to proof specs. w3c/vc-data-model#593, by @msporny.
-
Explain why order is important in @context property. w3c/vc-data-model#592, by @msporny.
-
Refer to Verifiable Credentials Extension Registry. w3c/vc-data-model#591, by @msporny.
-
Add IANA Considerations section. Related to #520. w3c/vc-data-model#590, by @msporny.
-
clarify language around @context w3c/vc-data-model#588, by @TallTed.
-
add base context to the appendix with a corresponding hash w3c/vc-data-model#587, by @yancyribbens.
-
-
31 pull requests merged.
-
add base context to the appendix with a corresponding hash w3c/vc-data-model#587.
-
Zkp section clarifying language w3c/vc-data-model#640.
-
Fixes #637 -- JWT examples now using NumericDate instead of String w3c/vc-data-model#638.
-
Fixes #635 -- minor jti inconsistency/typo w3c/vc-data-model#636.
-
clarify when type property is required w3c/vc-data-model#631.
-
clarified @context processing w3c/vc-data-model#630.
-
even less @id optionality ambiguity w3c/vc-data-model#628.
-
Addition to Presentation Proofs and JWT w3c/vc-data-model#627.
-
Update index.html w3c/vc-data-model#626.
-
Update index.html w3c/vc-data-model#625.
-
Added detailed lifecycle diagram and revised explanatory text details w3c/vc-data-model#624.
-
Update LD proof examples. w3c/vc-data-model#619.
-
rephrasing of proof mechanism note w3c/vc-data-model#614.
-
Alt Disputes w3c/vc-data-model#629.
-
Fix invalid context entries, add required fields. w3c/vc-data-model#623.
-
Update definition of issuance date w3c/vc-data-model#620.
-
name DID document in terminology section w3c/vc-data-model#618.
-
require proof details as well as mechanism w3c/vc-data-model#617.
-
Made optional nature of id more explicit w3c/vc-data-model#616.
-
clarify that expirationDate is optional w3c/vc-data-model#615.
-
adjust example context text w3c/vc-data-model#607.
-
Update VerifiablePresentation types in examples. w3c/vc-data-model#601.
-
Note difference between data schemas and @context. w3c/vc-data-model#598.
-
Note the end of Candidate Recommendation comment period. w3c/vc-data-model#597.
-
Update @context definition w3c/vc-data-model#595.
-
Add warning related to multiple subjects and JWTs. w3c/vc-data-model#594.
-
Explain and link to proof specs. w3c/vc-data-model#593.
-
Explain why order is important in @context property. w3c/vc-data-model#592.
-
Refer to Verifiable Credentials Extension Registry. w3c/vc-data-model#591.
-
Add IANA Considerations section. Related to #520. w3c/vc-data-model#590.
-
clarify language around @context w3c/vc-data-model#588.
-
-
2 pull requests closed.
-
Move Disputes section to Implementation Guidance. w3c/vc-data-model#599.
-
"final holder" may not be "final" w3c/vc-data-model#577.
-
-
27 pull requests received 153 new comments.
-
Rewrite Internationalization section. w3c/vc-data-model#641 (35 comments by @aphillips, @chaals, @msporny)
-
Added detailed lifecycle diagram and revised explanatory text details w3c/vc-data-model#624 (33 comments by @David-Chadwick, @ken-ebert, @msporny, @TallTed)
-
Update LD proof examples. w3c/vc-data-model#619 (12 comments by @brentzundel, @ChristopherA, @dlongley, @msporny)
-
add base context to the appendix with a corresponding hash w3c/vc-data-model#587 (9 comments by @dlongley, @msporny, @TallTed, @yancyribbens)
-
clarify when type property is required w3c/vc-data-model#631 (8 comments by @David-Chadwick, @dlongley, @TallTed)
-
Update @context definition w3c/vc-data-model#595 (7 comments by @brentzundel, @David-Chadwick, @msporny, @TallTed)
-
Move Disputes section to Implementation Guidance. w3c/vc-data-model#599 (6 comments by @David-Chadwick, @jricher, @msporny, @TallTed)
-
Update definition of issuance date w3c/vc-data-model#620 (4 comments by @brentzundel, @David-Chadwick)
-
Addition to Presentation Proofs and JWT w3c/vc-data-model#627 (3 comments by @David-Chadwick, @msporny)
-
Fix invalid context entries, add required fields. w3c/vc-data-model#623 (3 comments by @dmitrizagidulin, @msporny)
-
Add warning related to multiple subjects and JWTs. w3c/vc-data-model#594 (3 comments by @brentzundel, @David-Chadwick, @msporny)
-
Note difference between data schemas and @context. w3c/vc-data-model#598 (2 comments by @David-Chadwick, @msporny)
-
Made optional nature of id more explicit w3c/vc-data-model#616 (2 comments by @brentzundel, @TallTed)
-
Refer to Verifiable Credentials Extension Registry. w3c/vc-data-model#591 (2 comments by @brentzundel, @msporny)
-
Fixes #637 -- JWT examples now using NumericDate instead of String w3c/vc-data-model#638 (1 comment by @awoie)
-
Explain why order is important in @context property. w3c/vc-data-model#592 (1 comment by @David-Chadwick)
-
w3c/vc-imp-guide
-
3 pull requests opened.
-
(editorial) fix typos and punctuation w3c/vc-imp-guide#15, by @TallTed.
-
Progressive Trust w3c/vc-imp-guide#14, by @brentzundel.
-
Editorial: Indentation fix w3c/vc-imp-guide#13, by @brentzundel.
-
-
1 pull request received 10 new comments.
-
Added section on benefits of ZKP proofs w3c/vc-imp-guide#12 (10 comments by @brentzundel, @ken-ebert)
-
w3c/vc-use-cases
-
5 issues opened.
-
Questions on sub-credentials w3c/vc-use-cases#99, by @anthonycamilleri.
-
Please note that "inspector" is a deprecated term; these should all be changed to "verifier". w3c/vc-use-cases#97, by @RieksJ.
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96, by @RieksJ.
-
Add user task 'Trust claim' w3c/vc-use-cases#95, by @RieksJ.
-
Add use-case 'Fraud Detection' in retail section w3c/vc-use-cases#94, by @RieksJ.
-
-
3 issues received 4 new comments.
-
Add task 'Check revocation' and use-case that demonstrates its use/need w3c/vc-use-cases#96 (1 comment by @TallTed)
-
1 pull request opened.
-
fixes #94 - Added use case R.3 Fraud detection w3c/vc-use-cases#98, by @RieksJ.
-
-
1 pull request received 1 new comment.
Participants
-
2 participants left.
-
Andrei Sambra (AKASHA Foundation) left.
-
Matt Stone (BrightLink) left.
-
-
2 organizations joined.
-
AKASHA Foundation joined.
-
BrightLink joined.
-
GitHub
w3c/vc-data-model
-
22 issues opened.
-
Human readable @context w3c/vc-data-model#585, by @David-Chadwick.
-
misleadingly and confusingly named issuanceDate w3c/vc-data-model#584, by @TallTed.
-
(editorial) problem with the trust model w3c/vc-data-model#560, by @TallTed.
-
verifiable presentation w3c/vc-data-model#559, by @nadalin.
-
@Context Processing w3c/vc-data-model#558, by @nadalin.
-
problematic phrasing in 4.2 https://w3c.github.io/vc-data-model/#identifiers w3c/vc-data-model#556, by @TallTed.
-
unclear bit of text in "JWT Encoding" section w3c/vc-data-model#552, by @TallTed.
-
Appendix examples not complete w3c/vc-data-model#551, by @David-Chadwick.
-
Remove reliance on external URL by allowing primary context to be a JSON Object w3c/vc-data-model#549, by @yancyribbens.
-
Disputes w3c/vc-data-model#545, by @David-Chadwick.
-
Add informative references to LD Proofs, LD Signatures, detached JWS, and RsaSignature2018 w3c/vc-data-model#543, by @msporny.
-
Decoding rules for jti and sub are mixed up w3c/vc-data-model#541, by @awoie.
-
JSON-LD Reference w3c/vc-data-model#537, by @nadalin.
-
Consolidate all Verifiable Credential Registries to a single registry w3c/vc-data-model#530, by @msporny.
-
Change W3C TR link to vc-data-model w3c/vc-data-model#526, by @msporny.
-
5.3.1 Semantic Interoperability w3c/vc-data-model#525, by @nadalin.
-
Section 5 normative and non-normative parts w3c/vc-data-model#524, by @nadalin.
-
Section 4 normative and non-normative parts w3c/vc-data-model#523, by @nadalin.
-
Is Proof mandatory in Verifiable Presentation? w3c/vc-data-model#521, by @chaoxinhu.
-
Make a JWT a VC and not to encapsulate the VC inside a JWT w3c/vc-data-model#520, by @nadalin.
-
JSON-LD verifiable credential with multiple subjects w3c/vc-data-model#518, by @awoie.
-
-
23 issues closed.
-
8.4 Token Binding w3c/vc-data-model#495.
-
5.3.1 Semantic Interoperability w3c/vc-data-model#491.
-
Normative terminology (e.g. MUST) in sections marked non-normative w3c/vc-data-model#394.
-
Add "information related to the kind/type of credential" as a bullet in section 1.1 w3c/vc-data-model#462.
-
Not every entity can perform a role in the ecosystem. w3c/vc-data-model#463.
-
Does 'subject' relate to credentials or to claims? w3c/vc-data-model#464.
-
Faulty description of the issuer role w3c/vc-data-model#466.
-
Implied lack of governance Requirement in issuer/holder/verifier w3c/vc-data-model#471.
-
Holder signature in presentation does not indicate consent w3c/vc-data-model#472.
-
Subject matters (conflicting definitions, meaningless use, ...) w3c/vc-data-model#481.
-
Section 4.1 Context w3c/vc-data-model#483.
-
7.17 In-Private w3c/vc-data-model#492.
-
Decoding rules for jti and sub are mixed up w3c/vc-data-model#541.
-
4.5 Issuer w3c/vc-data-model#485.
-
Section 4 normative and non-normative parts w3c/vc-data-model#523.
-
Normative Reference w3c/vc-data-model#513.
-
5.2 Trust Model w3c/vc-data-model#490.
-
(editorial) problem with the trust model w3c/vc-data-model#560.
-
protocol statement in id section w3c/vc-data-model#478.
-
Charter w3c/vc-data-model#502.
-
Decide if there should be an EOL date on the spec? w3c/vc-data-model#253.
-
Introduction is misleading w3c/vc-data-model#482.
-
Is Proof mandatory in Verifiable Presentation? w3c/vc-data-model#521.
-
-
2 issues reopened.
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363, by @TallTed.
-
Coordinate with PING during review process w3c/vc-data-model#222, by @burnburn.
-
-
57 issues received 326 new comments.
-
4.3 Types w3c/vc-data-model#484 (26 comments by @brentzundel, @David-Chadwick, @dlongley, @msporny, @nadalin, @stonematt)
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480 (15 comments by @awoie, @brentzundel, @David-Chadwick, @dlongley, @jandrieu, @ken-ebert, @msporny, @RieksJ, @talltree)
-
Make a JWT a VC and not to encapsulate the VC inside a JWT w3c/vc-data-model#520 (15 comments by @awoie, @brentzundel, @chaals, @msporny, @nadalin, @stonematt)
-
Section 5 normative and non-normative parts w3c/vc-data-model#524 (15 comments by @David-Chadwick, @msporny, @nadalin, @stonematt)
-
Remove reliance on external URL by allowing primary context to be a JSON Object w3c/vc-data-model#549 (14 comments by @dlongley, @msporny, @rhiaro, @stonematt, @TallTed, @yancyribbens)
-
4.7 Proofs w3c/vc-data-model#486 (13 comments by @awoie, @brentzundel, @David-Chadwick, @msporny, @nadalin, @stonematt)
-
5.3.1 Semantic Interoperability w3c/vc-data-model#491 (12 comments by @brentzundel, @David-Chadwick, @msporny, @nadalin, @stonematt)
-
verifiable presentation w3c/vc-data-model#559 (11 comments by @brentzundel, @jandrieu, @msporny, @nadalin, @stonematt)
-
Normative Reference w3c/vc-data-model#513 (11 comments by @awoie, @brentzundel, @nadalin, @stonematt)
-
protocol statement in id section w3c/vc-data-model#478 (9 comments by @brentzundel, @David-Chadwick, @ken-ebert, @msporny, @TallTed)
-
4.8 Expiration w3c/vc-data-model#496 (8 comments by @awoie, @brentzundel, @msporny, @nadalin, @stonematt)
-
4.7 Proofs w3c/vc-data-model#489 (8 comments by @brentzundel, @David-Chadwick, @msporny, @nadalin, @stonematt)
-
8.2 Content Integrity Protection w3c/vc-data-model#494 (7 comments by @brentzundel, @nadalin, @stonematt)
-
Section 4.1 Context w3c/vc-data-model#483 (7 comments by @brentzundel, @chaals, @msporny, @nadalin, @stonematt)
-
Can JWT represent a verifiable credential with multiple subjects w3c/vc-data-model#511 (6 comments by @awoie, @msporny, @nadalin, @stonematt)
-
Change W3C TR link to vc-data-model w3c/vc-data-model#526 (6 comments by @ashimura, @burnburn, @msporny, @TallTed)
-
Schema vs @context w3c/vc-data-model#474 (5 comments by @agropper, @brentzundel, @David-Chadwick, @msporny, @stonematt)
-
JSON-LD verifiable credential with multiple subjects w3c/vc-data-model#518 (5 comments by @awoie, @David-Chadwick, @msporny)
-
5.3.1 Semantic Interoperability w3c/vc-data-model#525 (5 comments by @David-Chadwick, @msporny, @nadalin, @stonematt)
-
5.2 Trust Model w3c/vc-data-model#490 (5 comments by @brentzundel, @David-Chadwick, @nadalin, @stonematt)
-
JWS Examples and JOSE Consistency w3c/vc-data-model#470 (4 comments by @dlongley, @jricher, @msporny, @stonematt)
-
Section 4 normative and non-normative parts w3c/vc-data-model#523 (4 comments by @msporny, @nadalin, @stonematt)
-
(editorial) problem with the trust model w3c/vc-data-model#560 (4 comments by @David-Chadwick, @TallTed)
-
Decoding rules for jti and sub are mixed up w3c/vc-data-model#541 (4 comments by @awoie, @brentzundel, @stonematt)
-
Subject matters (conflicting definitions, meaningless use, ...) w3c/vc-data-model#481 (4 comments by @msporny, @RieksJ, @stonematt)
-
TITLE- Verifiable Credentials Data Model 1.0 w3c/vc-data-model#498 (4 comments by @David-Chadwick, @nadalin, @stonematt)
-
problematic phrasing in 4.2 https://w3c.github.io/vc-data-model/#identifiers w3c/vc-data-model#556 (3 comments by @msporny, @stonematt, @TallTed)
-
unclear bit of text in "JWT Encoding" section w3c/vc-data-model#552 (3 comments by @awoie, @msporny, @stonematt)
-
Terms of Use for credentials should not be at risk, but requires better purposes w3c/vc-data-model#479 (3 comments by @ken-ebert, @msporny, @RieksJ)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (2 comments by @burnburn, @msporny)
-
Holder signature in presentation does not indicate consent w3c/vc-data-model#472 (2 comments by @msporny, @stonematt)
-
Implied lack of governance Requirement in issuer/holder/verifier w3c/vc-data-model#471 (2 comments by @msporny, @stonematt)
-
Does 'subject' relate to credentials or to claims? w3c/vc-data-model#464 (2 comments by @msporny, @stonematt)
-
Not every entity can perform a role in the ecosystem. w3c/vc-data-model#463 (2 comments by @msporny, @stonematt)
-
Add "information related to the kind/type of credential" as a bullet in section 1.1 w3c/vc-data-model#462 (2 comments by @msporny, @stonematt)
-
Normative terminology (e.g. MUST) in sections marked non-normative w3c/vc-data-model#394 (2 comments by @msporny, @stonematt)
-
Is Proof mandatory in Verifiable Presentation? w3c/vc-data-model#521 (2 comments by @chaoxinhu, @msporny)
-
Add informative references to LD Proofs, LD Signatures, detached JWS, and RsaSignature2018 w3c/vc-data-model#543 (1 comment by @stonematt)
-
Consolidate all Verifiable Credential Registries to a single registry w3c/vc-data-model#530 (1 comment by @stonematt)
-
-
50 pull requests opened.
-
rephrased to address #552 w3c/vc-data-model#583, by @TallTed.
-
Update index.html w3c/vc-data-model#582, by @TallTed.
-
(editorial) clarify VC status check w3c/vc-data-model#581, by @TallTed.
-
(editorial) rephrase "ability enabling" and nearby w3c/vc-data-model#580, by @TallTed.
-
(editorial) attempt to clarify ... w3c/vc-data-model#579, by @TallTed.
-
(editorial) rephrasing for "historical" clarity w3c/vc-data-model#578, by @TallTed.
-
"final holder" may not be "final" w3c/vc-data-model#577, by @TallTed.
-
(editorial) phrasing improvements w3c/vc-data-model#576, by @TallTed.
-
Update VCDMExplainer.md w3c/vc-data-model#575, by @TallTed.
-
(editorial) U.S. English "Authorizes" w3c/vc-data-model#574, by @TallTed.
-
(editorial) minor phrasing improvement w3c/vc-data-model#573, by @TallTed.
-
(editorial) phrasing around either w3c/vc-data-model#572, by @TallTed.
-
(editorial) plurality consistency (adds an "s") w3c/vc-data-model#571, by @TallTed.
-
(editorial) deleted redundant word "when" w3c/vc-data-model#570, by @TallTed.
-
fixed error in JSON for example 23 w3c/vc-data-model#569, by @jonnycrunch.
-
(editorial) punctuation and a few words w3c/vc-data-model#568, by @TallTed.
-
(editorial) complimentary isn't complementary w3c/vc-data-model#567, by @TallTed.
-
Update index.html w3c/vc-data-model#566, by @TallTed.
-
(editorial) fix relic of another edit w3c/vc-data-model#565, by @TallTed.
-
minor rearrangements of words (issue 558) w3c/vc-data-model#564, by @brentzundel.
-
Update Appendix w3c/vc-data-model#563, by @David-Chadwick.
-
(editorial) improved Lifecycle note w3c/vc-data-model#562, by @TallTed.
-
(editorial) corrects trust model w3c/vc-data-model#561, by @TallTed.
-
minor edit w3c/vc-data-model#555, by @brentzundel.
-
minor edit w3c/vc-data-model#554, by @brentzundel.
-
(Editorial) clarify "transform the JWT specific" w3c/vc-data-model#553, by @TallTed.
-
Update conformance language w3c/vc-data-model#550, by @jricher.
-
Explain why @context provides interop w3c/vc-data-model#548, by @chaals.
-
Non-substantive refinement of Presentations section. w3c/vc-data-model#547, by @msporny.
-
Clarify why processing @context is useful for JSON-based processors. w3c/vc-data-model#546, by @msporny.
-
Update refresh service (Issue #458) w3c/vc-data-model#544, by @David-Chadwick.
-
fixed issue 541 - decoding rules for jti and sub are mixed up w3c/vc-data-model#542, by @awoie.
-
Limit refreshing of verifiable credentials to holders fixes "Refreshing questions" #458 w3c/vc-data-model#540, by @ken-ebert.
-
Clarify primacy of data model vs. syntax w3c/vc-data-model#539, by @jricher.
-
PR for Issue 488 w3c/vc-data-model#538, by @brentzundel.
-
Add clarifying text to PII section w3c/vc-data-model#536, by @brentzundel.
-
added clarifying note to @context section w3c/vc-data-model#535, by @brentzundel.
-
minor edit of text in Identifiers section. w3c/vc-data-model#534, by @brentzundel.
-
added clarifying note to credentialSchema section w3c/vc-data-model#533, by @brentzundel.
-
Address concerns raised by @jricher about syntaxes. w3c/vc-data-model#532, by @msporny.
-
Clarify that multiple proof mechanisms are supported. w3c/vc-data-model#531, by @msporny.
-
Editorial review of Accessiblity and Internationalization sections w3c/vc-data-model#529, by @grantnoble.
-
Editorial review suggestions for Security Considerations section w3c/vc-data-model#528, by @grantnoble.
-
Editorial update suggestions for Privacy Considerations section w3c/vc-data-model#527, by @grantnoble.
-
Editorial review of Syntaxes section w3c/vc-data-model#522, by @grantnoble.
-
Add note providing an example of a JWK as an issuer. w3c/vc-data-model#519, by @brentzundel.
-
Suggested editorial updates to Advanced Concepts section w3c/vc-data-model#517, by @grantnoble.
-
Editorial edit suggestions for Basic Concepts section w3c/vc-data-model#516, by @grantnoble.
-
Suggested editorial update to Core Data Model section w3c/vc-data-model#515, by @grantnoble.
-
Suggested editorial updates to Introduction and Terminology sections w3c/vc-data-model#514, by @grantnoble.
-
-
57 pull requests merged.
-
rephrased to address #552 w3c/vc-data-model#583.
-
Update index.html w3c/vc-data-model#582.
-
fixed error in JSON for example 23 w3c/vc-data-model#569.
-
(editorial) clarify VC status check w3c/vc-data-model#581.
-
(editorial) rephrase "ability enabling" and nearby w3c/vc-data-model#580.
-
(editorial) attempt to clarify ... w3c/vc-data-model#579.
-
(editorial) rephrasing for "historical" clarity w3c/vc-data-model#578.
-
(editorial) phrasing improvements w3c/vc-data-model#576.
-
Update VCDMExplainer.md w3c/vc-data-model#575.
-
(editorial) U.S. English "Authorizes" w3c/vc-data-model#574.
-
(editorial) minor phrasing improvement w3c/vc-data-model#573.
-
(editorial) phrasing around either w3c/vc-data-model#572.
-
(editorial) plurality consistency (adds an "s") w3c/vc-data-model#571.
-
(editorial) deleted redundant word "when" w3c/vc-data-model#570.
-
Update conformance language w3c/vc-data-model#550.
-
Non-substantive refinement of Presentations section. w3c/vc-data-model#547.
-
Clarify why processing @context is useful for JSON-based processors. w3c/vc-data-model#546.
-
(editorial) corrects trust model w3c/vc-data-model#561.
-
(editorial) punctuation and a few words w3c/vc-data-model#568.
-
(editorial) complimentary isn't complementary w3c/vc-data-model#567.
-
Update index.html w3c/vc-data-model#566.
-
(editorial) fix relic of another edit w3c/vc-data-model#565.
-
minor rearrangements of words (issue 558) w3c/vc-data-model#564.
-
Update Appendix w3c/vc-data-model#563.
-
(editorial) improved Lifecycle note w3c/vc-data-model#562.
-
(Editorial) clarify "transform the JWT specific" w3c/vc-data-model#553.
-
minor edit w3c/vc-data-model#555.
-
Clarify primacy of data model vs. syntax w3c/vc-data-model#539.
-
fixed issue 541 - decoding rules for jti and sub are mixed up w3c/vc-data-model#542.
-
Editorial update suggestions for Privacy Considerations section w3c/vc-data-model#527.
-
Suggested editorial updates to Advanced Concepts section w3c/vc-data-model#517.
-
Editorial edit suggestions for Basic Concepts section w3c/vc-data-model#516.
-
Suggested editorial update to Core Data Model section w3c/vc-data-model#515.
-
Suggested editorial updates to Introduction and Terminology sections w3c/vc-data-model#514.
-
Editorial review of Accessiblity and Internationalization sections w3c/vc-data-model#529.
-
Editorial review suggestions for Security Considerations section w3c/vc-data-model#528.
-
Update refresh service (Issue #458) w3c/vc-data-model#544.
-
added clarifying note to credentialSchema section w3c/vc-data-model#533.
-
minor edit of text in Identifiers section. w3c/vc-data-model#534.
-
PR for Issue 488 w3c/vc-data-model#538.
-
Clarify that multiple proof mechanisms are supported. w3c/vc-data-model#531.
-
unification of ecosystem overview and terminology w3c/vc-data-model#508.
-
added clarifying note to @context section w3c/vc-data-model#535.
-
Add clarifying text to PII section w3c/vc-data-model#536.
-
Editorial review of Syntaxes section w3c/vc-data-model#522.
-
Add note providing an example of a JWK as an issuer. w3c/vc-data-model#519.
-
Fixing "the subject of the credential" (issue #464) w3c/vc-data-model#512.
-
added clarifying language to private browsing section w3c/vc-data-model#510.
-
add note to 3.2 for issue 481 w3c/vc-data-model#509.
-
Added clarifying language to requirement w3c/vc-data-model#507.
-
Update entity definition (Issue #463) w3c/vc-data-model#504.
-
Information related to a credential (Fix for #462) w3c/vc-data-model#503.
-
Remove must/should from informative text w3c/vc-data-model#499.
-
Update Token Binding Reference w3c/vc-data-model#497.
-
Editorial fix to definitions w3c/vc-data-model#477.
-
Remove faulty assertion regarding consent w3c/vc-data-model#476.
-
Misplaced normative text, and other editorial issues w3c/vc-data-model#475.
-
-
5 pull requests closed.
-
Explain why @context provides interop w3c/vc-data-model#548.
-
minor edit w3c/vc-data-model#554.
-
Limit refreshing of verifiable credentials to holders fixes "Refreshing questions" #458 w3c/vc-data-model#540.
-
Clarification to Refresh Service to address #458 w3c/vc-data-model#501.
-
Address concerns raised by @jricher about syntaxes. w3c/vc-data-model#532.
-
-
37 pull requests received 356 new comments.
-
Suggested editorial updates to Advanced Concepts section w3c/vc-data-model#517 (52 comments by @David-Chadwick, @grantnoble, @ken-ebert, @msporny)
-
Editorial update suggestions for Privacy Considerations section w3c/vc-data-model#527 (44 comments by @grantnoble, @msporny)
-
Clarify primacy of data model vs. syntax w3c/vc-data-model#539 (31 comments by @awoie, @dlongley, @jricher, @msporny, @stonematt, @TallTed)
-
Editorial edit suggestions for Basic Concepts section w3c/vc-data-model#516 (31 comments by @grantnoble, @ken-ebert, @msporny)
-
Clarify that multiple proof mechanisms are supported. w3c/vc-data-model#531 (18 comments by @chaals, @jricher, @msporny, @nadalin)
-
Explain why @context provides interop w3c/vc-data-model#548 (15 comments by @David-Chadwick, @msporny)
-
"final holder" may not be "final" w3c/vc-data-model#577 (14 comments by @David-Chadwick, @msporny, @TallTed)
-
Non-substantive refinement of Presentations section. w3c/vc-data-model#547 (14 comments by @brentzundel, @dlongley, @msporny, @TallTed)
-
Address concerns raised by @jricher about syntaxes. w3c/vc-data-model#532 (12 comments by @dlongley, @jricher, @msporny)
-
added clarifying note to @context section w3c/vc-data-model#535 (11 comments by @brentzundel, @David-Chadwick, @dlongley, @jricher, @msporny)
-
Limit refreshing of verifiable credentials to holders fixes "Refreshing questions" #458 w3c/vc-data-model#540 (10 comments by @agropper, @brentzundel, @David-Chadwick, @dlongley, @msporny, @TallTed)
-
minor edit of text in Identifiers section. w3c/vc-data-model#534 (10 comments by @brentzundel, @David-Chadwick, @dlongley, @ken-ebert, @msporny, @TallTed)
-
Clarify why processing @context is useful for JSON-based processors. w3c/vc-data-model#546 (9 comments by @burnburn, @David-Chadwick, @dlongley, @msporny)
-
Update conformance language w3c/vc-data-model#550 (9 comments by @brentzundel, @dontcallmedom, @jricher, @msporny)
-
Update refresh service (Issue #458) w3c/vc-data-model#544 (9 comments by @David-Chadwick, @dlongley, @ken-ebert, @msporny)
-
Suggested editorial update to Core Data Model section w3c/vc-data-model#515 (8 comments by @grantnoble, @msporny)
-
Editorial review suggestions for Security Considerations section w3c/vc-data-model#528 (8 comments by @grantnoble, @msporny)
-
Suggested editorial updates to Introduction and Terminology sections w3c/vc-data-model#514 (7 comments by @David-Chadwick, @grantnoble, @msporny)
-
added clarifying note to credentialSchema section w3c/vc-data-model#533 (7 comments by @brentzundel, @David-Chadwick, @dlongley, @msporny)
-
Clarification to Refresh Service to address #458 w3c/vc-data-model#501 (6 comments by @brentzundel, @David-Chadwick, @msporny, @TallTed)
-
fixed error in JSON for example 23 w3c/vc-data-model#569 (3 comments by @davidlehn, @dontcallmedom, @msporny)
-
Editorial review of Accessiblity and Internationalization sections w3c/vc-data-model#529 (2 comments by @grantnoble, @msporny)
-
unification of ecosystem overview and terminology w3c/vc-data-model#508 (2 comments by @brentzundel, @ken-ebert)
-
fixed issue 541 - decoding rules for jti and sub are mixed up w3c/vc-data-model#542 (1 comment by @msporny)
-
added clarifying language to private browsing section w3c/vc-data-model#510 (1 comment by @stonematt)
-
w3c/vc-test-suite
-
1 issue opened.
-
An example to follow would be really nice w3c/vc-test-suite#14, by @brentzundel.
-
-
1 issue closed.
-
how to deference example context w3c/vc-test-suite#8.
-
-
3 issues received 9 new comments.
-
An example to follow would be really nice w3c/vc-test-suite#14 (5 comments by @brentzundel, @dmitrizagidulin)
-
Wrong content type and CORS headers not set w3c/vc-test-suite#9 (2 comments by @dlongley, @dmitrizagidulin)
-
-
5 pull requests opened.
-
Add implementation report for vc-js lib. w3c/vc-test-suite#16, by @dmitrizagidulin.
-
Add additional tests required by CR 1. w3c/vc-test-suite#15, by @dmitrizagidulin.
-
Update README.md w3c/vc-test-suite#13, by @TallTed.
-
Fix issuanceDate in example 5 to valid format. w3c/vc-test-suite#12, by @dmitrizagidulin.
-
Update example context url. w3c/vc-test-suite#11, by @dmitrizagidulin.
-
-
3 pull requests merged.
-
Fix issuanceDate in example 5 to valid format. w3c/vc-test-suite#12.
-
Update example context url. w3c/vc-test-suite#11.
-
update context to match spec definition w3c/vc-test-suite#10.
-
-
2 pull requests received 2 new comments.
w3c/vc-imp-guide
-
2 issues opened.
-
Use of aliases and extending VCs w3c/vc-imp-guide#10, by @David-Chadwick.
-
@context value ordering w3c/vc-imp-guide#9, by @David-Chadwick.
-
-
5 issues received 6 new comments.
-
Add guidance to prevent unauthorized credential reuse by verifiers w3c/vc-imp-guide#2 (2 comments by @brentzundel, @dlongley)
-
Add sections outlining benefits of different syntax + proof formats w3c/vc-imp-guide#8 (1 comment by @BigBlueHat)
-
Reference or attach generic (not-credential) data in credential w3c/vc-imp-guide#5 (1 comment by @burnburn)
-
-
2 pull requests opened.
-
Added section on benefits of ZKP proofs w3c/vc-imp-guide#12, by @ken-ebert.
-
Update README.md w3c/vc-imp-guide#11, by @TallTed.
-
-
1 pull request received 2 new comments.
w3c/vc-use-cases
-
1 issue closed.
-
Convert Sequences to Essential Narratives w3c/vc-use-cases#33.
-
-
6 issues received 8 new comments.
-
w3c/vc-use-cases#33 (1 comment by @jandrieu)
-
w3c/vc-use-cases#35 (1 comment by @jandrieu)
-
w3c/vc-use-cases#30 (1 comment by @joshueoconnor)
-
1 pull request opened.
-
Update README.md w3c/vc-use-cases#93, by @TallTed.
-
TR publications
-
1 document published.
-
Verifiable Credentials Data Model 1.0 published as a Candidate Recommendation Snapshot. History of Verifiable Credentials Data Model 1.0
-
Participants
-
1 organization joined.
-
Thomson Reuters Corp. joined.
-
GitHub
w3c/vc-data-model
-
51 issues opened.
-
Normative Reference w3c/vc-data-model#513, by @nadalin.
-
Can JWT represent a verifiable credential with multiple subjects w3c/vc-data-model#511, by @David-Chadwick.
-
4.9 Status w3c/vc-data-model#500, by @nadalin.
-
TITLE- Verifiable Credentials Data Model 1.0 w3c/vc-data-model#498, by @nadalin.
-
4.8 Expiration w3c/vc-data-model#496, by @nadalin.
-
8.4 Token Binding w3c/vc-data-model#495, by @nadalin.
-
8.2 Content Integrity Protection w3c/vc-data-model#494, by @nadalin.
-
8. Security Considerations w3c/vc-data-model#493, by @nadalin.
-
7.17 In-Private w3c/vc-data-model#492, by @nadalin.
-
5.3.1 Semantic Interoperability w3c/vc-data-model#491, by @nadalin.
-
5.2 Trust Model w3c/vc-data-model#490, by @nadalin.
-
4.7 Proofs w3c/vc-data-model#489, by @nadalin.
-
4.10 Presentations w3c/vc-data-model#488, by @nadalin.
-
4.7 Proofs w3c/vc-data-model#487, by @nadalin.
-
4.7 Proofs w3c/vc-data-model#486, by @nadalin.
-
4.5 Issuer w3c/vc-data-model#485, by @nadalin.
-
Section 4.1 Context w3c/vc-data-model#483, by @nadalin.
-
Introduction is misleading w3c/vc-data-model#482, by @nadalin.
-
Subject matters (conflicting definitions, meaningless use, ...) w3c/vc-data-model#481, by @RieksJ.
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480, by @RieksJ.
-
Terms of Use for credentials should not be at risk, but requires better purposes w3c/vc-data-model#479, by @RieksJ.
-
protocol statement in id section w3c/vc-data-model#478, by @brentzundel.
-
Schema vs @context w3c/vc-data-model#474, by @David-Chadwick.
-
Need clarity on ID URIs and what dereferencing does w3c/vc-data-model#473, by @mavarley.
-
Holder signature in presentation does not indicate consent w3c/vc-data-model#472, by @mavarley.
-
Implied lack of governance Requirement in issuer/holder/verifier w3c/vc-data-model#471, by @mavarley.
-
JWS Examples and JOSE Consistency w3c/vc-data-model#470, by @jricher.
-
Anybody knows about the details of vc? w3c/vc-data-model#468, by @DianeFeng.
-
Do we need 'actor' - 'agent' - 'party'? w3c/vc-data-model#467, by @RieksJ.
-
Faulty description of the issuer role w3c/vc-data-model#466, by @RieksJ.
-
Definition of 'credential w3c/vc-data-model#465, by @RieksJ.
-
Does 'subject' relate to credentials or to claims? w3c/vc-data-model#464, by @RieksJ.
-
Not every entity can perform a role in the ecosystem. w3c/vc-data-model#463, by @RieksJ.
-
Add "information related to the kind/type of credential" as a bullet in section 1.1 w3c/vc-data-model#462, by @RieksJ.
-
Editorial issue: 5.5 Refreshing: missing space w3c/vc-data-model#459, by @ken-ebert.
-
Refreshing questions w3c/vc-data-model#458, by @ken-ebert.
-
Editorial: the holder posses w3c/vc-data-model#457, by @ken-ebert.
-
Revocation should not reveal to the issuer any identifying information? w3c/vc-data-model#456, by @ken-ebert.
-
Extra ">" character in CR draft. w3c/vc-data-model#455, by @ken-ebert.
-
Please provide citation to 0xcert w3c/vc-data-model#450, by @fulldecent.
-
Is Proof mandatory or optional? w3c/vc-data-model#447, by @David-Chadwick.
-
Verification section contains normative statements for verifiers w3c/vc-data-model#446, by @msporny.
-
RESOLUTION: Make the expression of the @context property mandatory in the data model w3c/vc-data-model#444, by @stonematt.
-
Either proof or JWT MUST be provided. w3c/vc-data-model#441, by @msporny.
-
Conformance clauses are missing, wrong or inconsistent w3c/vc-data-model#440, by @David-Chadwick.
-
The table of format comparisons should be replaced by a section for each proposed format w3c/vc-data-model#439, by @brentzundel.
-
VC is verifiable without proof property in case of JWT w3c/vc-data-model#438, by @awoie.
-
Reference to ISO8601 should be more specific w3c/vc-data-model#437, by @aphillips.
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436, by @aphillips.
-
-
41 issues closed.
-
Definition of 'credential w3c/vc-data-model#465.
-
Please provide citation to 0xcert w3c/vc-data-model#450.
-
Image Descriptions requested by Accessibility Group w3c/vc-data-model#225.
-
Vocabulary location decisions w3c/vc-data-model#391.
-
Context URL is down .. and yet another question about override w3c/vc-data-model#427.
-
Need clarity on ID URIs and what dereferencing does w3c/vc-data-model#473.
-
Revocation should not reveal to the issuer any identifying information? w3c/vc-data-model#456.
-
Anybody knows about the details of vc? w3c/vc-data-model#468.
-
Do we need 'actor' - 'agent' - 'party'? w3c/vc-data-model#467.
-
Editorial issue: 5.5 Refreshing: missing space w3c/vc-data-model#459.
-
Editorial: the holder posses w3c/vc-data-model#457.
-
Extra ">" character in CR draft. w3c/vc-data-model#455.
-
anonymous presentation - missing in the standard w3c/vc-data-model#435.
-
ZKP section needs corrections w3c/vc-data-model#414.
-
Is Proof mandatory or optional? w3c/vc-data-model#447.
-
Sorting out @contexts w3c/vc-data-model#429.
-
`cred:RefreshService` definition missing from vocab w3c/vc-data-model#422.
-
Verification w3c/vc-data-model#408.
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136.
-
The table of format comparisons should be replaced by a section for each proposed format w3c/vc-data-model#439.
-
RESOLUTION: Make the expression of the @context property mandatory in the data model w3c/vc-data-model#444.
-
Conformance clauses are missing, wrong or inconsistent w3c/vc-data-model#440.
-
Evidence ID w3c/vc-data-model#432.
-
Non-agreed change in conformance language w3c/vc-data-model#413.
-
Verification section contains normative statements for verifiers w3c/vc-data-model#446.
-
Removing HolderID from Presentations w3c/vc-data-model#419.
-
Reference to ISO8601 should be more specific w3c/vc-data-model#437.
-
Issues from CCG review w3c/vc-data-model#383.
-
Section 7.3 Mandatory Types w3c/vc-data-model#428.
-
Multiple proofs w3c/vc-data-model#430.
-
Editorial in Appendix A.5 w3c/vc-data-model#433.
-
VC is verifiable without proof property in case of JWT w3c/vc-data-model#438.
-
Either proof or JWT MUST be provided. w3c/vc-data-model#441.
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203.
-
Reference or attach credential in another credentials w3c/vc-data-model#135.
-
Level of Assurance vs. Evidence w3c/vc-data-model#405.
-
Default namespace URL w3c/vc-data-model#206.
-
Determine how/if WebAuthn will work with VCs w3c/vc-data-model#162.
-
Add canonical way to reference JSON Schema against which credential should be validated w3c/vc-data-model#129.
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93.
-
-
3 issues reopened.
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436, by @r12a.
-
Normative terminology (e.g. MUST) in sections marked non-normative w3c/vc-data-model#394, by @rhiaro.
-
Reference to ISO8601 should be more specific w3c/vc-data-model#437, by @msporny.
-
-
73 issues received 286 new comments.
-
Section 4.1 Context w3c/vc-data-model#483 (17 comments by @brentzundel, @chaals, @David-Chadwick, @dmitrizagidulin, @nadalin)
-
Not every entity can perform a role in the ecosystem. w3c/vc-data-model#463 (14 comments by @chaals, @David-Chadwick, @jandrieu, @RieksJ, @talltree)
-
Define one or more media types for VCs w3c/vc-data-model#421 (13 comments by @BigBlueHat, @brentzundel, @dmitrizagidulin, @jonnycrunch, @pmcb55, @TallTed)
-
5.3.1 Semantic Interoperability w3c/vc-data-model#491 (11 comments by @brentzundel, @chaals, @David-Chadwick, @dmitrizagidulin, @jandrieu, @nadalin)
-
Normative terminology (e.g. MUST) in sections marked non-normative w3c/vc-data-model#394 (10 comments by @brentzundel, @burnburn, @ken-ebert, @msporny, @rhiaro)
-
Please provide citation to 0xcert w3c/vc-data-model#450 (8 comments by @brentzundel, @burnburn, @fulldecent, @xpepermint)
-
Coordinate with PING during review process w3c/vc-data-model#222 (8 comments by @brentzundel, @stonematt)
-
Context URL is down .. and yet another question about override w3c/vc-data-model#427 (8 comments by @ashimura, @brentzundel, @burnburn, @chaoxinhu, @msporny, @stonematt)
-
Many natural language text fields (such as "statusReason") have no language or direction support w3c/vc-data-model#436 (8 comments by @aphillips, @brentzundel, @burnburn, @chaals, @msporny)
-
Can JWT represent a verifiable credential with multiple subjects w3c/vc-data-model#511 (6 comments by @brentzundel, @David-Chadwick, @nadalin)
-
Implied lack of governance Requirement in issuer/holder/verifier w3c/vc-data-model#471 (6 comments by @brentzundel, @jandrieu, @mavarley)
-
Faulty description of the issuer role w3c/vc-data-model#466 (6 comments by @chaals, @David-Chadwick, @RieksJ, @stonematt)
-
RESOLUTION: Make the expression of the @context property mandatory in the data model w3c/vc-data-model#444 (6 comments by @brentzundel, @burnburn, @David-Chadwick, @jonnycrunch, @msporny)
-
Non-agreed change in conformance language w3c/vc-data-model#413 (6 comments by @brentzundel, @burnburn, @msporny, @stonematt)
-
Does 'subject' relate to credentials or to claims? w3c/vc-data-model#464 (5 comments by @brentzundel, @David-Chadwick, @RieksJ)
-
Vocabulary location decisions w3c/vc-data-model#391 (5 comments by @brentzundel, @burnburn, @msporny)
-
Revocation should not reveal to the issuer any identifying information? w3c/vc-data-model#456 (5 comments by @ken-ebert, @stonematt)
-
Reference to ISO8601 should be more specific w3c/vc-data-model#437 (5 comments by @aphillips, @brentzundel, @msporny)
-
8.2 Content Integrity Protection w3c/vc-data-model#494 (4 comments by @brentzundel, @dmitrizagidulin, @nadalin)
-
Decide if there should be an EOL date on the spec? w3c/vc-data-model#253 (4 comments by @brentzundel, @burnburn, @chaals, @ChristopherA)
-
anonymous presentation - missing in the standard w3c/vc-data-model#435 (4 comments by @brentzundel, @burnburn, @glauserr)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (4 comments by @brentzundel, @burnburn)
-
Default namespace URL w3c/vc-data-model#206 (4 comments by @brentzundel, @dmitrizagidulin, @jonnycrunch)
-
TITLE- Verifiable Credentials Data Model 1.0 w3c/vc-data-model#498 (3 comments by @brentzundel, @nadalin)
-
Add "information related to the kind/type of credential" as a bullet in section 1.1 w3c/vc-data-model#462 (3 comments by @burnburn, @chaals, @David-Chadwick)
-
Holder signature in presentation does not indicate consent w3c/vc-data-model#472 (3 comments by @burnburn, @mavarley, @stonematt)
-
Do we need 'actor' - 'agent' - 'party'? w3c/vc-data-model#467 (3 comments by @burnburn, @chaals, @jandrieu)
-
Conformance clauses are missing, wrong or inconsistent w3c/vc-data-model#440 (3 comments by @brentzundel, @jonnycrunch, @msporny)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (3 comments by @brentzundel, @stonematt)
-
protocol statement in id section w3c/vc-data-model#478 (2 comments by @brentzundel, @David-Chadwick)
-
Image Descriptions requested by Accessibility Group w3c/vc-data-model#225 (2 comments by @brentzundel, @burnburn)
-
`cred:RefreshService` definition missing from vocab w3c/vc-data-model#422 (2 comments by @brentzundel, @msporny)
-
Determine how/if WebAuthn will work with VCs w3c/vc-data-model#162 (2 comments by @brentzundel, @burnburn)
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203 (2 comments by @brentzundel, @dmitrizagidulin)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials. w3c/vc-data-model#128 (2 comments by @dmitrizagidulin)
-
Subject matters (conflicting definitions, meaningless use, ...) w3c/vc-data-model#481 (1 comment by @brentzundel)
-
Avoiding confusion by renaming 'credentialSubject' w3c/vc-data-model#480 (1 comment by @brentzundel)
-
The table of format comparisons should be replaced by a section for each proposed format w3c/vc-data-model#439 (1 comment by @msporny)
-
w3c/vc-data-model#42 (1 comment by @dlongley)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @brentzundel)
-
Add canonical way to reference JSON Schema against which credential should be validated w3c/vc-data-model#129 (1 comment by @brentzundel)
-
-
27 pull requests opened.
-
Fixing "the subject of the credential" (issue #464) w3c/vc-data-model#512, by @David-Chadwick.
-
added clarifying language to private browsing section w3c/vc-data-model#510, by @brentzundel.
-
add note to 3.2 for issue 481 w3c/vc-data-model#509, by @brentzundel.
-
unification of ecosystem overview and terminology w3c/vc-data-model#508, by @brentzundel.
-
Added clarifying language to requirement w3c/vc-data-model#507, by @brentzundel.
-
updated link to token binding rfc w3c/vc-data-model#506, by @brentzundel.
-
addressed use of 'must' in security considerations section w3c/vc-data-model#505, by @brentzundel.
-
Update entity definition (Issue #463) w3c/vc-data-model#504, by @David-Chadwick.
-
Information related to a credential (Fix for #462) w3c/vc-data-model#503, by @David-Chadwick.
-
Clarification to Refresh Service to address #458 w3c/vc-data-model#501, by @David-Chadwick.
-
Remove must/should from informative text w3c/vc-data-model#499, by @chaals.
-
Update Token Binding Reference w3c/vc-data-model#497, by @chaals.
-
Editorial fix to definitions w3c/vc-data-model#477, by @stonematt.
-
Remove faulty assertion regarding consent w3c/vc-data-model#476, by @stonematt.
-
Misplaced normative text, and other editorial issues w3c/vc-data-model#475, by @rhiaro.
-
Exemplify language tagging w3c/vc-data-model#469, by @chaals.
-
fix revocation by issuer #456 w3c/vc-data-model#461, by @ken-ebert.
-
Zkp section addition w3c/vc-data-model#460, by @brentzundel.
-
tweak i18n considerations w3c/vc-data-model#454, by @chaals.
-
Zkp section changes w3c/vc-data-model#453, by @brentzundel.
-
Removed or refactored some of the issues mentioned in the data model w3c/vc-data-model#452, by @brentzundel.
-
Add security contexts. w3c/vc-data-model#451, by @dlongley.
-
removed protocol-specific conformance statements w3c/vc-data-model#449, by @brentzundel.
-
addressed private browsing scenario w3c/vc-data-model#448, by @brentzundel.
-
Verification section updates... w3c/vc-data-model#445, by @grantnoble.
-
Conformance language changes/additions. w3c/vc-data-model#443, by @msporny.
-
Fixed conformance statements w3c/vc-data-model#442, by @brentzundel.
-
-
13 pull requests merged.
-
Exemplify language tagging w3c/vc-data-model#469.
-
fix revocation by issuer #456 w3c/vc-data-model#461.
-
Zkp section addition w3c/vc-data-model#460.
-
tweak i18n considerations w3c/vc-data-model#454.
-
Zkp section changes w3c/vc-data-model#453.
-
Removed or refactored some of the issues mentioned in the data model w3c/vc-data-model#452.
-
Add security contexts. w3c/vc-data-model#451.
-
addressed private browsing scenario w3c/vc-data-model#448.
-
Verification section updates... w3c/vc-data-model#445.
-
Conformance language changes/additions. w3c/vc-data-model#443.
-
removed protocol-specific conformance statements w3c/vc-data-model#449.
-
Zkp section corrections #1 w3c/vc-data-model#434.
-
Linking, unordered list, capitalization and line length edits w3c/vc-data-model#431.
-
-
5 pull requests closed.
-
updated link to token binding rfc w3c/vc-data-model#506.
-
addressed use of 'must' in security considerations section w3c/vc-data-model#505.
-
Add section on Syntax and Proof Format Trade-Offs. w3c/vc-data-model#384.
-
Use IPLD as a JSON syntax for claim w3c/vc-data-model#261.
-
Fixed conformance statements w3c/vc-data-model#442.
-
-
1 pull request reopened.
-
Use IPLD as a JSON syntax for claim w3c/vc-data-model#261, by @jonnycrunch.
-
-
21 pull requests received 113 new comments.
-
Conformance language changes/additions. w3c/vc-data-model#443 (35 comments by @brentzundel, @burnburn, @David-Chadwick, @msporny)
-
Fixed conformance statements w3c/vc-data-model#442 (21 comments by @brentzundel, @David-Chadwick, @msporny)
-
Zkp section addition w3c/vc-data-model#460 (6 comments by @brentzundel, @chaals, @davidlehn, @Fak3, @ken-ebert)
-
fix revocation by issuer #456 w3c/vc-data-model#461 (4 comments by @David-Chadwick, @Fak3, @jandrieu, @ken-ebert)
-
removed protocol-specific conformance statements w3c/vc-data-model#449 (4 comments by @brentzundel, @burnburn, @msporny)
-
Verification section updates... w3c/vc-data-model#445 (4 comments by @brentzundel, @David-Chadwick, @grantnoble)
-
Use IPLD as a JSON syntax for claim w3c/vc-data-model#261 (4 comments by @burnburn, @joeltg, @jonnycrunch)
-
Fixing "the subject of the credential" (issue #464) w3c/vc-data-model#512 (3 comments by @brentzundel, @David-Chadwick)
-
Add section on Syntax and Proof Format Trade-Offs. w3c/vc-data-model#384 (3 comments by @jonnycrunch, @msporny, @stonematt)
-
Zkp section corrections #1 w3c/vc-data-model#434 (3 comments by @brentzundel, @burnburn, @ken-ebert)
-
Clarification to Refresh Service to address #458 w3c/vc-data-model#501 (2 comments by @David-Chadwick, @ken-ebert)
-
unification of ecosystem overview and terminology w3c/vc-data-model#508 (2 comments by @brentzundel, @David-Chadwick)
-
addressed use of 'must' in security considerations section w3c/vc-data-model#505 (1 comment by @brentzundel)
-
w3c/vc-test-suite
-
2 issues opened.
-
Wrong content type and CORS headers not set w3c/vc-test-suite#9, by @yancyribbens.
-
how to deference example context w3c/vc-test-suite#8, by @yancyribbens.
-
-
2 issues received 4 new comments.
-
Wrong content type and CORS headers not set w3c/vc-test-suite#9 (3 comments by @davidlehn, @yancyribbens)
-
-
1 pull request opened.
-
update context to match spec definition w3c/vc-test-suite#10, by @yancyribbens.
-
-
1 pull request received 1 new comment.
w3c/vc-imp-guide
-
7 issues opened.
-
Add sections outlining benefits of different syntax + proof formats w3c/vc-imp-guide#8, by @msporny.
-
Suggestions on how to do progressive trust or graceful degredation w3c/vc-imp-guide#6, by @stonematt.
-
Reference or attach generic (not-credential) data in credential w3c/vc-imp-guide#5, by @stonematt.
-
Reference or attach credential in another credentials w3c/vc-imp-guide#4, by @burnburn.
-
Determine how/if WebAuthn will work with VCs w3c/vc-imp-guide#3, by @stonematt.
-
Add guidance to prevent unauthorized credential reuse by verifiers w3c/vc-imp-guide#2, by @dmitrizagidulin.
-
-
1 pull request opened.
-
Added sections on identifiers and proofs w3c/vc-imp-guide#7, by @deiu.
-
TR publications
-
1 document published.
-
Verifiable Credentials Data Model 1.0 published as a Working Draft. History of Verifiable Credentials Data Model 1.0
-
GitHub
w3c/vc-data-model
-
12 issues opened.
-
anonymous presentation - missing in the standard w3c/vc-data-model#435, by @glauserr.
-
Editorial in Appendix A.5 w3c/vc-data-model#433, by @David-Chadwick.
-
Evidence ID w3c/vc-data-model#432, by @David-Chadwick.
-
Multiple proofs w3c/vc-data-model#430, by @David-Chadwick.
-
Sorting out @contexts w3c/vc-data-model#429, by @David-Chadwick.
-
Section 7.3 Mandatory Types w3c/vc-data-model#428, by @David-Chadwick.
-
Context URL is down .. and yet another question about override w3c/vc-data-model#427, by @chaoxinhu.
-
`cred:RefreshService` definition missing from vocab w3c/vc-data-model#422, by @dlongley.
-
Define one or more media types for VCs w3c/vc-data-model#421, by @dhh1128.
-
Removing HolderID from Presentations w3c/vc-data-model#419, by @David-Chadwick.
-
ZKP section needs corrections w3c/vc-data-model#414, by @brentzundel.
-
Non-agreed change in conformance language w3c/vc-data-model#413, by @burnburn.
-
-
14 issues closed.
-
Authorisation w3c/vc-data-model#406.
-
Minor typo w3c/vc-data-model#243.
-
ZKP-Examples have different id values in credentialSchema w3c/vc-data-model#364.
-
[Identifiers] Clarify/be more explicit about where DIDs can be (optionally) used w3c/vc-data-model#362.
-
"Verifiable Credential" which only contains limited uses w3c/vc-data-model#312.
-
Deontic concepts supported by termsOfUse w3c/vc-data-model#276.
-
Is a VC a tree or a graph? w3c/vc-data-model#260.
-
Privacy issues w3c/vc-data-model#244.
-
Inconsistency in description of identifier registry w3c/vc-data-model#239.
-
Comments on Section 6.2 Terms of Use w3c/vc-data-model#234.
-
Validate requirements text matches test suite and current thinking w3c/vc-data-model#270.
-
Defining expected order of credential `type` values w3c/vc-data-model#371.
-
Review from Credentials Community Group w3c/vc-data-model#360.
-
Suggest changing `refreshService`'s `serviceEndpoint` to `id` to match other objects w3c/vc-data-model#380.
-
-
22 issues received 58 new comments.
-
Removing HolderID from Presentations w3c/vc-data-model#419 (20 comments by @brentzundel, @David-Chadwick, @dlongley, @jandrieu)
-
Define one or more media types for VCs w3c/vc-data-model#421 (8 comments by @brentzundel, @David-Chadwick, @msporny, @stonematt, @TallTed)
-
Defining expected order of credential `type` values w3c/vc-data-model#371 (2 comments by @BigBlueHat, @msporny)
-
ZKP-Examples have different id values in credentialSchema w3c/vc-data-model#364 (1 comment by @msporny)
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363 (1 comment by @msporny)
-
[Identifiers] Clarify/be more explicit about where DIDs can be (optionally) used w3c/vc-data-model#362 (1 comment by @msporny)
-
"Verifiable Credential" which only contains limited uses w3c/vc-data-model#312 (1 comment by @msporny)
-
Validate requirements text matches test suite and current thinking w3c/vc-data-model#270 (1 comment by @msporny)
-
-
13 pull requests opened.
-
Zkp section corrections #1 w3c/vc-data-model#434, by @brentzundel.
-
Linking, unordered list, capitalization and line length edits w3c/vc-data-model#431, by @grantnoble.
-
Terminology review suggestions w3c/vc-data-model#426, by @grantnoble.
-
More linking, grammar, and line length suggestions w3c/vc-data-model#425, by @grantnoble.
-
Linking, grammar, punctuation, and line length suggestions w3c/vc-data-model#424, by @grantnoble.
-
Clarified proof section w3c/vc-data-model#423, by @brentzundel.
-
Lifecycle Additions w3c/vc-data-model#420, by @gannan08.
-
Update Evidence language w3c/vc-data-model#418, by @stonematt.
-
Update authorization language w3c/vc-data-model#417, by @stonematt.
-
Update revocation to reference credentialStatus w3c/vc-data-model#416, by @stonematt.
-
Update non-normative requirements w3c/vc-data-model#415, by @stonematt.
-
Convert "SubjectOnly" property to termsOfUse use case. w3c/vc-data-model#412, by @msporny.
-
change namespace URI to www.w3.org-based w3c/vc-data-model#411, by @ashimura.
-
-
14 pull requests merged.
-
Linking, grammar, punctuation, and line length suggestions w3c/vc-data-model#424.
-
Terminology review suggestions w3c/vc-data-model#426.
-
More linking, grammar, and line length suggestions w3c/vc-data-model#425.
-
Clarified proof section w3c/vc-data-model#423.
-
Lifecycle Additions w3c/vc-data-model#420.
-
Update non-normative requirements w3c/vc-data-model#415.
-
Update Evidence language w3c/vc-data-model#418.
-
Update authorization language w3c/vc-data-model#417.
-
Update revocation to reference credentialStatus w3c/vc-data-model#416.
-
Explainer editorial pass w3c/vc-data-model#410.
-
Editorials w3c/vc-data-model#409.
-
Remove serviceEndpoint property, towards #391, fixes #380 w3c/vc-data-model#399.
-
Clean up conformance section w3c/vc-data-model#397.
-
change namespace URI to www.w3.org-based w3c/vc-data-model#411.
-
-
2 pull requests closed.
-
Convert "SubjectOnly" property to termsOfUse use case. w3c/vc-data-model#412.
-
Add lifecycle for an example of data flowing through beginning to end. w3c/vc-data-model#313.
-
-
11 pull requests received 203 new comments.
-
Add section on Syntax and Proof Format Trade-Offs. w3c/vc-data-model#384 (68 comments by @awoie, @brentzundel, @David-Chadwick, @dlongley, @msporny, @OR13, @pelle, @rxgrant)
-
Update non-normative requirements w3c/vc-data-model#415 (36 comments by @brentzundel, @msporny, @stonematt)
-
Convert "SubjectOnly" property to termsOfUse use case. w3c/vc-data-model#412 (29 comments by @brentzundel, @David-Chadwick, @dlongley, @ken-ebert, @msporny)
-
Update Evidence language w3c/vc-data-model#418 (16 comments by @brentzundel, @David-Chadwick, @jandrieu, @msporny, @stonematt)
-
Update revocation to reference credentialStatus w3c/vc-data-model#416 (16 comments by @brentzundel, @David-Chadwick, @msporny, @stonematt)
-
Update authorization language w3c/vc-data-model#417 (11 comments by @brentzundel, @David-Chadwick, @dlongley, @jandrieu, @msporny, @stonematt)
-
Add lifecycle for an example of data flowing through beginning to end. w3c/vc-data-model#313 (3 comments by @David-Chadwick, @gannan08, @msporny)
-
Linking, grammar, punctuation, and line length suggestions w3c/vc-data-model#424 (2 comments by @grantnoble, @msporny)
-
w3c/vc-test-suite
-
1 pull request opened.
-
Continue implementation w3c/vc-test-suite#7, by @dmitrizagidulin.
-
-
1 pull request merged.
-
Continue implementation w3c/vc-test-suite#7.
-
-
1 pull request received 7 new comments.
-
Continue implementation w3c/vc-test-suite#7 (7 comments by @BigBlueHat, @davidlehn, @dmitrizagidulin)
-
w3c/vc-use-cases
-
1 issue opened.
-
Amend task can be assigned to holder w3c/vc-use-cases#92, by @asghaier76.
-
Participants
-
2 organizations joined.
-
Transmute joined.
-
Intel Corporation joined.
-
-
1 organization left.
-
GROUPE BPCE left.
-
GitHub
w3c/vc-data-model
-
17 issues opened.
-
Verification w3c/vc-data-model#408, by @David-Chadwick.
-
Authorisation w3c/vc-data-model#406, by @David-Chadwick.
-
Level of Assurance vs. Evidence w3c/vc-data-model#405, by @David-Chadwick.
-
Normative terminology (e.g. MUST) in sections marked non-normative w3c/vc-data-model#394, by @nedmsmith.
-
Vocabulary location decisions w3c/vc-data-model#391, by @msporny.
-
Issues from CCG review w3c/vc-data-model#383, by @David-Chadwick.
-
Schema link needs updating in Example 13 w3c/vc-data-model#382, by @David-Chadwick.
-
Add reference to RFC3986 for URI and URL validation w3c/vc-data-model#381, by @BigBlueHat.
-
Suggest changing `refreshService`'s `serviceEndpoint` to `id` to match other objects w3c/vc-data-model#380, by @BigBlueHat.
-
Link "JSON Schema" text to it's specification as an informative reference w3c/vc-data-model#379, by @BigBlueHat.
-
Defining expected order of credential `type` values w3c/vc-data-model#371, by @BigBlueHat.
-
Remove example context URL from Example 9 in 7.1 Extensibility w3c/vc-data-model#368, by @BigBlueHat.
-
Remove id related requirement in Presentations w3c/vc-data-model#367, by @BigBlueHat.
-
ZKP-Examples have different id values in credentialSchema w3c/vc-data-model#364, by @awoie.
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363, by @mwherman2000.
-
[Identifiers] Clarify/be more explicit about where DIDs can be (optionally) used w3c/vc-data-model#362, by @mwherman2000.
-
Review from Credentials Community Group w3c/vc-data-model#360, by @ChristopherA.
-
-
19 issues closed.
-
Add reference to RFC3986 for URI and URL validation w3c/vc-data-model#381.
-
Link "JSON Schema" text to it's specification as an informative reference w3c/vc-data-model#379.
-
Typos w3c/vc-data-model#201.
-
Indy's needs for ZKPs w3c/vc-data-model#237.
-
Context out of date w3c/vc-data-model#231.
-
Schema link needs updating in Example 13 w3c/vc-data-model#382.
-
Remove example context URL from Example 9 in 7.1 Extensibility w3c/vc-data-model#368.
-
Remove id related requirement in Presentations w3c/vc-data-model#367.
-
How do we know if the subject of the claim is the one making the claim w3c/vc-data-model#303.
-
What does conformance to the recommendation mean? w3c/vc-data-model#294.
-
Just "registry" not "data verification registries" w3c/vc-data-model#292.
-
clarification of extensibility w3c/vc-data-model#241.
-
Only DOCUMENT conformance matters w3c/vc-data-model#317.
-
Explain data model in greater detail in Advanced Concepts section w3c/vc-data-model#268.
-
JWTs encoding/decoding rules are not clear w3c/vc-data-model#336.
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224.
-
Mandatory or Optional? w3c/vc-data-model#247.
-
Terms of Use Approach w3c/vc-data-model#269.
-
Remove language about "accepting" credentials w3c/vc-data-model#293.
-
-
26 issues received 51 new comments.
-
Level of Assurance vs. Evidence w3c/vc-data-model#405 (5 comments by @agropper, @David-Chadwick, @jandrieu, @stonematt)
-
Defining expected order of credential `type` values w3c/vc-data-model#371 (4 comments by @BigBlueHat, @msporny)
-
Validate requirements text matches test suite and current thinking w3c/vc-data-model#270 (3 comments by @msporny, @TzviyaSiegman)
-
ZKP-Examples have different id values in credentialSchema w3c/vc-data-model#364 (2 comments by @awoie, @brentzundel)
-
Schema link needs updating in Example 13 w3c/vc-data-model#382 (2 comments by @David-Chadwick, @msporny)
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224 (2 comments by @brentzundel, @msporny)
-
Explain data model in greater detail in Advanced Concepts section w3c/vc-data-model#268 (2 comments by @msporny)
-
Remove example context URL from Example 9 in 7.1 Extensibility w3c/vc-data-model#368 (1 comment by @msporny)
-
[Identifiers] Clarify/be more explicit about where DIDs can be (optionally) used w3c/vc-data-model#362 (1 comment by @stonematt)
-
How do we know if the subject of the claim is the one making the claim w3c/vc-data-model#303 (1 comment by @msporny)
-
[Mode of Operation] Is it necessary to specify only the *final* holder ... w3c/vc-data-model#363 (1 comment by @David-Chadwick)
-
34 pull requests opened.
-
Explainer editorial pass w3c/vc-data-model#410, by @brentzundel.
-
Editorials w3c/vc-data-model#409, by @David-Chadwick.
-
Update features at risk section w3c/vc-data-model#407, by @burnburn.
-
Update VCDMExplainer.md w3c/vc-data-model#404, by @David-Chadwick.
-
VC Explainer editorial pass w3c/vc-data-model#403, by @brentzundel.
-
Update VCDMExplainer.md w3c/vc-data-model#402, by @David-Chadwick.
-
Update VCDMExplainer.md w3c/vc-data-model#401, by @David-Chadwick.
-
Remove empty docuent sections w3c/vc-data-model#400, by @stonematt.
-
Remove serviceEndpoint property, towards #391, fixes #380 w3c/vc-data-model#399, by @rhiaro.
-
Adding some references w3c/vc-data-model#398, by @rhiaro.
-
Clean up conformance section w3c/vc-data-model#397, by @burnburn.
-
VCDM Explainer Review w3c/vc-data-model#396, by @grantnoble.
-
back to toc instead of title w3c/vc-data-model#395, by @ashimura.
-
Added JWT example to explainer w3c/vc-data-model#393, by @awoie.
-
Added selective disclosure to explainer w3c/vc-data-model#392, by @brentzundel.
-
Fix nesting of sections 10, 11 and 12 w3c/vc-data-model#390, by @rhiaro.
-
Fixes remaining editorial issues from #201 w3c/vc-data-model#389, by @rhiaro.
-
Appendix A Advance Examples update w3c/vc-data-model#388, by @grantnoble.
-
Section 9.10 to 9.12 updates w3c/vc-data-model#387, by @grantnoble.
-
Sections 9 to 9.9 updates w3c/vc-data-model#386, by @grantnoble.
-
Section 8 Review and update w3c/vc-data-model#385, by @grantnoble.
-
Add section on Syntax and Proof Format Trade-Offs. w3c/vc-data-model#384, by @msporny.
-
Explainer input with respect to JWT w3c/vc-data-model#378, by @awoie.
-
added zkp to explainer, also w3c/vc-data-model#377, by @brentzundel.
-
Implement js package. w3c/vc-data-model#376, by @mattcollier.
-
Implement js package. w3c/vc-data-model#375, by @mattcollier.
-
Section 7 updates - linking mostly and some grammar and formatting ch… w3c/vc-data-model#374, by @grantnoble.
-
Section 6 term linking and some grammar w3c/vc-data-model#373, by @grantnoble.
-
Section 3.3 grammar and wording update w3c/vc-data-model#372, by @grantnoble.
-
Section 3.2 grammar and wording update w3c/vc-data-model#370, by @grantnoble.
-
Section 3.1 grammar and wording update w3c/vc-data-model#369, by @grantnoble.
-
Reword section reference for consistency w3c/vc-data-model#366, by @grantnoble.
-
JWT decoding rules w3c/vc-data-model#365, by @awoie.
-
Provided examples for JWT w3c/vc-data-model#361, by @awoie.
-
-
34 pull requests merged.
-
Update features at risk section w3c/vc-data-model#407.
-
Update VCDMExplainer.md w3c/vc-data-model#404.
-
VC Explainer editorial pass w3c/vc-data-model#403.
-
Remove empty docuent sections w3c/vc-data-model#400.
-
Added JWT example to explainer w3c/vc-data-model#393.
-
Added selective disclosure to explainer w3c/vc-data-model#392.
-
Adding some references w3c/vc-data-model#398.
-
Fixes remaining editorial issues from #201 w3c/vc-data-model#389.
-
Appendix A Advance Examples update w3c/vc-data-model#388.
-
Section 9.10 to 9.12 updates w3c/vc-data-model#387.
-
Sections 9 to 9.9 updates w3c/vc-data-model#386.
-
Section 8 Review and update w3c/vc-data-model#385.
-
VCDM Explainer Review w3c/vc-data-model#396.
-
back to toc instead of title w3c/vc-data-model#395.
-
Explainer input with respect to JWT w3c/vc-data-model#378.
-
Section 6 term linking and some grammar w3c/vc-data-model#373.
-
Section 3.3 grammar and wording update w3c/vc-data-model#372.
-
Section 3.2 grammar and wording update w3c/vc-data-model#370.
-
added zkp to explainer, also w3c/vc-data-model#377.
-
Section 7 updates - linking mostly and some grammar and formatting ch… w3c/vc-data-model#374.
-
Section 3.1 grammar and wording update w3c/vc-data-model#369.
-
Reword section reference for consistency w3c/vc-data-model#366.
-
Implement js package. w3c/vc-data-model#376.
-
JWT decoding rules w3c/vc-data-model#365.
-
Replaced language about requirements for "accepting" a verifiable credential w3c/vc-data-model#298.
-
Add section on Zero-Knowledge Proofs. w3c/vc-data-model#352.
-
Section 11 Capitalization suggestion w3c/vc-data-model#359.
-
Section 10.1 formatting suggestions w3c/vc-data-model#358.
-
Section 9.5 wording suggestion w3c/vc-data-model#357.
-
Section 9.3 wording update w3c/vc-data-model#356.
-
Section 9.2 punctuation fix w3c/vc-data-model#355.
-
Section 8.3 links, grammar, and line length fixes w3c/vc-data-model#354.
-
Section 8.2 link fix w3c/vc-data-model#353.
-
Provided examples for JWT w3c/vc-data-model#361.
-
-
4 pull requests closed.
-
Update VCDMExplainer.md w3c/vc-data-model#402.
-
Update VCDMExplainer.md w3c/vc-data-model#401.
-
Fix nesting of sections 10, 11 and 12 w3c/vc-data-model#390.
-
Implement js package. w3c/vc-data-model#375.
-
-
19 pull requests received 44 new comments.
-
Add lifecycle for an example of data flowing through beginning to end. w3c/vc-data-model#313 (9 comments by @gannan08, @jandrieu, @msporny)
-
Update VCDMExplainer.md w3c/vc-data-model#402 (5 comments by @brentzundel, @David-Chadwick, @TzviyaSiegman)
-
Update VCDMExplainer.md w3c/vc-data-model#401 (4 comments by @David-Chadwick, @davidlehn, @TzviyaSiegman)
-
Remove serviceEndpoint property, towards #391, fixes #380 w3c/vc-data-model#399 (3 comments by @BigBlueHat, @rhiaro)
-
Add section on Syntax and Proof Format Trade-Offs. w3c/vc-data-model#384 (2 comments by @David-Chadwick, @pelle)
-
w3c/vc-test-suite
-
1 pull request opened.
-
Stub out MUSTs w3c/vc-test-suite#6, by @BigBlueHat.
-
-
2 pull requests merged.
-
Stub out MUSTs w3c/vc-test-suite#6.
-
This is a rewrite of the VC Data Model Test Suite to Javascript/Mocha w3c/vc-test-suite#5.
-
-
2 pull requests received 10 new comments.
-
This is a rewrite of the VC Data Model Test Suite to Javascript/Mocha w3c/vc-test-suite#5 (1 comment by @msporny)
w3c/vc-use-cases
-
1 issue opened.
-
Typo: contuning education w3c/vc-use-cases#91, by @westurner.
-
w3c/vc-data-integrity
-
2 issues opened.
-
[Terminology] Definition of a linked data document is not discernable w3c/vc-data-integrity#13, by @mwherman2000.
-
[EXAMPLE 1] Is Example 1 technically a Linked Data document or just a Simple Document? w3c/vc-data-integrity#14, by @mwherman2000.
-