From 1d7b5547ad0e0487392a70b4adb9abe2fd64f88c Mon Sep 17 00:00:00 2001
From: Jeffrey Yasskin <jyasskin@gmail.com>
Date: Thu, 30 Nov 2023 09:34:20 -0500
Subject: [PATCH] Provide guidance to specification authors on integrity
 checking of resources.

---
 index.html | 8 +++++---
 1 file changed, 5 insertions(+), 3 deletions(-)

diff --git a/index.html b/index.html
index e964c32e7..6e702e66d 100644
--- a/index.html
+++ b/index.html
@@ -3128,9 +3128,11 @@ <h2>Integrity of Related Resources</h2>
 an object in the <code>relatedResource</code> array.
         </p>
         <p>
-Any failure to verify content integrity information that is vital to the
-validity of a <a>conforming document</a>, such as the integrity of content
-identified by related `@context` URLs, SHOULD result in a validation error.
+Specification authors that write algorithms that fetch a resource based on the
+`id` of an object inside a <a>conforming document</a> need to consider whether
+that resource's content is vital to the validity of that document. If it is, the
+specification MUST produce a validation error unless the resource has the
+expected media type and its bytes hash to the expected digest.
         </p>
         <p>
 Implementers are urged to consult appropriate sources, such as the