IETF Logo Mail Archive

[Json] Description of parsers

Paul Hoffman <paul.hoffman@vpnc.org> Sun, 09 June 2013 20:38 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 39D4D21F85C9 for <json@ietfa.amsl.com>; Sun, 9 Jun 2013 13:38:05 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.402
X-Spam-Level:
X-Spam-Status: No, score=-102.402 tagged_above=-999 required=5 tests=[AWL=0.197, BAYES_00=-2.599, USER_IN_WHITELIST=-100]
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 VmVTcVaYq7hE for <json@ietfa.amsl.com>; Sun, 9 Jun 2013 13:38:04 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CF0ED21F8450 for <json@ietf.org>; Sun, 9 Jun 2013 13:38:04 -0700 (PDT)
Received: from [10.20.30.90] (50-0-66-165.dsl.dynamic.sonic.net [50.0.66.165]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r59Kc26i089257 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Sun, 9 Jun 2013 13:38:03 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="us-ascii"
Mime-Version: 1.0 (Mac OS X Mail 6.5 \(1508\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <51B44197.2000006@drees.name>
Date: Sun, 09 Jun 2013 13:38:02 -0700
Content-Transfer-Encoding: 7bit
Message-Id: <014BC561-ECB9-4C82-B759-580025770E58@vpnc.org>
References: <20130609042518.11918.qmail@joyce.lan> <51B44197.2000006@drees.name>
To: "json@ietf.org" <json@ietf.org>
X-Mailer: Apple Mail (2.1508)
Subject: [Json] Description of parsers
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: Sun, 09 Jun 2013 20:38:05 -0000

Starting this as a new thread.

On Jun 9, 2013, at 1:49 AM, Stefan Drees <stefan@drees.name> wrote:

> yes, thus I propose as NEW:
> 
> 4.  Parsers
> 
>   A JSON parser transforms JSON text into another representation,
>   MUST accept all texts that conform to the JSON grammar and MUST be
>   prepared to either accept duplicate names in objects or reject the
>   complete JSON text containing these.
>   A JSON parser MAY accept non-JSON forms or extensions.
> 
>   An implementation may set limits on any of the following: the size
>   of texts that it accepts, the maximum depth of nesting, the range
>   and precision of numbers, and the length and character contents of
>   strings.

v2.23.0 | Report a Bug | By Email