From 64ca2b9b3af8478546563e8c69433b6edb11e0af Mon Sep 17 00:00:00 2001
From: Henry Andrews <andrews_henry@yahoo.com>
Date: Sat, 5 Sep 2020 20:07:32 -0700
Subject: [PATCH] Clarify how "deprecated" works w/arrays & objects

---
 jsonschema-validation.xml | 10 +++++-----
 1 file changed, 5 insertions(+), 5 deletions(-)

diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
index 4f329b42..58165006 100644
--- a/jsonschema-validation.xml
+++ b/jsonschema-validation.xml
@@ -1083,7 +1083,7 @@
     "contentSchema": {
         "type": "array",
         "minItems": 2,
-        "items": [
+        "prefixItems": [
             {
                 "const": {
                     "typ": "JWT",
@@ -1177,10 +1177,10 @@
                     the entire resource being described MAY be removed in the future.
                 </t>
                 <t>
-                    When the "deprecated" keyword is applied to an item in an array by means of 
-                    "items", if "items" is a single schema, the deprecation relates to the whole 
-                    array, while if "items" is an array of schemas, the deprecation relates to 
-                    the corresponding item according to the subschemas position.
+                    The "deprecated" keyword applies to each instance location to which the
+                    schema object containing the keyword successfully applies.  This can
+                    result in scenarios where every array item or object property
+                    is deprecated even though the containing array or object is not.
                 </t>
                 <t>
                     Omitting this keyword has the same behavior as a value of false.