RFC 7396: JSON Merge Patch
In plain English — editorial summary, not part of the RFC
This specification defines the JSON merge patch format and processing rules. The merge patch format is primarily intended for use with the HTTP PATCH method as a means of describing a set of modifications to a target resource's content.
Document record
- Document ID
- RFC7396
- Published
- October 2014
- Authors
- P. Hoffman; J. Snell
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- art
- Pages
- 9
- Also known as
- —
- Obsoletes:
- RFC 7386
Topics
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7807Problem Details for HTTP APIsObsoleted
March 2016
- RFC 5789PATCH Method for HTTPCurrent
March 2010
- RFC 9264Linkset: Media Types and a Link Relation Type for Link SetsCurrent
July 2022
- RFC 9457Problem Details for HTTP APIsCurrent
July 2023
- RFC 7946The GeoJSON FormatCurrent
August 2016
- RFC 8030Generic Event Delivery Using HTTP PushCurrent
December 2016
- RFC 8142GeoJSON Text SequencesCurrent
April 2017
- RFC 8291Message Encryption for Web PushCurrent
November 2017
Also filed under
About this page
The document record above — title, authors, date, status, stream, area, relationships, DOI and errata — is imported verbatim from the public RFC Editor index. The “in plain English” section is editorial: written by The metasystema editorial team, not part of the RFC. Where the two differ, the RFC text governs.
Last checked against the RFC Editor index on . RFCs are never revised after publication; changes are issued as new documents.
Data sources · Editorial policy · Report a correction · What is an RFC?