Published revision: draft-jurkovikj-json-three-way-merge-00 · Expires: 5 February 2027
A deterministic, bounded, fail-closed three-way merge operation for a restricted JSON value domain.
Datatracker Read HTML Open demo
Inputs and results
Given a shared base value and independently derived source and target values, the operation produces one merged JSON value, an ordered set of structured conflicts, or a typed invalid-input, unsupported-domain, or resource failure.
Deterministic surface
- Strict JSON and finite binary64 numbers.
- Explicit scalar, object-member, and missing-member rules.
- RFC 6901 conflict paths and stable conflict ordering.
- Arrays fail closed unless a separately defined profile supplies array semantics.
- Disclosed limits for depth, tokens, bytes, and other resource ceilings.
Protocol boundary
The merge operation is independent of HTTP. An application can use it during reconciliation, but HTTP preconditions and atomic mutation remain separate concerns.
This is an individual Internet-Draft, not an RFC or an IETF standard.