RFC 7158: The JavaScript Object Notation (JSON) Data Interchange Format
This RFC has been replaced. Do not implement against it for new work — it was formally obsoleted by RFC 7159.
Current document in this lineage: RFC 8259 — The JavaScript Object Notation (JSON) Data Interchange Format
In plain English — editorial summary, not part of the RFC
JavaScript Object Notation (JSON) is a lightweight, text-based, language-independent data interchange format. It was derived from the ECMAScript Programming Language Standard. JSON defines a small set of formatting rules for the portable representation of structured data. This document removes inconsistencies with other specifications of JSON, repairs specification errors, and offers experience-based interoperability guidance.
Document record
- Document ID
- RFC7158
- Published
- March 2014
- Authors
- T. Bray
- Status
- PROPOSED STANDARD
- Stream
- IETF
- Area
- app
- Pages
- 16
- Also known as
- —
- Obsoleted by:
- RFC 7159
Standards lineage
This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.
- RFC 4627 (2006)
- RFC 7158 (2014)
- RFC 7159 (2014)
- RFC 8259 (2017) ✓
Read the full history of The JavaScript Object Notation (JSON) Data Interchange Format →
Referenced by
One later RFC formally updates or obsoletes part of this document.
Related documents
Ranked automatically by shared keywords, IETF area and stream — not by editorial selection.
- RFC 7162IMAP Extensions: Quick Flag Changes Resynchronization (CONDSTORE) and Quick Mailbox Resynchronization (QRESYNC)Current
May 2014
- RFC 7208Sender Policy Framework (SPF) for Authorizing Use of Domains in Email, Version 1Updated
April 2014
- RFC 7095jCard: The JSON Format for vCardCurrent
January 2014
- RFC 7073A Reputation Response Set for Email IdentifiersCurrent
November 2013
- RFC 7072A Reputation Query ProtocolCurrent
November 2013
- RFC 7071A Media Type for Reputation InterchangeCurrent
November 2013
- RFC 7070An Architecture for Reputation ReportingCurrent
November 2013
- RFC 7265jCal: The JSON Format for iCalendarUpdated
May 2014
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?