Permit clients to require a profile via the accept header.

gabesullice · gabesullice · commit 969d75aef4a8 · 2019-07-25T12:21:49.000-06:00
diff --git a/_format/1.1/index.md b/_format/1.1/index.md
@@ -49,9 +49,6 @@ The `profile` parameter is used to support [profiles].
 
 ### <a href="#content-negotiation-clients" id="content-negotiation-clients" class="headerlink"></a> Client Responsibilities
 
-Clients that include the JSON:API media type in their `Accept` header **MUST**
-specify the media type there at least once without any media type parameters.
-
 When processing a JSON:API response document, clients **MUST** ignore any
 parameters other than `profile` in the server's `Content-Type` header.
 
@@ -62,8 +59,8 @@ a request specifies the header `Content-Type: application/vnd.api+json`
 with any media type parameters other than `profile`.
 
 Servers **MUST** respond with a `406 Not Acceptable` status code if a
-request's `Accept` header contains the JSON:API media type and all instances
-of that media type are modified with media type parameters.
+request's `Accept` header contains the JSON:API media type and the server is
+unable to respond with an acceptable representation.
 
 > Note: These content negotiation requirements exist to allow future versions
 of this specification to add other media type parameters for extension
