IETF Logo Mail Archive

Re: [Json] JSON Concluded? Well, maybe not

Tim Bray <tbray@textuality.com> Sun, 31 December 2017 18:50 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 75ED3127342 for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 10:50:37 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -2.599
X-Spam-Level:
X-Spam-Status: No, score=-2.599 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, HTML_MESSAGE=0.001, RCVD_IN_DNSWL_LOW=-0.7] autolearn=ham autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=pass (2048-bit key) header.d=textuality-com.20150623.gappssmtp.com
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 N2S1PKDt1Jq5 for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 10:50:35 -0800 (PST)
Received: from mail-wm0-x233.google.com (mail-wm0-x233.google.com [IPv6:2a00:1450:400c:c09::233]) (using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id E34E8127058 for <json@ietf.org>; Sun, 31 Dec 2017 10:50:34 -0800 (PST)
Received: by mail-wm0-x233.google.com with SMTP id y82so11454098wmg.1 for <json@ietf.org>; Sun, 31 Dec 2017 10:50:34 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=textuality-com.20150623.gappssmtp.com; s=20150623; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=Q4Mxc2WttyonWXgmPQAmRSECIl8PV/qP95YPwnnr5IQ=; b=LUU8YX9WMSFAHzPj2Rj3k0eJ1CO5C/ktUZBN+uO1XEeHMhD0uYycQcPEbO5tye30V0 ZiybW17mmBUlcmjMUCJ34ON31tqu0RZkVPpEqGIb9dg0/uoTquTMlEtlmZJMnmm98NvD 4eDUg7phWLfpgDkuc5n5DtG9J5F/XaLDbg5cr75RnUR+5VzL4KmRT0p6mI4NeNmpcz8F eWIv+Vq8pGrBoA47mdDIvZO7d4oZB+8ZsS9zCODgCr2QSY/zHoG09oebqTRpsrXk8mHe wP726fP5IG8JrUXEIV3pAcNp/oaREHHz+6fe5yKi/XwB9acX/83axE4+E7C1xcgFlZSv ldPg==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=Q4Mxc2WttyonWXgmPQAmRSECIl8PV/qP95YPwnnr5IQ=; b=amsdhaFY+9an41F66LLNIbtZWzMpaPIxErmLAoWc3WBvXCe3Zu1OaB+GDGx3mUoC7a 92cw6xbSMyQ4q804jgNBcSEzX19jUUO0y9KeoHJdXJLMViZiFfjhJKXZWwi1O+MiGfuC ccPzTj4ZA/LBFGHS/vcxDhYgtLzBj0U274TbtYSOcRTGxMr8QMcrAm/xG2MYkueBO0Vy ahka1mQrBKba/FG4/HsBPY2bUroyI50g6q5NteSu02ElkTMn1d+CIqaghjt3nCo5yowO JIDWlBNxRV7R0Nj+SwZvbmN4Mo9ekbz0fahRXvytVB10JL60gr1Fw/AO4QkJkDQV7Z7W gmyQ==
X-Gm-Message-State: AKGB3mJPvjexc1q0NZ0vKGapxI4TPX4DuZDT8BsN6djGueixh0xCemRi aZpxA/l4EPpf4Va6N9b4lgxeY2i1/kKy/+5eZoDqyg==
X-Google-Smtp-Source: ACJfBovmIVRBm9wtgWBwNkPb5t2HnJ/RnavGdRwDf5j+boQ0nGuFCSW0EhlUhjWHpFwQpUEObA2IqCjpuERcvwcPC5s=
X-Received: by 10.80.174.2 with SMTP id c2mr53164038edd.93.1514746232799; Sun, 31 Dec 2017 10:50:32 -0800 (PST)
MIME-Version: 1.0
Received: by 10.80.192.129 with HTTP; Sun, 31 Dec 2017 10:50:12 -0800 (PST)
X-Originating-IP: [174.6.224.108]
In-Reply-To: <CALH+fvqBGu0i=LcciYgOLSwbQJXfqgcXTdd=rxvfHfqiRyBj7g@mail.gmail.com>
References: <13860352-ef8e-1d4b-2eff-27e275c25e3a@gmail.com> <CALH+fvqBGu0i=LcciYgOLSwbQJXfqgcXTdd=rxvfHfqiRyBj7g@mail.gmail.com>
From: Tim Bray <tbray@textuality.com>
Date: Sun, 31 Dec 2017 10:50:12 -0800
Message-ID: <CAHBU6itC+XAKhc_m_ywG5O2bpky9DnmzfiNVqP3WrxLaE7uenA@mail.gmail.com>
To: Richard Gibson <richard.gibson@gmail.com>
Cc: Anders Rundgren <anders.rundgren.net@gmail.com>, "json@ietf.org" <json@ietf.org>
Content-Type: multipart/alternative; boundary="94eb2c196ade2199eb0561a75732"
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/Ec78QgZqpvcqPd97fvGV3Nt2tVA>
Subject: Re: [Json] JSON Concluded? Well, maybe not
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.22
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: Sun, 31 Dec 2017 18:50:37 -0000

If I were going to make an argument for keeping the WG alive, it would
require someone to get energized and submit an I-D for a plausible JSON
schema system, or maybe even a much-needed formalization of JSONPath. We
use JSONPath a lot at AWS.

On Sun, Dec 31, 2017 at 10:43 AM, Richard Gibson <richard.gibson@gmail.com>
wrote:

> On the topic of JSON normalization, I believe that canonicaljson-spec
> <http://gibson042.github.io/canonicaljson-spec/> covers all cases while
> respecting prior art like https://tools.ietf.org/html/
> draft-staykov-hu-json-canonical-form-00 and RFC 7638. I'd like to get it
> published as an RFC to handle scenarios like those mentioned by Anders
> Rundgren, but am not sure how to go about doing so. Is this a good place to
> ask for assistance?
>
> On Sun, Dec 31, 2017 at 12:24 AM, Anders Rundgren <
> anders.rundgren.net@gmail.com> wrote:
>
>> Congratulations everybody to the revised JSON RFC!
>>
>> Does this mean that JSON is "done" for good?
>>
>> Probably not because the concept I have mentioned from time to time, the
>> ability adding a digital signature to a JSON object (in contrast to signing
>> arbitrary Base64Url-encoded data), is still very much alive.  In fact,
>> there is an I-D in preparation aiming at reducing the current proliferation
>> of "DIY-standards" for dealing with this highly requested feature.  The
>> only real challenge is agreeing on a suitable way "normalizing" JSON data
>> during parsing and serialization.  Such a scheme will be like an extended
>> version of I-JSON (RFC7493), potentially having an impact on "ordinary"
>> uses of JSON as well.
>>
>> Happy New [and optionally signed] JSON Year
>> Anders Rundgren
>>
>> _______________________________________________
>> json mailing list
>> json@ietf.org
>> https://www.ietf.org/mailman/listinfo/json
>>
>
>
> _______________________________________________
> json mailing list
> json@ietf.org
> https://www.ietf.org/mailman/listinfo/json
>
>


-- 
- Tim Bray (If you’d like to send me a private message, see
https://keybase.io/timbray)

v2.23.0 | Report a Bug | By Email