Re: [Json] I-JSON Topic #1: Media Types?

Paul Hoffman <paul.hoffman@vpnc.org> Tue, 29 April 2014 17:26 UTC

Return-Path: <paul.hoffman@vpnc.org>
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 7400D1A08DB for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 10:26:18 -0700 (PDT)
X-Virus-Scanned: amavisd-new at amsl.com
X-Spam-Flag: NO
X-Spam-Score: -1.347
X-Spam-Level:
X-Spam-Status: No, score=-1.347 tagged_above=-999 required=5 tests=[BAYES_00=-1.9, HELO_MISMATCH_COM=0.553] 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 AIO2S0XbZZZD for <json@ietfa.amsl.com>; Tue, 29 Apr 2014 10:26:17 -0700 (PDT)
Received: from hoffman.proper.com (IPv6.Hoffman.Proper.COM [IPv6:2605:8e00:100:41::81]) by ietfa.amsl.com (Postfix) with ESMTP id CE3E71A085A for <json@ietf.org>; Tue, 29 Apr 2014 10:26:17 -0700 (PDT)
Received: from [10.20.30.90] (142-254-17-198.dsl.dynamic.fusionbroadband.com [142.254.17.198]) (authenticated bits=0) by hoffman.proper.com (8.14.8/8.14.7) with ESMTP id s3THQFMq062402 (version=TLSv1/SSLv3 cipher=AES128-SHA bits=128 verify=NO) for <json@ietf.org>; Tue, 29 Apr 2014 10:26:16 -0700 (MST) (envelope-from paul.hoffman@vpnc.org)
X-Authentication-Warning: hoffman.proper.com: Host 142-254-17-198.dsl.dynamic.fusionbroadband.com [142.254.17.198] claimed to be [10.20.30.90]
Content-Type: text/plain; charset=us-ascii
Mime-Version: 1.0 (Mac OS X Mail 7.2 \(1874\))
From: Paul Hoffman <paul.hoffman@vpnc.org>
In-Reply-To: <535EAFDF.2020403@cisco.com>
Date: Tue, 29 Apr 2014 10:26:13 -0700
Content-Transfer-Encoding: quoted-printable
Message-Id: <6456FCD4-E410-4FAB-96D0-E46260AABD9D@vpnc.org>
References: <535EAFDF.2020403@cisco.com>
To: IETF JSON WG <json@ietf.org>
X-Mailer: Apple Mail (2.1874)
Archived-At: http://mailarchive.ietf.org/arch/msg/json/6bbhOonefG_53G6kiM2Nt2w1Jpo
Subject: Re: [Json] I-JSON Topic #1: Media Types?
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: Tue, 29 Apr 2014 17:26:18 -0000

<no hat>

> "Should there be an I-JSON media type, or a application/*+i-json
> suffix?  Draft i-json-01 calls for it, but this is at best controversial."

No. A receiver can check whatever data it gets against whatever rules it wants. I-JSON is a standardized set of rules that an emitter probably wants to follow. And emitter saying "Look! I followed those rules!" cannot be trusted anyway.

--Paul Hoffman