Credentials Community Group - Activity in 2019
No matches.
Participants
-
5 participants joined.
-
Matt Lisle joined.
-
Hans Pongratz (Technische Universität München) joined.
-
Erica Connell (Legendary Requirements) joined.
-
Noopur Tiwari joined.
-
Joel Hartshorn joined.
-
-
1 participant left.
-
Soo-hyuk Choi left.
-
-
3 organizations joined.
-
Technische Universität München joined.
-
European Commission joined.
-
Elastos Foundation joined.
-
GitHub
w3c-ccg/community
-
3 issues opened.
-
[PROPOSED WORK ITEM] Credential Issuer and Verifier APIs w3c-ccg/community#102, by @peacekeeper.
-
Need Facilitator to help chairs through CCG Charter Update w3c-ccg/community#101, by @ChristopherA.
-
Add links and doc to how we use this repo and issues to manage the CCG w3c-ccg/community#100, by @ChristopherA.
-
-
6 issues closed.
-
Update cryptosuites to use COSE Key / COSE Signature formats. w3c-ccg/community#32.
-
[PROPOSED WORK ITEM] WebKMS w3c-ccg/community#99.
-
[PROPOSED WORK ITEM] did:key DID Method w3c-ccg/community#98.
-
Name VCWG Maintenance Mode github repo w3c-ccg/community#93.
-
ACTION: merge the two crypto-ld registries, fix links w3c-ccg/community#96.
-
Create DID Explainer for W3C Tag, Integrate into DID Primer w3c-ccg/community#38.
-
-
10 issues received 34 new comments.
-
Name VCWG Maintenance Mode github repo w3c-ccg/community#93 (8 comments by @burnburn, @kimdhamilton, @msporny)
-
[PROPOSED WORK ITEM] Credential Issuer and Verifier APIs w3c-ccg/community#102 (4 comments by @David-Chadwick, @jandrieu, @peacekeeper)
-
Future meeting (Oct 1): how to support contribution to JSON-LD contexts and supporting documentation w3c-ccg/community#88 (4 comments by @kimdhamilton, @OR13)
-
SIP not working w3c-ccg/community#87 (4 comments by @David-Chadwick, @jandrieu, @kimdhamilton, @rhiaro)
-
Need a process summary for VCWG w3c-ccg/community#94 (3 comments by @ChristopherA, @David-Chadwick, @kimdhamilton)
-
Update cryptosuites to use COSE Key / COSE Signature formats. w3c-ccg/community#32 (2 comments by @kimdhamilton, @msporny)
-
ACTION: merge the two crypto-ld registries, fix links w3c-ccg/community#96 (2 comments by @dmitrizagidulin, @kimdhamilton)
-
Create DID Explainer for W3C Tag, Integrate into DID Primer w3c-ccg/community#38 (1 comment by @kimdhamilton)
-
w3c-ccg/did-key-spec
-
1 issue opened.
-
Key Type w3c-ccg/did-key-spec#7, by @David-Chadwick.
-
-
1 issue received 3 new comments.
w3c-ccg/lds-merkle-proof-2019
-
1 issue opened.
-
Defining Blink Structure / Example Blinks w3c-ccg/lds-merkle-proof-2019#5, by @ghost.
-
-
1 issue closed.
-
Please add a readable github.io link to the repository description (appears at the top) w3c-ccg/lds-merkle-proof-2019#4.
-
-
3 issues received 5 new comments.
-
Defining Blink Structure / Example Blinks w3c-ccg/lds-merkle-proof-2019#5 (3 comments by @ghost, @msporny)
-
Please add a readable github.io link to the repository description (appears at the top) w3c-ccg/lds-merkle-proof-2019#4 (1 comment by @ghost)
-
w3c-ccg/hashlink
-
1 issue opened.
-
Misspelled reference name w3c-ccg/hashlink#10, by @shaktisinha.
-
-
1 issue received 1 new comment.
w3c-ccg/did-method-web
-
1 issue opened.
-
Add language that explicitly deters IDPs (Facebook, Google, MSFT etc.) from abusing subdomain-based IDs w3c-ccg/did-method-web#6, by @csuwildcat.
-
-
1 issue received 3 new comments.
-
Add possibility to expose multiple identities under the same domain name w3c-ccg/did-method-web#2 (3 comments by @dmitrizagidulin, @gribneau)
-
-
1 pull request opened.
-
Add support for optional full path in the method specific identifier. w3c-ccg/did-method-web#5, by @gribneau.
-
-
1 pull request closed.
-
Support multiple DIDs per domain with a parameter. w3c-ccg/did-method-web#4.
-
-
3 pull requests received 16 new comments.
-
Add support for optional full path in the method specific identifier. w3c-ccg/did-method-web#5 (14 comments by @awoie, @dmitrizagidulin, @gribneau)
-
Support multiple DIDs per domain with a parameter. w3c-ccg/did-method-web#4 (1 comment by @gribneau)
-
w3c-ccg/http-signatures
-
2 issues opened.
-
Discussion: relations with alt-svc w3c-ccg/http-signatures#98, by @ioggstream.
-
Stance on using Query String instead of Header w3c-ccg/http-signatures#97, by @JCapriotti.
-
-
1 issue received 1 new comment.
-
Stance on using Query String instead of Header w3c-ccg/http-signatures#97 (1 comment by @ioggstream)
-
w3c-ccg/zcap-spec
-
1 pull request opened.
-
Rephrase how traversing the delegation chain affects authority/delega… w3c-ccg/zcap-spec#29, by @cwebber.
-
w3c-ccg/did-primer
-
1 pull request closed.
-
Change the wording and order of paragraphs w3c-ccg/did-primer#9.
-
Participants
-
6 participants joined.
-
Sankarshan Mukhopadhyay (Dhiway Networks Pvt Ltd) joined.
-
Ramesh Thupakula joined.
-
Stuart Freeman joined.
-
Evan Tedesco joined.
-
Michael Shea joined.
-
Soo-hyuk Choi joined.
-
-
1 participant left.
-
YuWei Wu left.
-
-
8 organizations joined.
-
AIOB TECHNOSOFT PRIVATE LIMITED joined.
-
Zerion Software, |nc. joined.
-
Newfang joined.
-
Hempchain™ joined.
-
KILT Protocol joined.
-
7bulls.com Sp. z o.o. joined.
-
Total Network Service, Inc. joined.
-
SymVerse joined.
-
GitHub
w3c-ccg/did-method-web
-
1 issue opened.
-
Add possibility to expose multiple identities under the same domain name w3c-ccg/did-method-web#2, by @jloic.
-
-
1 issue received 1 new comment.
-
Add possibility to expose multiple identities under the same domain name w3c-ccg/did-method-web#2 (1 comment by @gribneau)
-
-
2 pull requests opened.
-
Support multiple DIDs per domain with a parameter. w3c-ccg/did-method-web#4, by @gribneau.
-
Fix URL of did.json w3c-ccg/did-method-web#3, by @peacekeeper.
-
w3c-ccg/lds-merkle-proof-2019
-
2 issues opened.
-
Please add a readable github.io link to the repository description (appears at the top) w3c-ccg/lds-merkle-proof-2019#4, by @Fak3.
-
Use verificationMethod/proofPurpose w3c-ccg/lds-merkle-proof-2019#2, by @ghost.
-
-
2 issues received 9 new comments.
-
Use verificationMethod/proofPurpose w3c-ccg/lds-merkle-proof-2019#2 (6 comments by @dlongley, @dsemenovsky, @ghost)
-
Update Merkle Proof LD Signature Suite w3c-ccg/lds-merkle-proof-2019#1 (3 comments by @dsemenovsky, @ghost)
-
-
1 pull request opened.
-
Use verificationMethod/proofPurpose w3c-ccg/lds-merkle-proof-2019#3, by @ghost.
-
w3c-ccg/did-key-spec
-
2 pull requests opened.
-
fix typo in index.html w3c-ccg/did-key-spec#2, by @melvincarvalho.
-
Update index.html w3c-ccg/did-key-spec#1, by @TallTed.
-
w3c-ccg/community
-
7 issues opened.
-
[PROPOSED WORK ITEM] WebKMS w3c-ccg/community#99, by @msporny.
-
[PROPOSED WORK ITEM] did:key DID Method w3c-ccg/community#98, by @msporny.
-
Need to host Schema for current JSON-LD Signatures w3c-ccg/community#97, by @ChristopherA.
-
ACTION: merge the two crypto-ld registries, fix links w3c-ccg/community#96, by @kimdhamilton.
-
VC chairs to send email about CCG to old VC-WG list, including asking for volunteers. w3c-ccg/community#95, by @kimdhamilton.
-
Need a process summary for VCWG w3c-ccg/community#94, by @kimdhamilton.
-
Name VCWG Maintenance Mode github repo w3c-ccg/community#93, by @kimdhamilton.
-
-
5 issues closed.
-
LD Key Format Registry administrivia w3c-ccg/community#56.
-
Invite Adrian to present storage MVP work w3c-ccg/community#92.
-
Discuss knowledge transfer / onboarding opportunities w3c-ccg/community#73.
-
[PROPOSED WORK ITEM] Verifiable Credentials JSON Schemas Specification w3c-ccg/community#91.
-
Tracking of VC Maintenance Charter w3c-ccg/community#90.
-
-
11 issues received 29 new comments.
-
Future meeting (Oct 1): how to support contribution to JSON-LD contexts and supporting documentation w3c-ccg/community#88 (16 comments by @David-Chadwick, @kimdhamilton, @msporny, @OR13)
-
[PROPOSED WORK ITEM] Verifiable Credentials JSON Schemas Specification w3c-ccg/community#91 (2 comments by @jricher, @kimdhamilton)
-
Need to host Schema for current JSON-LD Signatures w3c-ccg/community#97 (1 comment by @ChristopherA)
-
ACTION: merge the two crypto-ld registries, fix links w3c-ccg/community#96 (1 comment by @kimdhamilton)
-
Discuss knowledge transfer / onboarding opportunities w3c-ccg/community#73 (1 comment by @kimdhamilton)
-
Create DID Explainer for W3C Tag, Integrate into DID Primer w3c-ccg/community#38 (1 comment by @jandrieu)
-
w3c-ccg/http-signatures
-
4 issues opened.
-
HTTP-Signatures discussed at IETF106 w3c-ccg/http-signatures#96, by @bblfish.
-
Delimit Signature Header Parameters With Semi-colon w3c-ccg/http-signatures#95, by @bdenton.
-
Algorithm signature parameter is too complex w3c-ccg/http-signatures#94, by @msporny.
-
:path pseudo header encoding w3c-ccg/http-signatures#93, by @msporny.
-
-
3 issues received 5 new comments.
w3c-ccg/credential-handler-api
-
1 pull request opened.
-
Add 1.0 version to the spec name. w3c-ccg/credential-handler-api#9, by @dmitrizagidulin.
-
-
1 pull request merged.
-
Add 1.0 version to the spec name. w3c-ccg/credential-handler-api#9.
-
Participants
-
12 participants joined.
-
Sid Sharma joined.
-
Steve Magennis joined.
-
Raullen Chai joined.
-
Bruno Fernandes joined.
-
Jan Christoph Ebersbach (Jan Christoph Ebersbach IT Consulting) joined.
-
Hongbin Mao joined.
-
Benny Jung joined.
-
Bernardus Kurnia joined.
-
Darren Cavell joined.
-
Yancy Ribbens joined.
-
Benedikt Olek joined.
-
Adrian Seni joined.
-
-
1 participant left.
-
Benny Jung left.
-
-
1 organization joined.
-
Devise Futures, Lda. joined.
-
-
2 organizations left.
-
Learning Machine left.
-
Bespoke Engineering left.
-
GitHub
w3c-ccg/http-signatures
-
4 issues closed.
-
Project stance on signatures incorporating external data w3c-ccg/http-signatures#91.
-
Project stance on signature & parameter negotiation w3c-ccg/http-signatures#90.
-
Project stance on multiple header instances w3c-ccg/http-signatures#89.
-
Don't trust ambiguous parameters w3c-ccg/http-signatures#63.
-
-
4 issues received 6 new comments.
-
Project stance on signatures incorporating external data w3c-ccg/http-signatures#91 (3 comments by @ioggstream, @liamdennehy)
-
Project stance on signature & parameter negotiation w3c-ccg/http-signatures#90 (1 comment by @liamdennehy)
-
Gather implementations for HTTP Signatures spec for IETF standardization push w3c-ccg/http-signatures#1 (1 comment by @azdagron)
-
-
2 pull requests merged.
-
Correct typos & Documentation of the algorithm parameter w3c-ccg/http-signatures#60.
-
Fix: #63. forbid erroneously duplicate parameters w3c-ccg/http-signatures#65.
-
-
3 pull requests received 21 new comments.
-
Project Principles, Readme & Contributing w3c-ccg/http-signatures#87 (15 comments by @ioggstream, @liamdennehy)
-
Fix: #63. forbid erroneously duplicate parameters w3c-ccg/http-signatures#65 (4 comments by @dlongley, @ioggstream, @liamdennehy)
-
Fix: #75. Reference representation data, not message body. w3c-ccg/http-signatures#76 (2 comments by @ioggstream, @liamdennehy)
-
w3c-ccg/community
-
4 issues opened.
-
Invite Adrian to present storage MVP work w3c-ccg/community#92, by @kimdhamilton.
-
[PROPOSED WORK ITEM] Verifiable Credentials JSON Schemas Specification w3c-ccg/community#91, by @thereisnogabe.
-
Tracking of VC Maintenance Charter w3c-ccg/community#90, by @kimdhamilton.
-
Future Meeting (10/22): Workday Credential Schemas Specification Draft w3c-ccg/community#89, by @kimdhamilton.
-
-
5 issues closed.
-
[PROPOSED WORK ITEM] Verifiable Credentials Extension Registry w3c-ccg/community#72.
-
Future Meeting (10/22): Workday Credential Schemas Specification Draft w3c-ccg/community#89.
-
Complete update to Veres One DID Method spec w3c-ccg/community#4.
-
Ryan Grant send a request for DID document test cases etc to the list w3c-ccg/community#25.
-
Should we discuss roadmap on an ongoing basis during calls? w3c-ccg/community#70.
-
-
8 issues received 24 new comments.
-
Future meeting (Oct 1): how to support contribution to JSON-LD contexts and supporting documentation w3c-ccg/community#88 (6 comments by @David-Chadwick, @kimdhamilton, @msporny, @OR13)
-
[PROPOSED WORK ITEM] Verifiable Credentials JSON Schemas Specification w3c-ccg/community#91 (3 comments by @David-Chadwick, @kimdhamilton, @ottonomy)
-
[PROPOSED WORK ITEM] Verifiable Credentials Extension Registry w3c-ccg/community#72 (3 comments by @kimdhamilton, @msporny)
-
Complete update to Veres One DID Method spec w3c-ccg/community#4 (3 comments by @kimdhamilton, @msporny)
-
Create DID Explainer for W3C Tag, Integrate into DID Primer w3c-ccg/community#38 (2 comments by @ChristopherA, @kimdhamilton)
-
Ryan Grant send a request for DID document test cases etc to the list w3c-ccg/community#25 (2 comments by @kimdhamilton)
-
Should we discuss roadmap on an ongoing basis during calls? w3c-ccg/community#70 (1 comment by @kimdhamilton)
-
w3c-ccg/lds-merkle-proof-2019
-
1 issue reopened.
-
Update Merkle Proof LD Signature Suite w3c-ccg/lds-merkle-proof-2019#1, by @kimdhamilton.
-
-
1 issue received 18 new comments.
-
Update Merkle Proof LD Signature Suite w3c-ccg/lds-merkle-proof-2019#1 (18 comments by @ChristopherA, @dsemenovsky, @ghost, @kimdhamilton, @msporny)
-
w3c-ccg/lds-ecdsa-secp256k1-2019
-
1 pull request merged.
-
Update Spec w3c-ccg/lds-ecdsa-secp256k1-2019#2.
-
Reports
-
1 report published.
-
Decentralized Identifiers (DIDs) v0.13 Data Model and Syntaxes published as a final report.
-
Participants
-
7 participants joined.
-
David Wilde joined.
-
Andrew Baxter (Tandem Technology Solutions Ltd) joined.
-
Kayode Ezike (Gobekli Inc) joined.
-
Christopher Allen joined.
-
Matt Pasiewicz joined.
-
Egidio Casati joined.
-
Kengo Suzuki joined.
-
-
3 participants left.
-
Kyle Den Hartog (Mattr Limited) left.
-
Dan Cowell left.
-
Kayode Ezike (Gobekli Inc) left.
-
-
7 organizations joined.
-
Blockchain-4SG Ltd. joined.
-
The Fifth9 Ltd joined.
-
Universities Admissions Centre joined.
-
Province of British Columbia joined.
-
Learning Machine joined.
-
Winding Tree Stiftung joined.
-
Department for Work and Pensions joined.
-
-
3 organizations left.
-
AKASHA Foundation left.
-
The Fifth9 Ltd left.
-
DXC Technology left.
-
GitHub
w3c-ccg/lds-ecdsa-secp256k1-2019
-
1 issue received 4 new comments.
-
1 pull request received 4 new comments.
w3c-ccg/did-method-web
-
1 pull request opened.
-
Expand Security and Privacy Considerations section. w3c-ccg/did-method-web#1, by @dmitrizagidulin.
-
-
1 pull request merged.
-
Expand Security and Privacy Considerations section. w3c-ccg/did-method-web#1.
-
w3c-ccg/http-signatures
-
1 issue opened.
-
HTTP Signatures for Solid w3c-ccg/http-signatures#92, by @bblfish.
-
-
1 issue closed.
-
relation to RDFAuth w3c-ccg/http-signatures#12.
-
-
3 issues received 8 new comments.
-
HTTP Signatures for Solid w3c-ccg/http-signatures#92 (4 comments by @bblfish, @dlongley, @liamdennehy)
-
Difference between Authorization and Signature not clear w3c-ccg/http-signatures#13 (1 comment by @bblfish)
-
w3c-ccg/community
-
1 issue opened.
-
1 issue received 1 new comment.
w3c-ccg/didm-btcr
-
1 issue opened.
-
Recommended updates from RWOT9 w3c-ccg/didm-btcr#21, by @kimdhamilton.
-
w3c-ccg/http-signatures-test-suite
-
2 pull requests merged.
-
Initial w3c-ccg/http-signatures-test-suite#7.
-
Remove unused messages w3c-ccg/http-signatures-test-suite#23.
-
-
1 pull request received 1 new comment.
w3c-ccg/did-primer
-
1 issue received 1 new comment.
-
1 pull request opened.
-
Update VC Primer reference w3c-ccg/did-primer#11, by @iherman.
-
Participants
-
3 participants joined.
-
Serge Wroclawski joined.
-
Joe Andrieu (Legendary Requirements) joined.
-
Satish Mohan joined.
-
-
1 participant left.
-
Dominik Tomaszuk left.
-
-
3 organizations joined.
-
Danube Tech GmbH joined.
-
中钞区块链技术研究院 joined.
-
Workday joined.
-
-
5 organizations left.
-
SC PULSARDEV SRL left.
-
Danube Tech left.
-
GS1-US left.
-
中钞区块链技术研究院 left.
-
Qollaboration, Inc. left.
-
GitHub
w3c-ccg/http-signatures
-
8 issues opened.
-
Project stance on signatures incorporating external data w3c-ccg/http-signatures#91, by @liamdennehy.
-
Project stance on signature & parameter negotiation w3c-ccg/http-signatures#90, by @liamdennehy.
-
Project stance on multiple header instances w3c-ccg/http-signatures#89, by @liamdennehy.
-
Project stance on backwards compatibility w3c-ccg/http-signatures#88, by @liamdennehy.
-
Implementation should throw if it would overwrite an Existing Authorization or Signature Header. w3c-ccg/http-signatures#85, by @aljones15.
-
Forbid "(request-target)" in response signature w3c-ccg/http-signatures#82, by @liamdennehy.
-
Proposal to Drop Normative Statements the depend on HTTP Message Parser behavior. w3c-ccg/http-signatures#81, by @aljones15.
-
Consider removing the `headers` field to the `Signed-Headers` header field. w3c-ccg/http-signatures#80, by @ioggstream.
-
-
12 issues closed.
-
Clarification on ECDSA signatures w3c-ccg/http-signatures#30.
-
Better Reference Tests w3c-ccg/http-signatures#43.
-
Server should not trust client header w3c-ccg/http-signatures#39.
-
Use case: server signing other content w3c-ccg/http-signatures#22.
-
Wrong section referenced for auth-param w3c-ccg/http-signatures#17.
-
relation to Secondary Certificate Authentication in HTTP/2 spec w3c-ccg/http-signatures#10.
-
Broken references in Feedback section w3c-ccg/http-signatures#15.
-
Proposal to Drop Normative Statements the depend on HTTP Message Parser behavior. w3c-ccg/http-signatures#81.
-
PROPOSAL: move index.xml to index.md w3c-ccg/http-signatures#71.
-
Omit rsa-sha1 from the Signature Algorithm Registry w3c-ccg/http-signatures#20.
-
Difference between Authorization and Signature not clear w3c-ccg/http-signatures#13.
-
header and signature parameters are confusing. w3c-ccg/http-signatures#58.
-
-
28 issues received 61 new comments.
-
Concatenation of multiple-instance headers in signing string w3c-ccg/http-signatures#50 (9 comments by @aljones15, @ioggstream, @liamdennehy)
-
Implementation should throw if it would overwrite an Existing Authorization or Signature Header. w3c-ccg/http-signatures#85 (7 comments by @ioggstream, @liamdennehy, @msporny)
-
Consider removing the `headers` field to the `Signed-Headers` header field. w3c-ccg/http-signatures#80 (5 comments by @aljones15, @ioggstream, @liamdennehy)
-
Revision 10's Extra 'algorithm' Note w3c-ccg/http-signatures#29 (4 comments by @ioggstream, @liamdennehy, @nightpool)
-
Wrong section referenced for auth-param w3c-ccg/http-signatures#17 (3 comments by @liamdennehy, @msporny)
-
Forbid "(request-target)" in response signature w3c-ccg/http-signatures#82 (3 comments by @ioggstream, @liamdennehy)
-
Describe how to use this to get origin authentication w3c-ccg/http-signatures#19 (2 comments by @ioggstream, @liamdennehy)
-
Clarification on ECDSA signatures w3c-ccg/http-signatures#30 (2 comments by @ejholmes, @liamdennehy)
-
Accept-Signature request header w3c-ccg/http-signatures#25 (2 comments by @ioggstream, @liamdennehy)
-
header and signature parameters are confusing. w3c-ccg/http-signatures#58 (2 comments by @aljones15, @liamdennehy)
-
Omit rsa-sha1 from the Signature Algorithm Registry w3c-ccg/http-signatures#20 (2 comments by @liamdennehy)
-
Difference between Authorization and Signature not clear w3c-ccg/http-signatures#13 (2 comments by @liamdennehy)
-
Signing string should include keyId and algorithm (if present) via pseudo headers w3c-ccg/http-signatures#77 (1 comment by @liamdennehy)
-
Security considerations should talk about public key distribution w3c-ccg/http-signatures#16 (1 comment by @liamdennehy)
-
relation to Secondary Certificate Authentication in HTTP/2 spec w3c-ccg/http-signatures#10 (1 comment by @liamdennehy)
-
Proposal to Drop Normative Statements the depend on HTTP Message Parser behavior. w3c-ccg/http-signatures#81 (1 comment by @aljones15)
-
Specify behaviour if client signs headers in addition to required w3c-ccg/http-signatures#6 (1 comment by @liamdennehy)
-
Specification of servers announcing allowed keyId types w3c-ccg/http-signatures#3 (1 comment by @liamdennehy)
-
Gather implementations for HTTP Signatures spec for IETF standardization push w3c-ccg/http-signatures#1 (1 comment by @msporny)
-
-
4 pull requests opened.
-
Project Principles, Readme & Contributing w3c-ccg/http-signatures#87, by @liamdennehy.
-
Building w3c-ccg/http-signatures#86, by @liamdennehy.
-
Forbid referring to zero-length header values. w3c-ccg/http-signatures#84, by @aljones15.
-
Clarify signing escaped/encoded :path parameter in signing string w3c-ccg/http-signatures#83, by @liamdennehy.
-
-
1 pull request merged.
-
Fix definition of rsa-sha256 to match previous versions w3c-ccg/http-signatures#55.
-
-
2 pull requests closed.
-
Building w3c-ccg/http-signatures#86.
-
Forbid referring to zero-length header values. w3c-ccg/http-signatures#84.
-
-
3 pull requests received 5 new comments.
-
Forbid referring to zero-length header values. w3c-ccg/http-signatures#84 (3 comments by @aljones15, @liamdennehy)
-
w3c-ccg/community
-
3 issues opened.
-
SIP not working w3c-ccg/community#87, by @ChristopherA.
-
BTCR Hackathon Report Out w3c-ccg/community#86, by @kimdhamilton.
-
Invite Wyoming Rep Mike Lin to speak on August 13 w3c-ccg/community#85, by @kimdhamilton.
-
-
6 issues closed.
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c-ccg/community#78.
-
Invite Wyoming Rep Mike Lin to speak on August 13 w3c-ccg/community#85.
-
Invite @apoelstra to speak at Crypto Tuesday about Cross-Curve DLEQ Sigma Protocol w3c-ccg/community#33.
-
Future meeting topic: chairs to schedule w3c-ccg/community#82.
-
BTCR Hackathon Report Out w3c-ccg/community#86.
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76.
-
-
7 issues received 7 new comments.
-
Discuss registries meta-process; what are next steps? w3c-ccg/community#75 (1 comment by @kimdhamilton)
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c-ccg/community#78 (1 comment by @kimdhamilton)
-
Need update from Ethereum Community on differences on various DID-based EIPs w3c-ccg/community#21 (1 comment by @ChristopherA)
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76 (1 comment by @kimdhamilton)
w3c-ccg/http-signatures-test-suite
-
8 issues opened.
-
Curate the signature algorithms in tests w3c-ccg/http-signatures-test-suite#20, by @liamdennehy.
-
Date value is impossibly huge w3c-ccg/http-signatures-test-suite#18, by @liamdennehy.
-
Don't provide 'headers` in 'verify' mode commandline w3c-ccg/http-signatures-test-suite#13, by @liamdennehy.
-
Explicit rejection mode vs simple exceptions to reduce false positives w3c-ccg/http-signatures-test-suite#12, by @liamdennehy.
-
``c14n`` as mode does not seem appropriate w3c-ccg/http-signatures-test-suite#10, by @liamdennehy.
-
Response signatures w3c-ccg/http-signatures-test-suite#9, by @liamdennehy.
-
Separate tests for Signature and Authorization headers w3c-ccg/http-signatures-test-suite#8, by @liamdennehy.
-
``npm test`` fails with JSON parse error w3c-ccg/http-signatures-test-suite#6, by @liamdennehy.
-
-
3 issues closed.
-
Date value is impossibly huge w3c-ccg/http-signatures-test-suite#18.
-
``c14n`` as mode does not seem appropriate w3c-ccg/http-signatures-test-suite#10.
-
``npm test`` fails with JSON parse error w3c-ccg/http-signatures-test-suite#6.
-
-
8 issues received 29 new comments.
-
Separate tests for Signature and Authorization headers w3c-ccg/http-signatures-test-suite#8 (13 comments by @aljones15, @liamdennehy)
-
Curate the signature algorithms in tests w3c-ccg/http-signatures-test-suite#20 (5 comments by @aljones15, @ChristopherA, @liamdennehy)
-
Date value is impossibly huge w3c-ccg/http-signatures-test-suite#18 (4 comments by @aljones15, @ChristopherA, @liamdennehy)
-
Response signatures w3c-ccg/http-signatures-test-suite#9 (3 comments by @aljones15, @detailyang, @liamdennehy)
-
Don't provide 'headers` in 'verify' mode commandline w3c-ccg/http-signatures-test-suite#13 (1 comment by @liamdennehy)
-
Explicit rejection mode vs simple exceptions to reduce false positives w3c-ccg/http-signatures-test-suite#12 (1 comment by @aljones15)
-
``c14n`` as mode does not seem appropriate w3c-ccg/http-signatures-test-suite#10 (1 comment by @aljones15)
-
``npm test`` fails with JSON parse error w3c-ccg/http-signatures-test-suite#6 (1 comment by @liamdennehy)
-
-
10 pull requests opened.
-
Remove unused messages w3c-ccg/http-signatures-test-suite#23, by @aljones15.
-
Implement add to cli interface. w3c-ccg/http-signatures-test-suite#22, by @aljones15.
-
Make key tests optional. w3c-ccg/http-signatures-test-suite#21, by @aljones15.
-
Remove 2 tests related to metadata. w3c-ccg/http-signatures-test-suite#19, by @aljones15.
-
Add message content dynamically w3c-ccg/http-signatures-test-suite#17, by @aljones15.
-
Add message body to match Content-Length and Digest values w3c-ccg/http-signatures-test-suite#16, by @liamdennehy.
-
Add ignore case test. w3c-ccg/http-signatures-test-suite#15, by @aljones15.
-
README + version dependency improvements w3c-ccg/http-signatures-test-suite#14, by @liamdennehy.
-
HTTP Signatures -> Signing HTTP Messages w3c-ccg/http-signatures-test-suite#11, by @liamdennehy.
-
Initial w3c-ccg/http-signatures-test-suite#7, by @aljones15.
-
-
8 pull requests merged.
-
Remove 2 tests related to metadata. w3c-ccg/http-signatures-test-suite#19.
-
Make key tests optional. w3c-ccg/http-signatures-test-suite#21.
-
Add message content dynamically w3c-ccg/http-signatures-test-suite#17.
-
Add message body to match Content-Length and Digest values w3c-ccg/http-signatures-test-suite#16.
-
Add ignore case test. w3c-ccg/http-signatures-test-suite#15.
-
README + version dependency improvements w3c-ccg/http-signatures-test-suite#14.
-
HTTP Signatures -> Signing HTTP Messages w3c-ccg/http-signatures-test-suite#11.
-
All tests w3c-ccg/http-signatures-test-suite#5.
-
-
1 pull request closed.
-
Initial w3c-ccg/http-signatures-test-suite#1.
-
-
8 pull requests received 33 new comments.
-
Add message content dynamically w3c-ccg/http-signatures-test-suite#17 (4 comments by @aljones15, @liamdennehy)
-
Remove unused messages w3c-ccg/http-signatures-test-suite#23 (3 comments by @aljones15, @liamdennehy)
-
Add message body to match Content-Length and Digest values w3c-ccg/http-signatures-test-suite#16 (3 comments by @aljones15, @dlongley, @liamdennehy)
-
README + version dependency improvements w3c-ccg/http-signatures-test-suite#14 (2 comments by @aljones15, @liamdennehy)
w3c-ccg/zcap-spec
-
4 issues opened.
-
Chain shortening w3c-ccg/zcap-spec#28, by @cwebber.
-
Why is signature part of of the signed blob? w3c-ccg/zcap-spec#27, by @danfinlay.
-
Add replay protection for invocations w3c-ccg/zcap-spec#26, by @danfinlay.
-
Is this spec/repo abandoned? w3c-ccg/zcap-spec#25, by @llorllale.
-
-
1 issue closed.
-
Is this spec/repo abandoned? w3c-ccg/zcap-spec#25.
-
-
3 issues received 8 new comments.
-
Add replay protection for invocations w3c-ccg/zcap-spec#26 (4 comments by @danfinlay, @dlongley, @mikelodder7)
-
Why is signature part of of the signed blob? w3c-ccg/zcap-spec#27 (2 comments by @danfinlay, @dlongley)
-
w3c-ccg/credential-handler-api
-
1 pull request opened.
-
Add IANA Considerations section. w3c-ccg/credential-handler-api#8, by @dmitrizagidulin.
-
-
1 pull request merged.
-
Add IANA Considerations section. w3c-ccg/credential-handler-api#8.
-
w3c-ccg/didm-btcr
-
1 issue opened.
-
VC issuing tool key encoding problems w3c-ccg/didm-btcr#19, by @kimdhamilton.
-
-
1 issue received 5 new comments.
-
VC issuing tool key encoding problems w3c-ccg/didm-btcr#19 (5 comments by @dmitrizagidulin, @ghost, @kimdhamilton)
-
-
1 pull request opened.
-
Update index.html w3c-ccg/didm-btcr#20, by @peacekeeper.
-
-
1 pull request merged.
-
Update index.html w3c-ccg/didm-btcr#20.
-
w3c-ccg/did-wg-charter
-
1 issue opened.
-
Issue with other deliverables listed in charter w3c-ccg/did-wg-charter#68, by @nadalin.
-
-
2 issues received 12 new comments.
-
Issue with other deliverables listed in charter w3c-ccg/did-wg-charter#68 (11 comments by @brentzundel, @ChristopherA, @csuwildcat, @jandrieu, @nadalin, @stonematt)
-
-
1 pull request closed.
-
Highlight points of complexity w3c-ccg/did-wg-charter#41.
-
-
1 pull request received 2 new comments.
w3c-ccg/lds-ecdsa-secp256k1-2019
-
1 issue received 6 new comments.
-
1 pull request opened.
-
Update Spec w3c-ccg/lds-ecdsa-secp256k1-2019#2, by @OR13.
-
-
1 pull request received 9 new comments.
w3c-ccg/multihash
-
1 pull request opened.
-
fix syntax error for embedded quotes around MH w3c-ccg/multihash#11, by @bshambaugh.
-
-
1 pull request received 3 new comments.
-
fix syntax error for embedded quotes around MH w3c-ccg/multihash#11 (3 comments by @davidlehn, @msporny)
-
w3c-ccg/security-vocab
-
1 issue opened.
-
change controller to keycontroller w3c-ccg/security-vocab#9, by @ChristopherA.
-
Participants
-
3 participants joined.
-
Thomas Herbst (evan.network) joined.
-
Andrii Tarykin joined.
-
Juan Antonio Garcia joined.
-
-
1 participant left.
-
Thomas Herbst (evan.network) left.
-
-
4 organizations joined.
-
evan.network joined.
-
SC PULSARDEV SRL joined.
-
GS1-US joined.
-
Universitat Rovira i Virgili joined.
-
GitHub
w3c-ccg/community
-
7 issues closed.
-
Add a DID web method as a work item w3c-ccg/community#65.
-
Review DID wg charter issues w3c-ccg/community#77.
-
Review DID Charter PRs and Issues w3c-ccg/community#66.
-
Book space at W3C TPAC 2019 w3c-ccg/community#67.
-
Discuss "Nonviolent Communication for W3C Working Groups" w3c-ccg/community#81.
-
Updating ABNF for DIDs w3c-ccg/community#57.
-
Work Item Repair w3c-ccg/community#45.
-
-
13 issues received 24 new comments.
-
Add a DID web method as a work item w3c-ccg/community#65 (5 comments by @awoie, @ChristopherA, @dmitrizagidulin, @TallTed)
-
LD Key Format Registry administrivia w3c-ccg/community#56 (3 comments by @ChristopherA, @dmitrizagidulin, @rhiaro)
-
Should we discuss roadmap on an ongoing basis during calls? w3c-ccg/community#70 (2 comments by @ChristopherA, @jandrieu)
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76 (2 comments by @BillBarnhill, @kimdhamilton)
-
Critical path problem with lack of JSON-LD 1.1 reference implementation w3c-ccg/community#83 (2 comments by @msporny)
-
Discuss registries meta-process; what are next steps? w3c-ccg/community#75 (1 comment by @kimdhamilton)
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c-ccg/community#78 (1 comment by @ChristopherA)
-
Discuss "Nonviolent Communication for W3C Working Groups" w3c-ccg/community#81 (1 comment by @ChristopherA)
-
-
1 pull request opened.
-
Advance DID Resolution to "Released Draft 0.1.0" w3c-ccg/community#84, by @peacekeeper.
-
-
1 pull request merged.
-
Advance DID Resolution to "Released Draft 0.1.0" w3c-ccg/community#84.
-
-
1 pull request received 6 new comments.
-
Advance DID Resolution to "Released Draft 0.1.0" w3c-ccg/community#84 (6 comments by @ChristopherA, @jandrieu, @peacekeeper)
-
w3c-ccg/hashlink
-
8 issues opened.
-
Parameter suites w3c-ccg/hashlink#9, by @davidlehn.
-
Transform algorithm w3c-ccg/hashlink#8, by @davidlehn.
-
Naming of "experimental" field. w3c-ccg/hashlink#7, by @davidlehn.
-
Refer to list of "insecure hashing functions". w3c-ccg/hashlink#6, by @davidlehn.
-
Multibase reference title is wrong. w3c-ccg/hashlink#5, by @davidlehn.
-
Support salted hashes. w3c-ccg/hashlink#4, by @davidlehn.
-
Multiple encoding rewording w3c-ccg/hashlink#3, by @davidlehn.
-
URL encoding should allow optional metadata w3c-ccg/hashlink#2, by @davidlehn.
-
-
2 issues received 2 new comments.
w3c-ccg/security-vocab
-
1 pull request opened.
-
Add terms for EcdsaSecp256 signature suites. w3c-ccg/security-vocab#8, by @mattcollier.
-
-
1 pull request merged.
-
Add terms for EcdsaSecp256 signature suites. w3c-ccg/security-vocab#8.
-
-
1 pull request received 2 new comments.
-
Add terms for EcdsaSecp256 signature suites. w3c-ccg/security-vocab#8 (2 comments by @dlongley, @mattcollier)
-
w3c-ccg/multihash
-
1 issue opened.
-
Add digest-algorithm iana considerations w3c-ccg/multihash#9, by @ioggstream.
-
-
1 pull request opened.
-
Add multihash to the available digest-algorithms. w3c-ccg/multihash#10, by @ioggstream.
-
-
1 pull request merged.
-
Add multihash to the available digest-algorithms. w3c-ccg/multihash#10.
-
-
2 pull requests received 2 new comments.
w3c-ccg/meetings
-
2 pull requests opened.
-
Converted IRC.log file and changed it to index.html w3c-ccg/meetings#11, by @SethiShivam.
-
Add materials for 2019-07-18 DID Spec and DID Resolution Spec telecon. w3c-ccg/meetings#10, by @peacekeeper.
-
-
1 pull request merged.
-
Add materials for 2019-07-18 DID Spec and DID Resolution Spec telecon. w3c-ccg/meetings#10.
-
w3c-ccg/http-signatures
-
2 issues opened.
-
Dis-entangle this spec from Digest w3c-ccg/http-signatures#79, by @ioggstream.
-
HMAC example is illustrated with headers, not *without* w3c-ccg/http-signatures#78, by @dastanza.
-
-
2 issues received 9 new comments.
-
Specify URL encoding for request-target w3c-ccg/http-signatures#26 (8 comments by @ioggstream, @liamdennehy, @MartinSchorel, @msporny)
-
HMAC example is illustrated with headers, not *without* w3c-ccg/http-signatures#78 (1 comment by @dastanza)
-
w3c-ccg/did-primer
-
1 issue opened.
-
verifiable-credentials-primer link is broken w3c-ccg/did-primer#10, by @puncsky.
-
w3c-ccg/did-wg-charter
-
8 issues opened.
-
Normative Specifications w3c-ccg/did-wg-charter#66, by @nadalin.
-
deterministic mapping w3c-ccg/did-wg-charter#65, by @nadalin.
-
DID Method Specification Requirements w3c-ccg/did-wg-charter#64, by @nadalin.
-
Decentralized Characteristics Rubric v1.0 w3c-ccg/did-wg-charter#63, by @nadalin.
-
single or multiple controllers ? w3c-ccg/did-wg-charter#61, by @nadalin.
-
Odd verbage hard to parse w3c-ccg/did-wg-charter#60, by @nadalin.
-
Clarity on Section 2.1 w3c-ccg/did-wg-charter#59, by @nadalin.
-
Test suite should be listed in deliverables w3c-ccg/did-wg-charter#55, by @jandrieu.
-
-
10 issues closed.
-
Scope w3c-ccg/did-wg-charter#21.
-
Test suite should be listed in deliverables w3c-ccg/did-wg-charter#55.
-
Normative Specifications w3c-ccg/did-wg-charter#33.
-
add link to SSI principles w3c-ccg/did-wg-charter#46.
-
Interoperability w3c-ccg/did-wg-charter#37.
-
More General Comments w3c-ccg/did-wg-charter#20.
-
Methods vs. Operations w3c-ccg/did-wg-charter#43.
-
Web Support w3c-ccg/did-wg-charter#42.
-
DID Benefits w3c-ccg/did-wg-charter#36.
-
Coordination section needs more w3c-ccg/did-wg-charter#44.
-
-
14 issues received 68 new comments.
-
Clarity on Section 2.1 w3c-ccg/did-wg-charter#59 (10 comments by @dlongley, @jandrieu, @msporny, @nadalin)
-
Decentralized Characteristics Rubric v1.0 w3c-ccg/did-wg-charter#63 (10 comments by @jandrieu, @msporny, @nadalin)
-
DID Benefits w3c-ccg/did-wg-charter#36 (8 comments by @brentzundel, @jandrieu, @msporny, @nadalin, @peacekeeper)
-
Odd verbage hard to parse w3c-ccg/did-wg-charter#60 (6 comments by @msporny, @nadalin, @TallTed, @talltree)
-
-
10 pull requests opened.
-
(editorial) tweak DID relation language w3c-ccg/did-wg-charter#67, by @TallTed.
-
(editorial) adjust "prove control" wording w3c-ccg/did-wg-charter#62, by @TallTed.
-
added section on interop. fixes #37 w3c-ccg/did-wg-charter#58, by @jandrieu.
-
added 8th scope element, to include DID Method requirements w3c-ccg/did-wg-charter#57, by @jandrieu.
-
(editorial) indentation fix w3c-ccg/did-wg-charter#56, by @TallTed.
-
Added reference to use cases' "Required Features" w3c-ccg/did-wg-charter#54, by @jandrieu.
-
Add coordination groups. Fix #44. w3c-ccg/did-wg-charter#53, by @msporny.
-
Add reference to self-sovereign identity principles. Fix #46. w3c-ccg/did-wg-charter#52, by @msporny.
-
Set clear expectations wrt. interoperability. Fix #37. w3c-ccg/did-wg-charter#51, by @msporny.
-
DIDs are not always controlled by the subject. w3c-ccg/did-wg-charter#50, by @msporny.
-
-
10 pull requests merged.
-
added 8th scope element, to include DID Method requirements w3c-ccg/did-wg-charter#57.
-
(editorial) indentation fix w3c-ccg/did-wg-charter#56.
-
Added reference to use cases' "Required Features" w3c-ccg/did-wg-charter#54.
-
Add reference to self-sovereign identity principles. Fix #46. w3c-ccg/did-wg-charter#52.
-
Set clear expectations wrt. interoperability. Fix #37. w3c-ccg/did-wg-charter#51.
-
DIDs are not always controlled by the subject. w3c-ccg/did-wg-charter#50.
-
Add coordination groups. Fix #44. w3c-ccg/did-wg-charter#53.
-
DID method implementation is out of scope w3c-ccg/did-wg-charter#32.
-
Update index.html w3c-ccg/did-wg-charter#49.
-
re-worded success criteria to explicitly mention interoperability w3c-ccg/did-wg-charter#39.
-
-
8 pull requests received 34 new comments.
-
added section on interop. fixes #37 w3c-ccg/did-wg-charter#58 (11 comments by @jandrieu, @jricher, @msporny, @talltree)
-
added 8th scope element, to include DID Method requirements w3c-ccg/did-wg-charter#57 (6 comments by @jricher, @msporny, @TallTed)
-
DIDs are not always controlled by the subject. w3c-ccg/did-wg-charter#50 (5 comments by @brentzundel, @dlongley, @msporny)
-
Highlight points of complexity w3c-ccg/did-wg-charter#41 (3 comments by @brentzundel, @jandrieu, @msporny)
-
Set clear expectations wrt. interoperability. Fix #37. w3c-ccg/did-wg-charter#51 (2 comments by @brentzundel, @msporny)
-
DID method implementation is out of scope w3c-ccg/did-wg-charter#32 (2 comments by @kimdhamilton, @msporny)
-
w3c-ccg/didm-btcr
-
1 issue received 1 new comment.
-
Remove word "continuation'; replace with "implicit"/"explicit" w3c-ccg/didm-btcr#18 (1 comment by @peacekeeper)
-
w3c-ccg/zcap-spec
-
1 issue received 2 new comments.
Participants
-
7 participants joined.
-
Shivam sethi joined.
-
YangHao Yuan joined.
-
Ting-Han Su joined.
-
YuWei Wu joined.
-
Grant Hu joined.
-
Grant Hu joined.
-
ch ci123 joined.
-
-
2 participants left.
-
Timothy Holborn left.
-
Grant Hu left.
-
-
5 organizations joined.
-
NextID Pte Ltd joined.
-
FortuneTimes Group joined.
-
National Cheng Kung University joined.
-
European Schools joined.
-
Southern Connecticut State Unbiversity joined.
-
GitHub
w3c-ccg/did-wg-charter
-
7 issues opened.
-
add link to SSI principles w3c-ccg/did-wg-charter#46, by @brentzundel.
-
Coordination section needs more w3c-ccg/did-wg-charter#44, by @brentzundel.
-
Methods vs. Operations w3c-ccg/did-wg-charter#43, by @nadalin.
-
Web Support w3c-ccg/did-wg-charter#42, by @nadalin.
-
Interoperability w3c-ccg/did-wg-charter#37, by @nadalin.
-
DID Benefits w3c-ccg/did-wg-charter#36, by @nadalin.
-
self-sovereign w3c-ccg/did-wg-charter#35, by @nadalin.
-
-
12 issues closed.
-
DID V1.0 w3c-ccg/did-wg-charter#13.
-
self-sovereign w3c-ccg/did-wg-charter#35.
-
Decentralized Identifier: "Decentralized" in working group name w3c-ccg/did-wg-charter#22.
-
General: current language precludes DIDs/methods leased from an authority w3c-ccg/did-wg-charter#16.
-
Clarify statement around VCWG coordination re Normalization and Signatures w3c-ccg/did-wg-charter#12.
-
Portability w3c-ccg/did-wg-charter#19.
-
Discovery w3c-ccg/did-wg-charter#18.
-
Authentication w3c-ccg/did-wg-charter#17.
-
Out of Scope: Access Management and Identity Management w3c-ccg/did-wg-charter#15.
-
Out of Scope: Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#14.
-
Use cases are outside of the charter w3c-ccg/did-wg-charter#9.
-
DID Resolution w3c-ccg/did-wg-charter#2.
-
-
15 issues received 29 new comments.
-
Clarify statement around VCWG coordination re Normalization and Signatures w3c-ccg/did-wg-charter#12 (6 comments by @msporny, @nadalin)
-
Out of Scope: Access Management and Identity Management w3c-ccg/did-wg-charter#15 (3 comments by @msporny, @nadalin)
-
Out of Scope: Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#14 (2 comments by @msporny, @nadalin)
-
Decentralized Identifier: "Decentralized" in working group name w3c-ccg/did-wg-charter#22 (1 comment by @msporny)
-
General: current language precludes DIDs/methods leased from an authority w3c-ccg/did-wg-charter#16 (1 comment by @msporny)
-
-
8 pull requests opened.
-
Update index.html w3c-ccg/did-wg-charter#49, by @TallTed.
-
Update index.html w3c-ccg/did-wg-charter#48, by @TallTed.
-
little grammar tweak in index.html w3c-ccg/did-wg-charter#47, by @TallTed.
-
Clarified DID to remove authentication w3c-ccg/did-wg-charter#45, by @brentzundel.
-
Highlight points of complexity w3c-ccg/did-wg-charter#41, by @brentzundel.
-
Update index.html w3c-ccg/did-wg-charter#40, by @TallTed.
-
re-worded success criteria to explicitly mention interoperability w3c-ccg/did-wg-charter#39, by @brentzundel.
-
remove term 'self-sovereign' from charter w3c-ccg/did-wg-charter#38, by @brentzundel.
-
-
8 pull requests merged.
-
Update index.html w3c-ccg/did-wg-charter#48.
-
Update index.html w3c-ccg/did-wg-charter#40.
-
Update index.html (minor, polish) w3c-ccg/did-wg-charter#31.
-
little grammar tweak in index.html w3c-ccg/did-wg-charter#47.
-
Clarified DID to remove authentication w3c-ccg/did-wg-charter#45.
-
remove term 'self-sovereign' from charter w3c-ccg/did-wg-charter#38.
-
Rubric for decentralized characteristics w3c-ccg/did-wg-charter#28.
-
clarified decentralized identifier w3c-ccg/did-wg-charter#27.
-
-
7 pull requests received 26 new comments.
-
re-worded success criteria to explicitly mention interoperability w3c-ccg/did-wg-charter#39 (3 comments by @brentzundel, @msporny, @TallTed)
-
DID method implementation is out of scope w3c-ccg/did-wg-charter#32 (2 comments by @msporny, @peacekeeper)
w3c-ccg/community
-
6 issues opened.
-
Critical path problem with lack of JSON-LD 1.1 reference implementation w3c-ccg/community#83, by @kimdhamilton.
-
Future meeting topic: chairs to schedule w3c-ccg/community#82, by @kimdhamilton.
-
Discuss "Nonviolent Communication for W3C Working Groups" w3c-ccg/community#81, by @kimdhamilton.
-
Update completed work items w3c-ccg/community#80, by @kimdhamilton.
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c-ccg/community#78, by @enuoCM.
-
Review DID wg charter issues w3c-ccg/community#77, by @kimdhamilton.
-
-
6 issues closed.
-
Update completed work items w3c-ccg/community#80.
-
address requests for clarity on correlation and privacy claims of DIDs w3c-ccg/community#44.
-
look at security model or threat model of DIDs w3c-ccg/community#43.
-
Add OpenPgpSignature2019 as a JSON-LD Signature Suite w3c-ccg/community#71.
-
Credential Fraud as a work item? w3c-ccg/community#74.
-
Need respec of RWOT paper as CCG Work Item w3c-ccg/community#63.
-
-
14 issues received 30 new comments.
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76 (6 comments by @aljones15, @BillBarnhill, @kimdhamilton)
-
Critical path problem with lack of JSON-LD 1.1 reference implementation w3c-ccg/community#83 (4 comments by @aljones15, @ChristopherA, @peacekeeper, @TallTed)
-
Discuss registries meta-process; what are next steps? w3c-ccg/community#75 (2 comments by @kimdhamilton)
-
Discuss "Nonviolent Communication for W3C Working Groups" w3c-ccg/community#81 (2 comments by @kimdhamilton)
-
address requests for clarity on correlation and privacy claims of DIDs w3c-ccg/community#44 (2 comments by @jandrieu, @kimdhamilton)
-
Add OpenPgpSignature2019 as a JSON-LD Signature Suite w3c-ccg/community#71 (2 comments by @jandrieu)
-
Need respec of RWOT paper as CCG Work Item w3c-ccg/community#63 (2 comments by @kimdhamilton, @lwolberg)
-
credentialSubject of Verifiable Credentials Data Model 1.0 w3c-ccg/community#78 (2 comments by @enuoCM, @TallTed)
-
w3c-ccg/http-signatures-test-suite
-
2 pull requests closed.
-
Update reports to use handlebars and a custom mocha reporter. w3c-ccg/http-signatures-test-suite#3.
-
Implement sign tests w3c-ccg/http-signatures-test-suite#4.
-
-
1 pull request received 1 new comment.
-
Update reports to use handlebars and a custom mocha reporter. w3c-ccg/http-signatures-test-suite#3 (1 comment by @aljones15)
-
w3c-ccg/zcap-spec
-
1 issue received 3 new comments.
w3c-ccg/http-signatures
-
7 issues opened.
-
Signing string should include keyId and algorithm (if present) via pseudo headers w3c-ccg/http-signatures#77, by @dlongley.
-
Digest acts on the representation-data, not the message body w3c-ccg/http-signatures#75, by @ioggstream.
-
Add sample code for generate examples. w3c-ccg/http-signatures#73, by @ioggstream.
-
PROPOSAL: move index.xml to index.md w3c-ccg/http-signatures#71, by @ioggstream.
-
Missing pseudo headers in draft version #11 examples w3c-ccg/http-signatures#68, by @hrobache.
-
Forbid empty `headers` parameter as it's subject to replay attacks. w3c-ccg/http-signatures#67, by @ioggstream.
-
created and expires should be signed if present w3c-ccg/http-signatures#66, by @ioggstream.
-
-
2 issues closed.
-
Forbid empty `headers` parameter as it's subject to replay attacks. w3c-ccg/http-signatures#67.
-
Status of this RFC related to European PSD2 (Berlin group) ? w3c-ccg/http-signatures#64.
-
-
7 issues received 17 new comments.
-
Forbid empty `headers` parameter as it's subject to replay attacks. w3c-ccg/http-signatures#67 (8 comments by @dlongley, @ioggstream, @liamdennehy)
-
Signing string should include keyId and algorithm (if present) via pseudo headers w3c-ccg/http-signatures#77 (2 comments by @dlongley, @ioggstream)
-
Status of this RFC related to European PSD2 (Berlin group) ? w3c-ccg/http-signatures#64 (2 comments by @earroyoron, @liamdennehy)
-
Creating and Signing the Signature String w3c-ccg/http-signatures#54 (2 comments by @ioggstream, @liamdennehy)
-
Link to signature-algorithms - page does not exist w3c-ccg/http-signatures#40 (1 comment by @ioggstream)
-
created and expires should be signed if present w3c-ccg/http-signatures#66 (1 comment by @liamdennehy)
-
-
5 pull requests opened.
-
Fix: #75. Reference representation data, not message body. w3c-ccg/http-signatures#76, by @ioggstream.
-
Add code for generating example signatures w3c-ccg/http-signatures#74, by @ioggstream.
-
Sign content-type when digest is used. #36 w3c-ccg/http-signatures#72, by @ioggstream.
-
Fix: #67. Forbid zero-length Signature.headers. w3c-ccg/http-signatures#70, by @ioggstream.
-
Fix #68: missing lines in signature string example. w3c-ccg/http-signatures#69, by @ioggstream.
-
-
1 pull request merged.
-
Fix: #67. Forbid zero-length Signature.headers. w3c-ccg/http-signatures#70.
-
-
5 pull requests received 16 new comments.
-
Sign content-type when digest is used. #36 w3c-ccg/http-signatures#72 (10 comments by @dlongley, @ioggstream, @liamdennehy)
-
Fix: #67. Forbid zero-length Signature.headers. w3c-ccg/http-signatures#70 (2 comments by @ioggstream, @msporny)
-
Fix #68: missing lines in signature string example. w3c-ccg/http-signatures#69 (2 comments by @hrobache, @ioggstream)
-
Fix: #63. forbid erroneously duplicate parameters w3c-ccg/http-signatures#65 (1 comment by @ioggstream)
-
w3c-ccg/announcements
-
1 pull request merged.
-
Add 2019 events: Identiverse, DWeb Camp, MyData w3c-ccg/announcements#6.
-
w3c-ccg/didm-btcr
-
3 issues opened.
-
Remove word "continuation'; replace with "implicit"/"explicit" w3c-ccg/didm-btcr#18, by @kimdhamilton.
-
Do we need confirmation time and DID document update time to be within a certain delta? w3c-ccg/didm-btcr#16, by @kimdhamilton.
-
Document v0.1 design decisions w3c-ccg/didm-btcr#15, by @kimdhamilton.
-
-
2 issues closed.
-
2 issues received 2 new comments.
-
BTCR uses tx references that deviate from Bech32 Encoded Transaction Position References w3c-ccg/didm-btcr#1 (1 comment by @kimdhamilton)
-
BTCR Resolver difference in resolving continuation documents based on im/mutable storage w3c-ccg/didm-btcr#2 (1 comment by @kimdhamilton)
-
-
1 pull request opened.
-
v0.1 changes, WIP w3c-ccg/didm-btcr#17, by @kimdhamilton.
-
-
1 pull request merged.
-
v0.1 changes, WIP w3c-ccg/didm-btcr#17.
-
w3c-ccg/lds-ecdsa-secp256k1-2019
-
1 issue opened.
-
Initial requirements w3c-ccg/lds-ecdsa-secp256k1-2019#1, by @peacekeeper.
-
-
1 issue received 3 new comments.
Participants
-
1 participant joined.
-
William Barnhill joined.
-
-
8 organizations joined.
-
MOAC joined.
-
Intel Corporation joined.
-
Kaiser Permanente joined.
-
Https Card - Internet Identity Card joined.
-
Iron Horse Software, LLC joined.
-
DataDelta joined.
-
Vidicode Inc joined.
-
Roche Diagnostics International joined.
-
-
1 organization left.
-
Gear Up left.
-
GitHub
w3c-ccg/community
-
6 issues opened.
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76, by @kimdhamilton.
-
Discuss registries meta-process; what are next steps? w3c-ccg/community#75, by @kimdhamilton.
-
Credential Fraud as a work item? w3c-ccg/community#74, by @kimdhamilton.
-
Discuss knowledge transfer / onboarding opportunities w3c-ccg/community#73, by @kimdhamilton.
-
[PROPOSED WORK ITEM] Verifiable Credentials Extension Registry w3c-ccg/community#72, by @msporny.
-
Add OpenPgpSignature2019 as a JSON-LD Signature Suite w3c-ccg/community#71, by @OR13.
-
-
6 issues closed.
-
Pin Top CCG Repos w3c-ccg/community#64.
-
Review results of 2018 EOY Survey w3c-ccg/community#61.
-
CCG call connection problems w3c-ccg/community#60.
-
Code of conduct w3c-ccg/community#69.
-
Determine next steps for survey results w3c-ccg/community#68.
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59.
-
-
11 issues received 28 new comments.
-
Add a DID web method as a work item w3c-ccg/community#65 (10 comments by @brentzundel, @ChristopherA, @dlongley, @nadalin, @peacekeeper, @vipinsun)
-
Add OpenPgpSignature2019 as a JSON-LD Signature Suite w3c-ccg/community#71 (6 comments by @ChristopherA, @kimdhamilton, @OR13)
-
Revisit doc to spectext conversion tool if that format is required for work items w3c-ccg/community#76 (3 comments by @BillBarnhill, @kimdhamilton)
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59 (1 comment by @kimdhamilton)
-
w3c-ccg/did-wg-charter
-
1 issue opened.
-
Normative Specifications w3c-ccg/did-wg-charter#33, by @nadalin.
-
-
1 issue closed.
-
DID charter does not include defining DID (scheme) itself w3c-ccg/did-wg-charter#5.
-
-
10 issues received 17 new comments.
-
Clarify statement around VCWG coordination re Normalization and Signatures w3c-ccg/did-wg-charter#12 (3 comments by @kimdhamilton, @nadalin)
-
Out of Scope: Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#14 (2 comments by @kimdhamilton)
-
Out of Scope: Access Management and Identity Management w3c-ccg/did-wg-charter#15 (1 comment by @kimdhamilton)
-
Decentralized Identifier: "Decentralized" in working group name w3c-ccg/did-wg-charter#22 (1 comment by @kimdhamilton)
-
General: current language precludes DIDs/methods leased from an authority w3c-ccg/did-wg-charter#16 (1 comment by @kimdhamilton)
-
3 pull requests opened.
-
Enable, not specify, Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#34, by @kimdhamilton.
-
DID method implementation is out of scope w3c-ccg/did-wg-charter#32, by @kimdhamilton.
-
Update index.html (minor, polish) w3c-ccg/did-wg-charter#31, by @TallTed.
-
-
7 pull requests merged.
-
Enable, not specify, Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#34.
-
Update language: DIDs enable cryptographic authentication w3c-ccg/did-wg-charter#29.
-
Address concern around finality of use cases w3c-ccg/did-wg-charter#24.
-
Specify that VCs are not restrictive use case w3c-ccg/did-wg-charter#26.
-
Add DID URI scheme definition as required output w3c-ccg/did-wg-charter#6.
-
Address confusing language w3c-ccg/did-wg-charter#25.
-
Enabling access/id mgmt via DIDs w3c-ccg/did-wg-charter#30.
-
-
1 pull request closed.
-
change to public and open communication w3c-ccg/did-wg-charter#11.
-
-
10 pull requests received 35 new comments.
-
Rubric for decentralized characteristics w3c-ccg/did-wg-charter#28 (18 comments by @brentzundel, @kimdhamilton, @msporny, @nadalin, @TallTed)
-
Update language: DIDs enable cryptographic authentication w3c-ccg/did-wg-charter#29 (4 comments by @kimdhamilton, @msporny, @nadalin, @peacekeeper)
-
Enabling access/id mgmt via DIDs w3c-ccg/did-wg-charter#30 (3 comments by @Fak3, @kimdhamilton, @msporny)
-
Address concern around finality of use cases w3c-ccg/did-wg-charter#24 (2 comments by @kimdhamilton)
-
DID method implementation is out of scope w3c-ccg/did-wg-charter#32 (2 comments by @brentzundel, @jandrieu)
-
Enable, not specify, Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#34 (1 comment by @kimdhamilton)
-
Specify that VCs are not restrictive use case w3c-ccg/did-wg-charter#26 (1 comment by @kimdhamilton)
-
Add DID URI scheme definition as required output w3c-ccg/did-wg-charter#6 (1 comment by @kimdhamilton)
-
w3c-ccg/security-vocab
-
2 pull requests opened.
-
Update browser packaging. w3c-ccg/security-vocab#7, by @davidlehn.
-
Export constants. w3c-ccg/security-vocab#6, by @mattcollier.
-
-
4 pull requests merged.
-
Implement browser support. w3c-ccg/security-vocab#4.
-
Browser support. w3c-ccg/security-vocab#5.
-
Export constants. w3c-ccg/security-vocab#6.
-
Update browser packaging. w3c-ccg/security-vocab#7.
-
-
1 pull request closed.
-
Node.js - use require() instead of fs.read. w3c-ccg/security-vocab#2.
-
-
3 pull requests received 6 new comments.
w3c-ccg/http-signatures
-
5 issues opened.
-
Status of this RFC related to European PSD2 (Berlin group) ? w3c-ccg/http-signatures#64, by @earroyoron.
-
Don't trust ambiguous parameters w3c-ccg/http-signatures#63, by @ioggstream.
-
2.1.2 signature in version 11 spec still tells people to use the algorithm parameter to sign. w3c-ccg/http-signatures#59, by @aljones15.
-
header and signature parameters are confusing. w3c-ccg/http-signatures#58, by @aljones15.
-
links to encryption algorithims documents in hsa registry go nowhere. w3c-ccg/http-signatures#57, by @aljones15.
-
-
2 issues closed.
-
Date header is not mandatory in HTTP/1.1 RFCs yet relied on by "headers" field w3c-ccg/http-signatures#33.
-
links to encryption algorithims documents in hsa registry go nowhere. w3c-ccg/http-signatures#57.
-
-
16 issues received 44 new comments.
-
Don't trust ambiguous parameters w3c-ccg/http-signatures#63 (9 comments by @aljones15, @ioggstream, @liamdennehy)
-
Status of this RFC related to European PSD2 (Berlin group) ? w3c-ccg/http-signatures#64 (7 comments by @earroyoron, @ioggstream, @liamdennehy)
-
Creating and Signing the Signature String w3c-ccg/http-signatures#54 (7 comments by @dlongley, @ioggstream, @liamdennehy, @RayTrommelenInfoSupport)
-
Difference between Authorization and Signature not clear w3c-ccg/http-signatures#13 (3 comments by @bblfish, @liamdennehy)
-
Server should not trust client header w3c-ccg/http-signatures#39 (2 comments by @ioggstream, @liamdennehy)
-
Signed Headers should either mention representation metadata or forbid them w3c-ccg/http-signatures#36 (2 comments by @ioggstream)
-
Date header is not mandatory in HTTP/1.1 RFCs yet relied on by "headers" field w3c-ccg/http-signatures#33 (2 comments by @ioggstream, @liamdennehy)
-
2.1.2 signature in version 11 spec still tells people to use the algorithm parameter to sign. w3c-ccg/http-signatures#59 (2 comments by @aljones15, @RayTrommelenInfoSupport)
-
links to encryption algorithims documents in hsa registry go nowhere. w3c-ccg/http-signatures#57 (2 comments by @aljones15, @RayTrommelenInfoSupport)
-
Concatenation of multiple-instance headers in signing string w3c-ccg/http-signatures#50 (1 comment by @ioggstream)
-
Link to signature-algorithms - page does not exist w3c-ccg/http-signatures#40 (1 comment by @aljones15)
-
-
6 pull requests opened.
-
Fix: #63. forbid erroneously duplicate parameters w3c-ccg/http-signatures#65, by @ioggstream.
-
We are signing parts of HTTP messages w3c-ccg/http-signatures#62, by @ioggstream.
-
Removed adding the content of the HTTP message in creating the signature string. w3c-ccg/http-signatures#61, by @RayTrommelenInfoSupport.
-
Correct typos & Documentation of the algorithm parameter w3c-ccg/http-signatures#60, by @aljones15.
-
[WIP] Add a version parameter. w3c-ccg/http-signatures#56, by @ioggstream.
-
Fix definition of rsa-sha256 to match previous versions w3c-ccg/http-signatures#55, by @jhominal.
-
-
4 pull requests received 22 new comments.
-
Correct typos & Documentation of the algorithm parameter w3c-ccg/http-signatures#60 (7 comments by @aljones15, @dlongley, @liamdennehy)
-
Removed adding the content of the HTTP message in creating the signature string. w3c-ccg/http-signatures#61 (2 comments by @ioggstream)
w3c-ccg/announcements
-
2 pull requests opened.
-
Add 2019 events: Identiverse, DWeb Camp, MyData w3c-ccg/announcements#6, by @peacekeeper.
-
Fix info for weekly dedicated DID calls w3c-ccg/announcements#5, by @peacekeeper.
-
-
1 pull request merged.
-
Fix info for weekly dedicated DID calls w3c-ccg/announcements#5.
-
-
1 pull request closed.
-
Add Trust and Internet Identity Meeting Europe w3c-ccg/announcements#4.
-
w3c-ccg/http-signatures-test-suite
-
5 pull requests opened.
-
All tests w3c-ccg/http-signatures-test-suite#5, by @aljones15.
-
Implement sign tests w3c-ccg/http-signatures-test-suite#4, by @aljones15.
-
Update reports to use handlebars and a custom mocha reporter. w3c-ccg/http-signatures-test-suite#3, by @aljones15.
-
Fix async exec w3c-ccg/http-signatures-test-suite#2, by @aljones15.
-
Initial w3c-ccg/http-signatures-test-suite#1, by @aljones15.
-
-
1 pull request merged.
-
Fix async exec w3c-ccg/http-signatures-test-suite#2.
-
-
1 pull request received 38 new comments.
-
Initial w3c-ccg/http-signatures-test-suite#1 (38 comments by @aljones15, @davidlehn, @mattcollier, @msporny)
-
w3c-ccg/lds-ed25519-2018
-
1 issue opened.
-
Secure alternatives w3c-ccg/lds-ed25519-2018#4, by @RorschachRev.
-
Participants
-
4 participants joined.
-
Jeffrey Song joined.
-
Gregg Kellogg joined.
-
Kim Duffy joined.
-
Timothy Holborn joined.
-
-
4 participants left.
-
Niels Quinten left.
-
Andrei Sambra (AKASHA Foundation) left.
-
Chris Seifert left.
-
Matt Stone (BrightLink) left.
-
-
5 organizations joined.
-
TNO joined.
-
Ockam joined.
-
AKASHA Foundation joined.
-
BrightLink joined.
-
Inrupt Inc. joined.
-
GitHub
w3c-ccg/community
-
7 issues opened.
-
Should we discuss roadmap on an ongoing basis during calls? w3c-ccg/community#70, by @kimdhamilton.
-
Code of conduct w3c-ccg/community#69, by @kimdhamilton.
-
Determine next steps for survey results w3c-ccg/community#68, by @kimdhamilton.
-
Book space at W3C TPAC 2019 w3c-ccg/community#67, by @msporny.
-
Review DID Charter PRs and Issues w3c-ccg/community#66, by @ChristopherA.
-
Add a DID web method as a work item w3c-ccg/community#65, by @dmitrizagidulin.
-
Pin Top CCG Repos w3c-ccg/community#64, by @ChristopherA.
-
-
5 issues received 54 new comments.
-
Add a DID web method as a work item w3c-ccg/community#65 (46 comments by @awoie, @cbruguera, @dlongley, @dmitrizagidulin, @friedger, @hawkmauk, @jandrieu, @Joachim16, @nadalin, @peacekeeper, @rhiaro, @talltree, @victorgrey)
-
LD Key Format Registry administrivia w3c-ccg/community#56 (2 comments by @ChristopherA, @kimdhamilton)
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59 (2 comments by @kimdhamilton)
-
w3c-ccg/security-vocab
-
2 pull requests opened.
-
Browser support. w3c-ccg/security-vocab#5, by @davidlehn.
-
Implement browser support. w3c-ccg/security-vocab#4, by @mattcollier.
-
-
2 pull requests received 17 new comments.
-
Node.js - use require() instead of fs.read. w3c-ccg/security-vocab#2 (10 comments by @dlongley, @dmitrizagidulin, @gannan08, @mattcollier)
-
Browser support. w3c-ccg/security-vocab#5 (7 comments by @davidlehn, @dlongley, @gannan08, @mattcollier)
-
w3c-ccg/did-wg-charter
-
11 issues opened.
-
Decentralized Identifier: "Decentralized" in working group name w3c-ccg/did-wg-charter#22, by @nadalin.
-
More General Comments w3c-ccg/did-wg-charter#20, by @nadalin.
-
Portability w3c-ccg/did-wg-charter#19, by @nadalin.
-
Authentication w3c-ccg/did-wg-charter#17, by @nadalin.
-
General: current language precludes DIDs/methods leased from an authority w3c-ccg/did-wg-charter#16, by @nadalin.
-
Out of Scope: Access Management and Identity Management w3c-ccg/did-wg-charter#15, by @nadalin.
-
Out of Scope: Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#14, by @nadalin.
-
Clarify statement around VCWG coordination re Normalization and Signatures w3c-ccg/did-wg-charter#12, by @nadalin.
-
-
10 issues received 74 new comments.
-
Decentralized Identifier: "Decentralized" in working group name w3c-ccg/did-wg-charter#22 (19 comments by @brentzundel, @ChristopherA, @jandrieu, @jcnelson, @nadalin, @OR13, @peacekeeper, @rhiaro)
-
General: current language precludes DIDs/methods leased from an authority w3c-ccg/did-wg-charter#16 (13 comments by @jandrieu, @jcnelson, @Joachim16, @kimdhamilton, @mitfik, @nadalin, @peacekeeper)
-
More General Comments w3c-ccg/did-wg-charter#20 (12 comments by @dlongley, @jandrieu, @jcnelson, @mrinalwadhwa, @nadalin, @peacekeeper, @talltree)
-
Use cases are outside of the charter w3c-ccg/did-wg-charter#9 (8 comments by @jandrieu, @kimdhamilton, @koalie, @nadalin)
-
DID charter does not include defining DID (scheme) itself w3c-ccg/did-wg-charter#5 (5 comments by @kimdhamilton, @nadalin, @talltree)
-
Out of Scope: Auth, Signing, Cryptography mechanisms w3c-ccg/did-wg-charter#14 (3 comments by @dlongley, @kimdhamilton, @nadalin)
-
Out of Scope: Access Management and Identity Management w3c-ccg/did-wg-charter#15 (1 comment by @kimdhamilton)
-
-
8 pull requests opened.
-
Enabling access/id mgmt via DIDs w3c-ccg/did-wg-charter#30, by @kimdhamilton.
-
Update language: DIDs enable cryptographic authentication w3c-ccg/did-wg-charter#29, by @kimdhamilton.
-
Rubric for decentralized characteristics w3c-ccg/did-wg-charter#28, by @brentzundel.
-
clarified decentralized identifier w3c-ccg/did-wg-charter#27, by @brentzundel.
-
Specify that VCs are not restrictive use case w3c-ccg/did-wg-charter#26, by @kimdhamilton.
-
Address confusing language w3c-ccg/did-wg-charter#25, by @kimdhamilton.
-
Address concern around finality of use cases w3c-ccg/did-wg-charter#24, by @kimdhamilton.
-
Change language to not disallow DIDs based on centralized authorities w3c-ccg/did-wg-charter#23, by @kimdhamilton.
-
-
1 pull request closed.
-
Change language to not disallow DIDs based on centralized authorities w3c-ccg/did-wg-charter#23.
-
-
2 pull requests received 6 new comments.
-
Change language to not disallow DIDs based on centralized authorities w3c-ccg/did-wg-charter#23 (4 comments by @jandrieu, @kimdhamilton)
-
change to public and open communication w3c-ccg/did-wg-charter#11 (2 comments by @peacekeeper, @sandhawke)
-
w3c-ccg/http-signatures
-
2 issues opened.
-
Creating and Signing the Signature String w3c-ccg/http-signatures#54, by @RayTrommelenInfoSupport.
-
Support a versioning scheme w3c-ccg/http-signatures#53, by @ioggstream.
-
-
1 issue closed.
-
Signature header does not contain date, expires w3c-ccg/http-signatures#35.
-
-
3 issues received 7 new comments.
-
Creating and Signing the Signature String w3c-ccg/http-signatures#54 (5 comments by @dlongley, @ioggstream, @liamdennehy, @RayTrommelenInfoSupport)
-
Signed Headers should either mention representation metadata or forbid them w3c-ccg/http-signatures#36 (1 comment by @ioggstream)
-
Signature header does not contain date, expires w3c-ccg/http-signatures#35 (1 comment by @ioggstream)
-
-
3 pull requests merged.
-
Clarify authorize vs sign w3c-ccg/http-signatures#48.
-
Fixes: #35. Add `date` and `expires` to signature w3c-ccg/http-signatures#37.
-
Add text to clarify the purpose of human-visible new lines in examples w3c-ccg/http-signatures#11.
-
-
2 pull requests closed.
-
Minor fixes - parameter delimiters, urls, typos w3c-ccg/http-signatures#49.
-
Date header w3c-ccg/http-signatures#44.
-
-
3 pull requests received 13 new comments.
-
Fixes: #35. Add `date` and `expires` to signature w3c-ccg/http-signatures#37 (9 comments by @dlongley, @ioggstream, @liamdennehy, @msporny)
-
Minor fixes - parameter delimiters, urls, typos w3c-ccg/http-signatures#49 (2 comments by @liamdennehy, @msporny)
-
w3c-ccg/data-minimization
-
1 issue opened.
-
Proof of Correctness - Verification - Inverse of Zi and Ri w3c-ccg/data-minimization#4, by @gith1chris.
-
-
1 issue closed.
-
Proof of Correctness - Verification - Inverse of Zi and Ri w3c-ccg/data-minimization#4.
-
-
1 issue reopened.
-
Proof of Correctness - Verification - Inverse of Zi and Ri w3c-ccg/data-minimization#4, by @gith1chris.
-
w3c-ccg/multihash
-
1 issue opened.
-
registry is underspecified w3c-ccg/multihash#5, by @nichtich.
-
-
1 issue received 4 new comments.
-
4 pull requests opened.
-
Move registry into its own XML file w3c-ccg/multihash#8, by @nichtich.
-
Use hexademical notation more consistently w3c-ccg/multihash#7, by @nichtich.
-
Normalize terminoloy of registry w3c-ccg/multihash#6, by @nichtich.
-
Update location and processing of registry w3c-ccg/multihash#4, by @nichtich.
-
-
3 pull requests merged.
-
Use hexademical notation more consistently w3c-ccg/multihash#7.
-
Normalize terminoloy of registry w3c-ccg/multihash#6.
-
Update location and processing of registry w3c-ccg/multihash#4.
-
-
2 pull requests received 7 new comments.
w3c-ccg/hashlink
-
1 pull request opened.
-
Add Hash URI Specification w3c-ccg/hashlink#1, by @nichtich.
-
-
1 pull request merged.
-
Add Hash URI Specification w3c-ccg/hashlink#1.
-
w3c-ccg/meetings
-
1 pull request opened.
-
minor edit to notes w3c-ccg/meetings#9, by @jonnycrunch.
-
Participants
-
7 participants joined.
-
david mason joined.
-
Christian Hartl joined.
-
Benjamin Goering joined.
-
Dong-jun LEE joined.
-
Andrea Taglia joined.
-
Ruben Cessa joined.
-
Andrei Sambra (AKASHA Foundation) joined.
-
-
1 participant left.
-
Anh Nguyen left.
-
-
5 organizations joined.
-
Factom Inc. joined.
-
Optum Technology joined.
-
dlt.nyc joined.
-
Cloud Compass Computing, Inc. joined.
-
[DUPLICATE] Protocol Labs, Inc. joined.
-
-
1 organization left.
-
YSZ left.
-
GitHub
w3c-ccg/community
-
4 issues opened.
-
Need respec of RWOT paper as CCG Work Item w3c-ccg/community#63, by @ChristopherA.
-
DIF to present on progress w3c-ccg/community#62, by @kimdhamilton.
-
Review results of 2018 EOY Survey w3c-ccg/community#61, by @kimdhamilton.
-
CCG call connection problems w3c-ccg/community#60, by @kimdhamilton.
-
-
3 issues closed.
-
DIF to present on progress w3c-ccg/community#62.
-
Review CCG Github Editors List at EOY w3c-ccg/community#34.
-
Update SIP connection instructions to reference OnSip w3c-ccg/community#58.
-
-
6 issues received 26 new comments.
-
Need update from Ethereum Community on differences on various DID-based EIPs w3c-ccg/community#21 (13 comments by @ChristopherA, @Drabiv, @frozeman, @kimdhamilton, @oed, @TallTed)
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59 (4 comments by @ChristopherA, @kimdhamilton, @peacekeeper)
-
Update SIP connection instructions to reference OnSip w3c-ccg/community#58 (1 comment by @kimdhamilton)
-
w3c-ccg/security-vocab
-
1 pull request opened.
-
Add KmsOperation terms. w3c-ccg/security-vocab#3, by @mattcollier.
-
-
1 pull request merged.
-
Add KmsOperation terms. w3c-ccg/security-vocab#3.
-
w3c-ccg/lds-merkleproof2017
-
3 pull requests opened.
-
Errata on introduction: wrong signature algorithm w3c-ccg/lds-merkleproof2017#4, by @davidlj95.
-
Errata on example signature suite name w3c-ccg/lds-merkleproof2017#3, by @davidlj95.
-
Wrong repository location (w3c-dvcg, not w3c) w3c-ccg/lds-merkleproof2017#2, by @davidlj95.
-
-
2 pull requests merged.
-
Errata on example signature suite name w3c-ccg/lds-merkleproof2017#3.
-
Wrong repository location (w3c-dvcg, not w3c) w3c-ccg/lds-merkleproof2017#2.
-
w3c-ccg/http-signatures
-
1 pull request received 1 new comment.
w3c-ccg/vc-examples
-
1 pull request opened.
-
create directories and instructions to hold two kinds of submissions w3c-ccg/vc-examples#1, by @rxgrant.
-
Participants
-
7 participants joined.
-
Paul Fuxjaeger (University of Vienna) joined.
-
Juan Castaneda joined.
-
Adam Bradley (Mastercard Incorporated) joined.
-
Anil John (Department of Homeland Security) joined.
-
Vineet Singh joined.
-
Michael Herman joined.
-
Jonathan Holt (Consensys) joined.
-
-
1 participant left.
-
Markus Sabadello (Danube Tech GmbH) left.
-
-
5 organizations joined.
-
CSIRO joined.
-
Fundacion CTIC joined.
-
Danube Tech joined.
-
Financial Security Institute joined.
-
Jolocom GmbH joined.
-
-
1 organization left.
-
Red Hat left.
-
GitHub
w3c-ccg/http-signatures
-
1 issue received 1 new comment.
w3c-ccg/community
-
4 issues opened.
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59, by @kimdhamilton.
-
Update SIP connection instructions to reference OnSip w3c-ccg/community#58, by @kimdhamilton.
-
Updating ABNF for DIDs w3c-ccg/community#57, by @ChristopherA.
-
LD Key Format Registry administrivia w3c-ccg/community#56, by @kimdhamilton.
-
-
5 issues closed.
-
Prime a discussion on PR changes to DID w3c-ccg/community#42.
-
Review Verifiable Credentials Data Model Specification w3c-ccg/community#28.
-
Create github issue templates for work items w3c-ccg/community#52.
-
DID resolution specification w3c-ccg/community#20.
-
Functional Identity Report w3c-ccg/community#53.
-
-
8 issues received 12 new comments.
-
Review Verifiable Credentials Data Model Specification w3c-ccg/community#28 (2 comments by @msporny)
-
DID methods in the registry without associated DID specifications w3c-ccg/community#59 (1 comment by @kimdhamilton)
w3c-ccg/did-wg-charter
-
2 issues opened.
-
Are there any strong use cases? w3c-ccg/did-wg-charter#10, by @sandhawke.
-
Use cases are outside of the charter w3c-ccg/did-wg-charter#9, by @koalie.
-
-
1 issue closed.
-
Are there any strong use cases? w3c-ccg/did-wg-charter#10.
-
-
2 issues received 17 new comments.
-
Are there any strong use cases? w3c-ccg/did-wg-charter#10 (11 comments by @Drabiv, @jandrieu, @msporny, @sandhawke)
-
Use cases are outside of the charter w3c-ccg/did-wg-charter#9 (6 comments by @jandrieu, @koalie, @msporny, @sandhawke)
-
-
1 pull request opened.
-
change to public and open communication w3c-ccg/did-wg-charter#11, by @jonnycrunch.
-
w3c-ccg/meetings
-
1 pull request opened.
-
Add audio logs for 2019-02-07 DID Resolution telecon. w3c-ccg/meetings#8, by @peacekeeper.
-
-
1 pull request merged.
-
Add audio logs for 2019-02-07 DID Resolution telecon. w3c-ccg/meetings#8.
-
-
1 pull request received 1 new comment.
-
Add audio logs for 2019-02-07 DID Resolution telecon. w3c-ccg/meetings#8 (1 comment by @kimdhamilton)
-
w3c-ccg/2015-2025-old-w3c-ccg-website
-
1 pull request opened.
-
Fix broken link w3c-ccg/2015-2025-old-w3c-ccg-website#16, by @solid-pay.
-
-
1 pull request merged.
-
Fix broken link w3c-ccg/2015-2025-old-w3c-ccg-website#16.
-
-
1 pull request received 1 new comment.
w3c-ccg/didm-btcr
-
1 issue received 1 new comment.
Participants
-
2 participants joined.
-
Eddie Kago joined.
-
Chris Seifert joined.
-
-
4 organizations joined.
-
Transmute joined.
-
Bespoke Engineering joined.
-
Isabel NV/SA joined.
-
JLINC Labs joined.
-
GitHub
w3c-ccg/zcap-spec
-
1 issue opened.
-
Why use asymmetric signatures? Why not macaroons? w3c-ccg/zcap-spec#24, by @WildCryptoFox.
-
w3c-ccg/community
-
8 issues opened.
-
Administrivia: handle newly accepted work items w3c-ccg/community#55, by @kimdhamilton.
-
CCG 2018 End of Year Survey w3c-ccg/community#54, by @kimdhamilton.
-
Functional Identity Report w3c-ccg/community#53, by @jandrieu.
-
Create github issue templates for work items w3c-ccg/community#52, by @kimdhamilton.
-
Discuss "DIDs, proof purposes, and verification methods" during CCG call w3c-ccg/community#50, by @kimdhamilton.
-
Add Hashlink as a work item w3c-ccg/community#48, by @msporny.
-
Add Multibase as a work item w3c-ccg/community#47, by @msporny.
-
Add Multihash as a work item w3c-ccg/community#46, by @msporny.
-
-
7 issues closed.
-
CCG 2018 End of Year Survey w3c-ccg/community#54.
-
Administrivia: handle newly accepted work items w3c-ccg/community#55.
-
Add Multibase as a work item w3c-ccg/community#47.
-
Add Hashlink as a work item w3c-ccg/community#48.
-
Add Multihash as a work item w3c-ccg/community#46.
-
Add tags to Repo descriptions w3c-ccg/community#15.
-
Discuss "DIDs, proof purposes, and verification methods" during CCG call w3c-ccg/community#50.
-
-
14 issues received 25 new comments.
-
Functional Identity Report w3c-ccg/community#53 (4 comments by @andrewhughes3000, @jandrieu, @mwherman2000)
-
Review Verifiable Credentials Data Model Specification w3c-ccg/community#28 (3 comments by @David-Chadwick, @ipatka)
-
Discuss "DIDs, proof purposes, and verification methods" during CCG call w3c-ccg/community#50 (3 comments by @dlongley, @kimdhamilton)
-
look at security model or threat model of DIDs w3c-ccg/community#43 (2 comments by @kimdhamilton, @rxgrant)
-
address requests for clarity on correlation and privacy claims of DIDs w3c-ccg/community#44 (1 comment by @kimdhamilton)
-
-
2 pull requests opened.
-
"DID Resolution" instead of "DID Resolver" w3c-ccg/community#51, by @peacekeeper.
-
Update work_items.md w3c-ccg/community#49, by @kimdhamilton.
-
-
2 pull requests merged.
-
"DID Resolution" instead of "DID Resolver" w3c-ccg/community#51.
-
Update work_items.md w3c-ccg/community#49.
-
w3c-ccg/http-signatures
-
1 issue opened.
-
Presentation issues for the test vectors w3c-ccg/http-signatures#52, by @bortzmeyer.
-
-
1 issue closed.
-
Broken link to "Security Considerations for HTTP Signatures" w3c-ccg/http-signatures#14.
-
-
1 issue received 2 new comments.
-
Broken link to "Security Considerations for HTTP Signatures" w3c-ccg/http-signatures#14 (2 comments by @ioggstream, @msporny)
-
w3c-ccg/didm-btcr
-
1 issue opened.
-
Continuation DID Document URL should support Hashlink w3c-ccg/didm-btcr#14, by @peacekeeper.
-
-
2 issues received 2 new comments.
-
Continuation DID Document URL should support Hashlink w3c-ccg/didm-btcr#14 (1 comment by @kimdhamilton)
-
BTCR Resolver difference in resolving continuation documents based on im/mutable storage w3c-ccg/didm-btcr#2 (1 comment by @peacekeeper)
-
-
1 pull request merged.
-
updated examples with latest version of txrefs; add example DID doc w3c-ccg/didm-btcr#13.
-
w3c-ccg/lds-ed25519-2018
-
1 issue received 1 new comment.
w3c-ccg/security-vocab
-
2 pull requests opened.
-
Node.js - use require() instead of fs.read. w3c-ccg/security-vocab#2, by @dmitrizagidulin.
-
Package w3c-ccg/security-vocab#1, by @mattcollier.
-
-
1 pull request merged.
-
Package w3c-ccg/security-vocab#1.
-
-
1 pull request received 4 new comments.
-
Node.js - use require() instead of fs.read. w3c-ccg/security-vocab#2 (4 comments by @davidlehn, @dmitrizagidulin)
-