Re: [Json] Proposal: the minimal edit

R S <sayrer@gmail.com> Tue, 25 June 2013 03:53 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 56C0B21E8084 for <json@ietfa.amsl.com>; Mon, 24 Jun 2013 20:53:30 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.536
X-Spam-Level:
X-Spam-Status: No, score=-2.536 tagged_above=-999 required=5 tests=[AWL=0.063, 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 QhfIJp4Cuu-l for <json@ietfa.amsl.com>; Mon, 24 Jun 2013 20:53:29 -0700 (PDT)
Received: from mail-wi0-x235.google.com (mail-wi0-x235.google.com [IPv6:2a00:1450:400c:c05::235]) by ietfa.amsl.com (Postfix) with ESMTP id 620E721E805E for <json@ietf.org>; Mon, 24 Jun 2013 20:53:29 -0700 (PDT)
Received: by mail-wi0-f181.google.com with SMTP id hq4so296842wib.8 for <json@ietf.org>; Mon, 24 Jun 2013 20:53:28 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=i6Vv7H0KclcZl02ABFjPM8y6yVqNe6t418pMlY8FaEI=; b=YcCZ6GqRj93rwTifMlYhTO0BpACkxzcHGKDXq7vh46QN20tkkA1tUKZDyGabz510Kh g2cv/wbp2pH7E9LQZQWcAX3NOWJioH7nwXvn7eIEq4le0wxrxWOdJVXWDPu+6BkZeqsV 8N10q3OoOdmm4v7s7TyzeUE+pt/L2FansYMYUB3bcerFIR/VO4en5ZglSsP5FKyP3d72 VLu0ON/J2ccoU/OzIYulR1Jan553gdUx+7z2XpI4gtDqtj5RwCdgV2mwBWU5qZJT7SO3 5Lpgo33y4KyxolhcgMoa5XQ+OhuCfpBxKq1ZvGjgRKd72Gy27vTJghjCi87TIIG+RrBo LVpQ==
MIME-Version: 1.0
X-Received: by 10.180.206.77 with SMTP id lm13mr7763454wic.18.1372132408514; Mon, 24 Jun 2013 20:53:28 -0700 (PDT)
Received: by 10.194.44.138 with HTTP; Mon, 24 Jun 2013 20:53:28 -0700 (PDT)
In-Reply-To: <20130625034827.GG14060@mercury.ccil.org>
References: <20130625032014.GF14060@mercury.ccil.org> <ECAD5568-05F1-44C0-A8E1-6A38DAFAF6D4@vpnc.org> <20130625034827.GG14060@mercury.ccil.org>
Date: Mon, 24 Jun 2013 20:53:28 -0700
Message-ID: <CAChr6Sy50Ya7ZsJwZ2axWB5S1OpQ4TynhssBKmC9qfZo5wWXgQ@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: John Cowan <cowan@mercury.ccil.org>
Content-Type: multipart/alternative; boundary="001a11c380aecb8ff604dff278df"
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [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: Tue, 25 Jun 2013 03:53:30 -0000

On Mon, Jun 24, 2013 at 8:48 PM, John Cowan <cowan@mercury.ccil.org> wrote:

> Paul Hoffman scripsit:
>
> > Hrm. Either you are focused only on the grammar section and not the
> > whole document, or you missed the Introduction to RFC 4627, which
> > say unequivocally:
> >
> >    A string is a sequence of zero or more Unicode characters [UNICODE].
>
> It's actually quite equivocal: it neither states that any Unicode character
> may appear in a string, nor that everything that appears in a string is
> a Unicode character.
>

I think that is a pretty strained interpretation.



>
> > That statement disagrees with ABNF in the grammar, so the RFC is
> > ambiguous. Some people in the WG believe that this sentence is right
> > and the ABNF is wrong; others believe the other.
>
> Since your proposal leaves the ambiguity intact, we don't know whether
> the meaning of the RFC as revised by your proposal is or is not the same
> as what ECMA-JSON prescribes.



The RFC is ambiguous and ECMA-JSON is not. That's the difference, and we
don't have to fix the RFC.

- Rob