[Json] RFC 7159 on The JavaScript Object Notation (JSON) Data Interchange Format

rfc-editor@rfc-editor.org Mon, 03 March 2014 10:55 UTC

Return-Path: <wwwrun@rfc-editor.org>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com []) by ietfa.amsl.com (Postfix) with ESMTP id 3C0491A0E74; Mon, 3 Mar 2014 02:55:17 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.449
X-Spam-Status: No, score=-2.449 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, RP_MATCHES_RCVD=-0.547, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=ham
Received: from mail.ietf.org ([]) by localhost (ietfa.amsl.com []) (amavisd-new, port 10024) with ESMTP id GsQMerTLnWw7; Mon, 3 Mar 2014 02:55:13 -0800 (PST)
Received: from rfc-editor.org (rfc-editor.org [IPv6:2607:f170:8000:1500::d3]) by ietfa.amsl.com (Postfix) with ESMTP id 69A7B1A0E3F; Mon, 3 Mar 2014 02:55:13 -0800 (PST)
Received: by rfc-editor.org (Postfix, from userid 30) id 4FCCC7FC399; Mon, 3 Mar 2014 02:55:08 -0800 (PST)
To: ietf-announce@ietf.org, rfc-dist@rfc-editor.org
From: rfc-editor@rfc-editor.org
Message-Id: <20140303105509.4FCCC7FC399@rfc-editor.org>
Date: Mon, 03 Mar 2014 02:55:08 -0800
Archived-At: http://mailarchive.ietf.org/arch/msg/json/AlhegQg2KYcPZejdleLkk-OtAzU
Cc: drafts-update-ref@iana.org, json@ietf.org, rfc-editor@rfc-editor.org
Subject: [Json] RFC 7159 on The JavaScript Object Notation (JSON) Data Interchange Format
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
Precedence: list
List-Id: "JavaScript Object Notation \(JSON\) WG mailing list" <json.ietf.org>
List-Unsubscribe: <https://www.ietf.org/mailman/options/json>, <mailto:json-request@ietf.org?subject=unsubscribe>
List-Archive: <http://www.ietf.org/mail-archive/web/json/>
List-Post: <mailto:json@ietf.org>
List-Help: <mailto:json-request@ietf.org?subject=help>
List-Subscribe: <https://www.ietf.org/mailman/listinfo/json>, <mailto:json-request@ietf.org?subject=subscribe>
X-List-Received-Date: Mon, 03 Mar 2014 10:55:17 -0000

A new Request for Comments is now available in online RFC libraries.  

Please note that this document is a republication of RFC 7158 in order to correct the publication year.

        RFC 7159

        Title:      The JavaScript Object Notation (JSON) 
                    Data Interchange Format 
        Author:     T. Bray, Ed.
        Status:     Standards Track
        Stream:     IETF
        Date:       March 2014 
        Mailbox:    tbray@textuality.com
        Pages:      16
        Characters: 27451
        Obsoletes:  RFC 4627, RFC 7158

        I-D Tag:    draft-ietf-json-rfc4627bis-rfc7159bis.txt

        URL:        http://www.rfc-editor.org/rfc/rfc7159.txt

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

This document removes inconsistencies with other specifications of
JSON, repairs specification errors, and offers experience-based
interoperability guidance.

This document is a product of the JavaScript Object Notation Working Group of the IETF.

This is now a Proposed Standard.

STANDARDS TRACK: This document specifies an Internet standards track
protocol for the Internet community,and requests discussion and suggestions
for improvements.  Please refer to the current edition of the Internet
Official Protocol Standards (STD 1) for the standardization state and
status of this protocol.  Distribution of this memo is unlimited.

This announcement is sent to the IETF-Announce and rfc-dist lists.
To subscribe or unsubscribe, see

For searching the RFC series, see http://www.rfc-editor.org/search
For downloading RFCs, see http://www.rfc-editor.org/rfc.html

Requests for special distribution should be addressed to either the
author of the RFC in question, or to rfc-editor@rfc-editor.org.  Unless
specifically noted otherwise on the RFC itself, all RFCs are for
unlimited distribution.

The RFC Editor Team
Association Management Solutions, LLC