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

R S <sayrer@gmail.com> Fri, 14 March 2014 00:32 UTC

Return-Path: <sayrer@gmail.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 405B51A0778 for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 17:32:00 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.999
X-Spam-Level:
X-Spam-Status: No, score=-1.999 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FREEMAIL_FROM=0.001, HTML_MESSAGE=0.001, SPF_PASS=-0.001] autolearn=ham
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 TMV6knHF8DXR for <json@ietfa.amsl.com>; Thu, 13 Mar 2014 17:31:57 -0700 (PDT)
Received: from mail-qc0-x233.google.com (mail-qc0-x233.google.com [IPv6:2607:f8b0:400d:c01::233]) by ietfa.amsl.com (Postfix) with ESMTP id BCB8E1A0752 for <json@ietf.org>; Thu, 13 Mar 2014 17:31:57 -0700 (PDT)
Received: by mail-qc0-f179.google.com with SMTP id m20so2097608qcx.24 for <json@ietf.org>; Thu, 13 Mar 2014 17:31:51 -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=7otj/AhA0iA/mKWo4eHZXhZDwCpCFZpdlrVjqrXpngw=; b=UJbic8pr0mIaq0YdOia0bZPAjsXs5MHbKFYX9seuMWR7deEAUKrHBFmX3eBFbwGJWp 2fuVe4gAi6/vrmQd7NjLcEf8osqiRBqLiGoyU1u9f4a8C5qJn8VWVf/oUhXXc4L2Ojjq Jn3RavddC7HdhnlogxqwI2F2oXG9UsWRj77rMAIzRDuvQpC6BcXDqjBaXFQpLzaWnuj5 AkcCMCvHrGItoLloMW+IoC1iQ/wjAgjiKppojxgP0qApTYyqZ40IY1o52Q7Okhsyxdlu mTMeUVuGmsLnHp46WfEOfbwxwXoXs/8OKW9P/umlvZzkN1F/nz9ZjIHibmIZpp0Z9nfH +ZGQ==
MIME-Version: 1.0
X-Received: by 10.224.66.8 with SMTP id l8mr6298786qai.16.1394757110991; Thu, 13 Mar 2014 17:31:50 -0700 (PDT)
Received: by 10.140.42.164 with HTTP; Thu, 13 Mar 2014 17:31:50 -0700 (PDT)
In-Reply-To: <CAHBU6ivygHCH1BR3akKKyQcQQTQXdRTUByE-Q4TuiRANDkH7nQ@mail.gmail.com>
References: <20140307171244.B1B8D7FC392@rfc-editor.org> <20E56125-5F9D-412D-B79A-D5B450798292@vpnc.org> <e5e5569a37874d6581e8e5039253c447@BL2PR02MB307.namprd02.prod.outlook.com> <CAHBU6ivygHCH1BR3akKKyQcQQTQXdRTUByE-Q4TuiRANDkH7nQ@mail.gmail.com>
Date: Thu, 13 Mar 2014 17:31:50 -0700
Message-ID: <CAChr6SzD0NYS_Uosb6ypX_tD_p6BOUv_X7KtG9M78EyQjf+3Cg@mail.gmail.com>
From: R S <sayrer@gmail.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: multipart/alternative; boundary=001a11c2c27a262cf104f4863277
Archived-At: http://mailarchive.ietf.org/arch/msg/json/0_LNrrqpNt6QxBmMHt9BTmWPjuE
Cc: Barry Leiba <barryleiba@computer.org>, 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>, Larry Masinter <masinter@adobe.com>
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: Fri, 14 Mar 2014 00:32:00 -0000

Oh bummer, I had raised this earlier:

<http://www.ietf.org/mail-archive/web/json/current/msg00100.html>

- Rob


On Thu, Mar 13, 2014 at 2:33 PM, Tim Bray <tbray@textuality.com> wrote:

> 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;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"?
>>
>>
>>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>