From 365533303e33e4416069f930c3f88f62175eef27 Mon Sep 17 00:00:00 2001
From: Manu Sporny <msporny@digitalbazaar.com>
Date: Sun, 20 Aug 2023 17:18:46 -0400
Subject: [PATCH] Mitigate context risk when transitioning to Proposed
 Recommendation.

---
 index.html | 11 +++++++++++
 1 file changed, 11 insertions(+)

diff --git a/index.html b/index.html
index 73c06e6ed..4163200c3 100644
--- a/index.html
+++ b/index.html
@@ -5563,6 +5563,17 @@ <h3>Base Context</h3>
 This section lists cryptographic hash values that might change during the
 Candidate Recommendation phase based on implementer feedback that requires
 the referenced files to be modified.
+<br><br>
+The Working Group is expecting all of the terms and URLs supplied in the
+JSON-LD Context to be either stabilized, or removed, before the publication of
+this specification as a Proposed Recommendation. While that means that this
+specification could be delayed if dependencies such as [[?VC-DATA-INTEGRITY]],
+[[?VC-JOSE-COSE]], SD-JWT, [[?VC-JSON-SCHEMA-2023]], or status list
+do not enter the Proposed Recommendation phase around the same time frame, the
+Working Group is prepared to remove the dependencies if an undue burden is
+placed on transitioning to the Recommendation phase. This is a calculated
+risk that the Working Group is taking and has a mitigation strategy in place
+to ensure the timely transition of this specification to a Recommendation.
         </p>
         <p>
 Implementations MUST treat the base context value, located at