TC 2025-01-29

docs/odata-protocol/odata-protocol.html

@@ -2388,7 +2388,7 @@ <h4 id="11422-create-related-entities-when-creating-an-entity"><a id="CreateRela
 <details open><summary>
 <h3 id="1143-update-an-entity"><a id="UpdateanEntity" href="#UpdateanEntity">11.4.3 Update an Entity</a></h3>
 </summary>
-<p>To update an individual entity, the client makes a <code>PATCH</code> or <code>PUT</code> request to a URL that identifies the entity. Services MAY restrict updates only to requests addressing the <a href="#ReadURLsandEditURLs">edit URL</a> of the entity.</p>
+<p>To update an individual entity, the client makes a <code>PATCH</code> or <code>PUT</code> request to a URL that identifies the entity. The <a href="#ReadURLsandEditURLs">edit URL</a> MAY differ from the canonical URL defined in <a href="https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part2-url-conventions.html#CanonicalURL">OData-URL, section 4.3.1</a>, in which case clients SHOULD use the edit URL when making changes to the entity.</p>
 <p>The body of the request MUST be a valid representation of the declared target entity type, or one of its derived types.</p>
 <p>Services SHOULD support <code>PATCH</code> as the preferred means of updating an entity. <code>PATCH</code> provides more resiliency between clients and services by directly modifying only those values specified by the client.</p>
 <p>The semantics of <code>PATCH</code>, as defined in <a href="#rfc5789">RFC5789</a>, is to merge the content in the request payload with the entity’s current state, applying the update only to those components specified in the request body. Collection properties and primitive properties provided in the payload corresponding to updatable properties MUST replace the value of the corresponding property in the entity or complex type. Complex properties are updated by applying <code>PATCH</code> semantics recursively, see also <a href="#UpdateaComplexProperty">section 11.4.9.3</a>. Omitted properties of the containing entity or complex property, including dynamic properties, MUST NOT be directly altered unless as a side effect of changes resulting from the provided properties.</p>

docs/odata-protocol/odata-protocol.md

@@ -4333,9 +4333,9 @@ On failure, the service MUST NOT create any of the entities.
 ### <a id="UpdateanEntity" href="#UpdateanEntity">11.4.3 Update an Entity</a>
 
 To update an individual entity, the client makes a `PATCH` or `PUT`
-request to a URL that identifies the entity. Services MAY restrict
-updates only to requests addressing the [edit URL](#ReadURLsandEditURLs)
-of the entity.
+request to a URL that identifies the entity. The [edit URL](#ReadURLsandEditURLs)
+MAY differ from the canonical URL defined in [OData-URL, section 4.3.1](https://docs.oasis-open.org/odata/odata/v4.02/odata-v4.02-part2-url-conventions.html#CanonicalURL),
+in which case clients SHOULD use the edit URL when making changes to the entity.
 
 The body of the request MUST be a valid representation of the
 declared target entity type, or one of its derived types.

odata-protocol/11.4 Data Modification.md

@@ -315,9 +315,9 @@ On failure, the service MUST NOT create any of the entities.
 ### ##subsubsec Update an Entity
 
 To update an individual entity, the client makes a `PATCH` or `PUT`
-request to a URL that identifies the entity. Services MAY restrict
-updates only to requests addressing the [edit URL](#ReadURLsandEditURLs)
-of the entity.
+request to a URL that identifies the entity. The [edit URL](#ReadURLsandEditURLs)
+MAY differ from the canonical URL defined in [#OData-URL#CanonicalURL],
+in which case clients SHOULD use the edit URL when making changes to the entity.
 
 The body of the request MUST be a valid representation of the
 declared target entity type, or one of its derived types.