Skip to content

Commit f092308

Browse files
authored
Update index.bs
html validation
1 parent e147fc6 commit f092308

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

index.bs

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -332,7 +332,7 @@ To understand the extent of the various standards, is it possible to refer to Mi
332332
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:
333333

334334
* **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).
335-
* **Identifiers**: [DIDs](https://www.w3.org/TR/did-core/) and the [DID methods](https://w3c.github.io/did-spec-registries/\#did-methods), or [WebID](https://w3c.github.io/WebID/spec/identity/).
335+
* **Identifiers**: [DIDs](https://www.w3.org/TR/did-core/) and the [DID methods](https://w3c.github.io/did-spec-registries/#did-methods), or [WebID](https://w3c.github.io/WebID/spec/identity/).
336336
* **Encoding Schemas:** JSON, JSON-LD, CBOR, CBOR-LD.
337337
* **Securing Mechanisms:** Each mechanism may or may not support different privacy features or be quantum-resistant:
338338
* **Enveloped Formats (Credential Formats)**: The proof wraps around the serialization of the credential.
@@ -341,7 +341,7 @@ This is why several Standards Development Organizations (SDOs) such as the World
341341
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/).
342342
* **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/).
343343
* **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., [Bitstring Status List v1.0](https://www.w3.org/TR/vc-bitstring-status-list/)), and Cryptographic Accumulators, etc..
344-
* **Communication Protocols**: for the different phases of Issuance and Presentation (e.g., [OID4VCI](https://openid.github.io/OpenID4VCI/openid-4-verifiable-credential-issuance-wg-draft.html), [OID4VP](https://openid.net/specs/openid-4-verifiable-presentations-1\0.html), [SIOPv2](https://openid.net/specs/openid-connect-self-issued-v2-1_0.html)).
344+
* **Communication Protocols**: for the different phases of Issuance and Presentation (e.g., [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)).
345345

346346
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).
347347

0 commit comments

Comments
 (0)