Clients SHOULD

docs/odata-protocol/odata-protocol.html

@@ -2272,6 +2272,7 @@ <h3 id="1142-create-an-entity"><a name="CreateanEntity" href="#CreateanEntity">1
 <p>If the entity being created is not an open entity, additional property values beyond those specified in the metadata SHOULD NOT be sent in the request body. The service MUST fail if unable to persist all property values specified in the request.</p>
 <p>If non-insertable properties are included in the request body, services MUST either ignore them or fail the request if the provided values do not match the service-determined values.</p>
 <p>A client who has out-of-band knowledge that a service has the latter behavior for certain non-insertable properties can provide them in an insert request and benefit from the certainty that, if the request succeeds, their service-determined values match the provided values. Providing such properties effectively imposes “post-conditions” that must be met for the request to succeed.</p>
+<p>Otherwise, clients SHOULD omit non-insertable properties from the request body.</p>
 <p>Non-insertable properties include (and are not limited to)</p>
 <ul>
 <li>dependent properties that are tied to non-key properties of the principal entity through a referential constraint <a href="#ODataCSDL">OData-CSDL, section 8.5</a> (informally: “denormalized” properties),</li>

docs/odata-protocol/odata-protocol.md

@@ -4190,6 +4190,8 @@ certainty that, if the request succeeds, their service-determined values match
 the provided values. Providing such properties effectively imposes "post-conditions"
 that must be met for the request to succeed.
 
+Otherwise, clients SHOULD omit non-insertable properties from the request body.
+
 Non-insertable properties include (and are not limited to)
 
 - dependent properties that are tied to non-key properties of the principal entity through a referential constraint [OData-CSDL, section 8.5](#ODataCSDL) (informally: "denormalized" properties),

odata-protocol/11.4 Data Modification.md

@@ -188,6 +188,8 @@ certainty that, if the request succeeds, their service-determined values match
 the provided values. Providing such properties effectively imposes "post-conditions"
 that must be met for the request to succeed.
 
+Otherwise, clients SHOULD omit non-insertable properties from the request body.
+
 Non-insertable properties include (and are not limited to)
 
 - dependent properties that are tied to non-key properties of the principal entity through a referential constraint [OData-CSDL, section 8.5](#ODataCSDL) (informally: "denormalized" properties),