Don't override external specifications. See #20.

draft-ietf-httpapi-rest-api-mediatypes.md

@@ -331,26 +331,15 @@ leaving most of the semantics of the schema up to the dialect to define. Clients
 MUST use the following order of precedence for determining the dialect of a
 schema.
 
-* The `$schema` keyword ({{schema-keyword}})
-* The "schema" media type parameter ({{schema-parameter}})
+* The `$schema` keyword defined in Section 8.1.1 of {{jsonschema}}
+* The `schema` media type parameter (see {{schema-parameter}})
 * The context of the enclosing document. This applies only when a schema is
   embedded within a document. The enclosing document could be another schema in
   the case of a bundled schema or it could be another type of document that
   includes schemas such as an OpenAPI document.
 * If none of the above result in identifying the dialect, client behavior is
   undefined.
 
-### The "$schema" Keyword {#schema-keyword}
-
-The `$schema` keyword is used as a JSON Schema dialect identifier. The value of
-this keyword MUST be a URI {{!RFC3986}}. This URI SHOULD identify a meta-schema
-that can be used to validate that the schema is syntactically correct according
-to the dialect the URI identifies.
-
-The dialect SHOULD define where the `$schema` keyword is allowed and/or
-recognized in a schema, but it is RECOMMENDED that dialects do not allow the
-schema to change within the same Schema Resource.
-
 ### Identifying a Schema via a Media Type Parameter {#schema-parameter}
 
 Media types MAY allow for a `schema` media type parameter, to support content