Re: [Json] [Technical Errata Reported] RFC7159 (3915)

Tim Bray <tbray@textuality.com> Thu, 13 March 2014 21:33 UTC

Return-Path: <tbray@textuality.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 1402A1A076C for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:33:51 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.478
X-Spam-Level:
X-Spam-Status: No, score=0.478 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, FM_FORGED_GMAIL=0.622, FRT_ADOBE2=2.455, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=no
Received: from mail.ietf.org ([4.31.198.44]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id n_kr2J_yFCZw for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 14:33:49 -0700 (PDT)
Received: from mail-vc0-f176.google.com (mail-vc0-f176.google.com [209.85.220.176]) by ietfa.amsl.com (Postfix) with ESMTP id 802721A075E for <json@ietf.org>; Thu, 13 Mar 2014 14:33:49 -0700 (PDT)
Received: by mail-vc0-f176.google.com with SMTP id lc6so1794541vcb.21 for <json@ietf.org>; Thu, 13 Mar 2014 14:33:42 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:cc:content-type; bh=WTAKyP+sKQ2I7Jb5Lts2qwYnQu9KWWoQ18p3Ix8MGxc=; b=CtH/yLNRk5pLY2pN4IwRsWadG/HofZqyVZLbJiwkx02B3Yq6wQZ7F7+1EpOwdnUH2Z lNuXdnsflAZfum8fqo33IOkewW604FP3t9Aq87gSniKj3DHJvfik1JhQ7IbzBUYHir45 pN2CNpLRR3l4ONoFwiFS4xh/WGeAvRCNbFlPPZu3zDSSlLAGmlNejOWAQIKaCznlEj5F IazYkL4m3l1RGRAghio70jGWTWORmJAkpVV1RclXH/2M3MLFBbDaH0q53JztpPvPT2xG YR4hyh8gCNk9mfDRqc2UK9wlGBrsXU7K+c2avnZs3reeD19PHc6PXpbAEBTtI8p/ycdS p4tg==
X-Gm-Message-State: ALoCoQk/3GLPDSKnazUnJMWbbgWHp6v0qmxjoB7K1kVESu5cxUmguVWDPzq3gMKZk+YSfNi1Gjgp
MIME-Version: 1.0
X-Received: by 10.52.34.137 with SMTP id z9mr2708810vdi.12.1394746422699; Thu, 13 Mar 2014 14:33:42 -0700 (PDT)
Received: by 10.220.98.73 with HTTP; Thu, 13 Mar 2014 14:33:42 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <e5e5569a37874d6581e8e5039253c447@BL2PR02MB307.namprd02.prod.outlook.com>
References: <20140307171244.B1B8D7FC392@rfc-editor.org> <20E56125-5F9D-412D-B79A-D5B450798292@vpnc.org> <e5e5569a37874d6581e8e5039253c447@BL2PR02MB307.namprd02.prod.outlook.com>
Date: Thu, 13 Mar 2014 14:33:42 -0700
Message-ID: <CAHBU6ivygHCH1BR3akKKyQcQQTQXdRTUByE-Q4TuiRANDkH7nQ@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Larry Masinter <masinter@adobe.com>
Content-Type: multipart/alternative; boundary=20cf30780f6213c35504f483b528
Archived-At: http://mailarchive.ietf.org/arch/msg/json/cPc0qSErU11gbnamvFSUSEcVnYQ
Cc: Pete Resnick <presnick@qti.qualcomm.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>, "vfaronov@gmail.com" <vfaronov@gmail.com>, "mamille2@cisco.com" <mamille2@cisco.com>, Barry Leiba <barryleiba@computer.org>
Subject: Re: [Json] [Technical Errata Reported] RFC7159 (3915)
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: Thu, 13 Mar 2014 21:33:51 -0000

That idea is at least plausible. And I bet a walk through the unicode
separator and white-space definitions might turn up a few more candidates.


On Thu, Mar 13, 2014 at 2:31 PM, Larry Masinter <masinter@adobe.com> wrote:

> > The WG chairs request that you approve this errata.
>
>
> I think the errata would be more useful if it actually explained the
> \u2028, \u2029 exception, rather than leaving it in a potentially unstable
> reference
> http://timelessrepo.com/json-isnt-a-javascript-subset
>
> Should \u2028 \u2029 characters be disallowed from an "i-json" profile?
> Since the purpose is a "safe subset"?
>
>
>