IETF Logo Mail Archive

Re: [Json] What is a JSON-text? [REVISITED]

Peter Patel-Schneider <pfpschneider@gmail.com> Thu, 03 October 2013 17:49 UTC

Return-Path: <pfpschneider@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 3AE9611E817D for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 10:49:59 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[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 Vx2iAg0KmwFw for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 10:49:47 -0700 (PDT)
Received: from mail-qe0-x233.google.com (mail-qe0-x233.google.com [IPv6:2607:f8b0:400d:c02::233]) by ietfa.amsl.com (Postfix) with ESMTP id 32BF821F90AF for <json@ietf.org>; Thu, 3 Oct 2013 10:34:09 -0700 (PDT)
Received: by mail-qe0-f51.google.com with SMTP id ne12so1976811qeb.24 for <json@ietf.org>; Thu, 03 Oct 2013 10:34:08 -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=dD9RnL5vZhFKodtIhxj9vS+hcwKA02rxyZXJauxezuo=; b=eAZhSOSDfhkA46QEPCTfJ44lG0DhYMWRbbR40KiXuvabQ6c8d49277EyhkYsdv37lQ IHSyTdxLCxZql32dyHtQigrrE8iK6xUyB2WySAZAp/aVEfzMpl4QEBunVdTOgs1Tfuon mqqNFAGw8LVPlYI/pfkUTu4Uev7vqKwBOzWj2kElNFPtw29gUeR/iRIEWYoqsJZCjIpb okyQ8EJGCJv/7k6R9icg+a6H5OrpqAy//pJ9ZTZBGf3w2ApcE6b1ogaYS4LiUgm4wFwX bvamgPQolZXZS3cxkoISC0/nxKE9PJeajDg68c83XwYdugaNfVzxatdNY3nZ3unrZCmf HhiQ==
MIME-Version: 1.0
X-Received: by 10.49.70.129 with SMTP id m1mr11149490qeu.69.1380821648524; Thu, 03 Oct 2013 10:34:08 -0700 (PDT)
Received: by 10.49.64.202 with HTTP; Thu, 3 Oct 2013 10:34:08 -0700 (PDT)
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
References: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
Date: Thu, 03 Oct 2013 10:34:08 -0700
Message-ID: <CAMpDgVw2MkRZTtDqoOpLfAH2bD8i8Q+ojk2mXnbAoA4s5R8dfg@mail.gmail.com>
From: Peter Patel-Schneider <pfpschneider@gmail.com>
To: "Matt Miller (mamille2)" <mamille2@cisco.com>
Content-Type: multipart/alternative; boundary="047d7b4721fedbcd1f04e7d99722"
Cc: JSON WG <json@ietf.org>
Subject: Re: [Json] What is a JSON-text? [REVISITED]
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: Thu, 03 Oct 2013 17:49:59 -0000

The proposal is to *change* JSON in a way that would break some current
JSON parsers and, worse, break some current consumers of JSON, to get
closer syntactic conformance with the ECMAScript JSON implementation.

If there is a goal to align JSON with the ECMAScript JSON implementation,
then I suggest that requiring EMCAScript numbers is much more important and
that even officially requiring support for unpaired UTF-16 surrogate code
units is more important.

I think that this proposal should not be adopted.

Peter F. Patel-Schneider
Nuance Communications


On Thu, Oct 3, 2013 at 9:33 AM, Matt Miller (mamille2)
<mamille2@cisco.com>wrote:

> Hello all,
>
> [....]
>
> There was previously much discussion on this topic[2].  Some have restated
> their support.  What do others think about changing JSON-text to allow any
> JSON value versus just objects or arrays?
>
>
> -  Paul Hoffman and Matt Miller
>
>
> [2] < http://www.ietf.org/mail-archive/web/json/current/msg00553.html >
> _______________________________________________
>
>
>

v2.27.6 | Report a Bug | By Email | System Status