diff --git a/jsonschema-core.xml b/jsonschema-core.xml
index d25b23ee..4b33df67 100644
--- a/jsonschema-core.xml
+++ b/jsonschema-core.xml
@@ -198,13 +198,17 @@
 
             <section title="Instance">
                 <t>
-                    A JSON document to which a schema is applied is known as an "instance".
+                    A document to which a schema is applied is known as an "instance".
                 </t>
 
                 <section title="Instance Data Model">
                     <t>
-                        JSON Schema interprets documents according to a data model. A JSON value
-                        interpreted according to this data model is called an "instance".
+                        JSON Schema interprets documents according to a data model. A value
+                        interpreted according to this data model is called an "instance".  JSON
+                        documents map trivially into the data model, with a few exceptions as
+                        noted below.  Documents of other media types MAY be treated as instances
+                        if a suitable application-defined mapping of the media type into the
+                        data model can be determined.
                     </t>
                     <t>
                         An instance has one of six primitive types, and a range of possible values
@@ -219,6 +223,12 @@
                             <t hangText="string:">A string of Unicode code points, from the JSON "string" value</t>
                         </list>
                     </t>
+                    <t>
+                        Binary data MAY be treated as an instance, however no data type in the data model
+                        is suitable.  Therefore, only schemas such as the empty schema that do not
+                        constrain the type can be considered to pass.  Rationales for and behavior of
+                        binary data as an instance SHOULD be defined by the consuming application.
+                    </t>
                     <t>
                         Whitespace and formatting concerns, including different lexical
                         representations of numbers that are equal within the data model, are thus
@@ -3796,7 +3806,7 @@ https://example.com/schemas/common#/$defs/count/minimum
                             <t></t>
                             <t></t>
                             <t></t>
-                            <t></t>
+                            <t>Clarify applicability to non-JSON media types</t>
                             <t></t>
                             <t></t>
                             <t></t>
diff --git a/jsonschema-validation.xml b/jsonschema-validation.xml
index 06966a8d..001bd67b 100644
--- a/jsonschema-validation.xml
+++ b/jsonschema-validation.xml
@@ -913,7 +913,9 @@
             <section title="Foreword">
                 <t>
                     Annotations defined in this section indicate that an instance contains
-                    non-JSON data encoded in a JSON string.
+                    non-JSON data encoded in a JSON string.  Additionally, they can be used in
+                    the context of resources of various media types to indicate binary resources
+                    not otherwise describable by JSON Schema.
                 </t>
                 <t>
                     These properties provide additional information required to interpret JSON data
@@ -945,14 +947,21 @@
                     consumer than that which processed the containing document.
                 </t>
                 <t>
-                    All keywords in this section apply only to strings, and have no
-                    effect on other data types.
+                    All keywords in this section generally apply to strings, and have no
+                    effect on other JSON data types.  Additionally, they MAY be used without
+                    type information when describing resources of other media types, subject
+                    to certain restrictions.
                 </t>
                 <t>
                     Implementations MAY offer the ability to decode, parse, and/or validate
-                    the string contents automatically.  However, it MUST NOT perform these
+                    the string contents automatically.  However, they MUST NOT perform these
                     operations by default, and MUST provide the validation result of each
-                    string-encoded document separately from the enclosing document.  This
+                    string-encoded document separately from the enclosing document.  In particular,
+                    these keywords, including "contentSchema", MUST NOT cause the containing schema
+                    to fail validation.
+                </t>
+                <t>
+                    The optional automatic decoding, parsing, and validating
                     process SHOULD be equivalent to fully evaluating the instance against
                     the original schema, followed by using the annotations to decode, parse,
                     and/or validate each string-encoded document.
@@ -1005,7 +1014,14 @@
                 <t>
                     If the instance is a string, this property indicates the media type
                     of the contents of the string.  If "contentEncoding" is present,
-                    this property describes the decoded string.
+                    this property describes the decoded string.  If the "type" keyword is
+                    absent, this keyword MAY be interpreted as describing an unencoded binary
+                    resource.  The exact meaning and behavior of this untyped usage is
+                    application-defined.
+                    <cref>
+                        For an example of application-defined untyped usage,
+                        see the forthcoming OpenAPI Specification v3.1
+                    </cref>
                 </t>
                 <t>
                     The value of this property MUST be a string, which MUST be a media type,
@@ -1015,8 +1031,9 @@
 
             <section title="contentSchema">
                 <t>
-                    If the instance is a string, and if "contentMediaType" is present, this
-                    property contains a schema which describes the structure of the string.
+                    If the instance is a string or an untyped binary resource,
+                    and if "contentMediaType" is present, this property contains a schema
+                    which describes the structure of the string.
                 </t>
                 <t>
                     This keyword MAY be used with any media type that can be mapped into
@@ -1433,8 +1450,8 @@
                         <list style="symbols">
                             <t>Correct email format RFC reference to 5321 instead of 5322</t>
                             <t>Clarified the set and meaning of "contentEncoding" values</t>
-                            <t></t>
-                            <t></t>
+                            <t>Clarified value requirements for "contentSchema"</t>
+                            <t>Expanded "contentMediaType" to unencoded binary media</t>
                             <t></t>
                             <t></t>
                             <t></t>