Re: [Json] What does "break compatibility" mean?

Barry Leiba <barryleiba@computer.org> Thu, 28 February 2013 21:46 UTC

Return-Path: <barryleiba@gmail.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 DFBEB21F892C for <json@ietfa.amsl.com>; Thu, 28 Feb 2013 13:46:43 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.039
X-Spam-Level:
X-Spam-Status: No, score=-102.039 tagged_above=-999 required=5 tests=[AWL=-0.061, BAYES_00=-2.599, FM_FORGED_GMAIL=0.622, NO_RELAYS=-0.001, USER_IN_WHITELIST=-100]
Received: from mail.ietf.org ([64.170.98.30]) by localhost (ietfa.amsl.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id D4VandY0DVBG for <json@ietfa.amsl.com>; Thu, 28 Feb 2013 13:46:43 -0800 (PST)
Received: from mail-la0-x231.google.com (mail-la0-x231.google.com [IPv6:2a00:1450:4010:c03::231]) by ietfa.amsl.com (Postfix) with ESMTP id 52D1F21F88ED for <json@ietf.org>; Thu, 28 Feb 2013 13:46:41 -0800 (PST)
Received: by mail-la0-f49.google.com with SMTP id fs13so2251045lab.22 for <json@ietf.org>; Thu, 28 Feb 2013 13:46:40 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:x-received:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:cc:content-type; bh=u9CDUk2jiuNAyGXMpLAHFEe1Q5lZ5Wp5fdjtypn8VZ8=; b=dt4CTIqn9FA1Y3FzIMwNTM0h6/g0hsd+L0x/G6kvUgs3NiRvsoWhXOVOvAiL+Wvlaw emKcRVPVylD6UWEf9Frw2S/q1unA0B3uJQk1HwR519MviMwyq8NTiDFAfWsN9RIE/P9K iAlNqf1KDA2hOw8pPX69MzeZhu7DwhQ2bdHdsC0yC6rzzlpdNzI6I3a3vl8Uf7An/aUC Oe5LSsnRzFQHdxzYsLZuU5s14wRLG2lMFYznpb47O3UZKSfOV224EXESgIcG2CU2BllL G/Uq9F9P/a9SPKIjKcOvvXt8AQ95Kl74SvU8M0+jcH4gZve3ZdVK9UiNsf7hBpr5s0Qr J0/Q==
MIME-Version: 1.0
X-Received: by 10.112.28.101 with SMTP id a5mr4295141lbh.0.1362088000018; Thu, 28 Feb 2013 13:46:40 -0800 (PST)
Sender: barryleiba@gmail.com
Received: by 10.112.76.98 with HTTP; Thu, 28 Feb 2013 13:46:39 -0800 (PST)
In-Reply-To: <63519CDF-144F-4DA4-A9F3-A1AB824861D2@vpnc.org>
References: <CAHBU6ityBeA+M-PEme09gO_jVySr33-X308i1UttxrQwSgYmGQ@mail.gmail.com> <0F513426-F26D-48F4-A7A8-88F3D3DA881B@vpnc.org> <CAK3OfOjFCnR8k1csVOkSKTDpA8exDvYdAijn80HKD5zwNzzeSw@mail.gmail.com> <4514F5D7-4A7E-476F-987D-C4C617F2BCBD@vpnc.org> <4D80AE86-4DBA-4236-9E2A-A06F2F9C30F7@mnot.net> <00b001ce1509$c4c99fc0$4e5cdf40$@packetizer.com> <CAC4RtVDXwPRL-Cz_Xf-kjU3dzzY+JheDGivSE9hF2v1NLkWEgQ@mail.gmail.com> <63519CDF-144F-4DA4-A9F3-A1AB824861D2@vpnc.org>
Date: Thu, 28 Feb 2013 16:46:39 -0500
X-Google-Sender-Auth: J1LoB9iqgQU9EmNP7xMf3QugoYg
Message-ID: <CALaySJKe9W9BCUXnbOudQE63bLbLTQEtgMc2Fxcjiwg=WByyjQ@mail.gmail.com>
From: Barry Leiba <barryleiba@computer.org>
To: Paul Hoffman <paul.hoffman@vpnc.org>
Content-Type: text/plain; charset=ISO-8859-1
X-Mailman-Approved-At: Thu, 28 Feb 2013 13:51:25 -0800
Cc: json@ietf.org
Subject: Re: [Json] What does "break compatibility" mean?
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.12
Precedence: list
List-Id: "Discussion related to JavaScript Object Notation \(JSON\)." <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, 28 Feb 2013 21:46:44 -0000

> As we discussed, RFC 4627 says "The names within an object SHOULD be
> unique." So, what does "break compatibility" mean for this specific issue?
...
> That certainly sounds reasonable. The question is whether you will allow
> clarifications that might make something incompatible.

Yes, I guess I did speak too soon: that specific change is one we've
talked about, and that's likely to be on the charter.

But we do need to scope this very tightly.

Barry