diff --git a/jsonschema-core.xml b/jsonschema-core.xml
index a93c377d..49df09c2 100644
--- a/jsonschema-core.xml
+++ b/jsonschema-core.xml
@@ -399,6 +399,13 @@
                         of any vocabulary, there is no analogous mechanism to indicate individual
                         keyword usage.
                     </t>
+                    <t>
+                        A schema vocabulary can be defined by anything from an informal description
+                        to a standards proposal, depending on the audience and interoperability
+                        expectations.  In particular, in order to facilitate vocabulary use within
+                        non-public organizations, a vocabulary specification need not be published
+                        outside of its scope of use.
+                    </t>
                 </section>
                 <section title="Meta-Schemas">
                     <t>
@@ -2061,13 +2068,6 @@
                 The current URI for the corresponding meta-schema is:
                 <eref target="https://json-schema.org/draft/2020-12/meta/applicator"/>.
             </t>
-            <t>
-                Updated vocabulary and meta-schema URIs MAY be published between
-                specification drafts in order to correct errors.  Implementations
-                SHOULD consider URIs dated after this specification draft and
-                before the next to indicate the same syntax and semantics
-                as those listed here.
-            </t>
             <section title="Keyword Independence">
                 <t>
                     Schema keywords typically operate independently, without
@@ -2497,13 +2497,6 @@
                 The current URI for the corresponding meta-schema is:
                 <eref target="https://json-schema.org/draft/2020-12/meta/unevaluated"/>.
             </t>
-            <t>
-                Updated vocabulary and meta-schema URIs MAY be published between
-                specification drafts in order to correct errors.  Implementations
-                SHOULD consider URIs dated after this specification draft and
-                before the next to indicate the same syntax and semantics
-                as those listed here.
-            </t>
 
             <section title="Keyword Independence">
                 <t>
diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
index e12c6cd2..3a3cbf61 100644
--- a/jsonschema-validation.xml
+++ b/jsonschema-validation.xml
@@ -1241,6 +1241,24 @@
                     an additional example.  If "examples" is absent, "default"
                     MAY still be used in this manner.
                 </t>
+                <t>
+                    Implementations MAY use the values of "namedExamples", if present, as
+                    additional examples.  If "examples" is absent, "namedExamples"
+                    MAY still be used in this manner.
+                </t>
+            </section>
+
+            <section title='"namedExamples"'>
+                <t>
+                    The value of this keyword MUST be an object.
+                    There are no restrictions placed on the values within the object.
+                </t>
+                <t>
+                    This keyword can be used to provide named sample JSON values associated with a
+                    particular schema, for the purpose of illustrating usage, and to make them
+                    available for referencing outside of the schema.  It is RECOMMENDED that these
+                    values be valid against the associated schema.
+                </t>
             </section>
         </section>
 
diff --git a/meta/meta-data.json b/meta/meta-data.json
index 05cbc22a..7a48a934 100644
--- a/meta/meta-data.json
+++ b/meta/meta-data.json
@@ -32,6 +32,9 @@
         "examples": {
             "type": "array",
             "items": true
+        },
+        "namedExamples": {
+            "type": "object"
         }
     }
 }