Re: [Json] Proposed rechartering for the JSON WG

Nico Williams <nico@cryptonector.com> Sat, 08 February 2014 22:50 UTC

Return-Path: <nico@cryptonector.com>
X-Original-To: json@ietfa.amsl.com
Delivered-To: json@ietfa.amsl.com
Received: from localhost (ietfa.amsl.com [127.0.0.1]) by ietfa.amsl.com (Postfix) with ESMTP id BC14B1A0630 for <json@ietfa.amsl.com>; Sat, 8 Feb 2014 14:50:16 -0800 (PST)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.378
X-Spam-Level:
X-Spam-Status: No, score=-1.378 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FM_FORGED_GMAIL=0.622, RCVD_IN_DNSWL_NONE=-0.0001] autolearn=no
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 9vUa1E_yOQvL for <json@ietfa.amsl.com>; Sat, 8 Feb 2014 14:50:15 -0800 (PST)
Received: from homiemail-a102.g.dreamhost.com (caiajhbdcahe.dreamhost.com [208.97.132.74]) by ietfa.amsl.com (Postfix) with ESMTP id 1181E1A0631 for <json@ietf.org>; Sat, 8 Feb 2014 14:50:14 -0800 (PST)
Received: from homiemail-a102.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTP id 408252005D105 for <json@ietf.org>; Sat, 8 Feb 2014 14:50:15 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha1; c=relaxed; d=cryptonector.com; h= mime-version:in-reply-to:references:date:message-id:subject:from :to:cc:content-type; s=cryptonector.com; bh=dLg5XYFrBVAq0o26tlWz Ep2Kstk=; b=bXUf2tjY8Xx8sCTF6I50qb5X4o8hMeoCPtDVG6l6ODb5us3E0g47 am+Q+k6b0JbU0s0uJb44lXpVzviTuNt38OOcxKk1NWoFyUcJr9Xz7pOoUle0QIGj D4WGPdP1geXBK3rTMxGG0/6E14Gbe5He376B4ryCbPhRBASlOmo7jEk=
Received: from mail-we0-f176.google.com (mail-we0-f176.google.com [74.125.82.176]) (using TLSv1 with cipher ECDHE-RSA-RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a102.g.dreamhost.com (Postfix) with ESMTPSA id E9EFA2005D100 for <json@ietf.org>; Sat, 8 Feb 2014 14:50:14 -0800 (PST)
Received: by mail-we0-f176.google.com with SMTP id q58so3205445wes.21 for <json@ietf.org>; Sat, 08 Feb 2014 14:50:13 -0800 (PST)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :cc:content-type; bh=+kmp0wWbDsnGN/tWeb/JI0h45ZM6XzqsKrXieqKd2dM=; b=Kz/Pz+FI9iEdnLTJ9MCsRNMQxh2nASvUNaJokepjap1bIQaDOaXVgTjmnC17PZMJPu Zzojb2+oBDB1ITLuUNjg/HZhukTiGZpMZ5FQ8mVzUUvM5s4FRSFpYw6mAiIsYJICGP8W X5tZMktBU44c7ds8OaN13L/6WEbqZbVx+IYyL93KSQwQYiALFQtB2N4f29OTTax5pUd9 FwlHsbvEfNPn9Yqp+j/dQ03+zLTapJwyL3KAZPNnDAVwRzGGGOi6fQEzrgi6bCLAyEm+ hOnSIVwpVqDWe0GHheMrCRcMbCRursdhybLf2yFb3ugtbulMJwehWTvabF17h6V9KEdc X09g==
MIME-Version: 1.0
X-Received: by 10.180.108.199 with SMTP id hm7mr4881738wib.1.1391899813257; Sat, 08 Feb 2014 14:50:13 -0800 (PST)
Received: by 10.227.198.69 with HTTP; Sat, 8 Feb 2014 14:50:13 -0800 (PST)
In-Reply-To: <CAHBU6iuR0MPm9q483jBMqTRkGV1f2giGNhp+UciQ7rRnrvcEBA@mail.gmail.com>
References: <52D9B39C.5020102@cisco.com> <1C1347D2-0D99-4D49-B4C1-199246167D23@vpnc.org> <CAMm+Lwj0phrmP563tBbZJKHeYw=Azh1as6GZOA6rANPpC6PJgA@mail.gmail.com> <CAHBU6iv+-9xQYAjZdfZk7+GeA6J+sjaV5era3L+PiJ9RoauBYg@mail.gmail.com> <CAMm+Lwh0O4+iuaJMUhYgj+0GS8e9b_nZtNNX91hOmjUypsgkTQ@mail.gmail.com> <CAK3OfOhu0GZY9CVQrqD4SyjHLVEoEg1DtYj_6imZbbHtzX2eEw@mail.gmail.com> <CAHBU6iuR0MPm9q483jBMqTRkGV1f2giGNhp+UciQ7rRnrvcEBA@mail.gmail.com>
Date: Sat, 08 Feb 2014 16:50:13 -0600
Message-ID: <CAK3OfOj7Ti+rRGXXdMQwFvErUrbG34N8Wn0JqGhaKBA4=ri-nA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset="UTF-8"
Cc: Phillip Hallam-Baker <hallam@gmail.com>, Paul Hoffman <paul.hoffman@vpnc.org>, "json@ietf.org" <json@ietf.org>
Subject: Re: [Json] Proposed rechartering for the JSON WG
X-BeenThere: json@ietf.org
X-Mailman-Version: 2.1.15
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: Sat, 08 Feb 2014 22:50:18 -0000

On Fri, Feb 7, 2014 at 7:14 PM, Tim Bray <tbray@textuality.com> wrote:
> I really want to stay away from the slippery schema slope. [...]
>
> I think nomenclature means having a uniform standardised way to express the
> meaning of the words between "value of" and "MUST".  Perhaps something like
> XPath for JSON.

An XPath/XSLT for JSON would be good.  There's a great candidate for
that: http://stedolan.github.io/jq .   But I don't propose
standardizing such a thing.

> Disclosure: I'm not convinced this is necessary or even useful.

Schemas help document protocols.  They are as useful as ABNF, ASN.1,
and so on.  In practice we can't get to where we have 100% formal
descriptions of everything relevant to interop, but a total lack of
formality isn't exactly a good thing either.  In absence of a JSON
schema language (or three) we'll have to resort to showing examples
and English prose for the rest.

Nico
--