[Json] Proposal: the minimal edit

R S <sayrer@gmail.com> Sat, 22 June 2013 16:58 UTC

Return-Path: <sayrer@gmail.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (localhost [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id CD90D11E810B for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 09:58:01 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.516
X-Spam-Level:
X-Spam-Status: No, score=-2.516 tagged_above=-999 required=5 tests=[AWL=0.083, BAYES_00=-2.599, HTML_MESSAGE=0.001, NO_RELAYS=-0.001]
Received: from mail.ietf.org ([12.22.58.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id A14GgQlk-YHm for <json@ietfa.amsl.com>; Sat, 22 Jun 2013 09:58:01 -0700 (PDT)
Received: from mail-we0-x22e.google.com (mail-we0-x22e.google.com [IPv6:2a00:1450:400c:c03::22e]) by ietfa.amsl.com (Postfix) with ESMTP id E63D321F9D31 for <json@ietf.org>; Sat, 22 Jun 2013 09:58:00 -0700 (PDT)
Received: by mail-we0-f174.google.com with SMTP id q58so7310241wes.33 for <json@ietf.org>; Sat, 22 Jun 2013 09:57:58 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type; bh=DXSXC3Yf1eVKtwRCY7i4pjxJDdgi/Y62KNIXVNJSOAg=; b=CLHSHsbWQx7nbFnu1ZVReZ1fvtvK7OYrTCUEYIH2luBzhuvszzOs1+2CIbMXsTdrx9 FyHXG4xMnzaM+KcDhr8laFgL+G5aQWdeBcRInI6iPR76Ei/WQd0H3DBZd2zURRcvyGBC RRrrE4GD+VVSOKhcH9qlxlzFnv36yUwFHeFjNNNvFjLXtij4pH+7rUV7T3uGXutn+eIQ d1f3yFYeJiXI9YRZFgXNw8l16i1i8VkmNoynxhrnZYRLoAlf4chq4Af/rY9dSjwwyM45 vFweOCuJnac3G+BOcKOS3jH+NjFs5tVA4tKtCc2jPFqQ0TOq9+wkhAjEDEcwHX209hbx bv9w==
MIME-Version: 1.0
X-Received: by 10.180.95.201 with SMTP id dm9mr1976601wib.21.1371920278871; Sat, 22 Jun 2013 09:57:58 -0700 (PDT)
Received: by 10.194.44.138 with HTTP; Sat, 22 Jun 2013 09:57:58 -0700 (PDT)
Date: Sat, 22 Jun 2013 09:57:58 -0700
Message-ID: <CAChr6SyN4Z3Hh8OFGHkK+AJN0+S09wMfjeobZ51GjKNL+GhPsw@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: "json@ietf.org" <json@ietf.org>
Content-Type: multipart/alternative; boundary="f46d044402b6e1e86c04dfc11470"
Subject: [Json] Proposal: the minimal edit
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
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: Sat, 22 Jun 2013 16:58:01 -0000

>From charter:

"The work is essentially a reclassification in place, with minimal changes.
The working group will review errata and update the document as needed
to incorporate
those, and will correct significant errors and inconsistencies, but will
keep changes to a minimum."

I propose a new section, to appear after "Generators" and before "IANA
Considerations"

+ N. Differences from ECMAScript
+
+ ECMAScript implementations produce and consume primitive JSON values at
the
+ root level of JSON documents.

It's my opinion that none of the errors or inconsistencies present in the
document are significant, since JSON works pretty well. I'll probably
oppose any edits that aren't to the introduction or the security
considerations, including updates to references such as ABNF and Unicode.
Note that the IETF does not update all standards track documents with
obsolete references, which demonstrates that leaving the current references
in place is tractable.

- Rob