What IETF RFC 7396 JSON Merge Patch - Recursive Merge Algorithm Application Merge Patch JSON Media Type and Object-Oriented Partial Update Semantics for HTTP PATCH requires
IETF RFC 7396 specifies the JSON Merge Patch format which describes modifications to a target JSON document using syntax that mirrors the target document with null values given special meaning to indicate the removal of existing values, processed via a recursive MergePatch algorithm where an object patch iterates through name-value pairs replacing or recursing into matching members and removing members where the patch value is null while non-object patches replace the entire target, registers the media type application-slash-merge-patch+json, references HTTP PATCH method security guidance from RFC 5789 and the JSON format from RFC 7159, with a notable limitation that JSON Merge Patch is best suited to JSON documents that primarily use objects and is not appropriate for documents that use explicit nulls or rely on arrays for modification.
Pillar: Workflow Automation · Authority: Internet Engineering Task Force (datatracker.ietf.org) · Version: 1.0.0 · Last updated:
Primary source: https://datatracker.ietf.org/doc/html/rfc7396
SHA-256 integrity: ef655591086aafff664cb737ff32576b17123a5d67a4dc1b15162217b83395b1
Primary Citations — 8 traced to source
- RFC 7396 JSON Merge Patch https://datatracker.ietf.org/doc/html/rfc7396
- Section 2 processing https://datatracker.ietf.org/doc/html/rfc7396#section-2
+ 6 more citations (full bibliography, deterministic workflow, actionable schema and crosswalks) included in the vault unlock — $0.01 via Skyfire / L402 / Direct Base USDC.
Access
- Discovery (free): /api/v1/nodes/ietf-rfc-7396-json-merge-patch.json — 6-field metadata
- Vault (full node): /api/v1/vault/nodes/ietf-rfc-7396-json-merge-patch.json — full 13-key payload, $0.01 USDC (L402/Skyfire/Direct Base)
- Canonical URL: https://bidda.com/intelligence/ietf-rfc-7396-json-merge-patch
- Back to registry: Browse all 10,085 compliance nodes