From dbd2213da461022353ec9da959771dead68bcd39 Mon Sep 17 00:00:00 2001 From: Simone Onofri Date: Tue, 25 Feb 2025 16:34:30 +0100 Subject: [PATCH] [standards] adding more standards IETF, ISO --- index.bs | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/index.bs b/index.bs index 47e17f6..2e208a9 100644 --- a/index.bs +++ b/index.bs @@ -422,7 +422,7 @@ Note: Not all of the technologies indicated are standard, so they should not be This is why several Standards Development Organizations (SDOs) such as the World Wide Web Consortium (W3C), the Internet Engineering Task Force (IETF), the OpenID Foundation (OIDF), and the Decentralized Identity Foundation (DIF) are coordinating to standardize the components and how they should communicate: -* **Data Models:** abstract models for Credentials and Presentation such as the [Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/) and mDL in ISO/IEC [18013-5:2021](https://www.iso.org/standard/69084.html). +* **Data Models:** abstract models for Credentials and Presentation such as the [Verifiable Credentials Data Model](https://www.w3.org/TR/vc-data-model/) and mDL in ISO/IEC [18013-5:2021](https://www.iso.org/standard/69084.html), and [IETF SD-JWT VC](https://datatracker.ietf.org/doc/draft-ietf-oauth-sd-jwt-vc/). * **Identifiers**: [DIDs](https://www.w3.org/TR/did-core/) and the [DID methods](https://w3c.github.io/did-spec-registries/#did-methods), [IndieAuth](https://www.w3.org/TR/indieauth/), [WebID](https://w3c.github.io/WebID/spec/identity/), X.509, URLs, or URIs. * **Encoding Schemas:** JSON, JSON-LD, CBOR, CBOR-LD. * **Securing Mechanisms:** Each mechanism may or may not support different privacy features or be quantum-resistant: @@ -432,7 +432,7 @@ This is why several Standards Development Organizations (SDOs) such as the World The mechanism to use VCDM with JOSE/COSE is described in [Securing Verifiable Credentials using JOSE and COSE](https://www.w3.org/TR/vc-jose-cose/). * **Embedded Formats (Signature Algorithms):** The proof is included in the serialization alongside the credentials (e.g., BBS, ECDSA, EdDSA). The mechanism is described in [Verifiable Credential Data Integrity 1.0](https://www.w3.org/TR/vc-data-integrity/). New securing mechanisms are coming up, like [SD-BLS](https://arxiv.org/abs/2406.19035) (which uses BLS), and ongoing efforts to use BBS. * **Status Information (Revocation Algorithms)**: *Issuers* can implement several ways to keep the credential's status up to date, such as a Revocation List, a Status List (e.g., [W3C Bitstring Status List v1.0](https://www.w3.org/TR/vc-bitstring-status-list/), [Status Assertions](https://datatracker.ietf.org/doc/html/draft-demarco-oauth-status-assertions), [Token Status List](https://datatracker.ietf.org/doc/html/draft-ietf-oauth-status-list-03)), and Cryptographic Accumulators, etc.. -* **Communication Protocols**: for the different phases of Issuance and Presentation such as [OID4VCI](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html), [OID4VP](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html), [SIOPv2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html), ISO REST’s API, and [Verifiable Credentials API](https://github.com/w3c-ccg/vc-api). +* **Communication Protocols**: for the different phases of Issuance and Presentation such as [OID4VCI](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html), [OID4VP](https://openid.github.io/OpenID4VP/openid-4-verifiable-presentations-wg-draft.html), [SIOPv2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html), mDoc REST’s API, mDoc JavaScript API, and [Verifiable Credentials API](https://github.com/w3c-ccg/vc-api). Note: This list is representative. For more detailed information, please refer to the [Comparison Matrix](https://docs.google.com/spreadsheets/d/1X93ptJcmfX1NZEo5E7ElnqJ-knDS4Dj6JOYSJ_2PsUw/edit#gid=1084392809).