Verifiable Credentials Working Group - Activity in 2018
No matches.
GitHub
w3c/vc-data-model
-
4 issues opened.
-
JWTs encoding/decoding rules are not clear w3c/vc-data-model#336, by @msporny.
-
Only DOCUMENT conformance matters w3c/vc-data-model#317, by @burnburn.
-
"Verifiable Credential" which only contains limited uses w3c/vc-data-model#312, by @chaoxinhu.
-
How do we know if the subject of the claim is the one making the claim w3c/vc-data-model#303, by @TomCJones.
-
-
3 issues closed.
-
Provide support for JWT data format w3c/vc-data-model#266.
-
Rename "claim" to "subject" w3c/vc-data-model#207.
-
More VC Type corrections w3c/vc-data-model#242.
-
-
7 issues received 19 new comments.
-
How do we know if the subject of the claim is the one making the claim w3c/vc-data-model#303 (6 comments by @David-Chadwick, @jandrieu, @TomCJones)
-
"Verifiable Credential" which only contains limited uses w3c/vc-data-model#312 (4 comments by @agropper, @chaoxinhu, @ChristopherA, @David-Chadwick)
-
-
57 pull requests opened.
-
Section 11 Capitalization suggestion w3c/vc-data-model#359, by @grantnoble.
-
Section 10.1 formatting suggestions w3c/vc-data-model#358, by @grantnoble.
-
Section 9.5 wording suggestion w3c/vc-data-model#357, by @grantnoble.
-
Section 9.3 wording update w3c/vc-data-model#356, by @grantnoble.
-
Section 9.2 punctuation fix w3c/vc-data-model#355, by @grantnoble.
-
Section 8.3 links, grammar, and line length fixes w3c/vc-data-model#354, by @grantnoble.
-
Section 8.2 link fix w3c/vc-data-model#353, by @grantnoble.
-
Add section on Zero-Knowledge Proofs. w3c/vc-data-model#352, by @msporny.
-
Section 7.8 Disputes, links added and some restructuring w3c/vc-data-model#351, by @grantnoble.
-
Example title text tidy up w3c/vc-data-model#350, by @grantnoble.
-
Section 7.7.4 Linking, and rewording w3c/vc-data-model#349, by @grantnoble.
-
Section 7.7.3 Links and wording changes w3c/vc-data-model#348, by @grantnoble.
-
Section 7.7.2 links and wording changes w3c/vc-data-model#347, by @grantnoble.
-
Section 7.7.1 links added and some wording changes w3c/vc-data-model#346, by @grantnoble.
-
Section 7.6 Evidence minor wording change w3c/vc-data-model#345, by @grantnoble.
-
Section 7.5 Terms of Use minor wording change w3c/vc-data-model#344, by @grantnoble.
-
Update conformance section. w3c/vc-data-model#343, by @davidlehn.
-
Section 6.4 term linking, formatting and grammar suggestions w3c/vc-data-model#342, by @grantnoble.
-
Section 6.3 formatting and grammar suggestions w3c/vc-data-model#341, by @grantnoble.
-
Section 6.2 mostly grammar and formatting suggestions w3c/vc-data-model#340, by @grantnoble.
-
Section 6.1.1 upper case Context to lower case w3c/vc-data-model#339, by @grantnoble.
-
Section 6 and 6.1 grammar and formatting suggestions w3c/vc-data-model#338, by @grantnoble.
-
Valid vs verify w3c/vc-data-model#337, by @David-Chadwick.
-
Section 5.7 link suggestions w3c/vc-data-model#335, by @grantnoble.
-
Section 5.6 "If specified" for consistency w3c/vc-data-model#334, by @grantnoble.
-
Section 5.5 updated heading level for consistency w3c/vc-data-model#333, by @grantnoble.
-
Section 5.4 link suggestions w3c/vc-data-model#332, by @grantnoble.
-
Section 5.3 links and formatting suggestions w3c/vc-data-model#331, by @grantnoble.
-
Section 5.2 links and grammar suggestions w3c/vc-data-model#330, by @grantnoble.
-
Section 5.1 minor update w3c/vc-data-model#329, by @grantnoble.
-
Section 4 links and grammar suggestions w3c/vc-data-model#328, by @grantnoble.
-
Section 3.3 links added and tidied up w3c/vc-data-model#327, by @grantnoble.
-
Section 3.2 links and grammar and other suggestions w3c/vc-data-model#326, by @grantnoble.
-
Section 3.1 one link added w3c/vc-data-model#325, by @grantnoble.
-
Section 2 Terminology links and grammar suggestions w3c/vc-data-model#324, by @grantnoble.
-
Section 1.3 add links and grammar suggestions w3c/vc-data-model#323, by @grantnoble.
-
Fix markup w3c/vc-data-model#322, by @davidlehn.
-
Add "id" to JWT example. w3c/vc-data-model#321, by @davidlehn.
-
Section 1.2 added links and grammar suggestions w3c/vc-data-model#320, by @grantnoble.
-
Section 1.1 Links added and some grammar suggestions w3c/vc-data-model#319, by @grantnoble.
-
Abstract/Intro sections links added plus a few grammar suggestions w3c/vc-data-model#318, by @grantnoble.
-
Change claim to credentialSubject. w3c/vc-data-model#316, by @davidlehn.
-
updated code sample, tricky design choices w3c/vc-data-model#315, by @TzviyaSiegman.
-
correct typos, add implementation and review info w3c/vc-data-model#314, by @TzviyaSiegman.
-
Add lifecycle for an example of data flowing through beginning to end. w3c/vc-data-model#313, by @gannan08.
-
Suggestions for Section 6.10 Syntactic Sugar w3c/vc-data-model#311, by @msporny.
-
Section 11 grammar and formatting suggestions w3c/vc-data-model#310, by @msporny.
-
Section 10 grammar and formatting suggestions w3c/vc-data-model#309, by @msporny.
-
Section 9 grammar and formatting suggestions w3c/vc-data-model#308, by @msporny.
-
Suggestions for section 6.10 syntactic sugar w3c/vc-data-model#307, by @grantnoble.
-
section11 grammar and formatting suggestions w3c/vc-data-model#306, by @grantnoble.
-
section10 grammar and formatting suggestions w3c/vc-data-model#305, by @grantnoble.
-
Create VCDM Explainer w3c/vc-data-model#304, by @TzviyaSiegman.
-
section9 grammar and formatting suggestions w3c/vc-data-model#302, by @grantnoble.
-
grantnoble section8 Verification grammar and formatting suggestions w3c/vc-data-model#301, by @grantnoble.
-
Grammar and formatting suggestions for section 7 Syntaxes w3c/vc-data-model#300, by @grantnoble.
-
Grantnoble section6 grammar format suggestions w3c/vc-data-model#299, by @grantnoble.
-
-
51 pull requests merged.
-
Section 7.8 Disputes, links added and some restructuring w3c/vc-data-model#351.
-
Example title text tidy up w3c/vc-data-model#350.
-
Section 7.7.3 Links and wording changes w3c/vc-data-model#348.
-
Section 7.7.4 Linking, and rewording w3c/vc-data-model#349.
-
Section 7.7.2 links and wording changes w3c/vc-data-model#347.
-
Section 7.7.1 links added and some wording changes w3c/vc-data-model#346.
-
Section 7.6 Evidence minor wording change w3c/vc-data-model#345.
-
Section 7.5 Terms of Use minor wording change w3c/vc-data-model#344.
-
Update conformance section. w3c/vc-data-model#343.
-
Fix markup w3c/vc-data-model#322.
-
Section 6.4 term linking, formatting and grammar suggestions w3c/vc-data-model#342.
-
Section 6.3 formatting and grammar suggestions w3c/vc-data-model#341.
-
Section 6.2 mostly grammar and formatting suggestions w3c/vc-data-model#340.
-
Section 6.1.1 upper case Context to lower case w3c/vc-data-model#339.
-
Section 6 and 6.1 grammar and formatting suggestions w3c/vc-data-model#338.
-
Remove delegation w3c/vc-data-model#283.
-
Section 1.2 added links and grammar suggestions w3c/vc-data-model#320.
-
Section 1.1 Links added and some grammar suggestions w3c/vc-data-model#319.
-
Abstract/Intro sections links added plus a few grammar suggestions w3c/vc-data-model#318.
-
Valid vs verify w3c/vc-data-model#337.
-
Section 5.7 link suggestions w3c/vc-data-model#335.
-
Section 5.6 "If specified" for consistency w3c/vc-data-model#334.
-
Section 5.5 updated heading level for consistency w3c/vc-data-model#333.
-
Section 5.4 link suggestions w3c/vc-data-model#332.
-
Section 5.3 links and formatting suggestions w3c/vc-data-model#331.
-
Section 5.2 links and grammar suggestions w3c/vc-data-model#330.
-
Section 5.1 minor update w3c/vc-data-model#329.
-
Section 4 links and grammar suggestions w3c/vc-data-model#328.
-
Section 3.3 links added and tidied up w3c/vc-data-model#327.
-
Section 3.1 one link added w3c/vc-data-model#325.
-
Section 3.2 links and grammar and other suggestions w3c/vc-data-model#326.
-
Section 2 Terminology links and grammar suggestions w3c/vc-data-model#324.
-
Section 1.3 add links and grammar suggestions w3c/vc-data-model#323.
-
Addressing issue #266 by providing a mapping of the data model for JWT w3c/vc-data-model#267.
-
updated code sample, tricky design choices w3c/vc-data-model#315.
-
Change claim to credentialSubject. w3c/vc-data-model#316.
-
correct typos, add implementation and review info w3c/vc-data-model#314.
-
Grantnoble section6 grammar format suggestions w3c/vc-data-model#299.
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214.
-
Suggestions for Section 6.10 Syntactic Sugar w3c/vc-data-model#311.
-
Section 11 grammar and formatting suggestions w3c/vc-data-model#310.
-
Section 10 grammar and formatting suggestions w3c/vc-data-model#309.
-
Section 9 grammar and formatting suggestions w3c/vc-data-model#308.
-
Create VCDM Explainer w3c/vc-data-model#304.
-
Add section on syntactic sugar. See #207 and #268. w3c/vc-data-model#255.
-
grantnoble section8 Verification grammar and formatting suggestions w3c/vc-data-model#301.
-
Grammar and formatting suggestions for section 7 Syntaxes w3c/vc-data-model#300.
-
Grammar and formatting suggestions for Section 5, Basic Concepts w3c/vc-data-model#297.
-
Mode of operation w3c/vc-data-model#291.
-
Add section on Data Schemas. Related to #241. w3c/vc-data-model#280.
-
Fix 242 w3c/vc-data-model#274.
-
-
8 pull requests closed.
-
Delegation and attenuation w3c/vc-data-model#229.
-
Added first few examples and text to data model that highlights zkp w3c/vc-data-model#265.
-
Add "id" to JWT example. w3c/vc-data-model#321.
-
Trust model fix w3c/vc-data-model#296.
-
Suggestions for section 6.10 syntactic sugar w3c/vc-data-model#307.
-
section11 grammar and formatting suggestions w3c/vc-data-model#306.
-
section10 grammar and formatting suggestions w3c/vc-data-model#305.
-
section9 grammar and formatting suggestions w3c/vc-data-model#302.
-
-
2 pull requests reopened.
-
Replaced language about requirements for "accepting" a verifiable credential w3c/vc-data-model#298, by @msporny.
-
Grantnoble section6 grammar format suggestions w3c/vc-data-model#299, by @dlongley.
-
-
20 pull requests received 167 new comments.
-
Replaced language about requirements for "accepting" a verifiable credential w3c/vc-data-model#298 (52 comments by @David-Chadwick, @dlongley, @jandrieu, @msporny, @stonematt, @TallTed)
-
Addressing issue #266 by providing a mapping of the data model for JWT w3c/vc-data-model#267 (31 comments by @awoie, @davidlehn, @dlongley, @msporny, @pelle)
-
Grantnoble section6 grammar format suggestions w3c/vc-data-model#299 (26 comments by @davidlehn, @dlongley, @grantnoble, @msporny)
-
Add lifecycle for an example of data flowing through beginning to end. w3c/vc-data-model#313 (11 comments by @David-Chadwick, @gannan08, @msporny, @stonematt, @TzviyaSiegman)
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214 (3 comments by @brentzundel, @dlongley, @msporny)
-
Added first few examples and text to data model that highlights zkp w3c/vc-data-model#265 (1 comment by @msporny)
-
Grammar and formatting suggestions for section 7 Syntaxes w3c/vc-data-model#300 (1 comment by @msporny)
-
w3c/vc-test-suite
-
1 pull request opened.
-
This is a rewrite of the VC Data Model Test Suite to Javascript/Mocha w3c/vc-test-suite#5, by @msporny.
-
-
1 pull request merged.
-
Pretty large refactor, plus most of the tests w3c/vc-test-suite#4.
-
w3c/vc-use-cases
-
1 issue received 1 new comment.
Participants
-
2 organizations joined.
-
Ping Identity joined.
-
SecureKey joined.
-
GitHub
w3c/vc-data-model
-
9 issues opened.
-
What does conformance to the recommendation mean? w3c/vc-data-model#294, by @David-Chadwick.
-
Remove language about "accepting" credentials w3c/vc-data-model#293, by @jandrieu.
-
Just "registry" not "data verification registries" w3c/vc-data-model#292, by @ChristopherA.
-
Deontic concepts supported by termsOfUse w3c/vc-data-model#276, by @simonstey.
-
What must the Creator field carry? IRI to pem or IRI to LD or a simple string w3c/vc-data-model#275, by @indrajra.
-
Validate requirements text matches test suite and current thinking w3c/vc-data-model#270, by @stonematt.
-
Terms of Use Approach w3c/vc-data-model#269, by @stonematt.
-
Explain data model in greater detail in Advanced Concepts section w3c/vc-data-model#268, by @msporny.
-
Provide support for JWT data format w3c/vc-data-model#266, by @awoie.
-
-
9 issues closed.
-
Review & Clarify Trust Model Section re: No Transitive Trust & Delegated Keys w3c/vc-data-model#252.
-
Refer to the threat model in the Use Cases document w3c/vc-data-model#251.
-
Inconsistency in presentation w3c/vc-data-model#240.
-
Disputed credentials - who can issue them? w3c/vc-data-model#226.
-
What must the Creator field carry? IRI to pem or IRI to LD or a simple string w3c/vc-data-model#275.
-
Should terms like ageOver be in the context? w3c/vc-data-model#245.
-
Accessibility Impact Statement w3c/vc-data-model#221.
-
Delegated authorization & VC distribution w3c/vc-data-model#204.
-
Add brief section explaining relationship between DIDs and VCs w3c/vc-data-model#250.
-
-
15 issues received 79 new comments.
-
Review & Clarify Trust Model Section re: No Transitive Trust & Delegated Keys w3c/vc-data-model#252 (19 comments by @ChristopherA, @David-Chadwick, @dlongley, @dmitrizagidulin, @jandrieu, @msporny, @stonematt)
-
Rename "claim" to "subject" w3c/vc-data-model#207 (15 comments by @David-Chadwick, @dlongley, @jandrieu, @msporny, @TallTed)
-
Explain data model in greater detail in Advanced Concepts section w3c/vc-data-model#268 (5 comments by @David-Chadwick, @msporny, @TallTed, @TzviyaSiegman)
-
What must the Creator field carry? IRI to pem or IRI to LD or a simple string w3c/vc-data-model#275 (5 comments by @dlongley, @indrajra, @msporny)
-
What does conformance to the recommendation mean? w3c/vc-data-model#294 (4 comments by @David-Chadwick, @jandrieu, @msporny)
-
Remove language about "accepting" credentials w3c/vc-data-model#293 (4 comments by @David-Chadwick, @jandrieu, @msporny)
-
Deontic concepts supported by termsOfUse w3c/vc-data-model#276 (3 comments by @David-Chadwick, @msporny)
-
Comments on Section 6.2 Terms of Use w3c/vc-data-model#234 (3 comments by @burnburn, @David-Chadwick, @stonematt)
-
Just "registry" not "data verification registries" w3c/vc-data-model#292 (1 comment by @ChristopherA)
-
-
27 pull requests opened.
-
Replaced language about requirements for "accepting" a verifiable credential w3c/vc-data-model#298, by @jandrieu.
-
Grammar and formatting suggestions for Section 5, Basic Concepts w3c/vc-data-model#297, by @grantnoble.
-
Trust model fix w3c/vc-data-model#296, by @David-Chadwick.
-
Revert "Deontic ToU" w3c/vc-data-model#295, by @msporny.
-
Mode of operation w3c/vc-data-model#291, by @David-Chadwick.
-
Revert "update" w3c/vc-data-model#290, by @David-Chadwick.
-
update w3c/vc-data-model#289, by @David-Chadwick.
-
Grantnoble section4 grammar typos suggestions w3c/vc-data-model#288, by @grantnoble.
-
Grammar and formatting suggestions for section 3, Core Data Model w3c/vc-data-model#287, by @grantnoble.
-
Grammar and formatting updates to terms.html (section 2 for VC data model) w3c/vc-data-model#286, by @grantnoble.
-
Grammar/typo/formatting updates for Section 1 w3c/vc-data-model#285, by @grantnoble.
-
Grammar/typo/formatting updates for Section 1 w3c/vc-data-model#284, by @grantnoble.
-
Remove delegation w3c/vc-data-model#283, by @David-Chadwick.
-
Deontic ToU w3c/vc-data-model#282, by @David-Chadwick.
-
Removed delegation w3c/vc-data-model#281, by @David-Chadwick.
-
Add section on Data Schemas. Related to #241. w3c/vc-data-model#280, by @msporny.
-
Add note on transitive trust to Trust Model section. Fix #252. w3c/vc-data-model#279, by @msporny.
-
Refer to the threat model in the Use Cases document. Fix #251. w3c/vc-data-model#278, by @msporny.
-
Rename "claim" to "credentialSubject" w3c/vc-data-model#277, by @msporny.
-
Fix 242 w3c/vc-data-model#274, by @David-Chadwick.
-
Update Subject paragraph to refer to claim w3c/vc-data-model#273, by @stonematt.
-
Update presentation definition w3c/vc-data-model#272, by @stonematt.
-
Rebased 217 - Describing presentation and clarifying its relationship to a credential w3c/vc-data-model#271, by @brentzundel.
-
Addressing issue #266 by providing a mapping of the data model for JWT w3c/vc-data-model#267, by @awoie.
-
Added first few examples and text to data model that highlights zkp w3c/vc-data-model#265, by @brentzundel.
-
Added first few examples using ZKP. w3c/vc-data-model#264, by @brentzundel.
-
Clarified URIs may be references to verifiable data registry w3c/vc-data-model#263, by @brentzundel.
-
-
19 pull requests merged.
-
Grantnoble section4 grammar typos suggestions w3c/vc-data-model#288.
-
Grammar and formatting suggestions for section 3, Core Data Model w3c/vc-data-model#287.
-
Grammar and formatting updates to terms.html (section 2 for VC data model) w3c/vc-data-model#286.
-
Deontic ToU w3c/vc-data-model#282.
-
Add note on transitive trust to Trust Model section. Fix #252. w3c/vc-data-model#279.
-
Refer to the threat model in the Use Cases document. Fix #251. w3c/vc-data-model#278.
-
Rename "claim" to "credentialSubject" w3c/vc-data-model#277.
-
Revert "update" w3c/vc-data-model#290.
-
update w3c/vc-data-model#289.
-
Grammar/typo/formatting updates for Section 1 w3c/vc-data-model#285.
-
Rebased #227 - David Chadwick's fixes for disputed credentials w3c/vc-data-model#259.
-
Update Subject paragraph to refer to claim w3c/vc-data-model#273.
-
Update presentation definition w3c/vc-data-model#272.
-
Add privacy paragraph to introduction w3c/vc-data-model#262.
-
Add examples JSON-LD Context file. Fix #245. w3c/vc-data-model#254.
-
Rebased 217 - Describing presentation and clarifying its relationship to a credential w3c/vc-data-model#271.
-
Finalize the context URL for the spec to address #206. w3c/vc-data-model#258.
-
Add section on Authorization. Fix #204. w3c/vc-data-model#257.
-
Add a section on identifiers to address issue #250. w3c/vc-data-model#256.
-
-
6 pull requests closed.
-
Revert "Deontic ToU" w3c/vc-data-model#295.
-
Clarified URIs may be references to verifiable data registry w3c/vc-data-model#263.
-
Removed delegation w3c/vc-data-model#281.
-
Grammar/typo/formatting updates for Section 1 w3c/vc-data-model#284.
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217.
-
Added first few examples using ZKP. w3c/vc-data-model#264.
-
-
29 pull requests received 209 new comments.
-
Addressing issue #266 by providing a mapping of the data model for JWT w3c/vc-data-model#267 (44 comments by @awoie, @burnburn, @dlongley, @msporny)
-
Mode of operation w3c/vc-data-model#291 (23 comments by @burnburn, @David-Chadwick, @dlongley, @msporny)
-
Grammar and formatting suggestions for Section 5, Basic Concepts w3c/vc-data-model#297 (18 comments by @David-Chadwick, @davidlehn, @grantnoble)
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214 (13 comments by @brentzundel, @David-Chadwick, @dlongley, @ken-ebert, @msporny, @stonematt)
-
Add section on Data Schemas. Related to #241. w3c/vc-data-model#280 (10 comments by @brentzundel, @David-Chadwick, @davidlehn, @dlongley, @msporny)
-
Replaced language about requirements for "accepting" a verifiable credential w3c/vc-data-model#298 (9 comments by @David-Chadwick, @jandrieu, @stonematt)
-
Deontic ToU w3c/vc-data-model#282 (9 comments by @brentzundel, @ChristopherA, @David-Chadwick, @dlongley, @jandrieu, @msporny)
-
Add note on transitive trust to Trust Model section. Fix #252. w3c/vc-data-model#279 (9 comments by @ChristopherA, @David-Chadwick, @davidlehn, @msporny)
-
Finalize the context URL for the spec to address #206. w3c/vc-data-model#258 (9 comments by @davidlehn, @gkellogg, @msporny)
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217 (8 comments by @brentzundel, @davidlehn, @msporny)
-
Clarified URIs may be references to verifiable data registry w3c/vc-data-model#263 (6 comments by @BigBlueHat, @brentzundel, @davidlehn, @ken-ebert, @msporny)
-
Added first few examples and text to data model that highlights zkp w3c/vc-data-model#265 (5 comments by @msporny)
-
Rebased #227 - David Chadwick's fixes for disputed credentials w3c/vc-data-model#259 (1 comment by @stonematt)
-
Rebased 217 - Describing presentation and clarifying its relationship to a credential w3c/vc-data-model#271 (1 comment by @msporny)
-
w3c/vc-use-cases
-
1 issue received 7 new comments.
-
Add a Threat Model section w3c/vc-use-cases#90 (7 comments by @CipherQueen, @David-Chadwick, @jandrieu)
-
w3c/vc-data-integrity
-
3 issues opened.
-
LD-Proofs v LD-Signatures w3c/vc-data-integrity#5, by @johnptoohey.
-
Authenticity checks w3c/vc-data-integrity#3, by @kimdhamilton.
-
Ambiguity resulting from signature -> proof rename w3c/vc-data-integrity#2, by @kimdhamilton.
-
-
2 issues received 5 new comments.
-
1 pull request opened.
-
Fix github links w3c/vc-data-integrity#1, by @kimdhamilton.
-
-
1 pull request merged.
-
Fix github links w3c/vc-data-integrity#1.
-
Participants
-
1 participant joined.
-
Naomi Yoshizawa (W3C) joined.
-
-
1 participant left.
-
Sam Sugimoto (W3C) left.
-
GitHub
w3c/vc-data-model
-
14 issues opened.
-
Is a VC a tree or a graph? w3c/vc-data-model#260, by @David-Chadwick.
-
Decide if there should be an EOL date on the spec? w3c/vc-data-model#253, by @stonematt.
-
Review & Clarify Trust Model Section re: No Transitive Trust & Delegated Keys w3c/vc-data-model#252, by @ChristopherA.
-
Refer to the threat model in the Use Cases document w3c/vc-data-model#251, by @msporny.
-
Add brief section explaining relationship between DIDs and VCs w3c/vc-data-model#250, by @dmitrizagidulin.
-
Add a summary text as meta information w3c/vc-data-model#248, by @RieksJ.
-
Mandatory or Optional? w3c/vc-data-model#247, by @David-Chadwick.
-
Should terms like ageOver be in the context? w3c/vc-data-model#245, by @cwebber.
-
Privacy issues w3c/vc-data-model#244, by @David-Chadwick.
-
Minor typo w3c/vc-data-model#243, by @David-Chadwick.
-
More VC Type corrections w3c/vc-data-model#242, by @David-Chadwick.
-
clarification of extensibility w3c/vc-data-model#241, by @David-Chadwick.
-
Inconsistency in presentation w3c/vc-data-model#240, by @David-Chadwick.
-
Inconsistency in description of identifier registry w3c/vc-data-model#239, by @David-Chadwick.
-
-
6 issues closed.
-
Terminology in the two documents w3c/vc-data-model#200.
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72.
-
New section/paper: gap analysis w3c/vc-data-model#233.
-
How are verifiable credentials updated w3c/vc-data-model#139.
-
Add renewalService URL to standard data model w3c/vc-data-model#19.
-
Privacy: Anonymous credentials w3c/vc-data-model#125.
-
-
32 issues received 67 new comments.
-
Rename "claim" to "subject" w3c/vc-data-model#207 (7 comments by @burnburn, @David-Chadwick, @jandrieu, @msporny, @RieksJ, @TallTed)
-
Add a summary text as meta information w3c/vc-data-model#248 (6 comments by @ChristopherA, @David-Chadwick, @msporny, @RieksJ, @stonematt)
-
Should terms like ageOver be in the context? w3c/vc-data-model#245 (4 comments by @burnburn, @David-Chadwick, @msporny)
-
Inconsistency in presentation w3c/vc-data-model#240 (3 comments by @David-Chadwick, @jandrieu, @stonematt)
-
Add brief section explaining relationship between DIDs and VCs w3c/vc-data-model#250 (2 comments by @dmitrizagidulin, @msporny)
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224 (2 comments by @dlongley, @msporny)
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203 (2 comments by @burnburn, @stonematt)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (2 comments by @msporny, @stonematt)
-
Add canonical way to reference JSON Schema against which credential should be validated w3c/vc-data-model#129 (2 comments by @gkellogg, @msporny)
-
Review & Clarify Trust Model Section re: No Transitive Trust & Delegated Keys w3c/vc-data-model#252 (1 comment by @David-Chadwick)
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72 (1 comment by @burnburn)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @burnburn)
-
w3c/vc-data-model#19 (1 comment by @dlongley)
-
-
10 pull requests opened.
-
Add privacy paragraph to introduction w3c/vc-data-model#262, by @brentzundel.
-
Use IPLD as a JSON syntax for claim w3c/vc-data-model#261, by @jonnycrunch.
-
Rebased #227 - David Chadwick's fixes for disputed credentials w3c/vc-data-model#259, by @dlongley.
-
Finalize the context URL for the spec to address #206. w3c/vc-data-model#258, by @msporny.
-
Add section on Authorization. Fix #204. w3c/vc-data-model#257, by @msporny.
-
Add a section on identifiers to address issue #250. w3c/vc-data-model#256, by @msporny.
-
Add section on syntactic sugar. See #207 and #268. w3c/vc-data-model#255, by @msporny.
-
Add examples JSON-LD Context file. Fix #245. w3c/vc-data-model#254, by @msporny.
-
Better requirement for proofPurpose's presence and validity. w3c/vc-data-model#249, by @cwebber.
-
Add section on Accessibility considerations. w3c/vc-data-model#246, by @msporny.
-
-
6 pull requests merged.
-
Consistently use the VerifiableCredential type w3c/vc-data-model#230.
-
Better requirement for proofPurpose's presence and validity. w3c/vc-data-model#249.
-
draft accessibility impact statement w3c/vc-data-model#238.
-
Add section on Accessibility considerations. w3c/vc-data-model#246.
-
Add refreshService feature. w3c/vc-data-model#210.
-
Add caveat about JIT bearer credentials w3c/vc-data-model#228.
-
-
3 pull requests closed.
-
Disputed credentials w3c/vc-data-model#227.
-
Add accessibility note w3c/vc-data-model#235.
-
Update link to common terms.html w3c/vc-data-model#236.
-
-
18 pull requests received 74 new comments.
-
Consistently use the VerifiableCredential type w3c/vc-data-model#230 (10 comments by @cwebber, @David-Chadwick, @jandrieu, @msporny)
-
Add section on Authorization. Fix #204. w3c/vc-data-model#257 (6 comments by @brentzundel, @David-Chadwick, @msporny)
-
Finalize the context URL for the spec to address #206. w3c/vc-data-model#258 (5 comments by @brentzundel, @David-Chadwick, @gkellogg, @msporny)
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214 (5 comments by @brentzundel, @David-Chadwick, @jandrieu, @msporny)
-
Update link to common terms.html w3c/vc-data-model#236 (5 comments by @gkellogg, @msporny, @stonematt)
-
Use IPLD as a JSON syntax for claim w3c/vc-data-model#261 (4 comments by @BigBlueHat, @burnburn, @jonnycrunch, @msporny)
-
Rebased #227 - David Chadwick's fixes for disputed credentials w3c/vc-data-model#259 (4 comments by @David-Chadwick, @dlongley, @gannan08, @msporny)
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217 (3 comments by @brentzundel, @burnburn, @msporny)
-
Add a section on identifiers to address issue #250. w3c/vc-data-model#256 (3 comments by @David-Chadwick, @dmitrizagidulin, @msporny)
-
Add section on syntactic sugar. See #207 and #268. w3c/vc-data-model#255 (3 comments by @David-Chadwick, @dlongley)
-
Add privacy paragraph to introduction w3c/vc-data-model#262 (2 comments by @brentzundel, @David-Chadwick)
-
Add examples JSON-LD Context file. Fix #245. w3c/vc-data-model#254 (2 comments by @BigBlueHat, @msporny)
-
Add section on Accessibility considerations. w3c/vc-data-model#246 (2 comments by @msporny, @stonematt)
-
Better requirement for proofPurpose's presence and validity. w3c/vc-data-model#249 (1 comment by @msporny)
w3c/vc-use-cases
-
2 issues opened.
-
Add a Threat Model section w3c/vc-use-cases#90, by @msporny.
-
Can I verifify/validate/understand who the issuer is w3c/vc-use-cases#89, by @stonematt.
-
-
2 issues closed.
-
Broken Links in respec w3c/vc-use-cases#78.
-
VC use cases - "Dispute" User task w3c/vc-use-cases#42.
-
-
1 issue reopened.
-
New section: gap analysis w3c/vc-use-cases#51, by @dlongley.
-
-
12 issues received 14 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)
-
w3c/vc-use-cases#37 (1 comment by @jandrieu)
-
1 pull request received 4 new comments.
-
Add example for International Travel with Minor w3c/vc-use-cases#86 (4 comments by @davidlehn, @stonematt)
-
w3c/vc-test-suite
-
2 pull requests opened.
-
Pretty large refactor, plus most of the tests w3c/vc-test-suite#4, by @cwebber.
-
Test expires w3c/vc-test-suite#3, by @cwebber.
-
-
1 pull request closed.
-
Test expires w3c/vc-test-suite#3.
-
-
1 pull request received 4 new comments.
Participants
-
1 participant joined.
-
Bohdan Andriyiv (W3C Invited Experts) joined.
-
-
1 organization joined.
-
Sovrin Foundation joined.
-
GitHub
w3c/vc-data-model
-
4 issues opened.
-
Indy's needs for ZKPs w3c/vc-data-model#237, by @mikelodder7.
-
Comments on Section 6.2 Terms of Use w3c/vc-data-model#234, by @riannella.
-
New section/paper: gap analysis w3c/vc-data-model#233, by @jandrieu.
-
Context out of date w3c/vc-data-model#231, by @cwebber.
-
-
3 issues closed.
-
Modeling Travel Use Case as an extension example w3c/vc-data-model#187.
-
Use schema.org as the base schema? w3c/vc-data-model#194.
-
Profile ID is ambiguous and potentially improper w3c/vc-data-model#133.
-
-
19 issues received 36 new comments.
-
Image Descriptions requested by Accessibility Group w3c/vc-data-model#225 (3 comments by @dhh1128, @stonematt, @TzviyaSiegman)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (3 comments by @Drabiv, @msporny)
-
Determine how/if WebAuthn will work with VCs w3c/vc-data-model#162 (2 comments by @burnburn, @dlongley)
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164 (1 comment by @stonematt)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @burnburn)
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224 (1 comment by @dhh1128)
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72 (1 comment by @burnburn)
-
6 pull requests opened.
-
draft accessibility impact statement w3c/vc-data-model#238, by @TzviyaSiegman.
-
Update link to common terms.html w3c/vc-data-model#236, by @stonematt.
-
Add accessibility note w3c/vc-data-model#235, by @dhh1128.
-
Remove Pearson reference and Varn w3c/vc-data-model#232, by @stonematt.
-
Consistently use the VerifiableCredential type w3c/vc-data-model#230, by @cwebber.
-
Delegation and attenuation w3c/vc-data-model#229, by @cwebber.
-
-
1 pull request merged.
-
Remove Pearson reference and Varn w3c/vc-data-model#232.
-
-
8 pull requests received 49 new comments.
-
Delegation and attenuation w3c/vc-data-model#229 (21 comments by @agropper, @cwebber, @David-Chadwick, @dhh1128, @dlongley, @msporny, @TallTed)
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217 (11 comments by @David-Chadwick, @dlongley, @lovesh)
-
Add accessibility note w3c/vc-data-model#235 (6 comments by @ChristopherA, @gkellogg, @msporny, @TzviyaSiegman)
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214 (4 comments by @dlongley, @lovesh)
-
w3c/vc-use-cases
-
2 issues opened.
-
Update User Task Image w3c/vc-use-cases#88, by @stonematt.
-
-
4 issues closed.
-
New section - Evidence of applicability w3c/vc-use-cases#50.
-
Supervised Remote In-Person Identity Proofing w3c/vc-use-cases#53.
-
Roles and Tasks w3c/vc-use-cases#79.
-
Sec 4.4 Store/Move claim: confusing “Motivations” w3c/vc-use-cases#2.
-
-
9 issues received 9 new comments.
-
w3c/vc-use-cases#2 (1 comment by @stonematt)
-
2 pull requests opened.
-
Update link to common glossary w3c/vc-use-cases#87, by @stonematt.
-
Add example for International Travel with Minor w3c/vc-use-cases#86, by @stonematt.
-
-
1 pull request merged.
-
Restate details of Store/Move Claim w3c/vc-use-cases#83.
-
-
1 pull request received 3 new comments.
-
Add example for International Travel with Minor w3c/vc-use-cases#86 (3 comments by @David-Chadwick, @davidlehn, @Fak3)
-
Participants
-
1 participant left.
-
Liam Quin (W3C) left.
-
GitHub
w3c/vc-data-model
-
7 issues opened.
-
Disputed credentials - who can issue them? w3c/vc-data-model#226, by @David-Chadwick.
-
Image Descriptions requested by Accessibility Group w3c/vc-data-model#225, by @stonematt.
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224, by @dhh1128.
-
Coordinate with PING during review process w3c/vc-data-model#222, by @stonematt.
-
Accessibility Impact Statement w3c/vc-data-model#221, by @stonematt.
-
Duplicated Syntaxes section (7 & 9) w3c/vc-data-model#212, by @elf-pavlik.
-
Repeated subsections in "Security Consideration" section w3c/vc-data-model#211, by @0x3bfc.
-
-
3 issues closed.
-
Subject NE Holder w3c/vc-data-model#106.
-
Repeated subsections in "Security Consideration" section w3c/vc-data-model#211.
-
Duplicated Syntaxes section (7 & 9) w3c/vc-data-model#212.
-
-
16 issues received 43 new comments.
-
Holders and Identifiers w3c/vc-data-model#105 (9 comments by @David-Chadwick, @msporny, @stonematt, @TallTed)
-
need way to manage terms of use in ZKP verifiable presentations w3c/vc-data-model#224 (7 comments by @CipherQueen, @David-Chadwick, @dhh1128, @dlongley)
-
Privacy: Anonymous credentials w3c/vc-data-model#125 (4 comments by @dhh1128, @lovesh, @stonematt, @talltree)
-
Does pseudo-anonymity require the issuer to cooperate? w3c/vc-data-model#209 (4 comments by @ChristopherA, @stevenrowat, @stonematt, @TzviyaSiegman)
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203 (3 comments by @David-Chadwick, @stonematt)
-
Disputed credentials - who can issue them? w3c/vc-data-model#226 (2 comments by @David-Chadwick, @msporny)
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164 (2 comments by @msporny, @stonematt)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (2 comments by @Drabiv, @kimdhamilton)
-
Repeated subsections in "Security Consideration" section w3c/vc-data-model#211 (1 comment by @msporny)
-
-
11 pull requests opened.
-
Add caveat about JIT bearer credentials w3c/vc-data-model#228, by @dhh1128.
-
Disputed credentials w3c/vc-data-model#227, by @David-Chadwick.
-
pedantic punctuation tweaks in index.html w3c/vc-data-model#223, by @TallTed.
-
Distinguish credentials from presentations w3c/vc-data-model#220, by @dhh1128.
-
Editorial response to issue #201 w3c/vc-data-model#219, by @stonematt.
-
Tamper-evident, not tamper-resistant w3c/vc-data-model#218, by @dhh1128.
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217, by @lovesh.
-
Tamper-evident, not -resistant w3c/vc-data-model#216, by @dhh1128.
-
Tamper-evident, not tamper-resistant w3c/vc-data-model#215, by @dhh1128.
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214, by @lovesh.
-
First draft of editorial changes for privacy preserving credentials w3c/vc-data-model#213, by @lovesh.
-
-
6 pull requests merged.
-
First draft of editorial changes for privacy preserving credentials w3c/vc-data-model#213.
-
Distinguish credentials from presentations w3c/vc-data-model#220.
-
pedantic punctuation tweaks in index.html w3c/vc-data-model#223.
-
Tamper-evident, not tamper-resistant w3c/vc-data-model#218.
-
Editorial response to issue #201 w3c/vc-data-model#219.
-
Subjectnotequal holder w3c/vc-data-model#198.
-
-
3 pull requests closed.
-
Changes for privacy respecting credentials w3c/vc-data-model#208.
-
Tamper-evident, not -resistant w3c/vc-data-model#216.
-
Tamper-evident, not tamper-resistant w3c/vc-data-model#215.
-
-
12 pull requests received 196 new comments.
-
First draft of editorial changes for privacy preserving credentials w3c/vc-data-model#213 (86 comments by @dhh1128, @dlongley, @lovesh)
-
Distinguish credentials from presentations w3c/vc-data-model#220 (45 comments by @David-Chadwick, @dhh1128, @msporny)
-
Describing presentation and clarifying its relationship to a credential. w3c/vc-data-model#217 (20 comments by @davidlehn, @dlongley, @lovesh, @msporny)
-
Replace identifier registry with Verifiable data registry. Clarify … w3c/vc-data-model#214 (10 comments by @lovesh, @msporny)
-
Add refreshService feature. w3c/vc-data-model#210 (8 comments by @David-Chadwick, @msporny, @stonematt)
-
w3c/vc-use-cases
-
3 issues closed.
-
coupons w3c/vc-use-cases#22.
-
Add Examples w3c/vc-use-cases#20.
-
Loyalty & Membership UseCase? w3c/vc-use-cases#21.
-
-
3 issues received 4 new comments.
-
w3c/vc-use-cases#20 (2 comments by @jandrieu)
-
w3c/vc-use-cases#22 (1 comment by @jandrieu)
-
w3c/vc-use-cases#21 (1 comment by @stonematt)
-
-
1 pull request received 1 new comment.
w3c/vc-data-integrity
-
1 issue received 4 new comments.
-
Missing "created" invalidates signature? w3c/vc-data-integrity#23 (4 comments by @ericelliott, @msporny)
-
Participants
-
3 participants joined.
-
Kazuyuki Ashimura (W3C) joined.
-
Matt Stone (BrightLink) joined.
-
Clare Nelson (W3C Invited Experts) joined.
-
-
2 organizations joined.
-
Becker-Carroll joined.
-
ZNO Labs, Inc. joined.
-
GitHub
w3c/vc-data-model
-
11 issues opened.
-
Does pseudo-anonymity require the issuer to cooperate? w3c/vc-data-model#209, by @stonematt.
-
Rename "claim" to "subject" w3c/vc-data-model#207, by @msporny.
-
Default namespace URL w3c/vc-data-model#206, by @burnburn.
-
Delegated authorization & VC distribution w3c/vc-data-model#204, by @cwebber.
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203, by @David-Chadwick.
-
Align JSON-LD Context with latest Verifiable Credentials specification w3c/vc-data-model#202, by @msporny.
-
Typos w3c/vc-data-model#201, by @CipherQueen.
-
Terminology in the two documents w3c/vc-data-model#200, by @CipherQueen.
-
Add Conformance section w3c/vc-data-model#195, by @msporny.
-
Use schema.org as the base schema? w3c/vc-data-model#194, by @msporny.
-
Enforce strict context ordering w3c/vc-data-model#193, by @msporny.
-
-
16 issues closed.
-
Align JSON-LD Context with latest Verifiable Credentials specification w3c/vc-data-model#202.
-
IDs Not Differentiated Sufficiently w3c/vc-data-model#120.
-
How to know who specified the Terms of Use w3c/vc-data-model#109.
-
Enforce strict context ordering w3c/vc-data-model#193.
-
Problems with the Extensibility Section w3c/vc-data-model#190.
-
Explicitly state JSON Object Types w3c/vc-data-model#123.
-
Will extensibility lead to vulnerability? w3c/vc-data-model#157.
-
Value of Type Property w3c/vc-data-model#183.
-
Add Conformance section w3c/vc-data-model#195.
-
Profiles w3c/vc-data-model#107.
-
Typo in Example 6 w3c/vc-data-model#108.
-
Are CredentialStatus, TermsOfUse, and Evidence useful types? w3c/vc-data-model#182.
-
Disputed credential section is confusing w3c/vc-data-model#180.
-
Renaming "issued" and "expires" to "issuanceDate" and "expirationDate" w3c/vc-data-model#184.
-
Need to restrict top level data types to those specified in the standard w3c/vc-data-model#149.
-
-
32 issues received 80 new comments.
-
Use schema.org as the base schema? w3c/vc-data-model#194 (7 comments by @BigBlueHat, @danbri, @David-Chadwick, @msporny, @stonematt)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (6 comments by @dlongley, @Drabiv, @gkellogg, @msporny, @stonematt)
-
Rename "claim" to "subject" w3c/vc-data-model#207 (5 comments by @David-Chadwick, @msporny, @stonematt)
-
Delegated authorization & VC distribution w3c/vc-data-model#204 (5 comments by @agropper, @ChristopherA, @cwebber, @David-Chadwick)
-
How to prevent a Verifier from acting as an unauthorised Holder w3c/vc-data-model#203 (5 comments by @agropper, @David-Chadwick, @dlongley, @msporny)
-
Does pseudo-anonymity require the issuer to cooperate? w3c/vc-data-model#209 (4 comments by @dlongley, @jandrieu, @stevenrowat)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (3 comments by @Drabiv, @msporny)
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164 (3 comments by @msporny, @stonematt)
-
Align JSON-LD Context with latest Verifiable Credentials specification w3c/vc-data-model#202 (1 comment by @gkellogg)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @msporny)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials. w3c/vc-data-model#128 (1 comment by @msporny)
-
Reference and Attachment properties - add a clear way to reference and attach data into credentials w3c/vc-data-model#126 (1 comment by @msporny)
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118 (1 comment by @David-Chadwick)
-
-
7 pull requests opened.
-
Add refreshService feature. w3c/vc-data-model#210, by @msporny.
-
Changes for privacy respecting credentials w3c/vc-data-model#208, by @lovesh.
-
Update context and vocabulary. w3c/vc-data-model#205, by @gkellogg.
-
Add section on caching credentials and refreshService. Fixes #164. Fixes #139. w3c/vc-data-model#199, by @msporny.
-
Subjectnotequal holder w3c/vc-data-model#198, by @David-Chadwick.
-
Add a section on Conformance w3c/vc-data-model#197, by @msporny.
-
Add processing restrictions to enable semantic interop. Fixes #183. w3c/vc-data-model#196, by @msporny.
-
-
8 pull requests merged.
-
Update context and vocabulary. w3c/vc-data-model#205.
-
Terms of use w3c/vc-data-model#188.
-
Add processing restrictions to enable semantic interop. Fixes #183. w3c/vc-data-model#196.
-
Add a section on Conformance w3c/vc-data-model#197.
-
Attempt to fix #182 by providing type expectations. w3c/vc-data-model#189.
-
Minor changes to disputed credential data model. Fixes #180. w3c/vc-data-model#185.
-
Migrate to issuanceDate and expirationDate. Fixes #184. w3c/vc-data-model#192.
-
Fix #149 by changing the purpose of the id property. w3c/vc-data-model#191.
-
-
3 pull requests closed.
-
Add section on caching credentials and refreshService. Fixes #164. Fixes #139. w3c/vc-data-model#199.
-
Added a new section on Subject NE Holder w3c/vc-data-model#169.
-
Clarified Terms of Use w3c/vc-data-model#170.
-
-
13 pull requests received 106 new comments.
-
Subjectnotequal holder w3c/vc-data-model#198 (53 comments by @cwebber, @David-Chadwick, @dlongley, @msporny)
-
Add section on caching credentials and refreshService. Fixes #164. Fixes #139. w3c/vc-data-model#199 (12 comments by @David-Chadwick, @davidlehn, @msporny)
-
Attempt to fix #182 by providing type expectations. w3c/vc-data-model#189 (12 comments by @burnburn, @David-Chadwick, @msporny)
-
Changes for privacy respecting credentials w3c/vc-data-model#208 (8 comments by @ChristopherA, @dlongley, @lovesh)
-
Minor changes to disputed credential data model. Fixes #180. w3c/vc-data-model#185 (4 comments by @David-Chadwick, @jandrieu, @msporny)
-
Added a new section on Subject NE Holder w3c/vc-data-model#169 (3 comments by @burnburn, @David-Chadwick, @msporny)
-
Add processing restrictions to enable semantic interop. Fixes #183. w3c/vc-data-model#196 (2 comments by @dlongley, @msporny)
-
w3c/vc-use-cases
-
4 issues opened.
-
New icons for Verifiable Claims Roleas w3c/vc-use-cases#80, by @stonematt.
-
Roles and Tasks w3c/vc-use-cases#79, by @stonematt.
-
Broken Links in respec w3c/vc-use-cases#78, by @stonematt.
-
Typos w3c/vc-use-cases#76, by @CipherQueen.
-
-
7 issues closed.
-
Sec 2. In “Holder” the second sentence omitted subject is possibly confusing. w3c/vc-use-cases#5.
-
Inconsistent capitalization of certain words, distracting; needs find/replace w3c/vc-use-cases#3.
-
Possible misinterpretation of ‘provides’ in Sec 1.2; amend to ‘intended’ w3c/vc-use-cases#4.
-
Typos w3c/vc-use-cases#76.
-
Formality/Informality clash in style of example w3c/vc-use-cases#9.
-
Status Section: Direct readers to Github issues as well as to mailing list? w3c/vc-use-cases#1.
-
-
1 issue reopened.
-
Add lifecycle engagement models w3c/vc-use-cases#34, by @jandrieu.
-
-
13 issues received 20 new comments.
-
Is storage out of scope? w3c/vc-use-cases#49 (4 comments by @jandrieu, @msporny, @stonematt, @TzviyaSiegman)
-
w3c/vc-use-cases#9 (2 comments by @stonematt)
-
w3c/vc-use-cases#4 (1 comment by @stonematt)
-
w3c/vc-use-cases#10 (1 comment by @stonematt)
-
w3c/vc-use-cases#6 (1 comment by @stonematt)
-
w3c/vc-use-cases#5 (1 comment by @TzviyaSiegman)
-
w3c/vc-use-cases#1 (1 comment by @stonematt)
-
-
5 pull requests opened.
-
Update definition of holder to match Datamodel w3c/vc-use-cases#84, by @stonematt.
-
Restate details of Store/Move Claim w3c/vc-use-cases#83, by @stonematt.
-
Fix usage of dash and emdash w3c/vc-use-cases#82, by @stonematt.
-
complete editorial changes for issue 76 w3c/vc-use-cases#81, by @stonematt.
-
Editorial changes related to issue #76 w3c/vc-use-cases#77, by @stonematt.
-
-
4 pull requests merged.
-
Update definition of holder to match Datamodel w3c/vc-use-cases#84.
-
Fix usage of dash and emdash w3c/vc-use-cases#82.
-
complete editorial changes for issue 76 w3c/vc-use-cases#81.
-
Editorial changes related to issue #76 w3c/vc-use-cases#77.
-
w3c/vc-data-integrity
-
1 issue opened.
-
Examples of the "domain" field in use? w3c/vc-data-integrity#15, by @cwebber.
-
-
1 issue received 2 new comments.
Participants
-
2 organizations joined.
-
Wymsical Inc joined.
-
Credly joined.
-
GitHub
w3c/vc-data-model
-
3 issues opened.
-
Problems with the Extensibility Section w3c/vc-data-model#190, by @David-Chadwick.
-
Modeling Travel Use Case as an extension example w3c/vc-data-model#187, by @dlongley.
-
Renaming "issued" and "expires" to "issuanceDate" and "expirationDate" w3c/vc-data-model#184, by @lovesh.
-
-
8 issues closed.
-
Holder Bundling of Separate Claims w3c/vc-data-model#70.
-
Unstated expectations and assumptions about subject-holder relationships w3c/vc-data-model#68.
-
Add Accessibility Use Case for under 3.3 Healthcare w3c/vc-data-model#50.
-
Credentials Must always be Verifiable w3c/vc-data-model#178.
-
Broken reference to LD-PROOFS w3c/vc-data-model#137.
-
Verifiable Claims --> Verifiable Credentials w3c/vc-data-model#181.
-
May 2018 - Review comments from Allen Brown w3c/vc-data-model#175.
-
Various questions related to the use of the "type" property w3c/vc-data-model#174.
-
-
23 issues received 61 new comments.
-
Are CredentialStatus, TermsOfUse, and Evidence useful types? w3c/vc-data-model#182 (10 comments by @David-Chadwick, @dlongley, @msporny)
-
Renaming "issued" and "expires" to "issuanceDate" and "expirationDate" w3c/vc-data-model#184 (6 comments by @ChristopherA, @lautarodragan, @msporny, @talltree)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (4 comments by @burnburn, @Drabiv, @msporny)
-
Add Accessibility Use Case for under 3.3 Healthcare w3c/vc-data-model#50 (3 comments by @jandrieu, @msporny, @TzviyaSiegman)
-
Problems with the Extensibility Section w3c/vc-data-model#190 (2 comments by @David-Chadwick, @msporny)
-
Reference and Attachment properties - add a clear way to reference and attach data into credentials w3c/vc-data-model#126 (2 comments by @burnburn, @Drabiv)
-
Unstated expectations and assumptions about subject-holder relationships w3c/vc-data-model#68 (1 comment by @jandrieu)
-
Need to restrict top level data types to those specified in the standard w3c/vc-data-model#149 (1 comment by @msporny)
-
Modeling Travel Use Case as an extension example w3c/vc-data-model#187 (1 comment by @David-Chadwick)
-
Various questions related to the use of the "type" property w3c/vc-data-model#174 (1 comment by @msporny)
-
Ideas for roles to add to the data model for next draft w3c/vc-data-model#57 (1 comment by @burnburn)
-
-
6 pull requests opened.
-
Migrate to issuanceDate and expirationDate. Fixes #184. w3c/vc-data-model#192, by @msporny.
-
Fix #149 by changing the purpose of the id property. w3c/vc-data-model#191, by @msporny.
-
Attempt to fix #182 by providing type expectations. w3c/vc-data-model#189, by @msporny.
-
Terms of use w3c/vc-data-model#188, by @David-Chadwick.
-
Merge pull request #1 from w3c/gh-pages w3c/vc-data-model#186, by @David-Chadwick.
-
Minor changes to disputed credential data model. Fixes #180. w3c/vc-data-model#185, by @msporny.
-
-
1 pull request closed.
-
Merge pull request #1 from w3c/gh-pages w3c/vc-data-model#186.
-
-
8 pull requests received 37 new comments.
-
Added a new section on Subject NE Holder w3c/vc-data-model#169 (14 comments by @burnburn, @David-Chadwick, @dlongley, @jandrieu, @stonematt)
-
Attempt to fix #182 by providing type expectations. w3c/vc-data-model#189 (12 comments by @David-Chadwick, @msporny)
-
Fix #149 by changing the purpose of the id property. w3c/vc-data-model#191 (3 comments by @David-Chadwick, @dlongley, @msporny)
-
Merge pull request #1 from w3c/gh-pages w3c/vc-data-model#186 (2 comments by @David-Chadwick, @stonematt)
-
Minor changes to disputed credential data model. Fixes #180. w3c/vc-data-model#185 (2 comments by @David-Chadwick, @msporny)
-
Migrate to issuanceDate and expirationDate. Fixes #184. w3c/vc-data-model#192 (1 comment by @ericelliott)
-
w3c/vc-use-cases
-
3 issues opened.
-
Holder Bundling of Separate Claims w3c/vc-use-cases#75, by @jandrieu.
-
Add Accessibility Use Case for under 3.3 Healthcare w3c/vc-use-cases#74, by @jandrieu.
-
Establish Guardianship of minor in Traveler Use Case w3c/vc-use-cases#71, by @stonematt.
-
-
2 issues closed.
-
Establish Guardianship of minor in Traveler Use Case w3c/vc-use-cases#71.
-
Typos in 3.1 Finance, L.4 Refugee crisis w3c/vc-use-cases#56.
-
-
3 issues received 9 new comments.
-
Establish Guardianship of minor in Traveler Use Case w3c/vc-use-cases#71 (6 comments by @stonematt, @TzviyaSiegman)
-
-
2 pull requests opened.
-
Update Traveler Use Case w3c/vc-use-cases#73, by @stonematt.
-
Fix typo for issue #56 w3c/vc-use-cases#72, by @stonematt.
-
-
3 pull requests merged.
-
Update Traveler Use Case w3c/vc-use-cases#73.
-
Fix typo for issue #56 w3c/vc-use-cases#72.
-
Reformat credential list in Focal Use Cases w3c/vc-use-cases#70.
-
-
2 pull requests received 5 new comments.
-
Reformat credential list in Focal Use Cases w3c/vc-use-cases#70 (4 comments by @stonematt, @TzviyaSiegman)
-
w3c/vc-data-integrity
-
1 issue received 1 new comment.
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18 (1 comment by @cwebber)
-
GitHub
w3c/vc-data-model
-
8 issues opened.
-
Value of Type Property w3c/vc-data-model#183, by @David-Chadwick.
-
Are CredentialStatus, TermsOfUse, and Evidence useful types? w3c/vc-data-model#182, by @msporny.
-
Verifiable Claims --> Verifiable Credentials w3c/vc-data-model#181, by @petrsnm.
-
Disputed credential section is confusing w3c/vc-data-model#180, by @dlongley.
-
Credentials Must always be Verifiable w3c/vc-data-model#178, by @David-Chadwick.
-
May 2018 - Review comments from Allen Brown w3c/vc-data-model#175, by @msporny.
-
Various questions related to the use of the "type" property w3c/vc-data-model#174, by @vieillevigne.
-
Remove MUST/SHOULDs from Ecosystem explanation w3c/vc-data-model#168, by @msporny.
-
-
5 issues closed.
-
Change VerifiableProfile to VerifiablePresentation w3c/vc-data-model#163.
-
Need section on binding of profile to current user w3c/vc-data-model#148.
-
Add "criticalProperty" field w3c/vc-data-model#158.
-
Remove MUST/SHOULDs from Ecosystem explanation w3c/vc-data-model#168.
-
Claim and attestation as two separate concepts w3c/vc-data-model#98.
-
-
1 issue reopened.
-
May 2018 - Review comments from Allen Brown w3c/vc-data-model#175, by @msporny.
-
-
14 issues received 95 new comments.
-
Various questions related to the use of the "type" property w3c/vc-data-model#174 (13 comments by @msporny, @vieillevigne)
-
Are CredentialStatus, TermsOfUse, and Evidence useful types? w3c/vc-data-model#182 (12 comments by @David-Chadwick, @dlongley, @msporny)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (8 comments by @Drabiv, @stonematt)
-
Add "criticalProperty" field w3c/vc-data-model#158 (7 comments by @David-Chadwick, @dlongley, @msporny, @stonematt)
-
Credentials Must always be Verifiable w3c/vc-data-model#178 (4 comments by @David-Chadwick, @msporny)
-
Verifiable Claims --> Verifiable Credentials w3c/vc-data-model#181 (2 comments by @msporny, @petrsnm)
-
Explicitly state JSON Object Types w3c/vc-data-model#123 (2 comments by @BigBlueHat, @David-Chadwick)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (1 comment by @Drabiv)
-
8 pull requests opened.
-
Responses to Allen Brown's Review Comments w3c/vc-data-model#179, by @msporny.
-
Add section on types. Related to #174. w3c/vc-data-model#177, by @msporny.
-
Improved Credential Status Scheme w3c/vc-data-model#176, by @David-Chadwick.
-
Add security section on token binding. Fixes #148. w3c/vc-data-model#173, by @msporny.
-
Removed MUST and SHOULDs from requirements. Fixes #168. w3c/vc-data-model#172, by @msporny.
-
Revise "Profile" concept to "Presentation", per F2F consensus w3c/vc-data-model#171, by @msporny.
-
Clarified Terms of Use w3c/vc-data-model#170, by @David-Chadwick.
-
Added a new section on Subject NE Holder w3c/vc-data-model#169, by @David-Chadwick.
-
-
8 pull requests merged.
-
Responses to Allen Brown's Review Comments w3c/vc-data-model#179.
-
Add section on types. Related to #174. w3c/vc-data-model#177.
-
Revise "Profile" concept to "Presentation", per F2F consensus w3c/vc-data-model#171.
-
Add security section on token binding. Fixes #148. w3c/vc-data-model#173.
-
Improved Credential Status Scheme w3c/vc-data-model#176.
-
Removed MUST and SHOULDs from requirements. Fixes #168. w3c/vc-data-model#172.
-
Improve refrences to prof lic/cert bodies in Intro and Ecosystem w3c/vc-data-model#166.
-
Modified the terms w3c/vc-data-model#167.
-
-
5 pull requests closed.
-
Fixed terms of use w3c/vc-data-model#146.
-
Fixed Credential Status Scheme w3c/vc-data-model#145.
-
Add new section on Subject.NE.Holder w3c/vc-data-model#134.
-
ADD a new section on Subject NE Holder. w3c/vc-data-model#122.
-
Modified the Terms w3c/vc-data-model#144.
-
-
16 pull requests received 159 new comments.
-
Added a new section on Subject NE Holder w3c/vc-data-model#169 (49 comments by @cwebber, @David-Chadwick, @davidlehn, @dlongley, @jandrieu, @msporny)
-
Responses to Allen Brown's Review Comments w3c/vc-data-model#179 (36 comments by @David-Chadwick, @dlongley, @msporny)
-
Clarified Terms of Use w3c/vc-data-model#170 (25 comments by @burnburn, @David-Chadwick, @davidlehn, @msporny, @stonematt)
-
Add section on types. Related to #174. w3c/vc-data-model#177 (16 comments by @David-Chadwick, @davidlehn, @dlongley, @msporny)
-
Removed MUST and SHOULDs from requirements. Fixes #168. w3c/vc-data-model#172 (6 comments by @cwebber, @David-Chadwick, @dlongley, @msporny, @stonematt)
-
Fixed Credential Status Scheme w3c/vc-data-model#145 (5 comments by @burnburn, @David-Chadwick, @dlongley, @msporny)
-
Revise "Profile" concept to "Presentation", per F2F consensus w3c/vc-data-model#171 (4 comments by @David-Chadwick, @msporny, @stonematt)
-
Add a section on extensibility to the specification. w3c/vc-data-model#159 (2 comments by @David-Chadwick)
-
Improve refrences to prof lic/cert bodies in Intro and Ecosystem w3c/vc-data-model#166 (1 comment by @msporny)
-
w3c/vc-use-cases
-
3 issues opened.
-
Consistency of 5.1 v 5.2 w3c/vc-use-cases#57, by @lwolberg.
-
Typos in 3.1 Finance, L.4 Refugee crisis w3c/vc-use-cases#56, by @lwolberg.
-
github.io link incorrect w3c/vc-use-cases#55, by @stonematt.
-
-
2 issues closed.
-
URL in github needs updating w3c/vc-use-cases#47.
-
github.io link incorrect w3c/vc-use-cases#55.
-
-
4 issues received 5 new comments.
-
13 pull requests opened.
-
Reformat credential list in Focal Use Cases w3c/vc-use-cases#70, by @stonematt.
-
Reformat VC list in Citizenship Focal Use Case w3c/vc-use-cases#69, by @stonematt.
-
Update threats in traveler use case w3c/vc-use-cases#68, by @stonematt.
-
Move subject != holder to distinction section w3c/vc-use-cases#67, by @stonematt.
-
editorial: line wrap at 100char w3c/vc-use-cases#66, by @stonematt.
-
Add Focal Use Case: Traveler w/ Minor w3c/vc-use-cases#65, by @stonematt.
-
Fix reSpec w3c/vc-use-cases#64, by @stonematt.
-
Add Citizenship Focal Use Case w3c/vc-use-cases#63, by @stonematt.
-
Move Stone and Siegman from author to editor w3c/vc-use-cases#62, by @stonematt.
-
move JoeA to editor w3c/vc-use-cases#61, by @stonematt.
-
update chair list w3c/vc-use-cases#60, by @stonematt.
-
update Joe Andrieu company w3c/vc-use-cases#59, by @stonematt.
-
Focal uc structure w3c/vc-use-cases#58, by @stonematt.
-
-
11 pull requests merged.
-
Update threats in traveler use case w3c/vc-use-cases#68.
-
Move subject != holder to distinction section w3c/vc-use-cases#67.
-
editorial: line wrap at 100char w3c/vc-use-cases#66.
-
Add Focal Use Case: Traveler w/ Minor w3c/vc-use-cases#65.
-
Fix reSpec w3c/vc-use-cases#64.
-
Add Citizenship Focal Use Case w3c/vc-use-cases#63.
-
Move Stone and Siegman from author to editor w3c/vc-use-cases#62.
-
move JoeA to editor w3c/vc-use-cases#61.
-
update Joe Andrieu company w3c/vc-use-cases#59.
-
update chair list w3c/vc-use-cases#60.
-
Focal uc structure w3c/vc-use-cases#58.
-
-
2 pull requests closed.
-
Reformat VC list in Citizenship Focal Use Case w3c/vc-use-cases#69.
-
Sec4.2 social authority freedonia w3c/vc-use-cases#17.
-
-
1 pull request reopened.
-
Move Stone and Siegman from author to editor w3c/vc-use-cases#62, by @stonematt.
-
-
7 pull requests received 11 new comments.
-
Move Stone and Siegman from author to editor w3c/vc-use-cases#62 (4 comments by @jandrieu, @stonematt)
-
w3c/vc-use-cases#17 (1 comment by @stonematt)
-
Participants
-
1 participant joined.
-
Allen Brown (W3C Invited Experts) joined.
-
-
3 organizations joined.
-
WU (Wirschaftsuniversität Wien) - Vienna University of Economics and Business joined.
-
Deutsche Telekom AG joined.
-
Best Innovation Group joined.
-
GitHub
w3c/vc-data-model
-
7 issues opened.
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164, by @stonematt.
-
Change VerifiableProfile to VerifiablePresentation w3c/vc-data-model#163, by @msporny.
-
Determine how/if WebAuthn will work with VCs w3c/vc-data-model#162, by @dlongley.
-
VC test suite requirements document w3c/vc-data-model#161, by @cwebber.
-
Add "criticalProperty" field w3c/vc-data-model#158, by @msporny.
-
Will extensibility lead to vulnerability? w3c/vc-data-model#157, by @burnburn.
-
Add section on extensibility w3c/vc-data-model#156, by @jandrieu.
-
-
15 issues closed.
-
VC test suite requirements document w3c/vc-data-model#161.
-
Trust Model w3c/vc-data-model#110.
-
Add Extensibility section to specification w3c/vc-data-model#143.
-
Add DO_NOT_CORRELATE flag to Verifiable Claims w3c/vc-data-model#41.
-
Should spec include WebIDL and XML expressions w3c/vc-data-model#54.
-
Dispute Resolution w3c/vc-data-model#111.
-
Ability to add images in verifiable claims w3c/vc-data-model#97.
-
VC Identity owner impersonation w3c/vc-data-model#115.
-
Property name for bunding credentials in a profile? w3c/vc-data-model#103.
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118.
-
Add section on extensibility w3c/vc-data-model#156.
-
Update/mint new JSON-LD context w3c/vc-data-model#127.
-
Privacy: Retention times w3c/vc-data-model#124.
-
Multiple subjects in a single credential w3c/vc-data-model#55.
-
What would a counter-signed RWoT claim look like? w3c/vc-data-model#60.
-
-
25 issues received 70 new comments.
-
Add "criticalProperty" field w3c/vc-data-model#158 (20 comments by @burnburn, @David-Chadwick, @dlongley, @msporny)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (11 comments by @David-Chadwick, @Drabiv)
-
Need section on binding of profile to current user w3c/vc-data-model#148 (5 comments by @David-Chadwick, @dlongley, @msporny, @prowley)
-
How to know who specified the Terms of Use w3c/vc-data-model#109 (4 comments by @David-Chadwick, @stonematt)
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72 (4 comments by @cwebber, @David-Chadwick)
-
Is Verifiable Credentials sufficiently different from Verifiable Claims? w3c/vc-data-model#112 (2 comments by @msporny, @trbouma)
-
Add Extensibility section to specification w3c/vc-data-model#143 (2 comments by @David-Chadwick, @msporny)
-
w3c/vc-data-model#32 (1 comment by @kimdhamilton)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @kimdhamilton)
-
Need to restrict top level data types to those specified in the standard w3c/vc-data-model#149 (1 comment by @David-Chadwick)
-
Issuers may express a Time to Live on the credential w3c/vc-data-model#164 (1 comment by @David-Chadwick)
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials. w3c/vc-data-model#128 (1 comment by @David-Chadwick)
-
Add canonical way to reference JSON Schema against which credential should be validated w3c/vc-data-model#129 (1 comment by @David-Chadwick)
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118 (1 comment by @msporny)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (1 comment by @stonematt)
-
-
11 pull requests opened.
-
Modified the terms w3c/vc-data-model#167, by @David-Chadwick.
-
Improve refrences to prof lic/cert bodies in Intro and Ecosystem w3c/vc-data-model#166, by @stonematt.
-
Add link to DM Test Cases w3c/vc-data-model#165, by @stonematt.
-
Add text discussing multiple subjects in a credential. w3c/vc-data-model#160, by @msporny.
-
Add a section on extensibility to the specification. w3c/vc-data-model#159, by @msporny.
-
Add proofPurpose requirement to spec. Fixes #103. w3c/vc-data-model#155, by @msporny.
-
Change termsOfUse examples based on feedback from @rianella. Fixes #41. w3c/vc-data-model#154, by @msporny.
-
Remove all vestiges of WebIDL. Fixes #54. w3c/vc-data-model#153, by @msporny.
-
Add section for Disputes. Fixes #111. w3c/vc-data-model#152, by @msporny.
-
Add a non-normative example of how to embed images. Fixes #97. w3c/vc-data-model#151, by @msporny.
-
Add section on device theft and impersonation. Fixes #115. w3c/vc-data-model#150, by @msporny.
-
-
14 pull requests merged.
-
Add link to DM Test Cases w3c/vc-data-model#165.
-
Fixed Evidence w3c/vc-data-model#147.
-
Add section on Trust Model to the specification. w3c/vc-data-model#131.
-
Add a section on extensibility to the specification. w3c/vc-data-model#159.
-
Change termsOfUse examples based on feedback from @rianella. Fixes #41. w3c/vc-data-model#154.
-
Remove all vestiges of WebIDL. Fixes #54. w3c/vc-data-model#153.
-
Add section for Disputes. Fixes #111. w3c/vc-data-model#152.
-
Add a non-normative example of how to embed images. Fixes #97. w3c/vc-data-model#151.
-
Add section on device theft and impersonation. Fixes #115. w3c/vc-data-model#150.
-
Add proofPurpose requirement to spec. Fixes #103. w3c/vc-data-model#155.
-
Update vocabulary based on changes to data model document. w3c/vc-data-model#138.
-
Enable embedded JSON-LD for SEO w3c/vc-data-model#140.
-
Add data retention limit example. Fixes #124. w3c/vc-data-model#132.
-
Clarify that credentials and profiles can be multi-subject. w3c/vc-data-model#121.
-
-
2 pull requests closed.
-
Add text discussing multiple subjects in a credential. w3c/vc-data-model#160.
-
Modified data model and terms to remove ambiguity w3c/vc-data-model#141.
-
-
14 pull requests received 47 new comments.
-
Add a section on extensibility to the specification. w3c/vc-data-model#159 (14 comments by @David-Chadwick, @dlongley, @jandrieu, @msporny, @waywardmonkeys)
-
Add proofPurpose requirement to spec. Fixes #103. w3c/vc-data-model#155 (4 comments by @msporny, @nage)
-
Modified data model and terms to remove ambiguity w3c/vc-data-model#141 (3 comments by @David-Chadwick, @msporny)
-
Add section for Disputes. Fixes #111. w3c/vc-data-model#152 (2 comments by @David-Chadwick, @msporny)
-
Add a non-normative example of how to embed images. Fixes #97. w3c/vc-data-model#151 (2 comments by @David-Chadwick, @msporny)
-
Clarify that credentials and profiles can be multi-subject. w3c/vc-data-model#121 (2 comments by @msporny)
-
Add section on device theft and impersonation. Fixes #115. w3c/vc-data-model#150 (1 comment by @David-Chadwick)
-
Participants
-
1 organization joined.
-
Consensys joined.
-
GitHub
w3c/vc-data-model
-
16 issues opened.
-
Need to restrict top level data types to those specified in the standard w3c/vc-data-model#149, by @David-Chadwick.
-
Need section on binding of profile to current user w3c/vc-data-model#148, by @jandrieu.
-
Add Extensibility section to specification w3c/vc-data-model#143, by @msporny.
-
How are verifiable credentials updated w3c/vc-data-model#139, by @r-soltani.
-
Broken reference to LD-PROOFS w3c/vc-data-model#137, by @rogargon.
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136, by @Drabiv.
-
Reference or attach credential in another credentials w3c/vc-data-model#135, by @Drabiv.
-
Profile ID is ambiguous and potentially improper w3c/vc-data-model#133, by @jandrieu.
-
Add "revocationAuthority" property w3c/vc-data-model#130, by @Drabiv.
-
Add canonical way to reference JSON Schema against which credential should be validated w3c/vc-data-model#129, by @Drabiv.
-
Add standard (generic) JSON Schema for implementors to validate their verifiable credentials. w3c/vc-data-model#128, by @Drabiv.
-
Update/mint new JSON-LD context w3c/vc-data-model#127, by @dlongley.
-
Reference and Attachment properties - add a clear way to reference and attach data into credentials w3c/vc-data-model#126, by @Drabiv.
-
Privacy: Anonymous credentials w3c/vc-data-model#125, by @rigow.
-
Privacy: Retention times w3c/vc-data-model#124, by @rigow.
-
Explicitly state JSON Object Types w3c/vc-data-model#123, by @David-Chadwick.
-
-
10 issues closed.
-
Are JWTs appropriate for Verifiable Claims? w3c/vc-data-model#26.
-
Linked Data in JWTs w3c/vc-data-model#3.
-
Composing JWT documents w3c/vc-data-model#2.
-
Nesting Signatures with JWT w3c/vc-data-model#1.
-
DID Documents as self-signed Verifiable Claims w3c/vc-data-model#61.
-
Add section/language about presentation of claims w3c/vc-data-model#46.
-
Add "revocationAuthority" property w3c/vc-data-model#130.
-
How do new claims and their signatures get generated from a collection of existing VCs w3c/vc-data-model#119.
-
Is Verifiable Credentials sufficiently different from Verifiable Claims? w3c/vc-data-model#112.
-
[admin] Add PR Preview | Diff links w3c/vc-data-model#117.
-
-
2 issues reopened.
-
Reference and Attachment properties - add a clear way to reference and attach data into credentials w3c/vc-data-model#126, by @Drabiv.
-
Add "revocationAuthority" property w3c/vc-data-model#130, by @Drabiv.
-
-
31 issues received 118 new comments.
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118 (23 comments by @ChristopherA, @cwebber, @dlongley, @Drabiv, @jandrieu)
-
Property name for bunding credentials in a profile? w3c/vc-data-model#103 (10 comments by @agropper, @ChristopherA, @dlongley, @jandrieu, @msporny, @stonematt)
-
Reference or attach generic (not-credential) data in credential w3c/vc-data-model#136 (9 comments by @agropper, @dlongley, @Drabiv, @msporny, @stonematt)
-
Profile ID is ambiguous and potentially improper w3c/vc-data-model#133 (6 comments by @coderintherye, @David-Chadwick, @dlongley, @gkellogg)
-
Reference and Attachment properties - add a clear way to reference and attach data into credentials w3c/vc-data-model#126 (6 comments by @dlongley, @Drabiv)
-
Privacy: Anonymous credentials w3c/vc-data-model#125 (5 comments by @David-Chadwick, @dlongley, @liamquin, @msporny)
-
Ability to add images in verifiable claims w3c/vc-data-model#97 (4 comments by @David-Chadwick, @msporny, @r-soltani)
-
Need section on binding of profile to current user w3c/vc-data-model#148 (3 comments by @David-Chadwick, @dlongley)
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72 (3 comments by @cwebber, @David-Chadwick, @msporny)
-
What would a counter-signed RWoT claim look like? w3c/vc-data-model#60 (2 comments by @burnburn, @kimdhamilton)
-
Claim and attestation as two separate concepts w3c/vc-data-model#98 (2 comments by @David-Chadwick, @dlongley)
-
Is Verifiable Credentials sufficiently different from Verifiable Claims? w3c/vc-data-model#112 (2 comments by @burnburn, @msporny)
-
Reference or attach credential in another credentials w3c/vc-data-model#135 (1 comment by @dlongley)
-
w3c/vc-data-model#19 (1 comment by @stonematt)
-
Ideas for roles to add to the data model for next draft w3c/vc-data-model#57 (1 comment by @burnburn)
-
Unstated expectations and assumptions about subject-holder relationships w3c/vc-data-model#68 (1 comment by @burnburn)
-
-
11 pull requests opened.
-
Fixed Evidence w3c/vc-data-model#147, by @David-Chadwick.
-
Fixed terms of use w3c/vc-data-model#146, by @David-Chadwick.
-
Fixed Credential Status Scheme w3c/vc-data-model#145, by @David-Chadwick.
-
Modified the Terms w3c/vc-data-model#144, by @David-Chadwick.
-
Add .gitignore. w3c/vc-data-model#142, by @davidlehn.
-
Modified data model and terms to remove ambiguity w3c/vc-data-model#141, by @David-Chadwick.
-
Enable embedded JSON-LD for SEO w3c/vc-data-model#140, by @gkellogg.
-
Update vocabulary based on changes to data model document. w3c/vc-data-model#138, by @gkellogg.
-
Add new section on Subject.NE.Holder w3c/vc-data-model#134, by @David-Chadwick.
-
Add data retention limit example. Fixes #124. w3c/vc-data-model#132, by @msporny.
-
Add section on Trust Model to the specification. w3c/vc-data-model#131, by @msporny.
-
-
1 pull request merged.
-
Add .gitignore. w3c/vc-data-model#142.
-
-
7 pull requests received 81 new comments.
-
Modified data model and terms to remove ambiguity w3c/vc-data-model#141 (61 comments by @BigBlueHat, @David-Chadwick, @dlongley, @jandrieu, @msporny)
-
Update vocabulary based on changes to data model document. w3c/vc-data-model#138 (8 comments by @David-Chadwick, @dlongley, @gkellogg)
-
Add new section on Subject.NE.Holder w3c/vc-data-model#134 (4 comments by @David-Chadwick, @davidlehn, @msporny)
-
ADD a new section on Subject NE Holder. w3c/vc-data-model#122 (3 comments by @David-Chadwick, @davidlehn, @jandrieu)
-
Add section on Trust Model to the specification. w3c/vc-data-model#131 (3 comments by @David-Chadwick, @msporny)
-
w3c/vc-data-integrity
-
1 issue opened.
-
Example that demonstrates input(s) and what gets fed to the signature algorithms? w3c/vc-data-integrity#19, by @waywardmonkeys.
-
Participants
-
1 organization joined.
-
Know Your Customer Limited joined.
-
GitHub
w3c/vc-data-model
-
15 issues opened.
-
IDs Not Differentiated Sufficiently w3c/vc-data-model#120, by @David-Chadwick.
-
How do new claims and their signatures get generated from a collection of existing VCs w3c/vc-data-model#119, by @r-soltani.
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118, by @ChristopherA.
-
[admin] Add PR Preview | Diff links w3c/vc-data-model#117, by @BigBlueHat.
-
Expiration of one-time VC votes submission w3c/vc-data-model#116, by @r-soltani.
-
VC Identity owner impersonation w3c/vc-data-model#115, by @r-soltani.
-
Identifier Registry vs Claims Registry w3c/vc-data-model#114, by @alexandermuehle.
-
Is Verifiable Credentials sufficiently different from Verifiable Claims? w3c/vc-data-model#112, by @trbouma.
-
Dispute Resolution w3c/vc-data-model#111, by @David-Chadwick.
-
Trust Model w3c/vc-data-model#110, by @David-Chadwick.
-
How to know who specified the Terms of Use w3c/vc-data-model#109, by @David-Chadwick.
-
Typo in Example 6 w3c/vc-data-model#108, by @David-Chadwick.
-
Profiles w3c/vc-data-model#107, by @David-Chadwick.
-
Subject NE Holder w3c/vc-data-model#106, by @David-Chadwick.
-
Holders and Identifiers w3c/vc-data-model#105, by @David-Chadwick.
-
-
6 issues closed.
-
Identifier Registry vs Claims Registry w3c/vc-data-model#114.
-
Add section about terms of use w3c/vc-data-model#48.
-
Expiration of one-time VC votes submission w3c/vc-data-model#116.
-
Design choices in expressing a verifiable claim w3c/vc-data-model#30.
-
Is the WebIDL expression necessary? w3c/vc-data-model#4.
-
Unclear on antecedent of "agent" in Entity Credentials capabilities w3c/vc-data-model#24.
-
-
33 issues received 119 new comments.
-
IDs Not Differentiated Sufficiently w3c/vc-data-model#120 (30 comments by @David-Chadwick, @dlongley, @Drabiv, @Fak3, @jandrieu, @msporny)
-
Multiple subjects in a single credential w3c/vc-data-model#55 (25 comments by @David-Chadwick, @dlongley, @Drabiv, @jandrieu, @msporny, @RieksJ, @stonematt, @talltree)
-
Holders and Identifiers w3c/vc-data-model#105 (3 comments by @David-Chadwick, @dlongley, @stonematt)
-
Claim and attestation as two separate concepts w3c/vc-data-model#98 (3 comments by @alexandermuehle, @dlongley)
-
Ability to add images in verifiable claims w3c/vc-data-model#97 (2 comments by @David-Chadwick, @stonematt)
-
Data Model in Context of Keys, Signatures & Countersignatures w3c/vc-data-model#118 (2 comments by @dlongley)
-
Add Accessibility Use Case for under 3.3 Healthcare w3c/vc-data-model#50 (2 comments by @David-Chadwick, @msporny)
-
Ideas for roles to add to the data model for next draft w3c/vc-data-model#57 (1 comment by @David-Chadwick)
-
Add section/language about presentation of claims w3c/vc-data-model#46 (1 comment by @David-Chadwick)
-
w3c/vc-data-model#19 (1 comment by @David-Chadwick)
-
Proposed resolution to issue about JOSE/JWT Verifiable Claims w3c/vc-data-model#93 (1 comment by @stonematt)
-
w3c/vc-data-model#32 (1 comment by @msporny)
-
w3c/vc-data-model#30 (1 comment by @msporny)
-
w3c/vc-data-model#26 (1 comment by @msporny)
-
w3c/vc-data-model#4 (1 comment by @msporny)
-
w3c/vc-data-model#3 (1 comment by @msporny)
-
w3c/vc-data-model#2 (1 comment by @msporny)
-
w3c/vc-data-model#1 (1 comment by @msporny)
-
Is Verifiable Credentials sufficiently different from Verifiable Claims? w3c/vc-data-model#112 (1 comment by @msporny)
-
How do we support delegation and attenuation of rights? w3c/vc-data-model#72 (1 comment by @David-Chadwick)
-
-
3 pull requests opened.
-
ADD a new section on Subject NE Holder. w3c/vc-data-model#122, by @David-Chadwick.
-
Clarify that credentials and profiles can be multi-subject. w3c/vc-data-model#121, by @msporny.
-
Add useful links to WG home and related repos w3c/vc-data-model#113, by @stonematt.
-
-
2 pull requests merged.
-
Add section on Verifiable Profiles to Basic Concepts w3c/vc-data-model#104.
-
Add useful links to WG home and related repos w3c/vc-data-model#113.
-
-
4 pull requests received 20 new comments.
-
ADD a new section on Subject NE Holder. w3c/vc-data-model#122 (13 comments by @burnburn, @David-Chadwick, @davidlehn, @liam, @liamquin)
-
Add section on Verifiable Profiles to Basic Concepts w3c/vc-data-model#104 (4 comments by @BigBlueHat, @David-Chadwick, @dlongley, @msporny)
-
Clarify that credentials and profiles can be multi-subject. w3c/vc-data-model#121 (2 comments by @David-Chadwick, @dlongley)
-
w3c/vc-data-integrity
-
2 issues opened.
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18, by @Drabiv.
-
Use cases for RsaSignatureAuthentication2018 / authentication suites w3c/vc-data-integrity#17, by @cwebber.
-
-
1 issue reopened.
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18, by @msporny.
-
-
2 issues received 7 new comments.
-
How order of signatures is ensured using ld-signatures? w3c/vc-data-integrity#18 (5 comments by @Drabiv, @msporny)
-
Use cases for RsaSignatureAuthentication2018 / authentication suites w3c/vc-data-integrity#17 (2 comments by @cwebber, @msporny)
-
w3c/vc-use-cases
-
1 pull request opened.
-
Create README.md w3c/vc-use-cases#54, by @stonematt.
-
-
1 pull request merged.
-
Create README.md w3c/vc-use-cases#54.
-
Participants
-
1 participant joined.
-
Sam Sugimoto (W3C) joined.
-
-
1 organization joined.
-
Centinal, LLC joined.
-
-
1 organization left.
-
Info Tech, Inc. left.
-
GitHub
w3c/vc-use-cases
-
1 issue received 1 new comment.
w3c/vc-data-model
-
1 issue opened.
-
Property name for bunding credentials in a profile? w3c/vc-data-model#103, by @msporny.
-
-
3 issues closed.
-
Define ONE concrete format for the revocation parameter w3c/vc-data-model#35.
-
Perform security and privacy assessment w3c/vc-data-model#71.
-
Expiration versus Revocation w3c/vc-data-model#58.
-
-
4 issues received 5 new comments.
-
Property name for bunding credentials in a profile? w3c/vc-data-model#103 (2 comments by @dlongley, @msporny)
-
w3c/vc-data-model#35 (1 comment by @msporny)
-
-
1 pull request opened.
-
Add section on Verifiable Profiles to Basic Concepts w3c/vc-data-model#104, by @msporny.
-
-
1 pull request received 2 new comments.
-
Add section on Verifiable Profiles to Basic Concepts w3c/vc-data-model#104 (2 comments by @dlongley)
-
w3c/vc-test-suite
-
1 issue opened.
-
Should we pass resources to issuers / verifiers? w3c/vc-test-suite#2, by @cwebber.
-
-
1 issue received 1 new comment.