JSON Merge Patch (RFC 7396) lets a consumer send the data to modify in a PATCH request rather than send a complete resource as with PUT. A modification model can make its properties optional and omit fields that cannot be changed after creation. section 5.3.4 section 13.5.6
Changing an account owner's home city
With PATCH /owners/123, a merge patch changing the home address city must include the entire addresses array, with the other address and unchanged data retained. JSON Patch can instead identify the city by a JSON pointer and replace just that value. Its smaller request comes with a more complex format. section 13.5.6
Figure 13.11 Updating the home address city with JSON Merge Patch requires sending the entire address array. With JSON Patch, we only describe the modification of the city property of the first element without needing to send the address array.
Compare the data each format sends to change one city within an address array. section 13.5.6
Prefer the simpler, widely adopted merge patch for ordinary partial updates. If large arrays make replacement costly, consider dedicated operations; content negotiation can also support JSON Patch alongside merge patch. An implementation must distinguish a JSON key whose value is null from a missing key rather than treating that distinction as a reason to reject merge patch. section 13.5.6 section 14.2.5
