Awesome-Mirrors
/
decentralized-id.github.io
mirror of https://github.com/Decentralized-ID/decentralized-id.github.io.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

split verifiable credentials to multiple posts

This commit is contained in:
⧉ infominer 2023-08-31 05:47:03 -04:00
parent b85f432c2f
commit 866beec967
3 changed files with 79 additions and 59 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

112
_data/standards.csv
View File

@ -48,63 +48,17 @@ 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,W3C,Verifiable Credentials Working Group,https://www.w3.org/2020/01/vc-wg-charter.html,,,,,,,Verifiable Credentials Working Group,The mission of the Verifiable Credentials (formerly known as Verifiable Claims) Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman.,,https://www.w3.org/2017/vc/WG/,,Working Group,,,Working Group,,,,,,,,2017-04-14,https://github.com/w3c/verifiable-claims,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,
Verifiable Credentials,VCWG,,,Manu Sporny,,,,,,Verifiable Credentials Data Model v1.1 is an official W3C standard!,"It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history",,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html,,Specificationification,,,Working Group,,,,,,,Credentials Community Group,2022-03-03,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Data Model v1.1,"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.","Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable.",https://www.w3.org/TR/2022/REC-vc-data-model-20220303/,https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg,Specificationification,RECOMMEND,,Working Group,,,,,,,Verifiable Credentials Working Group,2022-03-03,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Data Model v2.0,- The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials),"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.",https://www.w3.org/TR/vc-data-model-2.0/,https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg,Specificationification,DRAFT,,Working Group,,,,,,,Verifiable Credentials Working Group,2023-05-20,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credential Data Integrity 1.0,"This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.",,https://www.w3.org/TR/vc-data-integrity/,https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Status List v2021,"This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials.",,https://www.w3.org/TR/vc-status-list/,https://www.w3.org/TR/vc-status-list/diagrams/StatusList2021.svg,Specification,Working Draft,,Working Group,,,,,,,Verifiable Credentials WG,2023-04-27,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Implementation Guidelines 1.0,"This guide provides some examples and resources for implementing protocols which make use of verifiable credentials, beyond those available in the core specification.",,https://w3c.github.io/vc-imp-guide/,https://w3c.github.io/vc-imp-guide/diagrams/subject-ne-holder.svg,Guidance,Note,,Working Group,,,,,,,Verifiable Credentials Working Group,2023-02-03,https://github.com/w3c/vc-imp-guide,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,W3C Verifiable Credentials WG Test Suite,"Any conforming implementation MUST pass all tests in the test suite. There are multiple test suites, each of which is detailed below. You can review the current draft implementation report.",,https://w3c.github.io/vc-test-suite/,,Code,,,Working Group,,,,,,,Verifiable Credentials Working Group,2021-10-31,https://github.com/w3c/vc-test-suite/,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Use Cases,"This document does NOT attempt to define an architecture for the support of Verifiable Claims. Instead it expresses the sorts of needs that real users have that could be addressed through support for some sort of self-sovereign claim environment. It attempts to use terminology that is consistent with the other deliverables of the Verifiable Claims Working Group (you can see the relevant terms in Appendix A).<br><br>The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.","A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.",https://www.w3.org/TR/vc-use-cases/,https://i.imgur.com/J2IgVgl.png,Specification,Note,,Working Group,,,,,,,Verifiable Credentials Working Group,2019-09-24,https://github.com/w3c/vc-use-cases,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Verifiable Credentials Data Model Implementation Report 1.0,The purpose of this document is to demonstrate that there are at least two interoperable implementations of processors that are capable of generating output that is conformant to the Verifiable Credentials Data Model.,,https://w3c.github.io/vc-test-suite/implementations/,,Report,,,Working Group,,,,,,,,2021-10-30,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,The Verifiable Credential Specifications Directory,"This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual.",,https://w3c.github.io/vc-specs-dir/,,registry,,,Working Group,,,,,,,Verifiable Credentials WG,2023-04-08,https://github.com/w3c/vc-specs-dir/tree/main/specifications,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,ECDSA Cryptosuite v2019,This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1).,,https://www.w3.org/TR/vc-di-ecdsa/,,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,EdDSA Cryptosuite v2022,This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).,,https://www.w3.org/TR/vc-di-eddsa/,,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,BBS Cryptosuite v2023,This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures.,,https://www.w3.org/TR/vc-di-bbs/,,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,JSON Web Signatures for Data Integrity Proofs,This specification describes a JSON Web Signature Suite created in 2020 for the Verifiable Credentials Data Integrity Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA.,,https://www.w3.org/TR/vc-jws-2020/,,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-01-27,,,,,,,,,,,,,
Verifiable Credentials,VCWG,,,,,,,,,Securing Verifiable Credentials using JSON Web Tokens,This specification defines how Verifiable Credentials can be represented as JSON Web Tokens (JWT) [RFC7519] and secured using JSON Web Signatures (JWS) [RFC7515].,,https://www.w3.org/TR/vc-jwt/,,Specification,Working Draft,,Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
Verifiable Credentials,W3C,CCG,https://w3c-ccg.github.io/,,"Verifiable Credentials, Decentralized Identifiers",,,,,Credentials Community Group,"The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.",,https://www.w3.org/community/credentials/,,Working Group,,,Credentials Community Group,,,,,,,Credentials Community Group,2014-08-19,https://github.com/w3c-ccg/community,,,https://lists.w3.org/Archives/Public/public-credentials/,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,W3C CCG meeting transcripts,"This repo contains the meeting archives for the W3C-CCG (Credentials Community Group), including transcripts based on the IRC logs and audio files for our regular meetings, ancillary material such as slide presentations, etc. The archives for 2014-2019 can be found here.",COMMUNITY: W3C Credentials Community Group meeting transcripts - GitHub - w3c-ccg/meetings: COMMUNITY: W3C Credentials Community Group meeting transcripts,https://github.com/w3c-ccg/meetings,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,"RWOT, IIW",W3C CCG announcements,Announcements and events associated with the W3C Credentials CG,,https://github.com/w3c-ccg/announcements,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,W3C CCG Work Item Process,"This lets you write your specs in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar ""spec looking"" ReSpec format. ReSpec is just html with a javascript ReSpec library.",,https://github.com/w3c-ccg/workitem-process,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,"Global Open Badges Workgroup, Verifiable Credentials WG, Credentials Commiunity Group, Schema.org",,,,,WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials - w3c-ccg/edu_occ_verifiable_credentials,"Work on describing credentials is occurring within the IMS Global Open Badges Workgroup, W3C Verifiable Credentials Working Group, W3C Credentials Commiunity Group, Educational and Occupational Credentials in Schema.org Community Group, and Credential Engine/CTDL.<br><br>This effort will result in requirements, use cases, and/or draft specs to be formalized in the appropriate standards group",,https://github.com/w3c-ccg/edu_occ_verifiable_credentials,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,WORK ITEM: Verifiable Credentials Examples,"This GitHub Pages Website hosts example credentials, as well as documents needed to construct them. When contributing an example, you are encouraged to provide everything needed to generate an verify a credential. Do your best not to include ANY broken links or missing documentation. If possible, try to make the credential id resolvable as well.",,https://github.com/w3c-ccg/vc-examples,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
Verifiable Credentials,CCG,,Verifiable Credentials Extension Registry,,,,,,,Verifiable Credentials Extension Registry,- This document contains a list of all known Verifiable Credential extensions and their associated specifications. Credentials Community Group,,https://w3c-ccg.github.io/vc-extension-registry/,,Report,draft,,Credentials Community Group,,,,,,,Credentials Community Group,2022-11-14,,,,,,,,,,,,,
Verifiable Credentials,CCG,,Verifiable Credentials Extension Registry,Markus Sabadello,,,,,,Ed25519Signature2018,This specification describes a standard signature suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset Normalization Algorithm [RDF-DATASET-NORMALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and Ed25519 [ED25519] as the signature algorithm.,,https://w3c-ccg.github.io/lds-ed25519-2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2021-07-23,,,,,,,,,,,,,
Verifiable Credentials,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,RsaSignature2018,This specification describes the RSA Signature Suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset CANONICALIZATION Algorithm [RDF-DATASET-CANONICALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and the RS256 algorithm defined in JSON Web Signatures [RFC7515] as the signature algorithm.,,https://w3c-ccg.github.io/lds-rsa2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2020-05-26,,,,,,,,,,,,,
Verifiable Credentials,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,CredentialStatusList2017,A simple list-based mechanism for publishing and checking the status of a credential,,https://w3c-ccg.github.io/vc-csl2017/,,Report,,,Credentials Community Group,,,,Status Methods,,,Credentials Community Group,2020-12-29,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,Ecdsa Secp256k1 Signature 2019,This specification describes the Ecdsa Secp256k1 Signature created in 2019 for the Linked Data Signatures specification,,https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/,,Code,Draft,,Credentials Community Group,,,,,,,,2020-04-08,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,Verifiable Credential JSON Schemas,"The [VC_DATA_MODEL](https://www.w3.org/TR/vc-data-model/) specifies the models used for Verifiable Credentials and Verifiable Presentations, and explains the relationships between three parties: issuer, holder, and verifier. A critical piece of infrastructure out of the scope of those specifications is the Credential Schema.",A mechanism to use JSON Schemas with Verifiable Credentials - GitHub - w3c/vc-json-schema: A mechanism to use JSON Schemas with Verifiable Credentials,https://github.com/w3c-ccg/vc-json-schemas,,Code,,,Credentials Community Group,,,,,,,,2023-05-24,,,,,,,,,,,,,
Verifiable Credentials,CCG,,,,,,,,,Traceability Vocabulary v0.1,"This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to supply chain and other traceability information, similar to what is often referred to as ""provenance"", including country of origin, chemical properties, mechanical properties, and other attributes of products and materials. VCs using these terms can then be used to help determine the legitimacy of organizations participating in global trade and the status of the products and materials described therein",,https://w3c-ccg.github.io/traceability-vocab/,https://w3c-ccg.github.io/traceability-vocab/resources/product-identifier-verification-from-identification-key-license.png,Specification,v0.1,,Credentials Community Group,,,,,,,Credentials Community Group,2023-05-23,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,Claims and Credentials Working Group,"Join this group to contribute to the standards and technology that create, exchange, and verify claims and credentials in a decentralized identity ecosystem. For example, a cryptographically verifiable credential that proves an individual has a college degree or is of a certain age. Our members focus on specs that are vendor agnostic and based on industry standards.",,https://identity.foundation/working-groups/claims-credentials.html,,page,,,Claims and Credentials WG,,,,,,,,2020-09-18,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,presentation-exchange,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) - GitHub - decentralized-identity/presentation-exchange: Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission),https://github.com/decentralized-identity/presentation-exchange,,Code,,,Claims and Credentials WG,,,,,,,,2023-05-31,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,presentation-request,Requirements Analysis and Protocol Design for a VC Presentation Request Format,Requirements Analysis and Protocol Design for a VC Presentation Request Format - GitHub - decentralized-identity/presentation-request: Requirements Analysis and Protocol Design for a VC Presentation Request Format,https://github.com/decentralized-identity/presentation-request,,Code,,,Claims and Credentials WG,,,,,,,,2020-01-08,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,Credential Manifest,"Credential Manifests do not themselves define the contents of the output credential(s), the process the Issuer uses to evaluate the submitted inputs, or the protocol Issuers, Subjects, and their User Agents rely on to negotiate credential issuance. Instead, Credential Manifests are a data model for issuers to publish and/or send individually to would-be holders, allowing the software of the latter to understand and negotiate an issuance process.",,https://identity.foundation/credential-manifest/,,page,,,Claims and Credentials WG,,,,,,,,2023-05-04,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Kyle Den Hartog,,,,,,Example Design of an Authorization System with Verifiable Credentials and the Tradeoffs,"The primary focus of this blog post is to highlight the different problems that are likely to occur when going down the path of building an authorization system with verifiable credentials. I’ll be sure to keep things at a higher level so that anyone can understand these tradeoffs, but take you through the details that would be thought through by an architect designing the system.",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Development,,,,,,,,2021-06-22,,,,,,,,,,,,,
Verifiable Credentials,51 Nodes,,,,,,,,,Indexing and Querying Revoked Verifiable Credentials,this article describes a simple approach to revoke verifiable credentials and a decentralized and efficient way to index and query those revoked credentials using the [Graph protocol](https://thegraph.com/en/).,"Due to its immutability and censorship resistance, the Blockchain seems to be a suitable place to manage identities and credentials. However, querying the data on the blockchain in a trusted and…",https://medium.com/51nodes/indexing-and-querying-revoked-verifiable-credentials-e229dc2781d4,,Post,,,Development,,,,,,,,2022-07-01,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Nikos Fotiou ,,,,,,VC Issuance based on OAuth 2.0,"We design, implement, and evaluate a solution for achieving continuous authorization of HTTP requests exploiting Verifiable Credentials (VCs) and OAuth 2.0. Specifically, we develop a VC issuer that acts as an OAuth 2.0 authorization server, a VC verifier that transparently protects HTTP-based resources, and a VC wallet implemented as a browser extension capable of injecting the necessary authentication data in HTTP requests without needing user intervention.",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0084.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-14,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Orie Steele,,,,,,Supporting VC-JWT and BBS+ Presentation Exchange in the VC-HTTP-API,"[https://github.com/OR13/GNARLY](https://github.com/OR13/GNARLY)  (while we wait for a better name...)<br><br>This demo API and Spec has a number of improvements over the current<br><br>VC-HTTP-API, including tested support for VC-JWT, JsonWebSignature2020 and<br><br>BBS+ Selective Disclosure Presentation Exchange.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0313.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-31,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,Joe Andrieu,,,,,,Updated VC-API diagram for Supply Chain flow,I updated the supply chain version of the data flow diagram for verification. ,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,https://i.imgur.com/mH5TBtU.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-09-28,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Manu Sporny,,,,,,re: VC API: handling large documents client to server,"Typical solutions to this problem require that you put the binary data outside of the VC, if at all possible. This works well for common static images such as logos. It is also possible to split the VC into two VCs... one with the machine-readable data from the issuer (with a digital signature) and one with the image data from any source (without a digital signature, since, if hashlinked, the signature will verify the validity of the image data). That latter approach can be more privacy preserving AND more complex than many might feel is necessary.",,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0035.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-02-10,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Manu Sporny,,,,,,VC-API interoperability test suites ready for experimental integration,* [The VC API test suite for basic issuer interop is here](https://w3c-ccg.github.io/vc-api-issuer-test-suite/)<br>* [The VC API test suite for basic verifier interop is here](https://w3c-ccg.github.io/vc-api-verifier-test-suite/)<br>* [The Data Integrity test suite for Ed25519Signature2020 interop is here](https://w3c-ccg.github.io/di-ed25519-test-suite/),,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-26,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Manu Sporny,,,,,,Cross-industry VC API test suite achieves first multi-vendor interop for issue/verify,We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for the VC Issuer API and VC Verifier API. The test suites test the OAS definition files (which are used to generate the specification):<br>* [2.1 Verify Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity)<br>* [2.1 Issue Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-issuer-test-suite/#Issue%20Credential%20-%20Data%20Integrity),,https://lists.w3.org/Archives/Public/public-credentials/2022May/0041.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-05-18,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Joe Andrieu,,,,,,Diagrams for VC HTTP API work [was Re: [AGENDA] VC HTTP API Work Item - August 17th 2021],"a. *Holder* The entity who holds the VC once issued and later presents it for verification.<br>b. *Holder Application *The software or service that allows holders to manage their credentials. Often called a wallet. For symmetry, it could be called a Holder Service.<br>c. *Storage Service *The software or service that actually stores VCs long term (on behalf of the holder)<br>d. *Issuer Role* The website or software that provides issuing functionality to a holder on behalf of that issuer)<br>e. *Issuer Service* Software or service that actually signs VCs and VPs) This component is used by both the issuer (to mint VCs) and the holder (to create VPs for presentation)<br>f. *Verifier Role* The website or software that uses a Verification Service as part of its decision making process for providing services to holders.<br>g. *Verifier Service *The software or service that verifies VCs and VPs by checking proofs and checking status.",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0231.html,https://i.imgur.com/4hCNLVA.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-08-16,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Brian Richter,,,,,,Issuer API Cross Trust Boundary Scoping - VC-HAPI (f.k.a. VC-HTTP-API),I think I'm starting to understand how RAR fits into this picture. This decision can be made for us by punting the question to the authorization process entirely. With RAR we can force the user to authorize for the actual subject they are issuing the credential about. Is Alice authorized to issue VCs with claims about did:example:12345? To answer that question Alice asks for a token with the following RAR request,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0263.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-24,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Justin Richer,,,,,,RAR Structures for VC HTTP API,"It seemed like a good idea when I first invented it a decade ago:[https://blue-button.github.io/blue-button-plus-pull/#scopes](https://blue-button.github.io/blue-button-plus-pull/#scopes) or when it got pulled into other efforts like [https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html](https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html)… and Orie even suggested the following set of parameterized scopes for this API:<br>'create:credentials': Grants permission to create credentials<br>'derive:credentials': Grants permission to derive credentials<br>'create:presentations': Grants permission to create presentations<br>'verify:presentations': Grants permission to verify presentations<br>'exchange:presentations': Grants permission to exchange presentations<br>So what’s the problem? I can say with full confidence after years of experience building and deploying systems to support parameterized scopes like this that they are fragile, awkward, and lead to insecure corner cases.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0208.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-21,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Manu Sporny,,,,,,Bikeshed: Renaming the VC HTTP API,"the fundamental issue is that stringing a bunch of consonants together (""HTTP"") rarely leads to something easy to say in conversation.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0131.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-17,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Kerri Lemoie,,,,,,Question About Signatures & Contexts,Is a VC still considered to be valid if it contains fields that are not described in its context file(s)? Does it depend on the signature type?,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0290.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-30,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Bob Wyman,,,,,,Any Good use case of PAM (Privileged account Management) using Vcs,"A common example of this is when someone uses a ""Power of Attorney,"" to sign a contract. When they do, they typically sign documents with their own names and an annotation ""on behalf of,"" ""for,"" or ""by power of attorney,"" they don't forge the signature of the one who granted the power of attorney.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0028.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-11-06,,,,,,,,,,,,,
Verifiable Credentials,Mattr,,,,,,,,,Paper based Verifiable Credentials,Paper-based Verifiable Credentials allow us to have a low-tech solution for adopting VC's in situations where access to a phone cannot be guaranteed. This presentation looks at how this solution can be used to aid with the distribution of Vaccine Credentials.,Paper-based verifiable credentials allow us to have a low-tech solution for adopting verifiable credential's in situations where access to a phone cannot be ...,https://www.youtube.com/watch?v=EXvWxFjHvdY,,Video,,,Development,,,,,,,,2021-03-02,,,,,,,,,,,,,
Verifiable Credentials,LPFH,,,Kaliya IdentityWoman,,,,,,Verifiable Credentials Flavors Explained,"Below are the three primary flavors of VCs discussed in this paper. All have more than one critical implementation in various stages of production. There are advocated variations of these types, but they are less common.<br>* JSON-LD family with LD Signatures or with BBS+ Signatures that enable Zero Knowledge Proofs (ZKP or ZKPs)<br>* JSON with JSON Web Signatures, precisely in the form of a JSON Web Token (JWT)<br>* ZKP with Camenisch-Lysyanskaya Signatures (ZKP-CL)",,https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf,,Post,,,Varieties,,,,,,,,2021-02,,,,,,,,,,,,,
"Standards, Verifiable Credentials",LFPH,,https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf,Lucy Yang,,,,,,The Flavors of Verifiable Credentials,The differences between the different flavors of VCs for technically inclined readers. It elaborated on the differences between JSON and JSON-LD and articulated differences between the two different implementations of ZKP style credentials. The ‘Journey of a VC’ section articulated all steps where VCs are active and highlighted the differences in how different VC flavors ’behave’.,,https://www.lfph.io/2021/02/11/cci-verifiable-credentials-flavors-and-interoperability-paper/,,Paper,,,"Varieties, Decentralized Identity Stack",,,,,,,,2021-11-11,,,,,,,,,,,,,
Verifiable Credentials,Evernym,,,Daniel Hardman,,,,,,Categorizing Verifiable Credentials - Evernym,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation.,https://www.evernym.com/blog/categorizing-verifiable-credentials/,,Post,,,Varieties,,,,,,,,2019-11-07,,,,,,,,,,,,,
Verifiable Credentials,DIF,,https://github.com/decentralized-identity/vc-spec-map/releases/tag/v1.2.0,Michael Ruminer,,,,,,Verifiable Credentials Specification Relationships,"diagrams and documentation on the relationship of verfiable credential specifications<br><br>The current release contains some of the most core specifications and their related specs in a diagram. It does not yet address some of the items especially under DIF work groups for secure data storage, SIOP, Sidetree etc.","""Good for anyone but especially useful when trying to jump in on the deep end. If you walk even this limited tree of specs you know a lot"" - @michaelruminer",https://github.com/decentralized-identity/vc-spec-map,http://decentralized-id.com/images/VC-spec-map.webp,infographic,,,Interoperability,,,,,,,,2021-05-27,,,,,,,,,,,,,
Verifiable Credentials,Evernym,,,Brent Zundel,,,,,,Why the Verifiable Credentials Community Should Converge on BBS+,"BBS+ LD-Proofs use JSON-LD schemas, so credentials that use them can have a rich, hierarchical set of attributes. Instead of the heavy-handed mechanism for the encoding and canonicalization of attributes values that we’d imagined for Rich Schemas, they use RDF canonicalization and a hash function. Rather than expanding the credential definition, they discarded it, taking advantage of some properties of BBS+ keys which allow for deterministic expansion.",BBS+ ZKP signatures: The breakthrough the industry has been looking for to converge on a universal format for privacy-respecting VCs.,https://www.evernym.com/blog/bbs-verifiable-credentials/,,Post,,,Varieties,,,,,,,,2021-03-24,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Steve Lockstep,,,,,,The original #VerifiableCredentials were PKI-based SIM cards and EMV cards.,"These bind key pairs to individuals, and to signed assertions (account numbers) to deliver provenance, fidelity and proof of possession. [https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little](https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little)<br>$5",,https://twitter.com/Steve_Lockstep/status/1419935186188341249,https://i.imgur.com/ucAVxCX.png,tweet,,,Varieties,,,,,,,,2021-06-27,,,,,,,,,,,,,
Verifiable Credentials,CCG Mailing List,,,Anil John,,,,,,FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format,"We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br> … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br> - Credential Data Model Representation Syntax<br> - Credential Data Model Proof Format",,https://lists.w3.org/Archives/Public/public-credentials/2022Sep/0253.html,,Discussion,,,Interoperability,,,,,,,Credentials Community Group,2022-09-29,,,,,,,,,,,,,
Verifiable Credentials,DIF,,,,,,,,,Interoperability Mapping Exercise,The archive and information hub for the cross-community interoperability project. Focus is on education and familiarity for various efforts across multiple groups for interoperable decentralized identity infrastructure.,,https://github.com/decentralized-identity/interoperability/blob/master/assets/interoperability-mapping-exercise-10-12-20.pdf,https://i.imgur.com/QvpMl6M.png,infographic,,,Interoperability,,,,,,,,2020-10-13,,,,,,,,,,,,,
Verifiable Credentials,Github,,,creatornader,,,,,,Decentralized Identity Standards.md,"Decentralized Identifiers (DIDs), Decentralized Identifier (DID) Resolution, DID Spec Registries, DID Use Cases, DID Rubric, DID Key, DID Web, WebCrypto, WebAuthn, WebKMS, Verifiable Credentials (VCs), VC Use Cases, VC JSON Schemas, Credential Revocation List, Credential Handler API (CHAPI), Verifiable Presentation Request, JSON Linked Data (JSON-LD), CBOR Linked Data (CBOR-LD), Authorization Capabilities (ZCAP-LD), Linked Data Security Vocab, Linked Data Citizenship Vocab, Linked Data Traceability Vocab, Linked Data Cryptographic Suite Registry, Linked Data Proofs, Linked Data Proofs BBS+ Signatures, Universal Wallet, Encrypted Data Vaults (EDVs), Data Privacy Vocabulary, Data Minimization, ActivityPub, Confidential Storage, DID Peer, DIDComm Messaging, Well Known DID Configuration, Self-Issued DID Profile for OpenID, Verifiable Presentation Exchange, Identity Hubs, Credential Manifest, Sidetree, Key Event Receipt Infrastructure (KERI), OAuth 2.0, Grant Negotiation Access Protocol (GNAP), JWA/JWK, JWT/JWS/JWE, JSON Web Message (JWM), HTTP Signatures, Hashlink, BBS+ Signatures Scheme, Biometric Service Providers (BSPs), Aries RFCs, Interop Test Suite, The Trust Over IP (ToIP) Stack, Rich Schemas, Chained Credentials, Data Overlays, Data Consent Lifecycle, Indirect Identity Control, Anoncreds, Machine-Readable Trust Frameworks, Decentralized Key Management System (DKMS), eXtensible Data Interchange (XDI), OpenID Connect (OIDC), OIDC Credential Provider, User-Managed Access (UMA) 2.0, Consent Receipts, Blinding Identity Taxonomy (BIT)",,https://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725,,gist,,,Interoperability,,,,,,,,2020-11-25,,,,,,,,,,,,,
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,,,,,,,,,,,,,
Verifiable Credentials,Ontology,,,,,,,,,Verifiable Claim Protocol,The entire workflow of the verifiable claim is shown in the figure below. It contains three major parts:<br><br>Request claim;<br>Issue claim;<br>Verify claim.,Ontology decentralized identification protocol based on W3C DID specifications. - ontology-DID/claim_spec.md at master · ontio/ontology-DID,https://github.com/ontio/ontology-DID/blob/master/docs/en/claim_spec.md,,Specification,,,Implementations,,,,,,,,2017-03-20,,,,,,,,,,,,,
Verifiable Credentials,Crossword ,,,,Cybersecurity NGI,,,,,Crossword wins NGI Atlantic funds for Verifiable Credentials project,European Commission’s Next Generation Internet (NGI) initiative to lead a project to test the OpenID Foundation’s protocols for transferring verifiable credentials. Crossword’s partners in this project are Spruce Inc from the USA and Fraunhofer from Germany,,https://www.crosswordcybersecurity.com/post/next-generation-internet-grant-win,"https://static.wixstatic.com/media/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg/v1/fill/w_1000,h_563,al_c,q_85,usm_0.66_1.00_0.01/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg",Post,,,Implementations,,,,,,,,2022-08-04,,,,,,,,,,,,,
Verifiable Credentials,Identity.com,,,,,,,,,Identity.com Verifiable Credential Library,"This Javascript Library provides functionality around Verifiable Credentials (VC), a W3C standard. Enables Validators to issue, Credential Wallets to verify, filter and Requesters to verify credentials.","Verifiable Credential and Attestation Library. Latest version: 3.0.2, last published: 4 months ago. Start using @identity.com/credential-commons in your project by running `npm i @identity.com/credential-commons`. There are 3 other projects in the npm registry using @identity.com/credential-commons.",https://www.npmjs.com/package/@identity.com/credential-commons,,code,,,Implementations,,,,,,,,2023-02-13,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Samuel Smith,,,,,,VC Spec Enhancement Proposal,"the VC standard appears to be an adoption vector for Linked Data, not the other way around. My overriding interest is that the concept of a VC as a securely attributable statement is a very powerful and attractive one and therefore should be widely adopted. We should therefore be picking the best technologies that best support broad VC adoption, not the other way around.",,https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md,,Paper,,,Literature,,,,,,,,2022-04-04,,,,,,,,,,,,,
Verifiable Credentials,Personal,,,Phil Windley,,,,,,Verifiable Credential Exchange,"Multi-source identity (MSI) depends on issuing, exchanging, and verifying digital credentials. The specification for verifiable credentials is being formulated by the World Wide Web Consortium’s Verifiable Credentials Working Group. Verifiable credentials provide a standard way to express credentials in a way that is cryptographically secure, privacy respecting, and automatically verifiable.","Verifiable credential exchange is the foundation of decentralized, online identity. This post describes how it works.",https://www.windley.com/archives/2018/12/verifiable_credential_exchange.shtml,https://www.windley.com/archives/2018/12/claim_issuing_and_presenting.png,Post,,,Literature,,,,,,,,2018-12-10,,,,,,,,,,,,,
Verifiable Credentials,"Service-centric Networking, Telekom Innovation Laboratories, Technische Universiät Berlin",,,"Zoltán András Lux, Felix Beierle, Sebastian Zickau, Sebastian Göndör",,,,,,Full-text Search for Verifiable Credential Metadata on Distributed Ledgers,"The proposed solution is able to find credential types based on textual input from the user by using a full-text search engine and maintaining a local copy of the ledger. Thus, we do not need to rely on information about credentials coming from a very large candidate pool of third parties we would need to trust, such as the website of a company displaying its own identifier and a list of issued credentials. We have also proven the feasiblity of the concept by implementing and evaluating a prototype of the full-text credential metadata search service.",,https://arxiv.org/abs/1909.02895,,Paper,,,Literature,,,,,,,,2019-09-06,,,,,,,,,,,,,
@ -121,8 +75,56 @@ Verifiable Credentials,LTO Network,,,,Sphereon,,,,,25 Use Cases for Verifiable C
Verifiable Credentials,CCG Mailing List,,,Michael Herman,,,,,,Verifiable Credential Notarization and Third-Party Notary Services Providers: User Scenarios,User Scenario A: Alice self-issues a blood pressure home reading (BPHR) credential to Dr. Bob's Clinic using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network.<br><br>User Scenario B: The Province of Sovronia issues a Sovronia Driver's License to Alice using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network.,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0109.html,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/att-0109/image003.jpg,user journies,,,Use Case,,,,,,,Credentials Community Group,2021-07-15,,,,,,,,,,,,,
Verifiable Credentials,IDCommons,,,"Gena Morgan, Kevin Dean",IDCommons,,,,IIW,Verifiable Credentials for Authentic Data in the Supply Chain,"Using DiDs and VCs for verifiable product data in supply chains, leveraging the largest supply chain standard system in the world,<br><br>2.5 million users companies, over 6 billion product scans per day<br><br>Product data and attestations from a number of various authoritative sources<br><br>Leverage DIDs/VCs for distributed data sharing, verification",,https://iiw.idcommons.net/10G/_Verifiable_Credentials_for_Authentic_Data_in_the_Supply_Chain,,Session Notes,,,Use Case,,,,,,,,2021-05-06,,,,,,,,,,,,,
Verifiable Credentials,IDCommons,,,Mahmoud Alkhraishi,IDCommons,,,,IIW,Verifiable Credentials for Assets,General Framework on how to think of VCs for Assets including leveraging GS1 and other vocabularies in the traceability vocab.<br><br>Requirements and Opportunities that block adoption of VCs in Supply chains,,https://iiw.idcommons.net/21E/_Verifiable_Credentials_for_Assets_30_min,,Session Notes,,,Use Case,,,,,,,,2021-05-07,,,,,,,,,,,,,
Verifiable Credentials,Trusted Digital Web,,,,,,,,,Using Paper-based Structured Credentials to Humanize Verifiable Credentials,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by...,https://www.youtube.com/watch?v=kM30pd3w8qE,,Video,Rough Cut,,User Experience,,,,,,,,2021-11-19,,,,,,,,,,,,,
Verifiable Credentials,WebofTrustInfo,,,Manu Sporny,,,,,RWoT,Rendering Verifiable Credentials,"This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials.",,https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md,,Paper,,,User Experience,,,,,,,,2022-07-17,,,,,,,,,,,,,
VCs Development,W3C,Verifiable Credentials Working Group,https://www.w3.org/2020/01/vc-wg-charter.html,,,,,,,Verifiable Credentials Working Group,The mission of the Verifiable Credentials (formerly known as Verifiable Claims) Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman.,,https://www.w3.org/2017/vc/WG/,,Working Group,,,Verifiable Credentials Working Group,,,,,,,,2017-04-14,https://github.com/w3c/verifiable-claims,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,,,,https://lists.w3.org/Archives/Public/public-vc-wg/,,,
VCs Development,VCWG,,,Manu Sporny,,,,,,Verifiable Credentials Data Model v1.1 is an official W3C standard!,"It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history",,https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html,,Specificationification,,,Verifiable Credentials Working Group,,,,,,,Credentials Community Group,2022-03-03,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model v1.1,"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.","Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable.",https://www.w3.org/TR/2022/REC-vc-data-model-20220303/,https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg,Specificationification,RECOMMEND,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2022-03-03,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model v2.0,- The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials),"Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.",https://www.w3.org/TR/vc-data-model-2.0/,https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg,Specificationification,DRAFT,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2023-05-20,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credential Data Integrity 1.0,"This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs.",,https://www.w3.org/TR/vc-data-integrity/,https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Status List v2021,"This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials.",,https://www.w3.org/TR/vc-status-list/,https://www.w3.org/TR/vc-status-list/diagrams/StatusList2021.svg,Specification,Working Draft,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials WG,2023-04-27,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Implementation Guidelines 1.0,"This guide provides some examples and resources for implementing protocols which make use of verifiable credentials, beyond those available in the core specification.",,https://w3c.github.io/vc-imp-guide/,https://w3c.github.io/vc-imp-guide/diagrams/subject-ne-holder.svg,Guidance,Note,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2023-02-03,https://github.com/w3c/vc-imp-guide,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,W3C Verifiable Credentials WG Test Suite,"Any conforming implementation MUST pass all tests in the test suite. There are multiple test suites, each of which is detailed below. You can review the current draft implementation report.",,https://w3c.github.io/vc-test-suite/,,Code,,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2021-10-31,https://github.com/w3c/vc-test-suite/,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Use Cases,"This document does NOT attempt to define an architecture for the support of Verifiable Claims. Instead it expresses the sorts of needs that real users have that could be addressed through support for some sort of self-sovereign claim environment. It attempts to use terminology that is consistent with the other deliverables of the Verifiable Claims Working Group (you can see the relevant terms in Appendix A).<br><br>The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.","A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address.",https://www.w3.org/TR/vc-use-cases/,https://i.imgur.com/J2IgVgl.png,Specification,Note,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials Working Group,2019-09-24,https://github.com/w3c/vc-use-cases,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Verifiable Credentials Data Model Implementation Report 1.0,The purpose of this document is to demonstrate that there are at least two interoperable implementations of processors that are capable of generating output that is conformant to the Verifiable Credentials Data Model.,,https://w3c.github.io/vc-test-suite/implementations/,,Report,,,Verifiable Credentials Working Group,,,,,,,,2021-10-30,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,The Verifiable Credential Specifications Directory,"This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual.",,https://w3c.github.io/vc-specs-dir/,,registry,,,Verifiable Credentials Working Group,,,,,,,Verifiable Credentials WG,2023-04-08,https://github.com/w3c/vc-specs-dir/tree/main/specifications,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,ECDSA Cryptosuite v2019,This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1).,,https://www.w3.org/TR/vc-di-ecdsa/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,EdDSA Cryptosuite v2022,This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519).,,https://www.w3.org/TR/vc-di-eddsa/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,BBS Cryptosuite v2023,This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures.,,https://www.w3.org/TR/vc-di-bbs/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-18,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,JSON Web Signatures for Data Integrity Proofs,This specification describes a JSON Web Signature Suite created in 2020 for the Verifiable Credentials Data Integrity Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA.,,https://www.w3.org/TR/vc-jws-2020/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-01-27,,,,,,,,,,,,,
VCs Development,VCWG,,,,,,,,,Securing Verifiable Credentials using JSON Web Tokens,This specification defines how Verifiable Credentials can be represented as JSON Web Tokens (JWT) [RFC7519] and secured using JSON Web Signatures (JWS) [RFC7515].,,https://www.w3.org/TR/vc-jwt/,,Specification,Working Draft,,Verifiable Credentials Working Group,,,,Cryptography,,,Verifiable Credentials WG,2023-05-15,,,,,,,,,,,,,
VCs Development,W3C,CCG,https://w3c-ccg.github.io/,,"Verifiable Credentials, Decentralized Identifiers",,,,,Credentials Community Group,"The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations.",,https://www.w3.org/community/credentials/,,Working Group,,,Credentials Community Group,,,,,,,Credentials Community Group,2014-08-19,https://github.com/w3c-ccg/community,,,https://lists.w3.org/Archives/Public/public-credentials/,,,,,,,,,
VCs Development,CCG,,,,,,,,,W3C CCG meeting transcripts,"This repo contains the meeting archives for the W3C-CCG (Credentials Community Group), including transcripts based on the IRC logs and audio files for our regular meetings, ancillary material such as slide presentations, etc. The archives for 2014-2019 can be found here.",COMMUNITY: W3C Credentials Community Group meeting transcripts - GitHub - w3c-ccg/meetings: COMMUNITY: W3C Credentials Community Group meeting transcripts,https://github.com/w3c-ccg/meetings,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,"RWOT, IIW",W3C CCG announcements,Announcements and events associated with the W3C Credentials CG,,https://github.com/w3c-ccg/announcements,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,,W3C CCG Work Item Process,"This lets you write your specs in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar ""spec looking"" ReSpec format. ReSpec is just html with a javascript ReSpec library.",,https://github.com/w3c-ccg/workitem-process,,Page,,,Credentials Community Group,,,,,,,,,,,,,,,,,,,,,
VCs Development,CCG,,,,"Global Open Badges Workgroup, Verifiable Credentials WG, Credentials Commiunity Group, Schema.org",,,,,WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials - w3c-ccg/edu_occ_verifiable_credentials,"Work on describing credentials is occurring within the IMS Global Open Badges Workgroup, W3C Verifiable Credentials Working Group, W3C Credentials Commiunity Group, Educational and Occupational Credentials in Schema.org Community Group, and Credential Engine/CTDL.<br><br>This effort will result in requirements, use cases, and/or draft specs to be formalized in the appropriate standards group",,https://github.com/w3c-ccg/edu_occ_verifiable_credentials,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,,WORK ITEM: Verifiable Credentials Examples,"This GitHub Pages Website hosts example credentials, as well as documents needed to construct them. When contributing an example, you are encouraged to provide everything needed to generate an verify a credential. Do your best not to include ANY broken links or missing documentation. If possible, try to make the credential id resolvable as well.",,https://github.com/w3c-ccg/vc-examples,,Code,,,Credentials Community Group,,,,,,,Credentials Community Group,,,,,,,,,,,,,,
VCs Development,CCG,,Verifiable Credentials Extension Registry,,,,,,,Verifiable Credentials Extension Registry,- This document contains a list of all known Verifiable Credential extensions and their associated specifications. Credentials Community Group,,https://w3c-ccg.github.io/vc-extension-registry/,,Report,draft,,Credentials Community Group,,,,,,,Credentials Community Group,2022-11-14,,,,,,,,,,,,,
VCs Development,CCG,,Verifiable Credentials Extension Registry,Markus Sabadello,,,,,,Ed25519Signature2018,This specification describes a standard signature suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset Normalization Algorithm [RDF-DATASET-NORMALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and Ed25519 [ED25519] as the signature algorithm.,,https://w3c-ccg.github.io/lds-ed25519-2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2021-07-23,,,,,,,,,,,,,
VCs Development,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,RsaSignature2018,This specification describes the RSA Signature Suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset CANONICALIZATION Algorithm [RDF-DATASET-CANONICALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and the RS256 algorithm defined in JSON Web Signatures [RFC7515] as the signature algorithm.,,https://w3c-ccg.github.io/lds-rsa2018/,,Report,draft,,Credentials Community Group,,,,Proof Methods,,,Credentials Community Group,2020-05-26,,,,,,,,,,,,,
VCs Development,CCG,,Verifiable Credentials Extension Registry,"Manu Sporny, Dave Longley",,,,,,CredentialStatusList2017,A simple list-based mechanism for publishing and checking the status of a credential,,https://w3c-ccg.github.io/vc-csl2017/,,Report,,,Credentials Community Group,,,,Status Methods,,,Credentials Community Group,2020-12-29,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,,Ecdsa Secp256k1 Signature 2019,This specification describes the Ecdsa Secp256k1 Signature created in 2019 for the Linked Data Signatures specification,,https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/,,Code,Draft,,Credentials Community Group,,,,,,,,2020-04-08,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,,Verifiable Credential JSON Schemas,"The [VC_DATA_MODEL](https://www.w3.org/TR/vc-data-model/) specifies the models used for Verifiable Credentials and Verifiable Presentations, and explains the relationships between three parties: issuer, holder, and verifier. A critical piece of infrastructure out of the scope of those specifications is the Credential Schema.",A mechanism to use JSON Schemas with Verifiable Credentials - GitHub - w3c/vc-json-schema: A mechanism to use JSON Schemas with Verifiable Credentials,https://github.com/w3c-ccg/vc-json-schemas,,Code,,,Credentials Community Group,,,,,,,,2023-05-24,,,,,,,,,,,,,
VCs Development,CCG,,,,,,,,,Traceability Vocabulary v0.1,"This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to supply chain and other traceability information, similar to what is often referred to as ""provenance"", including country of origin, chemical properties, mechanical properties, and other attributes of products and materials. VCs using these terms can then be used to help determine the legitimacy of organizations participating in global trade and the status of the products and materials described therein",,https://w3c-ccg.github.io/traceability-vocab/,https://w3c-ccg.github.io/traceability-vocab/resources/product-identifier-verification-from-identification-key-license.png,Specification,v0.1,,Credentials Community Group,,,,,,,Credentials Community Group,2023-05-23,,,,,,,,,,,,,
VCs Development,DIF,,,,,,,,,Claims and Credentials Working Group,"Join this group to contribute to the standards and technology that create, exchange, and verify claims and credentials in a decentralized identity ecosystem. For example, a cryptographically verifiable credential that proves an individual has a college degree or is of a certain age. Our members focus on specs that are vendor agnostic and based on industry standards.",,https://identity.foundation/working-groups/claims-credentials.html,,page,,,Claims and Credentials Working Group,,,,,,,,2020-09-18,,,,,,,,,,,,,
VCs Development,DIF,,,,,,,,,presentation-exchange,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions,Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) - GitHub - decentralized-identity/presentation-exchange: Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission),https://github.com/decentralized-identity/presentation-exchange,,Code,,,Claims and Credentials Working Group,,,,,,,,2023-05-31,,,,,,,,,,,,,
VCs Development,DIF,,,,,,,,,presentation-request,Requirements Analysis and Protocol Design for a VC Presentation Request Format,Requirements Analysis and Protocol Design for a VC Presentation Request Format - GitHub - decentralized-identity/presentation-request: Requirements Analysis and Protocol Design for a VC Presentation Request Format,https://github.com/decentralized-identity/presentation-request,,Code,,,Claims and Credentials Working Group,,,,,,,,2020-01-08,,,,,,,,,,,,,
VCs Development,DIF,,,,,,,,,Credential Manifest,"Credential Manifests do not themselves define the contents of the output credential(s), the process the Issuer uses to evaluate the submitted inputs, or the protocol Issuers, Subjects, and their User Agents rely on to negotiate credential issuance. Instead, Credential Manifests are a data model for issuers to publish and/or send individually to would-be holders, allowing the software of the latter to understand and negotiate an issuance process.",,https://identity.foundation/credential-manifest/,,page,,,Claims and Credentials Working Group,,,,,,,,2023-05-04,,,,,,,,,,,,,
VCs Development,Personal,,,Kyle Den Hartog,,,,,,Example Design of an Authorization System with Verifiable Credentials and the Tradeoffs,"The primary focus of this blog post is to highlight the different problems that are likely to occur when going down the path of building an authorization system with verifiable credentials. I’ll be sure to keep things at a higher level so that anyone can understand these tradeoffs, but take you through the details that would be thought through by an architect designing the system.",,https://kyledenhartog.com/example-authz-with-VCs/,,Post,,,Development,,,,,,,,2021-06-22,,,,,,,,,,,,,
VCs Development,51 Nodes,,,,,,,,,Indexing and Querying Revoked Verifiable Credentials,this article describes a simple approach to revoke verifiable credentials and a decentralized and efficient way to index and query those revoked credentials using the [Graph protocol](https://thegraph.com/en/).,"Due to its immutability and censorship resistance, the Blockchain seems to be a suitable place to manage identities and credentials. However, querying the data on the blockchain in a trusted and…",https://medium.com/51nodes/indexing-and-querying-revoked-verifiable-credentials-e229dc2781d4,,Post,,,Development,,,,,,,,2022-07-01,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Nikos Fotiou ,,,,,,VC Issuance based on OAuth 2.0,"We design, implement, and evaluate a solution for achieving continuous authorization of HTTP requests exploiting Verifiable Credentials (VCs) and OAuth 2.0. Specifically, we develop a VC issuer that acts as an OAuth 2.0 authorization server, a VC verifier that transparently protects HTTP-based resources, and a VC wallet implemented as a browser extension capable of injecting the necessary authentication data in HTTP requests without needing user intervention.",,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0084.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-14,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Orie Steele,,,,,,Supporting VC-JWT and BBS+ Presentation Exchange in the VC-HTTP-API,"[https://github.com/OR13/GNARLY](https://github.com/OR13/GNARLY)  (while we wait for a better name...)<br><br>This demo API and Spec has a number of improvements over the current<br><br>VC-HTTP-API, including tested support for VC-JWT, JsonWebSignature2020 and<br><br>BBS+ Selective Disclosure Presentation Exchange.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0313.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-31,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,Joe Andrieu,,,,,,Updated VC-API diagram for Supply Chain flow,I updated the supply chain version of the data flow diagram for verification. ,,https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html,https://i.imgur.com/mH5TBtU.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-09-28,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,re: VC API: handling large documents client to server,"Typical solutions to this problem require that you put the binary data outside of the VC, if at all possible. This works well for common static images such as logos. It is also possible to split the VC into two VCs... one with the machine-readable data from the issuer (with a digital signature) and one with the image data from any source (without a digital signature, since, if hashlinked, the signature will verify the validity of the image data). That latter approach can be more privacy preserving AND more complex than many might feel is necessary.",,https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0035.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-02-10,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,VC-API interoperability test suites ready for experimental integration,* [The VC API test suite for basic issuer interop is here](https://w3c-ccg.github.io/vc-api-issuer-test-suite/)<br>* [The VC API test suite for basic verifier interop is here](https://w3c-ccg.github.io/vc-api-verifier-test-suite/)<br>* [The Data Integrity test suite for Ed25519Signature2020 interop is here](https://w3c-ccg.github.io/di-ed25519-test-suite/),,https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-04-26,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,Cross-industry VC API test suite achieves first multi-vendor interop for issue/verify,We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for the VC Issuer API and VC Verifier API. The test suites test the OAS definition files (which are used to generate the specification):<br>* [2.1 Verify Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity)<br>* [2.1 Issue Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-issuer-test-suite/#Issue%20Credential%20-%20Data%20Integrity),,https://lists.w3.org/Archives/Public/public-credentials/2022May/0041.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2022-05-18,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Joe Andrieu,,,,,,Diagrams for VC HTTP API work [was Re: [AGENDA] VC HTTP API Work Item - August 17th 2021],"a. *Holder* The entity who holds the VC once issued and later presents it for verification.<br>b. *Holder Application *The software or service that allows holders to manage their credentials. Often called a wallet. For symmetry, it could be called a Holder Service.<br>c. *Storage Service *The software or service that actually stores VCs long term (on behalf of the holder)<br>d. *Issuer Role* The website or software that provides issuing functionality to a holder on behalf of that issuer)<br>e. *Issuer Service* Software or service that actually signs VCs and VPs) This component is used by both the issuer (to mint VCs) and the holder (to create VPs for presentation)<br>f. *Verifier Role* The website or software that uses a Verification Service as part of its decision making process for providing services to holders.<br>g. *Verifier Service *The software or service that verifies VCs and VPs by checking proofs and checking status.",,https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0231.html,https://i.imgur.com/4hCNLVA.png,Discussion,,,Development,,,,,,,Credentials Community Group,2021-08-16,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Brian Richter,,,,,,Issuer API Cross Trust Boundary Scoping - VC-HAPI (f.k.a. VC-HTTP-API),I think I'm starting to understand how RAR fits into this picture. This decision can be made for us by punting the question to the authorization process entirely. With RAR we can force the user to authorize for the actual subject they are issuing the credential about. Is Alice authorized to issue VCs with claims about did:example:12345? To answer that question Alice asks for a token with the following RAR request,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0263.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-24,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Justin Richer,,,,,,RAR Structures for VC HTTP API,"It seemed like a good idea when I first invented it a decade ago:[https://blue-button.github.io/blue-button-plus-pull/#scopes](https://blue-button.github.io/blue-button-plus-pull/#scopes) or when it got pulled into other efforts like [https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html](https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html)… and Orie even suggested the following set of parameterized scopes for this API:<br>'create:credentials': Grants permission to create credentials<br>'derive:credentials': Grants permission to derive credentials<br>'create:presentations': Grants permission to create presentations<br>'verify:presentations': Grants permission to verify presentations<br>'exchange:presentations': Grants permission to exchange presentations<br>So what’s the problem? I can say with full confidence after years of experience building and deploying systems to support parameterized scopes like this that they are fragile, awkward, and lead to insecure corner cases.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0208.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-21,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Manu Sporny,,,,,,Bikeshed: Renaming the VC HTTP API,"the fundamental issue is that stringing a bunch of consonants together (""HTTP"") rarely leads to something easy to say in conversation.",,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0131.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-17,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Kerri Lemoie,,,,,,Question About Signatures & Contexts,Is a VC still considered to be valid if it contains fields that are not described in its context file(s)? Does it depend on the signature type?,,https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0290.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-07-30,,,,,,,,,,,,,
VCs Development,CCG Mailing List,,,Bob Wyman,,,,,,Any Good use case of PAM (Privileged account Management) using Vcs,"A common example of this is when someone uses a ""Power of Attorney,"" to sign a contract. When they do, they typically sign documents with their own names and an annotation ""on behalf of,"" ""for,"" or ""by power of attorney,"" they don't forge the signature of the one who granted the power of attorney.",,https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0028.html,,Discussion,,,Development,,,,,,,Credentials Community Group,2021-11-06,,,,,,,,,,,,,
VCs Development,Mattr,,,,,,,,,Paper based Verifiable Credentials,Paper-based Verifiable Credentials allow us to have a low-tech solution for adopting VC's in situations where access to a phone cannot be guaranteed. This presentation looks at how this solution can be used to aid with the distribution of Vaccine Credentials.,Paper-based verifiable credentials allow us to have a low-tech solution for adopting verifiable credential's in situations where access to a phone cannot be ...,https://www.youtube.com/watch?v=EXvWxFjHvdY,,Video,,,Development,,,,,,,,2021-03-02,,,,,,,,,,,,,
VCs Development,Trusted Digital Web,,,,,,,,,Using Paper-based Structured Credentials to Humanize Verifiable Credentials,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman,User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by...,https://www.youtube.com/watch?v=kM30pd3w8qE,,Video,Rough Cut,,User Experience,,,,,,,,2021-11-19,,,,,,,,,,,,,
VCs Development,WebofTrustInfo,,,Manu Sporny,,,,,RWoT,Rendering Verifiable Credentials,"This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials.",,https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md,,Paper,,,User Experience,,,,,,,,2022-07-17,,,,,,,,,,,,,
Decentralized Identifiers,CCG,,,,,,,,,A Primer for Decentralized Identifiers,An introduction to self-administered identifiers for curious people,"A Decentralized Identifier (DID) is a new type of identifier that is globally unique, resolvable with high availability, and cryptographically verifiable. DIDs are typically associated with cryptographic material, such as public keys, and service endpoints, for establishing secure communication channels. DIDs are useful for any application that benefits from self-administered, cryptographically verifiable identifiers such as personal identifiers, organizational identifiers, and identifiers for Internet of Things scenarios. For example, current commercial deployments of W3C Verifiable Credentials heavily utilize Decentralized Identifiers to identify people, organizations, and things and to achieve a number of security and privacy-protecting guarantees. This document is an introduction to the concept of Decentralized Identifiers.",https://w3c-ccg.github.io/did-primer/,https://w3c-ccg.github.io/did-primer/did-primer-diagrams/urn-format.png,Report,,,Main,,,,,,,Credentials Community Group,2021-11-11,https://github.com/w3c-ccg/did-primer,,,,,,,,,,,,
Decentralized Identifiers,W3C,,,Markus Sabadello,"Danube Tech, Sovrin Foundation, OASIS XDI TC",Vienna,,,W3C Workshop on Privacy and Linked Data,Decentralized IDentifers (DIDs),"- Developed at Rebooting-the-Web-of-Trust workshop and W3C Credentials CG<br>- Persistent, dereference-able, cryptographically verifable identifers<br>- Registered in a blockchain or other decentralized network",,https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf,https://i.imgur.com/7NRcJbq.png,Presentation,,,Main,,,,,,,,2018-04-17,,,,,,,,,,,,,
Decentralized Identifiers,Identity Foundation,,,,,,,,,Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation,"Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community.",The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development,https://blog.identity.foundation/w3cdidspec-2/,,Post,,,Main,,,,,,,,2022-06-22,,,,,,,,,,,,,
@ -149,7 +151,7 @@ Decentralized Identifiers,DIDWG,,,,,,,,,Decentralized Identifiers (DIDs) v0.13 D
Decentralized Identifiers,DIDWG,,,,,,,,,DID Implementation Guide,"This document acts as a technical narrative for the implementation of DID methods and is expected to cover many topics related to that subject that a developer may wish to consider, including guidance around implementation details that may also be used for third party evaluation of an authored DID method via the DID-RUBRIC.",,https://w3c.github.io/did-imp-guide/,https://w3c.github.io/did-imp-guide/diagrams/representation-specific-and-foreign-entries.png,Note,,,Literature,,,,,,,DID Working Group,2021-11-04,https://github.com/w3c/did-imp-guide,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,,,,,,,,,W3C DID Test Suite and Implementation Report,"This document describes the did core test suite, and summarizes the latest test results.",,https://w3c.github.io/did-test-suite/,,Internal,,,Literature,,,,,,,DID Working Group,2023-01-17,https://github.com/w3c/did-test-suite,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,,,,,,,,,W3C Decentralized Characteristics Rubric v1.0,This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs.,,https://w3c.github.io/did-rubric/,,Internal,,,Literature,,,,,,,DID Working Group,2022-01-11,https://github.com/w3c/did-rubric,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,,,,,,,,,Well Known DID Configuration,"The DID Configuration resource provides proof of a bi-directional relationship between the controller of an origin and a DID via cryptographically verifiable signatures that are linked to a DID's key material. This document describes the data format of the resource and the resource location at which origin controllers can publish their DID Configuration.","This repo contains proposals and links to proposals for .well-known uris related to DIDs, Hubs and Agents. See IETF RFC5785 for more details on Defining Well-Known Uniform Resource Identifiers.",https://identity.foundation/.well-known,,Specification,,,Supporting,,,,,,,DID Working Group,2020-12-10,https://github.com/decentralized-identity/.well-known,,,,,,,,,,,,
Decentralized Identifiers,DIDWG,,,,,,,,,Well Known DID Configuration,The DID Configuration resource provides proof of a bi-directional relationship between the controller of an origin and a DID via cryptographically verifiable signatures that are linked to a DID's key material. This document describes the data format of the resource and the resource location at which origin controllers can publish their DID Configuration.,"This repo contains proposals and links to proposals for .well-known uris related to DIDs, Hubs and Agents. See IETF RFC5785 for more details on Defining Well-Known Uniform Resource Identifiers.",https://identity.foundation/.well-known,,Specification,,,Supporting,,,,,,,DID Working Group,2020-12-10,https://github.com/decentralized-identity/.well-known,,,,,,,,,,,,
Decentralized Identifiers,CCG,,,,,,,,,Decentralized Identifier Resolution (DID Resolution) v0.3,"DID resolution is the process of obtaining a DID document for a given DID. This is one of four required operations that can be performed on any DID (""Read""; the other ones being ""Create"", ""Update"", and ""Deactivate""). The details of these operations differ depending on the DID method. Building on top of DID resolution, DID URL dereferencing is the process of retrieving a representation of a resource for a given DID URL. Software and/or hardware that is able to execute these processes is called a DID resolver.",,https://w3c-ccg.github.io/did-resolution/,https://w3c-ccg.github.io/did-resolution/diagrams/https-dereference-example-1.png,Specification,,,Supporting,,,,,,,Credentials Community Group,2023-01-18,https://github.com/w3c-ccg/did-resolution,,,,,,,,,,,,
Decentralized Identifiers,GoDiddy,,https://iiw.idcommons.net/2C/_godiddy.com_-_Universal_DID_Services,Markus Sabadello,,,,,,godiddy.com - Universal DID Services,"Basic functions are creating, resolving, updating, and deactivating DIDs across multiple DID methods and networks. Advanced functions include key management, search, transfer of DIDs, lookup of historical DID document versions, notification of DID-related events, and more.",,https://godiddy.com,,site,,,Supporting,,,,,,,,2021-05-06,,,,,,,,,https://docs.godiddy.com/,https://api.godiddy.com/,,,
Decentralized Identifiers,IDCommons,,,Markus Sabadello,,,,,,Standard Interfaces for DID Create/Update/Deactivate,"- There is an attempt to specify abstract interfaces if you want to Create/Update/Deactivate a did that could be implemented for all did methods.<br>- The idea of this specification is to provide a standard with the same assumptions as with resolution. It should be in an abstract level, meaning it should specify the inputs and outputs of creating/updating/deactivating a did but not how it should be implemented.",,https://iiw.idcommons.net/3C/_Standard_Interfaces_for_DID_Create/Update/Deactivate,,Session Notes,,,Supporting,,,,,,,,2021-07-17,,,,,,,,,,,,,

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
Verifiable Credentials W3C Verifiable Credentials Working Group https://www.w3.org/2020/01/vc-wg-charter.html Verifiable Credentials Working Group The mission of the Verifiable Credentials (formerly known as Verifiable Claims) Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman. https://www.w3.org/2017/vc/WG/ Working Group Working Group 2017-04-14 https://github.com/w3c/verifiable-claims https://lists.w3.org/Archives/Public/public-vc-wg/ https://lists.w3.org/Archives/Public/public-vc-wg/
Verifiable Credentials VCWG Manu Sporny Verifiable Credentials Data Model v1.1 is an official W3C standard! It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html Specificationification Working Group Credentials Community Group 2022-03-03
Verifiable Credentials VCWG Verifiable Credentials Data Model v1.1 Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable. https://www.w3.org/TR/2022/REC-vc-data-model-20220303/ https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg Specificationification RECOMMEND Working Group Verifiable Credentials Working Group 2022-03-03
Verifiable Credentials VCWG Verifiable Credentials Data Model v2.0 - The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials) Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. https://www.w3.org/TR/vc-data-model-2.0/ https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg Specificationification DRAFT Working Group Verifiable Credentials Working Group 2023-05-20
Verifiable Credentials VCWG Verifiable Credential Data Integrity 1.0 This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs. https://www.w3.org/TR/vc-data-integrity/ https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-15
Verifiable Credentials VCWG Verifiable Credentials Status List v2021 This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials. https://www.w3.org/TR/vc-status-list/ https://www.w3.org/TR/vc-status-list/diagrams/StatusList2021.svg Specification Working Draft Working Group Verifiable Credentials WG 2023-04-27
Verifiable Credentials VCWG Verifiable Credentials Implementation Guidelines 1.0 This guide provides some examples and resources for implementing protocols which make use of verifiable credentials, beyond those available in the core specification. https://w3c.github.io/vc-imp-guide/ https://w3c.github.io/vc-imp-guide/diagrams/subject-ne-holder.svg Guidance Note Working Group Verifiable Credentials Working Group 2023-02-03 https://github.com/w3c/vc-imp-guide
Verifiable Credentials VCWG W3C Verifiable Credentials WG Test Suite Any conforming implementation MUST pass all tests in the test suite. There are multiple test suites, each of which is detailed below. You can review the current draft implementation report. https://w3c.github.io/vc-test-suite/ Code Working Group Verifiable Credentials Working Group 2021-10-31 https://github.com/w3c/vc-test-suite/
Verifiable Credentials VCWG Verifiable Credentials Use Cases This document does NOT attempt to define an architecture for the support of Verifiable Claims. Instead it expresses the sorts of needs that real users have that could be addressed through support for some sort of self-sovereign claim environment. It attempts to use terminology that is consistent with the other deliverables of the Verifiable Claims Working Group (you can see the relevant terms in Appendix A).<br><br>The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address. A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address. https://www.w3.org/TR/vc-use-cases/ https://i.imgur.com/J2IgVgl.png Specification Note Working Group Verifiable Credentials Working Group 2019-09-24 https://github.com/w3c/vc-use-cases
Verifiable Credentials VCWG Verifiable Credentials Data Model Implementation Report 1.0 The purpose of this document is to demonstrate that there are at least two interoperable implementations of processors that are capable of generating output that is conformant to the Verifiable Credentials Data Model. https://w3c.github.io/vc-test-suite/implementations/ Report Working Group 2021-10-30
Verifiable Credentials VCWG The Verifiable Credential Specifications Directory This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual. https://w3c.github.io/vc-specs-dir/ registry Working Group Verifiable Credentials WG 2023-04-08 https://github.com/w3c/vc-specs-dir/tree/main/specifications
Verifiable Credentials VCWG ECDSA Cryptosuite v2019 This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1). https://www.w3.org/TR/vc-di-ecdsa/ Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-18
Verifiable Credentials VCWG EdDSA Cryptosuite v2022 This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519). https://www.w3.org/TR/vc-di-eddsa/ Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-18
Verifiable Credentials VCWG BBS Cryptosuite v2023 This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures. https://www.w3.org/TR/vc-di-bbs/ Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-18
Verifiable Credentials VCWG JSON Web Signatures for Data Integrity Proofs This specification describes a JSON Web Signature Suite created in 2020 for the Verifiable Credentials Data Integrity Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA. https://www.w3.org/TR/vc-jws-2020/ Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-01-27
Verifiable Credentials VCWG Securing Verifiable Credentials using JSON Web Tokens This specification defines how Verifiable Credentials can be represented as JSON Web Tokens (JWT) [RFC7519] and secured using JSON Web Signatures (JWS) [RFC7515]. https://www.w3.org/TR/vc-jwt/ Specification Working Draft Working Group Cryptography Verifiable Credentials WG 2023-05-15
Verifiable Credentials W3C CCG https://w3c-ccg.github.io/ Verifiable Credentials, Decentralized Identifiers Credentials Community Group The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations. https://www.w3.org/community/credentials/ Working Group Credentials Community Group Credentials Community Group 2014-08-19 https://github.com/w3c-ccg/community https://lists.w3.org/Archives/Public/public-credentials/
Verifiable Credentials CCG W3C CCG meeting transcripts This repo contains the meeting archives for the W3C-CCG (Credentials Community Group), including transcripts based on the IRC logs and audio files for our regular meetings, ancillary material such as slide presentations, etc. The archives for 2014-2019 can be found here. COMMUNITY: W3C Credentials Community Group meeting transcripts - GitHub - w3c-ccg/meetings: COMMUNITY: W3C Credentials Community Group meeting transcripts https://github.com/w3c-ccg/meetings Page Credentials Community Group
Verifiable Credentials CCG RWOT, IIW W3C CCG announcements Announcements and events associated with the W3C Credentials CG https://github.com/w3c-ccg/announcements Page Credentials Community Group
Verifiable Credentials CCG W3C CCG Work Item Process This lets you write your specs in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar "spec looking" ReSpec format. ReSpec is just html with a javascript ReSpec library. https://github.com/w3c-ccg/workitem-process Page Credentials Community Group
Verifiable Credentials CCG Global Open Badges Workgroup, Verifiable Credentials WG, Credentials Commiunity Group, Schema.org WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials - w3c-ccg/edu_occ_verifiable_credentials Work on describing credentials is occurring within the IMS Global Open Badges Workgroup, W3C Verifiable Credentials Working Group, W3C Credentials Commiunity Group, Educational and Occupational Credentials in Schema.org Community Group, and Credential Engine/CTDL.<br><br>This effort will result in requirements, use cases, and/or draft specs to be formalized in the appropriate standards group https://github.com/w3c-ccg/edu_occ_verifiable_credentials Code Credentials Community Group Credentials Community Group
Verifiable Credentials CCG WORK ITEM: Verifiable Credentials Examples This GitHub Pages Website hosts example credentials, as well as documents needed to construct them. When contributing an example, you are encouraged to provide everything needed to generate an verify a credential. Do your best not to include ANY broken links or missing documentation. If possible, try to make the credential id resolvable as well. https://github.com/w3c-ccg/vc-examples Code Credentials Community Group Credentials Community Group
Verifiable Credentials CCG Verifiable Credentials Extension Registry Verifiable Credentials Extension Registry - This document contains a list of all known Verifiable Credential extensions and their associated specifications. Credentials Community Group https://w3c-ccg.github.io/vc-extension-registry/ Report draft Credentials Community Group Credentials Community Group 2022-11-14
Verifiable Credentials CCG Verifiable Credentials Extension Registry Markus Sabadello Ed25519Signature2018 This specification describes a standard signature suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset Normalization Algorithm [RDF-DATASET-NORMALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and Ed25519 [ED25519] as the signature algorithm. https://w3c-ccg.github.io/lds-ed25519-2018/ Report draft Credentials Community Group Proof Methods Credentials Community Group 2021-07-23
Verifiable Credentials CCG Verifiable Credentials Extension Registry Manu Sporny, Dave Longley RsaSignature2018 This specification describes the RSA Signature Suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset CANONICALIZATION Algorithm [RDF-DATASET-CANONICALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and the RS256 algorithm defined in JSON Web Signatures [RFC7515] as the signature algorithm. https://w3c-ccg.github.io/lds-rsa2018/ Report draft Credentials Community Group Proof Methods Credentials Community Group 2020-05-26
Verifiable Credentials CCG Verifiable Credentials Extension Registry Manu Sporny, Dave Longley CredentialStatusList2017 A simple list-based mechanism for publishing and checking the status of a credential https://w3c-ccg.github.io/vc-csl2017/ Report Credentials Community Group Status Methods Credentials Community Group 2020-12-29
Verifiable Credentials CCG Ecdsa Secp256k1 Signature 2019 This specification describes the Ecdsa Secp256k1 Signature created in 2019 for the Linked Data Signatures specification https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/ Code Draft Credentials Community Group 2020-04-08
Verifiable Credentials CCG Verifiable Credential JSON Schemas The [VC_DATA_MODEL](https://www.w3.org/TR/vc-data-model/) specifies the models used for Verifiable Credentials and Verifiable Presentations, and explains the relationships between three parties: issuer, holder, and verifier. A critical piece of infrastructure out of the scope of those specifications is the Credential Schema. A mechanism to use JSON Schemas with Verifiable Credentials - GitHub - w3c/vc-json-schema: A mechanism to use JSON Schemas with Verifiable Credentials https://github.com/w3c-ccg/vc-json-schemas Code Credentials Community Group 2023-05-24
Verifiable Credentials CCG Traceability Vocabulary v0.1 This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to supply chain and other traceability information, similar to what is often referred to as "provenance", including country of origin, chemical properties, mechanical properties, and other attributes of products and materials. VCs using these terms can then be used to help determine the legitimacy of organizations participating in global trade and the status of the products and materials described therein https://w3c-ccg.github.io/traceability-vocab/ https://w3c-ccg.github.io/traceability-vocab/resources/product-identifier-verification-from-identification-key-license.png Specification v0.1 Credentials Community Group Credentials Community Group 2023-05-23
Verifiable Credentials DIF Claims and Credentials Working Group Join this group to contribute to the standards and technology that create, exchange, and verify claims and credentials in a decentralized identity ecosystem. For example, a cryptographically verifiable credential that proves an individual has a college degree or is of a certain age. Our members focus on specs that are vendor agnostic and based on industry standards. https://identity.foundation/working-groups/claims-credentials.html page Claims and Credentials WG 2020-09-18
Verifiable Credentials DIF presentation-exchange Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) - GitHub - decentralized-identity/presentation-exchange: Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) https://github.com/decentralized-identity/presentation-exchange Code Claims and Credentials WG 2023-05-31
Verifiable Credentials DIF presentation-request Requirements Analysis and Protocol Design for a VC Presentation Request Format Requirements Analysis and Protocol Design for a VC Presentation Request Format - GitHub - decentralized-identity/presentation-request: Requirements Analysis and Protocol Design for a VC Presentation Request Format https://github.com/decentralized-identity/presentation-request Code Claims and Credentials WG 2020-01-08
Verifiable Credentials DIF Credential Manifest Credential Manifests do not themselves define the contents of the output credential(s), the process the Issuer uses to evaluate the submitted inputs, or the protocol Issuers, Subjects, and their User Agents rely on to negotiate credential issuance. Instead, Credential Manifests are a data model for issuers to publish and/or send individually to would-be holders, allowing the software of the latter to understand and negotiate an issuance process. https://identity.foundation/credential-manifest/ page Claims and Credentials WG 2023-05-04
Verifiable Credentials Personal Kyle Den Hartog Example Design of an Authorization System with Verifiable Credentials and the Tradeoffs The primary focus of this blog post is to highlight the different problems that are likely to occur when going down the path of building an authorization system with verifiable credentials. I’ll be sure to keep things at a higher level so that anyone can understand these tradeoffs, but take you through the details that would be thought through by an architect designing the system. https://kyledenhartog.com/example-authz-with-VCs/ Post Development 2021-06-22
Verifiable Credentials 51 Nodes Indexing and Querying Revoked Verifiable Credentials this article describes a simple approach to revoke verifiable credentials and a decentralized and efficient way to index and query those revoked credentials using the [Graph protocol](https://thegraph.com/en/). Due to its immutability and censorship resistance, the Blockchain seems to be a suitable place to manage identities and credentials. However, querying the data on the blockchain in a trusted and… https://medium.com/51nodes/indexing-and-querying-revoked-verifiable-credentials-e229dc2781d4 Post Development 2022-07-01
Verifiable Credentials CCG Mailing List Nikos Fotiou VC Issuance based on OAuth 2.0 We design, implement, and evaluate a solution for achieving continuous authorization of HTTP requests exploiting Verifiable Credentials (VCs) and OAuth 2.0. Specifically, we develop a VC issuer that acts as an OAuth 2.0 authorization server, a VC verifier that transparently protects HTTP-based resources, and a VC wallet implemented as a browser extension capable of injecting the necessary authentication data in HTTP requests without needing user intervention. https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0084.html Discussion Development Credentials Community Group 2022-04-14
Verifiable Credentials CCG Mailing List Orie Steele Supporting VC-JWT and BBS+ Presentation Exchange in the VC-HTTP-API [https://github.com/OR13/GNARLY](https://github.com/OR13/GNARLY)  (while we wait for a better name...)<br><br>This demo API and Spec has a number of improvements over the current<br><br>VC-HTTP-API, including tested support for VC-JWT, JsonWebSignature2020 and<br><br>BBS+ Selective Disclosure Presentation Exchange. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0313.html Discussion Development Credentials Community Group 2021-07-31
Verifiable Credentials CCG Mailing List https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html Joe Andrieu Updated VC-API diagram for Supply Chain flow I updated the supply chain version of the data flow diagram for verification. https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html https://i.imgur.com/mH5TBtU.png Discussion Development Credentials Community Group 2021-09-28
Verifiable Credentials CCG Mailing List Manu Sporny re: VC API: handling large documents client to server Typical solutions to this problem require that you put the binary data outside of the VC, if at all possible. This works well for common static images such as logos. It is also possible to split the VC into two VCs... one with the machine-readable data from the issuer (with a digital signature) and one with the image data from any source (without a digital signature, since, if hashlinked, the signature will verify the validity of the image data). That latter approach can be more privacy preserving AND more complex than many might feel is necessary. https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0035.html Discussion Development Credentials Community Group 2022-02-10
Verifiable Credentials CCG Mailing List Manu Sporny VC-API interoperability test suites ready for experimental integration * [The VC API test suite for basic issuer interop is here](https://w3c-ccg.github.io/vc-api-issuer-test-suite/)<br>* [The VC API test suite for basic verifier interop is here](https://w3c-ccg.github.io/vc-api-verifier-test-suite/)<br>* [The Data Integrity test suite for Ed25519Signature2020 interop is here](https://w3c-ccg.github.io/di-ed25519-test-suite/) https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html Discussion Development Credentials Community Group 2022-04-26
Verifiable Credentials CCG Mailing List Manu Sporny Cross-industry VC API test suite achieves first multi-vendor interop for issue/verify We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for the VC Issuer API and VC Verifier API. The test suites test the OAS definition files (which are used to generate the specification):<br>* [2.1 Verify Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity)<br>* [2.1 Issue Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-issuer-test-suite/#Issue%20Credential%20-%20Data%20Integrity) https://lists.w3.org/Archives/Public/public-credentials/2022May/0041.html Discussion Development Credentials Community Group 2022-05-18
Verifiable Credentials CCG Mailing List Joe Andrieu Diagrams for VC HTTP API work [was Re: [AGENDA] VC HTTP API Work Item - August 17th 2021] a. *Holder* The entity who holds the VC once issued and later presents it for verification.<br>b. *Holder Application *The software or service that allows holders to manage their credentials. Often called a wallet. For symmetry, it could be called a Holder Service.<br>c. *Storage Service *The software or service that actually stores VCs long term (on behalf of the holder)<br>d. *Issuer Role* The website or software that provides issuing functionality to a holder on behalf of that issuer)<br>e. *Issuer Service* Software or service that actually signs VCs and VPs) This component is used by both the issuer (to mint VCs) and the holder (to create VPs for presentation)<br>f. *Verifier Role* The website or software that uses a Verification Service as part of its decision making process for providing services to holders.<br>g. *Verifier Service *The software or service that verifies VCs and VPs by checking proofs and checking status. https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0231.html https://i.imgur.com/4hCNLVA.png Discussion Development Credentials Community Group 2021-08-16
Verifiable Credentials CCG Mailing List Brian Richter Issuer API Cross Trust Boundary Scoping - VC-HAPI (f.k.a. VC-HTTP-API) I think I'm starting to understand how RAR fits into this picture. This decision can be made for us by punting the question to the authorization process entirely. With RAR we can force the user to authorize for the actual subject they are issuing the credential about. Is Alice authorized to issue VCs with claims about did:example:12345? To answer that question Alice asks for a token with the following RAR request https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0263.html Discussion Development Credentials Community Group 2021-07-24
Verifiable Credentials CCG Mailing List Justin Richer RAR Structures for VC HTTP API It seemed like a good idea when I first invented it a decade ago:[https://blue-button.github.io/blue-button-plus-pull/#scopes](https://blue-button.github.io/blue-button-plus-pull/#scopes) or when it got pulled into other efforts like [https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html](https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html)… and Orie even suggested the following set of parameterized scopes for this API:<br>'create:credentials': Grants permission to create credentials<br>'derive:credentials': Grants permission to derive credentials<br>'create:presentations': Grants permission to create presentations<br>'verify:presentations': Grants permission to verify presentations<br>'exchange:presentations': Grants permission to exchange presentations<br>So what’s the problem? I can say with full confidence after years of experience building and deploying systems to support parameterized scopes like this that they are fragile, awkward, and lead to insecure corner cases. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0208.html Discussion Development Credentials Community Group 2021-07-21
Verifiable Credentials CCG Mailing List Manu Sporny Bikeshed: Renaming the VC HTTP API the fundamental issue is that stringing a bunch of consonants together ("HTTP") rarely leads to something easy to say in conversation. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0131.html Discussion Development Credentials Community Group 2021-07-17
Verifiable Credentials CCG Mailing List Kerri Lemoie Question About Signatures & Contexts Is a VC still considered to be valid if it contains fields that are not described in its context file(s)? Does it depend on the signature type? https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0290.html Discussion Development Credentials Community Group 2021-07-30
Verifiable Credentials CCG Mailing List Bob Wyman Any Good use case of PAM (Privileged account Management) using Vcs A common example of this is when someone uses a "Power of Attorney," to sign a contract. When they do, they typically sign documents with their own names and an annotation "on behalf of," "for," or "by power of attorney," they don't forge the signature of the one who granted the power of attorney. https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0028.html Discussion Development Credentials Community Group 2021-11-06
Verifiable Credentials Mattr Paper based Verifiable Credentials Paper-based Verifiable Credentials allow us to have a low-tech solution for adopting VC's in situations where access to a phone cannot be guaranteed. This presentation looks at how this solution can be used to aid with the distribution of Vaccine Credentials. Paper-based verifiable credentials allow us to have a low-tech solution for adopting verifiable credential's in situations where access to a phone cannot be ... https://www.youtube.com/watch?v=EXvWxFjHvdY Video Development 2021-03-02
51 Verifiable Credentials LPFH Kaliya IdentityWoman Verifiable Credentials Flavors Explained Below are the three primary flavors of VCs discussed in this paper. All have more than one critical implementation in various stages of production. There are advocated variations of these types, but they are less common.<br>* JSON-LD family with LD Signatures or with BBS+ Signatures that enable Zero Knowledge Proofs (ZKP or ZKPs)<br>* JSON with JSON Web Signatures, precisely in the form of a JSON Web Token (JWT)<br>* ZKP with Camenisch-Lysyanskaya Signatures (ZKP-CL) https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf Post Varieties 2021-02
52 Standards, Verifiable Credentials LFPH https://www.lfph.io/wp-content/uploads/2021/02/Verifiable-Credentials-Flavors-Explained.pdf Lucy Yang The Flavors of Verifiable Credentials The differences between the different flavors of VCs for technically inclined readers. It elaborated on the differences between JSON and JSON-LD and articulated differences between the two different implementations of ZKP style credentials. The ‘Journey of a VC’ section articulated all steps where VCs are active and highlighted the differences in how different VC flavors ’behave’. https://www.lfph.io/2021/02/11/cci-verifiable-credentials-flavors-and-interoperability-paper/ Paper Varieties, Decentralized Identity Stack 2021-11-11
53 Verifiable Credentials Evernym Daniel Hardman Categorizing Verifiable Credentials - Evernym Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation. Not all verifiable credentials are created the same. This post examines the categories of credentials and the architectural choices driving this variation. https://www.evernym.com/blog/categorizing-verifiable-credentials/ Post Varieties 2019-11-07
Verifiable Credentials DIF https://github.com/decentralized-identity/vc-spec-map/releases/tag/v1.2.0 Michael Ruminer Verifiable Credentials Specification Relationships diagrams and documentation on the relationship of verfiable credential specifications<br><br>The current release contains some of the most core specifications and their related specs in a diagram. It does not yet address some of the items especially under DIF work groups for secure data storage, SIOP, Sidetree etc. "Good for anyone but especially useful when trying to jump in on the deep end. If you walk even this limited tree of specs you know a lot" - @michaelruminer https://github.com/decentralized-identity/vc-spec-map http://decentralized-id.com/images/VC-spec-map.webp infographic Interoperability 2021-05-27
54 Verifiable Credentials Evernym Brent Zundel Why the Verifiable Credentials Community Should Converge on BBS+ BBS+ LD-Proofs use JSON-LD schemas, so credentials that use them can have a rich, hierarchical set of attributes. Instead of the heavy-handed mechanism for the encoding and canonicalization of attributes values that we’d imagined for Rich Schemas, they use RDF canonicalization and a hash function. Rather than expanding the credential definition, they discarded it, taking advantage of some properties of BBS+ keys which allow for deterministic expansion. BBS+ ZKP signatures: The breakthrough the industry has been looking for to converge on a universal format for privacy-respecting VCs. https://www.evernym.com/blog/bbs-verifiable-credentials/ Post Varieties 2021-03-24
55 Verifiable Credentials Personal Steve Lockstep The original #VerifiableCredentials were PKI-based SIM cards and EMV cards. These bind key pairs to individuals, and to signed assertions (account numbers) to deliver provenance, fidelity and proof of possession. [https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little](https://constellationr.com/blog-news/not-too-much-identity-technology-and-not-too-little)<br>$5 https://twitter.com/Steve_Lockstep/status/1419935186188341249 https://i.imgur.com/ucAVxCX.png tweet Varieties 2021-06-27
56 Verifiable Credentials CCG Mailing List DSpace@MIT Anil John FYI >> DHS W3C VC/DID Implementation Profile: Credential Data Model Representation Syntax & Proof Format SolidVC : a decentralized framework for Verifiable Credentials on the web We are walking this path step-by-step by documenting the results and lessons from the DHS sponsored multi-platform, multi-vendor interoperability plug-fests and other rigorous plug-fests with similar goals to develop a “DHS Implementation Profile of W3C Verifiable Credentials and W3C Decentralized Identifiers” to ensure the use of Security, Privacy and Interoperability implementation choices that are acceptable to the USG such that these capabilities can be deployed on and connect to USG networks and infrastructure.<br> … please [find attached the DHS Implementation Profile](https://lists.w3.org/Archives/Public/public-credentials/2022Sep/att-0253/DHS.W3C.VC-DID.Implemenation.Profile-20220929-SHARE.pdf) of W3C VCs and W3C DIDs normative guidance on:<br> - Credential Data Model Representation Syntax<br> - Credential Data Model Proof Format 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://lists.w3.org/Archives/Public/public-credentials/2022Sep/0253.html 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 Discussion paper Interoperability Implementations Credentials Community Group 2022-09-29 2019
57 Verifiable Credentials DIF Paris P2P Paris P2P Festival Interoperability Mapping Exercise Blockstack and Verifiable Credentials - Paris P2P Festival The archive and information hub for the cross-community interoperability project. Focus is on education and familiarity for various efforts across multiple groups for interoperable decentralized identity infrastructure. • Keep auth and smart contracts on-chain<br> • Keep encrypted data off-chain<br> > • Wrap everything in an easy JavaScript API https://github.com/decentralized-identity/interoperability/blob/master/assets/interoperability-mapping-exercise-10-12-20.pdf https://p2p.paris/gen/attADzQJ92rNIv6B3-Blockstack_and_Verifiable_Credentials_-_Paris_P2P_Festival_.pdf https://i.imgur.com/QvpMl6M.png infographic presentation Interoperability Implementations 2020-10-13 2020-01-10
58 Verifiable Credentials Github LibP2P creatornader Decentralized Identity Standards.md Verifiable credentials and libp2p Decentralized Identifiers (DIDs), Decentralized Identifier (DID) Resolution, DID Spec Registries, DID Use Cases, DID Rubric, DID Key, DID Web, WebCrypto, WebAuthn, WebKMS, Verifiable Credentials (VCs), VC Use Cases, VC JSON Schemas, Credential Revocation List, Credential Handler API (CHAPI), Verifiable Presentation Request, JSON Linked Data (JSON-LD), CBOR Linked Data (CBOR-LD), Authorization Capabilities (ZCAP-LD), Linked Data Security Vocab, Linked Data Citizenship Vocab, Linked Data Traceability Vocab, Linked Data Cryptographic Suite Registry, Linked Data Proofs, Linked Data Proofs BBS+ Signatures, Universal Wallet, Encrypted Data Vaults (EDVs), Data Privacy Vocabulary, Data Minimization, ActivityPub, Confidential Storage, DID Peer, DIDComm Messaging, Well Known DID Configuration, Self-Issued DID Profile for OpenID, Verifiable Presentation Exchange, Identity Hubs, Credential Manifest, Sidetree, Key Event Receipt Infrastructure (KERI), OAuth 2.0, Grant Negotiation Access Protocol (GNAP), JWA/JWK, JWT/JWS/JWE, JSON Web Message (JWM), HTTP Signatures, Hashlink, BBS+ Signatures Scheme, Biometric Service Providers (BSPs), Aries RFCs, Interop Test Suite, The Trust Over IP (ToIP) Stack, Rich Schemas, Chained Credentials, Data Overlays, Data Consent Lifecycle, Indirect Identity Control, Anoncreds, Machine-Readable Trust Frameworks, Decentralized Key Management System (DKMS), eXtensible Data Interchange (XDI), OpenID Connect (OIDC), OIDC Credential Provider, User-Managed Access (UMA) 2.0, Consent Receipts, Blinding Identity Taxonomy (BIT) 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://gist.github.com/creatornader/c8a20c534d3cf8f65a9b34ce2ad81725 https://discuss.libp2p.io/t/verifiable-credentials-and-libp2p/206 https://global.discourse-cdn.com/standard17/uploads/libp2p/original/1X/aacb49457c3aace79a1038dd02996b402260215d.png gist discussion Interoperability Implementations 2020-11-25 2019-07-09
59 Verifiable Credentials Ontology Verifiable Claim Protocol The entire workflow of the verifiable claim is shown in the figure below. It contains three major parts:<br><br>Request claim;<br>Issue claim;<br>Verify claim. Ontology decentralized identification protocol based on W3C DID specifications. - ontology-DID/claim_spec.md at master · ontio/ontology-DID https://github.com/ontio/ontology-DID/blob/master/docs/en/claim_spec.md Specification Implementations 2017-03-20
60 Verifiable Credentials Crossword Cybersecurity NGI Crossword wins NGI Atlantic funds for Verifiable Credentials project European Commission’s Next Generation Internet (NGI) initiative to lead a project to test the OpenID Foundation’s protocols for transferring verifiable credentials. Crossword’s partners in this project are Spruce Inc from the USA and Fraunhofer from Germany https://www.crosswordcybersecurity.com/post/next-generation-internet-grant-win https://static.wixstatic.com/media/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg/v1/fill/w_1000,h_563,al_c,q_85,usm_0.66_1.00_0.01/082467_48feff2ccec04cb682e6101aefebd971~mv2.jpg Post Implementations 2022-08-04
61 Verifiable Credentials Identity.com Identity.com Verifiable Credential Library This Javascript Library provides functionality around Verifiable Credentials (VC), a W3C standard. Enables Validators to issue, Credential Wallets to verify, filter and Requesters to verify credentials. Verifiable Credential and Attestation Library. Latest version: 3.0.2, last published: 4 months ago. Start using @identity.com/credential-commons in your project by running `npm i @identity.com/credential-commons`. There are 3 other projects in the npm registry using @identity.com/credential-commons. https://www.npmjs.com/package/@identity.com/credential-commons code Implementations 2023-02-13
62 Verifiable Credentials Personal Samuel Smith VC Spec Enhancement Proposal the VC standard appears to be an adoption vector for Linked Data, not the other way around. My overriding interest is that the concept of a VC as a securely attributable statement is a very powerful and attractive one and therefore should be widely adopted. We should therefore be picking the best technologies that best support broad VC adoption, not the other way around. https://github.com/SmithSamuelM/Papers/blob/master/whitepapers/VC_Enhancement_Strategy.md Paper Literature 2022-04-04
63 Verifiable Credentials Personal Phil Windley Verifiable Credential Exchange Multi-source identity (MSI) depends on issuing, exchanging, and verifying digital credentials. The specification for verifiable credentials is being formulated by the World Wide Web Consortium’s Verifiable Credentials Working Group. Verifiable credentials provide a standard way to express credentials in a way that is cryptographically secure, privacy respecting, and automatically verifiable. Verifiable credential exchange is the foundation of decentralized, online identity. This post describes how it works. https://www.windley.com/archives/2018/12/verifiable_credential_exchange.shtml https://www.windley.com/archives/2018/12/claim_issuing_and_presenting.png Post Literature 2018-12-10
64 Verifiable Credentials Service-centric Networking, Telekom Innovation Laboratories, Technische Universiät Berlin Zoltán András Lux, Felix Beierle, Sebastian Zickau, Sebastian Göndör Full-text Search for Verifiable Credential Metadata on Distributed Ledgers The proposed solution is able to find credential types based on textual input from the user by using a full-text search engine and maintaining a local copy of the ledger. Thus, we do not need to rely on information about credentials coming from a very large candidate pool of third parties we would need to trust, such as the website of a company displaying its own identifier and a list of issued credentials. We have also proven the feasiblity of the concept by implementing and evaluating a prototype of the full-text credential metadata search service. https://arxiv.org/abs/1909.02895 Paper Literature 2019-09-06
75 Verifiable Credentials CCG Mailing List Michael Herman Verifiable Credential Notarization and Third-Party Notary Services Providers: User Scenarios User Scenario A: Alice self-issues a blood pressure home reading (BPHR) credential to Dr. Bob's Clinic using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network.<br><br>User Scenario B: The Province of Sovronia issues a Sovronia Driver's License to Alice using SOVRONA's credential notarization services. SOVRONA is a third-party notary services provider/network. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0109.html https://lists.w3.org/Archives/Public/public-credentials/2021Jul/att-0109/image003.jpg user journies Use Case Credentials Community Group 2021-07-15
76 Verifiable Credentials IDCommons Gena Morgan, Kevin Dean IDCommons IIW Verifiable Credentials for Authentic Data in the Supply Chain Using DiDs and VCs for verifiable product data in supply chains, leveraging the largest supply chain standard system in the world,<br><br>2.5 million users companies, over 6 billion product scans per day<br><br>Product data and attestations from a number of various authoritative sources<br><br>Leverage DIDs/VCs for distributed data sharing, verification https://iiw.idcommons.net/10G/_Verifiable_Credentials_for_Authentic_Data_in_the_Supply_Chain Session Notes Use Case 2021-05-06
77 Verifiable Credentials IDCommons Mahmoud Alkhraishi IDCommons IIW Verifiable Credentials for Assets General Framework on how to think of VCs for Assets including leveraging GS1 and other vocabularies in the traceability vocab.<br><br>Requirements and Opportunities that block adoption of VCs in Supply chains https://iiw.idcommons.net/21E/_Verifiable_Credentials_for_Assets_30_min Session Notes Use Case 2021-05-07
78 Verifiable Credentials VCs Development Trusted Digital Web W3C Verifiable Credentials Working Group https://www.w3.org/2020/01/vc-wg-charter.html Using Paper-based Structured Credentials to Humanize Verifiable Credentials Verifiable Credentials Working Group User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman The mission of the Verifiable Credentials (formerly known as Verifiable Claims) Working Group (VCWG) is to make expressing and exchanging credentials that have been verified by a third party easier and more secure on the Web.<br><br>The Chairs of the Working Group are Kristina Yasuda and Brent Zundel. The W3C Staff Contact for the Working Group is Ivan Herman. User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by... https://www.youtube.com/watch?v=kM30pd3w8qE https://www.w3.org/2017/vc/WG/ Video Working Group Rough Cut User Experience Verifiable Credentials Working Group 2021-11-19 2017-04-14 https://github.com/w3c/verifiable-claims https://lists.w3.org/Archives/Public/public-vc-wg/ https://lists.w3.org/Archives/Public/public-vc-wg/
79 Verifiable Credentials VCs Development WebofTrustInfo VCWG Manu Sporny RWoT Rendering Verifiable Credentials Verifiable Credentials Data Model v1.1 is an official W3C standard! This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials. It's official, the Verifiable Credentials Data Model v1.1 is a W3C standard!<br><br> Verifiable Credentials Data Model v1.1<br> https://www.w3.org/TR/2022/REC-vc-data-model-20220303/<br><br>This was largely a maintenance release of the specification. The list of (minor) revisions since the v1.0 release can be found here:https://www.w3.org/TR/2022/REC-vc-data-model-20220303/#revision-history https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md https://lists.w3.org/Archives/Public/public-credentials/2022Mar/0005.html Paper Specificationification User Experience Verifiable Credentials Working Group Credentials Community Group 2022-07-17 2022-03-03
80 VCs Development VCWG Verifiable Credentials Data Model v1.1 Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. Driver's licenses are used to claim that we are capable of operating a motor vehicle, university degrees can be used to claim our education status, and government-issued passports enable holders to travel between countries. This specification provides a standard way to express these sorts of claims on the Web in a way that is cryptographically secure, privacy respecting, and automatically verifiable. https://www.w3.org/TR/2022/REC-vc-data-model-20220303/ https://www.w3.org/TR/2022/REC-vc-data-model-20220303/diagrams/ecosystem.svg Specificationification RECOMMEND Verifiable Credentials Working Group Verifiable Credentials Working Group 2022-03-03
81 VCs Development VCWG Verifiable Credentials Data Model v2.0 - The components that constitute a [verifiable credential](https://www.w3.org/TR/2022/WD-vc-data-model-2.0-20220811/%23dfn-verifiable-credentials) Credentials are a part of our daily lives; driver's licenses are used to assert that we are capable of operating a motor vehicle, university degrees can be used to assert our level of education, and government-issued passports enable us to travel between countries. This specification provides a mechanism to express these sorts of credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable. https://www.w3.org/TR/vc-data-model-2.0/ https://www.w3.org/TR/vc-data-model-2.0/diagrams/zkp-cred-pres.svg Specificationification DRAFT Verifiable Credentials Working Group Verifiable Credentials Working Group 2023-05-20
82 VCs Development VCWG Verifiable Credential Data Integrity 1.0 This specification describes mechanisms for ensuring the authenticity and integrity of Verifiable Credentials and similar types of constrained digital documents using cryptography, especially through the use of digital signatures and related mathematical proofs. https://www.w3.org/TR/vc-data-integrity/ https://www.w3.org/TR/vc-data-integrity/diagrams/hiw-verification.svg Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-05-15
83 VCs Development VCWG Verifiable Credentials Status List v2021 This specification describes a privacy-preserving, space-efficient, and high-performance mechanism for publishing status information such as suspension or revocation of Verifiable Credentials. https://www.w3.org/TR/vc-status-list/ https://www.w3.org/TR/vc-status-list/diagrams/StatusList2021.svg Specification Working Draft Verifiable Credentials Working Group Verifiable Credentials WG 2023-04-27
84 VCs Development VCWG Verifiable Credentials Implementation Guidelines 1.0 This guide provides some examples and resources for implementing protocols which make use of verifiable credentials, beyond those available in the core specification. https://w3c.github.io/vc-imp-guide/ https://w3c.github.io/vc-imp-guide/diagrams/subject-ne-holder.svg Guidance Note Verifiable Credentials Working Group Verifiable Credentials Working Group 2023-02-03 https://github.com/w3c/vc-imp-guide
85 VCs Development VCWG W3C Verifiable Credentials WG Test Suite Any conforming implementation MUST pass all tests in the test suite. There are multiple test suites, each of which is detailed below. You can review the current draft implementation report. https://w3c.github.io/vc-test-suite/ Code Verifiable Credentials Working Group Verifiable Credentials Working Group 2021-10-31 https://github.com/w3c/vc-test-suite/
86 VCs Development VCWG Verifiable Credentials Use Cases This document does NOT attempt to define an architecture for the support of Verifiable Claims. Instead it expresses the sorts of needs that real users have that could be addressed through support for some sort of self-sovereign claim environment. It attempts to use terminology that is consistent with the other deliverables of the Verifiable Claims Working Group (you can see the relevant terms in Appendix A).<br><br>The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address. A verifiable claim is a qualification, achievement, quality, or piece of information about an entity's background such as a name, government ID, payment provider, home address, or university degree. Such a claim describes a quality or qualities, property or properties of an entity which establish its existence and uniqueness. The use cases outlined here are provided in order to make progress toward possible future standardization and interoperability of both low- and high-stakes claims with the goals of storing, transmitting, and receiving digitally verifiable proof of attributes such as qualifications and achievements. The use cases in this document focus on concrete scenarios that the technology defined by the group should address. https://www.w3.org/TR/vc-use-cases/ https://i.imgur.com/J2IgVgl.png Specification Note Verifiable Credentials Working Group Verifiable Credentials Working Group 2019-09-24 https://github.com/w3c/vc-use-cases
87 VCs Development VCWG Verifiable Credentials Data Model Implementation Report 1.0 The purpose of this document is to demonstrate that there are at least two interoperable implementations of processors that are capable of generating output that is conformant to the Verifiable Credentials Data Model. https://w3c.github.io/vc-test-suite/implementations/ Report Verifiable Credentials Working Group 2021-10-30
88 VCs Development VCWG The Verifiable Credential Specifications Directory This document serves as an unofficial directory for all known Verifiable Credential specifications whether they are released by a global standards setting organization, a community group, an open source project, or an individual. https://w3c.github.io/vc-specs-dir/ registry Verifiable Credentials Working Group Verifiable Credentials WG 2023-04-08 https://github.com/w3c/vc-specs-dir/tree/main/specifications
89 VCs Development VCWG ECDSA Cryptosuite v2019 This specification describes a Data Integrity Cryptosuite for use when generating a digital signature using the Elliptic Curve Digital Signature Algorithm (ECDSA) based on the Standards for Efficient Cryptography over prime fields using a verifiably random Elliptic Curve (secpr1). https://www.w3.org/TR/vc-di-ecdsa/ Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-05-18
90 VCs Development VCWG EdDSA Cryptosuite v2022 This specification describes a Data Integrity cryptographic suite for use when creating or verifying a digital signature using the twisted Edwards Curve Digital Signature Algorithm (EdDSA) and Curve25519 (ed25519). https://www.w3.org/TR/vc-di-eddsa/ Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-05-18
91 VCs Development VCWG BBS Cryptosuite v2023 This specification describes the BBS+ Signature Suite created in 2023 for the Data Integrity specification. The Signature Suite utilizes BBS+ signatures to provide the capability of zero knowledge proof disclosures. https://www.w3.org/TR/vc-di-bbs/ Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-05-18
92 VCs Development VCWG JSON Web Signatures for Data Integrity Proofs This specification describes a JSON Web Signature Suite created in 2020 for the Verifiable Credentials Data Integrity Proof specification. The Signature Suite utilizes Detached JWS signatures to provide support for a subset of the digital signature algorithms registered with IANA. https://www.w3.org/TR/vc-jws-2020/ Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-01-27
93 VCs Development VCWG Securing Verifiable Credentials using JSON Web Tokens This specification defines how Verifiable Credentials can be represented as JSON Web Tokens (JWT) [RFC7519] and secured using JSON Web Signatures (JWS) [RFC7515]. https://www.w3.org/TR/vc-jwt/ Specification Working Draft Verifiable Credentials Working Group Cryptography Verifiable Credentials WG 2023-05-15
94 VCs Development W3C CCG https://w3c-ccg.github.io/ Verifiable Credentials, Decentralized Identifiers Credentials Community Group The mission of the Credentials Community Group is to explore the creation, storage, presentation, verification, and user control of credentials. We focus on a verifiable credential (a set of claims) created by an issuer about a subject—a person, group, or thing—and seek solutions inclusive of approaches such as: self-sovereign identity; presentation of proofs by the bearer; data minimization; and centralized, federated, and decentralized registry and identity systems. Our tasks include drafting and incubating Internet specifications for further standardization and prototyping and testing reference implementations. https://www.w3.org/community/credentials/ Working Group Credentials Community Group Credentials Community Group 2014-08-19 https://github.com/w3c-ccg/community https://lists.w3.org/Archives/Public/public-credentials/
95 VCs Development CCG W3C CCG meeting transcripts This repo contains the meeting archives for the W3C-CCG (Credentials Community Group), including transcripts based on the IRC logs and audio files for our regular meetings, ancillary material such as slide presentations, etc. The archives for 2014-2019 can be found here. COMMUNITY: W3C Credentials Community Group meeting transcripts - GitHub - w3c-ccg/meetings: COMMUNITY: W3C Credentials Community Group meeting transcripts https://github.com/w3c-ccg/meetings Page Credentials Community Group
96 VCs Development CCG RWOT, IIW W3C CCG announcements Announcements and events associated with the W3C Credentials CG https://github.com/w3c-ccg/announcements Page Credentials Community Group
97 VCs Development CCG W3C CCG Work Item Process This lets you write your specs in markdown, or technically bikeshed -- a markdown document, with special extensions understood by the bikeshed tool. The bikeshed tool is run on-commit via the spec-prod github action, generating the familiar "spec looking" ReSpec format. ReSpec is just html with a javascript ReSpec library. https://github.com/w3c-ccg/workitem-process Page Credentials Community Group
98 VCs Development CCG Global Open Badges Workgroup, Verifiable Credentials WG, Credentials Commiunity Group, Schema.org WORK ITEM: Drafts and Ideas of Educational and Occupational Verifiable Credentials - w3c-ccg/edu_occ_verifiable_credentials Work on describing credentials is occurring within the IMS Global Open Badges Workgroup, W3C Verifiable Credentials Working Group, W3C Credentials Commiunity Group, Educational and Occupational Credentials in Schema.org Community Group, and Credential Engine/CTDL.<br><br>This effort will result in requirements, use cases, and/or draft specs to be formalized in the appropriate standards group https://github.com/w3c-ccg/edu_occ_verifiable_credentials Code Credentials Community Group Credentials Community Group
99 VCs Development CCG WORK ITEM: Verifiable Credentials Examples This GitHub Pages Website hosts example credentials, as well as documents needed to construct them. When contributing an example, you are encouraged to provide everything needed to generate an verify a credential. Do your best not to include ANY broken links or missing documentation. If possible, try to make the credential id resolvable as well. https://github.com/w3c-ccg/vc-examples Code Credentials Community Group Credentials Community Group
100 VCs Development CCG Verifiable Credentials Extension Registry Verifiable Credentials Extension Registry - This document contains a list of all known Verifiable Credential extensions and their associated specifications. Credentials Community Group https://w3c-ccg.github.io/vc-extension-registry/ Report draft Credentials Community Group Credentials Community Group 2022-11-14
101 VCs Development CCG Verifiable Credentials Extension Registry Markus Sabadello Ed25519Signature2018 This specification describes a standard signature suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset Normalization Algorithm [RDF-DATASET-NORMALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and Ed25519 [ED25519] as the signature algorithm. https://w3c-ccg.github.io/lds-ed25519-2018/ Report draft Credentials Community Group Proof Methods Credentials Community Group 2021-07-23
102 VCs Development CCG Verifiable Credentials Extension Registry Manu Sporny, Dave Longley RsaSignature2018 This specification describes the RSA Signature Suite created in 2018 for the Linked Data Signatures [LD-SIGNATURES] specification. It uses the RDF Dataset CANONICALIZATION Algorithm [RDF-DATASET-CANONICALIZATION] to transform the input document into its canonical form. It uses SHA-256 [RFC6234] as the message digest algorithm and the RS256 algorithm defined in JSON Web Signatures [RFC7515] as the signature algorithm. https://w3c-ccg.github.io/lds-rsa2018/ Report draft Credentials Community Group Proof Methods Credentials Community Group 2020-05-26
103 VCs Development CCG Verifiable Credentials Extension Registry Manu Sporny, Dave Longley CredentialStatusList2017 A simple list-based mechanism for publishing and checking the status of a credential https://w3c-ccg.github.io/vc-csl2017/ Report Credentials Community Group Status Methods Credentials Community Group 2020-12-29
104 VCs Development CCG Ecdsa Secp256k1 Signature 2019 This specification describes the Ecdsa Secp256k1 Signature created in 2019 for the Linked Data Signatures specification https://w3c-ccg.github.io/lds-ecdsa-secp256k1-2019/ Code Draft Credentials Community Group 2020-04-08
105 VCs Development CCG Verifiable Credential JSON Schemas The [VC_DATA_MODEL](https://www.w3.org/TR/vc-data-model/) specifies the models used for Verifiable Credentials and Verifiable Presentations, and explains the relationships between three parties: issuer, holder, and verifier. A critical piece of infrastructure out of the scope of those specifications is the Credential Schema. A mechanism to use JSON Schemas with Verifiable Credentials - GitHub - w3c/vc-json-schema: A mechanism to use JSON Schemas with Verifiable Credentials https://github.com/w3c-ccg/vc-json-schemas Code Credentials Community Group 2023-05-24
106 VCs Development CCG Traceability Vocabulary v0.1 This specification describes a Linked Data vocabulary for asserting Verifiable Credentials related to supply chain and other traceability information, similar to what is often referred to as "provenance", including country of origin, chemical properties, mechanical properties, and other attributes of products and materials. VCs using these terms can then be used to help determine the legitimacy of organizations participating in global trade and the status of the products and materials described therein https://w3c-ccg.github.io/traceability-vocab/ https://w3c-ccg.github.io/traceability-vocab/resources/product-identifier-verification-from-identification-key-license.png Specification v0.1 Credentials Community Group Credentials Community Group 2023-05-23
107 VCs Development DIF Claims and Credentials Working Group Join this group to contribute to the standards and technology that create, exchange, and verify claims and credentials in a decentralized identity ecosystem. For example, a cryptographically verifiable credential that proves an individual has a college degree or is of a certain age. Our members focus on specs that are vendor agnostic and based on industry standards. https://identity.foundation/working-groups/claims-credentials.html page Claims and Credentials Working Group 2020-09-18
108 VCs Development DIF presentation-exchange Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) - GitHub - decentralized-identity/presentation-exchange: Specification that codifies an inter-related pair of data formats for defining proof presentations (Presentation Definition) and subsequent proof submissions (Presentation Submission) https://github.com/decentralized-identity/presentation-exchange Code Claims and Credentials Working Group 2023-05-31
109 VCs Development DIF presentation-request Requirements Analysis and Protocol Design for a VC Presentation Request Format Requirements Analysis and Protocol Design for a VC Presentation Request Format - GitHub - decentralized-identity/presentation-request: Requirements Analysis and Protocol Design for a VC Presentation Request Format https://github.com/decentralized-identity/presentation-request Code Claims and Credentials Working Group 2020-01-08
110 VCs Development DIF Credential Manifest Credential Manifests do not themselves define the contents of the output credential(s), the process the Issuer uses to evaluate the submitted inputs, or the protocol Issuers, Subjects, and their User Agents rely on to negotiate credential issuance. Instead, Credential Manifests are a data model for issuers to publish and/or send individually to would-be holders, allowing the software of the latter to understand and negotiate an issuance process. https://identity.foundation/credential-manifest/ page Claims and Credentials Working Group 2023-05-04
111 VCs Development Personal Kyle Den Hartog Example Design of an Authorization System with Verifiable Credentials and the Tradeoffs The primary focus of this blog post is to highlight the different problems that are likely to occur when going down the path of building an authorization system with verifiable credentials. I’ll be sure to keep things at a higher level so that anyone can understand these tradeoffs, but take you through the details that would be thought through by an architect designing the system. https://kyledenhartog.com/example-authz-with-VCs/ Post Development 2021-06-22
112 VCs Development 51 Nodes Indexing and Querying Revoked Verifiable Credentials this article describes a simple approach to revoke verifiable credentials and a decentralized and efficient way to index and query those revoked credentials using the [Graph protocol](https://thegraph.com/en/). Due to its immutability and censorship resistance, the Blockchain seems to be a suitable place to manage identities and credentials. However, querying the data on the blockchain in a trusted and… https://medium.com/51nodes/indexing-and-querying-revoked-verifiable-credentials-e229dc2781d4 Post Development 2022-07-01
113 VCs Development CCG Mailing List Nikos Fotiou VC Issuance based on OAuth 2.0 We design, implement, and evaluate a solution for achieving continuous authorization of HTTP requests exploiting Verifiable Credentials (VCs) and OAuth 2.0. Specifically, we develop a VC issuer that acts as an OAuth 2.0 authorization server, a VC verifier that transparently protects HTTP-based resources, and a VC wallet implemented as a browser extension capable of injecting the necessary authentication data in HTTP requests without needing user intervention. https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0084.html Discussion Development Credentials Community Group 2022-04-14
114 VCs Development CCG Mailing List Orie Steele Supporting VC-JWT and BBS+ Presentation Exchange in the VC-HTTP-API [https://github.com/OR13/GNARLY](https://github.com/OR13/GNARLY)  (while we wait for a better name...)<br><br>This demo API and Spec has a number of improvements over the current<br><br>VC-HTTP-API, including tested support for VC-JWT, JsonWebSignature2020 and<br><br>BBS+ Selective Disclosure Presentation Exchange. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0313.html Discussion Development Credentials Community Group 2021-07-31
115 VCs Development CCG Mailing List https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html Joe Andrieu Updated VC-API diagram for Supply Chain flow I updated the supply chain version of the data flow diagram for verification. https://lists.w3.org/Archives/Public/public-credentials/2021Sep/0141.html https://i.imgur.com/mH5TBtU.png Discussion Development Credentials Community Group 2021-09-28
116 VCs Development CCG Mailing List Manu Sporny re: VC API: handling large documents client to server Typical solutions to this problem require that you put the binary data outside of the VC, if at all possible. This works well for common static images such as logos. It is also possible to split the VC into two VCs... one with the machine-readable data from the issuer (with a digital signature) and one with the image data from any source (without a digital signature, since, if hashlinked, the signature will verify the validity of the image data). That latter approach can be more privacy preserving AND more complex than many might feel is necessary. https://lists.w3.org/Archives/Public/public-credentials/2022Feb/0035.html Discussion Development Credentials Community Group 2022-02-10
117 VCs Development CCG Mailing List Manu Sporny VC-API interoperability test suites ready for experimental integration * [The VC API test suite for basic issuer interop is here](https://w3c-ccg.github.io/vc-api-issuer-test-suite/)<br>* [The VC API test suite for basic verifier interop is here](https://w3c-ccg.github.io/vc-api-verifier-test-suite/)<br>* [The Data Integrity test suite for Ed25519Signature2020 interop is here](https://w3c-ccg.github.io/di-ed25519-test-suite/) https://lists.w3.org/Archives/Public/public-credentials/2022Apr/0126.html Discussion Development Credentials Community Group 2022-04-26
118 VCs Development CCG Mailing List Manu Sporny Cross-industry VC API test suite achieves first multi-vendor interop for issue/verify We are happy to announce today that we have our first demonstration of cross-vendor interoperability between Danube Tech and Digital Bazaar for the VC Issuer API and VC Verifier API. The test suites test the OAS definition files (which are used to generate the specification):<br>* [2.1 Verify Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-verifier-test-suite/#Verify%20Credential%20-%20Data%20Integrity)<br>* [2.1 Issue Credential - Data Integrity](https://w3c-ccg.github.io/vc-api-issuer-test-suite/#Issue%20Credential%20-%20Data%20Integrity) https://lists.w3.org/Archives/Public/public-credentials/2022May/0041.html Discussion Development Credentials Community Group 2022-05-18
119 VCs Development CCG Mailing List Joe Andrieu Diagrams for VC HTTP API work [was Re: [AGENDA] VC HTTP API Work Item - August 17th 2021] a. *Holder* The entity who holds the VC once issued and later presents it for verification.<br>b. *Holder Application *The software or service that allows holders to manage their credentials. Often called a wallet. For symmetry, it could be called a Holder Service.<br>c. *Storage Service *The software or service that actually stores VCs long term (on behalf of the holder)<br>d. *Issuer Role* The website or software that provides issuing functionality to a holder on behalf of that issuer)<br>e. *Issuer Service* Software or service that actually signs VCs and VPs) This component is used by both the issuer (to mint VCs) and the holder (to create VPs for presentation)<br>f. *Verifier Role* The website or software that uses a Verification Service as part of its decision making process for providing services to holders.<br>g. *Verifier Service *The software or service that verifies VCs and VPs by checking proofs and checking status. https://lists.w3.org/Archives/Public/public-credentials/2021Aug/0231.html https://i.imgur.com/4hCNLVA.png Discussion Development Credentials Community Group 2021-08-16
120 VCs Development CCG Mailing List Brian Richter Issuer API Cross Trust Boundary Scoping - VC-HAPI (f.k.a. VC-HTTP-API) I think I'm starting to understand how RAR fits into this picture. This decision can be made for us by punting the question to the authorization process entirely. With RAR we can force the user to authorize for the actual subject they are issuing the credential about. Is Alice authorized to issue VCs with claims about did:example:12345? To answer that question Alice asks for a token with the following RAR request https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0263.html Discussion Development Credentials Community Group 2021-07-24
121 VCs Development CCG Mailing List Justin Richer RAR Structures for VC HTTP API It seemed like a good idea when I first invented it a decade ago:[https://blue-button.github.io/blue-button-plus-pull/#scopes](https://blue-button.github.io/blue-button-plus-pull/#scopes) or when it got pulled into other efforts like [https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html](https://openid.net/specs/openid-heart-fhir-oauth2-1_0-2017-05-31.html)… and Orie even suggested the following set of parameterized scopes for this API:<br>'create:credentials': Grants permission to create credentials<br>'derive:credentials': Grants permission to derive credentials<br>'create:presentations': Grants permission to create presentations<br>'verify:presentations': Grants permission to verify presentations<br>'exchange:presentations': Grants permission to exchange presentations<br>So what’s the problem? I can say with full confidence after years of experience building and deploying systems to support parameterized scopes like this that they are fragile, awkward, and lead to insecure corner cases. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0208.html Discussion Development Credentials Community Group 2021-07-21
122 VCs Development CCG Mailing List Manu Sporny Bikeshed: Renaming the VC HTTP API the fundamental issue is that stringing a bunch of consonants together ("HTTP") rarely leads to something easy to say in conversation. https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0131.html Discussion Development Credentials Community Group 2021-07-17
123 VCs Development CCG Mailing List Kerri Lemoie Question About Signatures & Contexts Is a VC still considered to be valid if it contains fields that are not described in its context file(s)? Does it depend on the signature type? https://lists.w3.org/Archives/Public/public-credentials/2021Jul/0290.html Discussion Development Credentials Community Group 2021-07-30
124 VCs Development CCG Mailing List Bob Wyman Any Good use case of PAM (Privileged account Management) using Vcs A common example of this is when someone uses a "Power of Attorney," to sign a contract. When they do, they typically sign documents with their own names and an annotation "on behalf of," "for," or "by power of attorney," they don't forge the signature of the one who granted the power of attorney. https://lists.w3.org/Archives/Public/public-credentials/2021Nov/0028.html Discussion Development Credentials Community Group 2021-11-06
125 VCs Development Mattr Paper based Verifiable Credentials Paper-based Verifiable Credentials allow us to have a low-tech solution for adopting VC's in situations where access to a phone cannot be guaranteed. This presentation looks at how this solution can be used to aid with the distribution of Vaccine Credentials. Paper-based verifiable credentials allow us to have a low-tech solution for adopting verifiable credential's in situations where access to a phone cannot be ... https://www.youtube.com/watch?v=EXvWxFjHvdY Video Development 2021-03-02
126 VCs Development Trusted Digital Web Using Paper-based Structured Credentials to Humanize Verifiable Credentials User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages. Michael Herman User Scenario: ABC Grocery wants to use the Trusted Digital Web to issue a Purchase Order for 10 cabbages from David's Cabbages.This tutorial was inspired by... https://www.youtube.com/watch?v=kM30pd3w8qE Video Rough Cut User Experience 2021-11-19
127 VCs Development WebofTrustInfo Manu Sporny RWoT Rendering Verifiable Credentials This paper explores ways in which the Verifiable Credentials data model could be extended to support visual, audio, and physical renderings for Verifiable Credentials. https://github.com/WebOfTrustInfo/rwot11-the-hague/blob/master/advance-readings/rendering-verifiable-credentials.md Paper User Experience 2022-07-17
128 Decentralized Identifiers CCG A Primer for Decentralized Identifiers An introduction to self-administered identifiers for curious people A Decentralized Identifier (DID) is a new type of identifier that is globally unique, resolvable with high availability, and cryptographically verifiable. DIDs are typically associated with cryptographic material, such as public keys, and service endpoints, for establishing secure communication channels. DIDs are useful for any application that benefits from self-administered, cryptographically verifiable identifiers such as personal identifiers, organizational identifiers, and identifiers for Internet of Things scenarios. For example, current commercial deployments of W3C Verifiable Credentials heavily utilize Decentralized Identifiers to identify people, organizations, and things and to achieve a number of security and privacy-protecting guarantees. This document is an introduction to the concept of Decentralized Identifiers. https://w3c-ccg.github.io/did-primer/ https://w3c-ccg.github.io/did-primer/did-primer-diagrams/urn-format.png Report Main Credentials Community Group 2021-11-11 https://github.com/w3c-ccg/did-primer
129 Decentralized Identifiers W3C Markus Sabadello Danube Tech, Sovrin Foundation, OASIS XDI TC Vienna W3C Workshop on Privacy and Linked Data Decentralized IDentifers (DIDs) - Developed at Rebooting-the-Web-of-Trust workshop and W3C Credentials CG<br>- Persistent, dereference-able, cryptographically verifable identifers<br>- Registered in a blockchain or other decentralized network https://www.w3.org/2018/vocabws/presentations/Sabadello.pdf https://i.imgur.com/7NRcJbq.png Presentation Main 2018-04-17
130 Decentralized Identifiers Identity Foundation Decentralized Identifiers (DID) 1.0 specification approved as W3C Recommendation Announcing the [Decentralized Identifiers (DID) v1.0 specification](https://www.w3.org/TR/did-core/) as an open web standard signals that it is technically sound, mature, and ready for widespread adoption. Having an established v1.0 specification allows work to continue with renewed energy and focus, not only at the many groups meeting at DIF, but across the digital identity community. The W3C has approved the DIDCore V1.0 spec as an official Recommentdation; DIDs are now an open web standard ready for use and further development https://blog.identity.foundation/w3cdidspec-2/ Post Main 2022-06-22
151 Decentralized Identifiers DIDWG DID Implementation Guide This document acts as a technical narrative for the implementation of DID methods and is expected to cover many topics related to that subject that a developer may wish to consider, including guidance around implementation details that may also be used for third party evaluation of an authored DID method via the DID-RUBRIC. https://w3c.github.io/did-imp-guide/ https://w3c.github.io/did-imp-guide/diagrams/representation-specific-and-foreign-entries.png Note Literature DID Working Group 2021-11-04 https://github.com/w3c/did-imp-guide
152 Decentralized Identifiers DIDWG W3C DID Test Suite and Implementation Report This document describes the did core test suite, and summarizes the latest test results. https://w3c.github.io/did-test-suite/ Internal Literature DID Working Group 2023-01-17 https://github.com/w3c/did-test-suite
153 Decentralized Identifiers DIDWG W3C Decentralized Characteristics Rubric v1.0 This rubric presents a set of criteria which an Evaluator can apply to any DID Method based on the use cases most relevant to them. We avoid reducing the Evaluation to a single number because the criteria tend to be multidimensional and many of the possible responses are not necessarily good or bad. It is up to the Evaluator to understand how each response in each criteria might illuminate favorable or unfavorable consequences for their needs. https://w3c.github.io/did-rubric/ Internal Literature DID Working Group 2022-01-11 https://github.com/w3c/did-rubric
154 Decentralized Identifiers DIDWG Well Known DID Configuration The DID Configuration resource provides proof of a bi-directional relationship between the controller of an origin and a DID via cryptographically verifiable signatures that are linked to a DID's key material. This document describes the data format of the resource and the resource location at which origin controllers can publish their DID Configuration. This repo contains proposals and links to proposals for .well-known uris related to DIDs, Hubs and Agents. See IETF RFC5785 for more details on Defining Well-Known Uniform Resource Identifiers. https://identity.foundation/.well-known Specification Supporting DID Working Group 2020-12-10 https://github.com/decentralized-identity/.well-known
155 Decentralized Identifiers CCG Decentralized Identifier Resolution (DID Resolution) v0.3 DID resolution is the process of obtaining a DID document for a given DID. This is one of four required operations that can be performed on any DID ("Read"; the other ones being "Create", "Update", and "Deactivate"). The details of these operations differ depending on the DID method. Building on top of DID resolution, DID URL dereferencing is the process of retrieving a representation of a resource for a given DID URL. Software and/or hardware that is able to execute these processes is called a DID resolver. https://w3c-ccg.github.io/did-resolution/ https://w3c-ccg.github.io/did-resolution/diagrams/https-dereference-example-1.png Specification Supporting Credentials Community Group 2023-01-18 https://github.com/w3c-ccg/did-resolution
156 Decentralized Identifiers GoDiddy https://iiw.idcommons.net/2C/_godiddy.com_-_Universal_DID_Services Markus Sabadello godiddy.com - Universal DID Services Basic functions are creating, resolving, updating, and deactivating DIDs across multiple DID methods and networks. Advanced functions include key management, search, transfer of DIDs, lookup of historical DID document versions, notification of DID-related events, and more. https://godiddy.com site Supporting 2021-05-06 https://docs.godiddy.com/ https://api.godiddy.com/
157 Decentralized Identifiers IDCommons Markus Sabadello Standard Interfaces for DID Create/Update/Deactivate - There is an attempt to specify abstract interfaces if you want to Create/Update/Deactivate a did that could be implemented for all did methods.<br>- The idea of this specification is to provide a standard with the same assumptions as with resolution. It should be in an abstract level, meaning it should specify the inputs and outputs of creating/updating/deactivating a did but not how it should be implemented. https://iiw.idcommons.net/3C/_Standard_Interfaces_for_DID_Create/Update/Deactivate Session Notes Supporting 2021-07-17

7
_posts/web-standards/w3c/2020-01-10-verifiable-credentials.md
View File

@ -1,13 +1,12 @@
---
date: 2020-01-10
title: "Verifiable Credentials - W3C"
name: Verifiable Credentials
layout: standards
headings: ["About","Comparisons","Working Group","Credentials Community Group","Claims and Credentials WG","Development","Varieties","Interoperability","Literature","Use Case","User Experience"]
headings: ["About","Comparisons","Implementations","Literature","Use Case"]
description: a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
excerpt: >
Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019.
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","OAuth","FIDO","Claims and Credentials WG"]
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","Claims and Credentials WG"]
categories: ["Web Standards"]
permalink: web-standards/w3c/verifiable-credentials/
header:
@ -23,6 +22,6 @@ redirect_from:
- specs-standards/verifiable-credentials/
- web-standards/verifiable-credentials/
- specs-standards/verifiable credentials/
last_modified_at: 2023-05-08
last_modified_at: 2023-08-29
---

19
_posts/web-standards/w3c/2023-08-29-VCs-Standards-and-Development.md Normal file
View File

@ -0,0 +1,19 @@
---
title: "Verifiable Credentials - Working Groups, Standards and Development"
name: VCs Development
layout: standards
headings: ["Verifiable Credentials Working Group","Credentials Community Group","Claims and Credentials Working Group","Varieties","Development","User Experience"]
description: a standard way to express credentials on the Web in a way that is cryptographically secure, privacy respecting, and machine-verifiable.
excerpt: >
Verifiable credentials (VCs) are the electronic equivalent of the physical credentials that we all possess today, such as: plastic cards, passports, driving licenses, qualifications and awards, etc. The data model for verifiable credentials is a World Wide Web Consortium Recommendation, "Verifiable Credentials Data Model 1.0 - Expressing verifiable information on the Web" published 19 November 2019.
tags: ["W3C","Verifiable Credentials","Credentials Community Group","VC-WG","JSON-LD","OAuth","FIDO","Claims and Credentials WG"]
categories: ["Web Standards","Development"]
permalink: web-standards/w3c/verifiable-credentials/standards-and-development/
header:
image:
caption:
teaser:
canonical_url: "https://decentralized-id.com/web-standards/w3c/verifiable-credentials/standards-and-development/"
last_modified_at: 2023-08-29
---