IETF Logo Mail Archive

Re: [Json] Consensus call: establishing name equality

Tim Bray <tbray@textuality.com> Fri, 21 June 2013 22:29 UTC

Return-Path: <tbray@textuality.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 5160121F9E76 for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 15:29:42 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -0.3
X-Spam-Level:
X-Spam-Status: No, score=-0.3 tagged_above=-999 required=5 tests=[AWL=-0.752, BAYES_00=-2.599, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HTML_MESSAGE=0.001, RCVD_IN_SORBS_DUL=0.877, RDNS_NONE=0.1]
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 auGenyPJy2oq for <json@ietfa.amsl.com>; Fri, 21 Jun 2013 15:29:38 -0700 (PDT)
Received: from mail-vc0-x22a.google.com (mail-vc0-x22a.google.com [IPv6:2607:f8b0:400c:c03::22a]) by ietfa.amsl.com (Postfix) with ESMTP id 2296B21F9E75 for <json@ietf.org>; Fri, 21 Jun 2013 15:29:38 -0700 (PDT)
Received: by mail-vc0-f170.google.com with SMTP id hf12so62529vcb.1 for <json@ietf.org>; Fri, 21 Jun 2013 15:29:37 -0700 (PDT)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:x-originating-ip:in-reply-to:references:date :message-id:subject:from:to:cc:content-type:x-gm-message-state; bh=UvEHhrxG4rF1/0+unNsXQq+3ifi9+j0GdgkIYBScA4k=; b=UbIrAUsPuDHYgcbbC3zA/37nJLmMjZikfvey4SUUEDGVNb8+XefnLQCWwijCYFNs4b BZmEUKkeu1dL1JD0GWWF1DUKWlX9g3OWUJYI2MKZh4ib/ySrjU8ZyltIY6jXXWwZYjgJ ULWnFM81F7oSgphsCSh/0YYSyCmUBQZeO0gXDQQnAYZ/Y8yeNjAK5W5lzsirT/sz447W pUDdSOThvrhRFLxeBfSsoWXVcgtA7GHnrgTIVQx2beTiSUBe5s7GzLRqPzgzOU5k/Ity iuSKckATXaKj007Qsi5wbHoFeGdDW23tBVtxScVTXkOUyzsGcDn19QeibS0X2/0fuRQT igjA==
MIME-Version: 1.0
X-Received: by 10.52.119.233 with SMTP id kx9mr5608483vdb.50.1371853777482; Fri, 21 Jun 2013 15:29:37 -0700 (PDT)
Received: by 10.220.219.200 with HTTP; Fri, 21 Jun 2013 15:29:37 -0700 (PDT)
X-Originating-IP: [96.49.81.176]
In-Reply-To: <CAO1wJ5SzsOvj2voaeM83G2FxmEwBSREHP5YtE5T8G-mgoM4jNw@mail.gmail.com>
References: <DB211AD8-6BBA-4D95-9B6E-F00AA69E584E@vpnc.org> <6BCAAC4F-2B45-43BA-A40B-96F3369A5851@tzi.org> <CAO1wJ5SzsOvj2voaeM83G2FxmEwBSREHP5YtE5T8G-mgoM4jNw@mail.gmail.com>
Date: Fri, 21 Jun 2013 15:29:37 -0700
Message-ID: <CAHBU6iv8wGJQGpsswSf0GgkN6uQAXP8XFRbabjzWnNSJoifQzw@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
To: Jacob Davies <jacob@well.com>
Content-Type: multipart/alternative; boundary="047d7bdc8be4174b1d04dfb199f5"
X-Gm-Message-State: ALoCoQkq8gGSGC4uwPXNWFXVklQnzoeFhV8TteyzewJbrCl1IYLolM3A8c2vNqWF3d0F3WYgn7YP
Cc: Carsten Bormann <cabo@tzi.org>, Paul Hoffman <paul.hoffman@vpnc.org>, JSON WG <json@ietf.org>
Subject: Re: [Json] Consensus call: establishing name equality
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: Fri, 21 Jun 2013 22:29:42 -0000

Hm, I think this is useful.  I’ve seen people go off the rails trying to be
overly clever comparing strings, so this in effect is just telling them not
to overthink. -T


On Fri, Jun 21, 2013 at 3:23 PM, Jacob Davies <jacob@well.com> wrote:

> On Fri, Jun 21, 2013 at 11:18 AM, Carsten Bormann <cabo@tzi.org> wrote:
>
>> Do we have consensus what we'll use the name equality for that we just
>> defined?
>>
>
> That's my question. What is the problem this is seeking to solve again?
> Because I'm inclined to say 0, especially since keys cannot be guaranteed
> to be unique (and so no definition of uniqueness needs to be defined for
> that). It seems like this is dictating the interpretation of data, rather
> than its format.
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>

v2.31.3 | Report a Bug | By Email | System Status