T. Bray is credited as editor of RFC 8259, the 2017 specification of JSON as a format for serialization of structured data. The document makes both the grammar and data format interoperability requirements explicit: a shared notation is most useful when independent implementations agree on what it means.[ref]
The JavaScript Object Notation (JSON) Data Interchange Format. Editor byline; Sections1–2: purpose, data values and grammar
One concrete example is duplicate object names. The invented text
{"x":1,"x":2} fits the object grammar, but the specification recommends unique names because receiving implementations can handle duplicates differently. Some keep the last pair, some reject the input and some expose all pairs. A parser accepting text and two applications agreeing on its interpretation are different conditions.[ref]The JavaScript Object Notation (JSON) Data Interchange Format. Section4: object grammar, unique-name recommendation and differing receiver behavior
The specification also requires UTF-8 for exchanged JSON outside a closed ecosystem. Character encoding, syntax and agreement on values thus contribute separately to reliable interchange.[ref]
The JavaScript Object Notation (JSON) Data Interchange Format. Section8.1: network interchange encoding
This work illustrates a contribution through precise specification: identifying where superficially similar implementations can disagree and stating requirements that make exchange predictable. The initial-only header retains the document's editor byline.
Portrait page: www.tbray.org/ongoing/misc/Tim
New to topics? Read the docs here!