The encyclopedia · Software & IT · Technical decision · 2010–2014
JSON-LD brought linked data to the web by keeping JSON's syntax
W3C's JSON-LD keeps JSON's syntax and adds an optional @context for linking; schema.org supports it, and it became the way sites mark up data.
W3C · schema.org (Google, Microsoft, Yahoo)
The solution
Linked Data had been the web's promise for years, but its early tooling demanded XML and heavyweight machinery that most developers avoided. JSON-LD's bet was that the syntax was the barrier: keep JSON, which every programmer and every browser already knew, and add linked-data capability on top.
The mechanism is a @context. In JSON-LD a normal JSON object stays a normal JSON object, and a @context maps its terms to shared vocabularies so other applications can follow links and understand meaning. json-ld.org describes it as a lightweight Linked Data format based on the already successful JSON format, easy for humans to read and write, and ideal for REST services and unstructured databases.
Adoption came from the search ecosystem. schema.org — the shared vocabulary from Google, Microsoft and Yahoo — documents JSON-LD alongside Microdata and RDFa as a way to add structured data to web content, giving publishers one dictionary and one format that the platforms already read.
Why it worked
- The syntax is identical to JSON, so no new parsing or tools are needed.
- The @context is optional — plain JSON still works.
- schema.org's vocabulary gave publishers a shared dictionary to link to.
- W3C standardization gave enterprises a neutral, stable target.
What can be applied
Adoption follows familiarity: make the new capability optional and keep the syntax everyone already uses, and the standard rides in on existing habits.
Aftermath
JSON-LD became one of the three formats schema.org documents for web markup, and its JSON-first design made it the natural choice for API-heavy sites — a standard that won by changing as little as possible about how developers already wrote data.
Sources
- JSON-LD 1.1: A JSON-based Serialization for Linked Data
- Getting started with schema.org using Microdata
spotted an error? The archive wants to know.