IETF Logo Mail Archive

[Json] Questions regarding duplicate names

Pete Resnick <presnick@qti.qualcomm.com> Tue, 16 July 2013 02:57 UTC

Return-Path: <presnick@qti.qualcomm.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 DF1EB11E817B for <json@ietfa.amsl.com>; Mon, 15 Jul 2013 19:57:56 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.599
X-Spam-Level:
X-Spam-Status: No, score=-102.599 tagged_above=-999 required=5 tests=[AWL=0.000, 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 r0zcnqebsZtl for <json@ietfa.amsl.com>; Mon, 15 Jul 2013 19:57:52 -0700 (PDT)
Received: from sabertooth02.qualcomm.com (sabertooth02.qualcomm.com [65.197.215.38]) by ietfa.amsl.com (Postfix) with ESMTP id A618621F8C9D for <json@ietf.org>; Mon, 15 Jul 2013 19:57:52 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=simple/simple; d=qti.qualcomm.com; i=@qti.qualcomm.com; q=dns/txt; s=qcdkim; t=1373943472; x=1405479472; h=message-id:date:from:mime-version:to:subject: content-transfer-encoding; bh=k0Y2UHY/XDFe6lxXpeXwlkcVTiEMPhTZlWcP4WdHBPo=; b=bnLdgczmJ6hg7bEX8HPLVGTBnMDeYYLxKyNpmu3WVDJdHMog73a5mPoW rdal16ZmjIeBCVGg/CvXxx+vOzEhyYEzPTaDkV/AM6Xsdhgxe3Ad9T5xE e/d3ysFCc/+VKxwfl2ji29Rxl1DgkAN/0x0kTsTYM0CMgbUFQCWVxNDh6 c=;
X-IronPort-AV: E=Sophos;i="4.89,673,1367996400"; d="scan'208";a="47574185"
Received: from ironmsg02-lv.qualcomm.com ([10.47.202.183]) by sabertooth02.qualcomm.com with ESMTP; 15 Jul 2013 19:57:52 -0700
Received: from nasanexhc03.na.qualcomm.com ([172.30.48.26]) by ironmsg02-lv.qualcomm.com with ESMTP/TLS/RC4-SHA; 15 Jul 2013 19:57:51 -0700
Received: from nasanexhc05.na.qualcomm.com (172.30.48.2) by NASANEXHC03.na.qualcomm.com (172.30.48.26) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 15 Jul 2013 19:57:51 -0700
Received: from resnick2.qualcomm.com (172.30.48.1) by qcmail1.qualcomm.com (172.30.48.2) with Microsoft SMTP Server (TLS) id 14.2.318.4; Mon, 15 Jul 2013 19:57:51 -0700
Message-ID: <51E4B6AE.4040502@qti.qualcomm.com>
Date: Mon, 15 Jul 2013 21:57:50 -0500
From: Pete Resnick <presnick@qti.qualcomm.com>
User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.7; en-US; rv:1.9.1.9) Gecko/20100630 Eudora/3.0.4
MIME-Version: 1.0
To: "json@ietf.org" <json@ietf.org>
Content-Type: text/plain; charset="ISO-8859-1"; format="flowed"
Content-Transfer-Encoding: 7bit
X-Originating-IP: [172.30.48.1]
Subject: [Json] Questions regarding duplicate names
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: Tue, 16 Jul 2013 02:57:57 -0000

There are folks who want the spec to forbid generators from emitting 
objects that contain duplicate names. There are folks who don't. To the 
folks that don't:

     a) Do you actually want a normative statement saying that 
generators MAY produce duplicate names?

     b) Do you want/are you OK with text that would give instructions 
about what parsers should do with duplicate names? If so:

     c) What should parsers do with duplicate names?

Yes/No answers aren't terribly interesting to a) or b). Give some 
explanation.

I'll likely have more questions to follow up on this topic, but these 
seem like a good starting point.

I look forward to your answers.

pr

-- 
Pete Resnick<http://www.qualcomm.com/~presnick/>
Qualcomm Technologies, Inc. - +1 (858)651-4478

v2.23.0 | Report a Bug | By Email