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

Nico Williams <nico@cryptonector.com> Wed, 19 February 2014 16:06 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 CC5751A055A for <json@ietfa.amsl.com>; Wed, 19 Feb 2014 08:06: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 9KcL8I2CPrWo for <json@ietfa.amsl.com>; Wed, 19 Feb 2014 08:06:21 -0800 (PST)
Received: from homiemail-a87.g.dreamhost.com (caiajhbdcagg.dreamhost.com [208.97.132.66]) by ietfa.amsl.com (Postfix) with ESMTP id C9FA21A04F7 for <json@ietf.org>; Wed, 19 Feb 2014 08:06:21 -0800 (PST)
Received: from homiemail-a87.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTP id 9167426C078 for <json@ietf.org>; Wed, 19 Feb 2014 08:06: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; s=cryptonector.com; bh=Yn5sPIYFcYDR/qFKUSvt yED7+2E=; b=wEOQ/yLG9C8WaQoYUSoqdPzDSaZw2CTyRtAwd0bwNjiK9huFSpe7 EYSaah/T8Vu+ZYQmKLFQWMy8DahCoVaP4IQcu5PT8v7ih251WcTCLMyJ2RFltn3w Fg3Fr27sGdUu9PTZirhpYSBuax6BWOWg28sdsA/bOBYgFaOYLytuMQ0=
Received: from mail-wg0-f49.google.com (mail-wg0-f49.google.com [74.125.82.49]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a87.g.dreamhost.com (Postfix) with ESMTPSA id 2964A26C05E for <json@ietf.org>; Wed, 19 Feb 2014 08:06:17 -0800 (PST)
Received: by mail-wg0-f49.google.com with SMTP id y10so493903wgg.4 for <json@ietf.org>; Wed, 19 Feb 2014 08:06:16 -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=3DU6dn0kE1miCjvkk794GbYIYWGc0aZzrboMe68Ac+s=; b=kEHlVoauVq1ivdZE8o2EtzE9JOUZ4v8t9xipICBP2gGkjjWSdne++WC9M+HBVxYMIw pIijdfq/ULO9UjuWdiGW2d2GZYy2teGomarDUwfxKr2xhxr7mlb1+XAZtSDrMR3xrEtd nXbrm74W3wVyvfuZ7GebwIt5Z3Gm+nDqzDb/YYLdxHVdZBe3KDcy3y9sgXQvd/BgXaSV chR4J5RTTAeq8L6ebHQp9nHkT8+zUAtTWp2ndbprCX0fUcfpe6/nSTXp9PLLaqUwDR+o u+48FKQeizkrBQVAvxElhNBiUbefRukkToDXwQIQYGECbUxOHpINkwgDuyhOqqzvoiAQ h9pA==
MIME-Version: 1.0
X-Received: by 10.194.185.165 with SMTP id fd5mr1762863wjc.95.1392825976330; Wed, 19 Feb 2014 08:06:16 -0800 (PST)
Received: by 10.217.108.132 with HTTP; Wed, 19 Feb 2014 08:06:16 -0800 (PST)
In-Reply-To: <CAMm+LwhUh_yN-hzaoDWfrO_H2iGvYvj99BCE4EcYmgqCPqXoVQ@mail.gmail.com>
References: <C87F9B96-E028-4F0E-A950-B39D3F68FFE7@vpnc.org> <CAMm+LwhUh_yN-hzaoDWfrO_H2iGvYvj99BCE4EcYmgqCPqXoVQ@mail.gmail.com>
Date: Wed, 19 Feb 2014 10:06:16 -0600
Message-ID: <CAK3OfOgK9XBtWZPM5fDi+4Tp8G7iLnzy+w5L2kjLpxNkDcy=vQ@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Phillip Hallam-Baker <hallam@gmail.com>
Content-Type: text/plain; charset=UTF-8
Archived-At: http://mailarchive.ietf.org/arch/msg/json/6At4bIKi28Bs7_WWiJXj3ULyFrA
Cc: Paul Hoffman <paul.hoffman@vpnc.org>, 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: Wed, 19 Feb 2014 16:06:23 -0000

On Wed, Feb 19, 2014 at 9:56 AM, Phillip Hallam-Baker <hallam@gmail.com> wrote:
> So even though my view is that JSON is the data model I intend to use for
> all future protocols (unless something else comes along), It seems to me
> that if we design a formal documentation/prototyping tool we should have it
> be capable of dumping out the equivalent XML and ASN.1 schemas. But since
> the capabilities of XML and ASN.1 schema are a superset of the capabilities
> of JSON, this is pretty easy to do.

Sure that's doable.  Quick question: should a JSON schema also follow
the model of defining "types", like ASN.1?  Or do you have something
else in mind?

Nico
--