From 1023ee6bfe0a616c190c5c87f9b52b7755219d31 Mon Sep 17 00:00:00 2001
From: wes-smith <wes.apps.2014@gmail.com>
Date: Tue, 25 Jun 2024 14:33:41 -0400
Subject: [PATCH] Add section for handling unknown options/data.

- adds text requiring implementations throw an error on receiving data, options, or option values not understood by the endpoint.
---
 index.html | 11 ++++++++++-
 1 file changed, 10 insertions(+), 1 deletion(-)

diff --git a/index.html b/index.html
index 32f7dbc..17c7753 100644
--- a/index.html
+++ b/index.html
@@ -686,7 +686,16 @@ <h3>Content Serialization</h3>
 All entity bodies in requests and responses sent to or received from the API endpoints defined by this specification MUST be serialized as JSON and include the `Content-Type` header with a media type value of `application/json`. 
       </p>
     </section>
-
+    <section>
+      <h3>Handling Unknown Options and Data</h3>
+      <p>
+Many of the endpoints defined in the following sections receive data and options in request bodies.
+      </p>
+      <p>
+Implementations MUST throw an error if an endpoint receives data, options, or option values that it
+does not understand or know how to process.
+      </p>
+    </section>
     <section>
       <h3>API Component Overview</h3>
         <p>