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

Erik Wilde <erik.wilde@dret.net> Sun, 31 December 2017 19:41 UTC

Return-Path: <erik.wilde@dret.net>
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 1B7F5120725 for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 11:41:02 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.801
X-Spam-Level:
X-Spam-Status: No, score=-1.801 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, SPF_PASS=-0.001, T_DKIM_INVALID=0.01, T_RP_MATCHES_RCVD=-0.01] autolearn=no autolearn_force=no
Authentication-Results: ietfa.amsl.com (amavisd-new); dkim=neutral reason="invalid (public key: not available)" header.d=dret.net
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 zJWgcfq3M9cS for <json@ietfa.amsl.com>; Sun, 31 Dec 2017 11:41:00 -0800 (PST)
Received: from postoffice.gristmillmedia.com (dret.net [209.188.86.86]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (No client certificate requested) by ietfa.amsl.com (Postfix) with ESMTPS id 77FC51200C5 for <json@ietf.org>; Sun, 31 Dec 2017 11:41:00 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; c=relaxed/relaxed; d=dret.net; s=default; h=Content-Transfer-Encoding:Content-Type:In-Reply-To:MIME-Version :Date:Message-ID:From:References:Cc:To:Subject:Sender:Reply-To:Content-ID: Content-Description:Resent-Date:Resent-From:Resent-Sender:Resent-To:Resent-Cc :Resent-Message-ID:List-Id:List-Help:List-Unsubscribe:List-Subscribe: List-Post:List-Owner:List-Archive; bh=56JaxMKFw9fI/Uhjj2T0T8Z5Tp0Mk9Fj6lj3j12NG/U=; b=Pidibv80ZY4oMt2rW0c/IRhWDG U21ERRZpiDIHfOmPYY4LFwN3Diwx63EZAskVqB0RPeoMbZ9jHA0G2k18Gfr5Wx0kgyLWejCgpUmXs uWgemWT33USsSPBRTVwLCy1NZxWsE1Bo4Pt5fbIEacsKlAJWpflkQwHL6fM98OuAdJcf9HI1m5eht qcQRNyWEhzY8GRtJjwryPbsUGEhXRygRiEq01WljsvQSKI1lKQ1bld3ul+O5jyQH5ysRStI35MhJo GuIU+U60/rLOpJDlt9NT73b0fYLCZdauj5ESVjG7oLJ6iife/m6Vyqlw06ZvFyZeihkGIitZIoT61 plH6Q0Mg==;
Received: from 108-67-65-66.lightspeed.sntcca.sbcglobal.net ([108.67.65.66]:56221 helo=[192.168.1.78]) by postoffice.gristmillmedia.com with esmtpsa (TLSv1.2:ECDHE-RSA-AES128-GCM-SHA256:128) (Exim 4.89_1) (envelope-from <erik.wilde@dret.net>) id 1eVjTe-0001ZD-Hi; Sun, 31 Dec 2017 14:40:58 -0500
To: Tim Bray <tbray@textuality.com>, Richard Gibson <richard.gibson@gmail.com>
Cc: "json@ietf.org" <json@ietf.org>, Anders Rundgren <anders.rundgren.net@gmail.com>
References: <13860352-ef8e-1d4b-2eff-27e275c25e3a@gmail.com> <CALH+fvqBGu0i=LcciYgOLSwbQJXfqgcXTdd=rxvfHfqiRyBj7g@mail.gmail.com> <CAHBU6itC+XAKhc_m_ywG5O2bpky9DnmzfiNVqP3WrxLaE7uenA@mail.gmail.com>
From: Erik Wilde <erik.wilde@dret.net>
Message-ID: <92077f95-5dd6-3f5b-4765-d14067f698ac@dret.net>
Date: Sun, 31 Dec 2017 11:40:56 -0800
User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10.13; rv:52.0) Gecko/20100101 Thunderbird/52.5.0
MIME-Version: 1.0
In-Reply-To: <CAHBU6itC+XAKhc_m_ywG5O2bpky9DnmzfiNVqP3WrxLaE7uenA@mail.gmail.com>
Content-Type: text/plain; charset="utf-8"; format="flowed"
Content-Language: en-US
Content-Transfer-Encoding: 7bit
X-AntiAbuse: This header was added to track abuse, please include it with any abuse report
X-AntiAbuse: Primary Hostname - postoffice.gristmillmedia.com
X-AntiAbuse: Original Domain - ietf.org
X-AntiAbuse: Originator/Caller UID/GID - [47 12] / [47 12]
X-AntiAbuse: Sender Address Domain - dret.net
X-Get-Message-Sender-Via: postoffice.gristmillmedia.com: authenticated_id: birdhouse@dret.net
X-Authenticated-Sender: postoffice.gristmillmedia.com: birdhouse@dret.net
X-Source:
X-Source-Args:
X-Source-Dir:
Archived-At: <https://mailarchive.ietf.org/arch/msg/json/C7YvXkXOrW2r8WWK8pLo8edbodg>
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 19:41:02 -0000

hello.

On 2017-12-31 10:50, Tim Bray wrote:
> 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.

for the schema aspect:

https://github.com/json-schema-org/json-schema-spec/issues/526 makes the 
relatively small team behind JSON schema (which started out as a 
continuation of the long-abandoned effort by kris zyp	) aware of this 
possibility. i am not involved enough to decide whether they are 
interested in making this step, but at least it's an effort that has 
been pretty active, and it might be an interesting candidate for a JSON 
schema language.

for the JSON path aspect: +1 as well, but i am not aware of something as 
active as the schema language effort above that could be pulled in.

for kicks and giggles, i'd also like to throw in that it would be great 
to have some reusable way of how various vocabularies can exist 
alongside in JSON. one could mutter the words "XML namespaces" here, but 
most people have negative views of them. but still: in APIs, there often 
is the need to support extensibility and openness, and it seems like 
every JSON-based API design has to come up with its own way of doing it.

cheers (and happy new year to everybody!),

dret.

-- 
erik wilde | mailto:erik.wilde@dret.net |
            | http://dret.net/netdret    |
            | http://twitter.com/dret    |