IETF Logo Mail Archive

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

"Markus Lanthaler" <markus.lanthaler@gmx.net> Thu, 03 October 2013 18:53 UTC

Return-Path: <markus.lanthaler@gmx.net>
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 1604321F9948 for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 11:53:52 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 0.758
X-Spam-Level:
X-Spam-Status: No, score=0.758 tagged_above=-999 required=5 tests=[BAYES_00=-2.599, MSGID_MULTIPLE_AT=1.449, RCVD_ILLEGAL_IP=1.908]
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 JpeFK90VYBjr for <json@ietfa.amsl.com>; Thu, 3 Oct 2013 11:53:36 -0700 (PDT)
Received: from mout.gmx.net (mout.gmx.net [212.227.17.22]) by ietfa.amsl.com (Postfix) with ESMTP id 6ACDA21F8445 for <json@ietf.org>; Thu, 3 Oct 2013 11:43:59 -0700 (PDT)
Received: from Vostro3500 ([2.34.217.54]) by mail.gmx.com (mrgmx102) with ESMTPSA (Nemesis) id 0MXmpv-1VMbBy1QL1-00WpLL for <json@ietf.org>; Thu, 03 Oct 2013 20:43:58 +0200
From: Markus Lanthaler <markus.lanthaler@gmx.net>
To: 'JSON WG' <json@ietf.org>
References: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
In-Reply-To: <BF7E36B9C495A6468E8EC573603ED9411EF2B583@xmb-aln-x11.cisco.com>
Date: Thu, 03 Oct 2013 20:43:55 +0200
Message-ID: <01fa01cec068$84932290$8db967b0$@lanthaler>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
X-Mailer: Microsoft Office Outlook 12.0
Thread-Index: AQHOwFZLzW8CgHOE6U+dHM+wYcr+wpnjTzFA
Content-Language: de
X-Provags-ID: V03:K0:cREsGfQNSkYywZ/ei16ClJ8DO0vXsDbjwLqhQMFYyZ6nQfZr1MY xIWbRIsfXGjqLn74sA71r6nWWgLOQckrD65iu3RDYxWky5BTvUrZYUEu0o8p1g/666KLci9 PJzcCCK8rxaUpnRQyYf14JCosP9X/s0z6l2xqtPQ0q9H8akK4rH6/4P2SFsq6g46ZBrhvyY d1pZntKB6h7yUmVyJ9v4Q==
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 18:53:57 -0000

On Thursday, October 03, 2013 6:34 PM, Matt Miller (mamille2) wrote:
> There appears to be rough consensus to reference ECMA-262 edition 5.1.
> As James pointed out[1], something will need to be said about what is a
> JSON-text; either 4627bis states a difference from ECMA-262 edition
> 5.1, or 4627bis states a difference from RFC 4627.
> 
> 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?

I'm strongly against this. I think it is a bad idea in general - for a
serialization format, not JavaScript - and it would break a lot of existing
systems.


--
Markus Lanthaler
@markuslanthaler

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