IETF Logo Mail Archive

Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter

Nico Williams <nico@cryptonector.com> Mon, 17 March 2014 03:51 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 94B431A02B7 for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 20:51:38 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: 1.753
X-Spam-Level: *
X-Spam-Status: No, score=1.753 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, FH_RELAY_NODNS=1.451, FM_FORGED_GMAIL=0.622, HELO_MISMATCH_COM=0.553, IP_NOT_FRIENDLY=0.334, RDNS_NONE=0.793] 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 wNanHkHaCCzS for <json@ietfa.amsl.com>; Sun, 16 Mar 2014 20:51:37 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (unknown [69.163.253.172]) by ietfa.amsl.com (Postfix) with ESMTP id B4FE01A02B6 for <json@ietf.org>; Sun, 16 Mar 2014 20:51:37 -0700 (PDT)
Received: from homiemail-a66.g.dreamhost.com (localhost [127.0.0.1]) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTP id F2C05350078 for <json@ietf.org>; Sun, 16 Mar 2014 20:51:29 -0700 (PDT)
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=cuJk5Qkb6olRM+Bl0WCX KpwBNMo=; b=kHIXPVQ0/ksXIdYxdEFXBsJ7vM6F9Q25JidIDXRowxtYDAnWmL7Z eq6aIdQ9YUSNIF+jHAdVIe7s+gKbZnfx3SXp4Fk4Hhwqak++6cCkeRo8vAHeUQFY XuZc7cGkdUyQx2TUkiulvV6eYuQyL1WSC7+za4gvfJ6ZmkKKKhrE5h4=
Received: from mail-wi0-f178.google.com (mail-wi0-f178.google.com [209.85.212.178]) (using TLSv1 with cipher RC4-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: nico@cryptonector.com) by homiemail-a66.g.dreamhost.com (Postfix) with ESMTPSA id A5881350072 for <json@ietf.org>; Sun, 16 Mar 2014 20:51:29 -0700 (PDT)
Received: by mail-wi0-f178.google.com with SMTP id bs8so708354wib.5 for <json@ietf.org>; Sun, 16 Mar 2014 20:51:28 -0700 (PDT)
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=0J1zyt0c19FM7MqRDZF/ub570xtHiaTBQTnBX4Zg7cg=; b=PZ1vqgVzcOblk9Cc2AHX41Oxc+A8lphZe766r7hJ+QeUOfAKx3U78d18XzLYrHKJG+ /Kch2j64G+72a+LRwaI2KxnmjKs80i14Kd6iOj83uacCLXBFhSbJSuYCcGsFSzovDTI+ 39mIslV32TB+izT04t/LQO45F88bXgvEjiQZHN7Y5TI9lFeTM/yG8tfTk6490vS4+MVM zTz3L1t0OTRaLQcTxIhkMY/NCf5kh6SiSNt9jZ+mwOEKVcIbx5iBEfFaFQr9uXwew0jm a4y8U4et3rLyR0QZPuvNEdb/swOhz7UZJZUf0bYZ5E/O8FoNByvQrLx9KFjpzPydms4g vhHA==
MIME-Version: 1.0
X-Received: by 10.180.98.35 with SMTP id ef3mr7758745wib.39.1395028288377; Sun, 16 Mar 2014 20:51:28 -0700 (PDT)
Received: by 10.216.199.6 with HTTP; Sun, 16 Mar 2014 20:51:28 -0700 (PDT)
In-Reply-To: <53238F21.2030508@cisco.com>
References: <53238F21.2030508@cisco.com>
Date: Sun, 16 Mar 2014 22:51:28 -0500
Message-ID: <CAK3OfOjBTN4yXxDftOz6fkR60rPJ-c7=_DSXwwQacyVY7o5xiA@mail.gmail.com>
From: Nico Williams <nico@cryptonector.com>
To: Matt Miller <mamille2@cisco.com>
Content-Type: text/plain; charset="UTF-8"
Archived-At: http://mailarchive.ietf.org/arch/msg/json/X97Wgjo0SfWYM4d_aTVzxeq-uC4
Cc: IETF JSON WG <json@ietf.org>
Subject: Re: [Json] Call for WG Consensus to Adopt I-JSON as a WG Item in the Charter
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: Mon, 17 Mar 2014 03:51:38 -0000

My main complaint is with the recommendation/requirement that JSON
texts be objects at the top-level.

Instead I would say that if there's reason to need to signal "schema"
metadata in-band then a) application should specify how they do that,
b) here's a few ways in which they might, and all their pros and cons.

Note too that there are many apps where there's no need to signal
schema metadata in-band because they always have some way to
communicate relevant metadata out of band.

Nico
--

v2.23.0 | Report a Bug | By Email