From 6f73904346833567ac0686afff96b441a90cd112 Mon Sep 17 00:00:00 2001 From: Manu Sporny Date: Sat, 18 Nov 2023 15:35:04 -0500 Subject: [PATCH] Fix broken links in specification. --- index.html | 14 +++++++------- 1 file changed, 7 insertions(+), 7 deletions(-) diff --git a/index.html b/index.html index 2f9fa88a2..98f0ff6e5 100644 --- a/index.html +++ b/index.html @@ -3988,7 +3988,7 @@

JSON-LD

As elaborated upon in Section -, some software applications +, some software applications might not perform generalized JSON-LD processing. Authors of conforming documents are advised that interoperability might be reduced if JSON-LD keywords in the `@context` value are used to globally affect values in a @@ -4003,7 +4003,7 @@

JSON-LD

In order to increase interoperability, conforming document authors are urged to not use JSON-LD features that are not easily detected when performing - + credential-type-specific processing. These features include:

@@ -5560,17 +5560,17 @@

Inappropriate Use

While valid cryptographic signatures and successful status checks signify the reliability of credentials, they do not signify that all credentials are interchangeable for all contexts. It is crucial that verifiers -also validate any claims which might be relevant, considering the source and -nature of the claim as well as privilege or service for which the credential is -presented. +also validate any claims which might be relevant, +considering the source and nature of the claim as well as privilege or service +for which the credential is presented.

For instance, in scenarios where a certified medical diagnosis is required, a self-asserted credential carrying the necessary data might not suffice because it lacks validity from an authoritative medical source. To ensure the propriety of credential use, stakeholders are urged to assess the -credential's relevance and authority within the specific context of their -intended application. +credential's relevance and authority within the +specific context of their intended application.