[Json] Question regarding RFC 7159
Patrice Guérin <guerinp@magic.fr> Fri, 18 November 2016 15:29 UTC
Return-Path: <guerinp@magic.fr>
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 8D6F912958D for <json@ietfa.amsl.com>; Fri, 18 Nov 2016 07:29:21 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.721
X-Spam-Level:
X-Spam-Status: No, score=-0.721 tagged_above=-999 required=5 tests=[BAYES_20=-0.001, RCVD_IN_DNSWL_LOW=-0.7, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=ham autolearn_force=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 zwnOArF1UwNg for <json@ietfa.amsl.com>; Fri, 18 Nov 2016 07:29:20 -0800 (PST)
Received: from smtp26.services.sfr.fr (smtp26.services.sfr.fr [93.17.128.10]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E60C7128B37 for <json@ietf.org>; Fri, 18 Nov 2016 07:29:19 -0800 (PST)
Received: from [192.168.10.1] (104.161.147.77.rev.sfr.net [77.147.161.104]) by msfrf2626.sfr.fr (SMTP Server) with ESMTP id AA80C1C001018 for <json@ietf.org>; Fri, 18 Nov 2016 16:29:17 +0100 (CET)
Received: from [192.168.10.1] (104.161.147.77.rev.sfr.net [77.147.161.104]) (using TLSv1 with cipher ECDHE-RSA-AES256-SHA (256/256 bits)) (No client certificate requested) (Authenticated sender: patrice.guerin20@sfr.fr) by msfrf2626.sfr.fr (SMTP Server) with ESMTPSA for <json@ietf.org>; Fri, 18 Nov 2016 16:29:17 +0100 (CET)
Authentication-Results: sfr.fr; auth=pass (PLAIN) smtp.auth=patrice.guerin20@sfr.fr
Message-ID: <582F1E4C.20406@magic.fr>
Date: Fri, 18 Nov 2016 16:29:16 +0100
From: Patrice Guérin <guerinp@magic.fr>
User-Agent: Mozilla/5.0 (Windows NT 5.0; rv:12.0) Gecko/20120429 Firefox/12.0 SeaMonkey/2.9.1
MIME-Version: 1.0
To: json@ietf.org
X-sfr-mailing: LEGIT
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/E14Gkc9ZRsrwFytAvRygjMul5AE>
X-Mailman-Approved-At: Sat, 19 Nov 2016 17:54:30 -0800
Subject: [Json] Question regarding RFC 7159
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.17
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: <https://mailarchive.ietf.org/arch/browse/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, 18 Nov 2016 15:38:57 -0000
Hello, In section 4 - Objects, member name is specified as string. Is there any limitations in this case ? For example, is a name beginning with a number valid or not ? Thank you. Kind regards, Patrice.
- [Json] Question regarding RFC 7159 Patrice Guérin