Awesome-Mirrors/decentralized-id.github.io
1
0
Fork 0
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git synced 2025-09-27 19:51:11 -04:00
Code Issues Projects Releases Packages Wiki Activity

split json-ld vc 2 pages

Browse source
This commit is contained in:
⧉ infominer 2023-09-29 23:25:27 -04:00
parent 6f19a9ce9f
commit da776c41ab
10 changed files with 208 additions and 210 deletions
Download patch file Download diff file Expand all files Collapse all files

1
_data/standards.csv
View file

@ -48,6 +48,7 @@ Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,What are VCs simil
Verifiable Credentials,Personal,,https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html,"Kyle Den Hartog, Manu Sporny",,,,,,Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22),"Agreed, when it comes to the number of checks that occur it's much greater<br>because of the delegation. With that in mind, looking at the semantics only<br>of the system VCs in my opinion weren't optimally designed for permission<br>tokens. This difference between the two requires that an implementation<br>that wants to support both claims tokens and permissions tokens has to<br>grapple with the different mental model that arise when trying to stuff<br>these things together. This introduces additional complexity. Additionally<br>it leads to weird statements that are being made where it's difficult to<br>tell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Comparisons,,,,,,,,2021-06-24,,,,,,,,,,,,,
"Verifiable Credentials, Object Capabilities",Personal,,,Kyle Den Hartog,,,,,,Comparing VCs to ZCAP-LD,Why make the investment then to put the time and effort into ZCAPs when we’ve already got VCs? Simply put because security is hard and trying to push square pegs into round holes often times leads to bugs which are elevated to mission critical authentication/authorization bypass vulnerabilities. By designing around a fit for purpose data model with a well defined problem being solved it allows for us to be much more precise about where we believe extensibility is important versus where normative statements should be made to simplify the processing of the data models. By extension this leads to a simpler security model and likely a much more robust design with fewer vulnerabilities.,,https://kyledenhartog.com/comparing-VCs-with-zcaps/,,Post,,,"Comparisons, Main",,,,,,Object Capabilities,,2021-09-25,,,,,,,,,,,,,
"Verifiable Credentials, Object Capabilities",CCG Mailing List,,,Dave Longley,,,,,,Re: VCs - zCaps / OCap a Discussion,"TL; DR: My current view is that the main confusion here may be over the difference between VCs and LD Proofs, not VCs and ZCAPs. VCs are not a generalized container for attaching a cryptographic proof to a document. That's what LD proofs (or JOSE style proofs) are for. VCs *use* LD proofs (or JOSE style proofs) to attach an assertion proof to a document that specifically models statements made by an issuer about some subject, which is therefore inherently about the identity of that subject",,https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0027.html,,Discussion,,,"Comparisons, Main",,,,,,Object Capabilities,Credentials Community Group,2020-12-05,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,List of Implementations for the Verifiable Credentials Data Model,"<ul><li>Go<ul><li><a href=""https://github.com/TBD54566975/ssi-sdk/tree/main/credential"">Credential Manifest Builders</a> (DI &amp; JWT)</li><li><a href=""https://github.com/hyperledger/aries-framework-go"">Hyperledger Aries Framework Go</a> (DI &amp; JWT)</li></ul></li><li>Java<ul><li><a href=""https://github.com/danubetech/verifiable-credentials-java"">Verifiable Credentials Java</a> (DI &amp; JWT)</li></ul></li><li>JavaScript/TypeScript<ul><li><a href=""https://github.com/digitalbazaar/vc-js"">Verifiable Credentials JS Library</a> (DI)</li><li><a href=""https://github.com/transmute-industries/verifiable-data/tree/main/packages/vc.js"">Verifiable Data Credential JS Library with JWT</a> (DI &amp; JWT)</li><li><a href=""https://github.com/decentralized-identity/did-jwt-vc"">W3C Verifiable Credentials and Presentations in JWT format</a> (JWT)</li></ul></li><li>Kotlin<ul><li><a href=""https://github.com/microsoft/VerifiableCredential-SDK-Android"">Verifiable Credentials in Kotlin</a> (JWT)</li></ul></li><li>Python<ul><li><a href=""https://github.com/hyperledger/aries-cloudagent-python"">Hyperledger Aries Cloud Agent - Python (ACA-Py)</a> (DI &amp; JWT)</li></ul></li><li>Rust<ul><li><a href=""https://github.com/spruceid/didkit"">DIDKit</a> (DI &amp; JWT)</li></ul></li><li>Swift<ul><li><a href=""https://github.com/microsoft/VerifiableCredential-SDK-iOS"">Verifiable Credentials in Swift</a> (JWT)</li></ul></li></ul>",,https://github.com/w3c/verifiable-credentials/blob/main/implementations.md,,Page,,,Implementations,,,,,,,,2022-06-03,,,,,,,,,,,,,
Verifiable Credentials,DSpace@MIT,,,,,,,,,SolidVC : a decentralized framework for Verifiable Credentials on the web,"SolidVC is a decentralized Verifiable Credentials platform built with the open protocols of the Web. It is implemented on top of Solid, a Web framework developed at MIT in 2016 that allows decentralized applications to interact with personal user data to provide services in an access controlled environment.",,https://dspace.mit.edu/handle/1721.1/121667,https://dspace.mit.edu/bitstream/handle/1721.1/121667/1102055877-MIT.pdf.jpg?sequence=4&isAllowed=y,paper,,,Implementations,,,,,,,,2019,,,,,,,,,,,,,
Verifiable Credentials,Paris P2P,,,,,,,,Paris P2P Festival,Blockstack and Verifiable Credentials - Paris P2P Festival,• Keep auth and smart contracts on-chain<br> • Keep encrypted data off-chain<br> > • Wrap everything in an easy JavaScript API,,https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf,,presentation,,,Implementations,,,,,,,,2020-01-10,,,,,,,,,,,,,
Verifiable Credentials,LibP2P,,,,,,,,,Verifiable credentials and libp2p,Hi - we’re looking into libp2p as a network stack for our application and exploring how we could integrate verifiable credentials (https://w3c.github.io/vc-data-model/ 2) infrastructure. A basic use case is that of a node being challenged to provide some specific credential to join the network. The bootstrap node handling the incoming connection should verify the credential with the issuer and complete the connection/bootstrap or terminate it.,,https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206,https://global.discourse-cdn.com/standard17/uploads/libp2p/original/1X/aacb49457c3aace79a1038dd02996b402260215d.png,discussion,,,Implementations,,,,,,,,2019-07-09,,,,,,,,,,,,,

1 main parent name supporting authors related location serving policy event title text description link image type status platform section sector industry market focus projects tech working group date github twitter youtube list feed discord crunchbase linkedin docs devtools app telegram forum
48 Verifiable Credentials Personal https://lists.w3.org/Archives/Public/public-credentials/2021Jun/0244.html Kyle Den Hartog, Manu Sporny Re: The dangers of using VCs as permission tokens (was: PROPOSALs for VC HTTP API call on 2021-06-22) Agreed, when it comes to the number of checks that occur it's much greater<br>because of the delegation. With that in mind, looking at the semantics only<br>of the system VCs in my opinion weren't optimally designed for permission<br>tokens. This difference between the two requires that an implementation<br>that wants to support both claims tokens and permissions tokens has to<br>grapple with the different mental model that arise when trying to stuff<br>these things together. This introduces additional complexity. Additionally<br>it leads to weird statements that are being made where it's difficult to<br>tell if the VC is behaving like a claims token or a permissions token.<br><br>Yes, exactly this. Exactly what Kyle states above is the reason why it's so complicated (and thus dangerous) to use VCs as permissions tokens.<br><br>This is one of the primary reasons that we separated out the Authorization Capabilities work from the Verifiable Credentials work. Things get really complicated when you start mixing authz/authn/claims/permissions into a Verifiable Credential. Just because you can do it doesn't mean you should https://kyledenhartog.com/example-authz-with-VCs/ Post Comparisons 2021-06-24
49 Verifiable Credentials, Object Capabilities Personal Kyle Den Hartog Comparing VCs to ZCAP-LD Why make the investment then to put the time and effort into ZCAPs when we’ve already got VCs? Simply put because security is hard and trying to push square pegs into round holes often times leads to bugs which are elevated to mission critical authentication/authorization bypass vulnerabilities. By designing around a fit for purpose data model with a well defined problem being solved it allows for us to be much more precise about where we believe extensibility is important versus where normative statements should be made to simplify the processing of the data models. By extension this leads to a simpler security model and likely a much more robust design with fewer vulnerabilities. https://kyledenhartog.com/comparing-VCs-with-zcaps/ Post Comparisons, Main Object Capabilities 2021-09-25
50 Verifiable Credentials, Object Capabilities CCG Mailing List Dave Longley Re: VCs - zCaps / OCap a Discussion TL; DR: My current view is that the main confusion here may be over the difference between VCs and LD Proofs, not VCs and ZCAPs. VCs are not a generalized container for attaching a cryptographic proof to a document. That's what LD proofs (or JOSE style proofs) are for. VCs *use* LD proofs (or JOSE style proofs) to attach an assertion proof to a document that specifically models statements made by an issuer about some subject, which is therefore inherently about the identity of that subject https://lists.w3.org/Archives/Public/public-credentials/2020Dec/0027.html Discussion Comparisons, Main Object Capabilities Credentials Community Group 2020-12-05
51 Verifiable Credentials VCWG List of Implementations for the Verifiable Credentials Data Model <ul><li>Go<ul><li><a href="https://github.com/TBD54566975/ssi-sdk/tree/main/credential">Credential Manifest Builders</a> (DI &amp; JWT)</li><li><a href="https://github.com/hyperledger/aries-framework-go">Hyperledger Aries Framework Go</a> (DI &amp; JWT)</li></ul></li><li>Java<ul><li><a href="https://github.com/danubetech/verifiable-credentials-java">Verifiable Credentials Java</a> (DI &amp; JWT)</li></ul></li><li>JavaScript/TypeScript<ul><li><a href="https://github.com/digitalbazaar/vc-js">Verifiable Credentials JS Library</a> (DI)</li><li><a href="https://github.com/transmute-industries/verifiable-data/tree/main/packages/vc.js">Verifiable Data Credential JS Library with JWT</a> (DI &amp; JWT)</li><li><a href="https://github.com/decentralized-identity/did-jwt-vc">W3C Verifiable Credentials and Presentations in JWT format</a> (JWT)</li></ul></li><li>Kotlin<ul><li><a href="https://github.com/microsoft/VerifiableCredential-SDK-Android">Verifiable Credentials in Kotlin</a> (JWT)</li></ul></li><li>Python<ul><li><a href="https://github.com/hyperledger/aries-cloudagent-python">Hyperledger Aries Cloud Agent - Python (ACA-Py)</a> (DI &amp; JWT)</li></ul></li><li>Rust<ul><li><a href="https://github.com/spruceid/didkit">DIDKit</a> (DI &amp; JWT)</li></ul></li><li>Swift<ul><li><a href="https://github.com/microsoft/VerifiableCredential-SDK-iOS">Verifiable Credentials in Swift</a> (JWT)</li></ul></li></ul> https://github.com/w3c/verifiable-credentials/blob/main/implementations.md Page Implementations 2022-06-03
52 Verifiable Credentials DSpace@MIT SolidVC : a decentralized framework for Verifiable Credentials on the web SolidVC is a decentralized Verifiable Credentials platform built with the open protocols of the Web. It is implemented on top of Solid, a Web framework developed at MIT in 2016 that allows decentralized applications to interact with personal user data to provide services in an access controlled environment. https://dspace.mit.edu/handle/1721.1/121667 https://dspace.mit.edu/bitstream/handle/1721.1/121667/1102055877-MIT.pdf.jpg?sequence=4&isAllowed=y paper Implementations 2019
53 Verifiable Credentials Paris P2P Paris P2P Festival Blockstack and Verifiable Credentials - Paris P2P Festival • Keep auth and smart contracts on-chain<br> • Keep encrypted data off-chain<br> > • Wrap everything in an easy JavaScript API https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf presentation Implementations 2020-01-10
54 Verifiable Credentials LibP2P Verifiable credentials and libp2p Hi - we’re looking into libp2p as a network stack for our application and exploring how we could integrate verifiable credentials (https://w3c.github.io/vc-data-model/ 2) infrastructure. A basic use case is that of a node being challenged to provide some specific credential to join the network. The bootstrap node handling the incoming connection should verify the credential with the issuer and complete the connection/bootstrap or terminate it. https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206 https://global.discourse-cdn.com/standard17/uploads/libp2p/original/1X/aacb49457c3aace79a1038dd02996b402260215d.png discussion Implementations 2019-07-09