metasystema.org
ObsoletedINFORMATIONALIETF stream

RFC 4627: The application/json Media Type for JavaScript Object Notation (JSON)

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 memo provides information for the Internet community.

Document record

Document ID
RFC4627
Published
July 2006
Authors
D. Crockford
Status
INFORMATIONAL
Stream
IETF
Area
—
Pages
10
Also known as
—
Obsoleted by:
RFC 7159

Topics

Standards lineage

This document is one revision in a chain of 4 RFCs, each formally replacing the one before it.

  1. RFC 4627 (2006)
  2. RFC 7158 (2014)
  3. RFC 7159 (2014)
  4. 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.

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?

canonical URL: /rfc/4627-the-application-json-media-type-for-javascript-object-notation-json