Content Negotiation: Remove detailed error requirement; use 415

ethanresnick · ethanresnick · commit 0ab8a2d86517 · 2015-05-26T17:28:47.000-07:00
diff --git a/format/index.md b/format/index.md
@@ -31,24 +31,15 @@ interpreted as described in RFC 2119
 Clients **MUST** send all JSON API data in request documents with the header
 `Content-Type: application/vnd.api+json`, without any media type parameters.
 
+If clients violate this requirement, servers **MUST** return a
+`415 Unsupported Media Type` status code.
+
 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.
 
-Servers **MUST** return a `400 Bad Request` status code if clients violate
-either of the requirements above. The server's response to such violations
-**MUST** contain a JSON API document with an [error object](#error-objects).
-The `"href"` member of that object **MUST** be
-`"http://jsonapi.org/errors/invalid-media-type-parameter"`.
-
 Servers **MUST** send all JSON API data in response documents with the header
 `Content-Type: application/vnd.api+json`, without any media type parameters.
 
-Clients **MUST** ignore any parameters for the `application/vnd.api+json`
-media type received in the `Content-Type` header of response documents.
-
-> Note: These requirements exist to allow future versions of this specification
-to use media type parameters for extension negotiation and versioning.
-
 Servers **MUST NOT** send responses with the `application/vnd.api+json` media
 type if the client has not indicated, using its `Accept` header, that it can
 understand this format.
@@ -60,6 +51,12 @@ considered to be sending "JSON API data" for the purposes of the requirement
 above, but rather simple JSON data, and the client cannot rely on any of the
 rules laid out in this specification.
 
+Clients **MUST** ignore any parameters for the `application/vnd.api+json`
+media type received in the `Content-Type` header of response documents.
+
+> Note: These requirements exist to allow future versions of this specification
+to use media type parameters for extension negotiation and versioning.
+
 ## Document Structure <a href="#document-structure" id="document-structure" class="headerlink"></a>
 
 This section describes the structure of a JSON API document, which is identified
