Re: [Json] What does "break compatibility" mean?
Paul Hoffman <paul.hoffman@vpnc.org> Thu, 28 February 2013 20:43 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 7010B21F8976 for <json@ietfa.amsl.com>; Thu, 28 Feb 2013 12:43:20 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -102.688
X-Spam-Level:
X-Spam-Status: No, score=-102.688 tagged_above=-999 required=5 tests=[AWL=-0.089, BAYES_00=-2.599, 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 6I6kE13rsv8A for <json@ietfa.amsl.com>; Thu, 28 Feb 2013 12:43:20 -0800 (PST)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id 06EA021F8922 for <json@ietf.org>; Thu, 28 Feb 2013 12:43:19 -0800 (PST)
Received: from [10.20.30.90] (50-1-98-12.dsl.dynamic.sonic.net [50.1.98.12]) (authenticated bits=0) by hoffman.proper.com (8.14.5/8.14.5) with ESMTP id r1SKhFlt032295 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO); Thu, 28 Feb 2013 13:43:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
Content-Type: text/plain; charset="windows-1252"
Mime-Version: 1.0 (Mac OS X Mail 6.2 \(1499\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <CAHBU6ivXpRaTPsbLd90zBDdiypO2pYn9mckkNcCh9ZEApsK1yg@mail.gmail.com>
Date: Thu, 28 Feb 2013 12:43:14 -0800
Content-Transfer-Encoding: quoted-printable
Message-Id: <C29B03E1-30DB-42E8-9132-AC542052BEE7@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> <CAHBU6ivXpRaTPsbLd90zBDdiypO2pYn9mckkNcCh9ZEApsK1yg@mail.gmail.com>
To: Tim Bray <tbray@textuality.com>
X-Mailer: Apple Mail (2.1499)
Cc: Barry Leiba <barryleiba@computer.org>, 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 20:43:20 -0000
On Feb 28, 2013, at 12:06 PM, Tim Bray <tbray@textuality.com> wrote: > It’s clear to me that, *for the purposes of the IETF*, someone needs to say “People sending JSON MUST NOT use duplicate keys.” The fact that certain libraries allow less-clueful developers to do this, and that parsing software is observed to behave unpredictably when they do, should only encourage us. That doesn't answer the question in the heading, and the question was aimed at our esteemed Area Director. :-) --Paul Hoffman
- [Json] Counterproposal on work items Tim Bray
- Re: [Json] Counterproposal on work items Paul Hoffman
- Re: [Json] Counterproposal on work items Matt Miller (mamille2)
- Re: [Json] Counterproposal on work items Gonzalo Salgueiro
- Re: [Json] Counterproposal on work items Mike Jones
- Re: [Json] Counterproposal on work items Tatu Saloranta
- Re: [Json] Counterproposal on work items Nico Williams
- Re: [Json] Counterproposal on work items Tony Hansen
- Re: [Json] Counterproposal on work items Paul Hoffman
- Re: [Json] Counterproposal on work items Joe Hildebrand (jhildebr)
- Re: [Json] Counterproposal on work items Mark Nottingham
- Re: [Json] Counterproposal on work items Tim Bray
- Re: [Json] Counterproposal on work items Peter Saint-Andre
- Re: [Json] Counterproposal on work items Robert Sayre
- Re: [Json] Counterproposal on work items Paul E. Jones
- Re: [Json] Counterproposal on work items Barry Leiba
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Peter Saint-Andre
- Re: [Json] Counterproposal on work items Paul E. Jones
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Carsten Bormann
- Re: [Json] Counterproposal on work items Francis Galiegue
- Re: [Json] Counterproposal on work items Markus Lanthaler
- [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Tim Bray
- Re: [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Nico Williams
- Re: [Json] What does "break compatibility" mean? Barry Leiba
- Re: [Json] What does "break compatibility" mean? Paul Hoffman
- Re: [Json] What does "break compatibility" mean? Tim Bray
- Re: [Json] What does "break compatibility" mean? Nico Williams
- Re: [Json] What does "break compatibility" mean? Tatu Saloranta
- Re: [Json] What does "break compatibility" mean? Martin J. Dürst
- Re: [Json] What does "break compatibility" mean? Paul Hoffman