IETF Logo Mail Archive

Re: [Json] Normative reference reasoning and logistics

"Joe Hildebrand (jhildebr)" <jhildebr@cisco.com> Tue, 17 November 2015 09:10 UTC

Return-Path: <jhildebr@cisco.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id 69B361B2D24 for <json@ietfa.amsl.com>; Tue, 17 Nov 2015 01:10:48 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -15.086
X-Spam-Level:
X-Spam-Status: No, score=-15.086 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, RCVD_IN_DNSWL_HI=-5, RP_MATCHES_RCVD=-0.585, SPF_PASS=-0.001, USER_IN_DEF_DKIM_WL=-7.5] autolearn=ham
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 Z4AEa808DnGE for <json@ietfa.amsl.com>; Tue, 17 Nov 2015 01:10:47 -0800 (PST)
Received: from rcdn-iport-5.cisco.com (rcdn-iport-5.cisco.com [173.37.86.76]) (using TLSv1.2 with cipher DHE-RSA-SEED-SHA (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 52BFC1B2D22 for <json@ietf.org>; Tue, 17 Nov 2015 01:10:47 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=cisco.com; i=@cisco.com; l=1212; q=dns/txt; s=iport; t=1447751447; x=1448961047; h=from:to:subject:date:message-id:references:in-reply-to: content-id:content-transfer-encoding:mime-version; bh=bNsl7GI+zT7s5Jy0fxmunow7kZ0ovYegCjFbRXNzVZQ=; b=mmkeYux3L1x2cBAbVbEdVRtZKhroht4mxe3bf35cNA5//UUT9UXF6T+e BuJH/6h6DTYEQu4hYTqOboSUpqR6sayXgbjYN9XRsrcIXThJNWO0DH7/4 UE6WvANjeiqrWbBGQO5NVqME8f3xG8xRyHzTGDkta8NDKbBZ5GZuk3v3+ g=;
X-IronPort-Anti-Spam-Filtered: true
X-IronPort-Anti-Spam-Result: A0AKAgCF7kpW/4UNJK1dgzuBQga+VwENgWWGEAIcgS44FAEBAQEBAQGBCoQ1AQEEIxFVAgEIDgwCJgICAjAVEAIEARKILqsHkEQBAQEBAQEBAQEBAQEBAQEBAQEBAQEYgQGFU4IQgm6EWYMcL4EVAQSWSQGNKYFblniDcQEfAQFChARyhAOBBwEBAQ
X-IronPort-AV: E=Sophos;i="5.20,307,1444694400"; d="scan'208";a="47548480"
Received: from alln-core-11.cisco.com ([173.36.13.133]) by rcdn-iport-5.cisco.com with ESMTP/TLS/DHE-RSA-AES256-SHA; 17 Nov 2015 09:10:46 +0000
Received: from XCH-RTP-004.cisco.com (xch-rtp-004.cisco.com [64.101.220.144]) by alln-core-11.cisco.com (8.14.5/8.14.5) with ESMTP id tAH9Akfo009178 (version=TLSv1/SSLv3 cipher=AES256-SHA bits=256 verify=FAIL); Tue, 17 Nov 2015 09:10:46 GMT
Received: from xch-rtp-001.cisco.com (64.101.220.141) by XCH-RTP-004.cisco.com (64.101.220.144) with Microsoft SMTP Server (TLS) id 15.0.1104.5; Tue, 17 Nov 2015 04:10:45 -0500
Received: from xch-rtp-001.cisco.com ([64.101.220.141]) by XCH-RTP-001.cisco.com ([64.101.220.141]) with mapi id 15.00.1104.000; Tue, 17 Nov 2015 04:10:45 -0500
From: "Joe Hildebrand (jhildebr)" <jhildebr@cisco.com>
To: Tim Bray <tbray@textuality.com>, "json@ietf.org" <json@ietf.org>
Thread-Topic: [Json] Normative reference reasoning and logistics
Thread-Index: AQHRHxA7TAPtcsxNR0yDl0V93+X9ZZ6gViIA
Date: Tue, 17 Nov 2015 09:10:45 +0000
Message-ID: <C80A322B-D3FF-4A13-BB32-8545794611B8@cisco.com>
References: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com>
In-Reply-To: <CAHBU6iu0j492Mzbo2HriFtjm_o5516yCsQCX9PGHvqAxhU0Zjg@mail.gmail.com>
Accept-Language: en-US
Content-Language: en-US
X-MS-Has-Attach:
X-MS-TNEF-Correlator:
user-agent: Microsoft-MacOutlook/0.0.0.151105
x-ms-exchange-messagesentrepresentingtype: 1
x-ms-exchange-transport-fromentityheader: Hosted
x-originating-ip: [10.228.162.65]
Content-Type: text/plain; charset="utf-8"
Content-ID: <8B3D004F2B924B4D9001147AAAA71765@emea.cisco.com>
Content-Transfer-Encoding: base64
MIME-Version: 1.0
Archived-At: <http://mailarchive.ietf.org/arch/msg/json/u-taCf-C6xDcY64z4MY09ILLQec>
Subject: Re: [Json] Normative reference reasoning and logistics
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Tue, 17 Nov 2015 09:10:48 -0000

On 11/14/15, 8:10 PM, "json on behalf of Tim Bray" <json-bounces@ietf.org on behalf of tbray@textuality.com> wrote:



>But I have a practical question. What exact effect to we expect this to have?  Will ECMA-404 be updated in place with a reference to 7159bis (ECMA specs can be updated in place, because -404 already has been,
> to remove a silly typo).  Will there be an ECMA-404bis, and if so, should we work carefully with ECMA to make sure that the two -bis specs mutually reference each other?

My understanding is that this is the intent.  A normative reference makes roughly the same amount of sense in the other direction (i.e. Perhaps none, depending on your point of view), but that we have pre-discussed with the -404 team this potential approach for moving forward.

Our ECMA liaison might want to speak more formally to this point.

-- 
Joe Hildebrand

v2.23.0 | Report a Bug | By Email