IETF Logo Mail Archive

Re: [Json] Nudging the English-language vs. formalisms discussion forward

Nico Williams <nico@cryptonector.com> Thu, 20 February 2014 00:31 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 974201A02D8 for <json@ietfa.amsl.com>; Wed, 19 Feb 2014 16:31:22 -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 Fjm1_zeJbdcB for <json@ietfa.amsl.com>; Wed, 19 Feb 2014 16:31:21 -0800 (PST)
Received: from homiemail-a24.g.dreamhost.com (caiajhbdcbhh.dreamhost.com [208.97.132.177]) by ietfa.amsl.com (Postfix) with ESMTP id 3E4831A02AE for <json@ietf.org>; Wed, 19 Feb 2014 16:31:21 -0800 (PST)
Received: from homiemail-a24.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTP id 05C912C806B for <json@ietf.org>; Wed, 19 Feb 2014 16:31:18 -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:content-transfer-encoding; s= cryptonector.com; bh=kdiuU/RjLfc4el4EJYJWQMMcZXY=; b=SRXCb34dxfT hspEjapUEPuZ8UPJ5i17Buyh+0kOGITha7crciVq5G+OSp91IRSAThG/bFWAzxXm 5LDQE9nOOjN9nA40h3ZZRIa24NI/74d2I1FzazOeVihuMcDBp9tH3Ri7l0iyA3br gJ1I+R2nSf8X3tKVb1DESlFZHS6kPBxM=
Received: from mail-wi0-f169.google.com (mail-wi0-f169.google.com [209.85.212.169]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a24.g.dreamhost.com (Postfix) with ESMTPSA id A85A12C806D for <json@ietf.org>; Wed, 19 Feb 2014 16:31:17 -0800 (PST)
Received: by mail-wi0-f169.google.com with SMTP id e4so97103wiv.2 for <json@ietf.org>; Wed, 19 Feb 2014 16:31:15 -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:content-transfer-encoding; bh=xJkfbys78o8wvtgWPq3lxmCvM36qoCr8AnAlwYufKAE=; b=T9Efd+LI2Uw5X0H6ur69cZfD9p0y0P8rD8s8IIWhLttId/tgdBmGyh+0Ty2B2oOtqi FzGHu201vWyMGXsKuEQNMoHBnekzJE7tgrHSagIW1UsLXZmYAAcfALniZbMGlb00lm10 rUslg4bTJztNH8gxgtrQWMq1lqbm0ordeJcRCh8dMdYGDFbgTsUNIhwV8W5FuD/eem0u ZdsBKJMXViwiyJZQgs+hVzjts4HwTRsodsNJvj0VpFJTFS2nU0aHkfTnRRbj0mLxjOtN tsXxIxInrmpd+Q8rSwQhUlToeeSpuEY6fS9EUTkYYcsi38qZ1LoWy2n1T9XvzR2SBedc C09Q==
MIME-Version: 1.0
X-Received: by 10.180.102.42 with SMTP id fl10mr4222238wib.42.1392856275831; Wed, 19 Feb 2014 16:31:15 -0800 (PST)
Received: by 10.217.108.132 with HTTP; Wed, 19 Feb 2014 16:31:15 -0800 (PST)
In-Reply-To: <CAHBU6is7iH3CQE4uH55iszCAQ1afDrX8MYVXkJY8cJJ96P+wBA@mail.gmail.com>
References: <CAHBU6itzQ0rzU3EUYUqzm2qhx03qk1mpx2sehS_zeiw1ypcEgw@mail.gmail.com> <CAK3OfOhfjkbq6eREkt=MBVL1C9ubh-6My3Lvg-mnOxD0+cpN1Q@mail.gmail.com> <CAHBU6isZbew8O1HJ+XcFsMCR42iDoO_uemPXVwa3=vM5A=MngA@mail.gmail.com> <CAK3OfOgmVsNJqrqCfsD7h37axssOoaX3DGHqO=bTn5bWrA+MFA@mail.gmail.com> <A4B53816-6FBF-4A37-8BC9-F0A9D0867BCD@tzi.org> <CAC4RtVDLQ3q5KxG+jDYfDB09JZUOBcojTR3ebxhr1QUOXLeEvA@mail.gmail.com> <CAMm+LwiCHt2NLW8AV93Tzh=hUXGT7SWM8W5zXSehmBF+nEMCkw@mail.gmail.com> <rvcag9tv4cn6jioncd1rmmc19gcm59l6e9@hive.bjoern.hoehrmann.de> <CAK3OfOgOghu_4jxHuoDSnHbyJJRu=xa_YBmgO92CMspMQApceg@mail.gmail.com> <255B9BB34FB7D647A506DC292726F6E1153B778363@WSMSG3153V.srv.dir.telstra.com> <CAHBU6is7iH3CQE4uH55iszCAQ1afDrX8MYVXkJY8cJJ96P+wBA@mail.gmail.com>
Date: Wed, 19 Feb 2014 18:31:15 -0600
Message-ID: <CAK3OfOicmOX1rY7BrVLLn2ER_+fQSaemdUzA9hTp44HqbYwJKQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Tim Bray <tbray@textuality.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
Archived-At: http://mailarchive.ietf.org/arch/msg/json/lEGZZy8kuVNX8i0x44kdTBt2Oyg
Cc: "Manger, James" <James.H.Manger@team.telstra.com>, JSON WG <json@ietf.org>
Subject: Re: [Json] Nudging the English-language vs. formalisms discussion forward
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: Thu, 20 Feb 2014 00:31:22 -0000

On Wed, Feb 19, 2014 at 6:24 PM, Tim Bray <tbray@textuality.com> wrote:
> Hm, obvious when you think about it, since JSON’s roots are in JavaScript
> and JSON docs are parseable as such, a bagful of JS assertions (yeah, I know
> JS doesn’t have an “assert” primitive, but still) could be a not-terrible
> stand-in for a schema. Sort of Schematron-like.

Yes, pattern matching type rules would WFM as one option.  Note that
the stuff you're responding to here looks not too unlike... XDR, or
even ASN.1.  The metaphor seems to be: named types.

Nico
--

v2.23.0 | Report a Bug | By Email